PS3 Archiving my library of PSN games

@Charles_n_town Thanks for info. So I will look for better solution for Windows. I really hate PowerShell syntax. ^^"

@Rissy Most important question: do You have backup of "exdata" BEFORE any modification You have made, no matter if it was homebrew or CellOS itself? If not and You are unable to decrypt licenses (for encrypt them on target console), Your only way is seek for RAPs for Your content - let's say, piracy in some meaning - or do everything again... However, Sony forcing half year cooldown before You will be able activate that console again. If that assumption is right, You have Your all content but not have licenses (so do not delete it, it is fine :P).

You didn't stick to Ultimate UserData Guide since the beginning plus paranoia (sorry to said that ^^) and that's the result.

Anyway, licenses are named by NP Comm ID so run cmd/terminal and go to exdata folder, and perform:

Linux or Linux in WSL:
Code:
ls -1 >> ${HOME}/Desktop/list.txt

Windows CMD or PowerShell:
Code:
DIR >> "%HOMEPATH%\Desktop\list.txt"

Maybe I have some licenses for Your stuff, so I can share it and at least You would be able test final step of recovery scenario for some eg. games.
 
Last edited:
I can understand @Rissy ' perspective if you don't know enough, but I can also understand concerns for an ECDSA flaw that could lead to more piracy. I don't believe in piracy whatsoever, but there's a lot of unscrupulous people in the Playstation scenes. I mean sony is at least allowing exploits to be released, and now you're going to rip them off for the favor?
 
Most important question: do You have backup of "exdata" BEFORE any modification You have made, no matter if it was homebrew or CellOS itself? If not and You are unable to decrypt licenses (for encrypt them on target console), Your only way is seek for RAPs for Your content - let's say, piracy in some meaning - or do everything again... However, Sony forcing half year cooldown before You will be able activate that console again. If that assumption is right, You have Your all content but not have licenses (so do not delete it, it is fine :P).
You didn't stick to Ultimate UserData Guide since the beginning plus paranoia (sorry to said that ^^) and that's the result.
Anyway, licenses are named by NP Comm ID so run cmd/terminal and go to exdata folder, and perform:
Linux or Linux in WSL:
Code:
ls -1 >> ${HOME}/Desktop/list.txt
Windows CMD or PowerShell:
Code:
DIR >> "%HOMEPATH%\Desktop\list.txt"
Maybe I have some licenses for Your stuff, so I can share it and at least You would be able test final step of recovery scenario for some eg. games.

I don't think i do. I have confusingly enough, a bunch of .rap files, which i think must have come out of Apollo by saying "export licences", but these are not obviously going to be valid, now that I understand that to do the conversion from .rif to .rap, you must have the original act.dat which the .rif were made with, which I don't have. Anyway, that's one exdata folder backup.
I also have a different exdata folder backup, and that one contains .rif files. I thought these would be the original .rif that came with the games, but now i'm not so sure. I can't remember what i've done and when.

In all fairness, I did read your ultimate guide (although i don't think i was made aware of it until after i'd made the console into CFW), but it didn't specify that you must leave your console activated when making the console CFW anyway. This sort of information might be obvious to the well initiated and experienced, but for someone new to everything (the type of person who might want to read such a "manual" in the first place), and not sure what's coming up further down the road of the journey, this to me wasn't clear. I just knew that there were options within Cobra (I didn't know about Apollo at that time) that said "activate console". So without any instruction on the limitations of what that meant, I thought it was good enough for what I wanted to do. Now I understand, it isn't. Clearly my AccountID is still locked into this console, but despite this; the act.dat which Cobra (and Apollo) create, isn't a true representation of what the original one was. The act.dat creation mechanism there, either doesn't look at the active accountID, or it's missing something else which the Sony mechanism has. I guess this is the bit that @zecoxao is trying to figure out....
 
I'm not sure what happen if Apollo or xai_plugin found already existed act.dat on target account during user demand to activate account, but probably it is not overwritten but ignored or make new one, while other is renamed.

BTW: Your journey brings for me that ideas to added to guide more info about bubbles as it seems confused You much, and add at all info about activation - which I didn't even think before, that someone would want deactivate it before hack the console.
 
I'm not sure what happen if Apollo or xai_plugin found already existed act.dat on target account during user demand to activate account, but probably it is not overwritten but ignored or make new one, while other is renamed.

BTW: Your journey brings for me that ideas to added to guide more info about bubbles as it seems confused You much, and add at all info about activation - which I didn't even think before, that someone would want deactivate it before hack the console.

