Since locked Verizon SGS3 is now the main problem, i'v decided to split my kernel thread to separate one that focus directly on unlocking bootloader and progress in that matter.
Summary of the problem
Verizon model is protected from flashing unsigned/modified boot.img and recovery.img. Which means there is no known root method as for now for SCH-I535.
And that is where our adventure starts ....
Rooted stock boot.img issue:
CWM Recovery.img flash issue:
Research status: 50%
+ 20% - Some devs stated that RIL is hacked and there is also sucessfull Kexec implentation in works - http://forum.xda-developers.com/show...&postcount=262 Stay tuned for more news. Kexec proof-of-concept thread: http://forum.xda-developers.com/show....php?t=1760678
+ 20% - phone can boot from unsigned boot.img flashed to recovery partition, this will leave you without recovery and requires to boot-trough-recovery every time u rebooting phone! (thanx invisiblek)
Links: http://forum.xda-developers.com/show...9&postcount=47 , http://pastebin.com/eARk7r48
+ 10% - phone rooted trough system.img tricks -> http://forum.xda-developers.com/show....php?t=1756885 (by invisiblek)
ROM analysys:
boot.img -> signed
recovery.img -> signed
system.img -> not signed
cache.img -> not signed
Update [7/7/2012]
News about locked Verizon model is spreading over the websites and main tech-related portals. Hopefully we will get some detailed info soon.
Update [7/7/2012]
It looks like it has been rooted by using system.img trick (system.img is not signed)
http://forum.xda-developers.com/show....php?t=1756885
Enjoy! and thanx to invisiblek :) good job!
Thanks!
Summary of the problem
Verizon model is protected from flashing unsigned/modified boot.img and recovery.img. Which means there is no known root method as for now for SCH-I535.
And that is where our adventure starts ....
Rooted stock boot.img issue:
Quote:
<ID:0/008> Firmware update start.. <ID:0/008> boot.img <ID:0/008> NAND Write Start!! <ID:0/008> FAIL! (Auth) |
Quote:
<ID:0/003> Firmware update start.. <ID:0/003> recovery.img <ID:0/003> NAND Write Start!! <ID:0/003> <ID:0/003> Complete(Write) operation failed. |
+ 20% - Some devs stated that RIL is hacked and there is also sucessfull Kexec implentation in works - http://forum.xda-developers.com/show...&postcount=262 Stay tuned for more news. Kexec proof-of-concept thread: http://forum.xda-developers.com/show....php?t=1760678
+ 20% - phone can boot from unsigned boot.img flashed to recovery partition, this will leave you without recovery and requires to boot-trough-recovery every time u rebooting phone! (thanx invisiblek)
Links: http://forum.xda-developers.com/show...9&postcount=47 , http://pastebin.com/eARk7r48
+ 10% - phone rooted trough system.img tricks -> http://forum.xda-developers.com/show....php?t=1756885 (by invisiblek)
ROM analysys:
boot.img -> signed
recovery.img -> signed
system.img -> not signed
cache.img -> not signed
Update [7/7/2012]
News about locked Verizon model is spreading over the websites and main tech-related portals. Hopefully we will get some detailed info soon.
Update [7/7/2012]
It looks like it has been rooted by using system.img trick (system.img is not signed)
http://forum.xda-developers.com/show....php?t=1756885
Enjoy! and thanx to invisiblek :) good job!
Thanks!