PS3 Please need help with a PS3 maybe bricked or i don't know

ciukkino89

Forum Noob
Hello,

i have a slim PS3 model CECH-200xA.
Some years ago, maybe 10, I installed a CFW, I think the Rebug, i'm not able to remember if CEX or DEX.
After using for some months I left the PS3 for many years without using.
One day I tried to re-use but I had some troubles with something like Eid Root Key and some conversion with CEX/DEX or DEX/CEX untill I was not able to start any homebrew.
I left it again there without use it.
Today i'm trying to use my PS3 for any use and so i take off the Hard Disk, and i formatted it with my PC.
After it I tried to install trough USB key any FW (official, hybrid or custom) but the PS3 says that there is nothing inside the USB K.
I tried to format the USB Key in FAT32, I use the right parent directory with PS3UPDAT.PUP but always the same message: Nothing pertinent inside the key.
If i go to recovery I can see all the 6 options, but if I tried to select them everyone seems to crash and reboot the Playstation3 without restore the system, or the database or the factory setting.
I don't know if i bricked or compromise any pieces like the flash (?) or something else.
When i turn on the PS3, it doesn't show me any SONY image or something PS3 but the following message:
The system can not be run correctly. Press the PS button to try restart. ...... Connect storage media that contains update data of version 2.70 or later, then press START and SELECT... etc etc...

I would like to restore it in anyway, like OFW or CFW or if possible with an alternative OS. I would like if is not possible to restore it for play to PS3 game to transform it in a retrogame console with some emulators.
I would like to understand if i totally bricked or not.
Sorry for any my mistake word or consideration and for my english.
Thanks to who will care about my business.
 
Well chances are you are converted to DEX as it will always state 2.70 or later message. Also the drive will not detect the CFW on the system. So let's do a few things to check.

First grab this firmware file. It is Rebug D-REX

https://mega.nz/#!JIZUxQyT!X5GPuUqNfAB4qFS1ftgAmLN5JPMnqPRJL6P4pI5QnTY

Grab a flash drive and if over 16gb ensure you format to MBR and choose 64kb cluster size. Then ensure it is setup like this and case sensitive

PS3/UPDATE/PS3UPDAT.PUP

After this please report back and we can try some more stuff if this doesn't fix it.
 
Hello,

i have a slim PS3 model CECH-200xA.
Some years ago, maybe 10, I installed a CFW, I think the Rebug, i'm not able to remember if CEX or DEX.
After using for some months I left the PS3 for many years without using.
One day I tried to re-use but I had some troubles with something like Eid Root Key and some conversion with CEX/DEX or DEX/CEX untill I was not able to start any homebrew.
I left it again there without use it.
Today i'm trying to use my PS3 for any use and so i take off the Hard Disk, and i formatted it with my PC.
After it I tried to install trough USB key any FW (official, hybrid or custom) but the PS3 says that there is nothing inside the USB K.
I tried to format the USB Key in FAT32, I use the right parent directory with PS3UPDAT.PUP but always the same message: Nothing pertinent inside the key.
If i go to recovery I can see all the 6 options, but if I tried to select them everyone seems to crash and reboot the Playstation3 without restore the system, or the database or the factory setting.
I don't know if i bricked or compromise any pieces like the flash (?) or something else.
When i turn on the PS3, it doesn't show me any SONY image or something PS3 but the following message:
The system can not be run correctly. Press the PS button to try restart. ...... Connect storage media that contains update data of version 2.70 or later, then press START and SELECT... etc etc...

I would like to restore it in anyway, like OFW or CFW or if possible with an alternative OS. I would like if is not possible to restore it for play to PS3 game to transform it in a retrogame console with some emulators.
I would like to understand if i totally bricked or not.
Sorry for any my mistake word or consideration and for my english.
Thanks to who will care about my business.
atreyu187 already gave you all the info you need, I would only add that you should not worry, if the console still boots to recovery mode, it is very unlikely it is bricked, or at least not fully anyway, you should be able to revive it.
It is "quite normal" that other recovery options crash because you reformatted the internal hdd & there are no partitions for those features to process.
Tbph s#ny could have done a better job of this recovery environment, why crash & reboot when there is no partition to process? Why not tell the user there is no partition on the hdd & invite to install OS?
Imho we would really need a custom recovery homebrew with better options & features implementations than the official one, unfortunately given the overall interest in recent years I have a feeling somehow that we will not see such a project any time soon.

As to the update system not finding the pup update file on your USB device, there are 2 main causes, responsible 99% of the time, for that kind of situation:

1. The console is in DEX mode & you are trying to feed it a CEX PUP update. In this case, there are 2 options:
A] if the console still boots to XMB (which is not your case), launch the Rebug Toolbox, use the feature to dump the eid_root_key to the internal hdd, then convert the console to CEX. From there you can install any CEX CFW.
B] if the console no longer boots into XMB (which is your case as you reformatted the hdd), you should install Rebug D-REX (not REX) 4.84.2 from recovery. Then you can boot into XMB & convert to CEX if you wish to install a 4.88 CFW.

2. The USB device you are using is not compatible (it can happen with some external hdd brands, exotic USB setups using a USB hub internally or hidden system partitions on the disk) or it is not partitioned/formatted in a way supported by the PS3 OS.
It's better to use a simple, small size USB stick with as little data (if any) on it.
Make sure the partitioning type is MBR (the ps3 only supports legacy MBR, not modern GPT), the partition is fat32 & the pup path is upper cased as follows:
/PS3/UPDATE/PS3UPDAT.PUP
 
Last edited:
I still have to try i want to say thanks meanwhile. When i will be quiete at home i will try.
I want add to my first post that i formatted the PS HDD in FAT32 mode, I read that somebody usually formatted in NTFS, should be better?
And my usb keys available for this try are:
- 16 Gb usb key
- 8 Gb usb key
I should use smaller usb Key?
Yes, i'm not able to acces in XMB.

I will let you know as soon as possible my report. Thanks for the advice.
 
atreyu187 already gave you all the info you need, I would only add that you should not worry, if the console still boots to recovery mode, it is very unlikely it is bricked, or at least not fully anyway, you should be able to revive it.
It is "quite normal" that other recovery options crash because you reformatted the internal hdd & there are no partitions for those features to process.
Tbph s#ny could have done a better job of this recovery environment, why crash & reboot when there is no partition to process? Why not tell the user there is no partition on the hdd & invite to install OS?
Imho we would really need a custom recovery homebrew with better options & features implementations than the official one, unfortunately given the overall interest in recent years I have a feeling somehow that we will not see such a project any time soon.

As to the update system not finding the pup update file on your USB device, there are 2 main causes, responsible 99% of the time, for that kind of situation:

1. The console is in DEX mode & you are trying to feed it a CEX PUP update. In this case, there are 2 options:
A] if the console still boots to XMB (which is not your case), launch the Rebug Toolbox, use the feature to dump the eid_root_key to the internal hdd, then convert the console to CEX. From there you can install any CEX CFW.
B] if the console no longer boots into XMB (which is your case as you reformatted the hdd), you should install Rebug D-REX (not REX) 4.84.2 from recovery. Then you can boot into XMB & convert to CEX if you wish to install a 4.88 CFW.

2. The USB device you are using is not compatible (it can happen with some external hdd brands, exotic USB setups using a USB hub internally or hidden system partitions on the disk) or it is not partitioned/formatted in a way supported by the PS3 OS.
It's better to use a simple, small size USB stick with as little data (if any) on it.
Make sure the partitioning type is MBR (the ps3 only supports legacy MBR, not modern GPT), the partition is fat32 & the pup path is upper cased as follows:
/PS3/UPDATE/PS3UPDAT.PUP

With your permission Mr. @bguerville, I would like to add a third cause to the USB thumb drive not being detected (mainly in the Slim lineup).

3. Disconnect any USB devices (controllers included) and plug only the USB stick. Some PS3 models have a low power consumption and the USB ports can't deliver enough power to a controller and a stick at the same time (really weird and bad design from Sony's engineers). I know that in Recovery Mode you must have a controller plugged in, but just connect it when the instructions tell you to and disconnect it right after pressing the corresponding buttons in order to give enough power to the USB drive.
 
I read that somebody usually formatted in NTFS, should be better?
it was probably me that read that from. i got it from esc0rtd3w but i now think he was talking about one certain situation that it might help.

generally, how you format the drive does not matter because ps3 will format again anyway.
 
Thank you guys!
With all your advises this operation was very easy.
My PS3 is working, starts with the rebug logo and the system version now is at 4.84.
I don't remember nothing about how to use this CFW and so i have to study and maybe inform myself better because the last time that I were trying to change with a better and more updated FW I created this problem.
I remember that I had some troubles with the conversion DEX/CEX and something about eid.root.key.
What do you suggest me to do now?
What is the best CFW?
Or what is also the best CFW for dumbers?

