yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Powell730:
yeah my phone is still bringing up the verizon thing. in the bottom right corner you should get something that says your device is ready to use. so long as it does then youve got the drivers.
[Thunderbolt Android Development] HolyGrail:
Jr4000 try this tutorial to make sure your drivers are properly set up.

http://androidforums.com/evo-4g-tips...droid-sdk.html
[Thunderbolt Android Development] shanetrain:
Well, I finally got this thing to work.

Went through step one, no problems, a number of times.

I kept running into that stupid hash error on step 2, though, and couldn't get SU and Rom Manager installed.

I finally just started at step 2, and got it to take.

Much appreciation to the OP and the testers!
[Thunderbolt Android Development] tommyxv:
I got the "You now have a fully rooted Thunderbolt with S-OFF. Congradulations!" message.... :)

I check my versions and it looks like you don;t even have to use Rom Manager anymore. It's is back to normal. :)
[Thunderbolt Android Development] HolyGrail:
Yeah, adb is finicky at times an won't take. Congrats. :)
[Thunderbolt Android Development] jr4000watts:
so confirmed and for sure you are rooted?
[Thunderbolt Android Development] maizekidstill81:
Ok cannot get step three to reboot phone.

Have colsed reopened all the above
[Thunderbolt Android Development] HolyGrail:
Try closing out the program, unplug and replug, and try again on step 3. Also make sure debug is on. It gets turned off after reboot from step 2.

Make sure its showing you in adb devices.
[Thunderbolt Android Development] HolyGrail:
I don't understand. Did you finish all steps? Did you check fix permissions in rom manager to make sure all went well?
[Thunderbolt Android Development] maizekidstill81:
Debug is on . Closed out and unplug and plugged back in . Ran step 3 and no reboot.

Where do I see if it has me in adb devices?
[Thunderbolt Android Development] tommyxv:
I can confirm that I am rooted and everything is working just fine.
[Thunderbolt Android Development] gsxraddict:
Im rooted also had to kill rooter.exe a couple times but other than that its flawless. thanks for the amazing work!
[Thunderbolt Android Development] HolyGrail:
Right click in the package folder, and click on " open command prompt here"

Then type "adb devices" without the quotes.
[Thunderbolt Android Development] tommyxv:
After I re-booted from finishing step 3, I check my versions first and they are all back to what I had before the root, which is correct. I did see the downgraded version btw step 2 and 3.

So, i'm rooted and and it's all good. Now onto removing the bloatware!
[Thunderbolt Android Development] HolyGrail:
Any of you guys that got easyroot working, mind helping me help users for a little while? I'm having a hard time keeping up with posts. :)
[Thunderbolt Android Development] shanetrain:
Yes sir, CWM never looked so good. (in orange).

I will say this:

You've got to play with it a little, though, or at least I did .

Like I said, I did step 1 a number of times, kept getting the hash error on step 2, decided to just start at step 2, got it to take, and then I had to do step 3 twice.

I didn't do that initially with step 3, (wait for it to reboot). Rom Manager and SU were in the apps drawer, but I wasn't getting the SU popup.

I unplugged and re-plugged and hit step 3 again, and the phone rebooted, and everything is now good to go. :D
[Thunderbolt Android Development] Powell730:
just got mine working with very minimal issues.. its 445 am here but since you helped me im going to fight it out and help you as much as possible :)

thank you so much for whoever created that PDF file.. it helped sooo much!
[Thunderbolt Android Development] jr4000watts:
my dumb ass is having a hard time :(
[Thunderbolt Android Development] tommyxv:
What PDF file? I must of missed that....doesn't matter now.

Much thx to the dev and testers, and the member's who been very helpful in this thread.
[Thunderbolt Android Development] Powell730:
i think the last post on page 70
[Thunderbolt Android Development] HolyGrail:
Man, I'm happy you guys got it working, and can't tell you how many times over the testing period, I had to test the steps and having things break on me and give bug reports. Sucks @ss.

Powell good job. I was kind of worried that you were going to be trying for awhile to get it working. ;)
[Thunderbolt Android Development] Powell730:
where are you at?
[Thunderbolt Android Development] maizekidstill81:
I guess I dont have adb installed I see that nowhere

I dont even have the open command part anywhere
[Thunderbolt Android Development] HolyGrail:
Sorry man. My mistake. Right click and hold shift down in the package folder. You should see it then.

