Hi. thanks in advance. I have a fat model H NOR (which is fully capable of being jailbroken) but I am stuck on firmware 3.41. no matter what I do to update to an OFW or CFW, it will look at the data right before it installs and aways gives me the "data is corrupt" error. I am looking to run rebug if possible.
So I have this specific information:
several years ago I got a dongle that allows me to boot and install pkg files etc.
i am thinking this may be a reason why i am stuck not updating?
I am able to install certain package files including Multiman
Multiman however shows that the PS3 firmware is 0.00
I cannot use the internet browser for any web based updates because it is stuck on 3.41 and too old
I have tried all the safe mode settings including repairing database and restore defaults etc.
I have heard about putting it into factory settings mode, but i cannot boot into that screen where it show at the bottom right hand corner in red
Does anybody have any ideas as to how I can get to at least update my firmware? if I can get it up to 4.82 or so, I should be able to install rebug from there. but I cant get out of 3.41.
any ideas or help is appreciated! let me know if more info is needed. thanks in advance!
TD
There are various possible causes for update issues, you would need to provide more details including info about the console itself, for instance why & how did it end up in 3.41 or has it been on 3.41 ever since the official 3.41 update & unused for years?
Have you ever had any error codes when trying to install a pup? Only the no applicable data found message?
Has recovery ever asked you for a minimum firmware version when you tried to reinstall? If so what was it? 3.41 or other?
1. USB storage issue (the most common & luckily the easiest to address).
Disconnect all USB devices except the USB stick, don't use hubs, don't use an external hard drive or fancy storage devices.
Make sure the stick is partitioned in MBR scheme (not GPT) & the partition is fat32.
Make sure the pup files are not corrupted (use md5 checksum if need be).
Make sure the full path of the pup is in upper case like so: /PS3/UPDATE/PS3UPDAT.PUP
I suggest you try the USB stick with one of the XMB Audio/Video/Pictures features (try to copy a picture for instance) to make sure the system mounts the USB partition properly, that way you can confirm that the USB stick isn't the cause of the problem.
Use recovery mode option 6 (enter with power button sequence) instead of the XMB system update feature.
2. 999 downgrader issue.
Afaik it can happen when someone uses some 999 downgrader pup file to downgrade to 3.xx instead of the recommended way (ie enabling QA & using a standard pup file).
The syscon gets set to 9.99 so installing 4.8x is like a downgrade, if QA is not enabled, the update automatically fails.
If you can install pkg files, you could try running a QA toggler, you should be able to find pkg files on store.brewology.com or in our resources section.
There is also a set of dumpers & other tools that you might find useful.
https://github.com/bucanero/psl1ghtv2_ports
Note that I cannot guarantee that all those brews will be fully compatible with 3.41 though.
3. CEX/DEX issues
It can happen when Rebug REX/D-REX has been installed on a console & the console was converted with the Rebug Toolbox.
When in CEX mode, only CEX pup files can be installed
When in DEX mode, only DEX pup files can be installed, in which case you can install Rebug D-REX 4.84.2 & convert back to CEX.
4. FSM mode (Factory Service Mode)
Don't confuse with the standard recovery mode accessible with the power button sequence.
FSM is a mode you can get into to remarry BD drives & perform other such low level tasks. When a console is in FSM, you can see a red banner on XMB, you must NEVER try to update the firmware or you risk to partially brick the console.
You must always exit FSM (rebooting is not enough to exit FSM, you must reboot with the exit lv2diag.self on a USB dongle or use the exit FSM CFW Tools menu item on XMB if it's installed) before attempting any update.
5. Hardware related issues.
Hardware issues & HDD partitions corruption can lead to undefined behaviour when attempting to update. Usually the system spits out an error code but in some cases, it might not.
6. Jailbreak
OFW 4.8x can be installed on any console whereas CFWs require jailbreak.
Nowadays the easiest way to go & avoid confusion is to update directly to OFW 4.8x, then use the PS3 Toolset in the browser to jailbreak, reboot, install the CFW of your choice & enable QA permanently to avoid future installation issues.
etc.. etc...
