PS3 SS ,Installed CCAPI WITH PS3HEN, BRICKED ?

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.

I never experienced that issue myself but I imagine if too much sectors are damaged on the hdd partitions on the eMMC, the only way is to install a phisical HDD.
Just assumption but the hdd partitions are the most stressed for write operations (specially with 12gb space only, you must install/uninstall games often) . Compared to flash or eflash where the data are almost read only exept for firmware update or settings record (xregistry).
 
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.
I think my ps3 eMMC is dead... Neither controllers are not connecting... Can I do something?? like re-install the fw. I am dumb :(. If it works, I wont re-exploit the ps3 again.... Model PS3 SuperSlim 12gb cech-42xxxxA
 
I never experienced that issue myself but I imagine if too much sectors are damaged on the hdd partitions on the eMMC, the only way is to install a phisical HDD.
Just assumption but the hdd partitions are the most stressed for write operations (specially with 12gb space only, you must install/uninstall games often) . Compared to flash or eflash where the data are almost read only exept for firmware update or settings record (xregistry).
When I plug an hdd, it doesnt do anything..
 
When I plug an hdd, it doesnt do anything..

I don't know how helpful this will be, but I own a super slim 12GB. I installed an hdd before turning it on. when I did, it asked to change save location, then if I wanted to copy from internal memory. the latter thing might be why it's not doing anything. it has to copy from internal memory first. I'm not sure if it's required, because it asks the question, but the firmware doesn't have to be installed again.
 
I bought a PlayStation 3 Superslim (cech-4204a) which is ccapi bricked for 10 bucks. At first, i bought it for parts (for repairing my 500gb ps3, just in case anything happens), but then i wanted to make it function. When i power it on, the hdd indicator doesn't flash, no image displayed (no pad syncing) and safe mode is not working too. I found out that the console didn't have an hdd, but it had the 16gb (12gb usable) emmc flash. I am thinking of getting the 500gb drive from my main console and put it onto the 12gb one. Should it launch? I am wondering about the firmware differences as well, as i don't know what firmware it has. I want to test it, but right now, it is not on my home. What's your opinion? Is it saveable or should i try and use the hardware flashing mod? (it might be a waste of time as well, lol)
 
Isnt possible to add a check to the ccapi installer? So if the installer knows that the user is running hen and not a cfw then it display a message that say that ccapi cannot be installed on hen?

It should be easy to check that

This way we could reduce ps3 ss brick
 
I bought a PlayStation 3 Superslim (cech-4204a) which is ccapi bricked for 10 bucks. At first, i bought it for parts (for repairing my 500gb ps3, just in case anything happens), but then i wanted to make it function. When i power it on, the hdd indicator doesn't flash, no image displayed (no pad syncing) and safe mode is not working too. I found out that the console didn't have an hdd, but it had the 16gb (12gb usable) emmc flash. I am thinking of getting the 500gb drive from my main console and put it onto the 12gb one. Should it launch? I am wondering about the firmware differences as well, as i don't know what firmware it has. I want to test it, but right now, it is not on my home. What's your opinion? Is it saveable or should i try and use the hardware flashing mod? (it might be a waste of time as well, lol)
if you can solder it and read/write the nand, then you could make a dump and it could be analyzed and possibly made working. I have not actually looked into this at all, but i do have at least one emmc ss i could potentially also dump and compare some stuff
 
I am thinking of getting the 500gb drive from my main console and put it onto the 12gb one. Should it launch? I am wondering about the firmware differences as well, as i don't know what firmware it has.
Firmware is on flash memory, not on HDD. And HDD is encrypted per console keys. For Your eMMC console, HDD from another be filled by garbage, treating like empty (so it is like in every other PS3s). Besides that, You still need fully functional console for HDD switching, at least so-called recovery must work and things it is depend of. Or else You will not be able to switch to HDD.

Even if what I said above would be bullshit (which unfortunately isn't), You would hit another problem: on NAND models on HDD there is cache partition and user partition, on NOR, we have cache partition, user partition and vflash which contains data not fitted on NOR which was before on NAND. On eMMC it is probably the same structure as NAND, but in eFlash section is VHDD section like VFLASH on HDD on NOR models (we don't know that because we don't have low level access to decrypted storage, and no known way to retrieve decryption keys to do that outside PS3, so everything in this margin are speculations).
 
Oh my, are you the one from r/PS3 i advised to come here before doing anything with that unit? If that's so i wish you learned something now xD
 
You can try mounting the drive with linux using gparted, then try to backup the drive. Or just delete all partitions and then create new mbr ntfs partition and put it back in the console. If you can enter recovery mode try option 3 w/o hdd. If nothing else you can buy usb flasher for about 5$ and use that to try to fix that unit.
 
@esc0rtd3w as enstone probably will never update the ccapi installer to avoid installation on ps3 hen console, isnt possible to update ps3hen to avoid running the ccapi installer (just by title id checking - dev_hdd0/game/ENSTONEXX)?

So if a ps3 hen user try to run the ccapi installer (the eboot inside ENSTONEXX folder) then an error message is displayed that alert the user that ccapi cannot be installed on ps3 hen?

It is not the best way to do that, but user never read warning message and enstone will never update the ccapi installer
 
@esc0rtd3w as enstone probably will never update the ccapi installer to avoid installation on ps3 hen console, isnt possible to update ps3hen to avoid running the ccapi installer (just by title id checking - dev_hdd0/game/ENSTONEXX)?

So if a ps3 hen user try to run the ccapi installer (the eboot inside ENSTONEXX folder) then an error message is displayed that alert the user that ccapi cannot be installed on ps3 hen?

It is not the best way to do that, but user never read warning message and enstone will never update the ccapi installer
Yes, we were going to look into blocking it next update.
 
Maybe You could create empty folder with that ID and set him read only permissions (0444) so installer will return error trying overwriting it and/or unpack there contents? I'm not sure if empty folder are treating like Corrupted Data, if so, then maybe put there just PARAM.SFO with some info that it is CCAPI placeholder or whatever.
 
Maybe You could create empty folder with that ID and set him read only permissions (0444) so installer will return error trying overwriting it and/or unpack there contents? I'm not sure if empty folder are treating like Corrupted Data, if so, then maybe put there just PARAM.SFO with some info that it is CCAPI placeholder or whatever.
Pretty good idea. I like that. We'll have to do some tests.
 
You can try mounting the drive with linux using gparted, then try to backup the drive. Or just delete all partitions and then create new mbr ntfs partition and put it back in the console.
For what reason? PS3 not using MBR partition table, nor the NTFS filesystem. If the goal is to make the disk unrecognized, it is pointless too because it will be unrecognized anyway as data cannot be decrypted from different console.
 
Back
Top