WARNING: DO NOT ENTER SERVICE MODE IN 3.56 OR 3.60 (YOU WILL BE STUCK IN IT FOREVER END OF STORY!!)

**Ben Jeremy** · 01-27-2011,10:30 AM

So we just need to use the latest 3.56 lv2 (or was it app?) key to resign the executable with a new authid.

We should try signing the modified "exit" self with the lv2, l1, and app, and see which one works.

Sorry somebody is now the designated guinea pig, but hopefully somebody can knock this out (I'm on company time right now, otherwise, I'd look into finding the tools to resign/rencrypt the self.

I think this time we will have to decrypt the self and re-encrypt it, too... I don't know if the tools are up to the task, or if they are still hobbled (yes, I'm glaring at you, Marcan). Enough with the silly anti-piracy stances holding back the actual homebrew scene. We need the master npdrm keys (to make homebrew work on ALL firmware) and we need working tools!!

**sorrowuk** · 01-27-2011,10:33 AM

^^ I don't think we can do that though.

We can't get the 3.56 private key. This is the key that encrypts everything for 3.56.

And apparently you can only run 3.56 lv2diag.selfs from service mode now and we dont have any

**Ben Jeremy** · 01-27-2011,10:59 AM

Originally Posted by sorrowuk

^^ I don't think we can do that though.

We can't get the 3.56 private key. This is the key that encrypts everything for 3.56.

And apparently you can only run 3.56 lv2diag.selfs from service mode now and we dont have any

Ah yes... I see that. Sony will likely fix their random number generator now.

So this will require a custom firmware with patches to run unsigned apps at several levels.

...and flashing firmware from the XMB in service mode is bad news. Not good.

Can't exit service mode without the ability to run unsigned apps, but can't flash patched firmware to run unsigned apps. Nasty catch-22 there.

**fldash** · 01-27-2011,11:18 AM

I think Sony just accidentally the whole PS3...

Yikes!

**UnXuthoriXeD** · 01-27-2011,01:00 PM

Well I hope some of you guys are wrong and we can fix the lv2diag. Thankfully I have 3 other ps3s this was the 1 I test everything on. Funny thing is, iv bricked and unbricked this one twice and service mode might be what kills it.

**hackeyking** · 01-27-2011,01:11 PM

Originally Posted by fldash

I think Sony just accidentally the whole PS3...

Yikes!

[lang=fr]i dont think it was accidentally[/lang]

**Ben Jeremy** · 01-27-2011,01:55 PM

Originally Posted by UnXuthoriXeD

Well I hope some of you guys are wrong and we can fix the lv2diag. Thankfully I have 3 other ps3s this was the 1 I test everything on. Funny thing is, iv bricked and unbricked this one twice and service mode might be what kills it.

I know you aren't SUPPOSED to update in Service mode, but it might be possible, once 3.56 CFW is out, to try it, and maybe you'll have access to the lv2diag tools again under patches in the new CFW.

That or maybe a patched COREOS to allow you to run the lv2diag.

Something... people will undoubtedly need some sort of solution.

**jordn** · 01-28-2011,02:29 PM

i went from 3.55 OFW > GEO > Waninkoko + GEO

ON 3.56 NOW

all signed aps stayed, just cant open retruns to XMB,

**Ben Jeremy** · 01-28-2011,05:18 PM

I think Sony has pissed off the wrong person.

Maybe graf_chokolo can come through and giuve us some of the HV and CELL recovery modes that might be available... we can make our own pin jigs and fix some bricks.

**carlos123456** · 01-28-2011,05:35 PM

well posted sorrowuk thanks for the heads up even if this is just a pass on

User Tag List

Thread: WARNING: DO NOT ENTER SERVICE MODE IN 3.56 OR 3.60 (YOU WILL BE STUCK IN IT FOREVER END OF STORY!!)

Tweet

LinkBack

Thread Tools

Display


	Would you like to get all the new info from PSX-Scene in your email each day? Subscribe to our Daily Digest! Want to learn more about the team keeping you up to date with the latest scene news? Read about them now! Check out our Developer bios, too!