PS3 Please HELP - Firmware flash on a DECH S4000AB Debug Console

mtd

mtd

Forum Noob
Hi guys
I have a DECH 4000AB Ps3 Super Slim that is driving me nuts, sorry for my rough english
It's a debug unit that i have found a while ago, when i turn it on i need to plug the controller and being asked to update/reflash for a firmware 4.25 or above.

Theres was no HDD so i have installed one, gone through safe mode and formatted it.
While i was there i restored the unit and the file system structure options (i think i have tryed them all at some point).

I then tryed 4 different usb sticks, older and newer, formatted in FAT32 with the DEX firmaware 4.25, and then i tryed other 5-6 firmware above this one in random way untill the last one, 4.81 i think.

On the left port of the PS3, the usbpen does not work, it keeps posting about an update not being found.
On the second port the usb are reconized but no matter what i try i keep getting "the data is corrupted 8002f2e4" or "the data is corrupted 8002f2e5".

I also tryed out of desperation some customs firmware (also made for DEX models), some SEX and AEX firmware, even for the TOOL system but nothing works.
Original firmwares looks like are not reconized at all.
Do you have any suggestions other that throw it out of the window? Thanks
 
Try this: once you press X to confirm the update process, unplug your controller immediately.

I've come across issues on my Slim while trying to update my FW via Recovery Menu while having my controller connected (as stated in the screen instructions). Once unpluged, the update process was a success.
 
  • Like
Reactions: mtd
Thanks for the tip, unfortunatly it is not working.
I forgot to mention that the error on boot is "The system software cannot start, insert usb with 4.25 or above and press START + SELECT".
I just tryed right now also a CFW called REBUG D-REX 4.84.2 as i have read that i could have an empy NOR or HDD, but still i got "The Data is corrupted 8002F2C5"
 
