The above video goes away if you are a member and logged in, so log in now!
Purposely Bricked My CECHE01 256MB with Factory Service Mode in Update Loop 8002F14E, Recovered w/o my Infectus
Purposely Bricked My CECHE01 256MB with Factory Service Mode in Update Loop 8002F14E, Recovered w/o my Infectus –
I did this with the intention of actually using my Infectus to read/write the nand of my ps3 that will not likely take the heat gun anymore.
Garyopa testing 3.55 LV2diag.self B4 sending a faulty console 2 the recycle bin gave me the idea originally.
My First Post So Any Interest and Comments are Appreciated
I have a 80GB CECHE01 doesn't read disks and I have done a bunch of reflows just sitting around that had 3.55 rebug also a Infectus 2 doing nothing so I started the DG without the drive connected green light blinked green for 45min killed the power was able to get into recovery restored 3.55OFW got (8002F14E) I let it loop until it tells you to power down. NOW the fun part !! stuck my E3 in and (jb) instant RSOD what I had hoped for,
Update 0% RSOD with 3.55,DG files, even DG files patched lv2. I for sure bricked/corrupted the nand so off I went to find how to install the infectus and recover with CVOS v3.1 and a lot of people with 256MB nand bricked/RSOD could not fix then using any suggested method that worked on most 16MB fat, (format HDD,remove battery and so on. when I came home I started taking the ps3 apart removed the HDD and went to format and windows couldn't see it, used disk management to format it and I everything I read said 256MB consoles do not rely on the hard drive for updates and OS and doing just that would not help the RSOD, So I thought what the hell I will try putting the patched lv2 and modified 3,41 and a usb stick it in and hit power..
Now this makes no sense to anything I have read or even the process of factory service mode light sequence !!
The light stayed solid green (meaning in the DG tutorial use different flash drive) But NO RSOD and after 10sec or so my usb flashed a few times 10 more sec flashed a few more (still solid green) by the power button and after a while the activity light on the usb picked up and the console started flashing green, Thinking to myself no way its going finish but it did ????? Put it file 2 and 10sec later shutdown removed it and pressed power and It surprised me with a different boot logo I don't ever remember seeing (black screen w/ Sony Entertainment no fancy XMB wave.
Some people have actually fixed their rsod by formatting their hdd, I think that you have corrupted the nand but not in a way to cause bad sectors so it may have overwritten the flash if not I hope this leads to something that doesn't require 50+ wires to solder
I'm fairly new to the PS3 never owned one until geohot released his first exploit Downgraded my 360 years ago with Infectus and have been waiting for a use for a ps3 dump because until recently dumping your nand was kind of useless.
Originally Posted by foenix
Anyway the part that didn't make sense is somehow in recovery mode update loop booted my E3 (jb) instant RSOD at 0% recovery mode update, I used the DG files as if I were already in factory service mode and It at first acted like a semi-brick (no flashing yellow lights on the console solid green then it started very slowly reading from the usb,
I'm no expert but the yellow lights I assume the console indicating R/W of the nand and when I downgraded and it failed it flashed the yellow lights like the tutorial said it would.
This could be absolutely useless information but on the other hand maybe not. I will try and recreate what I did and record it because someone stuck in a update loop could possibly fix it for $11 I paid for my E3 from *********** instead of a lot more on a new console If you know what I mean.
This site has been a one stop shop for everything and again thanks to Garyopa for the idea of testing or trying something that will almost certainly make the console never work again!!
knowing that I have never shelled out a single cent to Sony and for someone with nothing to loose or no eBay account to recoup a few bucks give it a try and see if it helps
Thanks Again for the reply foenix
So these were your steps just to clarify,
Restored 3.55ofw through recovery mode
Used 3.55 e3 downgrade files
Booted into factory service mode with e3 caused rsod
Booted with 3.41 downgrade files
Booted lv2diag to exit factory service mode
did you enter factory service mode before you got rsod?
sorry for the questions I am a bit inquisitive
3.55.1 normal mode
Originally Posted by foenix
Infinite flashing green light didn't self power down LOG
manufacturing updating start
PackageName = /dev_usb000/PS3UPDAT.PUP
settle polling interval success
vflash is disabled...
boot from nand flash...
creating flash regions...
create storage region: (region id = 2)
format partition: (region_id = 2, CELL_FS_IOS:BUILTIN_FLSH1, CELL_FS_FAT)
create storage region: (region id = 3)
format partition: (region_id = 3, CELL_FS_IOS:BUILTIN_FLSH2, CELL_FS_FAT)
create storage region: (region id = 4)
format partition: (region_id = 4, CELL_FS_IOS:BUILTIN_FLSH3, CELL_FS_FAT)
create storage region: (region id = 5)
create storage region: (region id = 6)
taking a while...
start Updating Proccess
Initialize elapsed time = 54 msec
Check UPL elapsed time = 56 msec
check Package Size
get package size elapsed time = 8 msec
start Updating Package
Update packages num = 30
Update packages total size = 162260220
Update Package Revoke list
read package revoke list package (576 bytes) elapsed = 24 msec
update package revoke list elapsed = 111 msec
Update Package Revoke list done(0x8002f000)
Update Core OS Package
read core os package (5182047 bytes) elapsed = 286 msec
update core os package elapsed = 195 msec
Update Core OS Package done(0x8002f14b)
update package elapsed time = 616 msec
Updating or Verifying failure 0x8002f14b
manufacturing updating FAILURE(0x8002f14b)
Total Elapsed time = 1965 msec
It acted like semi-brick only booted recovery (hold power beeps)
UPDATE 3.55ofw failed at 75% (0x8002f14b)
Loop until it says power down wait retry whatever
Stuck E3 in (power+Eject) RSOD
Rebooted and it began trying the 3.55ofw restore again
0% RSOD no matter what I did I got the same error(booting E3(jb),3.55ofw@ps3/update
no flash drive Always the same 0% RSOD
spent the day away from home searching the net on how to install infectus and reading other posts about RSOD, semi-bricks, bricks and everything in between, Got home and removed the hard drive formatted it and put it back in
NOTE EXACTLY WHAT I DID (the part that makes no scene to me)
PS3UPDAT.PUP (modified 3.41)
Pressed power (no e3 no jb just power and console light was solid green about 10sec
the usb status light blinked a few times slowly picked up and starting flashing powered down
file2 self powered down
power boot to 3.41
last night I got the console back to 3.55.1 what it was before and if not before Saturday I'm going record this entire process because if I can do it twice that has to mean something if not I can again go back to rebug and wait for it to die playing snes DR.MARIO and moonwalker for saga
I'm happy to answer questions because maybe help someone fix there ps3 or even 1 more thing to try before giving up.
Thanks Again !!!
thank's mate, I am going to try and emulate your procedure tonight as I have a 3.41 with rsod, going to upgrade to 3.55 and see if it makes a difference, I have tried everything with my rsod console and was going to toss it or use for parts but you haven put light into the rsod darkness
3.55 is the base version of how I did it, can you get into recovery mode because that's essential for how I got it to work.
Originally Posted by foenix
Let me know how it works and what it took for the RSOD to happen in your case