oh wait i think i understand now, i totally passed it up before. after running ./adb shell /data/local/busybox md5sum /data/local/misc.img my check sum is exactly the same. i guess it wasn't before horray
[Mac Procedure]: How to Root the HTC Thunderbolt
- Thread starter Cory Streater
- Start date
- Status
Thanks for all the hard work. Worked perfectly for me first time through!! Just have to follow the directions to the letter.
Ok, tried it tonight....again. This time I couldn't even get it to recognize my phone. Please don't go any more complicated. This was bad enough.
Ok from what I can tell, and im not terribly experienced, is you haven't gone too far astray. Hopefully I can lend some tips from some trouble shooting I went through today.
I believe that this output you get in the terminal has only do with entering something wrong or you being in the wrong directory. I know I copy and pasted a couple of times while doing this and left in the $ before the commands. I think leaving that in will give the same kind of "no such file or directory" error. Now I don't know how, but you might have also gotten out of the directory of android-sdk and its sub-folder, tools that contains adb. I think this could be likely if you left the terminal before/after/during the downloading of the new PG05IMG.zip file and placing it to your SD card. But if you leave terminal anytime just do these 4 commands again, "$ cd .. $ cd .. $ cd and* $ cd tools", same as listed below. The computer not recognizing the ./adb devices command would not have anything to do with incorrectly downloading and saving the new PG05IMG file to your sd card.
Since it sounds like you are trying to start over make sure phone is in debugging and....
you could do a test: (without the $ in front of each line)
$ cd ..
$ cd ..
$ cd and*
$ cd tools
$ ./adb devices
( try this first without the T-bolt plugged in and then again with, just to check if your android-sdk is working as it should )
and if the ./adb command is not recognized when you have no t-bolt in, then you should try re-downloading and installing android-sdk-mac_x86.zip as given in the very first step and start again from there.
if ./adb is recognized without t-bolt as a command but not when it is plugged in, then im just as stumped as you and hopefully a tech wizard will be able to jump in and make good things happen.
Lastly i had trouble with an improperly downloaded pd05img file, so starting over with fresh downloads can make the process seem like a piece o cake again because there hopefully wont be anymore glitches
I believe that this output you get in the terminal has only do with entering something wrong or you being in the wrong directory. I know I copy and pasted a couple of times while doing this and left in the $ before the commands. I think leaving that in will give the same kind of "no such file or directory" error. Now I don't know how, but you might have also gotten out of the directory of android-sdk and its sub-folder, tools that contains adb. I think this could be likely if you left the terminal before/after/during the downloading of the new PG05IMG.zip file and placing it to your SD card. But if you leave terminal anytime just do these 4 commands again, "$ cd .. $ cd .. $ cd and* $ cd tools", same as listed below. The computer not recognizing the ./adb devices command would not have anything to do with incorrectly downloading and saving the new PG05IMG file to your sd card.
Ok, tried it tonight....again. This time I couldn't even get it to recognize my phone. Please don't go any more complicated. This was bad enough.
Since it sounds like you are trying to start over make sure phone is in debugging and....
you could do a test: (without the $ in front of each line)
$ cd ..
$ cd ..
$ cd and*
$ cd tools
$ ./adb devices
( try this first without the T-bolt plugged in and then again with, just to check if your android-sdk is working as it should )
and if the ./adb command is not recognized when you have no t-bolt in, then you should try re-downloading and installing android-sdk-mac_x86.zip as given in the very first step and start again from there.
if ./adb is recognized without t-bolt as a command but not when it is plugged in, then im just as stumped as you and hopefully a tech wizard will be able to jump in and make good things happen.
Lastly i had trouble with an improperly downloaded pd05img file, so starting over with fresh downloads can make the process seem like a piece o cake again because there hopefully wont be anymore glitches
Ok....I'll try downloading everything again and see what happens.Ok from what I can tell, and im not terribly experienced, is you haven't gone too far astray. Hopefully I can lend some tips from some trouble shooting I went through today.
I believe that this output you get in the terminal has only do with entering something wrong or you being in the wrong directory. I know I copy and pasted a couple of times while doing this and left in the $ before the commands. I think leaving that in will give the same kind of "no such file or directory" error. Now I don't know how, but you might have also gotten out of the directory of android-sdk and its sub-folder, tools that contains adb. I think this could be likely if you left the terminal before/after/during the downloading of the new PG05IMG.zip file and placing it to your SD card. But if you leave terminal anytime just do these 4 commands again, "$ cd .. $ cd .. $ cd and* $ cd tools", same as listed below. The computer not recognizing the ./adb devices command would not have anything to do with incorrectly downloading and saving the new PG05IMG file to your sd card.
Since it sounds like you are trying to start over make sure phone is in debugging and....
you could do a test: (without the $ in front of each line)
$ cd ..
$ cd ..
$ cd and*
$ cd tools
$ ./adb devices
( try this first without the T-bolt plugged in and then again with, just to check if your android-sdk is working as it should )
and if the ./adb command is not recognized when you have no t-bolt in, then you should try re-downloading and installing android-sdk-mac_x86.zip as given in the very first step and start again from there.
if ./adb is recognized without t-bolt as a command but not when it is plugged in, then im just as stumped as you and hopefully a tech wizard will be able to jump in and make good things happen.
Lastly i had trouble with an improperly downloaded pd05img file, so starting over with fresh downloads can make the process seem like a piece o cake again because there hopefully wont be anymore glitches
IT WORKED!!!!!!!!! I'M ROOTED!!!!!!!!!! WOO HOO!
Now to see about all the cool stuff I can do with a rooted TB.
Now to see about all the cool stuff I can do with a rooted TB.
Good to hear it worked
.... Now to get rid of that nasty bloatware. I saw once that was disabled the phone could start to live up to its name again
.... Now to get rid of that nasty bloatware. I saw once that was disabled the phone could start to live up to its name againBloatware....gone. Well....moved. Now to figure out what else I can do.
Gingerbread ROM
Hi, I've followed the guide step by step but I cannot get my TB to show up under devices attached.
This is my first post but these instructions are EXTREMELY easy to follow, but my TB won't show up in the Terminal yet it mounts to the computer and i see it on the desktop. What's wrong?? USB debugging is on and it's set to Disk Drive already...sorry for the noob question...
Sorry if i anger anyone with my noob problem...but after putting the phone in bootloader the first time, the phone never asks me if i want to apply update. It just takes me back to the screen with Fastboot selected. What am i doing wrong? No problem besides that. I reformatted my memory card also, idk if that makes a difference, and it still did the same thing.
To everyone who is having issues with seeing the device after ./adb devices ---- if you have easytether installed you need to do this:
Do not follow this advice if you are not a software developer who uses the Android SDK on Mac. Otherwise run "sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext" to unload the EasyTether driver manually. Load it again with kextload when/if necessary.
Do not follow this advice if you are not a software developer who uses the Android SDK on Mac. Otherwise run "sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext" to unload the EasyTether driver manually. Load it again with kextload when/if necessary.
First time rooting and the procedure went flawless. Thanks for the instructions it is greatly appreciated.
fubaracing7374
Well-known member
- Oct 26, 2009
- 135
- 2
- 0
I rooted my phone and everything went fine but now my wifi and regular internet connection is not working well. Do you have a way to unroot and put it back to factory settings? I see you have a post for unrooting using a PC but I would like to unroot using a mac as I did to root my phone using this post. Hope you can help. Thanks
Last edited:
- Status
Similar threads
Trending Posts
-
-
-
-
-
Question How to factory reset without Samsung account android 15
- Started by postald
- Replies: 6
Facebook
Twitter
Instagram