[SonyH@K&R]

Originally Posted by euss Another death by not dehashing... Highly suspected downgraded console that bricked on lv1 hash checks when unpatched lv1 CFW was installed. 2 ways to fix: hardware flasher and following normal downgrade guide Factory Service mode with Cobra switch set on Downgrader and reinstall RogeroV3.1 followed by QA-toggle. References: http://www.ps3devwiki.com/wiki/Talk:...ia_Rogero_v3.1 http://www.ps3devwiki.com/wiki/Downg...rdware_flasher

Problem is he has no backup of ps3. How is he supposed to do? Make a backup, patch, and flash it?

[iPwnz]

Originally Posted by SonyH@K&R Problem is he has no backup of ps3. How is he supposed to do? Make a backup, patch, and flash it?

be sure youre psp is on 5.50 GEN-D and you use the rightest usb slot! then try again...

[euss]

Originally Posted by SonyH@K&R Problem is he has no backup of ps3. How is he supposed to do? Make a backup, patch, and flash it?

ofcourse if you did NOT click my links and read them, you would NOT know.

reverse is also true, if you clicked them, you would not be asking that, because you already was answered before asking.

but even without clicking, the shortguide explaination of how to fix was also posted, both ways.

[shuhratm]

Originally Posted by playerkp420 I hate to say, but I doubt there is a way to fix. Not without a bios backup from the console. You can install your e3 flasher. You will have to solder a wire from sbe point on ribbon to nor tristate on mobo. Or solder a wire from nor tristate to a ground point on mobo. This will keep the ps3 on to be able to make a backup and flash. Make a backup with switches 1 and 3 up, and the rest down. Then patch your backup with e3 autopatcher. Then flash the patched backup with all switches down. Reboot PS3 and then continue with service mode downgrade steps. This is assuming that this is a nor chip model PS3?

Working on this. Installed E3 flasher and soldered a wire. With 1 up and the rest down (flash fun on) the console did not turn off. I think that is already some progress. Will now try to backup and see how it goes.
************* [ - Post Merged - ] *************

Originally Posted by euss Another death by not dehashing... Highly suspected downgraded console that bricked on lv1 hash checks when unpatched lv1 CFW was installed. 2 ways to fix: hardware flasher and following normal downgrade guide Factory Service mode with Cobra switch set on Downgrader and reinstall RogeroV3.1 followed by QA-toggle. References: http://www.ps3devwiki.com/wiki/Talk:...ia_Rogero_v3.1 http://www.ps3devwiki.com/wiki/Downg...rdware_flasher

Thanks for the info. I have successfully downgraded my own console just recently and now on Cobra CFW. I will try the normal downgrade process and see how it goes. The console is dead anyways. Could it get even more dead??

[shuhratm]

Originally Posted by playerkp420 I hate to say, but I doubt there is a way to fix. Not without a bios backup from the console. You can install your e3 flasher. You will have to solder a wire from sbe point on ribbon to nor tristate on mobo. Or solder a wire from nor tristate to a ground point on mobo. This will keep the ps3 on to be able to make a backup and flash. Make a backup with switches 1 and 3 up, and the rest down. Then patch your backup with e3 autopatcher. Then flash the patched backup with all switches down. Reboot PS3 and then continue with service mode downgrade steps. This is assuming that this is a nor chip model PS3?

did the first two steps. got the backup and patched it. read the e3 flasher log... all seems to be ok and no read errors or anything.
after patching the backup, i should restore it with all switches down, but it wont stay on if not in flash fun mode. what should i do? flash it with flash fun mode on? makes any difference?

UPDATE:
Backed up, patched and restored the backup (in flash fun mode). The console is officially debricked now!! Thanks everyone for assistance.
Now... i went on with the normal downgrade and flashed the downgrade.bin to the console. Next, connected the dongle in downgrade mode and started the Step1 (Lv2diag.self,PS3UPDAT.PUP). With these two files in a thumb drive started the PS3 and the console, instead of getting flashed to the CFW that is in the drive, just turned on to the old Rogero that was in it in Factory/Service Mode.

