yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Cmotion:
OK, so I figured out how to get adb on there, now I have this problem. So I typed cd and then dragged the platform-tools folder into the terminal, it looks like this:

cd /Users/christophermoran/android-sdk-mac_x86/platform-tools/

then when I enter ./adb /push psneuter /data/local/

it doesn't give me the line saying "2106 KB/s (58731 bytes in 0271s)" or whatever feedback you're supposed to get. Instead, it just says:

christopher-morans-computer:~/android-sdk-mac_x86/platform-tools christophermoran$

I feel like if I get past this initial hiccup I should be OK. I've tried reading up on adb and just can't figure out what's going on. Any help would be much appreciated.
[Thunderbolt Android Development] bmcclure937:
cd into the correct directory and type

ls -la

This will list the contents of the directory. I want to make sure you are in the correct directory before you execute any commands.

If ADB is listed in platform-tools then simply enter the following:

./adb devices

This will list your device if it is attached and recognized.

From here we can move forward with the actual rooting process!
[Thunderbolt Android Development] Cmotion:
Thanks for the help, I was at the andirc thunderbolt root help chat site today for a few hours, tried a bunch of things, none of them worked. Went home, tried on my girlfriend's Mac, eezy peezy... I think my older version of Mac OS (10.4.11) just has a really hard time with this stuff. Great tutorial and again, thanks for the help! (also obviously thanks to jcase and all the amazing developers that managed to get us root) :D
[Thunderbolt Android Development] jlevy73:
@OP: This is a very good guide indeed. Only thing I would add is that when the phone reboots after flashing the Rom that they must re-enable debugging otherwise the device will not be recognized by adb.
[Thunderbolt Android Development] IISiDeK1CKII:
Touche. I don't know why I forgot to include that... I think it's because I thought it was common knowledge. I'll fix that now.

No problem man. I do what I can. Glad this helped people.
[Thunderbolt Android Development] :
Great writeup. Worked perfectly for me. The only question I have is at the very end you say flash Thunderbolt recovery, what is that? Thanks!!!
[Thunderbolt Android Development] IISiDeK1CKII:
I posted a jpeg with a red arrow pointing to it. If something goes horrendously wrong and you mess up your phone, you can recover it using CWM. All you need is either a. a backup on your phone or b. a new rom on your sd card.
[Thunderbolt Android Development] :
So "Flash ClockworkMod Recovery" (in ROM Manager) is the same as "Flash Thunderbolt Recovery" (from your instructions)? Or are you saying we should "Backup Current ROM"? Thanks!
[Thunderbolt Android Development] IISiDeK1CKII:
You *need* to press "Flash ClockworkMod Recovery", which is in fact the same as "Flash Thunderbolt Recover". When you press flash CWM recovery the first time, it'll tell you the recovery is for HTC Thunderbolt, just let it run, allow Superuser and ta-da!

I also strongly recommend you backup current ROM, jic something goes wrong.
[Thunderbolt Android Development] SteveDusa:
I just want to thank everyone who made the root possible!

Followed the guide and was able to root my shiny new TBolt in one shot!
[Thunderbolt Android Development] IISiDeK1CKII:
Glad I could help simplify and expedite things. Enjoy your new phone!
[Thunderbolt Android Development] enyalius:
Thanks for the writeup!

I am running into an "issue", though, and was hoping you guys can help me out. I follow all of the steps, but once I reboot into the bootloader (setp 4), I hit the power button while "bootloader" is selected, it goes through its thing, which looks like this:

HBOOT (white text blue background)

SD Checking...

Loading...[PG05DIAG.zip]

No image!

Loading...[PG05DIAG.nbh]

No image or wrong image!

Loading...[PG05IMG.zip]

All the text above (except for HBOOT) is green, and there is a blue bar working from top to bottom in the top right quarter of the screen.

After, it says:

HBOOT

Checking..[PG05IMG.zip]

Again, the text is green, but this time it has a yellow/golden progress bar in the top right quarter of the screen.

After that, I am presented with a menu that looks like this:

HBOOT (hilighted in blue)

<VOL UP> to previous item

<VOL DOWN> to next item

<POWER> to select

FASTBOOT (white text hilighted in blue)

RECOVERY (green text)

FACTORY RESET (red text)

SIMLOCK (blue text)

HBOOT USB (olive text)

IMAGE CRC (black text)

At no point was I asked to upgrade, as the step says I should have, and I'm at a loss as to what I'm doing wrong (yes, the image file is on my SD card). I normally choose "FASTBOOT" and then "REBOOT", but nothing seems to have changed on my phone. Any advice would be appreciated.