Man, i'm dumb.
[Thunderbolt Android Development] jr4000watts:
really wanna know?

i download the easy root files but cant seem to get it to install driver correctly from the HTC sync. im scared to hit step 1 knowing ADB is giving me **** right now.
[Thunderbolt Android Development] maizekidstill81:
Ok its there and my device shows
[Thunderbolt Android Development] Powell730:
haha! once i got my driver issue figured out it was smooth sailing.. it was very easy... i was just starting to get pretty fluent with my fascinate before this came out.. not quite the same but having experience with that def helped a bit.
[Thunderbolt Android Development] Powell730:
when you plug your phone into your computer do you get the installing drives window that comes up in the bottom right?
[Thunderbolt Android Development] maizekidstill81:
I still cannot get step three to take
[Thunderbolt Android Development] jr4000watts:
nope nothing
[Thunderbolt Android Development] Powell730:
are you getting anything on your phone?
[Thunderbolt Android Development] HolyGrail:
Well If it was happening to me, I would try (yes again) step 3 again a few more times.

And if that didn't work, I would redo step 2, because maybe that didn't take fully and could be keeping step 3 from working.

There is always, what I call: The unknown factor.

When that happens go back and retrace your steps.
[Thunderbolt Android Development] jr4000watts:
ok i restarted my pc connected my phone i had a small window pop up saying error installing drivers, and on my phone yes i get the "type of connection" and is on Charge only

EDIT: ok i tried re installing the files for the HTC syn and they all are going thru this time after a re boot of PC.
[Thunderbolt Android Development] maizekidstill81:
Yeah in step 2 when going through the process I did have to click it a few times

Thanks for all the help I will let you know if I got it
[Thunderbolt Android Development] HolyGrail:
Jr4000 I'm going to go back and read you're posts. So I can try and help you better.

Did you get a chance to check out that set up tutorial?
[Thunderbolt Android Development] jr4000watts:
clicked it and bad link. how would i know if my device is listed in the ADB?, cant seem to keep the command screen open just opens for a few seconds then closes. install all HTC syn driver and now says the device is installed.
[Thunderbolt Android Development] Powell730:
then your phone is ready to start at step 1.
[Thunderbolt Android Development] ruddymart:
no reboot for me in step 3. I see superuser app and rom manager but when I click on fix permissions pops-up an error message " An error occurred while attempting to run privileged commands". What should I do? And do I need to install adb or this method is without adb installation on pc?
[Thunderbolt Android Development] jr4000watts:
in Android SDK and AVD manager on virtual devices it shows nothing is connected, should i start even tho its not reading my device?
[Thunderbolt Android Development] Powell730:
holy: im running into an issue myself.. im not able to boot into CWM from RM because im getting the SU FC.. i thought i booted into CWM without RM by holding vol down whilte the phone boots up but that takes me to hboot then asks if i wanna start update again? is that where i need to be, just hit yet to start update?
[Thunderbolt Android Development] denpad2010:
hello i just tried a few minutes ago and a error message pop up saying something like the adb name is not correctly typed then i click ok and message pop up agin about 5 times then the applicacion started to push files well that what says,but is taking long is about 20 minutes now the phone is like nothing i mean is in home screen charging etc.... what i should do???:D
[Thunderbolt Android Development] dbzfanatic:
@james Even the updated one?

@cliff you're welcome

@denpad is it "adb is not recognized"? What is the exact error? Kill the program and run it again,see if it happens again and if it does tell me exactly what it says.

I updated this thread with a poll, please vote! I will also be updating the OP with the recommended driver if htc sync fails.
[Thunderbolt Android Development] sportadic22:
well guess i need to get affiliated with adb then again... have not used it since back in the day when i first got my droid 1... and rooted it. gottaa do some research and get files ha
[Thunderbolt Android Development] dbzfanatic:
The info you need on setting up adb is already here in the thread so really all you need to do is download the sdk.
[Thunderbolt Android Development] jamestx10:
I have ADB in my PATH. I tried the exe that came in the first 800 meg file. Nadda. Tried the No ADB needed.zip and nadda. Tried the ADB needed.zip and bam it is working. Starting step 3 now.
[Thunderbolt Android Development] denpad2010:
Thats the message and I click ok and then pop up again

The message pop up several times then program say pushing files....

