Skip to content

Downgrading 3004 from 6.61 PRO-C2∞ to 6.60, error LPTFFFFFFFE, still boots into 6.60, UMD not working #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
soadroxs opened this issue Mar 20, 2020 · 20 comments

Comments

@soadroxs
Copy link

Hello there,
As the title says, due to some incompatibilities I found with 6.61, I chose to downgrade to 6.60 with your tool, knowing the risk. The downgrade was going fine, but stopped at 89% and gave that error, and I thought the PSP was done for, but it did boot into 6.60 with no problems at all, after checking System Information. Problem is, now the UMD drive isn't working and after some searching I am afraid it could be a corrupted IDStorage, what is your insight on this issue?

Thanks for your help!

@soadroxs soadroxs changed the title Downgrading 3000 from 6.61 PRO-C2∞ to 6.60, error LPTFFFFFFFE, still boots into 6.60 Downgrading 3000 from 6.61 PRO-C2∞ to 6.60, error LPTFFFFFFFE, still boots into 6.60, UMD not working Mar 20, 2020
@soadroxs soadroxs changed the title Downgrading 3000 from 6.61 PRO-C2∞ to 6.60, error LPTFFFFFFFE, still boots into 6.60, UMD not working Downgrading 3004 from 6.61 PRO-C2∞ to 6.60, error LPTFFFFFFFE, still boots into 6.60, UMD not working Mar 20, 2020
@CelesteBlue-dev
Copy link

Please send pictures of PSPident, and idstorage leafs gotten using IdStorage Manager v1.3.

@soadroxs
Copy link
Author

IDStorage Manager shows "The motherboard cannot be determined (...) the IDStorage identifies the region set to a European PSP 1003/4".

Here are the files. I believe the idstorage leafs are these.
pspident_000
keys.zip

@soadroxs
Copy link
Author

Fun update. From 6.60, I downgraded to 6.20 with Chronoswitch, giving the same error. I did a factory reset (Triangle+Square+Select+Start) combination when force rebooting because the XMB didn't show up. The device was on 6.20, no problem, but the UMD wasn't working yet, so I used the official updater to get to 6.60. The update looped at 99% to 84% constantly, so I force rebooted once again back into the OS, and boom, the UMD is now working, and the device is at 6.60. Great adventure, but a lot of risk-taking I think. Do you want any dumps from my device to try and find out what happened?

@CelesteBlue-dev
Copy link

Nice. Please now send the same infos as before so I can look if something has changed.

@soadroxs
Copy link
Author

Here you go.

keys660umd.zip

pspident_001

@CelesteBlue-dev
Copy link

CelesteBlue-dev commented Mar 22, 2020

By comparing the two PSPident screenshots, we can see that when your PSP UMD drive was not working, UMD firmware version was not displayed.

When downgrading from FW 6.61 to 6.60, it stopped at 89% and gave error LPTFFFFFFFE.
Theory: it failed to install UMD firmware. That error could be located in the updater .prx to give more detail.
When you rebooted the PSP, it was on FW 6.60 but the UMD firmware was corrupted.
So you downgraded to FW 6.20, then installed FW 6.60. This time, even though it looped at 99%, it had already installed UMD firmware.

The question is why did it fail to properly downgrade from FW 6.61 to 6.60, and why specifically at UMD firmware step. It might be your PSP UMD drive that is faulty. It might also be IdStorage but IdStorage has no link with UMD firmware installation.

Comparing the IdStorage leaves, they haven't been modified downgrading / updating.
May you repeat the experience please:
update to FW 6.61, install infinity, downgrade to FW 6.60.

@soadroxs
Copy link
Author

Sure, I will. Could CFW have anything to do with this? Is there a signed version of PSPident and IdStorage Manager so I could avoid having to install CFW?

@CelesteBlue-dev
Copy link

"Could CFW have anything to do with this?"
Maybe.
"Is there a signed version of PSPident and IdStorage Manager so I could avoid having to install CFW?"
No because they need to call kernel functions using an unsigned kernel prx so a kernel exploit is needed. It might be doable to sign the kernel prx with a donor but I don't know. Look at Infinity source code and writeup if you really want to sign these homebrews.

@soadroxs
Copy link
Author

Okay, so I updated to 6.61 and it looped from 84% to 99%, and dead UMD on boot. Had to factory reset for it to get into XMB. Do you want any dumps from here?

@CelesteBlue-dev
Copy link

Now that you are on FW 6.61:
take a PSPident screenshot
reinstall FW 6.61.

@soadroxs
Copy link
Author

soadroxs commented Mar 22, 2020

Okay, I take back what I said. UMD is actually working, the UMD I used this time was just faulty, because UMD firmware shows up in PSPIdent just as it did on 6.60 after official updater.

@CelesteBlue-dev
Copy link

Nice. Now install Infinity. Then downgrade to FW 6.60 using Chronoswitch.

@soadroxs
Copy link
Author

Hey there. It's been a year, but coming back to this issue, I downgraded to FW 6.60 using Chronoswitch, after having Infinity. The downgrade was successful, and I got a UMD firmware in PSPident. But I can't read UMDs even after installing a UMD drive from a working PSP 3000.. Some games read at least the game info but crash after gameboot on a black screen. I'm really confused with this.

@rreha
Copy link

rreha commented Dec 17, 2022

I'n having this same problem aswell, I couldn't find anything on the internet about this, is there any fix?

@theAkito
Copy link

How is it possible to debug this issue, though?

@rreha
Copy link

rreha commented Dec 17, 2022

How is it possible to debug this issue, though?

Well I have no idea but I think it's about the corruption of the UMD part of the IDStorage, I'll check that out soon by using IDStorage Manager, since the backup of it is in there as it says in the psdevwiki page of IDStorage. It's definitely an UMD issue though since the error code has "LPT..." on it which means "Lepton" which is the codename of PSP's UMD chip. Updater log on flash1:/updater/u.log looks like this:
400AC736-57AE-410D-8A47-623BA881D95C

@rreha
Copy link

rreha commented Dec 18, 2022

Well I've compared all of IDStorage keys that have backups, all of them are identical with their backups at least for my case. Looks like it's more of a hardware issue. Probably Lepton chip is dead. Please let me know if someone wants me to try something. I'll probably swap the motherboard anyway. Also according to my research, this is kinda common for the 3000 model.

@theAkito
Copy link

Good to know.

Please let me know if someone wants me to try something. I'll probably swap the motherboard anyway. Also according to my research, this is kinda common for the 3000 model.

Is it possible for you to test or otherwise confirm that it's a hardware issue? Would probably relieve a lot of pain from others, who experienced this issue, so they can calmly stop searching for a solution to an issue, that can be only solved with a hardware fix.

Probably Lepton chip is dead.

Why do you think that?

@rreha
Copy link

rreha commented Dec 18, 2022

I really don't know what else I can do to confirm that it's not a software issue, don't know how to confirm that it's a hardware issue either.
Well I think it's an issue with the Lepton chip because it's used for decrypting UMDs, for my case whenever I insert my UMD, it says "The disc could not be read" immidiately, but when I put the PSP to the sleep mode and power it on again, this time the UMD laser starts to work and the UMD motor spins the disc, but it just stays on reading (the spinning clock at the bottom right corner) forever and the UMD motor stops spinning after a while.

@rreha
Copy link

rreha commented Jan 23, 2023

So, I don't have the PSP anymore, I still have the IDStorage keys backup so here they are:
LPTFFFFFFFE_keys.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants