I get to step 5 which is same as step 2 but when trying to use adb command for busybox it fails but it pushed fine in step 2 which is exactly the same what's going on here?
Last edited:
[ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011
- Thread starter jcase
- Start date
Just says main version is older and aborts when flashing img
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Just successfully rooted my Tbolt. Checked CM7 site and it doesn't have Tbolt under its devices. Is there a separate site where I can download the ROM and Gapps?
Same Here! I messed up and updated which reverted to stock and now i cant root it keeps saying version is older.
Help would be greatly appreciated!
main version higher indicates that the misc image was not properly written.
when you ran this,did your md5match?
Code:
/data/local/busybox md5sum /data/local/misc.imgwhat happened when you ran this?
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17you can check out my session back on page 96 and see how yours is different.
did you try readding it as suggested? only thing i could think of as well was that it was accidently removed or somehow became corrupt
I just used the one on android central. Worked perfect I think this version is older than what my cpo came w
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
when? it depends on what ruus youve flashed and if youve flashed seperate radios after that.
a little more detail in your question is needed.
if you have just rooted using this guide and files,your baseband will end in 402.
I have used this this to root two thunderbolts. One has no problems, can change roms and move/rename files using Root Explorer. The other however I have changed roms a few times, but can't change system from r/o to r/w to move or rename files. Any ideas?
Sent from my ADR6400L using Tapatalk
Sent from my ADR6400L using Tapatalk
This is so dang WEIRD!
I unrooted and installed the stock ROM again but couldn't live with the bloat so I rooted again and had exactly the same experience as I did the first time (posted earlier)! After step 4 it refused to install the downgrade ROM, repeated everything and it worked.
After step 7 I typed "adb reboot bootloader" and got an error, can't find ADB(!) so I manually entered the boot loader and all went fine, it's rooted and new ROM installed.
So why did I have to repeat steps 1 - 4 both times I did rooted and why do I get "ADB not found" at the last step? That can't be normal, can it?
I unrooted and installed the stock ROM again but couldn't live with the bloat so I rooted again and had exactly the same experience as I did the first time (posted earlier)! After step 4 it refused to install the downgrade ROM, repeated everything and it worked.
After step 7 I typed "adb reboot bootloader" and got an error, can't find ADB(!) so I manually entered the boot loader and all went fine, it's rooted and new ROM installed.
So why did I have to repeat steps 1 - 4 both times I did rooted and why do I get "ADB not found" at the last step? That can't be normal, can it?
Im having a problem @ step4. When I “adb reboot bootloader” the phone reboots just fine, however, when I select fastboot, the only option is to go back to bootloader, it doesn’t see the PG05IMG.zip, but I have verified that it is sitting in the root of the sdcard. I’ve verified the checksum, and there are not two extensions on the IMG file. Anyone have any ideas? I’ve been searching, and have not found a resolution.
Thanks,
jwb
Thanks,
jwb
if you have placed the file on the ROOT of your sd card there are only 2 reasons that the phone will not find it:
1)its not named correctly(keep in mind windows automatically adds and hides the file extension. how are you checking for proper name? if you see PG05IMG.zip in windows you have in fact renamed PG05IMG.zip.zip). it must be PG05IMG.zip(zero,not uppercase letter "O")
2)your sd card is not formatted FAT32. right click on it while its plugged in and click properties. if you see FAT or anytthing other than FAT32 youll have to back it up and reformat.
one of those 2 things is wrong. good luck
1)its not named correctly(keep in mind windows automatically adds and hides the file extension. how are you checking for proper name? if you see PG05IMG.zip in windows you have in fact renamed PG05IMG.zip.zip). it must be PG05IMG.zip(zero,not uppercase letter "O")
2)your sd card is not formatted FAT32. right click on it while its plugged in and click properties. if you see FAT or anytthing other than FAT32 youll have to back it up and reformat.
one of those 2 things is wrong. good luck
Question
My girlfriend accepted the update to 1.70.650.0 with the 1.39.00.0627 radio. (Official release with new radio) she want's to root her phone at this point and I was wondering if the Downgrade RUU would flash her rom/radio back to stock settings so all is fine or if it only restores the system but not the radio. I don't want her getting the security warnings from a failed downgrade. If anyone knows what to do please let me know. I don't want her to brick her device. Let me know!
-TeK
My girlfriend accepted the update to 1.70.650.0 with the 1.39.00.0627 radio. (Official release with new radio) she want's to root her phone at this point and I was wondering if the Downgrade RUU would flash her rom/radio back to stock settings so all is fine or if it only restores the system but not the radio. I don't want her getting the security warnings from a failed downgrade. If anyone knows what to do please let me know. I don't want her to brick her device. Let me know!
-TeK
yes it will work fine. follow the guide,and make sure you flash a rom immediately after,as the guide will leave you on rooted mr1,not rooted mr2. trying to continued on older stock firmware will lead to possible OTA acceptance and other bad things.
there is a rooted 1.70.605.0 you can flash after rooting if you simply want to continue on stock firmware.
I need to look into that one....
If I'm not mistaken, and based on what I remember jcase doing with the Eris 1-2 years ago (!), the phone will be rooted but running essentially 'stock' (with an updated kernel + recovery) ? It will allow overclocking (presuming the kernel supports that), removing bloatware, etc, etc ? What about wireless tethering ?
thats pretty much what will happen. the only prollem is that this rooted firmware is old... it is mr1(firmware number 1.13.605.7) and you need to be on mr2(1.70.605.0). what you will need to do is follow the guide,and when your finished youll need to immediately flash a new rom. either a custom rom,or the rooted mr2.
just do not try and continue on the mr1 upgrade ruu... it will ultimately result in your phone trying to OTA itself to mr2,wich can be disastrous
wireless tethering does indeed work fine using barnacle,wifi thether,or one of the other root only tether apps.
I've rooted both my parents Thunderbolts... when adb can't be found and you have enabled usb debugging.... Simply unplug and replug the usb. Adb devices shows the device but offline next to it.. Unplug the phone and replug run adb devices again and it says online. I've duplicated it on both phones.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
189OUTDATED
Augest 14 2011
Unrevoked and AlpharevX released a new version of their http://revolutionary.io/ tool, use it, and preserve your data.
Do not use the root method below.
Original root left for a good read.
Advanced users wanting a different hboot please see http://xdaforums.com/showthread.php?t=1186022, others continue as is.
Updated May 12th 2011
This guide has been updated to MR1/OTA Firmware 1.13.605.7
This guide has been updated on April 21 2011 to make it more reliable, and faster.
On request I am reposting this in full, but please check out the original here first.
HTC tried to stop us. They made signed images, a signed kernel, and a signed recovery. They locked the memory. In short, the ThunderBolt is their most locked-down phone to date.
We fixed it for you. Unlike the root method we described yesterday, following the instructions below will provide S-OFF, remove signature checks, and unlock eMMC. Enjoy!
Rooting The ThunderBolt – Version 3
Pros
Root with read/write access to /system
Ability to downgrade and flash any RUU (i.e. signed firmware)
S-OFF
Fully unlocked bootloader
All ThunderBolts survived testing
Cons
Voids warranty
Could brick your phone if you aren’t careful
The method of rooting your Android device as described in the article herein is solely for enthusiasts and not for the faint of heart.
IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA.
Android Police and Team AndIRC disclaim all liability for any harm that may befall your device, including, but not limited to: bricked phones, voided manufacturer warranties, exploding batteries, etc.
The instructions below assume you already have a strong familiarity with adb command lines – this is not for beginners.
Credits
Scotty2, jamezelle, jcase, and all of Team AndIRC
dsb9938 for the tutorial cleanup
Testers, especially ProTekk and Trident
Thanks to scotty2 for WPThis
Busybox was pulled from a CyanogenMod ROM, source should be available here
psneuter was pulled from somewhere, credit to scotty2, source here
All firmware credit goes to 911sniper
Jaroslav from Android Police for editorial help
If I missed anyone in the credits, it was unintentional and I will fix it soon. Lots of people had their hands in on this project.
*** Please read the instructions in full before you attempt the process or head to IRC to ask questions. Also, make sure your battery is fully charged before taking the plunge. ***
Step 1
First, download these files:
Downgrade RUU PG05IMG_downgrade.zip ( (md5sum : aae974054fc3aed275ba3596480ccd5b) THIS IS THE DOWNGRADE RUU USED IN STEP 4:
Multiupload mirror
Mirrors for the package (contains busybox, wpthis, psneuter, su, readme.txt, misc.img, and hbooteng.nb0) (md5sum : 3b359efd76aac456ba7fb0d6972de3af) THIS IS THE EXPLOITS FILE:
Multiupload mirror
DroidSite mirror
Custom upgrade PG05IMG_MR1_upgrade.zip (md5sum : 7960c7977c25b2c8759605be264843ea) THIS IS THE CUSTOM RUU USED IN STEP 7:
http://www.multiupload.com/NEANZBS5S4
Step 2
Note that adb is required.
Push misc.img, busybox, and psnueter using the following commands:
Code:adb push psneuter /data/local/ adb push busybox /data/local/ adb push misc.img /data/local/ adb shell chmod 777 /data/local/psneuter adb shell chmod 777 /data/local/busybox
Step 3
This step will gain temp root and flash the custom misc.img. Run:
Code:adb shell
Now the shell should display "$".
Run:
Code:/data/local/psneuter
You will now be kicked out of adb, and adb will restart as root.
Let’s confirm the md5 of misc.img:
Code:adb shell
At this point, the shell should display "#".
Now run:
Code:/data/local/busybox md5sum /data/local/misc.img
Output should be "c88dd947eb3b36eec90503a3525ae0de." If it’s anything else, re-download the file and try again.
Now let’s write misc.img:
Code:dd if=/data/local/misc.img of=/dev/block/mmcblk0p17 exit
Step 4
Here you will rename the downgrade RUU (PG05IMG_downgrade.zip) as PG05IMG.zip and place it on your SD card (put the phone in drive mode and just copy it with your OS). Then, run the following command:
Code:adb reboot bootloader
Choose the bootloader option and press power; let the ROM flash. When asked to upgrade, choose yes. Don’t freak, it’s a long reboot.
Once done, reboot and delete PG05IMG.zip from your SD card.
Step 5
Set up the two part exploit, to gain root and unlock MMC.
Push wpthis, busybox, and psnueter:
Code:adb push psneuter /data/local/ adb push busybox /data/local/ adb push wpthis /data/local/ adb shell chmod 777 /data/local/psneuter adb shell chmod 777 /data/local/busybox adb shell chmod 777 /data/local/wpthis
Gain root (this will once again throw you out of adb):
Code:adb shell /data/local/psneuter
Unlock MMC:
Code:adb shell /data/local/wpthis exit
Step 6
Please pay attention – this is very important. This step involves a small chance of bricking if you mess up.
To push the eng bootloader:
Code:adb push hbooteng.nb0 /data/local/ adb shell /data/local/busybox md5sum /data/local/hbooteng.nb0
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.
Now we will write the new bootloader.
Code:dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
Confirm proper write:
Code:/data/local/busybox md5sum /dev/block/mmcblk0p18
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #root or go here AndIRC Thunderbolt Web Chat DO NOT REBOOT.
Reboot.
Step 7
Now, put the custom MR1 RUU (PG05IMG_MR1_upgrade.zip) on your SD card by putting the phone in drive mode and copying it with your OS. Then rename it to PG05IMG.zip
Then using an md5sum type program, check the md5sum and make sure it matches 7960c7977c25b2c8759605be264843ea, if it does not, redownload it. (Here is a free windows md5summer).
Next, run this command:
Code:adb reboot bootloader
Choose the bootloader option and press power; let the ROM flash. When asked to upgrade, choose yes. Don’t freak, it’s a long reboot.
Once done, reboot and delete PG05IMG.zip from your SD card.
After it flashes, you will be running release firmware with S-OFF.
Reboot your phone. You should now have full root permissions, an engineering kernel and recovery.
I recommend you get rom manger from market.
If you still have problems, come to the chat: irc.andirc.net #thunderbolt or use http://chat.andirc.net:9090/?channels=#thunderbolt.
.3http://www.youtube.com/watch?v=-UK_CiB2SYk
This video is great.. just follow that for a really quick and easy root using the new revolutionary tool2
The RUU is just HTC's equivalent of a ROM. The first one downgrades the software so that the exploits work. Once root is obtained using this RUU, you flash the other RUU so that you have the most recent firmware from HTC.2
Trying not to make any assumptions but from what you've said, it SOUNDS like you used the wrong file.
You need to put the DOWNGRADE file, called either "RUU_Mecha_VERIZON_WWE_1.03.605.10_Radio_1.02.00.0103_2r_NV_8k_1.37_9k_1.52_release_165253_signed.zip" or "PG05IMG_downgrade.zip" if you used the multiupload link. In either case, you rename it to PG05IMG.zip, and reboot to the bootloader etc. Once you choose the bootloader option and press power it'll take a second or two before the screen starts doing anything; it'll "fail" looking for a few different zip files before landing on the right one. After that wait a good 5 minutes or so, but you SHOULD see progress bars in the top right of the screen. Once its done, it'll ask you to update.
EDIT: And just an FYI it'll reboot midway, and recheck before continuing on. DON'T PANIC, and DO NOT abort the process; its normal; just let it do its thing.
