PS3 Error 8002F224

dankmolot

Member
Installing any cfw and ofw displays error 8002F224. As I understood this is due to the change of idps. At the moment I have a blank hard drive on which I cannot install anything. Can I somehow change the idps, or the problem is not even that.

PS3 Slim.
CECH-2003B

Thanks in advance for any help
 
Installing any cfw and ofw displays error 8002F224. As I understood this is due to the change of idps. At the moment I have a blank hard drive on which I cannot install anything. Can I somehow change the idps, or the problem is not even that.

PS3 Slim.
CECH-2003B

Thanks in advance for any help
Let's start at the beginning if that's OK, we need to get an idea of your setup.

What is the current CFW version?
If not a 4.86 fw, is the system software version spoofed with SEN Enabler ?

What is the current CFW type?
If Rebug REX, what mode are you using (cex or dex)?
If DEX mode, have you changed the ps3 active Id with Rebug Toolbox to be able to connect to PSN?

Has the idps been spoofed?
If yes, how? Using what tool? Idpset?
Where did you get the spoof idps from?
Do you still have the old original idps?

And finally, what are you trying to do?
Change internal HDD?
If so, do you have the previous hdd still untouched? Can you still boot into XMB if you reinsert it?
 
Last edited:
What is the current CFW version?
Previously was Rogero 3.55. Now nothing

What is the current CFW type?
CEX, and yes i changed ps3 ID to be able to connect to PSN. Changed the id for the tutorial: https://consolecrunch.org/threads/easier-way-to-permanently-change-idps-and-psid.4097/

Has the idps been spoofed?
Idpset.
https://consolecrunch.org/threads/console-id-2067.29610/
No.

And finally, what are you trying to do?
Fully formatted the disk. Changed internal drive. Used different cfw, ofw and downgraders.

If so, do you have the previous hdd still untouched? Can you still boot into XMB if you reinsert it?
This is a huge problem, I have no access to xmb.
 
Have you ever managed to install a firmware update after you spoofed the idps with idpset? Can you remember?

I cannot say for sure whether it is the case BUT if ever you used idpset to set an invalid idps for the current setup, it could be cause for such an update loop.
The console would keep working, at least until the day you must reinstall a firmware.
In this case, you would be snookered, no quick fix, the only way to change an idps is to use a hardware flasher to reprogram the eid0 and/or eid5 regions of the NOR chip.
 
Have you ever managed to install a firmware update after you spoofed the idps with idpset? Can you remember?
No, nothing installed.

In this case, you would be snookered, no quick fix, the only way to change an idps is to use a hardware flasher to reprogram the eid0 and/or eid5 regions of the NOR chip.
Then can you tell me which flasher to use and how to change the eid0 and eid5 regions with it?
 
No, nothing installed.


Then can you tell me which flasher to use and how to change the eid0 and eid5 regions with it?
Though I can't tell you how to change eid regions (I can say that it will probably be through modifying one of your functional flash backups), e3 flasher would work with your system as it is NOR and not NAND or EMMC. I have heard success with a few other flashers, but that was one I used specifically for repairs.

If you get one, the clip is finicky at best, and treat the cable like it's made out of toilet paper. On one system I had to hold the clips with my fingers while the thing flashed, because penny tricks and foam didn't work. Three backups and a flash took forever when you have to use exact constant pressure the entire time at risk of bricking a console.

You'll probably need a few tools to modify your backup. someone like @littlebalup might be better at the eid stuff, and modifying the flash. @baileyscream is another person with way more experience with flash. I'm NOT discounting anyone on this forum either, bg, as I know you're part of the team for the ps3 toolset for hen.

You're getting solid info here, just throwing in a few cents, and hopefully some helpful info. :)
 
No, nothing installed.


Then can you tell me which flasher to use and how to change the eid0 and eid5 regions with it?
Bad idps spoofing might be the reason for your troubles, it fits, it's likely, however I cannot guarantee without fail that it is the case.

To get an overview of the Flash memory data structure & the different regions, you can use the psdevwiki. https://www.psdevwiki.com/ps3/Flash

If you wish to amend the changes you made with idpset, you will need to get a hardware flasher.
Either a Teensy (prjc.com) with a compatible NOR clip or a E3 board with its dedicated NOR clip.
Overall the cheapest is probably to get a clone of the E3 limited edition ( board + clip) on aliexpress.
Both flashers work fine.

The Teensy way is a little more expensive because the clip is usually more expensive however the Teensy board can be used on both NOR & NAND consoles whereas E3 is only for NOR consoles.

Once you have acquired a hardware flasher & dumped the NOR contents, you will have to patch the dump with a valid idps (which you will have to get from somewhere, like a dead or dying console) then when ready, you will have to reprogram the chip with the patched dump.

Anyway, if you decide to go ahead with this plan, I suggest that you get the hardware first. When you are ready to roll, just let us know, there will be someone around to guide you from there.
 
@bguerville
I'm wondering if he's messed with the cex dex setting in idpset
If i remember correctly you can install rebug still when this happens to bring the console back to life.
this symptom does feel like thats the reason [emoji848]
And im sure idpset was fixed to only allow the cex dex setting if your in rebug. So unless he found the 1 release before the rebug check or he tried changing firmwares while in partial dex then I'm with you on the flasher option.
 
@bguerville
I'm wondering if he's messed with the cex dex setting in idpset
If i remember correctly you can install rebug still when this happens to bring the console back to life.
this symptom does feel like thats the reason [emoji848]
And im sure idpset was fixed to only allow the cex dex setting if your in rebug. So unless he found the 1 release before the rebug check or he tried changing firmwares while in partial dex then I'm with you on the flasher option.
I agree & I think it could well be the latter.
I have always been very wary of partial dex tbph, especially when other features/brew are used on top of it that may also apply changes affecting the idps.

And there is always the possibility that the idps is custom generated & invalid in such a way that at least one of the algos using it during the update process simply fails.
We know for instance that valid idps spoofing usually leads to wrong minver results which are used during the update process, with whatever consequences. An invalid idps (or a value derived from it) could pass certain checks & not others, succeed in calculating valid (ie within expected range) values with certain algos but not with others.. The idps is used for many things in different parts of the OS.

Idps spoofing has always been source of many issues, the idps is not just an id, it is tightly & specifically linked to the console it belongs to.
Personally, I don't use permanent spoofing at all, ever.. I much prefer to rely on the many tools that can apply idps spoofing at runtime, automatically & safely, leaving the system idps totally untouched.
 
Last edited:
Are you sure that you are currently on 3.55 Rogero? I assume you have tried to reinstall that CFW? And 3.55 OFW?

You should also try both Rebug REX 4.84 & Rebug D-REX 4.84 if you haven't already to make sure Rebug related settings issue are not at play.
Use the web archive service to access rebug.me.

I have this 3.55 habib 999 downgrader.
https://mega.nz/file/aJxGXA5D#gzndO2fZeoYeLQGRwX1n4vYrj85t2eftJ686BSKFi40

I also have some Miralatijera 999 downgraders with several patches, you can give them a shot too if you wish.
https://mega.nz/file/aJYwHZba#6VaAMs0aT-2bZaCi1ChHGO30Dv1nmbBTWjXaJpsLI7w

If none of the above works, then the previously raised idps issue will be likely.
 
Last edited:
Back
Top