With both Cobra AND Apollo, if you request activation with an existing act.dat file already there, it refuses to create a new one and simply advises you to delete the existing one first (But that's left up to the user to do or not do).
 
what i'm trying to find is the act.dat/rif private key. said key is universal and is not bound to any of the files you have. due to a fail in implementing ecdsa (made by sony) it's possible to retrieve this key if the file in question has two different pairs of signatures with same R but different S

Since it's easier to find rifs than it is to find act.dat, sharing the rifs is a better way to do this, and, in the end, we all benefit from it.

To see what i'm talking about see:

https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm#Security
 
I'm back! (I can hear you all sigh :joyous:)

I been absent for a bit as my frustrations lead me to needing a break from the PS3 stuff, but I got back on to it a few weeks ago.

I've been quietly doing my own thing, and now that I'm done, I thought I'd share with you where I've got to since I last posted.

The console I had originally converted from OFW into CFW, but deactivated my account on before the conversion has been fully refurbished. Stripped down, cleaned up, CMOS battery replaced, and a new HDD installed.

I put this console through a series of events in my own attempts to be happy to put it back online with my own cherished account login.

Originally at CFW 4.91.2, I downgraded the console to OFW 4.89.
Then I pulled the HDD and replaced it with a new one.
Again, with OFW 4.89, the console was completely built up again on this new HDD.
At this point, I removed the HDD and formatted it using my laptop and stripped down the console for cleaning out, pulling the CMOS battery and cleaning/reapplying thermal paste to the chipsets. The CMOS battery was pulled from the board for around 24hrs in total.
Then after rebuilding the console, I rebuilt it again using OFW 4.89 on the newly formatted new HDD.
Then I updated to OFW 4.90.
Then I updated to OFW 4.91.
At this point, I repeated the removal of the HDD, formatted it, disassembled the console and pulled the CMOS battery again for another 24hrs or so.
Then after rebuilding the console one last time, I then rebuild the console on OFW 4.91 on the newly formatted HDD once more.

At this point, I thought to myself that there is nothing else I can do to attempt to remove all evidence of CFW ever being on this console before putting it back online again, and signing into my cherished account. Checking the chipset information from ps3tools.com shows that the retained memory shows the latest two firmware versions to be 4.91 and then 4.91 again, which is representative of there being a HDD swap from the original HDD to the replacement, both sporting OFW 4.91 as far as Sony are concerned. So nothing untoward there.

I was happy to prove the console online now. I logged in using my temporary secondary account I created earlier this year, and all looked good with it. No issues observed. Then I logged in using my cherished account, and again, nothing untoward there.
At this point, I proceeded to install every game I own on to the machine, and downloaded all my PSN account content on to it so that this machine was fully representative of everything I own for PS3.

Due to the history of the machine already being CFW, and being armed with the idps and eid_rootkey files, I had no need to make this machine CFW again (If I didn't need to), so with everything on it, I then proceeded to remove the HDD and plugged it into my laptop. From here, I was able to copy my activated act.dat, all my rif files, game updates, patches, addons, psn games, save files, trophies, everything; over to my laptop.
I was then able to convert my rif files correctly into rap files.
I also dragged off a copy of my registry file.
Using everything from that console, I was then able to hack the registry file of my fulltime CFW console to make it as my cherished account and put all of my newly acquired content from the OFW console on to it, and activate everything and and have everything work as it does on my fulltime OFW console, which still remains unopened and untampered under my TV. All my games work, all my save games load up, and all my trophies continue to be recognised etc (or so it would seem). I preferred the approach of hacking the registry rather than resigning content as it means it doesn't matter which console I use to continue a save game or collect a trophy on, as this can then be transplanted to another console without much hassle. I also couldn't work out how to get Apollo to resign trophies. Save games work OK, but trophies doesn't seem to have a way of doing it similarly....?
There was quite a long time spent matching file structures between the content on my laptop, and making the CFW console file structure appropriately the same etc, but that's fine as it gave me time to read about and understand what some of the files are for etc, which has allowed me to further my learning.

So the end result is, that I now know and understand what needs to be done to do what I've done, and I've now proven to myself that I can do it, and I'm very happy with the result. I'm thinking about writing a guide instruction for others to follow, as I still feel that if such a thing had existed earlier in the year when I was trying to do everything for the first time, I wouldn't have fallen down the pitfalls I experienced and could have had this done a lot quicker than the time it eventually took me to do.

The next step I'm thinking about undertaking is converting folder games into package files to make it easier to install in the future, so back to do more reading I guess...
 
I put this console through a series of events in my own attempts to be happy to put it back online with my own cherished account login. (...) Then after rebuilding the console one last time, I then rebuild the console on OFW 4.91 on the newly formatted HDD once more.
Series of non-sense actions. ^^"
Checking the chipset information from ps3tools.com shows that the retained memory shows the latest two firmware versions to be 4.91 and then 4.91 again, which is representative of there being a HDD swap from the original HDD to the replacement
No, it shows what is read from ROS0 and ROS1 sections.
I was happy to prove the console online now. I logged in using my temporary secondary account I created earlier this year, and all looked good with it. No issues observed. Then I logged in using my cherished account, and again, nothing untoward there.
At this point, I proceeded to install every game I own on to the machine, and downloaded all my PSN account content on to it so that this machine was fully representative of everything I own for PS3.
Yeah, do NOT deactivate accounts again. :P
being armed with the idps and eid_rootkey files, I had no need to make this machine CFW again
Indeed. All You have to access data on HDD and resign it/decrypt it.
All my games work, all my save games load up, and all my trophies continue to be recognised etc (or so it would seem). I preferred the approach of hacking the registry rather than resigning content as it means it doesn't matter which console I use to continue a save game or collect a trophy on, as this can then be transplanted to another console without much hassle.
Indeed. Finally! :D
and I'm very happy with the result.
:]
I'm thinking about writing a guide instruction for others to follow, as I still feel that if such a thing had existed earlier in the year when I was trying to do everything for the first time, I wouldn't have fallen down the pitfalls I experienced and could have had this done a lot quicker than the time it eventually took me to do.
Plenty exists. ;p
The next step I'm thinking about undertaking is converting folder games into package files to make it easier to install in the future, so back to do more reading I guess...
Well, again, I already explained that in the past. :P
 

Similar threads

Back
Top