• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Updated Phone Rooting

J

jamala00

Android Enthusiast
OK guys, I have an OTA Up To Date Inc 2 and was wondering if somebody can point me in the right direction to root this thing and get S-Off? I just did it to an old Org Inc I had and it wasn't to bad. Wondering if I can do something similar with my Inc2?

I would also like a stock "Debloated" Sense Based stock GB ROM to load on it after it's rooted.

Can somebody get me pointed in the right direction? It would also be nice if there was a fix for the Apple Lawsuit of directions only opening in the browser instead of Maps...
 
this is what i would use:
[GUIDE] Comprehensive S-OFF/Root Methods - xda-developers
its basically doing the same thing you just did on your inc 1,with exception that youre using taco root for temp root,rather than htcdev.

the directions and commands are a lil confusing,just extract the files it says to extract,and then put everything into a "miniadb" folder.

if you want to keep your inc 2 adb files seperate from inc 1 files(wich is a really good idea) use this one: mini-adb.zip it contains no phone specific files. just download and extract it like you did with the inc 1,and rename it "miniadb_inc2" and put all the files you download into it.

make sure to cd c:\miniadb_inc2 and then you can copy/paste the commands from the code boxes on xda without worrying about the "put the path in front blah blah" pART.

if i get a chance ill try and update to your firmware,and run thru it on my inc 2,and see if there are any hitches to watch for.

otherwise,just holler if you have questions.

edit:
its also worth noting,that if you can find someone with an xtc clip,it will work on the inc 2 and give you a true radio s-off,unlike the patched hboot that you get from revolutionary. if you happen to be within driving distance of dayton,oh,i could do it for ya :D
 
bberryhill0 said:
I'm pretty sure s-off is s-off no matter how you get it.
Click to expand...

yes and no.

the affects of a patched hboot are largely the same,in that you can flash radio files,splash images,etc. pretty much anything other an hboot. ;)

however,the radio s-off is superior,imo,in that the phone is not doing any security checks. the patched hboot is simply ignoring the radios helpless cries that its s-on.

think of it this way:
hboot finds a file. it asks the radio,"hey is security on??".
s-off radio answers "nope.i dont care what you do."

s-on answers "yup. is that file signed? better check it out". hboot replies "nope,im not checkin anything. im just gonna go ahead and flash it" :eek:

as long as hboot versions remain pretty similar,a patched or real eng hboot works fine-alot of devices have recieved s-off via an eng,or patched hboot(eris,thunderbolt,even the nexus 1). however,as firmware progresses,those with patched hboots will be stuck at certain softwares until someone patches new hboots. or they will be forced to give up s-off in order to run compatible new hboots.

ICS is a good example. every device ive seen thats gotten a factory update has gotten a new hboot along with it,and its not compatible with gingerbred. yes there are ways to make it work. the ICS ports for the inc 2 and otrher devices have been made to work with available firmware.

but,if the inc 2 got an official ICS update,and you flashed the ruu and it contained a new,incompatible hboot,it wont work. with a radio s-off,you can simply flash the new bootloader,and still be s-off.

hope that clears it up a lil. :)
 
scotty85 said:
this is what i would use:
[GUIDE] Comprehensive S-OFF/Root Methods - xda-developers
its basically doing the same thing you just did on your inc 1,with exception that youre using taco root for temp root,rather than htcdev.

the directions and commands are a lil confusing,just extract the files it says to extract,and then put everything into a "miniadb" folder.

if you want to keep your inc 2 adb files seperate from inc 1 files(wich is a really good idea) use this one: mini-adb.zip it contains no phone specific files. just download and extract it like you did with the inc 1,and rename it "miniadb_inc2" and put all the files you download into it.

make sure to cd c:\miniadb_inc2 and then you can copy/paste the commands from the code boxes on xda without worrying about the "put the path in front blah blah" pART.

if i get a chance ill try and update to your firmware,and run thru it on my inc 2,and see if there are any hitches to watch for.

otherwise,just holler if you have questions.

edit:
its also worth noting,that if you can find someone with an xtc clip,it will work on the inc 2 and give you a true radio s-off,unlike the patched hboot that you get from revolutionary. if you happen to be within driving distance of dayton,oh,i could do it for ya :D
Click to expand...

You know I could always just activate the Inc I just rooted for a week or so and send this Inc2 to you so you could? Just a thought? Also like I mentioned I may end up with the Inc 4G this weekend...;)
 
jamala00 said:
You know I could always just activate the Inc I just rooted for a week or so and send this Inc2 to you so you could? Just a thought? Also like I mentioned I may end up with the Inc 4G this weekend...;)
Click to expand...

i certainly would do it for you,if you wish to do that. just cover shipping both ways with however much insurance you need.

you also might search craiglist for "unlock htc" and see what pops up. there are alot of adds around here for guys that will root and rom phones,and simunlock. alot of them are using the xtc clip. its not impossible that you can find someone local where you could take the phone,and theyll unlock it with the clip(giving s-off and superCID in the process :D)for $10-$20. might also check with some of the smaller phone shops,and maybe even put a post in general on xda.

