SamyGO

You welcome.

I`ve got the same with 3000.2 and ex-link...
I can enter "debug" and the console says but i can`t activate DEBUG TOP menu with 1198282. It doesn`t accept any other inputs exept "debug"
I can`t activate linux shell with ctr+c too...
I can`t enter to the boot menu with "~" also. It freezes on the first line "ONBOOT: ...."
It`s verry sad. Does someone know another code/method to activate linux shell?

juuso wrote:I`ve got the same with 3000.2 and ex-link...
I can enter "debug" and the console says

Code: Select all

[SERIAL INPUT MANAGE] 1-th ENABLE Magic serial input match! 
[SERIAL INPUT MANAGE] 2-th ENABLE Magic serial input match! 
[SERIAL INPUT MANAGE] 3-th ENABLE Magic serial input match! 
[SERIAL INPUT MANAGE] 4-th ENABLE Magic serial input match! 
[SERIAL INPUT MANAGE] 5-th ENABLE Magic serial input match! 
[SERIAL INPUT MANAGE] serial input ENABLE!!!!!

but i can`t activate DEBUG TOP menu with 1198282. It doesn`t accept any other inputs exept "debug"
I can`t activate linux shell with ctr+c too...
I can`t enter to the boot menu with "~" also. It freezes on the first line "ONBOOT: ...."
It`s verry sad. Does someone know another code/method to activate linux shell?

I guess enter boot menu worked before for you ?
I'm suprissed as boot menu is diffrent partition of flash and new firmware doesn't have such files in update bundle.

I didn`t try it before i flashed 3000.2. The fact is that i can`t enter to boot menu. it`s not necessary, the main problem remains that i can`t use samyGo...
I`ve idea... why don`t try like

erdem_ua wrote: Modify it via SamyGO Firmware Patcher
Encode exe.img by XOR and AES
Put it to v2005's image directory.
Modify exe image Checksum
Mofidy the version number to 2006
Use RSA Disable to disable RSA check
Flash!

Basis of update - old firmware. Thinks to make - all as erdem_ua in another post wrote but version number change to 3001 or smth else? Does fw upgrade not start properly? Like fake upgrade. Realy - downgrade? If samsung upgrade process starts after it checks fw version in USB, then all what we have to make - falsify upgrade version number to revert firmware back?I gues its to easy to be truth?
Do i think wrong?

2) Which source? There is no source at all! You needed to read binary /assembly here.
3) We can also prepare attack to RSA keys with cloud OpenCL applications. But problem is if we succeed, samsung will change that RSA key at next update...

4* Alternative = Hack first burn later approach that a mechanism could implantable to FW Patcher that disables Content library checking...

And isn't it possible to get the RSA keys ?!

RSA uses asymmetric keys.
We could get 'public' keys which needed for verify package but we need 'secret' keys for signing our package.