PS3 is there a way to save a ps3 super slim that got an update loop? (error 8002f1f9)

M

Mav109

Forum Noob
A good friend of mine decided to entrust his beloved ps3 on my hands to install hen on it, and i accidentally got it on an update loop, from what Ive heard and tried its practically imposible to get out of it on a super slim model, but i read somewhere that replacing the hard drive could do something, and i was wondering if that could solve this major F%$# up of mine, the ps3 has a bad bluetooth/wifi chip and was running on OFW
 
Update: I managed to get out of the update loop, im gonna list the steps i followed.
youll need a usb stick with an ofw(I used 4.89 since the console was on that version before the update loop)

1. Turn on your ps3, count 4 seconds and remove your hard drive from your console, the console should ask you to connect a ps3 controller and to press the ps button. (if you get a blue screen the timing was off and should try it again)
2. insert back your hard drive into the console and plug your usb into the right usb port.
3. follow what the console says until you get to another update screen with the version you had on your usb drive, and when you get to the terms of service and user agreement, DECLINE THEM and CANCEL the operation, then it should boot you right back into the xmb.
I had to do it multiple times because after declining the ToS the console went back to the update loop, but it ended up working.


sorry for any typos, english is not my first language and im doing this in a hurry, but i hope this helps someone eventually
 
replacing the hdd may do something, but superslims I think come in both NOR and EMMC varieties. I don't know about all EMMC, but the 12GB versions of the superslim will store the firmware on the chips. I suspect that's what you have, because there's no way to install an update on a superslim with a broken bt. I think it's due to needing lv1 patches, which isn't doable with hen. it sucks that sony did that, I agree without you having to say anything. ;)
 
Mav109 said:
A good friend of mine decided to entrust his beloved ps3 on my hands to install hen on it, and i accidentally got it on an update loop, from what Ive heard and tried its practically imposible to get out of it on a super slim model, but i read somewhere that replacing the hard drive could do something, and i was wondering if that could solve this major F%$# up of mine, the ps3 has a bad bluetooth/wifi chip and was running on OFW
Click to expand...
It depends on the model - if it's NOR based then replacing or reformatting the HDD will fix the issue. If it's EMMC based I'm not sure it can be fixed.
 
Bootloop on eMMC models so far means perm brick. Just FYI. If we know logic structure of it, that probably would be possible to fix it having emmc flasher, just by overwriting one sector from dev_hdd1 area and forcing PS3 to format it (in assumption, that works the same as on NAND/NOR models). Obstacle is encryption layer, and without knowing how to decrypt any eMMC memory, we are unable to locate offset of that partition (which should be the same on all units).
 
Berion said:
Bootloop on eMMC models so far means perm brick. Just FYI. If we know logic structure of it, that probably would be possible to fix it having emmc flasher, just by overwriting one sector from dev_hdd1 area and forcing PS3 to format it (in assumption, that works the same as on NAND/NOR models). Obstacle is encryption layer, and without knowing how to decrypt any eMMC memory, we are unable to locate offset of that partition.
Click to expand...
It's a tedious process but you could in theory create a full eMMC backup and then overwrite like a KB of data with garbage and see whether it achieves the desired result, and if it doesn't then restore it from backup and overwrite another KB.
 
You cannot do that. Because eMMC is used not only for VHDD but what NOR/NAND contains. If You do that blindly, You will end in perm brick beyond repair for sure. Such trials on writing 512B, then test it, and in case of no results, test again, on 16GiB chip is quite extremely time consuming. Besides that, eMMC chips have banks inaccessible by readers and high probably Sony using them (they using them on PSC so we can be almost sure also on PS3).
 
Last edited:
If You have full dump from what is accessible, You can restore it of course. But imagine amount of data and tests on 16GiB size memory.
 
Mav109 said:
Update: I managed to get out of the update loop, im gonna list the steps i followed.
Click to expand...
Mav109 said:
youll need a usb stick with an ofw(I used 4.89 since the console was on that version before the update loop)

1. Turn on your ps3, count 4 seconds and remove your hard drive from your console, the console should ask you to connect a ps3 controller and to press the ps button. (if you get a blue screen the timing was off and should try it again)
2. insert back your hard drive into the console and plug your usb into the right usb port.
3. follow what the console says until you get to another update screen with the version you had on your usb drive, and when you get to the terms of service and user agreement, DECLINE THEM and CANCEL the operation, then it should boot you right back into the xmb.
I had to do it multiple times because after declining the ToS the console went back to the update loop, but it ended up working.


sorry for any typos, english is not my first language and im doing this in a hurry, but i hope this helps someone eventually
Click to expand...

Hello, I created this account just to comment that this method worked for my PS3 super slim CECH-4011B, with the same problem of the broken WiFi/BT module.
In my case I installed OFW 4.86, and a new 1000GB HDD, now I will look to see if I can install some HEN, update it to a more recent version or use it officially.
 
Mav109 said:
Update: I managed to get out of the update loop, im gonna list the steps i followed.
youll need a usb stick with an ofw(I used 4.89 since the console was on that version before the update loop)

1. Turn on your ps3, count 4 seconds and remove your hard drive from your console, the console should ask you to connect a ps3 controller and to press the ps button. (if you get a blue screen the timing was off and should try it again)
2. insert back your hard drive into the console and plug your usb into the right usb port.
3. follow what the console says until you get to another update screen with the version you had on your usb drive, and when you get to the terms of service and user agreement, DECLINE THEM and CANCEL the operation, then it should boot you right back into the xmb.
I had to do it multiple times because after declining the ToS the console went back to the update loop, but it ended up working.


sorry for any typos, english is not my first language and im doing this in a hurry, but i hope this helps someone eventually
Click to expand...
Is there any video tutorials on how to remove my hard drive for my console, never done this before.
 
BIack itout said:
Is there any video tutorials on how to remove my hard drive for my console, never done this before.
Click to expand...

based on my memory of my own superslim, one of the side panels slides, so you move that back, then detach it, then there's your hdd secured by a single screw. unscrew it from the system, pull out the caddie, unscrew the screws from the caddie. and, replace the hdd. it's very easy to do.
 
Mav109 said:
Update: I managed to get out of the update loop, im gonna list the steps i followed.
youll need a usb stick with an ofw(I used 4.89 since the console was on that version before the update loop)

1. Turn on your ps3, count 4 seconds and remove your hard drive from your console, the console should ask you to connect a ps3 controller and to press the ps button. (if you get a blue screen the timing was off and should try it again)
2. insert back your hard drive into the console and plug your usb into the right usb port.
3. follow what the console says until you get to another update screen with the version you had on your usb drive, and when you get to the terms of service and user agreement, DECLINE THEM and CANCEL the operation, then it should boot you right back into the xmb.
I had to do it multiple times because after declining the ToS the console went back to the update loop, but it ended up working.


sorry for any typos, english is not my first language and im doing this in a hurry, but i hope this helps someone eventually
Click to expand...


can i talk to you over something like discord about this? my tag is the following: pathologicaltruthteller
 
You must log in or register to reply here.

Similar threads

Back
Top