Hello guys, I'm sorry if I'm posting this in the wrong category of subjects but this is a must-know, since a man learns from his mistakes. [and sorry for any bad english, i'm not a native speaker/writer]
Since lately i've been using CFW 4.91, webman, irisman, all kinds of apps and everything was good and working flawlessly. The console started to run a little louder and louder everyday so it was time to do a simple re-thermal paste job, cleaning job, you know, the usual.
Everything went well and smooth, and I've put everything back together and hoped for the best.
This were some hurried-up operations [on my end] so I guess no one should hurry up when doing such simple tasks.
After everything was back together it was time to re-start the console to check the temps and that everything works as it should.
Wait up a little (because here it becomes stressfull and funny).
Cables connected, and started the console by the button, I already pressed the Ps3 button on the controller but nothing happened (this was the first question mark in my head, why did she not start by wireless?).
Got almost to the XMB, then a prompt was on the screen to set up date&time; I did set it, and tried to start a game trough webman. Another prompt up-right screen saying 'webman is not running'. (this was the second question mark lol). At this point I was like "well what the hell did I do wrong?".
Here comes the fun:
- [First mistake] I was thinking about the firmware might have got corrupt (on the HDD or something, maybe a bad stop to the console by my side), but this wasn't the case.
- The next bad ideea was to download the official PS3 firmware and maybe to a re-CFW'it after that, that could have fixed everything right? No. That wasn't the case.
- ^ At this point I've got the OFW 4.91 on one FAT32 usb drive, got the console in recovery mode and tried the "Magic Update To OFW" lol, so when it was almost over, an error appeared about 70 to 80 percents of the install. The code was 8002F1F9 (more precisely said by google: your bluetooth/wifi module isn't working properly).
- Also google took me to various posts on the internet/reddit(hmm?)/this forum, and most of us replied they've changed the CMOS battery, or, ordered another bluetooth/wifi module from ebay or another places and got it working again. This, was not the case.
- After getting the code I decided to turn it off completely and see what should I do first.
* I took the battery out, swapped another one in (a better one), The first battery that was in the console had 2,80 Volts, the new one I've put in was 3,20 Volts. (altough this should be better, nothing ever happened). By changing the battery I've had to remove everything back again, thus, repasting the console again.
Restarted it, she started installing again, and again I've got the same error with the same error code.
* The battery being take cared of, I removed the cover again to look for anything that I have done wrong.
I could not figure out, but thinking backwards and about everything I did and, I DID IT,
the ideea came in and I GOT A STRAIGHT FACEPALM
=== the wiring from the WIFI/bluetooth module, to the MAIN PCB of the console was inverted in the connecting sockets, both of them of course ===, f**ck.
I've placed everything together as it should have been, and after starting the console the controller paired up wirelessly to the console.
This was a good sign, But at this point I was saving me a headache and put another CFW on the USB, to save me the re-unjail process.
Since the OFW never finished install, the NAND never got jailed again, did it? It did not.
Back into the recovery menu, updating the firmware straight to the latest EVILNAT CFW, and it worked like a charm this time.
The things to learn?
# If you are in a hurry don't do little things like this one, or if you are feeling like you are forgetting something in the process, #make a picture with your phone to see everything , and where-goes-what.
# If you are stuck in a boot-loop and try to go at least to the recovery mode, # swap in whatever hard drive you have (2.5inch ofc) or same factoryformat ssd, but remember, it must be formatted to # MBR, not GPT, and if possible, # FAT32 as the format, the console will format it to what she likes anyway.
# Always investigate the cause first, don't just stick that usb drive up like a laser-saber and start blasting it to the console because she won't get that scared
) she will actually give you a little headache in return for your arrogance and she will eat you like two hours of your life.
# Always keep one small empty hdd/ssd in any case if you use CFW.
# Be pacient
# Don't buy new wifi/bluetooth modules you won't actually need, always put the connecting cables the way they were when everything was working, lol.
Since lately i've been using CFW 4.91, webman, irisman, all kinds of apps and everything was good and working flawlessly. The console started to run a little louder and louder everyday so it was time to do a simple re-thermal paste job, cleaning job, you know, the usual.
Everything went well and smooth, and I've put everything back together and hoped for the best.
This were some hurried-up operations [on my end] so I guess no one should hurry up when doing such simple tasks.
After everything was back together it was time to re-start the console to check the temps and that everything works as it should.
Wait up a little (because here it becomes stressfull and funny).
Cables connected, and started the console by the button, I already pressed the Ps3 button on the controller but nothing happened (this was the first question mark in my head, why did she not start by wireless?).
Got almost to the XMB, then a prompt was on the screen to set up date&time; I did set it, and tried to start a game trough webman. Another prompt up-right screen saying 'webman is not running'. (this was the second question mark lol). At this point I was like "well what the hell did I do wrong?".
Here comes the fun:
- [First mistake] I was thinking about the firmware might have got corrupt (on the HDD or something, maybe a bad stop to the console by my side), but this wasn't the case.
- The next bad ideea was to download the official PS3 firmware and maybe to a re-CFW'it after that, that could have fixed everything right? No. That wasn't the case.
- ^ At this point I've got the OFW 4.91 on one FAT32 usb drive, got the console in recovery mode and tried the "Magic Update To OFW" lol, so when it was almost over, an error appeared about 70 to 80 percents of the install. The code was 8002F1F9 (more precisely said by google: your bluetooth/wifi module isn't working properly).
- Also google took me to various posts on the internet/reddit(hmm?)/this forum, and most of us replied they've changed the CMOS battery, or, ordered another bluetooth/wifi module from ebay or another places and got it working again. This, was not the case.
- After getting the code I decided to turn it off completely and see what should I do first.
* I took the battery out, swapped another one in (a better one), The first battery that was in the console had 2,80 Volts, the new one I've put in was 3,20 Volts. (altough this should be better, nothing ever happened). By changing the battery I've had to remove everything back again, thus, repasting the console again.
Restarted it, she started installing again, and again I've got the same error with the same error code.
* The battery being take cared of, I removed the cover again to look for anything that I have done wrong.
I could not figure out, but thinking backwards and about everything I did and, I DID IT,
the ideea came in and I GOT A STRAIGHT FACEPALM
=== the wiring from the WIFI/bluetooth module, to the MAIN PCB of the console was inverted in the connecting sockets, both of them of course ===, f**ck.
I've placed everything together as it should have been, and after starting the console the controller paired up wirelessly to the console.
This was a good sign, But at this point I was saving me a headache and put another CFW on the USB, to save me the re-unjail process.
Since the OFW never finished install, the NAND never got jailed again, did it? It did not.
Back into the recovery menu, updating the firmware straight to the latest EVILNAT CFW, and it worked like a charm this time.
The things to learn?
# If you are in a hurry don't do little things like this one, or if you are feeling like you are forgetting something in the process, #make a picture with your phone to see everything , and where-goes-what.
# If you are stuck in a boot-loop and try to go at least to the recovery mode, # swap in whatever hard drive you have (2.5inch ofc) or same factoryformat ssd, but remember, it must be formatted to # MBR, not GPT, and if possible, # FAT32 as the format, the console will format it to what she likes anyway.
# Always investigate the cause first, don't just stick that usb drive up like a laser-saber and start blasting it to the console because she won't get that scared
) she will actually give you a little headache in return for your arrogance and she will eat you like two hours of your life.# Always keep one small empty hdd/ssd in any case if you use CFW.
# Be pacient
# Don't buy new wifi/bluetooth modules you won't actually need, always put the connecting cables the way they were when everything was working, lol.
