|
unable to upgrade to 3.71
|
|
|
kevbuzz
Junior Member
|
19. December 2007 @ 19:25 |
Link to this message
|
|
im having a little trouble upgrading to 3.71 m33. i upgraded o 3.51 and then to 3.52 and finally to 3.52 m33-3....but when i tried to upgrade to 3.71 i just keep getting a corrupt file instead of update program....i got the 3.71 eboot file and renamed it to 371.pbp...i copied the update folder to the correct directory and put the 371.pbp inside it and i get nothing...can anyone help please? let me know wot the problem is and how i can solve it...i chose to upgrade to 3.71 because i was using 3.03oeA before and it wouldnt let me play ps1 games and i couldnt figure out why...so someone sed to upgrade to 3.71 m33...so thats wot im trying to do...al i want out of all this is to play ps1 games on my psp. thanks any help appreciated.
howdy
|
|
Advertisement
|
|
|
|
Junior Member
|
19. December 2007 @ 19:37 |
Link to this message
|
|
Sorry but the file 371.pbp, is that the update file that you renamed and put in the update folder because thats what I'm assuming it is( make sure the update folder is inside the game folder). Do you have all the folder's such as M33 creator etc.. inside Game150 which is seperate from game folder but inside the psp folder?
My PSP History:
1.00 >1.5>2.00>1.5>3.03 OE-C>BRICKED>Pandora battery ^_^>1.5>3.03 OE-C>3.52 M33-2>3.71 M33-4
|
|
kevbuzz
Junior Member
|
19. December 2007 @ 21:17 |
Link to this message
|
|
ok heres wot i did...i downloaded the 3.71 firmware update folder...the readme sed to put this update folder in (memorycard/psp/game) so i put it in there...i then downloaded the 3.71 eboot.pbp file and renamed it to 371.pbp....i then pasted it into the update folder i placed on my memory card. wen i try to run it on my psp it just shows a corupt file
howdy
|
Junior Member
|
19. December 2007 @ 22:22 |
Link to this message
|
|
okay you put the update file in the correct place, where exactly did you put the 3.71 m33 update files? The program that needs the 3.71 udpate?
My PSP History:
1.00 >1.5>2.00>1.5>3.03 OE-C>BRICKED>Pandora battery ^_^>1.5>3.03 OE-C>3.52 M33-2>3.71 M33-4
|
Senior Member
|
19. December 2007 @ 22:48 |
Link to this message
|
|
Make sure the file you renamed does not have 2 .pbp extensions...
(example 371.PBP.PBP)
Go into one of your windows explorer windows and navigate to 'Tools', then 'folder options'-click the 'view' tab-Uncheck 'Hide extensions for known file types'
-and also make sure your kernel is set to 3.52 in the recovery console..Access recovery by fully powering down the psp (not sleep or standby), then while turning the psp back on, hold down the R trigger button to boot into recovery mode. From there, navigate to "configuration" and scroll to the
"homebrew folder currently set at..." you will want it at 3.52 rather than 1.50
If you still have trouble, try downloading your eboot from a different source.
This message has been edited since posting. Last time this message was edited on 19. December 2007 @ 22:54
|
|
bu22ard
Senior Member
|
20. December 2007 @ 04:31 |
Link to this message
|
|
3.71 EBOOT.PBP
hash values:
crc32: dd6352de
md5: 6babee6e1415ae27999928566adbd569
sha1: 07f01412992b072fd330e66d3ad05e1b71b6520a
this will allow you to check if you have the right EBOOT.
1.52>2.0>1.5>3.40 OE-A>3.71 M33-4
3.60>4.01 M33-2
|
|
kevbuzz
Junior Member
|
20. December 2007 @ 06:14 |
Link to this message
|
Originally posted by dEEz_nUtz:
Make sure the file you renamed does not have 2 .pbp extensions...
(example 371.PBP.PBP)
Go into one of your windows explorer windows and navigate to 'Tools', then 'folder options'-click the 'view' tab-Uncheck 'Hide extensions for known file types'
-and also make sure your kernel is set to 3.52 in the recovery console..Access recovery by fully powering down the psp (not sleep or standby), then while turning the psp back on, hold down the R trigger button to boot into recovery mode. From there, navigate to "configuration" and scroll to the
"homebrew folder currently set at..." you will want it at 3.52 rather than 1.50
If you still have trouble, try downloading your eboot from a different source.
ok i checked my kernel version and its 3.52 not 1.50...i also checked to make sure there wasnt 2 file extensions so that cant be the problem. i put the update folder in (memorycard/psp/game) i then put the 371.pbp into that folder. and when i try to run it it just shows up as a corrupt file. still need help
howdy
|
|
rafasmax
Junior Member
|
20. December 2007 @ 07:08 |
Link to this message
|
|
you need to be<on 3.52m33-4 hope that helped
PSP Modding - Dominated - GeN Fanboy
Wii Modding - Brick masta - Why didnt someone tell me to backup my NAND First?????
XBOX360 Modding - Uber Noob - Yeah im still looking into it...
Im the man and you .:try:. to follow me
8D
|
Senior Member
|
20. December 2007 @ 07:41 |
Link to this message
|
Originally posted by rafasmax:
you need to be<on 3.52m33-4 hope that helped
You could also be on 3.52 m33 -3 but being on update 4 is the best...
Other past updates like update 2 won't work don't know why...
:)
|
|
kevbuzz
Junior Member
|
20. December 2007 @ 07:51 |
Link to this message
|
|
you can do it on m33-3 it says in the readme file..but still i cnt do this...still need peoples help
howdy
|
|
kevbuzz
Junior Member
|
20. December 2007 @ 12:31 |
Link to this message
|
|
one more question is...do i really need to upgrade to 3.71 m33 to play ps1 games on my psp? can i do it with 3.52 m33-3? if not the please carry on tryin to help wiv the upgrade
howdy
|
Senior Member
|
21. December 2007 @ 08:53 |
Link to this message
|
Originally posted by kevbuzz:
one more question is...do i really need to upgrade to 3.71 m33 to play ps1 games on my psp? can i do it with 3.52 m33-3? if not the please carry on tryin to help wiv the upgrade
You could play PSX on 3.52 M33-3 ...
:)
|
|
rafasmax
Junior Member
|
25. December 2007 @ 11:07 |
Link to this message
|
still in this sticky it recomends m33-4, i would give it a try. if not you can always the the DCv3 to go to 3.71 m33-2, then upgrade. personallly i would stick with the 3.52m33-4 since your on a fat.
because to run homebrew on 3.71 and + you need to delete the korean font and free location player.
PSP Modding - Dominated - GeN Fanboy
Wii Modding - Brick masta - Why didnt someone tell me to backup my NAND First?????
XBOX360 Modding - Uber Noob - Yeah im still looking into it...
Im the man and you .:try:. to follow me
8D
This message has been edited since posting. Last time this message was edited on 25. December 2007 @ 11:10
|
|
Advertisement
|
|
|
AfterDawn Addict
|
25. December 2007 @ 12:17 |
Link to this message
|
Allot of the above advice given (1.50/3.52 kernel and 371.PBP.PBP) wouldn't make a difference when it came to the type of issue your having.
The issue with a corrupt data icon would be due to...
1) The UPDATE folder and EBOOT file inside is in the wrong directory. (Make sure the UPDATE folder is in the /PSP/GAME folder and "EBOOT.PBP, umodule.prx and 371.PBP" is in the UPDATE folder).
2) Your Memory Stick has an issue. (Format the Memory Stick via System Settings).
3) The 3.71 M33 update file you downloaded was corrupted some how (Download this 3.71 M33 file HERE and extract it. Drag the UPDATE folder to the /PSP/GAME folder (All files needed are in the UPDATE folder no need to add anything).
4) All the updating you did from 3.03 OE to 3.51 M33 to 3.52 M33 to 3.52 M33-3 messed up the instillation of the custom firmware in some way (Go HERE and follow this guide to recover back to 1.50 and then update to 3.52 M33-4 then use this guide HERE to update to 3.71 M33-4 + 1.50 ADD ON-2).
Try doing the below and see if it works first...
Format your Memory Stick (Make sure you back up anything you want saved before formating).
Then follow the advice under section 3) and download the provided file linked above under that section.
Now go to Game Menu Memory Stick and see if it shows being corrupt still. If it is not corrupt run the update.
If it is still corrupt then follow the advice under section 4) above to recover to 1.50 then go to 3.52 M33-4 then to 3.71 M33-4.
Going from 3.03 OE to 3.51 M33 then to 3.52 M33 then to 3.52 M33-3 is just allot of chances that 1 of the custom firmware instillation didn't go right and now has corrupted the custom firmware in some way.
This message has been edited since posting. Last time this message was edited on 25. December 2007 @ 12:27
|
