[JustThatDude]

Originally Posted by DEFAULTDNB The dongle masterkey generator hasnt worked since 3.55. I believe it was patched out by sony in 3.56+ rendering current dongles useless. I looked into this a while back.

You sure that we just haven't looked in the right places for it, I'm sure they didn't take it out of there OS. And if they did they would need to make another App to put FSM on because i don't think they could go without it.

[DEFAULTDNB]

You are correct in some senses. I would be 99% sure FSM exists, just how to access it is the question. Surely Sony cant make the same mistake again and re-use dongles (with updated keys) to access it? .. that would be too easy/obvious.

If only we knew a Sony engineer or someone with a clue as to how to get back in to fsm.

[JustThatDude]

Originally Posted by DEFAULTDNB You are correct in some senses. I would be 99% sure FSM exists, just how to access it is the question. Surely Sony cant make the same mistake again and re-use dongles (with updated keys) to access it? .. that would be too easy/obvious. If only we knew a Sony engineer or someone with a clue as to how to get back in to fsm.

I think they would stick to the dongle way because it takes so much time to open the Ps3. Maybe there isn't a usb/dongle way but I know almost for a fact it's a soft-mod which will probably never change because it just takes to much time to open. I was thinking maybe they can run it on a disc so that people like us wouldn't be able to get the files to run in FSM. I don't really know at this point but In my opinion I think it would be easier to just create a new FSM then downgrade to 3.55 so we can have homebrew.


Sent from my iPhone using Tapatalk

[DEFAULTDNB]

There must by that logic also still be a QA mode, I believe there must be new button combos or something, who knows what else lurks in the XMB.

[JustThatDude]

Originally Posted by DEFAULTDNB There must by that logic also still be a QA mode, I believe there must be new button combos or something, who knows what else lurks in the XMB.

Well tomorrow I'm going to start looking more deeply into FSM because I find it a lot easier than QA Flagging. Like I said I don't think it would be hard to just make a new FSM. I also think we could possibly find an exploit in the Data Transfer option by making a program run on the computer to downgrade through ethernet cable. The reason why i say we should downgrade is because a 4.11 Jb is clearly not coming out soon and also in my oppion harder.


Sent from my iPhone using Tapatalk

[DEFAULTDNB]

So you aim to make a software downgrader for those who have ps3's capable of minimum version check of <=3.55? Through ethernet?

Hardware cant even downgrade CECH 300x series PS3's.

Good luck with this project, I think you may have some interesting angles here, but I think it won't be so straight forward.

[JustThatDude]

Okay just thought about this what if we use Psjig to get into service mode? All you need is a Psp and lv2diag.self I believe like i said a lot more research will go on tomorrow. Read all the post on this website (there is only like 5): http://bit.ly/L2EYHb


Sent from my iPhone using Tapatalk

[DEFAULTDNB]

Again dongle and jigs (that we know of/non official sony tech support) will only work on <=3.55.

EDIT: PERHAPS you will get in but you DEFINITELY wont get out of it without newer signed LV2diag.

[playerkp420]

The problem isn't getting in fsm. The problem (from what I understand) is that once in, you can not call on the syscalls to do anything. Including getting out. So your console would be stuck in fsm. And the only way to fix it would be buying a hardware flasher.

So maybe to fix this, you would need to figure out how to make lv2diag.self files that are compatible with the higher firmware.

I could be wrong on how or why it works like that. But you get the basic idea.

[DEFAULTDNB]

Originally Posted by playerkp420 The problem isn't getting in fsm. The problem (from what I understand) is that once in, you can not call on the syscalls to do anything. Including getting out. So your console would be stuck in fsm. And the only way to fix it would be buying a hardware flasher. So maybe to fix this, you would need to figure out how to make lv2diag.self files that are compatible with the higher firmware. I could be wrong on how or why it works like that. But you get the basic idea.

Exactly right.

I only mentioned syscalls as an alternate method for downgrading (if DH MAD method is correct), but its useful to know that syscalls would be usless in the FSM environment.

LV2diag would just need signing for 3.60+ to get out afaik.