The above video goes away if you are a member and logged in, so log in now!
downgrade to fix semibrick(loop while update, i formated the hdd , think it semi bricked)
downgrade to fix semibrick(loop while update, i formated the hdd , think it semi bricked) –
can someone please help me i am tired of days of searching for answers
i have a 60gb fat console
it was on the 3 42 ofw i tried to update to 3 55 ofw it kept getting stuck around 70 so i tooked out the hdd and formated it on my pc
now my ps3 wont show anything on screen and powers itself down after 30 sec i can acces recovery mode
if i try ps3 system restore from recovery mode right after i format the hdd the ps3 turns off if i try again right after the first time it says that the hard drive cannot be accesed
i m thinking i have to rewrite the ps3's internal memory where the firmware is kept
and i m thinking i can only do that with a downgrade procedure
am i right ? will this work ? what are the risks given the console's current state
becasue i m thinking it s only semi bricked and don't want to completly brick it
someone please have mercy and help me out i ve spend all my free time the last few days on this problem not because i badly need to play but it keeps me up at night that i failed to solve it
i am trully sorry for the lack of punctation and wierd writing but i had to take all of it out because the site woldn t let me post it thinking i was posting links
PS3 SuperSlim 120gb Firmware: 4.31 OFW / PS3 Slim 1Tb Firmware: Rebug 4.30.2
sadly i don't have a dongle and no way of getting one where i live, i only have a android phone, can i use that instead?
i made progress, it began to install new firmware then at 60% and something ti jumped straight to 100% restarted and after that the green light briefly lights up then turns yellow then red light is blinking....any ideas?or is it dead for good this time?
ok after reading up on the ylod, i figured it can't be a coincidence that it overheated at the exact same time the update process completed, so i figured it was the faulty hardware that did the ylod due to the new firmware, witch would explain the first error when trying to update in the first time
only problem is now, how do i find out witch component isn't working?
Last edited by nightratts; 02-29-2012 at 07:02 PM.
any sugestions plz anyone?