• Official PS3 Toolset is now supporting 4.92 Firmware

    View Official Release Post for additional information HERE

PS3 [BG Toolset] User Issues and Dump Submissions

Hmmm..

A) If you don't have an original dump made before patching, you cannot provide any proper referential to check for patching errors/corruption outside the boundaries of the 2 ROS regions targeted by the no-fsm patch, you would have no way to restore the Flash memory in case of corruption (even though chances of corruption of Flash memory areas without obvious warnings & error messages when using the PS3 Toolset's Flash Memory Manager are basically null as long as strict mode is kept turned on).
Not keeping a valid backup of the Flash memory before any patching attempt is always risky, such situations should be avoided at all cost..

B) Without the dump made after patching (with idps masked), nobody can check anything for you at all. If you don't provide the file, you can expect to get vague answers, unless someone experienced the exact same issue which in this case is doubtful because I have never heard of anything resembling your issue ever since the initial project release 15 months ago, to my knowledge, nobody has ever reported a "bootloop to recovery" situation found to be caused by successful no-fsm patching with the PS3 Toolset so far.

Have you validated the patched dump using the latest pyps3checker(available at github.com/littlebalup/PyPS3tools)?
If not, please do so & post screenshots of the log output (don't forget to mask idps when required, that goes for screenshots as much as for dump files, you should use the IDPS masker available in this thread's OP to remove the IDPS properly from your dump files before posting them).

C) How exactly did you go about patching the console with the PS3 Toolset?
1. Did you keep the Flash memory manager default strict mode turned on at all times as (strongly) recommended for all users except devs?
2. Did you simply load the 4.88 no-fsm patch using the "load patch via https" context menu entry?
3.Did the patch load successfully (success on patch loading progress dialog, no error, no warning)?
4.After you load the patch file in the Flash memory manager, you have to apply it, was the patch applied successfully (success on patch apply progress dialog, no error, no warning)?
5. After the patch was applied, did you get a toast message inviting you to reboot the console?

IF you answer yes to all 5 questions above, I can already tell you even without looking at your NOR dump that the patch process completed correctly & that the Flash memory was checked & validated successfully after patching.
If so, your issue is not related to the PS3 Toolset or the patching process & you would probably have had that issue no matter what.
IF you answer no to one or more of the 5 questions then you will need to describe in details everything you remember about the flashing process.

