Advancements in 1.51...
Won't work. It checks the update against the firmware version installed on the PSP.pinhocarlos wrote:EDIT: if we crate a folder in MS2 named UPDATE and put the 1.50 in it, and then create a folder called UPDATE1 and put the 1.52 in it... what will gona heppen??mvpo.geo wrote:How do you know this is an exploit? When you did this you had 1.52 update in....Im pretty sure that the update is gonna run fine when you have the 1.52 UPDATE in your PSP.
is this what U are think???
sorry for my poor english!
http://forums.ps2dev.org/viewtopic.php?t=2257 This thread outlines(somewhat) what is going on during the update procedure. As I have stated before:
We need a firmware specifically written to downgrade.
I think pinhocarlos is on the write track when he says that we should figure out a way to edit the files inside of the upgrade PBP to allow writing the upgrade files of a lower firmware version than the one currently installed to the psps memory. If we can figure out how to comment out the current firmware check in the updater and still be able to run it without it showing as corrupt we might have a shot at being able to downgrade.
-
- Posts: 10
- Joined: Mon Jun 27, 2005 7:24 am
we get to a point, which one we focus on, disable the firmware check so we can run the 1.50, or edit the 1.50 PBP and change the sfo for the 1.52... like, because if we just change the sfo and put the data.psp to "connect" with it, we will be fine...HaredX wrote:I think pinhocarlos is on the write track when he says that we should figure out a way to edit the files inside of the upgrade PBP to allow writing the upgrade files of a lower firmware version than the one currently installed to the psps memory. If we can figure out how to comment out the current firmware check in the updater and still be able to run it without it showing as corrupt we might have a shot at being able to downgrade.
-
- Posts: 10
- Joined: Mon Jun 27, 2005 7:24 am
-
- Posts: 14
- Joined: Sat Jun 25, 2005 5:11 am
-
- Posts: 10
- Joined: Mon Jun 27, 2005 7:24 am
-
- Posts: 10
- Joined: Mon Jun 27, 2005 7:24 am
I think it was already mensioned here but here it goes... when we plug in and plug out the AC Adapter a lot of times, it gives an error "battery low, charge battery" i think we need to explore this error and see why this error appers, becuase i was with 99% of battery and this error apper... i think with "this" error we can find the solution of downgrading"
-
- Posts: 12
- Joined: Sat Jun 25, 2005 2:42 pm
- Contact:
I have a 1.51 psp, and a 1.5. I've tried upgrading hte 1.51 to 1.52, and it tells me it cannot do that. Because the bettery charge is low (100%). Tested this with both batteries, same thing. One of them was new. wiped off my memory stick plenty of times, and redownloaded it. Same thing. This isn't even using a modded version of the upgrade, it just plain doesn't work.
-
- Posts: 12
- Joined: Sat Jun 25, 2005 2:42 pm
- Contact:
thats what im thinking dudepinhocarlos wrote:I think it was already mensioned here but here it goes... when we plug in and plug out the AC Adapter a lot of times, it gives an error "battery low, charge battery" i think we need to explore this error and see why this error appers, becuase i was with 99% of battery and this error apper... i think with "this" error we can find the solution of downgrading"
-
- Posts: 8
- Joined: Sun Jul 03, 2005 8:25 am
- Location: CA, USA
this is just an idea i got a few seconds ago, dunno if anybody has though of it or if it would even work...
what if someone wrote some kind of loader that would execute the update... but the loader just wouldnt execute it, it would stay in memory and watch or dump the update files as they are unencrypted and executed?
but then i suppose the problem would be a person needing an older psp to hack at the update... and then youd need a way to encrypt/sign it so it will run on newer psps...
it was just a thought...
what if someone wrote some kind of loader that would execute the update... but the loader just wouldnt execute it, it would stay in memory and watch or dump the update files as they are unencrypted and executed?
but then i suppose the problem would be a person needing an older psp to hack at the update... and then youd need a way to encrypt/sign it so it will run on newer psps...
it was just a thought...
I disagree.HaredX wrote:you guys are veering way off track here,
True but making it work by way of a downgrade might be the answer.we are trying to figure out how we can load homebrew on 1.51,
Eh.... not true. Coders make mistakes. I bet that it is still possible to run homebrew on 1.51 and 1.52. You just have to figure out where the mistake is and a way to exploit it.downgrading the psp via homebrew is obviously not an option
Refer to previous statement.because you need to be able to run homebrew to do that which 1.51 can't......
OK. I have said this once already....
Read the damned thread I linked to in my last post. It outlines just about every damn thing you guys are proposing here, save checksum alterations(if its possible I know not how to do it).
I tried the mix and match of SFO and Upgrade data, between 1.50 JP update, 1.51 US, and 1.52 US and JP updates. It doesn't work. The DATA.PSP probably contains a quick checking program that reads the flash and then reads the file's version # or check-sum or what have you.
The ONLY way to downgrade is get a job at Sony and(most certainly, illegally) write a downgrade program. Unless anyone of you know how to get the AES key and/or signature and code your own downgrade, I am afraid we wont be downgrading anytime soon...
Read the damned thread I linked to in my last post. It outlines just about every damn thing you guys are proposing here, save checksum alterations(if its possible I know not how to do it).
I tried the mix and match of SFO and Upgrade data, between 1.50 JP update, 1.51 US, and 1.52 US and JP updates. It doesn't work. The DATA.PSP probably contains a quick checking program that reads the flash and then reads the file's version # or check-sum or what have you.
The ONLY way to downgrade is get a job at Sony and(most certainly, illegally) write a downgrade program. Unless anyone of you know how to get the AES key and/or signature and code your own downgrade, I am afraid we wont be downgrading anytime soon...
If we could run homebrew on a 1.51 to downgrade, then we wouldn't need to downgrade to run homebrew, thats what I am saying, you proved my point more, the easiest way to run homebrew isnt to make homebrew that downgrades because by being able to run homebrew that downgrades the psp we have already accomplished it...Nick Fury wrote: True but making it work by way of a downgrade might be the answer.
Not true at all, I think that as soon as we find a way to access and write to the memory where the psp's system files are we can just copy and paste files from a earlier firmware dump into that directoryF9zDark wrote:Unless anyone of you know how to get the AES key and/or signature and code your own downgrade, I am afraid we wont be downgrading anytime soon...
-
- Posts: 14
- Joined: Sat Jun 25, 2005 5:11 am
well there might have been a flaw in a different area, not nessary in the booting stage. it could have been network bug, or something else causing the psp to crash or something.F9zDark wrote:Exactly. And that is out best bet, searching for holes.DrKickflip13 wrote:well they woudnt have made a 1.52 update if the 1.51 wasnt flawed...
There are 10 types of people in the world: Those who understand binary, and those who don't...
-
- Posts: 8
- Joined: Sun Jul 03, 2005 8:25 am
- Location: CA, USA
I didn't prove jack shit for you. Instead there was a misunderstanding by way of communication.HaredX wrote:If we could run homebrew on a 1.51 to downgrade, then we wouldn't need to downgrade to run homebrew, thats what I am saying, you proved my point more, the easiest way to run homebrew isnt to make homebrew that downgrades because by being able to run homebrew that downgrades the psp we have already accomplished it...
You seem to think that we need the ability to run homebrew applications on the PSP to downgrade the firmware. That's not necessarily the case as pointed out by other users in this very thread.
Don't assume that the downgrade will come by way of running homebrew. It could come by other means.