Now what should I do next? Try to exit the service mode and live happy or try to upgrade to Rogero 3.1 and be even happier?
************* [ - Post Merged - ] *************
unable to exit factory/service mode... tried to update to another Rogero, but its not working. Placed Lv2diag.self and PS3UPDAT.PUP and even tried the step two file to exit - not working. Placed the PS3UPDAT.PUP in root and in /ps3/update folders - doesnt work either.
What should I do?
************* [ - Post Merged - ] *************
Darn IT!!! it was my thumb drives fault. everything worked. got Rogero 3.1. Thanks everyone for assistance.

[komran]

when shall I exactly remove that soldiered wire between NOR Tristate and ground point on Board ?


when exiting FUN MODE successfully ? or when the whole process finish ? and ROGERO 3.55 is restored successfully ?

cause I am de-bricking my ps3 and obtaining a BIOS dumb backup for the 1st time.


will this soldered wire over-heat the NOR flash if left for a longer time ?

[komran]

is it correct ,that if I succeeded in dumping Bios of my bricked console in "Flash Fun Mode" , but I didn't check / verify for errors.

then I patched using e-patcher , then flashed the console back , but it still didn't succeed to get de-bricked.

did I lose the ability to backup the Bios dump again ? or I still have a chance for a good bios dump backup ??


I could understand from some forums , that as long as I didn't write a Bios dump from another console on mine , I still have a good chance to de-brick my console , by trying again & again to obtain a good bios dump backup from my own console ?

true ??

[Bigbones87]

Not necessarily true. If you flashed bad bios to your nor and it succeeded in writing over all the information, like per console data, you just made yourself a pretty expensive paper weight. You should always check your bios for validity BEFORE flashing to the console. Let's say you got a bios dump, but when you opened the .bin in hex editor it is all 00 and ff in all lines, and you write that to your console. Now your playstation is basically completely empty of all bios information. If you don't already have a good backup to write to it, you can never retrieve your per console data as it is now 00 and ff. did you not read EVERY guide out there? Everyone says make sure you have valid bios dumps before continuing . You may be able to get a good dump still, but the only way to find out is to try. First make sure the ones you have are truly bad.

[baileyscream]

sorry to but in on the thread.

Originally Posted by euss Another death by not dehashing... Highly suspected downgraded console that bricked on lv1 hash checks when unpatched lv1 CFW was installed. 2 ways to fix: hardware flasher and following normal downgrade guide Factory Service mode with Cobra switch set on Downgrader and reinstall RogeroV3.1 followed by QA-toggle. References: http://www.ps3devwiki.com/wiki/Talk:...ia_Rogero_v3.1 http://www.ps3devwiki.com/wiki/Downg...rdware_flasher

is it just the Cobra that can access fsm when its "soft bricked" when de-hash has been missed?

i have tried with the avr but the console turns off to fast to activate fsm & i take it Cobra activates fsm for you?
or am i way off the mark?

cheers gandEUSS

[komran]

Originally Posted by Bigbones87 Not necessarily true. If you flashed bad bios to your nor and it succeeded in writing over all the information, like per console data, you just made yourself a pretty expensive paper weight. You should always check your bios for validity BEFORE flashing to the console. Let's say you got a bios dump, but when you opened the .bin in hex editor it is all 00 and ff in all lines, and you write that to your console. Now your playstation is basically completely empty of all bios information. If you don't already have a good backup to write to it, you can never retrieve your per console data as it is now 00 and ff. did you not read EVERY guide out there? Everyone says make sure you have valid bios dumps before continuing . You may be able to get a good dump still, but the only way to find out is to try. First make sure the ones you have are truly bad.

U r right. I had put my console on the hand of some illitrate technicans.. who think that by trial and error u can reach ure goal. I have no idea weather my bios is still alive or not . Will c today.
************* [ - Post Merged - ] *************
Hi Bigbones87,

do you know , which lines in the hex editor represent the "per console data" ? for a bios dump backup ?