PS3 PS3 Super Slim stuck in Update Loop and it soft-bricked. Error 8002F1F9 (Broken Bluetooth 100%)

V

vladyslavrom

Forum Noob
Hi guys,

Recently I wanted to update HFW because games wouldn't launch and started giving me an error. I was at 4.90.2 and wanted to update to 4.91.2. And I was stuck in update loop (my console Bluetooth was dead year ago), after this I was able to exit it in XMB with one method from Reddit, but on a flash drive I wrote OFW 4.90 and the console now has the official firmware. And because there was no way to play through the official firmware, I tried again to update console and then get out of the update loop. But I couldn't get past 30%, I just used to be able to get to 99% when it was on a flash drive OFW, and it was essentially updated. But now it didn't, so I try to exit update loop and my PS3 is not starting, it just soft bricked and go only to safe mode. I tried hard drive trick, but it don't pass after ~37%. Maybe anyone know how to fix this? Please help, and sorry for my bad English. I can't fix Bluetooth because in my city repair shops can't do this. Also I formatted hard drive so my data isn't important to me.

What I mean at soft bricked, when I try to update and cancel, it don't go to XMB it just turn off and when I power on it show green light and just turn off.
 
NightLess said:
Yes, I just searched it. I don't have a SS system so I'm not familiar with it. Sorry, it seems that only the BT problem can be solved to avoid getting stuck in the update loop.
https://www.psx-place.com/threads/super-slim-cech-4001c-boot-loop-error-8002f1f9-help.23236/page-2
I was looking at this thread, and it seems that the update can bypass the fault code by removing the hard drive during the update process. I don't know if it works...
Click to expand...
I dunno, man. I have a 12GB superslim myself, and I remember the firmware being intact even after removing the hdd. an hdd isn't required for that version of system iirc. it's like the NAND, but you can store all of the firmware on the emmc (including what would be installed to an hdd), so it's brick central with that type of system. afaik, there's nothing he can do. I don't know if you can repair the bluetooth on that system or not.
 
Charles_n_town said:
I dunno, man. I have a 12GB superslim myself, and I remember the firmware being intact even after removing the hdd. an hdd isn't required for that version of system iirc. it's like the NAND, but you can store all of the firmware on the emmc (including what would be installed to an hdd), so it's brick central with that type of system. afaik, there's nothing he can do. I don't know if you can repair the bluetooth on that system or not.
Click to expand...
You have to teardown and measure it to diagnose. I have only repaired 25XX Bluetooth models, and usually the voltage converters are broken because they are supplying power to the Bluetooth module when in standby mode.
 
NightLess said:
Yes, I just searched it. I don't have a SS system so I'm not familiar with it. Sorry, it seems that only the BT problem can be solved to avoid getting stuck in the update loop.
I was looking at this thread, and it seems that the update can bypass the fault code by removing the hard drive during the update process. I don't know if it works...
Click to expand...
Yes, I've seen this method and tried it many times but I can't find the moment where I need to eject the disk, because it always gives an error but a little later. But thanks anyway. One time I eject it good and it go to 99% but then error
 
I've grown too accustomed to bluetooth (even bought a brooks adapter for my ps2, when I had one, to use the dualsense, which worked perfectly after updating). I don't think I could handle a cord. I'm pretty sure when I owned the nes, snes, psx, genesis, etc. classics/mini, I had to have a wireless controller as not to trip over a wired one when coming back to my room. I remember the nes and snes especially had very short cables.
 
Charles_n_town said:
I've grown too accustomed to bluetooth (even bought a brooks adapter for my ps2, when I had one, to use the dualsense, which worked perfectly after updating). I don't think I could handle a cord. I'm pretty sure when I owned the nes, snes, psx, genesis, etc. classics/mini, I had to have a wireless controller as not to trip over a wired one when coming back to my room. I remember the nes and snes especially had very short cables.
Click to expand...
Wireless controllers can effectively protect your collection consoles from being tripped and damaged by wires XD. By the way, I just found this. If you have a multimeter and soldering equipment, you might as well try it. I hope that only the voltage converter or a capacitor is damaged instead of the entire BT module. If it is the latter, it will be more difficult.
 
NightLess said:
You have to teardown and measure it to diagnose. I have only repaired 25XX Bluetooth models, and usually the voltage converters are broken because they are supplying power to the Bluetooth module when in standby mode.
Click to expand...
I found a one post that says if unconnect power supply for 10 minutes it can pass the update, and I teardown it fully, I can measure it but can you please provide what voltage it must be on convertor, I'm not very knowledgeable about this.

((((

Charles_n_town said:
I dunno, man. I have a 12GB superslim myself, and I remember the firmware being intact even after removing the hdd. an hdd isn't required for that version of system iirc. it's like the NAND, but you can store all of the firmware on the emmc (including what would be installed to an hdd), so it's brick central with that type of system. afaik, there's nothing he can do. I don't know if you can repair the bluetooth on that system or not.
Click to expand...

Idk but I read that when you eject HDD you can bypass this check because at 21 to 30% it check hardware so you pull out at 20% and it didn't check it. Because to 20% the HDD light is blinking, so HDD is in use. Maybe at 20% it send command to check hardware.
 
Last edited by a moderator:
ebFTyLG.jpeg

This is the repair I made to the 25xx. I used the same AMS1117 1.8V buck converter as in the video. In my case, the original converter normally outputs 2.2v. I measured the output and found that it directly outputs 5.5v without conversion. Fortunately, the BT/WIFI module survived the high voltage. I removed the original buck converter and replaced it with AMS1117, which outputs 1.8v. It has been half a year and it still works well. I hope it can help you.
 
vladyslavrom said:
I found a one post that says if unconnect power supply for 10 minutes it can pass the update, and I teardown it fully, I can measure it but can you please provide what voltage it must be on convertor, I'm not very knowledgeable about this.

((((



Idk but I read that when you eject HDD you can bypass this check because at 21 to 30% it check hardware so you pull out at 20% and it didn't check it. Because to 20% the HDD light is blinking, so HDD is in use. Maybe at 20% it send command to check hardware.
Click to expand...
Super Slim? I don't have this game console. On Slim 25xx, you can get input ~5.5v and output ~2.3v. The key point is the output. Without ~2.3v, BT/WIFI will not work. In my case, the buck converter is damaged and the output is 5.5v (from PSU). The voltage is too high and it can't work. You can check the MLCC ceramic capacitors near the buck converter and on the BT/WIFI module to see if they are burnt/cracked or shorted to ground.
 
I restored my PS3!! I pulled out the disk at 21-27% and the update reached 99% and then to be honest, I don't remember what I did to go from update loop (maybe formatted [create 30 gb fat32 partition and other unlocated] my hard drive with PC, or put another formatted HDD to boot into recovery and then start the update but later decline Terms of Policy to cancel it) but it show me text that my hard drive need to be formatted and it formatted it and booted to xmb
 
vladyslavrom said:
I restored my PS3!! I pulled out the disk at 21-27% and the update reached 99% and then to be honest, I don't remember what I did to go from update loop (maybe formatted [create 30 gb fat32 partition and other unlocated] my hard drive with PC, or put another formatted HDD to boot into recovery and then start the update but later decline Terms of Policy to cancel it) but it show me text that my hard drive need to be formatted and it formatted it and booted to xmb
Click to expand...
That's good to hear.
 
You must log in or register to reply here.

Similar threads

Back
Top