Then It will be a bad new for those who having a new PSP.
I read some information from your blog about you re-flash 1007 PSP to 1.0 and try to update it to 1.5 but not sucess. I think one of the possible reason is , the 2.X machine change the decrypt(IPL) process in both software and hardware way. So if we update our PSP from 1.0 to 2.X , after PSP updated it use software way to emulate 2.X hardware IPL. But for 2.X PSP from factory , it use hardware way to do IPL.
If my guess is right , even if you downgrade the new PSP to 1.0 , it should not be able to run any sign code, and that's why you cant run the 1.5 updater. (The reason why you can run 1.0 VSH because most of the function in 1.0 flash is not encrypt) And I think if we re-flash the 1.5 firmware to new PSP , the VSH cant load. (This may be also the reason why the multi-firmware dont work) So in order to make 1.5 firmware to new PSP , we must decrypt the file first and then flash it to the machine. (But I think this is meaning less , since the PSP lost the decrypt power means it cant run any sign code, for example , games)
Have you tried run 2.X updater from a downgraded 2.x->1.0 PSP?
0okm0000 wrote:"
laichung wrote:...
But did you solve the problem about the new ver. hardware can't downgrade to lower version firmware?
no
"PSP Multi Firmware module" Not support PSP new ver. hardware(TA-082)
laichung wrote:Then It will be a bad new for those who having a new PSP.
I read some information from your blog about you re-flash 1007 PSP to 1.0 and try to update it to 1.5 but not sucess. I think one of the possible reason is , the 2.X machine change the decrypt(IPL) process in both software and hardware way. So if we update our PSP from 1.0 to 2.X , after PSP updated it use software way to emulate 2.X hardware IPL. But for 2.X PSP from factory , it use hardware way to do IPL.
If my guess is right , even if you downgrade the new PSP to 1.0 , it should not be able to run any sign code, and that's why you cant run the 1.5 updater. (The reason why you can run 1.0 VSH because most of the function in 1.0 flash is not encrypt) And I think if we re-flash the 1.5 firmware to new PSP , the VSH cant load. (This may be also the reason why the multi-firmware dont work) So in order to make 1.5 firmware to new PSP , we must decrypt the file first and then flash it to the machine. (But I think this is meaning less , since the PSP lost the decrypt power means it cant run any sign code, for example , games)
Have you tried run 2.X updater from a downgraded 2.x->1.0 PSP?
0okm0000 wrote:"
laichung wrote:...
But did you solve the problem about the new ver. hardware can't downgrade to lower version firmware?
no
"PSP Multi Firmware module" Not support PSP new ver. hardware(TA-082)
no
IPL come from FW
1007 can run 1.51/1.52/2.00 .... update EBOOT.PBP
just can't run 1.50 update EBOOT.PBP
Yes but IPL is just a piece of code and function which passing the data from ram to chip to decode , but we still don't know what exactly the chip is doing when IPL call.
But It is wired that it can run 1.51 updater but not 1.50 , since 1.51 should be only patched the Folder String problem which used in kxploit. They should have exactly the same IPL structure , right?
[quote="0okm0000]
no
IPL come from FW
1007 can run 1.51/1.52/2.00 .... update EBOOT.PBP
just can't run 1.50 update EBOOT.PBP[/quote]
laichung wrote:Yes but IPL is just a piece of code and function which passing the data from ram to chip to decode , but we still don't know what exactly the chip is doing when IPL call.
But It is wired that it can run 1.51 updater but not 1.50 , since 1.51 should be only patched the Folder String problem which used in kxploit. They should have exactly the same IPL structure , right?
i use Hardware Downgrader make it to FW1.00
and try use FW1.50 EBOOT.PBP to update it but not success
the error same as software Downgrader :P
1007 with FW1.00 or FW2.00+1.00index.dat can't run 1.50 update EBOOT.PBP !!
so the problem is NOT on the IPL !!
So, somethings happen between the hardware and software.
As you said before , after downgrade to 1.0 FW , the PSP can't run 1.5 updater ONLY. But since we know that before the machine downgrade , it can run 1.5 encrypt files. (That mean the updater should right normally too.)
So now the questions has changed to , Why only 1.5 updater cant run? Why Sony think 1.51 is more safe to run?
The 1.5 updater may have some bugs during update the firmware , that cause the PSP stop running the 1.5 updater. (or Sony discover some way to check the code , and know it is a 1.5 updater?)
So , is that possible we replace some modules/codes inside the updater and repack it?
ok so it cant update to 1.5 lets skip that for now
great work thus far with the multi firmware module
id build one quick ...just wondering how cabling would
go into a psp and if it were possible to disconnet
multi firmware module from psp ...thus making it a
simple connection....shouldnt be so hard ...probably just
a couple cables shrinked together hanging out ...but if
its not possible then that is ok as most my psps have no
outer shell anyhow :P
dot_blank wrote:ok so it cant update to 1.5 lets skip that for now
great work thus far with the multi firmware module
id build one quick ...just wondering how cabling would
go into a psp and if it were possible to disconnet
multi firmware module from psp ...thus making it a
simple connection....shouldnt be so hard ...probably just
a couple cables shrinked together hanging out ...but if
its not possible then that is ok as most my psps have no
outer shell anyhow :P
dot_blank wrote:ok so it cant update to 1.5 lets skip that for now
great work thus far with the multi firmware module
id build one quick ...just wondering how cabling would
go into a psp and if it were possible to disconnet
multi firmware module from psp ...thus making it a
simple connection....shouldnt be so hard ...probably just
a couple cables shrinked together hanging out ...but if
its not possible then that is ok as most my psps have no
outer shell anyhow :P
PSP need a "KEY" to check or decrypt the "update EBOOT.PBP"
may be 1007 haven't this "KEY" for 1.50 ?
I just have one question that I cant deduce anything from reading through these posts. I have a version 2.6 psp that I bought used from eb. Not sure of the hardware version or anything, just couldnt buy a new one,,, couldnt afford it.
So I have a 2.6.
What I want this to do if I buy it is -
Run firmware 1.0 or 1.5 on my 2.6.
Therefore running 1.5 or 1.0 homebrew apps on my 2.6 psp.
Ive heard people mentioning the other way around ie running higher firmwares on lower fw psps ( which doesnt even make sense to me )
Im not asking if it can downgrade or whatnot. Its supposedly dual firmware. So........ can I run 1.5 or 1.0 firmware on my 2.6 without the aid of any other psp.
No friends have lower firmwares. No money or way to get lower firmwares. Hence my burning question
I think it is not possible because 1.5 updater should be encrypt by 1.0 key(so that 1.0 psp can run the updater), since you can run 1.0 fw on it , I think the key is OK.
or Sony use hardware way to banned the Key for 1.5 updater? if yes , why they dont ban other fw version key too?(or as you said , delete those fw version keys)
How about the Updater mode? May be 1007 hardware must change to Update mode before updating fw, and 1.5 updater missed this step? So can we write a program , reboot 1007 1.0 fw into Updater mode , and load the 1.5 updater?
0okm0000 wrote:PSP need a "KEY" to check or decrypt the "update EBOOT.PBP"
may be 1007 haven't this "KEY" for 1.50 ?
May be you can ask moonlight about how to log the functions called by the Updater. In the following message, moonlight mention that 1.5 updater use it own lflash_fatfmt.prx module but not the one in 1.0 fw. (May be this is one of the reason why 1.5 updater fail.)
now that is sexy :) i look very much
forward to blessing one or maybe multiples
of my psps with those babies :) ...who needs
a modchip when youve got 0okm
the 1.50 updater fails to run on psp-1007 because the scechkuppkg module doesn't think the psp is a legit retail model (it performs a idstoragelookup() on the model key but it gets an unknown keys as an answer so it believes the hardware you are trying to run the updater on is not a retail hardware (such as a devkit or a testing tool) and gives you a 80000025 error
The only way to run that updater on a psp-1007 device is to modify the model key located in idstorage and to do that scenand access is needed.
As for the hardware it's the same as any other psp, the 1.00 and 1.50 firmwares can perfectly run on those devices.
The only change from other psps is in the idstorage area which is unique per psp and of course it's model key which is unique per models.
The only fail is that the 1.50 chkuppkg module is older than the ones in the 1.51+ updaters and that it doesn't recognise the psp-1007 model key as legit.
for PSP FW1.00/1.50 user
this "module" can work with your PSP
for PSP FW1.51/1.52/2.00/2.01/2.50/2.60/2.70/2.71 user
if your PSP's Hardware ver is TA-079/080/081
and you have FW1.00/1.50 image file
this "module" can work with your PSP
is there a guide how to find out which version psp i have without opening it?
regarding the price:
so to get my 2.6 psp to 1.0/1.5 i will have to buy the chip and the lpt-cable, right?
totaling to 65$, which can in fact compete easily with the other one.
hope you find a producer soon, the earlier we get some competition on that market the sooner the prices will go down *g*
I read the post and it's confuse for me.
You say it first, it works at 50% on a psp 2.5x and 2.6x
and you say after, it 's compatible with 2.5x ,2.6x, 2.7x
i think downgrading is not the interesting point here....
running a 1.0 on a originally 2.01+ psp so you have a possibility to upgrade to the newest features and games (the original flash) and another firmware for using homebrew freely (or maybe someday even a custom os / linux on the psp).
also, the second (1.X) flash needs to be reflashable when its bricked *g*
Just wondering if I understand this correctly before I post my real question.
Samsung is the maker of the the 32MB Nand flash. Now this flash module carries 32MB of flash memory and also 32MB of Main System RAM for the PSP at the same time?
If Samsung had a 64MB version (not sure if they do or don't) and this version had the same pinout would the PSP make use of the extra 32MB of RAM for a total of 64MBytes? I guess this question can only be answered if there was a 64 MBytes version of this chip.
Lastly, are there other manufactures that also create a PSP compatible Nand Flash?
0okm0000 wrote:2.50 new "protection" :
if you replace the flash0/vsh/etc/index.dat w/ old ver index.dat
you will can not lunch update EBOOT.PBP
2.60 new "protection" :
if you replace the flash0/vsh/etc/index.dat w/ old ver index.dat
when you power-on you will get a error screen
What happened if you overwrite flash0/vsh/etc/index.dat with NEWER index.dat?
For example:
a) HW with original 2.60 - just replaced index.dat (both encrypted & plaintext) with ones from 2.70 ?
b) HW with original 2.60 - whole firmware replaced with 2.50 AND index.dat replaced with 2.70 ?
So, what is the major difference of U.P. flash add on
and yours? It is basically the same difference, you add
the flash to allow the PSP to run a different firmware. Then
you could also implement a USB interface to flash the
second flash with anything you like, even Linux.
Right?
See www.kienhoefer.com/pspflash
Can you plz help me answer the following question:
My psp have CE trace cut but it still works how can this be?
I think that CE is logical inverted (0 = Chip Enable) and in this case if CE line is broken, the chip is always enable but i don't sure, wait for Ookm confirmation.
I checked and CE isn't grounded.. If I connect 3.3v before the trace cut closest to CE the psp don't boot as expected. I see why you think CE could be grounded that would make senses but the psp is 100% clean and checked. Only the trace is cut..there's not really a ground source in the neighbourhood. Its weird..
At first I made the cut connected the psp and original flash was off but then I wanted to access it but then I got a blue screen to repair setting. After this the psp was always on with original flash. psp is version 081 with 2.71 firm
Since you cut the trace, the CE line will be floating, the PSP is interpretting this as a low input. It does not have to be connected to ground to be interpretted as a low.
[quote="MrR"]
I checked and CE isn't grounded.. If I connect 3.3v before the trace cut closest to CE the psp don't boot as expected. I see why you think CE could be grounded that would make senses but the psp is 100% clean and checked. Only the trace is cut..there's not really a ground source in the neighbourhood. Its weird..
[/quote]
I got a question about the manufacturing of the module. Wouldn't it be easier to get a flex connecter with 8 contacts and solder the connector to the traces, cut the CE trace and solder only one wire to the floating connector pin. Then make a flex cable that run all the way up to this place instead of having to route copper cable which can easily desolder?
This would ensure a really reliable connection.
The only thing i don't know is if there are any .1mm pitch connector and flex cable.