Thanks!
[Thunderbolt Android Development] enyalius:
EDIT:

OK, I guess I'm more of a n00b than I thought (or, I shouldn't have been trying to rush this during my lunch break :p ).

Anyway, it looks like I was trying to use the PG05IMG_downgrade.zip file for step four instead of the very, very long named file listed first in your downloads section. Oops...
[Thunderbolt Android Development] IISiDeK1CKII:
@enyalius: Did you figure it out or not? LOL, You didn't specify.
[Thunderbolt Android Development] cr125rider329:
Main Version is older?

After loading the first zip and trying to flash(THE REALLY LONG NAMED ONE) i get an error that Reads "Main Version is older!""Update Fail!""Press <power> to reboot"

Any idea's on what could cause that?
[Thunderbolt Android Development] IISiDeK1CKII:
Did you rename it to PG015IMG.zip?
[Thunderbolt Android Development] Zshazz:
If the OP's suggestion doesn't work, you absolutely did the dd misc.img part of step 3, right?

That's what allow you to flash older firmwares (such as the engineering build included), IIRC.
[Thunderbolt Android Development] contractcooker:
This should be a sticky. i know that most people probably use windows but it's great to have a guide for OS X.
[Thunderbolt Android Development] IISiDeK1CKII:
Meh, my guide really just a small modification of jcase's original thread. I think while helpful, doesn't really mean it needs a sticky. I'm all up for one though :D
[Thunderbolt Android Development] longjas:
Rooted!

I love the forums on xda! I finally have a rooted thunderbolt. Thank you so much for all the hard work everyone has spent putting this walk through together. Now to decide what rom to load! Hopefully cm7 comes out for the Thunderbolt soon. Loved that on my incredible.
[Thunderbolt Android Development] IISiDeK1CKII:
Glad we could all be of assistance. Enjoy your phone!
[Thunderbolt Android Development] djkeller3:
I don't know what I'm doing wrong here. I have experience rooting my OG Droid, Droid X, several Incredibles and a Fascinate. I'm not a programmer and have never used ADB before, and until the T-Bolt came out, I had never heard of it.

I followed the directions in the OP to the letter. ADB is apparently not finding the ADB files, and it's not finding my T-Bolt either.

As per the instructions, I placed the unzipped Android_SDK_Macx86 file on my desktop. I downloaded the 3 files and placed the RUU Verizon zip and the Exploits zip into the Platforms-Tools folder. I copied that folder and drug it into the Terminal and got the green dot with the + in the middle.

When I start the copy and paste process, here's what I get (from my terminal):

Last login: Sat Apr 9 14:33:35 on ttys000

david-kellers-macbook-pro:~ dakeller3$ /Users/dakeller3/Desktop/android-sdk-mac_x86/platform-tools ./adb push psneuter /data/local/

-bash: /Users/dakeller3/Desktop/android-sdk-mac_x86/platform-tools: is a directory

david-kellers-macbook-pro:~ dakeller3$ ./adb push busybox /data/local/

-bash: ./adb: No such file or directory

david-kellers-macbook-pro:~ dakeller3$

Am I missing something?

If I type in ./adb devices, I get:

Last login: Sat Apr 9 15:26:35 on ttys001

david-kellers-macbook-pro:~ dakeller3$ /Users/dakeller3/Desktop/android-sdk-mac_x86/platform-tools ./adb devices

-bash: /Users/dakeller3/Desktop/android-sdk-mac_x86/platform-tools: is a directory

david-kellers-macbook-pro:~ dakeller3$

Something isn't working. Help!! :confused:
[Thunderbolt Android Development] IISiDeK1CKII:
To make sure:

1. Make sure you take the files out of the exploit folder and put them in the platform-tools folder.

2. type cd before dragging to the terminal window

3. press enter after changing directories. What you are doing is just listing a directory and attaching a command to the end.

You can't see what devices are attached because you still aren't in the platform tools folder. Try what I said (type cd then drag the platform tools to terminal window) and post back and let me know if it works.
[Thunderbolt Android Development] djkeller3:
OMG!! I'm getting somewhere! Thank you!! I'll let you know when I'm done!! Thank you so much!!!
[Thunderbolt Android Development] IISiDeK1CKII:
NP man, it's the easy things we overlook the most.
[Thunderbolt Android Development] djkeller3:
I'm at the part where I get kicked out of abd, and I think it resetarted, but I'm not sure how to do this part:

You will now be kicked out of adb, and adb will restart as root. Let’s confirm the md5 of misc.img:

./adb shell

At this point, the shell should display "#".

