Other os 4.82 rebug black screen

PS3 model ?

The "boot flag" (to select either gameOS or otherOS) is stored in a region inside VFLASH
PS3 models with NOR flash type has the VFLASH region on hdd

I remember to read (from glevand) a solution for this is to overwrite that hdd sector (where is stored the boot flag) with another sector containing the boot flag set to "gameOS"

But i guess this sector needs to be taken from your hdd (before you made the change), so you cant get it now
Maybe it can be made by replacing the hdd temporally by other... and copy that sector from the new hdd... then overwrite the sector on the old hdd

Not sure, better wait for other people to reply with other ideas, and dont format the hdd yet
 
sandungas said:
PS3 model ?

The "boot flag" (to select either gameOS or otherOS) is stored in a region inside VFLASH
PS3 models with NOR flash type has the VFLASH region on hdd

I remember to read (from glevand) a solution for this is to overwrite that hdd sector (where is stored the boot flag) with another sector containing the boot flag set to "gameOS"

But i guess this sector needs to be taken from your hdd (before you made the change), so you cant get it now
Maybe it can be made by replacing the hdd temporally by other... and copy that sector from the new hdd... then overwrite the sector on the old hdd

Not sure, better wait for other people to reply with other ideas, and dont format the hdd yet
Click to expand...
Im hoping its not perma bricked or something cuz i love this model. :/
 
BobTheDuck said:
also its cechg01
Click to expand...
Ops, this PS3 model uses NAND flash, so the area i mentioned before named VFLASH (virtual flash) is actually inside the NAND (so is not virtual)

The concept of "virtual" means the system accesses to that region are redirected to a "virtual" region on hdd, but in your PS3 model you dont have that, take a read here:
http://www.psdevwiki.com/ps3/Talk:Harddrive#HDD_partitions
The boot flag is stored together with otherOS bootloader in a partition (or region in sony slang) that is located inmediatly after dev_flash3,named cell_ext_os_area
In your PS3 model is located inside NAND (compare both tables)
http://www.psdevwiki.com/ps3/Flash#NAND_Flash

There are some notes under the table also that applyes to this problem:
Sector backup/restore tips
-There are some specific sectors that contains criticall data or are prone to be lost, sectors can be regenerated by having the related keys, or can be overwritted from another hdd formatted in the same PS3 (all hdds formatted by the same PS3 shares the same encryption with the same keys)

-Some users lost the "HDD partition table" when connecting the HDD to a windows PC, because windows will try to "initialize" the HDD, and this initialization implyes to write an MBR of size 1 sector (so if the user accepts the initialization the first sector of the HDD will be lost). This can be solved by connecting another hdd to PS3 and allow PS3 to format it (this regenerates the HDD partition table), then is posible to connect the HDD to PC and "backup" the first sector with a hexeditor (like HxD)... this sector can be used to repair the other HDD. This process doesnt needs any key, is just a copy-paste of sectors from 2 HDD's

-When the "boot otheros" flag is used under GameOS, but the petitboot partition is damaged, or petitboot is not present, corrupted, etc... (or when failing at updating petitboot) the console enters is a loop/brick where the bootchain tryes to boot from petitboot, but the system is not able to find it. To fix this problem is needed to "regenerate" the contents of the petitboot region in PC as explained here: how to fix a corrupted petitboot region in PC. This process needs the keys

- Alternativelly, is posible to make backups of this criticall sectors in PC just in case some day are needed. Having the backuped sectors the fix consists simply in a copy-paste of them, no keys needed
Click to expand...
But in your PS3 all that group of VFLASH is inside the real NAND/s
This is an explain from glevand of how to decrypt that region, to make this is needed for you to have the "eEID root key" dumped previouslly, but he made it in a PS3 model with VFLASH in hdd, so doesnt applyes to you i guess
http://www.psdevwiki.com/ps3/Mounting_HDD_on_PC#Making_Changes_to_cell_ext_os_area_VFLASH_Region
As alternativelly i guess is posible in this models with VFLASH on hdd to replace the hdd temporally by a new one, allow the PS3 to format it, then use the "dd" linux command to copy that sectors containing the "boot flag" (with the default value to boot gameOS), then use this sectors to overwrrite the original hdd (where the problem happened)... so you recover your old hdd with all its contents booting normally to gameOS

But with NAND... i dunno if there is some other way :/
 
Last edited:
sandungas said:
Ops, this PS3 model uses NAND flash, so the area i mentioned before named VFLASH (virtual flash) is actually inside the NAND (so is not virtual)

The concept of "virtual" means the system accesses to that region are redirected to a "virtual" region on hdd, but in your PS3 model you dont have that, take a read here:
http://www.psdevwiki.com/ps3/Talk:Harddrive#HDD_partitions
The boot flag is stored together with otherOS bootloader in a partition (or region in sony slang) that is located inmediatly after dev_flash3,named cell_ext_os_area
In your PS3 model is located inside NAND (compare both tables)
http://www.psdevwiki.com/ps3/Flash#NAND_Flash

There are some notes under the table also that applyes to this problem:

But in your PS3 all that group of VFLASH is inside the real NAND/s
This is an explain from glevand of how to decrypt that region, to make this is needed for you to have the "eEID root key" dumped previouslly, but he made it in a PS3 model with VFLASH in hdd, so doesnt applyes to you i guess
http://www.psdevwiki.com/ps3/Mounting_HDD_on_PC#Making_Changes_to_cell_ext_os_area_VFLASH_Region
As alternativelly i guess is posible in this models with VFLASH on hdd to replace the hdd temporally by a new one, allow the PS3 to format it, then use the "dd" linux command to copy that sectors containing the "boot flag" (with the default value to boot gameOS), then use this sectors to overwrrite the original hdd (where the problem happened)... so you recover your old hdd with all its contents booting normally to gameOS

But with NAND... i dunno if there is some other way :/
Click to expand...
So im guessing ive got a new paper weight then?
 
sandungas said:
I cant tell for sure, i guess there must be some way to fix it with a flasher, but im a bit lost at this point, if i put myself inside your boots i would not know what to do next
Click to expand...
Well thanks for taking time out of your day to help gather a bit of info on it. Looks like its superslim ofw for me again. :/
 
BobTheDuck said:
Well thanks for taking time out of your day to help gather a bit of info on it. Looks like its superslim ofw for me again. :/
Click to expand...
Dont throw the towel yet, i guess sony had some prevention to get out of this egg-chicken loop
Is just i dont know much about this, i know it can happens and why it happens... but the solutions ?... no idea... you should do a loong hardcore google search to see what did the people that had this problem

I just found this talk http://www.ps3hax.net/showthread.php?t=45875
And while reading the first thing that came to mind is you should try to boot the PS3 in all (and any) posible boot modes known
http://www.psdevwiki.com/ps3/Boot_modes

Actually, they are saying it can be booted in "factory service mode"
Not sure if this is right... but it makes sense because "factory service mode" should override that boot flag you have in NAND that is redirecting the boot to petitboot (instead of gameOS)

Maybe is enought with entering in "factory service mode"... and exiting (and thats all, no other change needed)
Im guessing the boot flag is reset (to gameOS) when you enter
 
You must log in or register to reply here.

Similar threads

Back
Top