D) My guts feeling about this problem is that there is a hdd related issue & the system proceeds to the default behaviour in such cases ie reinstalling the system software (which may be bypassed by pressing the PS pad button although that doesn't guarantee the XMB will load successfully).
It could be caused by a file system issue on any of the system partitions of the internal hdd or maybe even the database needing rebuilt.
Anyway I cannot be 100% sure at this stage given the limited data at our disposal but for now I am enclined to think that your issue doesn't have anything to do with PS3 Toolset usage or no-fsm patching.
Have you tried reinstalling OFW 4.88 rather than a CFW?
Because they are unfamiliar with the process, people sometimes think they applied the patch but actually didn't, they only loaded the patch into RAM & it was never written to the Flash memory. If so the console remains unpatched & only OFW will install (make sure the usb key is properly formatted, MBR partition only & that the path to the PUP is correct, all in upper case).
If you need jailbreak confirmation, validating the NOR dump with pyps3checker, as I mentioned before, will tell you whether or not the no-fsm patch was applied successfully by the Flash Memory Manager or not at all.
 
Last edited:
i got it finally thanks coro so did bguerville you guys actually helped me solve my problem than when i asked 3 times and nobody was giving me the correct answer i need but you did id give you points on your profile but idk how to or if you can and now its installing evilnat again thank you so much
 
Good Day guys,

complete noob here when it comes to CFW/HFW.

So I decided to install PS3HEN since it looked simple enough and installed the bgtoolset as I thought it was needed (don't ask why I thought so, think I saw something of it in NETWORK on the XMB). Unfortunately it wasn't and ps3hen will not work. Also unable to get into safe mode to reinstall OFW, all I get is 3 beeps and the system starts as normal. Hen will not work and can't revert to OFW so I can't do over the HEN process without installing those tools as they are not needed.

Can anyone point me in the right direction to getting this resolved. Thanks in advance...

  • PS3 Model: CECH-[A01]
  • Firmware Version: [Stuck on HFW4.88]
  • IDPS Is Masked: [No]
  • Have Original Dump: [NO]
  • Have Patched Dump: [NO]
  • System Boots To XMB: [Yes]
  • System Boots To Recovery: [No]
  • Firmware Version Displayed In Recovery: [No Recovery/Safe Mode]
  • Minimum Firmware Version Displayed In Toolset: [VERSION_DISPLAYED]
  • Disc In Drive: [No]
 
AMEPSX1 said:
Good Day guys,

complete noob here when it comes to CFW/HFW.

So I decided to install PS3HEN since it looked simple enough and installed the bgtoolset as I thought it was needed (don't ask why I thought so, think I saw something of it in NETWORK on the XMB). Unfortunately it wasn't and ps3hen will not work. Also unable to get into safe mode to reinstall OFW, all I get is 3 beeps and the system starts as normal. Hen will not work and can't revert to OFW so I can't do over the HEN process without installing those tools as they are not needed.

Can anyone point me in the right direction to getting this resolved. Thanks in advance...

  • PS3 Model: CECH-[A01]
  • Firmware Version: [Stuck on HFW4.88]
  • IDPS Is Masked: [No]
  • Have Original Dump: [NO]
  • Have Patched Dump: [NO]
  • System Boots To XMB: [Yes]
  • System Boots To Recovery: [No]
  • Firmware Version Displayed In Recovery: [No Recovery/Safe Mode]
  • Minimum Firmware Version Displayed In Toolset: [VERSION_DISPLAYED]
  • Disc In Drive: [No]
Click to expand...
You need to take a step back & stop messing with your console before it's too late.
You are confusing CFW & HEN, they are completely different jailbreak methods.

HEN is a partial jailbreak usable on ALL console models, it is applied through a ps3 browser exploit at runtime (after each boot) on consoles running on HFW. It does not require the PS3 Toolset at all.

CFW is a full & semi permanent jailbreak solution, the most powerful you can get.
It is usable ONLY on fat models & slim models up to to cech-25xx & it comes in the shape of a PUP file. To install a CFW on a compatible console, you can use the PS3 Toolset on OFW 4.8x (no need for HFW) to patch the Flash memory & enable the installation of a CFW PUP file.

If your console is a fat cecha model (the very first ps3 model released, backwards compatible with ps2), you can choose between CFW & HEN, you cannot mix both.

If you want more details about the current state of the console jailbreak, you should post a screenshot of the PS3 Toolset loaded in the ps3 browser with Flash memory manager tab opened (remember to hide the idps with the context menu option).
 
Last edited:
bguerville said:
You need to take a step back & stop messing with your console before it's too late.
You are confusing CFW & HEN, they are completely different jailbreak methods.

HEN is a partial jailbreak usable on ALL console models, it is applied through a ps3 browser exploit at runtime (after each boot) on consoles running on HFW. It does not require the PS3 Toolset at all.

CFW is a full & semi permanent jailbreak solution, the most powerful you can get.
It is usable ONLY on fat models & slim models up to to cech-25xx & it comes in the shape of a PUP file. To install a CFW on a compatible console, you can use the PS3 Toolset on OFW 4.8x (no need for HFW) to patch the Flash memory & enable the installation of a CFW PUP file.

If your console is a fat cecha model (the very first ps3 model released, backwards compatible with ps2), you can choose between CFW & HEN, you cannot mix both.

If you want more details about the current state of the console jailbreak, you should post a screenshot of the PS3 Toolset loaded in the ps3 browser with Flash memory manager tab opened (remember to hide the idps with the context menu option).
Click to expand...

Hey, thanks for the response and sorry bout my late reply.
Oh Yes... Realized I screw up afterwards. Didn't do anything else since. I just want to get it back the way it was so I can use HEN. I've attached the image requested.
Thanks in advance...
 
AMEPSX1 said:

Hey, thanks for the response and sorry bout my late reply.
Oh Yes... Realized I screw up afterwards. Didn't do anything else since. I just want to get it back the way it was so I can use HEN. I've attached the image requested.
Thanks in advance...
Click to expand...
We cannot see the image you tried to attach.
It's not surprising though, check the image url in your post:
http://"F:\Desktop\Game Console Stuff\PS3 Stuff\20210819_170815.jpg"
 
AMEPSX1 said:
fe4FRQxR

Oh I'm sorry, thought it would have uploaded as an attachment. heres the mage link
https://mega.nz/file/fe4FRQxR#1E-JZ3uPckrlRZ6sSprWDUcXbGiAdn39s5akjkVNMuI
Click to expand...
According to your screenshot, the no-fsm patch for 4.88 CEX has been applied properly.
From here you must decide what you want, you cannot have both at the same time.

1. CFW
You must enter recovery mode to install a 4.88 CFW PUP file from usb storage. That's all.

2. HEN
You must enter recovery mode to install the 4.88 HFW pup file from usb storage. Then on reboot you must use the PS3 browser to install PS3HEN from **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new).
Refer to the HEN tutorial thread by Coro.

From the data you provided, I see no reason for recovery mode to fail to launch.
You might wanna check that you are using the right power button sequence.
 
bguerville said:
According to your screenshot, the no-fsm patch for 4.88 CEX has been applied properly.
From here you must decide what you want, you cannot have both at the same time.

1. CFW
You must enter recovery mode to install a 4.88 CFW PUP file from usb storage. That's all.

2. HEN
You must enter recovery mode to install the 4.88 HFW pup file from usb storage. Then on reboot you must use the PS3 browser to install PS3HEN from **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new).
Refer to the HEN tutorial thread by Coro.

From the data you provided, I see no reason for recovery mode to fail to launch.
You might wanna check that you are using the right power button sequence.
Click to expand...

Ok. lets see if i can explain this a bit more so it actually makes sense.
Originally, I updated the console to OFW 4.88 via the internet and everything was fine. After a few days on reading up on CFW and HEN, I decided to go with HEN as it seems the simplest to install and don't risk the console getting ban.

I downloaded the HEN 4.88 and put on my flash drive and did the update through the console's safe mode. All went well. As per #2 above, I went through with the console browser and installed the xploit and restarted the console.

At first it worked fine, was able to install IRISMAN and copied a couple games from disc to the system. After a few days, the console started to freeze on loading HEN or IRISMAN from the XMB, and only when i tried loading those programs, as i can launch and play games from DISC totally fine otherwise.

I tried reloading HEN from the beginning again, it would sometimes work perfect and sometimes freeze the console. I even replaced the HDD thinking maybe it had some bad sectors or so. But that didnt help.

I remembered seeing some video on HEN where a person opened the xploit page on the consoles browser and clicked on the tools and installed the patch. Thinking I needed to do that, I went ahead and did the same.

Now since then, even though the HEN firmware 4.88 loads fine, I cannot launch the HEN or IRISMAN on XMB. HEN just bounces me back to the XMB without loading, and IRISMAN either freezes or errors out. I tried getting back into safe mode to try reinstalling OFW, but that wont work. I touch and hold the console's power button for a few seconds, first i'll get the second beep then the console will turn off indicating video reset, immediatelly after I'll touch and hold the console power button to get into safe mode, but it just beeps once and then 3beeps and the console will load to the xmb normal. Trying the update from the XMB for OFW with the flash drive tells me "NO applicable update date was found", but if I put the HEN update file on the flash, it will find that update and will want to begin the update process.

So my whole delimma is that I want to get it back to OFW so i can start over the HEN installation adn figure out the freezing afterwards without interfering with anything else.

I will check the thread by CORO and see if it helps me...
 
It's like I said, you are using different tools for different jailbreaks at the same time.

Once you had installed HFW then HEN there was nothing more to do, that was it, why on earth did you use the PS3 Toolset to flash the patch memory?
Because you saw a guy on a video doing that? That's exactly why I do not recommend using YT videos as trusted learning material in general, too many vid posters simply don't have a clue about what they are trying to teach, a bit like a music teacher who could not read, write or play music.
Well no matter the reason, you should not have done it on a whim, patching the Flash memory can potentially kill the console, it should never be done casually.

Anyway luckily for you the Toolset patching process is quite safe & it should not have impacted the console system.

Firmware cannot be reinstalled from XMB, only updated, so you must get into recovery mode to install a 4.88 PUP, that's perfectly normal.
The recovery mode files on your system are fine so any problem you may have to enter recovery mode should be unrelated to the Toolset patching.
 
bguerville said:
It's like I said, you are using different tools for different jailbreaks at the same time.

Once you had installed HFW then HEN there was nothing more to do, that was it, why on earth did you use the PS3 Toolset to flash the patch memory?
Because you saw a guy on a video doing that? That's exactly why I do not recommend using YT videos as trusted learning material in general, too many vid posters simply don't have a clue about what they are trying to teach, a bit like a music teacher who could not read, write or play music.
Well no matter the reason, you should not have done it on a whim, patching the Flash memory can potentially kill the console, it should never be done casually.

Anyway luckily for you the Toolset patching process is quite safe & it should not have impacted the console system.

Firmware cannot be reinstalled from XMB, only updated, so you must get into recovery mode to install a 4.88 PUP, that's perfectly normal.
The recovery mode files on your system are fine so any problem you may have to enter recovery mode should be unrelated to the Toolset patching.
Click to expand...
OK... I fully understand that I made alot of mistakes from the beginning, and you've made it clear that I've done so from the beginning, but it seems that somehow installing your tool is blocking the system from entering recovery mode to do anything else. How do I uninstall your tool and get back to OFW as I want. YOUR toolset is blocking me... I WANT TO UNINSTALL that tool and get back OFW. HOW HOW HOW? I cannot get into recovery mode as I keep explaining... Thank You...
 
First of all, I am merely trying to help, I am not trying to make you feel like a fool, you made a mistake, big deal, we all do, the only thing that should matter is what you learn from the experience.
Secondly every homebrew & every hack made available to the public are "use at your own risk" things.
Thirdly, my tool, as you put it, doesn't install anything else on the console than the no-fsm patch for the Flash memory from @littlebalup's pyps3tools project (for hardware flashers) & from your screenshot I can tell you the patch was applied successfully because the sha256 hashes of both your Flash memory ROS regions match that of the patch.
This 4.88 no-fsm patch is basically an Evilnat 4.88 standard CEX CFW CoreOS, it has been fully tested & nobody has ever reported to me any recovery mode issues until now but then again I don't know whether anyone has done what you have just done so far, I would assume it is probable because accidents & errors happen but I haven't seen any such reports yet.
Having said that, if you feel there is a problem with the patch, you need to take up that conversation with littlebalup himself because I didn't make it.

In the meantime, I can think of 3 ways to remove the patch.
1. Reinstall a firmware pup file.
2. Use a hardware flasher to rewrite the ROS regions with the 4.88 OFW CoreOS.
3. Patch the Flash memory again with "my tool" but using a custom patch file that contains the 4.88 OFW CoreOS.
That would bring you back exactly where you were before ever patching the Flash memory.
Anyone on OFW 4.88 can make a patch for you using the PS3 Toolset ROS dump feature on an appropriate OFW 4.88 ROS. At your own risk all over again.

And finally, when you use a jailbreak whether it's HEN or CFW, you acquire extended capabilities, like acquiring admin permissions on Windows or root permissions on Linux.
It means that once the jailbreak is applied, it becomes possible to do things that can damage your system, just like you can damage a pc system by doing the wrong things. It's good to keep that in mind when discovering HEN or CFW.

Also strictly speaking, applying the no-fsm patch with the PS3 Toolset when HEN is installed/enabled & running should not be a problem with a CFW compatible console, at least in theory as I never tried, and in any case it should not impact the recovery mode in particular.
 
Last edited:
I have never tried to do this though & I offer no guarantee it would work.

After installing a no-fsm patch (and before installing a CFW PUP), if the console is CFW compatible, on reboot the system will be running on CoreOS CFW & standard CEX CFW custom syscalls will be available.
If you install the no-fsm patch on a slim 3xxx or superslim, the console will brick but on a CFW compatible model that will give the console CFW capabilities at hypervisor & kernel level, even if the XMB stuff is still OFW.
You can see in the PS3 Toolset whether CFW custom syscalls have been detected & it's the case in the posted screenshot.

Consequently HEN should not be needed to execute a homebrew & if you had HEN installed already before, you should still have a working pkg manager item on XMB so you should be able to install homebrews from usb.
If so, that may potentially offer a couple of solutions. You could for instance install/run a self executable homebrew with a feature to reboot the console into recovery mode & see if that works out. The Rebug Toolbox among others should be able to do that.

Or one might even be able to enable QA flag with a QA toggler homebrew, iirc after reboot, that might make firmware installation including downgrades possible from the XMB (to be confirmed, I haven't used that feature for a while tbh).

Again it is just an idea, I dunno whether it will work out or whether certain homebrews may experience issues with such an hybrid setup & I cannot try it to confirm.
 
Last edited:
@bguerville Quick question for you. First off my issue isn't related to any issue that sprang up from your toolset. I've had fantastic luck using it everytime. Thank you for making it!

I'm just in the process of trying to gather information and necessary hardware to fix my CECHA console that unfortunately seems to have fallen victim to a bad flash (it appears) after attempting a 1.5 tb installation upgrade. Long story short, I was advised by a fellow scene member to downgrade to 4.46 in order to complete this larger upgrade install. I installed 4.46 habib, it seemed to take the drive upgrade fine at first, showed the proper space, it was when I attempted to bring it back to 4.88 Evilnat, that something went wrong after it started copying the pup file, and the console just shut off. Since then I can't get it to accept any drive, or boot into XMB. It also refuses to recognize any HD even in recovery mode. Seems to me like a corrupted nand issue, a few others have chimed in on my posts and seem to agree. Sorry that was long winded lol.

My question is this. I have a 4.88 backup (think I took 2) I took using your toolset. Is there a certain patcher program that I will need to use in order to patch these and install them on my nands once I get the proper hardware in order to accomplish this? I appreciate any advice you can offer.
 
Checkity_CheckYoSelf said:
@bguerville Quick question for you. First off my issue isn't related to any issue that sprang up from your toolset. I've had fantastic luck using it everytime. Thank you for making it!

I'm just in the process of trying to gather information and necessary hardware to fix my CECHA console that unfortunately seems to have fallen victim to a bad flash (it appears) after attempting a 1.5 tb installation upgrade. Long story short, I was advised by a fellow scene member to downgrade to 4.46 in order to complete this larger upgrade install. I installed 4.46 habib, it seemed to take the drive upgrade fine at first, showed the proper space, it was when I attempted to bring it back to 4.88 Evilnat, that something went wrong after it started copying the pup file, and the console just shut off. Since then I can't get it to accept any drive, or boot into XMB. It also refuses to recognize any HD even in recovery mode. Seems to me like a corrupted nand issue, a few others have chimed in on my posts and seem to agree. Sorry that was long winded lol.

My question is this. I have a 4.88 backup (think I took 2) I took using your toolset. Is there a certain patcher program that I will need to use in order to patch these and install them on my nands once I get the proper hardware in order to accomplish this? I appreciate any advice you can offer.
Click to expand...
CoreOS corruption is extremely unlikely.

Given the system the ps3 uses to update CoreOS, it should not be possible to get corruption when an update procedure fails.
The system purposefully provides 2 ros regions to store CoreOS but uses only one at a given time.
Say the console currently uses ros0 & you update the firmware, the updated CoreOS installation will take place in ros1 & the active ros currently set to ros0 (in syscon for nor & in the ros header in nand) will only be set to ros1 after the update process is complete & verified successfully.
So if there is a power failure during the update procedure, the active ros remains set to ros0 & no harm is done to the console as the "corrupted" ros1 region is never used.

Anyway, if you cannot get access to the XMB, you are stuck & only a hardware flasher can write to the Flash memory.
On nand, that means installing a Teensy board & going through roughly the same steps as you would for CFW installation via hardware flashing.
 
Last edited:
bguerville said:
CoreOS corruption is extremely unlikely.

Given the system the ps3 uses to update CoreOS, it should not be possible to get corruption when an update procedure fails.
The system purposefully provides 2 ros regions to store CoreOS but uses only one at a given time.
Say the console currently uses ros0 & you update the firmware, the updated CoreOS installation will take place in ros1 & the active ros currently set to ros0 (in syscon for nor & in the ros header in nand) will only be set to ros1 after the update process is complete & verified successfully.
So if there is a power failure during the update procedure, the active ros remains set to ros0 & no harm is done to the console as the "corrupted" ros1 region is never used.

Anyway, if you cannot get access to the XMB, you are stuck & only a hardware flasher can write to the Flash memory.
On nand, that means installing a Teensy board & going through roughly the same steps as you would for CFW installation via hardware flashing.
Click to expand...
Yea this is the route i'm looking at going since no other option seems to be working. Do you know by chance is it necessary to patch these dumps I took from your site before installing them? also is it necessary to downgrade, or am I just able to flash with these dumps in order to restore my XMB access? It is QA enabled btw if that helps. Thank you for your suggestion
 
Checkity_CheckYoSelf said:
Yea this is the route i'm looking at going since no other option seems to be working. Do you know by chance is it necessary to patch these dumps I took from your site before installing them? also is it necessary to downgrade, or am I just able to flash with these dumps in order to restore my XMB access? It is QA enabled btw if that helps. Thank you for your suggestion
Click to expand...

Sorry to ask this if you've already answer it, but can't you get into Recovery Mode and do a system update from there?. If your console is QA enabled already, that's a huge advantage in installing anything.

Try to check every posibility out before taking the last resort: soldering and flashing.
 
GuilloteTesla said:
Sorry to ask this if you've already answer it, but can't you get into Recovery Mode and do a system update from there?. If your console is QA enabled already, that's a huge advantage in installing anything.

Try to check every posibility out before taking the last resort: soldering and flashing.
Click to expand...
No unfortunately, it refuses to see any other HDD I put into it, even in recovery mode. It won't flash firmware if it can't read your drive.
 
Checkity_CheckYoSelf said:
No unfortunately, it refuses to see any other HDD I put into it, even in recovery mode. It won't flash firmware if it can't read your drive.
Click to expand...

I've run into kinda same problem with my NOR Slim 2501B model. After a full format HDD, the system refused to boot into XMB and Recovery Mode didn't detect my HDD (which was the factory one). So, I've surrendered, called it a brick and disconnected everything.

But the following morning, I've decided to give it another shot by downloading 4.88 OFW, triple MD5 check, using two old USB thumbs (FAT32 MBR, 512 MB each) and booted into Recovery Mode.

First, I've selected Restore file system in order to let the PS3 format the HDD and set everything up. Then, I've update the FW and everything went good. I was relieved that my console didn't brick and saved almost U$D 250 for an E3 Flasher.

I believe that maybe there is some capacitor or circuitry that holds some charge and blocks some chip or processor into booting properly.
 
You must log in or register to reply here.

Similar threads

Back
Top