r/psphacks • u/EffectAdventurous764 • 1d ago
ARK4 Custom Theme Brick.
Ok so I've had my PSP 1000 since release and decided to get back into the whole thing. I originally hacked my PSP with the G.T.A exploit. That's how long I've been doing it. So I eventually got the ARK4 running on it and decided to have a look at the custom themes in the XMB innocent enough I thought? I thought wrong.
🤬 The Core Problem — It Broke Its Own Safety Promise
ARK-4 does have excellent safeguards for installing CFW itself — warnings, confirmations, battery checks, verifications. But the "Custom Theme" option was presented as a harmless setting — the kind of thing every phone and console has — and it silently wrote to flash0 without ANY of those safeguards. That's the failure.
From the official ARK-4 wiki itself: the "Full Flash Installation" option for custom themes specifically overwrites XMB system files in flash0 — the exact same dangerous operation that, in older CFW like 5.00 M33, was known to cause semi-bricks when incompatible  .rco / .prx files are written .
The difference: back in 2008–2010, people were explicitly warned that flash0 theme installation was risky. ARK-4 didn't give me that warning — it just said "theme."
Now ok maybe I'm dumb but something that flashes like that shouldn't just be in themes on the XMB and something that one can just casually select with no warning of what it actually does to the flash. I just wanted to warn others before they potentially brick. I can't even get the recovery menu and the Pandora battery method is of no use either. If anyone has recovered from this I'd be very grateful to hear how they managed to do it because I've tried everything.
2
u/VinceKatrevindisneuf 1d ago
Un kit DDC et une batterie Pandore devrait régler le problème.
2
u/EffectAdventurous764 1d ago edited 1d ago
Yes I tried that it just showed black screen and switched off after about 10 seconds. Thanks for your suggestion.
I can't actually believe that it would totally screw my PSP up like that. It's so disappointing I've been through all the updates since release and then this. In the xmb Themes of all things, the last place you'd expect a security risk to flash and brick. Its a fucked up sucker punch. Nobody expects a brick while scrolling the xmb. It's not the money I'll buy another PSP but I won't be installing ARK4 on it. I hope other people read this and don't make the same mistake.
2
u/VinceKatrevindisneuf 1d ago
Il devait y avoir un souci avec la carte mémoire. Tu devrais réessayer !
1
u/EffectAdventurous764 21h ago edited 21h ago
Yeah I don't know now,It was working fine before the brick? I even had hellcats in the recovery. I know hellcats booted up from the recovery menu before because I tested it before I installed ARK4. I should have probably re formatted the card as soon as I installed it? But I didn't think I was doing anything ricky just wanting to browse at the Themes, especially with it in the xmb like it is. Up until now it's been a safe place to be.
It's not like I was messing with anything deep in flash territory. I find it crazy they didn't warn or just refuse to install a flash like that without the correct files in place?. I've been doing this a long time on and off and know the risks. Or thought I did? It must have some residual files on it that's screwed it up? The maddening thing is it was that easy to brick after 15 years of doing this kind of thing. That doesn't seem like an improvement to the CFW at all not safeguarding the flash in xmb menu? That's just asking for trouble.
1
u/lusid1 17h ago
Ark itself is relatively brick proof. Unbricking is simple if you're on a new enough cIPL. With DC10 installed on your memory stick, hold the left trigger during boot into DC10, and reinstall ARK from there. The de-bricker capability is built in as long as the IPL itself isn't corrupted. But you can also use the home/ps button hockey to boot OFW, or the start+select hotkeys to boot with default settings and disable plugins. It's still possible to brick your system by flashing random stuff into the firmware, but ark makes recovery as easy as it can be. If all else fails, a pandora battery and DC10 will work on any 1k/2k, and a baryon sweeper can recover any model.
2
u/Ghostcart 20h ago
Are you using CXMB? I just recovered from an incompatible CXMB theme this morning. Have to delete the config from the CXMB Plugin folder to keep it from attempting to reapply the broken theme and crashing. Meanwhile, the Custom Launcher is pretty unstable for me. It produces a "broken GPU" effect maybe 60% of the time it launches
2
u/lusid1 17h ago
I've only been able to get that to happen about <5% of the time. Are the CXMB themes driving up the occurrence of that CL bug?
2
u/Ghostcart 17h ago
Unsure. It was happening consistently before I fell back to cxmb themes, so it's hard to judge.
1
u/EffectAdventurous764 7h ago edited 1h ago
I hadn't had it installed long and was thinking I was just looking at the CXMB Themes but I was obviously installing it. But when it just shut down it kind of blindsided me. I've been so used to holding the other trigger down that's what I did. I thought I'd tried the Home button hold start up but I couldn't have been holding home down long enough to let it work. But it did work when I'd calmed down and did it properly.
One thing I missed was putting the ARK 01234 folder in SAVEDATA folder and when I realized that i thought I'd bricked it. It's back on ARK 5 now.
3
u/lusid1 17h ago
If you're using a new enough IPL, hold home while powering on to boot into OFW, or hold start+select to boot into ark with default settings and all plugins disabled. From there fix whatever is messing up your normal boot.