I haven't done anything since getting kicked out of abd. I don't see the "#".
[Thunderbolt Android Development] djkeller3:
Ok, I get it... I got the "#". All is good.
[Thunderbolt Android Development] djkeller3:
Question... one of the files I downloaded is already named PG05IMG.zip. Can I copy this one to my sd card, or do I still need to rename the RUU(long name) file and use it instead?
[Thunderbolt Android Development] gadsden:
You need both. If you downloaded the files in this thread, the names have been changed a little from the original file names. You need to flash the downgrade .zip first. The custom RUU is the second flash in the process. If you've gotten them mixed up a little bit, check the md5sum to make sure you're using the right one at the right step. It's a good idea to check the md5sum before you even get started, anyway. That way you know you have good files and you don't have to worry about downloading anything after you start.
[Thunderbolt Android Development] IISiDeK1CKII:
You need to rename RUU_Mecha_VERIZON_WWE_1.03.605.10_Radio_1.02.00.01 03_2r_NV_8k_1.37_9k_1.52_release_165253 as PG05IMG.zip. The other zip is a custom RUU that you need to install later. (the former RUU is a downgrade, you NEED TO downgrade. Make sure to check your MD5 sums...)
[Thunderbolt Android Development] IISiDeK1CKII:
When you are finished, please let me know if there is anything I can do to make the instructions more clear.
[Thunderbolt Android Development] djkeller3:
Okay... I renamed the file as you said. Got into Hboot. I clicked yes to flash, or so I think, as soon as I touched my lower volume rocker the yes option went away and it told me to hit power to reboot, which I did, and it was not what I would call a long one. When it booted up, my phone desktop was just as it was before flashing. I rebooted again as per instructions, and went in to enable debugging, but it was still enabled.

I'm wondering if the downgrade flashed. Is there a way I can check before I go any further? If it did not, what do I need to do to reflash? Thanks!!

Software number is 1.12.605.6

Baseband is 1.16.00.0223r
[Thunderbolt Android Development] gadsden:
I'm pretty sure the option to flash is volume UP. If you pushed DOWN, it probably canceled the flash.
[Thunderbolt Android Development] gadsden:
It seems you have added in the EXIT command that was missing when I rooted. Other than that, it seems like the steps 4 and 5 are not the same as the original instructions from jcase. I don't know if that was on purpose, but it makes it difficult to get help from people who haven't followed this set of instructions, because their step 4 and 5 aren't the same as these.
[Thunderbolt Android Development] IISiDeK1CKII:
It's because your phone didn't wipe. I know for certain it didn't flash. Make sure all the files pushed and make sure the md5 sum is right and flash the renamed RUU again.
[Thunderbolt Android Development] djkeller3:
Okay... that's cool. Next question is do I need to start all over or can I reboot into hboot and pick up at the point of update?
[Thunderbolt Android Development] IISiDeK1CKII:
as long as you pushed the misc.img, busybox and psneuter, yes, you can go straight back into hboot.

@gadsden: I haven't changed instructions since you rooted, only added pics. I think you might have overlooked something. Alot of my instructions are different from jcase's, jut the setup though, nothing else.
[Thunderbolt Android Development] tekhna:
Has anyone here tried the easy root option for OS X yet?

http://xdaforums.com/showthread.php?t=1027836

http://www.fryetech.com/thunderbolt.php
[Thunderbolt Android Development] IISiDeK1CKII:
I don't trust these. There is no source and there are no credits. I don't believe for one second this guy compiled this and made an exploit without any assistance from ANYONE else.
[Thunderbolt Android Development] tekhna:
I'm inclined your way, but what is it that you don't trust? That it's not his own work, or that they're not clean, no malware?
[Thunderbolt Android Development] IISiDeK1CKII:
I'm not telling anyone to choose my way not his. It bothers me that he is posting this as his own work, when I can almost guarantee he is using other people's work as his own. The stuff is most certainly clean, but he did not gain root on his own.
[Thunderbolt Android Development] djkeller3:
Another question, sorry guys... I'm almost done.

I flashed the custom PG05IMG which upgraded me to the release firmware with S-Off.

I then ran: "./adb reboot bootloader" as per the instructions. Hboot came up but nothing was happening. Bootloader was highlighted, so I selected it and all it did was load PG0510000 and is now asking me if I want to update. I presume the answer is NO, but need confirmation that this is correct.

Did the bootloader flash when HBoot came up? The instructions made it sound like it would be an automatic flash.
[Thunderbolt Android Development] gadsden:
@IISiDeK1CKII- If you haven't changed anything, maybe I just missed the exit command. Or perhaps you are looking back to the second TB I rooted. Anyway, if the exit command was never missing, then I just overlooked it. Oops!

