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

[soadroxs]

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!

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

[soadroxs]

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.

keys.zip

[soadroxs]

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?

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

[soadroxs]

Here you go.

keys660umd.zip

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]

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?

"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]

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?

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

[soadroxs]

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.

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

[soadroxs]

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.