SENT FROM MY HTC THUNDERBOLT
[Thunderbolt Android Development] jr4000watts:
still a bit confused on this works. i finally download the Android SDK last night downloaded and installed all files. but not sure which file to install from your OP. TB rooting has giving me a big headache lately.
[Thunderbolt Android Development] dbzfanatic:
@denpad you're trying to run directly from the rar archive, you can't do that you have to extract the files first.

@jr4000 if you already have the sdk download the one that says "adb needed" or however i phrased it in the OP, the MU link not the exe. There's info on how to setup adb in your PATH if you don't already have it that way.
[Thunderbolt Android Development] ipawd1:
I'm waiting for Z4root, or SOMETHING
[Thunderbolt Android Development] jamestx10:
I got to:

Mounting /system

Copying su and changing permissions.

Reboot 2 or 3 times then open RomManager and intall the Thunderbolt recovery by clicking "Flash ClockworkMod Recovery".

I then cold booted the phone 2 times. Opened Rom Manager and it could not find SU.
[Thunderbolt Android Development] frodsteamin2:
@dbzfanatic thanks for your patience and knowledge, the install Path instructions in this thread helped correctly setup adb and the htc sync drivers helped recognize the device and i proceeded to step one and it began pushing the files onto phone after about 5 minutes "choose the bootloader option" showed in the exe up but phone didnt reboot into bootloader. i will kill the exe and try again. Note: i used the adb needed file
[Thunderbolt Android Development] madzozs:
Downloaded the program and both .exe's just in case. Tried to run after unpackaging the .rar and it hung after step 1 where it says,

It sat for a few minutes and I closed out the program. Tried the no adb needed, and the adb needed exe and they both sit at that part with nothing changing on my phone at all.
[Thunderbolt Android Development] denpad2010:
ok i did put on desktop realy is just one file the exe program right, well i did again the same result,i downloade the 358kb i need download anything else???
[Thunderbolt Android Development] dbzfanatic:
You need to download the megaupload files, the 800MB files.
[Thunderbolt Android Development] denpad2010:
hahaha thanks man i feel like a stupid lol i didnt download, i will do it now thanks man
[Thunderbolt Android Development] dbzfanatic:
@madzoz with the adb needed one you actually need adb in your PATH, do you have it there?

@james sorry, try running step 3 a coule times in a row, see if that helps then do the reboots. also are superuser and RomManager in your app drawer or did you get them from the market?

@everyone else

I'm very sleepy, i am going to go to sleep. I will resume help when I wake up. I know what's going on but not why so i'm taking stabs in the dark as to how to fix it.
[Thunderbolt Android Development] dave0373:
Lol, the file take forever to download.
[Thunderbolt Android Development] frodsteamin2:
I have successfully voided my warranty and yes that is a good thing.

After being stuck and not loading into bootloader, i killed the needed adb exe program, restarted and after waiting exactly 5 minutes on step 1, I am in bootloader and its loading up all the goodies.
[Thunderbolt Android Development] jamestx10:
SuperUser app is there and opens but when opening rommanager it says "you must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use google to find instructions for rooting your phone.

Rom manager and superuser where in the app drawer I did not get them from the market
[Thunderbolt Android Development] rckeystone:
Much deserved sleep our friend. Thanks for your work and time.
[Thunderbolt Android Development] Powell730:
the program just will not reboot your phone if its not reading it properly.. i dont see why it would hurt.
[Thunderbolt Android Development] HolyGrail:
Try step 3 again,

if not, redo step 2
[Thunderbolt Android Development] HolyGrail:
Checking.....

Ok did you put on the lastest Clock work recovery? If not, don't. They posted it had issues. I think the latest is 2.4, put on 2.2 instead. I just tried to reboot into recovery from rm and it worked fine.
[Thunderbolt Android Development] gsxraddict:
If you press number 1 it will say reading device if no device shows up then its no detecting HTC sync will say its not responding regardless
[Thunderbolt Android Development] jr4000watts:
clicked step 1 pushing files
[Thunderbolt Android Development] Powell730:
i did but i will down grade.. but my problem is that i am getting force closes everytime SU requests permission.. so im trying to flash the .zip in another thread that fixes SU.. im not able to use RM to boot into CWM since it asks for permission first. so i have to boot manually which i guess im not sure how to do it.
[Thunderbolt Android Development] HolyGrail:
By the way, if your rooted, don't forget to delete PG05IMG.zip from your SD CARD.
[Thunderbolt Android Development] maizekidstill81:
Still nothing on step three . I even wen through and re did the whole thing over

