[jhax78]

Originally Posted by bartez82 I have PS3break v1.0 and I'm 100% sure it's working well.I have used this a lot of times.I think in this patched bin still seating something from 3.56 that why ask me for 3.56 firmware or higher. One mor Q. After re-flash did i need install firmware from FSM or install e3_downgrade.bin and then FSM?

don't use e3downgrade.bin or something.

only flash the patched bin back

then install from fsm like it always was with 3.55
it gets prepatched for 3.55 ofc there's still 3.56 fw there

and make sure you power eject fast enough


just for the heck of it i prepatched another with 2.05 patches to see what happens if all other things fail
check pm

[haz367]

verify by wiki and its a minverchk 3.56, the tool reports 3.50 minverchk, this could be as my own 2504B 1A jsd-001 is also 3.50 minverchk and not what the wiki reports = 3.55? on it, does the tool gets the minverchk capable firmware from "trvk" files,for the 2504B 1A NORinspector also reports 3.50 for it, and just for tes...NORpatch reports back ROS0/1 reports 3.56v1/3.56v2, rest unknown..

why is the Tool crashing on that offset in 3.56v1?!, i see every dump with diff firmwares have same value at that offset = the fixed one on C0000..so it must be the 3.56v1 and coded into the NORinspector for it to crash or something...

and IS IT the reason of that offset to not boot?

00 00 00 03 00 00 00 09 00 00 00 00 00 4B 19 CC @ C0000

dont think so right? it got updated to 3.56v2 after it, the install error seems from the 3.56v1 one/offset C0000?! noticed after pathing the 3.56 dump the offset C0000 isn't changed = bad line....if everything else is OK like hdd etc..then these pre-patched dumps should work, either 355 if it can go that low..else use the 4.30 one(all switches down or first up-rest down) to restore, with 355 trigger FSM and for 430 reboot into recovery

good infos and this NORinspector is a great tool btw..

@bartez82
incase u wanna test
http://rghost.net/43773981

[bartez82]

@jhax78 I have re-flash yours another patched bin and now preparing for update stop on 99% and nothing happends.I install rogero 4.30 v2.05 straight away.

[jhax78]

Originally Posted by bartez82 @jhax78 I have re-flash yours another patched bin and now preparing for update stop on 99% and nothing happends.I install rogero 4.30 v2.05 straight away.

very strange need to have a good thinking about this
it should not behave like this anymore

fsm way btw

[playerkp420]

Try a different HDD.

[euss]

Originally Posted by haz367 verify by wiki and its a minverchk 3.56, the tool reports 3.50 minverchk, this could be as my own 2504B 1A jsd-001 is also 3.50 minverchk and not what the wiki reports = 3.55?

Wiki list that console as minver 3.50 with revision key C3266E4BBB282E76B7677095

00 00 0E 92

C3 26 6E 4B BB 28 2E 76 B7 67 70 95

CECH-25xx (JSD-001/JTP-001) 0xB

Metldr 3.50+ Enforced

Source: http://www.ps3devwiki.com/wiki/Talk:...asecure_loader

0B	CECH-25xx (JSD-001) with 3.56 from factory - datecode 0D	E9 60	0E 92	2F570	2F 53	2F 53	OK	3.50
0B	CECH-25xx (JTP-001) with 3.56 from factory - datecode 1A	E9 60	0E 92	2F570	2F 53	2F 53	OK	3.50

Source: http://www.ps3devwiki.com/wiki/Valid...Bbootldr_sizes

And minver PUP will also report 3.50 nicely: http://www.ps3devwiki.com/wiki/Talk:...e_version_info

THERE IS NO MINVER 3.55
Stop sniffing paint please

Originally Posted by haz367 IS IT the reason of that offset to not boot? 00 00 00 03 00 00 00 09 00 00 00 00 00 4B 19 CC @ C0000

The ROS header corruption was indeed preventing console to boot from ROS0, as the wiki shows: http://www.ps3devwiki.com/wiki/Flash:ROS#ros0
0x4B19CC is too short for ROS0 and the 03 / 09 likely set the offset for it wrong, thus not loading the filetable that it normally points to, like wiki documents. Reason NORinspector crashed is the same reason why the ps3 was unable to interprete the ROS tables.

Originally Posted by bartez82 @jhax78 I have re-flash yours another patched bin and now preparing for update stop on 99% and nothing happends.I install rogero 4.30 v2.05 straight away.

When updating directly to v2.05 you are not solving the corruptive errors. Downgrade to 3.55 v3.7 first (using PSgrade/JIG), QA-flag it (check QA-menu comes up after button combo) , then dehash to make sure syscon has a clean set of hashes. From there, update to 4.3x 2.05 or higher. //end wiki guide

[bartez82]

Originally Posted by euss When updating directly to v2.05 you are not solving the corruptive errors. Downgrade to 3.55 v3.7 first (using PSgrade/JIG), QA-flag it (check QA-menu comes up after button combo) , then dehash to make sure syscon has a clean set of hashes. From there, update to 4.3x 2.05 or higher. //end wiki guide

I have try with fsm but i cant put my ps3 into fsm.Dongle is light up but the console not turned off by itself.

[jhax78]

eussNL> he is doing FSM wrong too, wrong hex, wrong trigger, no poweroff, not reading wiki etc.

[bartez82]

Originally Posted by jhax78 eussNL> he is doing FSM wrong too, wrong hex, wrong trigger, no poweroff, not reading wiki etc.

I have check it dongle on Fat 80gb 3.55 and works fine,then update to 3.56 and do FSM without any problems.So why i can't put this f***** Slim in to FSM?

[playerkp420]

Originally Posted by bartez82 I have check it dongle on Fat 80gb 3.55 and works fine,then update to 3.56 and do FSM without any problems.So why i can't put this f***** Slim in to FSM?

Follow METHOD 3 in Chapter 2, of the guide below. I bet that works.