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

Root Thunderbolt Root/Unroot Thread

I don't think it worked. I skipped the fastboot oem rebootRUU and went fdirectly flashing that img file with the fastbboot command. You think that's the problem. Also I did not get the same output as you when recovery was flashed.

Code:
driller@driller-Latitude-D620:~/Downloads$ fastboot flash recovery recovery-ra-mecha-3.06-gnm.img
sending 'recovery' (5776 KB)... OKAY
writing 'recovery'... OKAY
driller@driller-Latitude-D620:~/Downloads$ fastboot reboot
rebooting... 
driller@driller-Latitude-D620:~/Downloads$ fastboot devices
driller@driller-Latitude-D620:~/Downloads$ adb devices
List of devices attached 

driller@driller-Latitude-D620:~/Downloads$ adb reboot recovery
driller@driller-Latitude-D620:~/Downloads$ adb devices
List of devices attached 
HT12HS005115    recovery

driller@driller-Latitude-D620:~/Downloads$ adb shell
/ # nandroid-mobile.sh -b --norecovery --nocache --nomisc --nosplash1 --nosplash

nandroid-mobile v2.2.3

Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default: cr

Using 2 --defaultinput 1>&2cr- prefix to create a backup folder

mounting system and data read-only, sdcard read-write
sh: --defaultinput: unknown operand
touch: unrecognized option '--defaultinput'
BusyBox v1.19.2 (2011-10-25 10:43:33 EDT) multi-call binary.

Usage: touch [-c] FILE [FILE]...

Update the last-modified date on the given FILE[s]

    -c    Don't create files

sh: --defaultinput: unknown operand
rm: unrecognized option '--defaultinput'
BusyBox v1.19.2 (2011-10-25 10:43:33 EDT) multi-call binary.

Usage: rm [-irf] FILE...

Remove (unlink) FILEs

    -i    Always prompt before removing
    -f    Never prompt
    -R,-r    Recurse

checking free space on sdcard
boot found on /dev/block/mmcblk0p22
sh: missing ]
Dumping boot to /sdcard/nandroid/HT12HS005115/2 --defaultinput 1>&2cr-BDS-20120210-0409/boot.img...BusyBox v1.19.2 (2011-10-25 10:43:33 EDT) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
    [seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

    if=FILE        Read from FILE instead of stdin
    of=FILE        Write to FILE instead of stdout
    bs=N        Read and write N bytes at a time
    ibs=N        Read N bytes at a time
    obs=N        Write N bytes at a time
    count=N        Copy only N input blocks
    skip=N        Skip N input blocks
    seek=N        Skip N output blocks
    conv=notrunc    Don't truncate output file
    conv=noerror    Continue after read errors
    conv=sync    Pad blocks with zeros
    conv=fsync    Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

md5sum: can't open '/sdcard/nandroid/HT12HS005115/2 --defaultinput 1>&2cr-BDS-20120210-0409/boot.img': No such file or directory
BusyBox v1.19.2 (2011-10-25 10:43:33 EDT) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
    [seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

    if=FILE        Read from FILE instead of stdin
    of=FILE        Write to FILE instead of stdout
    bs=N        Read and write N bytes at a time
    ibs=N        Read N bytes at a time
    obs=N        Write N bytes at a time
    count=N        Copy only N input blocks
    skip=N        Skip N input blocks
    seek=N        Skip N output blocks
    conv=notrunc    Don't truncate output file
    conv=noerror    Continue after read errors
    conv=sync    Pad blocks with zeros
    conv=fsync    Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

md5sum: can't open '/sdcard/nandroid/HT12HS005115/2 --defaultinput 1>&2cr-BDS-20120210-0409/boot.img': No such file or directory
BusyBox v1.19.2 (2011-10-25 10:43:33 EDT) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
    [seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

    if=FILE        Read from FILE instead of stdin
    of=FILE        Write to FILE instead of stdout
    bs=N        Read and write N bytes at a time
    ibs=N        Read N bytes at a time
    obs=N        Write N bytes at a time
    count=N        Copy only N input blocks
    skip=N        Skip N input blocks
    seek=N        Skip N output blocks
    conv=notrunc    Don't truncate output file
    conv=noerror    Continue after read errors
    conv=sync    Pad blocks with zeros
    conv=fsync    Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

md5sum: can't open '/sdcard/nandroid/HT12HS005115/2 --defaultinput 1>&2cr-BDS-20120210-0409/boot.img': No such file or directory
BusyBox v1.19.2 (2011-10-25 10:43:33 EDT) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
    [seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

    if=FILE        Read from FILE instead of stdin
    of=FILE        Write to FILE instead of stdout
    bs=N        Read and write N bytes at a time
    ibs=N        Read N bytes at a time
    obs=N        Write N bytes at a time
    count=N        Copy only N input blocks
    skip=N        Skip N input blocks
    seek=N        Skip N output blocks
    conv=notrunc    Don't truncate output file
    conv=noerror    Continue after read errors
    conv=sync    Pad blocks with zeros
    conv=fsync    Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

md5sum: can't open '/sdcard/nandroid/HT12HS005115/2 --defaultinput 1>&2cr-BDS-20120210-0409/boot.img': No such file or directory
BusyBox v1.19.2 (2011-10-25 10:43:33 EDT) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
    [seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

    if=FILE        Read from FILE instead of stdin
    of=FILE        Write to FILE instead of stdout
    bs=N        Read and write N bytes at a time
    ibs=N        Read N bytes at a time
    obs=N        Write N bytes at a time
    count=N        Copy only N input blocks
    skip=N        Skip N input blocks
    seek=N        Skip N output blocks
    conv=notrunc    Don't truncate output file
    conv=noerror    Continue after read errors
    conv=sync    Pad blocks with zeros
    conv=fsync    Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

md5sum: can't open '/sdcard/nandroid/HT12HS005115/2 --defaultinput 1>&2cr-BDS-20120210-0409/boot.img': No such file or directory
Fatal error while trying to dump boot, aborting.
/ # exit
driller@driller-Latitude-D620:~/Downloads$ adb reboot
error: closed
driller@driller-Latitude-D620:~/Downloads$ adb devices
List of devices attached 
HT12HS005115    recovery
 
Upvote 0
from this,it doesnt look like you entered the entire command:

Code:
driller@driller-Latitude-D620:~/Downloads$ adb shell
/ # [COLOR="Red"]nandroid-mobile.sh -b --norecovery --nocache --nomisc --nosplash1 --nosplash[/COLOR]

command is:
nandroid-mobile.sh -b --norecovery --nocache --nomisc --nosplash1 --nosplash2 --defaultinput 1>&2

one line,sorry if it looked funny

edit: to answer your other question,you dont need the oem rebootRUU command to fastboot flash the image. the way you did it was fine,and you got the correct outputs for that method.
 
Upvote 0
from this,it doesnt look like you enteresd the entire command:

Code:
driller@driller-Latitude-D620:~/Downloads$ adb shell
/ # [COLOR=Red]nandroid-mobile.sh -b --norecovery --nocache --nomisc --nosplash1 --nosplash[/COLOR]
command is:
nandroid-mobile.sh -b --norecovery --nocache --nomisc --nosplash1 --nosplash2 --defaultinput 1>&2

one line,sorry if it looked funny

reflashed using your zip file instead and going through it again. one sec
 
Upvote 0
YOU ROCK dude.

Thanks a million. Everything worked as you said. The phone is now in stock with security on. I even got the annoying thunderbolt noise at the boot :) Although I did not have a screen (blank/black) on my phone to see what was happening, I really did not need it.

Your instructions are flawless. I was going to write something specific for Linux but I would be just copying yours. You may want to add to the original post that if anyone is using Ubuntu Linux (or Linux) and has setup sdk and adb correctly, all they have to do is fire up a terminal and follow your directions. If they follow this link they can see how to setup sdk, adb, and java in Ubuntu Linux (mint is the same too)

I haved added to the thread by writing it for the latest version of Ubuntu at this link.

For the md5 values, all they have to do is to change to the directory the file is in and run the md5sum command replace directory and filename with the ones you have)

Code:
cd directory
md5sum filename
no need for the tools in the tbolt.zip file. I guess you would need the hbooteng.nb0 if you have used the revolutionary method to root. I rooted manually so I did not need it. Hence, in post #5 of this thread, I skipped steps relating to that (steps 1, 2, 17). Just download the 2 zip files in that post, original post, or mirrors I posted above, put them in a directory in the Home folder, cd to it in terminal and follow scotty's direction. That's all folks.

The instructions for the amon recovery was also on target and worked great. I was able to nandroid back up twice using adb. :) heaven!!! iPhone can't do all this.

I have clicked all the thanks button of yours I've seen. I really appreciated. You should setup a paypal for "BEER" though. It can support your work. You are very valuable to the Android community. I sent you a PM also. Anyone with Linux needing help with this, I could help. Either here or on XDA PM me.

Thanks again.
 
  • Like
Reactions: scotty85
Upvote 0
im glad it worked out for you. :cool: all credit however goes to erisuser1 who originally provided the commands in this thread: http://androidforums.com/eris-all-things-root/163423-flashing-rom-trackball-not-working.html blast from the past! all i did was remember where to find it :p

you can wipe data,restore a backup,and even flash a rom with adb,if needed. i may play around with this and see if i can get it working with other recoveries as well.

also thanks a bunch for the linux comments and links,also. for now ill put a link to that in the first post,im sure others will appreciate it!
 
Upvote 0
scotty I'm not very good with this stuff and you've been a huge help for me and many others so thank you very much.

I've pm'd you and with your help I have been able to successfuly un-root my wifes phone that was rooted the revolutionary way. But that way was made easy with your help along with natmil with a youtube video. I am now trying to unroot my other thunderbolt to sell that was rooted the old school way and there is no video help that I can find.

I know you have instructions here but they are rather confusing to me. I know its a PITA for you but do you have an easy explanation for me to un-root the old school way. Just simple link to files to download and simple instructions? (i already have adb set up)

Thank you and sorry for being a PITA myself but the Nexus world is calling me and its time to sell the T-Bolts. Thanks in advance for your help.

EDIT: I'm going to try and sell it rooted first. Why the heck not. Remove sim card, delete pics/photos off and wipe phone of apps/data wipe and move on. Seems like the easier route and maybe someone woyuld prefer to buy a rooted phone. Worth the shot to save myself the stress and trouble for now.
 
Upvote 0
s
I know you have instructions here but they are rather confusing to me. I know its a PITA for you but do you have an easy explanation for me to un-root the old school way. Just simple link to files to download and simple instructions? (i already have adb set up)

is the old schook thunderbolt running shadowmintes permanent hboot? check you hboot.
if you have: 1.04.0000 unlocked then you will need to follow all directions on the first post to remove it,or just leave it in place(my personal suggestion. there is no benefit from removing it)

if you have 1.04.2000 eng hboot,you can easily overwrite it,but id still prolly reccomend leaving it in place.

to sell your TB as unrooted,all you need to do is flash the "no hboot" file(the big one). this wipes all your data,and updates the phone to the most current unmolested software.

if the buyer wants to root it later they will be happy to discover an s-off hboot and be very gratefull to you. :D
 
Upvote 0
Scotty, I made two nandroid back up of my broken/returned thunderbolt before I returned to stock and and shipped it back to factory. Now I'm trying to restore the nandroid back ups and it says no backup found. Here are some details:

1- First time using Amon Ra and did the back up with adb (screen was broken) as above posts.

2- I did two back ups just in case, a folder named nandroid was created on the sd card. In it there is a folder names as my old thunderbolt's s/n. Inside of that there are two folders for the two backups. IN each of those there are 3 img files, boot, system, and data and one nandroid.md5.

3- the s/n on my new phone is different on the sticker under the battery from what I get in adb devices (I used the one I get in adb to root).

I just copied the nandroid folder to the ad card of the new phone, flashed the amon ra recovery and hoped I could get all me data back. But neither worked. Do you think renaming the folder in the nandroid folder the s/n of the new phone may work? I fear my backups are corrupt.
 
Upvote 0
naw,the backups are fine :)

heres what id do: remove the nandroid folder that you copied. boot back to recovery so that amon makes its own folder. mount the sd to the pc,and copy the nandoid files from your old nandroid folder into the new phones newly created nandroid folder.

ive restored across phones like that before. :)
 
Upvote 0
naw,the backups are fine :)

heres what id do: remove the nandroid folder that you copied. boot back to recovery so that amon makes its own folder. mount the sd to the pc,and copy the nandoid files from your old nandroid folder into the new phones newly created nandroid folder.

ive restored across phones like that before. :)

great, thanks. It worked perfect. The backups we made with adb worked great. Why more poeple don't use amon is beyond me. I didn't even know about amon until recently. You're a life saver.

I was too lazy to remove the 2GB folder and re-transfer so I just renamed the first nandroid folder oldnandroid. This is going to be my wife's phone and I had set it up for her, so I went ahead and made a nandroid so I can go back to it. This created a nandroid backup/folder as you suggested.

The problem proved to be that the main folder after the nandroid, takes the name of the current phone's serial number. So if the name of the folder was the old phones serial number, it will not recognize it. I guess it's an added safety measure Amon has so people don't accidently flash the wrong backup and brick. (different models)

I then as you suggested copied the old folders inside the s/n folder of the old phone bypassing the s/n folder itself and pasted them in the new nandroid folder in the s/n folder of the new phone. Magic :)

Only problem I encountered was that I could not mount while in recovery. I use Ubuntu so it may have a conflict with it. No biggie, I just rebooted and did it while the phone was booted and attached to the computer as an external drive.

a few questions:

1- Are CWM recovery and Amon Ra recovety compatible? Can they restore each other's backup?