I think this is a little bit confusing here. I think the adb reboot bootloader command you are running IS the one that you run to flash the custom RUU. It just tells you to flash in the instructions, and the reboot bootloader command is written after it tells you what you're doing. It's confusing, IISiDeK1CKII, unless I'm mistaken again about what I'm looking at.
[Thunderbolt Android Development] djkeller3:
Feel like an idiot. I backed out of the above and ran the command again and this time with HBoot came up I saw that "Reboot Bootloader" was an option, so that's what I did. This could be spelled out in the instructions for newbies like me who need to be told to toggle down to "reboot bootloader"... sorry!
[Thunderbolt Android Development] djkeller3:
One last final question. Here is the very last part:

"The following will remount /system and set up SU:

Code:

./adb shell

mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system

/data/local/busybox cp /data/local/su /system/xbin/su

chown 0:0 /system/xbin/su

chmod 6755 /system/xbin/su"

The first line includes the ./adb. None of the other lines do. I entered them as shown above. After each of the 4 without the ./adb, I got a "#". Is this correct? Or should I have used ./adb to preface the other 4 commands?
[Thunderbolt Android Development] djkeller3:
Everything seems to have worked out. I downloaded ROM Manager and flashed ClockworkMod Recovery and got SuperUser permissions with no problem whatsoever, so that MUST mean that I NOW HAVE A ROOTED THUNDERBOLT!!!!!!!!!

I AM SO FRIGGIN HAPPY - I CANNOT FIND THE WORDS TO EXPRESS IT!!!!

Finally, I can have a Thunderbolt that is truly MINE!!!

All I can say is that the ROOTED COMMUNITY is AWESOME!! The resource and expertise that you all bring to smart-phones is immeasurable and invaluable. I am SO PROUD OF THIS COMMUNITY and of the willingness of the many VERY SMART PEOPLE here who help those who are willing to help themselves.

THANK YOU, THANK YOU, THANK YOU!! And to the Original Poster, YOU ARE AWESOME!!!
[Thunderbolt Android Development] IISiDeK1CKII:
Glad I could help man. It's things like this why I made this, I knew I could make people happy. It feels great to root my own device, but feels even better when you make someone else's day.

Enjoy your thunderbolt! I am sure your posts will help someone else out now!
[Thunderbolt Android Development] tekhna:
Right, of course. But he did find a slick way of packaging it. He should, of course, give credit where it's due.
[Thunderbolt Android Development] IISiDeK1CKII:
Correct. Simplifying someone's method is awesome, but not giving credit where credit is due is wrong.

I refuse to use his method or refer it to anyone based on that. There have been people banned for the same thing, I am d/l his package to see exactly what is included and I will let the proper people know to have this dealt with. I simply cannot stand when people take other people's work as their own. And all it would take is a quick "these people helped" and that's it.

Our developer community is full of people who are already substantially unappreciated by the majority of the users here on this site. People ***** and moan when updates take too long and then download something and complain about any problem, user error or not, all day. It's a slippery slope we are on, eventually the devs will have enough and we will be stuck with carrier crap on our phones, and that day, everyone will realize hindsight is 20/20.

So, long story (long, apocalyptic story at that) short, give FREAKING credit where it's due and stop complaining to devs. If you have nothing nice to say, then don't freaking say it.

/rant
[Thunderbolt Android Development] kawfeegod:
When flashing the second RUU, can it be any custom rom or does it need to be the one indicated in the instructions?
[Thunderbolt Android Development] IISiDeK1CKII:
It needs to be the one in the directions. Not sure if you could use another one, but why risk it?
[Thunderbolt Android Development] kawfeegod:
Cool, is there a guide somewhere on flashing custom ROMS/kernels? Yours was stellar on rooting. Had a couple of issues, but reading solved them.
[Thunderbolt Android Development] IISiDeK1CKII:
I took these from here, the tesla coil ROM page.

Install:

make sure you have root and Clockwork recovery installed

-boot into recovery via ROM Manager.

-select "wipe data/factory reset"

-select "Yes -- delete all data"

-go back "the back softkey"

-select "install zip from sdcard"

-select "choose zip from sdcard"

-find and select newROM.zip

-reboot
[Thunderbolt Android Development] tekhna:
Well I decided to do it with ADB, but I can't even open ADB. It just opens a help file and spits me out into "process completed." Any clues?
[Thunderbolt Android Development] IISiDeK1CKII:
You don't open ADB. You follow the steps I've listed. You just use the folder ADB is in (Platform-tools) as a point of reference in Terminal.

