dark420bishop
01-12-2007, 07:16 PM
Use Cintro without having to risk bricking! No flashing involved!
Okay everyone probably already knows this but there's an easy way to fix the original Cintro to work on 3.03 OE-A' and 3.03 OE-B. I claim no credit for any of this. I just rearranged the files using Piccahoe's release (http://dl.qj.net/CIntro-PSP-Homebrew-Applications/pg/12/fid/10679/catid/140) and Shadowz' (http://forums.qj.net/member.php?u=43783) guide (http://forums.qj.net/f-psp-homebrew-discussion-12/t-guide-using-cintro-without-writing-to-flash-on-300-custom-firmwares-89753.html).
(No-flashing) Cintro for 3.03 OE-A' & 3.03 OE-B (http://dl.qj.net/dl.php?fid=12248) ... (Mirror 1) (http://fast.filespace.org/dark420bishop/CINTRO_0-1-OE_Mod.zip) (Mirror 2) (http://z33.zupload.com/download.php?file=getfile&filepath=18279)
Thanks to Piccahoe & Shadowz.
More thanks to Sorin P, C, and dark_alex.
Update:
* Jan 25, 07 - This is not working on 3.03 OE-C right now because the auto-boot function is reportedly broken in OE-C. I expect this to be working again in the next firmware update.
Okay everyone probably already knows this but there's an easy way to fix the original Cintro to work on 3.03 OE-A' and 3.03 OE-B. I claim no credit for any of this. I just rearranged the files using Piccahoe's release (http://dl.qj.net/CIntro-PSP-Homebrew-Applications/pg/12/fid/10679/catid/140) and Shadowz' (http://forums.qj.net/member.php?u=43783) guide (http://forums.qj.net/f-psp-homebrew-discussion-12/t-guide-using-cintro-without-writing-to-flash-on-300-custom-firmwares-89753.html).
(No-flashing) Cintro for 3.03 OE-A' & 3.03 OE-B (http://dl.qj.net/dl.php?fid=12248) ... (Mirror 1) (http://fast.filespace.org/dark420bishop/CINTRO_0-1-OE_Mod.zip) (Mirror 2) (http://z33.zupload.com/download.php?file=getfile&filepath=18279)
Thanks to Piccahoe & Shadowz.
More thanks to Sorin P, C, and dark_alex.
Update:
* Jan 25, 07 - This is not working on 3.03 OE-C right now because the auto-boot function is reportedly broken in OE-C. I expect this to be working again in the next firmware update.