This is my PS3 FW version at the moment, is normal that look like an OFW?
IMG-20220119-170613-842.jpg

zJwmyJ0
 
Last edited:
@ciukkino89 I say stick with Rebug 4.84 REX if you aren't bothered about PSN access. While it has advanced features, you can still use it like a simpler CFW such as Ferrox Cobra (just make sure you have Cobra enabled - which should be default - in Rebug Toolbox).

EID root key (ERK) is used for converting CEX<--->DEX as well as being able to read the otherwise encrypted contents of the PS3's HDD on a PC, using something like PS3 Tools Collection. It may have other purposes, but I can't remember right now. :)

To see if you're in DEX mode (which you seem to be as you were previously asked to install 2.70 or higher firmware) you can either check in Rebug Toolbox or simply, on the XMB in the corner of the screen will be a local IP address of your PS3.

My advice on DEX v CEX is simply, unless you have a reason to be on DEX, use CEX as it will perform every function other common CEX firmwares will, which is probably enough for the large majority of users' needs. For less experienced users who don't need the additional functionality of DEX firmware (such as homebrew development, real-time modding) then CEX is all you will ever need.
This is my PS3 FW version at the moment, is normal that look like an OFW?
Yes. System Information will only ever display the firmware version number, which I believe is contained as a string value within the firmware). In other words, it will never display "Rebug", "Ferrox", "EvilNat" etc.

I hope this answers a few of your questions :)
 
Thank you guys!
With all your advises this operation was very easy.
My PS3 is working, starts with the rebug logo and the system version now is at 4.84.
I don't remember nothing about how to use this CFW and so i have to study and maybe inform myself better because the last time that I were trying to change with a better and more updated FW I created this problem.
I remember that I had some troubles with the conversion DEX/CEX and something about eid.root.key.
What do you suggest me to do now?
What is the best CFW?
Or what is also the best CFW for dumbers?

This is my PS3 FW version at the moment, is normal that look like an OFW?
IMG-20220119-170613-842.jpg

zJwmyJ0
If you used the D-REX pup file to reinstall the firmware, the console is currently in DEX mode.
Originally DEX is the firmware installed on a debugging station, Rebug just adapted that firmware to work on retail consoles, this way developers could use debugging features on retail consoles & game modders could use specific DEX features to make their mods work.

Unless you are a developer or a game modder I suggest you convert to CEX retail mode.

4.84 is the last firmware version for DEX CFWs, if you wish to update to 4.88, you will have to use CEX mode.

Converting to CEX mode (and vice versa) is easy, launch the Rebug Toolbox, if it is not installed yet, you can install it from the package manager, the pkg is just there waiting.
In the Rebug Toolbox, go to the last column & choose to dump eid_root_key to your internal hdd (default directory iirc).
Next, you can use the "rewrite target ID" option in the Toolbox cex/dex column, the Toolbox should find the eid_root_key automatically, the console will reboot in CEX mode.
That's all.

I also recommend you keep a backup of the eid_root_key safe (along with a dump of your Flash memory) on a PC/USB stick, those things can get you out of sticky situations.

Once you are in CEX mode you can install any CFW you want, and if you keep QA enabled (you can toggle it on/off with the Rebug Toolbox), you can also downgrade at will.

When in doubt over the current mode, cex or dex, you can use the Rebug Toolbox system info feature, if the lv2 kernel is set to DEX, the console is in DEX mode, otherwise it is in CEX mode.
 
Last edited:
I will try as soon as possible how suggested from you guys, meanwhile I please ask to you:
- what are the pro to update at 4.88?
- and in case i would like to use the PSN for example to download app like netflik or what else what could happen?
- some years ago i had some troubles with the eid root Key, and i think to don't have any backup of It, in this case can i convert It in CEX anyway?
 
I will try as soon as possible how suggested from you guys, meanwhile I please ask to you:
- what are the pro to update at 4.88?
- and in case i would like to use the PSN for example to download app like netflik or what else what could happen?
- some years ago i had some troubles with the eid root Key, and i think to don't have any backup of It, in this case can i convert It in CEX anyway?

Really only thing is PSN access if you update to 4.88 as Sony changed how authentication for PlayStation Network changed. So the dev that made the spoofer said he will not be making one until he can find the changes needed.

As for the apps you can get No PSN patched apps so no need to connect to PSN. BTW Netflix has removed any PSN checks but the rest you can find here.

http://nopsn.com/pkg/ps3/

Now there is no 100% safe way to use PSN. I suggest using a throwaway account because if it gets banned it deactivates all games connected to the PSN ID. I myself lost around $1000+ of PS3, PSP & PSV games. Luckily I could activate them again due to CFW/EnsĹŤ.

