title says it all. will still work ATM for 3.02OE-B/3.03OE-A/A'/B.
Printable View
title says it all. will still work ATM for 3.02OE-B/3.03OE-A/A'/B.
Does it brick
cant brick
wont work
honestly i doubt it would brick, being that 3.03OE-C doesnt even have a module/vshmain.prx....its split up which is why the firmware boots faster i think.
better to be safe than sorry, but i dont think it would just brick. it would just make a new file in flash0 that is unnecessary.
Interesting :D
Does anyone know if it is still safe to use if you modified the boot path to boot cintro from memory-stick instead of the flash0?
What's cintro???
Dark_alex
Elite PSP Hacker
Registered: Aug 2005
Posts: 338
Argh, the autoboot program is currently broken.
I don't know how i will fix that if the flash driver is not initialized at the point my code gets executed... Well i will think of something for next version
u cant use on oe-c
ne way to get the non flashing cintro to work cause it wont work for me:(
Yes. C Intro don't work on OE-C. At first, I thought it was just me. Like the DAX quote above says: Autoboot is broken in OE-C.
Kando warns his C-Inro mod isn't working on OE-C either, for techniqual reasons...
I guess we'll have to just suffice with custom bootsounds (instead of C-Inros) until someone figures out a work around, or when DAX releases a fix for it in OE-D...
BTW, a little off topic; but for the record, I installed Random Gameboot Mod, and it seemed too unstable on OE-C to call useable. (Which sucks b/c I loved it :( )