I am lost
[Thunderbolt Android Development] HolyGrail:
Did you run fix permissions? You needed to do that before you can use rom manager.
[Thunderbolt Android Development] Powell730:
same problem.. cant do it due to it requesting permission.
[Thunderbolt Android Development] HolyGrail:
I don't understand. When you go into fix permissions, does it come up with a request from superuser asking if you want permissions? Or does it come up with an error?
[Thunderbolt Android Development] maizekidstill81:
how do u get 2.2 version?
[Thunderbolt Android Development] Powell730:
well it trys to bring it up asking for permission thats where i get the force close. i have a .zip file that i can flash via CWM that will correct this issue. I just need help getting into CWM manually... like as the phone boots up hold vol down right?
[Thunderbolt Android Development] Powell730:
clockworkmod 2.2?
[Thunderbolt Android Development] jr4000watts:
ok it loaded into bootloader said wrong img and all, but still whent thru now asking me to update vol up yes and vol down no? sooo..... even tho it said wrong img
[Thunderbolt Android Development] Powell730:
vol up.. allow it.. youre good.
[Thunderbolt Android Development] HolyGrail:
Maize, I'm trying to think of of a way. Do me a favor and check fix permission in RM
[Thunderbolt Android Development] jr4000watts:
rebooted into bootloader again and said no image and no image or wrong image but still loading?
[Thunderbolt Android Development] HolyGrail:
Scroll down in RM, and you'll see "All Clockworkmod Recoveries". Has all older versions.
[Thunderbolt Android Development] Powell730:
yeah, mine said that everytime.
[Thunderbolt Android Development] HolyGrail:
Do you have your plug still in the phone? If so that could be the reason for the force close.
[Thunderbolt Android Development] Powell730:
nope its not. do you know how to boot into CWM manually?
[Thunderbolt Android Development] maizekidstill81:
got it I think everything is working good. Still need to do a backup
[Thunderbolt Android Development] HolyGrail:
Sorry Powell, I don't. I don't understand why its force closing on you when you try and fix permissions. In rm will it let you put on a previous CWR?
[Thunderbolt Android Development] Powell730:
@Holy: i figured it out. you do hold vol down while the phone boots, my problem was that i still had that .img file on my SD card that the root pushes and it was trying to load that everytime. deleted it and then i was able to select recovery.

@jr4000: if you go to page 70 and scroll to the last post there is a very detailed PDF that will take you exactly step by step and it is very helpful.
[Thunderbolt Android Development] HolyGrail:
LOL, That's why I scream it out on the older post to delete it, to stop future problems. Nice you got it working.
[Thunderbolt Android Development] jr4000watts:
reading the pdf file now and already on step 2 updating waiting to reboot wish me luck cause i heard step 3 has more issues.

read step 3 and says its going to push files thru ADB? i have it on my PC and installed all the files avail, would i be ok? even if time i try to open ADB it closed right away?
[Thunderbolt Android Development] Powell730:
I didn't have a single problem with step 3. You'll be fine
[Thunderbolt Android Development] jr4000watts:
hope so step 2 is down rebooted into clock work recovery, click reboot to phone, so lets see how this goes for step 3, skipping google, re enabling debug and clicking step 3. ..........nervous........ lol
[Thunderbolt Android Development] Tlowery88:
it was a little quirky, took some plugging/unplugging and some restarting the program a few times but i have root and have successfully done a backup in CWM 2.2 so thanks to the OP and the community for all the input and hard work
[Thunderbolt Android Development] jr4000watts:
boy has rooted finally. fixing permissions now, quick question am i supoused to delete something now? a ZIP? just wanna make sure. so there is this rom i want to install just released 24 for the TB, is it safe to make back up, clear and whip and install from sd card as every other roms we have used? or ADB the only way to flash roms for now on the TB.
[Thunderbolt Android Development] dbzfanatic:
Yeah you need to delete the PG05IMG.zip file so you don't reflash when you reboot.
[Thunderbolt Android Development] jr4000watts:
well good morning lol while you were asleep i finally rooted at 530am!! ha but yea installed root explore deleted the zip, now making a back up and hopefully loading up the senseless rom see how that goes.
[Thunderbolt Android Development] dbzfanatic:
Glad you finally got root. Sorry about all the delays (like sleep) but at least this version is out.
[Thunderbolt Android Development] HolyGrail:
Well look who arrived at the party. :D Can I please go to sleep now?
[Thunderbolt Android Development] dbzfanatic:
Lol yeah sorry I thought you'd be asleep already. Thanks for the help you've got 3 hours before we start testing the two-step and one-click :P
[Thunderbolt Android Development] jr4000watts:
no worries bro you needed the sleep and this release actually worked without a flaw, got a little worried when in to boot it was saying no img or wrong img but still went thru. awesome job will be donating soon.
[Thunderbolt Android Development] HolyGrail:
Sweet. Goodnight everyone. Don't drink and root! :cool:
[Thunderbolt Android Development] jr4000watts:
lol too late i did mine buzzed
[Thunderbolt Android Development] bigbarrel:
Thanks to dbzfanatic I've got root and superuser. I deleted the .img file and just downgraded CW Recovery from 2.4 to 2.2. When I run the Fix Permissions, it gives me the privileged commands error and FC's. I know people have talked about this but I haven't found a solution. Any suggestions?
[Thunderbolt Android Development] dbzfanatic:
You're using the updated file right? Sometimes step 3 doesn't take (known bug, see OP) so you need to press step 3 twice to get it to take. It seems to be a glitch with adb recognizing the phone. Remember to turn usb debugging back on and unplug/replug your phone before starting step 3.
[Thunderbolt Android Development] bigbarrel:
Yes, I did step 3 several times and I got Superuser and ROM Manager to show up.
[Thunderbolt Android Development] dbzfanatic:
You didn't answer my first (and most important) question, are you using the updated files? When did you download them?
[Thunderbolt Android Development] bigbarrel:
Thursday. What updated files are you referring to?
[Thunderbolt Android Development] dbzfanatic:
Nevermind, I need a bit of info. Right click on the rooter file then click properties, then go to the details tab and let me know what version it is please.
[Thunderbolt Android Development] bigbarrel:
Version: 1.3.5.0
[Thunderbolt Android Development] dbzfanatic:
You have an older version of the files and you need to re-download them from the OP, that's why it isn't working. Give me about five minutes and I'll attach just the updated exe for people with older files like yourself.

Edit: added.
[Thunderbolt Android Development] bigbarrel:
Do I just download the .exe that you added and run it? Any other steps?
[Thunderbolt Android Development] oneders65:
What Windows OS works better with this program ? Has anyone made a YouTube video of your program?
[Thunderbolt Android Development] dbzfanatic:
@bigbarrel Just download it, extract it to the folder with the other files,and run step 3 once or maybe twice for good measure. You should be fine then.

@oneders No, no one has made a video yet and as for OS it should work with all of them from XP to 7.
[Thunderbolt Android Development] bigbarrel:
Thanks a lot.
[Thunderbolt Android Development] jawonder:
I had the older no ADB file does update have a no ADB or it's just ADB ? . Are the files at post #1 the updated files ? . What do i need to do now ?. I need some Cyanogen for my headaches lol .
[Thunderbolt Android Development] dbzfanatic:
This is technically a no-adb version but if you have adb it won't hurt. I tried to make this as universal as possible. Yes the files in the first post are the updated ones, you need to download the full archive if you haven't gotten clockwork flashed yet. All you need to do after you download the archive is extract it somewhere and start from step 1 but I suggest if you tried rooting before that you return to stock by flashing the unroot image file to ensure that you encounter as few errors as possible.
[Thunderbolt Android Development] bigbarrel:
dbz, I'm still getting the same error in CWM when running Fix Permissions. Do I need to uninstall ROM Manager and reinstall it? What do you think?
[Thunderbolt Android Development] dbzfanatic:
Did you turn usb debugging back on and unplug/replug your phone then run through step 3? If so just download the full archive and start from step 2.
[Thunderbolt Android Development] bigbarrel:
Usb debugging was on before I ran step 3. I downloaded the new rooter.exe, extracted to my folder and then launched it with my phone already connected and hit step 3. The first time nothing happened. The second time my phone rebooted. Both times, I went to ROM Manager and got the same error when running the Fix Permissions.

If I start from step 2 again is this going to wipe my phone again?
[Thunderbolt Android Development] dbzfanatic:
Yes it will wipe your phone again. If you would prefer just PM me and I can help you get things setup but the newer version of the program does not have these bugs (except for the aforementioned step 3 which doesn't happen all the time,just sometimes).