but failing all that,shoot me a PM and ill give you my snail mail addy if you decide to do it that way.
 
bberryhill0 said:
SuperCID doesn't seem to be applicable to this phone.
Click to expand...

if by "applicable" you mean "not much point" youre correct. the only RUUs safe to flash on the inc2(that i know of at least) are the vzw ones, and you dont need to be superCIDed for them. :p

but if the xtc clip is used,supercid is a by-product of the diag file thats used. its not needed,but you get it,and it doesnt hurt anything either. if it bothers you(not you specifically. you the public in general),it can be changed. this was with the eng 0.98.2000 hboot. red are my inputs:

Code: 
c:\miniadb_inc2>[COLOR="Red"]fastboot getvar cid[/COLOR]
cid: 11111111
finished. total time: 0.001s

c:\miniadb_inc2>[COLOR="red"]fastboot oem changeCid vzw__001[/COLOR]
                              ... INFOChage CID command
INFOsdcc_init_memory_device done
INFOStart to do authentication
INFOsdcc_init_memory_device done
INFOsdcc_init_memory_device done
INFOsdcc_init_memory_device done
INFOsdcc_init_memory_device done
INFOsdcc_init_memory_device done
INFOsdcc_init_memory_device done
INFOStart to change CID!
INFObuf_addr:4FC300,buf_size:200,start_sector:1739D
INFOsdcc_init_memory_device done
INFOFinish write sector address 1739D ...
INFODone!
OKAY [ 35.472s]
finished. total time: 35.474s

c:\miniadb_inc2>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
     rebooting into bootloader... OKAY [  0.144s]
finished. total time: 0.144s

c:\miniadb_inc2>[COLOR="red"]fastboot getvar cid[/COLOR]
cid: vzw__001
finished. total time: 0.001s

c:\miniadb_inc2>

one last thing to consider is that radio s-off on the inc 2 is not reversable. the writesecureflag command is not part of the oem arsenal,and there is not firmware old enuff for the gfree exploit to work on,so once you sure the radio secure flag off its off for good.(read: no way to s-on)

on a side note,i just updated my inc 2 to the 6.01.605.1 fimrware. i will go thru the steps in the guide when i get a chance,if you wish to use revolutiionary,wich is reversable,if you need it.
 
i just ran thru the commands... they are not so much user friendly. i had to change one of the commands. it was also a little tricky figuring out wich link to clock to download taco root :eek:

but anyway,heres what it looked like. red are my inputs:

Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>[COLOR="Red"]cd c:\miniadb_inc2[/COLOR]

c:\miniadb_inc2>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:\miniadb_inc2>[COLOR="red"]adb push tacoroot.sh /data/local/[/COLOR]
297 KB/s (2129 bytes in 0.007s)

c:\miniadb_inc2>[COLOR="red"]adb shell chmod 755 /data/local/tacoroot.sh[/COLOR]

c:\miniadb_inc2>[COLOR="red"]adb shell /data/local/tacoroot.sh --setup[/COLOR]
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by

both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory

c:\miniadb_inc2>[COLOR="red"]adb shell /data/local/tacoroot.sh --root[/COLOR]
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by

both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.

c:\miniadb_inc2>[COLOR="red"]adb push misc_version /data/local/tmp/misc_version[/COLOR]
2542 KB/s (367096 bytes in 0.141s)

c:\miniadb_inc2>[COLOR="red"]adb shell chmod 777 /data/local/tmp/misc_version[/COLOR]

c:\miniadb_inc2>[COLOR="red"]adb shell /data/local/tmp/misc_version -s 2.18.605.3[/COLOR]
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...

c:\miniadb_inc2>[COLOR="red"]adb shell /data/local/tacoroot.sh --undo[/COLOR]
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by

both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Root removed, rebooting

c:\miniadb_inc2>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inc2>[COLOR="red"]fastboot getvar mainver[/COLOR]
mainver: 2.18.605.3
finished. total time: 0.001s

note that i had to change this command:
adb shell sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
to this:
adb shell /data/local/tmp/misc_version -s 2.18.605.3

and that my phone was bootlooping while i entered this block of commands(:eek:) :
Code: 
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb shell /data/local/tacoroot.sh --undo
adb reboot bootloader

i did not run the ruu,as it would have worked for me anyway(radio s-off) but the fastboot getvar command shows the main version is what was intended,so if it was an s-on phone,the downgrade would have worked.

last adn not least,when using RUU mode,erase cache prior to entering ruu mode. i find doing it aftrer frequently disconnects the device and youll have to unplug and pull the battery to get it connected again.

if you want,i can take the commands and organize them a little better and with a little more info. as i said,the xda directions are somewhat lacking if youre not somewhat familiar with things.
 
If you don't mind cleaning them up. The Inc I did was very straight forward, copy\paste instructions. If you can get these that way, I probably would attempt this phone also. Didn't end up with the Inc 4G yesterday, went to the store here after dinner, but I was to late the doors were locked. Will probably be going back today...
 
You must log in or register to reply here.
Back
Top Bottom