That being said 4.88.2 EvilNat has some checks in place to make it as safe as possible. This way you can mount said game then disable syscalls to seem more OFW-ish with the serves.

And you can still get the eID key even on DEX using Rebug Toolbox to convert back to CEX at that time.

If you need anything else feel free to reach out.
 
Last edited:
what are the pro to update at 4.88?
'safer' PSN access other than spoofing firmware. However, even using PSNpatch, webMAN MOD or another method to disable CFW syscalls and remove homebrew history, there is still no guarantee you won't get banned.

I'm on 4.87 CFW and can still access YouTube by using the NoPSN version. Netflix no longer requires PSN login to use; you can download the pkg here (just select the appropriate region) and install it via Package Manager. If an update is needed, you can safely update it on the PS3 (since there is no PSN login, there is no ban risk).

You can re-dump your EID root key using Rebug Toolbox. From there, you can copy the file from your PS3 to your PC using FTP, so you have a copy stored elsewhere should you need it in future.
 
Sorry, i am little bit confused: I didn't understand which CFW is the best?
I read that rebug there is no 4.88.
But is available the 4.88.2 Evilnat, right? Is this the best CFW? Or still Rebug?
I saw some tutorial on this forum but the best one that I found was for HEN users, what Is the best updated tutorial that i can follow for a starter like me that can answer to all my FAQ?
 
If you want to play online EvilNat 4.88.2 is your only choice. If you do not care about online play stick with Rebug. If you are in fact in DEX mode you must convert back to CEX before installing 4.88 as the latest "DEX" is 4.84
 
Guys, something no good happen:
I tried to change from DEX to CEX, before i tried dump the root key.
Then i press change to DEX to CEX, the PS3 reboot but it show me a black screen, to turn off i have to take off the power cable and after I can go to recovery only... to the update always ask me the message:
Connect storage media that contains update data of version 2.70 or later, then press START and SELECT
 
Guys, something no good happen:
I tried to change from DEX to CEX, before i tried dump the root key.
Then i press change to DEX to CEX, the PS3 reboot but it show me a black screen, to turn off i have to take off the power cable and after I can go to recovery only... to the update always ask me the message:
Connect storage media that contains update data of version 2.70 or later, then press START and SELECT
1. We gave you precise steps, if you don't follow them, you should expect a strong potential for overall failure.
2. If I am not mistaken, you cannot convert cex/dex without an existing eid_root_key located in the following path
/dev_hdd0/game/RBGTLBOX2/USRDIR/eid_root_key. Iirc it is a prerequisite to the conversion & the Rebug Toolbox would not let you start that process without it.
So if you didn't dump the eid_root_key, the console should still be in DEX mode.

Anyway if you are now stuck in recovery mode, you probably will have to reinstall Rebug D-REX 4.84.2 & try the conversion again.
 
You are right I forgot to dump it before :tranquillity: shame on me
All right, was a success.
Thanks to everybody.
This forum is amazing, around youtube there many tutorial but more of these are fake or just clickbait.
Have you got a nice tutorial to follow for a starter about the homebrews and the way to use all the functions of the CFW.
Now my PS3 are on 4.88.2 Evilnat
 
You are right I forgot to dump it before :tranquillity: shame on me
All right, was a success.
Thanks to everybody.
This forum is amazing, around youtube there many tutorial but more of these are fake or just clickbait.
Have you got a nice tutorial to follow for a starter about the homebrews and the way to use all the functions of the CFW.
Now my PS3 are on 4.88.2 Evilnat


No real need for a guide. Just put the PKG on the root of a USB drive for an app you would like to use and install via Package Manager. Most of the stuff you just run and play no real setup required. But there are guides here for just about anything you want. Pinky and myself wrote a ton of guides here. Just use the search function and 99% of the time there is a post about it. It is the tiny magnifying glass in the upper right hand site banner. It can be a bit hidden if you aren't aware. But that will yield results faster then posting and waiting.,
 
Guys, always me, I downloaded some homebrew like PSP_Minis_Launcher.pkg.885.v1.00_brewology_com and PSP_Minis_Launcher.pkg.885.v1.00_brewology_com.
I was thinking that were for starts PS2 isos and PSP, but didn't work so I decided to cancel them.
The problem is that now these two remain in my XMB like "corrupted data" and i can not delete.
What i should do?
Gave me error 80010026
 
Last edited:

Similar threads

Back
Top