PS3 SS ,Installed CCAPI WITH PS3HEN, BRICKED ?

Oh if safe mode is working, you could try reinstall HFW from there, or try restore to factory defaults and format. I only have super slims with HDD only so not exactly sure how those 12GB super slims behave. Maybe someone else can help more.
 
DeViL303 said:
Oh if safe mode is working, you could try reinstall HFW from there, or try restore to factory defaults and format. I only have super slims with HDD only so not exactly sure how those 12GB super slims behave. Maybe someone else can help more.
Click to expand...
It didn't work... I tried to restore to factory settings but it was saying, "The hard drive is inaccsessible" But when I tried to install the hfw... I lost the safe mode option...
 
Not much you can do then, those were the only 2 options that might have been able to help.
 
supergamer228yea said:
Does it mean that it is alive??
Click to expand...

no, your PS3 is pretty much bricked, even with a hardware flasher and tools to dump the internal ps3 flash memory chip, I'm not aware of any tool to fix or patch the dump and restore it to a useful state.

there's not so much research or information about those late super-slims without HDD... perhaps dumping a memory from a working 12gb super-slim, and using that dump to write over the broken one could be a solution, but only if there's no console-specific information on that flash chip.

If not, you'd have to mix the original broken dump with the donor working dump, and see what needs to go where, etc.
 
DeViL303 said:
No sorry. This is why there are warnings about CCAPI. :(
Click to expand...

as a side note, I wonder if a "TITLE_ID" check could be added to the PS3HEN payload, to check if the user is trying to install/run a CCAPI package, and abort it before the damage is done.
 
Yeah, The HEN sprx probably could have that pkg or EBOOT.BIN blocked somehow. Not sure if they are planning on updating it anymore.
 
bucanero said:
no, your PS3 is pretty much bricked, even with a hardware flasher and tools to dump the internal ps3 flash memory chip, I'm not aware of any tool to fix or patch the dump and restore it to a useful state.

there's not so much research or information about those late super-slims without HDD... perhaps dumping a memory from a working 12gb super-slim, and using that dump to write over the broken one could be a solution, but only if there's no console-specific information on that flash chip.

If not, you'd have to mix the original broken dump with the donor working dump, and see what needs to go where, etc.
Click to expand...
Neither if I buy e3 flasher? I just want to have image on screen and install the fw from sony, i don't care if it is saying, blah blah.. System software is corrupted... blah blah...
 
I don't know. like I said, I don't know for sure. I just recently bought a super slim 12GB model that I don't plan to hack. I think that's what you have, right? I know that when I installed the 1TB hdd, it said "hdd detected, would you like to change save locations?" then, it asks whether you'd like to copy everything from the internal flash 12GBs. it's very slow too. took at least 20 minutes, then it manages the data after it restarts, so you have to wait another 15 minutes or so. I don't know if everything, including firmware, is now on the hdd. I didn't have to reinstall the firmware or anything, and the 12GB space was empty anyway (no games or users).
 
bucanero said:
I guess that only @littlebalup might have the experience related to PS3 flash images to answer that question.
Click to expand...

supergamer228yea said:
OK, I hope he/she help me.... I can buy a flasher but I don't know what type. I think E3 and the chip..
Click to expand...

The 12gb CECH-4xxxA super slim models have an eMMC flash. It's not a NOR so E3 flasher can't help.
When no HDD has been added, everything is stored in the eMMC (bootldr, metldr, eid, core OS, eflash, hdd0, etc).

It's possible to read/write the eMMC pretty easily with a relatively simple hardware mod: https://www.psx-place.com/threads/r...eries-hardware-flash.23224/page-2#post-186775

So its possible to do simple things like restoring a correct coreOS.

However, if the corrupted data is not in the coreOS but in the eid (like the IDPS), the eflash or even the hdd0 partitions, the eid root key is necessary to be able to do someting.
 
Last edited:
@littlebalup Something that came to my mind. When you have a 12Gb "A" and you didn't use the option "change to HDD" and never export eMMC data to HDD, means the NOR is totally empty, or there's data that both shares at the same time when the console is brand new?

I'm mention this 'cause I think I faced a couple of 4xxxA with a damaged/deattached eMMC (console won't boot, turns off about 20/30 seconds after and it only boots on recovery mode, leading you to choose "change to HDD" option which works). And by that I believe critical information were wrote on both memories, Am I right?

In this case when you write on eMMC, you already wrote on the NOR too with the same firmware information?
 
ElGris said:
@littlebalup Something that came to my mind. When you have a 12Gb "A" and you didn't use the option "change to HDD" and never export eMMC data to HDD, means the NOR is totally empty, or there's data that both shares at the same time when the console is brand new?

I'm mention this 'cause I think I faced a couple of 4xxxA with a damaged/deattached eMMC (console won't boot, turns off about 20/30 seconds after and it only boots on recovery mode, leading you to choose "change to HDD" option which works). And by that I believe critical information were wrote on both memories, Am I right?

In this case when you write on eMMC, you already wrote on the NOR too with the same firmware information?
Click to expand...

There is no NOR at all on those models. Only eMMC. Basicaly everything is on the eMMC: the flash data (per console data, core OS,...), the eflash (/dev_flash, xregistry...), the HDD data (/dev_hdd0, ...).

When a physical HDD is installed, the flash data (for sure) and eflash (to be confirmed) remain on the eMMC. Only HDD partitions are copied to the physical HDD. At the end, the structure is very similar to the NAND consoles with 256MB flash+eflash on the eMMC and everything else on the HDD.
 
littlebalup said:
There is no NOR at all on those models. Only eMMC. Basicaly everything is on the eMMC: the flash data (per console data, core OS,...), the eflash (/dev_flash, xregistry...), the HDD data (/dev_hdd0, ...).

When a physical HDD is installed, the flash data (for sure) and eflash (to be confirmed) remain on the eMMC. Only HDD partitions are copied to the physical HDD. At the end, the structure is very similar to the NAND consoles with 256MB flash+eflash on the eMMC and everything else on the HDD.
Click to expand...
Wow, didn't notice that for some reason, my bad. But this issue I mentioned then.. you can't access the eMMC as internal storage, and by what you're saying, that flash is totally fine then. I also found MN6840 instead of the NOR, and I areadly found what it is from a reply you did to sandungas:

"Yes, the "Starship 2" controler is a kind of NOR emulator from dual NAND. It seems to manage the bus conversion, NANDs ECC, scrambeling...

And yes, the MN66840 seems to do something similar with the KLMAG2GE4A-A001 eMMC. (Southbridge is the same for NOR and EMMC).

However, I don't think we can access the eMMC via the MN66840 like a regular NOR (like we can't access the NANDs via the Starship 2)."

Anywways, thanks for the clarification.
 
You must log in or register to reply here.

Similar threads

Back
Top