PS3Hax Network - Playstation 3 Hacks and Mods

PS3Hax Network - Playstation 3 Hacks and Mods (http://www.ps3hax.net/forums.php)
-   PS3 | Help (http://www.ps3hax.net/forumdisplay.php?f=10)
-   -   Anyone wanna help my poor console? (http://www.ps3hax.net/showthread.php?t=43635)

Bigbones87 09-27-2012 08:30 PM

Anyone wanna help my poor console?
 
Man....I have an awesome backwards compatible console on ofw 1.94. I can't get the system to update. The blue ray drive won't read discs, so I figured it was a bd drive on the fritz. I tried to install 3.55 noBDnoBT, but it failed. It gives me error 8002f147. Here is the bad part, since it is on such a low firmware I can't use recovery mode to update. I am updating though the XMb. When it fails, it asks me to restart the console, and then it boots back to 1.94 ofw. It isn't in an update loop per say, but I can't get it to 3.55. Would love if someone could help a poor old soul.

JustThatDude 09-27-2012 08:43 PM

Try FSM maybe and see if you can downgrade. Then if you can update to 3.55

Bigbones87 09-27-2012 08:49 PM

@JustThatDude Can I use fsm on such a low firmware? I have never used fsm for anything other than downgrading with a flasher. Same concept? Toggle fsm then put step1 lvl2diag and a firmware on USB then use lvl2 diag step 2 to exit.

playerkp420 09-27-2012 08:50 PM

Code:

Update error        0x8002F147        Error with installing Firmware update. Make sure the sourcedrive with the PUP is readable and reboot the system first
That is what ps3devwiki says that error is.

I guess the update is failing between 0% and 40%?

Quote:

0%-40%
Cause: At this point the update is verifying and unpacking files from the .pup, then updating files on the NAND (and HDD for newer consoles with NOR flash). In 9/10 cases any failures at this point are due to a corrupt update file which happens pretty easily if it has been downloaded over a poor wireless network or poor connection in general. Otherwise in rare cases there could be a write failure to flash which I have NEVER witnessed.
Fixes:Download the latest update version and prep a USB stick into FAT32. It maybe a good idea to double check the MD5 of the file to be certain it is a 1:1 copy once downloaded. Place the update named 'PS3UPDAT.PUP' on the USB device inside the correct folders (for example: F:\PS3\UPDATE). Anywhere else and the PS3 will not see the file. Swap out the current hard drive in the PS3 for a spare one, it doesn't have to be formatted or anything like that as the PS3 will do it for you. Now you will have to turn the console on but instead of booting it normally, put it into recovery mode. For anyone who doesn't know how to do that: hold the power button until the console turns on then off again, take your finger off and hold it down again so the console turns on again then wait for it to beep twice in quick succession before removing your finger. The console should then ask for you to connect a controller via cable and press the PS button. Once in recovery mode put your USB stick in any port and then choose the 'System Update' option. It will format, prepare and hopefully install the update without any further error.
SOURCE
************* [ - Post Merged - ] *************
Quote:

Originally Posted by Bigbones87 (Post 441888)
@JustThatDude Can I use fsm on such a low firmware? I have never used fsm for anything other than downgrading with a flasher. Same concept? Toggle fsm then put step1 lvl2diag and a firmware on USB then use lvl2 diag step 2 to exit.

It is not recommended to update in FSM!!

Bigbones87 09-27-2012 09:09 PM

@playerkp420 I am using a flash drive that I use on these all the times. Also, I am using the updat.pup I used to fix the chechg01 i had that you helped me with. I don't think it is the flash drive or the updat file. What would you do if it were your console? I'm anxious to get this thing Jailbroke, and the guy I got it from said the only time he got the disc drive to read a game it prompted him to update and he tried and he got the same error. Now the drive won't read DVD or blue ray discs. I am trying to use 3.55 noBDnoBT pup.
************* [ - Post Merged - ] *************
Oh yeah and this is a different hard drive then he was using, but it is a hard drive from a previous ps3 I had.

playerkp420 09-27-2012 09:16 PM

@Bigbones87

What percent does the update stop and give the error?

Bigbones87 09-27-2012 09:26 PM

Early on. Before 10%. Prolly like 5 or 6%. I'm not completely sure. I will check when I am near it if it is important. I thought about reformatting the hard drive to NTSC and let the ps3 reformat it, but I don't think that will help since it is a BC model and stores the firmware completely on the NAND. Head scratcher for sure. I only have an e3 flasher, so no reflashing. I would buy a progskeet, but I'm horrible at soldering and have no clue how to use it. @playerkp420

playerkp420 09-27-2012 10:14 PM

The PUP is copied to the hard drive, then installed to the nands.

Have you tried to update to, say 2.60 or whatever the first ofw with recovery menu.

Bigbones87 09-27-2012 10:24 PM

Nope. I will try that, although I don't hold much hope for it. If it installs to the hard drive like you say, then to the NAND then maybe it is a hard drive issue. It would be really weird tho because this is the second hard drive that has given this error. I will try the first update .pup that has recovery mode and see if it works. Maybe I should make a mfw with no bd check incase the bd drive board is bad, to prevent update loop. If the drive takes in and ejects discs and shows the swirling circle when I put a disc in, would you say it is a bad bd drive board or just a laser issue?

playerkp420 09-27-2012 11:06 PM

@Bigbones87

That sounds like a laser problem.

The blue ray is not what is stopping the update. It would stop between 65%-75%.

Maybe you could try to downgrade in FSM, if the console can go lower than 1.94. Then try and update.
Then if it is the rare "write failure to flash", maybe FSM downgrade would fix it. Or it would at least show us an error code in the log file if that fails too.


All times are GMT -5. The time now is 03:05 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.