Root After Update 7/8/2011

[roman08225]

What is the easiest way to root after current update?

I tried rooting previously (1 click root) and it was giving me error that my ADB, IMAGE was old. So now i want to try again with new update, what is the best way to do it

 

[fatboy97]

I found the ADB process to work very well for me... I read it completely through the first post... then did it... but that was a couple months ago... I'd check the last couple pages on that thread to see how it's working for others... then if it looks good do it.

 

[shellguy05]

I just did the one click today while at work. I downloaded all the needed files at home on my laptop and when I got here I rooted it. Took me about 45 min and went smooth as silk. Luckily! All thanks to the Android Central community!

 

[shellguy05]

Oh, I had done the newest update from VZW. Just updated a few days ago.

 

[baldmike]

I rooted 3rd Thunderbolt yesterday, after accepting the ota last week. My 1st T-bolt went bat **** crazy and the screen would 'twitch' often. My 2nd, lost the ability to get 4G. So VZW sent me anouther phone and I waited a couple weeks before rooting to make sure it was okay. Anyway, I heard a rumor that either VZW or HTC (can't remember which) were going to patch the firmware so you can't root on the next ota. I don't know if it's true or not, but I didn't want to take a chance. After doing the auto root, I flashed [ROM][FROYO][MR2] Team GTP Eaton Rom v1.5.3 and have had no issues. It is stable and snappy! Still Froyo, but I'm happy with it.

Edit: Sorry, posted wrong ROM the 1st time.

 

[roman08225]

this is the error that i get (see attached)

 

[roman08225]

by the way i did pull the battery tried few times and nothing. Is it because of old ADB?

 

[baldmike]

Maybe, I've only used ADB to unroot. Try the auto root, it works fine. I've used it on 3 different T-bolts and have had no issues. Sure, it only brings you up to MR1, but then you can flash any ROM and/or radio you want.

[Auto] Root and Unroot (Windows)**Updated**5/20** w/MR1 update

 

[chuckh0308]

I get the same errors with the auto root and I've tried about 15 times, including re downloading everything. I think a friend of mine who is an Android developer is going to give it a go one of these days...

 

[baldmike]

Well, I'm at a loss. Do you have USB Debugging turned on? Settings > Applications > Development > USB debugging. Is there a green check mark in the box? Also, make sure Stay Awake below that has a green check in it as well. Also, you might try different USB ports on your computer. I hear that can give you problems as well.

I just rooted my phone yesterday with the auto root and had no problems. I'm no pro at this by any means, so I'm not the best to get advice from.

 

[Smitty_82]

This error is most likely due to the USB port you are using. ADB will only work on the primary USB port. On a desktop, it will be one of the ports on the back. On a laptop/netbook, your guess is as good as mine. Just keep trying with different ports untill you find the one that works.

 

[turdbogls]

Good to know. i got the same message as in the pics. this also caused me to loose constant 4G connectivity for some reason. not sure why, but 4G was good before, and not working properly afterwords. got a new phone yesterday, will be trying auto root in the coming weeks. hopefully all goes well. i would love a rooted TB WITH 4G service.

 

[jeski]

Just curious, how is battery life after rooting?