Recent content by haxxxen

maybe OFW DEX brick or resigning an OC lv1 gone bad. what is the story to this PS3? edit as long as lv0 gets loaded, it mostly can be software error

actually, no, it is not borked. you can even use a flasher during FSM, but you won't exit it magically this way. sounds like you are still in FSM, so do an official upgrade with lv2diag and 3.55 PUP on usb and then do exit FSM with other lv2diag, BUT only on FW 3.55. if you want to downgrade...

^^hey, some bot...well, dunno why so many fear LM, but I never had any problems so far, since about 2010. ok, maybe when cleaning off this stuff. I had run even my CECH-L with custom heatsinks and LM for few years in vertically position and there was never any dripping off, so they must be...

have you set platform toolset = PPU SNC?

interesting approach, but are there no problems? I have underclocked both 400/550 and got serious XMB slowdowns and tripple beep shutdowns. the only positive effect was the temps were equal and bit lower on both, CELL and RSX

does this mean, now you can get QA (=Install Package Files) on debug vsh (DEX, DEH) as well? currently, this only works on DEX with retail vsh, if token is re-calculated. talking about CEX2DEX/DEX2CEX, btw. or was it only sysconf_plugin? dunno exactly atm

@Mystix try booting without hdd first, and if you are lucky you still get the no hdd message. if so, you maybe have a chance to reflash safe CFW in Recovery (can take several tries) if you still cannot get it done, your only way to fix is using flasher and take NOR backup and replace lv1 in backup

@Berion does not work I was told, but have not tried myself

ok, I see. if possible, you want to go (the infamous) DEX route on Superslims. fine for me, but probably problem for regular users.

yay, jackpot (....bound to 4.21), thanks :D does the target do not interfere? I mean, token is bound to target/idps (already have checked this and improoved qa flagging myself), how could this help with retail?

it does not want to get into my mind, how exactly (please describe method) could this help? you cannot calculate and it is bound to DEX on the other hand, the case looks different and interesting :D

I think, maybe no bugs but features, because S0ny loves hardcoded values, lol

what's the point? how does this help anywhere?

oh, and please restrain from memory patches, which are unique!

I am sure, because of debug output and already have found the error in libfs_ sys library. must be some hardcoded value, so maybe can be patched...