My thunderbolt had root
and it suffered bootloop yesterday due to some reason after flashing dasBAMF rom.
So I tried flashing 2.11.605.5 rooted ota PG05IMG from Android Police
and it totally went back to stock rom
I also realized I've lost root when I tried using apps for rooted phones only.
It was strange because I saw in the download thread saying it has root..
I tried flashing again on HBOOT and I found
there were no "LOCKED" text on the top. I believe that should be there if I don't have root.
Instead, it said "Revolutionary" on the top
So anyhow I found this thread, trying to gain root again.
When I ran the revolutionary program,
it came out said "Your device is already S-OFF"
Well, the apps I tried to run said I don't have root
and this program says I'm already rooted..
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
All the mirrors for clockworkmod recovery were somehow unavailable,
but barely found AmonRA recovery mirror did work.
I downloaded rom manager to flash another rom,
and I was surprised to see that it said CWM recovery was already installed..
I wonder how that could happen...
After doing some searching about invalid beta keys in the Revolutionary tool, I have seen that the font is a little hard to read on the terminal, and so it's easy to confuse an "I" for a "1" and whatnot. I didn't realize you can paste into the terminal via the dropdown menu in the top left corner. I will try that tomorrow. Hopefully I am just entering it incorrectly. I would be majorly disappointed if I coudn't root and rom my final replacement Thunderbolt.
I left my laptop at church yesterday morning, and I won't be able to get it until Tuesday. But I'll try this again Wednesday morning.
I am trying it on a co-workers laptop, but wouldn't you know the Revolutionary site appears to be down right now, so I can't get a beta key until it's back up. :-(
I don't suppose you could try and go there just to see if it is really down or something is going on with my computer? And if it's up, would you mind me PM'ing you my serial number, and you could pm me back the beta key?
Hopefully it's just down for maintenance, and big-brother didn't take it down. :-)
I know big-brother took down a lot of the RUU links on the megaupload sites.
It's back up, and I got the key. I copied and pasted it into Word and upped the font size a bit so I can make sure I'm reading correctly.
Thumbs crossed.
I'm confident in being able to root my phone, however; in order to do so, I have to downgrade my software from version .9 to a .5. This is where my issues follow. The tutorials that I have come across are a bit confusing considering that I have not done this before. It was recommended to downgrade by some sort of .exe file but I do not know its location. Could someone please assist me in downgrading my phone? Thank you.
edit: I'm rooted!
Last edited by Brainchild; January 30th, 2012 at 08:37 PM.
The Following User Says Thank You to Brainchild For This Useful Post:
easiset way to downgrade is to download the .exe file for 2.11.605.5 and run it on the PC. plug in your phone when it tells you. links for this and other RUUs are in the 4th post of this thread
easiset way to downgrade is to download the .exe file for 2.11.605.5 and run it on the PC. plug in your phone when it tells you. links for this and other RUUs are in the 4th post of this thread
Most of the links in these posts are not working.. I get "file not found" or invalid.
Most of the links in these posts are not working.. I get "file not found" or invalid.
Are these links going to be updated sometime?
Thanks!
every one ive checked,the "Wupload" link is still working for download.
the radio,recovery,hboot files can be uploaded to media fire,but the bigger files will need somewhere else for a mirror,as media fire has a 200mb limit,so i am prolly not going to update the links until such a time that they stop working.
So here is my dilemma, scotty is trying to help me but I'm sure he is busy too. So In the mean time feel free to help. ANY HELP IS GREATLY APPRECIATED
My tbolt was rooted the original way manually. Now my screen is blank/black. The phone is up and running but I can't see anything. ADB is setup and I can get to fastboot. I use Linux (ubuntu or mint). They are sending me a new one since my warranty is not over yet but I would like to return it to stock before returning it. Here are my questions:
1- I don't need the tbolt.zip file since I used the original manual root (jcase and teamandirc), correct? All I need the the other two files from post #5, right?
2- I can't download the two files, the website is down. Any mirrors?
3-When I go through this process, does this erase everything? I actually prefer this since I want my personal data erased. Anything else I can do to make sure it is erased before I send it back (erasing any folders?)
ive added mirrors for tbolt and hboot only. no hboot is still at about 51%
since you dont have adb set up,you dont need most of tbolt,but it does contian the md5 application it contains the hboot youll need,so you might as well download it,even if you just wish to move those things into your adb file
turns out its easy peezy to make a backup with amon and adb,so if youre willing to install amon to make said backup,ill get working on the directions to add making a backup to the unroot.
last,and not least,yes,everything will be erased after flashing the ruu(no hboot.zip)
ive added mirrors for tbolt and hboot only. no hboot is still at about 51%
since you dont have adb set up,you dont need most of tbolt,but it does contian the md5 application it contains the hboot youll need,so you might as well download it,even if you just wish to move those things into your adb file
turns out its easy peezy to make a backup with amon and adb,so if youre willing to install amon to make said backup,ill get working on the directions to add making a backup to the unroot.
last,and not least,yes,everything will be erased after flashing the ruu(no hboot.zip)
I'll bring our conversation here just in case it would help another poor soul in the future.
Yes I do have adb setup and can access fastboot so I'm all set. I also seem to have downloaded all three files. Someone on XDA sent me a link for a mirror, I have not checked the md5 but will as soon as I get home. I run Linux boxes so md5 program not needed. I will just run it in the terminal.
both file names from post#1 and his link say 2.11.605.9, so I assume they are the same file.
questions:
1- Do I need the first step for the hbooteng.nb0? I used the original root method not revolutionary? I thought I read some where that this step is only needed for the revolutionary method.
2- I'd love to try the amon to back up. But my whole reasoning was that titanium backup is able to extract app and data from the cwm nandroid so I could get some of my data back. You think it can be done with amon too? It should. I have to this before anything else, right?
3- without a screen, is there a way to confirm that the phone is S-ON and stock?
Also, I'm going to use the note you sent me on XDA to backup my data folder
c:\tbolt>adb shell
/ # nandroid-mobile.sh -b --norecovery --nocache --nomisc --nosplash1 --nosplash
2 --defaultinput 1>&2
nandroid-mobile.sh -b --norecovery --nocache --nomisc --nosplash1 --nosplash
2 --defaultinput 1>&2
nandroid-mobile v2.2.3
Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default: Accepting default.
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
boot found on /dev/block/mmcblk0p22
sh: missing ]
Dumping boot to /sdcard/nandroid/HT12CS012936/BDS-19800106-0001/boot.img...1024+
0 records in
1024+0 records out
4194304 bytes (4.0MB) copied, 0.229339 seconds, 17.4MB/s
done
Dump of the recovery partition suppressed.
Dump of the misc partition suppressed.
Dump of the wimax partition suppressed.
Dumping system to /sdcard/nandroid/HT12CS012936/BDS-19800106-0001/system.img...d
one
Dumping data to /sdcard/nandroid/HT12CS012936/BDS-19800106-0001/data.img...done
Dump of the cache partition suppressed.
generating md5sum file...done
unmounting system, data and sdcard
Backup successful.
/ # exit
exit
c:\tbolt>adb reboot
edit:
crap! looks like no hboot stuck at 70% ill start it again...
Last edited by scotty85; February 9th, 2012 at 06:59 PM.
I'll bring our conversation here just in case it would help another poor soul in the future.
Yes I do have adb setup and can access fastboot so I'm all set. I also seem to have downloaded all three files. Someone on XDA sent me a link for a mirror, I have not checked the md5 but will as soon as I get home. I run Linux boxes so md5 program not needed. I will just run it in the terminal.
both file names from post#1 and his link say 2.11.605.9, so I assume they are the same file.
questions:
1- Do I need the first step for the hbooteng.nb0? I used the original root method not revolutionary? I thought I read some where that this step is only needed for the revolutionary method.correct. if you rooted old school,and youre following the directions in post#5,you wont need hbooteng.nb0,thats your current bootloader,and youll be replacing it directly with the 1.05.0000
2- I'd love to try the amon to back up. But my whole reasoning was that titanium backup is able to extract app and data from the cwm nandroid so I could get some of my data back. You think it can be done with amon too? It should. I have to this before anything else, right?correct. hopefully the above clears it up some.do the backup before doing anything else in post #5.
once you get the new phone,install amon,restore the backup. if you want to continue on a new rom,just run titanium backup at this time.
3- without a screen, is there a way to confirm that the phone is S-ON and stock? you can do a fastboot getvar all with the phone in fastboot. right after step 19 would be a good time
Also, I'm going to use the note you sent me on XDA to backup my data folder
to restore it in the new phone. Is this going to work?
it should. id do the amon backup,too,or even instead of. i just did it on my TB and it worked fine. made the backup like that,wiped and restored that backup. no issues.
You are my hero I would like to buy you a beer, you do not have anything setup for that.
nope
i do appreciate the offer,tho. just click the "thanks" button is enuff
Once I do this with Ubuntu Linux, will write something to add to this thread to help others running Linux awsome. sounds like a worthwhile addition,id appreciate the contribution
oops,10 char
Last edited by scotty85; February 9th, 2012 at 06:20 PM.
heres what youll see with the getvar. this is my thunderbolt,but it gives you the idea:
Code:
c:\tbolt>adb reboot bootloader
c:\tbolt>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.04.2000 <-this should say 1.05.0000
INFOversion-baseband: 1.48.00.0101w <-this should be 1.48.00.0930w
INFOversion-cpld: None
INFOversion-microp: /
INFOversion-main: 2.10.605.1 <-this should be 2.11.605.9
INFOserialno: HTxxxxxxxx
INFOimei: 355195000000017
INFOproduct: mecha
INFOplatform: HBOOT-7630
INFOmodelid: PG05*****
INFOcidnum: 11111111 <- this should be VZW_001
INFObattery-status: good
INFObattery-voltage: 4112mV
INFOpartition-layout: Generic
INFOsecurity: off <-this should say on
INFObuild-mode: ENG <-this should be SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 9a13ccd2
INFOhbootpreupdate: 12
INFOgencheckpt: 0
INFOregion-id: not support
all: Done!
finished. total time: 0.023s
Last edited by scotty85; February 9th, 2012 at 06:33 PM.
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
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.
Last edited by scotty85; February 9th, 2012 at 10:28 PM.
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)
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.
Last edited by loveubuntu; February 11th, 2012 at 03:54 AM.
The Following User Says Thank You to loveubuntu For This Useful Post:
im glad it worked out for you. all credit however goes to erisuser1 who originally provided the commands in this thread: Flashing Rom, Trackball not working! blast from the past! all i did was remember where to find it
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!
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.
Last edited by Yellow Snowman; February 11th, 2012 at 12:19 PM.
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.
Done, couldn't have been easier. Scotty please tell me you're coming over to Galaxy Nexus!
Either way you've been an incredible help and flat out life saver for me. The MB is lucky to have you man. Post your paypal so I can give thanks the right way.
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.
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.
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?
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 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
Thanks again
The Following User Says Thank You to scotty85 For This Useful Post:
Have you compared these two listings? I don't think the puerto rico one in this thread is the same as the one called MR4 - Leak January 21, 2012 in this other page, do you?
thats why i hate this MRxx name system 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.
thats why i hate this MRxx name system 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.
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
Ok now that I have both of them set up with their Thunderbolts and have stolen their upgrade to get the Galaxy Nexus (the second upgrade is waiting for the Galaxy Note/Journal), on to rooting the Galaxy Nexus.
3Likes
)
I get "file not found" or invalid.
ill start it again...
