Is there any way of launching apps like OPL from the PSBBN with your chip enabled? I've been trying different methods to have PSBBN run apps with my Matrix Infinity Chip enabled but so far no luck.. It Freezes. Any thoughts on this?
As I mentioned in that another forum, try disable every "fix" things in the Matrix menu, specially the ATAD auto patch function
PSBBN + MODCHIP = BOOM PSBBN will WIPE EE memory and modchip patches go bye bye. Stop using modchips... lol
I once try using HDDOSD & a G2 ModChip on a SPCH-18000. Before HDDOSD loaded it worked ok.. but once HDDOSD was loaded it not working right. I'm thinking HDDOSD wipe EE memory as well. I removed the modchip and now I just use HDDOSD & HDLGameInstaller on a 320gb HDD.
Your modchip installation wasn't even done properly, was it? I remember that you mentioned that some part was not working as how it was supposed to. The HDD OSD is not DNAS-protected, so it won't ever wipe memory. On the other hand, the PSBBN does.
Surprisingly, the gentlemen @ PSX Planet had no problem running the PSBBN with their Matr!x. DNAS WithHDD threads, EE memory wipes and the Linux kernel setup gone fine. BUT, the crap failed to launch KELFs thru the MBR (that's the way the PSBBN runs stuff). MG decryption fuckup is a common issue with modchips. Also keep in mind that the Macrovision patch of the Matr!x mangles CDVDMAN (or CDVDFSV ?) in the IOP RAM, the ATAD patching method is quite lame... and I'm not mentioning its kernel hooks. For all your MG decryption needs, better disable all your modchip features.
True, I don't think it was ever working 100% right. Discs worked great but but the ATAD patching was not working... and once HDDOSD loaded the modchip more or less just stopped working. They say that the G2 is working 100% on SPCH-1x000 units but I don't think it was ever made for it as the guide for it was all wrong. My bad, I was just thinking that maybe it was somewhat the same problem.
Neither I did, but PSBBN wipes the patches, what make the modchip useless. The console is left in a state where it might even be unable to boot legit discs due to the ALTERA chip of the modchip being left in a "braindead" state. Keep in mind that the EE kernel stub controls the ALTERA chip through SIF sending commands through that EE memory window which let the EE poke registers of hardware connected to the IOP. The kernel stub writes to the ROM region to talk with the modchip, exactly like that lame HDDPro hunk of garbage does to talk to the harddrive it has attached.