Make sure you follow the guide step to step and you won't have any problems. If you overlook things, you will run into issues. Just take your time and be patient, and it will work.
[Thunderbolt Android Development] IISiDeK1CKII:
I guess the lack of posts in here for the last few days is evidence that all TB owners on macs are rooted. I guess this thread can die happily. :D
[Thunderbolt Android Development] cr125rider329:
Yea i changed the name and i followed all the instructions perfectly a couple of times now...everytime its still the same answer The Main Version Is Older!
[Thunderbolt Android Development] cr125rider329:
nvm...finally went through
[Thunderbolt Android Development] IISiDeK1CKII:
:thumbs up:
[Thunderbolt Android Development] jakejonez:
Haha. Rooted since day one on the bolt :D
[Thunderbolt Android Development] IISiDeK1CKII:
Congrats, when did you get your phone, today?
[Thunderbolt Android Development] UnclePauly:
THANKS! This reminded me of the good old days on my original DROID... good old adb. i had forgotten everything. took me like 2 hours, but everything went perfect! 2 issues i had:

1. you weren't clear on where to put the exploit stuff. I just threw the folder in the directory, until i realized u actually put all the FILES, not just the folder, into Platform-tools

2. i had a bit of a time getting my macbook pro to see my device. the fix turned out to be a couple of reboots, then toggle usb debugging a time or two.

I also was a bit confused as to why u put RUU_MECHA into the platform folder, when it never does anything there? it ends up just going to the root of the sd card later on in the instructions right before the first flash. no biggie, but i reread everything and retraced my steps for no reason, because i thought i missed something.

thanks again for the mac help!!!!!!!!!!
[Thunderbolt Android Development] IISiDeK1CKII:
**10 Char**
[Thunderbolt Android Development] michaelkahl:
My Thunderbolt is not showing up under available devices.

My-MacBook-Pro:platform-tools my$ ./adb devices
List of devices attached

My-MacBook-Pro:platform-tools my$

So when I try to push files it doesn't go, since it can't find an attached device. I've got all the files located in the platform tool folder, adb and the sdk are obviously running and installed...so what am I missing?

ADB debugging is turned on.
[Thunderbolt Android Development] IISiDeK1CKII:
I recommend you try these 3 things, try a different USB slot, enable "disk drive", and try pdanet. If those don't work, post back.
[Thunderbolt Android Development] michaelkahl:
I've tried a different usb slot and cable

I enabled disk drive

I tried PDAnet

All are a no-go :(
[Thunderbolt Android Development] michaelkahl:
I think site maintenance pretty much killed off troubleshooting last night. The only other thing I can think of that might cause this is EasyTether. I installed the software on my mac earlier in the week.

Thoughts?
[Thunderbolt Android Development] michaelkahl:
I fired up my netbook and rooted with Windows instead. Thanks for the help.
[Thunderbolt Android Development] IISiDeK1CKII:
Well, that's what the tutorials are there for. I have no idea what to say. Good luck with your future endeavors, sorry I was no help.
[Thunderbolt Android Development] michaelkahl:
You were a great help. I appreciate the guide and the time you took, I think it's well done. Like I said, EasyTether had been installed and used on my MBP prior to my rooting attempts. They may be the reason why it wasn't picking up correctly for ADB.

I just figured I'd root it on the netbook because it was quicker and easier. If I ever find out what keeps adb from working on my MBP I'll post it so others will know what NOT to do ;)

Thanks again :D
[Thunderbolt Android Development] michaelkahl:
Hell Yeah!!! I got an instant hit after checking google on the issue. Sorry I didn't try this sooner, but again...you have a great guide here and it's well done.

http://www.mobile-stream.com/easytether/android_faq.html#adbmacosx
[Thunderbolt Android Development] IISiDeK1CKII:
haha, I will have to add that to the original post. Thanks!
[Thunderbolt Android Development] albotz21:
i smell rotten fruit
[Thunderbolt Android Development] haggisman14:
Should this method still work if you've installed the OTA update by Verizon?
[Thunderbolt Android Development] haggisman14:
I know this is a slightly old post, but will having the Verizon OTA update installed on my phone cause any issues by having to install the downgraded RUU prior to flashing any other ROMs?

Thanks
[Thunderbolt Android Development] Chopstick2U:
Bump. This.
[Thunderbolt Android Development] Classick206:
Any answer yet on whether the OTA will conflict with this method?
[Thunderbolt Android Development] oldnavyguy:
Didn't affect me :-)