[JustChillin1414]

It looks like I may be buying it from modchipcentral.com (anyone have any experiance with them?). I will be getting the limited edition one since the standard is out of stock. Will I be able to follow the regular downgrade procedure to fix this or would I have to do something else in order to fix this? Like, would I have to do anything other than dumping, adding the e3_downgrade.bin to the microsd and reflashing?

[zecoxao]

just check the error code it gives and go to www.ps3devwiki.com section error codes...

edit: maybe your friend gave you a ps3 with a non working BD drive

edit2: readed your OP, perhaps it's another kind of error... anyhow you should just check what it returns before you buy something as a flasher just because you're getting an update failure

[saxile]

I've ordered from modchipcentral in the past, it's been a while though but I doubt they've changed since then, good company

[playerkp420]

I had someone drop off a console for me to downgrade for the, with this same problem.
First thing i did was try to update it to 4.11. Then it was is the loop you are talking about. From all the research I did to get it out of the loop a lot said it was bad blocks on the hard drive and there was a trick to get it out of the loop.

But this console was not the hdd. I tested it and it had 0 bad blocks. So I figured what the heck, I hooked my e3 flasher up to try and downgrade it.

To my amazement when I turned it on with the flasher installed, it completed the update. So i thought sweet. Now I can downgrade.

I proceeded with backups and got 3 good ones. Then continued with the downgrade procedures. But when i got to installing Rogero in fsm, it would not install. I would have to find the log file, but it said it errored at creating regions.

I could not figure it out and tried many different lv2diag.self and different pup files. Still the same thing. So I flashed the 4.11 backup back to it and it was stuck in the update loop again. Stuck at 99% then would give error.
Luckily the customer said whoever he bought it from was going to give him another.

Not sure how to fix this, even with e3 flasher. Just thought I would give you a heads up, as to what your getting into.

[zecoxao]

Originally Posted by playerkp420 I had someone drop off a console for me to downgrade for the, with this same problem. First thing i did was try to update it to 4.11. Then it was is the loop you are talking about. From all the research I did to get it out of the loop a lot said it was bad blocks on the hard drive and there was a trick to get it out of the loop. But this console was not the hdd. I tested it and it had 0 bad blocks. So I figured what the heck, I hooked my e3 flasher up to try and downgrade it. To my amazement when I turned it on with the flasher installed, it completed the update. So i thought sweet. Now I can downgrade. I proceeded with backups and got 3 good ones. Then continued with the downgrade procedures. But when i got to installing Rogero in fsm, it would not install. I would have to find the log file, but it said it errored at creating regions. I could not figure it out and tried many different lv2diag.self and different pup files. Still the same thing. So I flashed the 4.11 backup back to it and it was stuck in the update loop again. Stuck at 99% then would give error. Luckily the customer said whoever he bought it from was going to give him another. Not sure how to fix this, even with e3 flasher. Just thought I would give you a heads up, as to what your getting into.

like i said, checking what error it gives while updating usually does the trick. i had the same problem, 99% , loop, error after trying for 3 consecutive times. so i noted down the error and went to ps3devwiki. Surprise, surprise, the bd drive was disconnected from the motherboard :/ Mounted it back on and installed the firmware again. Went to 100% and even with a broken BD drive, i still managed to downgrade and get rogero no bd to work... and you know what? it installed pkgs :D ... this couldn't been done without the help of euss of course

[playerkp420]

Originally Posted by zecoxao like i said, checking what error it gives while updating usually does the trick. i had the same problem, 99% , loop, error after trying for 3 consecutive times. so i noted down the error and went to ps3devwiki. Surprise, surprise, the bd drive was disconnected from the motherboard :/ Mounted it back on and installed the firmware again. Went to 100% and even with a broken BD drive, i still managed to downgrade and get rogero no bd to work... and you know what? it installed pkgs :D ... this couldn't been done without the help of euss of course

It wasn't that easy. It was not the blue ray drive or the hdd. The error it gave after being stuck at 99% was 8002f313. Which is not even on the Error Codes page of ps3devwiki. The closest error to that on there is

Update error 	0x8002F285 	Issue with System Restore or installing Firmware update in Recovery Mode. Reboot system and reinstall firmware.

And rebooting the system and reinstalling did not work.

Here is one of the log files from when I tried to downgrade. I know your gonna say don't use JaiCraB, but this just happens to be the only log file I could find. I used both of these and the log files said same thing.

Lv2Diag version JaiCraB.NoBDv1
PackageName = /dev_usb000/PS3UPDAT.PUP
settle polling interval success
vflash is enabled...
creating system regions...
create storage region: (region id = 1)
create storage region: (region id = 2)
format partition: (region_id = 2, CELL_FS_UTILITY:HDD0, CELL_FS_UFS)
create storage region: (region id = 3)
format partition: (region_id = 3, CELL_FS_UTILITY:HDD1, CELL_FS_FAT)
creating system regions done.
boot from nor flash...
delete region failure(error = 0x8001000c)
delete storage region for Nor Flash failure. but it is not fatal error(0x8001000c).
creating nor flash regions...
create storage region: get device info device id = 0x100000000000004 failure(error = 0x80010002)
create_region() failure = 0x80010002
create storage region for Nor Flash failure
setup_storage_regions() failure
manufacturing updating FAILURE(0x8002f0e0)
Total Elapsed time = 16708 msec

I didn't get much info looking up those errors either.

EINVAL 	0x80010002 	Invalid argument.
EABORT 	0x8001000C 	The operation is aborted
Update error 	0x8002F0E0 	Error with installing Firmware update. Harddrive is not found or disconnected.

I believe it to be bad blocks on the nor or something.

I am just glad I do not have the console anymore. It was really giving me a headache trying to figure it out.

[zecoxao]

damn, that sucks then

[JustChillin1414]

But my problem is now that it says any firmware I throw at it is corrupted. Will the E3 flasher work or is the PS3 done?

[playerkp420]

Originally Posted by JustChillin1414 But my problem is now that it says any firmware I throw at it is corrupted. Will the E3 flasher work or is the PS3 done?

Take the hdd out of your ps3 and format it with your pc. Then put it back in your ps3 and follow the on screen instructions.

Edit - make sure you are getting the PS3UPDAT.PUP from a trusted source. And install from recovery.

[JustChillin1414]

I have tried downloading from the sony website and the link on the previous page, I think it was an update from 3.70 to 3.72 or 3.66 to 3.70 that went bad. It asks for 3.70 or later, I have tried installing 3.70 and 4.11. I just formatted my hdd, got into recovery mode, tried to do a system update, got error 8002F2C5 (firmware corrupted). I will try to download the firmware from the sony website one more time. I will compare it with the hashes on the ps3devwiki this time.