Then your USB drive is not properly formatted in FAT32, or is not compatible (some USB thumbs don't work).

If you have a spare CD-R and a burner, you can burn the PUP and update the console with the CD in the BD drive. The path must be as always: PS3/UPDATE/PS3UPDAT.PUP
 
mtd said:
Thanks for the tip, unfortunatly it is not working.
I forgot to mention that the error on boot is "The system software cannot start, insert usb with 4.25 or above and press START + SELECT".
I just tryed right now also a CFW called REBUG D-REX 4.84.2 as i have read that i could have an empy NOR or HDD, but still i got "The Data is corrupted 8002F2C5"
Click to expand...
DECH4k is pretty much useless unless you have a working HEN. You can't install any CFW
 
Joonie said:
DECH4k is pretty much useless unless you have a working HEN. You can't install any CFW
Click to expand...
Thanks, i honestly just wanted to make the console work again, that is why i'm trying anything to past this hell of a screen. The fact is that i have literally tryed 5 different usb pens (kingstone, sandisk, lexar, generic chinese) and i always get the data corrupt error, could it really be that i'm so unlucky to just have all uncompatible usbpens?

I'll try the CD option, i didn't even know that was possible

EDIT: WOW, i cannot believe it... "The Data is corrupted. 8002F2E4".. on a CD! i have tryed a random 4.40Dex firmware from archive.midnightchannel.net and still, it did not work!

Is it briked somehow? it's so weird...
 
Last edited:
mtd said:
Thanks, i honestly just wanted to make the console work again, that is why i'm trying anything to past this hell of a screen. The fact is that i have literally tryed 5 different usb pens (kingstone, sandisk, lexar, generic chinese) and i always get the data corrupt error, could it really be that i'm so unlucky to just have all uncompatible usbpens?

I'll try the CD option, i didn't even know that was possible

EDIT: WOW, i cannot believe it... "The Data is corrupted. 8002F2E4".. on a CD! i have tryed a random 4.40Dex firmware from archive.midnightchannel.net and still, it did not work!

Is it briked somehow? it's so weird...
Click to expand...

You should stick to DEX firmware only.

try DEX OFW 4.80 or 4.81 on the second port.

also post a picture of the sticker label. Your model maybe slightly different than regular testkit.
 
GuilloteTesla said:
Could it be that the eMMc flash is corrupted/broken?.

I'm not used to SuperSlims, just throwing an idea.
Click to expand...

i think his pup might have been corrupted while downloading. I've seen that happened before

perhaps He has to check md5 hash ln that pup in his drive
 
Joonie said:
i think his pup might have been corrupted while downloading. I've seen that happened before

perhaps He has to check md5 hash ln that pup in his drive
Click to expand...

That's the only thing left to check. If the hashes match, then the unit must have some serious corruption somewhere.
 
Hey guys, thank you for helping me. Can you teach me how can i check the md5 hash? It's something i have heard before but never gone into.
I'll try to stick with the latest 4.80/4.81 dex but i'm pretty sure i have tryed that already the first time (i always aim for the latest with my ps consoles). I'll post the sticker tomorrow if needed, now it's late here. Thanks again
 
Sure mate!.

First of all, you need a Hash Checker app, which calculates the hash of a file and compares it with the target to verify if it matches or not. Here are a couple for Windows and Linux:
- Hash Viewer
- Hasher
- GtkHash

And a thorough tutorial on how to use some of them, you can even calculate the hash using commands too.

Where to get the PUP hashes?. Most of the sites that archive and distribute console FWs provide the hash in order to prevent a bad download, a corrupt binary or even a tampered FW with malicious code that can even brick your console.

- Darthsternie DEX FW archive
upload_2023-3-19_8-10-49.png


- Midnight Channel DEX FW archive
upload_2023-3-19_8-11-7.png



Remember to check the hash of your DEX PUP two times: once after you've downloaded it to check if it is valid, and again after you've put it into your USB stick to check if it copied correctly and your drive has no issues.

Good luck!.
 
  • Like
Reactions: mtd
Thanks buddy. So, i just did that with FW 4.81 and i have tryed with both website (and same exact result), using Hasher. I don't have the MD5 to match. What should i do then?
 
All right (sorry for the big pictures)
I downloaded 4.25 and compared with Hasher the md5 hash both when downloaded and put on the pendrive and they were finally the same as posted.
I put my ps3 on safe mode, drive on the second port, pressed start+select and boom, same error.
I'll also post the sticker on the back.
It must be seriously bricked at this point?



 
mtd said:
All right (sorry for the big pictures)
I downloaded 4.25 and compared with Hasher the md5 hash both when downloaded and put on the pendrive and they were finally the same as posted.
I put my ps3 on safe mode, drive on the second port, pressed start+select and boom, same error.
I'll also post the sticker on the back.
It must be seriously bricked at this point?



Click to expand...
DECH-S4000AB is not a debug PS3... but a "AV Tool" PS3 (intended for Blu-Ray video production)
Unfortunatelly the highest leaked AV firmware was 1.30 (and your console is requesting 4.25 or later)
https://www.psdevwiki.com/ps3/Template:System_Firmware
 
mtd said:
Oh wow, i was so convinced that this was a debug, as the sticker clearly says. What a bummer :( There is basically nothing i can do i suppose? Thanks for the reply
Click to expand...
The "S" in the model is what indicates is a "AV tool", the console doesnt have any problem, right now is not acepting any firmware but if you had a "4.25 AV firmware" (or later) it would acept it at first try
The hardware is the same than a standard debug, the differences are just software configs related with the HDMI controller

maybe you could try to sell it to someone with collector fetishism, or exchange it by a standard debug, a superslim "AV tool" is a bit special :D

The 2 solutions suggested by @M4j0r are pretty much:
1) convert the console to a standard debug (by modifying syscon config)
2) convert a standard debug PUP to "AV tool" PUP (latest was 4.81 as far i know)

I never heard about someone else doing this, so im not so sure about the details
 
You must log in or register to reply here.

Similar threads

Back
Top