2-The last two radios were the official OTA in Dec or Nov of 2011 and the leaked one in Jan of 2012. What's your experience with them? I have my wife on the official and my son on the leaked one ( I now have the Galaxy Nexus).

3- doing the nandroid backup, amon gives you more options than cwr. Do I just go with the defaults of boot, system, data and cache? the sd-ext, recovery, and I think one more thing is also available. Do I leave those empty?

Thanks again
 
Upvote 0
cool. glad it worked for ya :cool:

a few questions:

1- Are CWM recovery and Amon Ra recovety compatible? Can they restore each other's backup? amon can restore clockwork backups,but clockwork will not restore amon backups.

2-The last two radios were the official OTA in Dec or Nov of 2011 and the leaked one in Jan of 2012. What's your experience with them? I have my wife on the official and my son on the leaked one ( I now have the Galaxy Nexus).the leaked radio is for a carrier in puerto rico,id be really surprised if it actually gives better results than the official one dezined to work with verizon :eek: no harm in trying it out,but id do alot of before and after speed tests to make sure any percieved differences arent due to the placebo affect of it being a leak ;)

3- doing the nandroid backup, amon gives you more options than cwr. Do I just go with the defaults of boot, system, data and cache? the sd-ext, recovery, and I think one more thing is also available. Do I leave those empty? ill normally just leakve the default things checked(boot system,data,cache),but sometimes i will check recovery if i need an image of that recovery for other purposes-i can just pull it from the nandroid. but the recovery is not actually able to restore the recovery,so while it certainly wont hurt to back up recovery every time,i dont think theres much point to doing so,especially if you have an image of recovery allready that you can use in a "worse case" scenario :D

Thanks again
 
  • Like
Reactions: loveubuntu
Upvote 0
thats why i hate this MRxx name system :mad: he is not listing the puerto rican radio at all on the thread that you mentioned. at least hes providing a key thats describing whats what,so if you comepare the radio numbers,what hes calling "mr4" is the same radios im calling the "minor GB OTA". the date is confusing,seems hes got the date for the puerto rico leak attached to the minor GB OTA for vzw,for some reason... 2.11.605.9 came out before that,i believe,ill see if i can dig up when it happened.

call them what you want,but your going to be running 1.48.00.0930w 0.01.78.0916w_2 weather you download "minor GB OTA" from AF,or download "MR4" from that page ;)

the 930 radio is what i run on my TB,its the newest,and likely the best/fastest/most stable/best battery life,etc.

edit: 2.11.605.9 happened in december: http://www.androidpolice.com/2011/1...n-volume-exchange-and-more-sorry-no-ics-here/ so hes got his dates confused becasue of the whole "MR" naming system. :rolleyes:
 
  • Like
Reactions: loveubuntu
Upvote 0
thats why i hate this MRxx name system :mad: he is not listing the puerto rican radio at all on the thread that you mentioned. at least hes providing a key thats describing whats what,so if you comepare the radio numbers,what hes calling "mr4" is the same radios im calling the "minor GB OTA". the date is confusing,seems hes got the date for the puerto rico leak attached to the minor GB OTA for vzw,for some reason... 2.11.605.9 came out before that,i believe,ill see if i can dig up when it happened.

call them what you want,but your going to be running 1.48.00.0930w 0.01.78.0916w_2 weather you download "minor GB OTA" from AF,or download "MR4" from that page ;)

the 930 radio is what i run on my TB,its the newest,and likely the best/fastest/most stable/best battery life,etc.

edit: 2.11.605.9 happened in december: [Update: RUU Posted] HTC Thunderbolt Poised For An Update v2.11.605.9 With Fixes To Contact Ringtones, Notification Volume, Exchange, And More - Sorry, No ICS Here so hes got his dates confused becasue of the whole "MR" naming system. :rolleyes:

hmmm, my wife's says 930w_3 and 916w_3. Why the 3s vs 2s? This must be the minor OTA, right?

My son's says 0101w and 1110w_1. is this the puerto rico one?

they both seem to be working fine though :)

edit: the page you linked, also has the _3s not the _2s.
 
Upvote 0
hmmm, my wife's says 930w_3 and 916w_3. Why the 3s vs 2s? This must be the minor OTA, right?
hmmm,thats a good question. it may be that the "_3" is for the official GB OTA,wich i had purposely left out since they were suposeldy the same. ill have to pull that,flash it and check it out later.

My son's says 0101w and 1110w_1. is this the puerto rico one?
yup. thats it :)


they both seem to be working fine though :)

edit: the page you linked, also has the _3s not the _2s.
cool,thanx

10 char :)
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones