Related
Been lurking for sometime learning things here and there, but now I've got an issue of my own I been pulling hair out over for the last 6 hrs.
I Upgraded to 2.11.605.9 Verizon OTA release today... attempted to use the revolutionary tool to re-root after the upgrade. Well that didn't work. I just get the message "Zerging Root... this might take a minute or so.. Failed to get Root! "
I have tried http://forum.xda-developers.com/showthread.php?t=1009423 the non root users section. With no luck.
Pretty new at this stuff, so if someone can let me if its possible to get s-off, i'd just like to downgrade to an earlier pg05img and NOT get the latest update So i can use revolutionary root.
Thanks in advance.
Nick
Try this..
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
CaptainStrange said:
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
Click to expand...
Click to collapse
I've rooted multiple times using the method above, but since the update, I can't get past the Zerging Root step, even following the posts from the first link you sent
Flashed the Pg image using .androidpolice.com/2011/10/24/exclusive-gingerbread-build-2-11-605-5-for-the-htc-thunderbolt-fixes-several-issues-from-the-previous-leak/[/url] and it works, I was able to re-root using the rev.
Capt....
I am having the same problem as him. After I got this warranty replacement yesterday, no matter what I tried, I can't get past "zerging root". Cannot gain root access. I see you said to flash that image, but how do you do that if you cannot get s-off. I have also rooted thunderbolt several times using the "one click method" (which is also not working for this new 2.11. 605.9 build) and revolutionary. Any suggestions or instructions?
You dont need S-off to load that image... Simply download the file and rename it pg05img.zip and put it on the root of your SD card. Reboot the phone and hold down the vol down + power button to access the bootloader, push the volume button and it will search the sd card for the pg05img.zip file and load it. Just keep in mind it will reload it to factory settings, so back anything up that you have. It takes about 15 mins, but it does work. Once you have that image loaded from the link above you can use the revolutionary root. Let me know if you need help.
Rooting after 2.11.605.9 on TB solution
For those of you that have endured the frustration of updating to the latest software version (2.11.605.9) There is hope! Apparently with this software version, the bootloader is locked. And for some reason this version would not allow the "Revolutionary" rooting method to work. (I would imagine everyone with this problem had issues with not being able to get past Zerg Root. At least that was the problem I had)
Anyways, I got my phone rooted....heres how.
Per the instructions for using Revolutionary, install the driver as stated on their website. (Make sure HTC Sync is not installed on your computer)
Download Mecha_2.11.605.3.zip (I'm a newbie here so I cant post links, but I found it through Android Police but if u google it its easy to find, its hosted on multi upload) rename the zip file as PG05IMG and put on the root of your SD card (as you would in other rooting methods) and run the bootloader.
Once its booted and all that fun waiting is over and your TB powers back up, make sure to turn off all wireless connections to make sure OTA doesnt try to upgrade you. (I turned on airplane mode as soon as I could)
From there run Revolutionary as instructed from their website. Worked like a charm for me, and hope it does for all of you with this same problem.
I TAKE ABSOLUTELY NO CREDIT FOR THIS SOLUTION. Thank you for all you developers out there that make our phones able to be so much cooler and more enjoyable. I'm just glad I could help in this marginal way, and hope that someone will find it usefull. SPREAD THE WORD IF YOU KNOW OF ANYONE HAVING
So if I unroot and my phone takes the latest 2.11.605..9 update, all I have to do is flash the 2.11.605.5 RUU, put phone into airplane mode as soon as it boots, then I can root again?
I am not sure if I missed something but I followed those steps. When I went into boot, it said my version is "older- failed" and won't revert to the .5
I am miserable here with stock. I want to be rooted again.
Any thing else I can do?
Not sure why it wouldn't let you revert to an earlier RUU. Have you tried other earlier versions other than .5? The RUU I used was 2.11.605.3. Try that one. What version bootloader do you have? Also is there Pink letter at the top that says LOCKED?
I have not tried an earlier version... Yet. Will try and will update you. But the bootloader says "***locked***" s-on on the main screen. So I am not sure any older one will work. I read other people were able to accept a downgrade so I am hopeful.
Bootloader 1.5 and yes... It is ***locked*** sigh...
Try loading the 2.11.605.3 If it works just make sure you disable wireless connections when it boots, so OTA doesn't push the upgrade
Even if the OTA comes up before you disable any wireless connection it will download the OTA but then ask if you want to accept or defer. Just hit defer and proceed with the Revolutionary method to root and gain s-off.
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Ok guys hold on now, this is kind of misleaing... so did the OP have s-off for the downgrade ? Revolutionary has a password protected HBOOT that was designed to maintain s-off during an OTA or upgrade RUU, hence the reason a downgrade would be possible... Is the OP able to confirm they had S-OFF during the upgrade or S-ON. If i upgrade to 2.11.605.9 on a stock phone S-ON, am i going to be able to downgrade with ease ? I would say no.. not without tricking the bootloader into thinking its an older version which is what the commands are for:
adb push misc.img /data/local/
adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
However you can't do this without a temporary root shell.
on build 2.11.605.9 there is no exploit for temporary root shell currently..
Please clarify.. ?
rberry88 said:
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Click to expand...
Click to collapse
No matter how far out you pick, the limit is 5 days. Picking anything longer, the phone will tell you that.
Like I was saying before the OTA came out, this OTA patches zergRush.
Bootloader has always been locked, this is not new.
I have a few vulns found, and erishasnobattery and I have a couple working exploits done.
However I am on vacation and wont be home until late tonight, once I am we will get something packaged and released for root.
Until then (this isn't the one we are going to release)
Awesome, i just bought my wife a t-bolt Friday and it did an OTA (that i just assumed was the same old gingerbread update that my buddy got but apparently it wasn't because i could not root. Thanks jcase for working on this for us.
I was able to get root with 2.11.605.9
I was already on 2.11.605.5 with root and S-OFF (revolutionary). Perhaps you can try one of the earlier releases such as MR2? This is what you do to get root with 2.11.605.9 if you can get your phone back to 2.11.605.5 or older:
1. Reinstall 2.11.605.5 stock (no root). I got the file from Android Police. I had to rename the file as PG05IMG.zip and run it from the bootloader.
2. Obtain S-OFF with Revolutionary after 2.11.605.5 has installed. Do not install clockworkmod or super user yet.
3. Allow the 2.11.605.9 OTA to be installed. Let the phone do it's thing, the update took my phone awhile.
4. Install Clockwork Recovery (again rename it as PG05IMG.zip and run it from the bootloader)
5. Boot into bootloader again and select Recovery. Install superuser.
6. Reboot and enjoy.
PS. I stumbled upon this on another thread here.
So I'm on a new phone that just did the .9 update about 10 minutes ago and then I find this thread after failing to root. So I'm s on stock everything. I can't revert can I? I'm screwed. I hate stock phones. Adds everywhere. No tether boring no options. I want my skyraider back.
EDIT: UPDATE .... i managed to get the phone rebooted .... held the force reboot buttons for literally over a min in desperation.... not i need to fully unroot and start from scratch but am having trouble with that still.... can anyone help me either (A) get s-off ... or (B) get it so that i am completely unrooted so i can start over from scratch to get s-off????
Ok folks, i am officially stuck.... its been quite awhile since i have really asked for help on here but i am stuck in a really bad way!!!
Here is how i got to where i am
Just bought my brand new EVO LTE today and went to root it using "[ROOT] RegawMOD EVO 4G LTE Rooter | Updated 06.13.12" from this section!
everything seemed to work great and it said everything rooted properly.... I love Clockwork mod recovery so i then flashed that and it worked properly to or so i thought! so i went to create an origional Nand but it would not work, so i decided to flash TWRP back instead and do that way. when going into the bootloader it said "Tampered" as expected, but it still said S-on so obviously not a proper and correct root.
So i ran RegaMOD again as it said in the instructions, but it would never get passed the HTCdev part, it would just say "sucessfully logged out" and sit there forever and do nothing. So after a few tries of that i decided to unroot and start over from scratch. I could not find an unroot method for RegaMOD so i then went to the other root method "How to Root HTC Evo 4G LTE! [Windows/Mac/Linux] - by Zedomax" in this section and saw it had an unroot method which i followed to the letter! did full unroot through SuperSU and then downloaded the stock RUU from that section for my phone with the proper version number.
everything seemed to be running fine went to the black "HTC" screen and everything was going smoothly.... then the update failed and my phone stayed on the black HTC screen. my computer prompted me to recover which i could not really do as you can't pull the battery on this phone. So i then tried to update the RUU again except this time it did not list a current software version, only the one i was updating too.... it failed again 2 more times!!
when plugged into the computer my phone displays the black "HTC" screen
when plugged into the charger it displays the following screen info (bootloader look)
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT AO <---- MIGHT BE FASTBOOT AC HARD TO TELL
Update Fail!
when un-plugged it says almost the same thing
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT <---- THIS IS THE ONLY CHANGE
Update Fail!
no buttons do anything at all, in any combination or holding pattern
PLEASE HELP ME!!!!! THANKS TO ALL IN ADVANCE!!!
just one thing, s-on or s-ff has nothing to do with root
did you relock your bootloader before running the RUU?
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
+1
shootin4aces said:
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
Click to expand...
Click to collapse
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
shootin4aces said:
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
Click to expand...
Click to collapse
read the post above yours he did tell you how to do it..lol
Oh and before I forget: Don't use CWM. Unless they've fixed it in the last couple of days it breaks your /misc partition, which is quite probably what caused your issues in the first place.
Use TWRP. After you have root/unlocked you can download goomanager from the Play Store...it will install it for you.
smw6180 said:
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
Click to expand...
Click to collapse
+1 and wrong section
This is the method I used on my 4lte without a problem. But you should read entire post before attempting cause it flashes TWRP recovery automatically along with SU. Clockwork still is buggy.
http://forum.xda-developers.com/showthread.php?p=26955832
from my "Beach Watcher" 4LTE
thankyou
all problems have been fixed, thankyou everyone for all your help
again, sry for posting in the wrong forum with this issue, and i am sorry if i came off as a noob! I'm really not, just completely jumped the gun and am very very tired as i have been up for almost 36 hours now
thankyou again for all the help, and as i normally do, i will perform all my research before my next venture.... a lot has changed between this phone and my last one that i rooted and modded, i will be more prepared in the future!
Selders, you're here now?! Good to see ya here
sent from a shining jewel 4g LTE
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
hunteditor said:
Okay, guys, I apologize for what I'm about to ask, but I am now completely lost in the Global Update thread, so I needed to start fresh.
I was rooted and on stock 3.14.605.13. I kept getting annoying update messages from Verizon and tried several forum suggestions to turn them off. Finally I just decided to try to get the update. I was able to unroot and install an RUU back to 3.14.605.12, but now I'm completely stuck. :crying: I'm getting the same Service Unavailable message as others who try to get the small .13 update.
I have downloaded the 3.14.605.13 update zip but can't decipher how to get it installed since the Global Update Thread is now so jumbled.
If anyone has the time to helps us NOOBS (I think I saw several others in my situation), could you please give a step by step rundown of what we need to do? Please start from step 1. For example, do I need to root again now before I can get up to .13?
Finally, if I do get to .13, can I just unroot and get the new global update via Verizon?
Click to expand...
Click to collapse
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Wow, that was fast.
synisterwolf said:
going to need some more information:
1. Are you S-off or S-on
2. Are you dev unlocked, locked, or engineering hboot
3. What hboot are you currently on
Click to expand...
Click to collapse
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
hunteditor said:
S-ON
***RELOCKED*** (I did the HTC unlock with a pin code when I originally rooted, but I "unrooted" via a one-click program, so I don't know the correct answer to the lock question). I relocked the bootloader via sdk if that helps.
hboot is 2.25
Click to expand...
Click to collapse
you should be good to do the update.
ruu using this zip http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
(place on root of sd card, rename PH98IMG.zip)
it will run 2 times. once with be bootloader and recovery, second time will be the full rom.
this will get you to stock OTA should show up a little while after its all installed and connected to the network.
EDIT:
If updated doesnt show up in a day you should be able to update with this zip: http://forum.xda-developers.com/showpost.php?p=40768590&postcount=35
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
hunteditor said:
Okay, I think you're going to be able to get me there ... but ...
I downloaded the zip file and renamed it to PH98IMG.zip. I copied it to the root of both the internal and external cards since I wasn't sure which it needed to be on.
Now how do I execute the RUUx2s? The last one I did to get back to .12 was an .exe file, so that was easy.
I do have SKD and can open a command prompt, so you don't have to go that far back in instructions.
Click to expand...
Click to collapse
once on root of external sd card. reboot the phone into bootloader
power off device hold vol - and power till you see hboot
hboot will detect it and run for you.
make sure you have 70+ battery before trying this. and do not pull the battery or loose power or it will birck.
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
hunteditor said:
Worked like a charm. A million thanks to you.
Donation on the way!
Thanks again for being so patient!
Click to expand...
Click to collapse
wow, thank you kindly. Any time you need help just ask, thats how we all learn.
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
hunteditor said:
Okay, hopefully last question.
I downloaded the OTA zip just in case.
If I need to end up doing that manually, do I rename it (and if so to what?) copy it to root and then run hboot?
Click to expand...
Click to collapse
just like the ruu rename it to PH98IMG.zip and flash in hboot. again make sure you have enough battery
Hello all, I tried searching but if I missed the thread please point me to it. I was able to unlock the bootloader using HTC Dev but I cant seem to install TWRP. Am I missing a step or something? I am running an HTC Evo 4G LTE on 3.17. I tried putting the PJ75IMG.zip in the root of the sd card but when restarted in the bootloader it read it and said main version is older. I tried using goomanager to download and install but that didnt work either. Am i doing something wrong here? Thanks in advance guys (and girls)!
fastboot flash it PJ75IMG.zip will only work if you are S-OFF
Put the .img file in the folder you are using to run the commands from.
fastboot flash recovery nameofrecovery.img
OK. So fastboot is the best method. Then I can install super user correct? I dont HAVE to install a ROM if i dont want to correct? I can just run stock root? If I wanted to install a ROM would I need to be S-OFF? or could I install one while still being S-ON? It has been quite some time since I rooted a phone. Last phone was the Samsung Epic 4G. What a terrible phone. Thanks and sorry for so many questions.
quattroa430 said:
OK. So fastboot is the best method. Then I can install super user correct? I dont HAVE to install a ROM if i dont want to correct? I can just run stock root? If I wanted to install a ROM would I need to be S-OFF? or could I install one while still being S-ON? It has been quite some time since I rooted a phone. Last phone was the Samsung Epic 4G. What a terrible phone. Thanks and sorry for so many questions.
Click to expand...
Click to collapse
I personally use fastboot to install twrp then when you want/need to update twrp you can fastboot flash again or use goomanager from the playstore.
You can install SuperSU and run stock rooted or flash a custom rom which has superuser added
As for flashing roms you can flash them while s-on it's just more work because you have to fastboot flash the kernel/boot.img then flash the rom.
I always recommend S-OFF as it will save you the extra steps in flahing roms and also if you mess something up you can flash an older RUU if the most current RUU is not available.
@FinZ28 has a great guide explaining how to flash the kernel/boot.img
OK, so now the question becomes what method for S-OFF should I use? I would like to be able to make it look like I never rooted the phone if need be if at all possible. I heard good things about rumrunner for 3.17. am i correct that this would be the best method or is there a better one? again sorry its been too long and this is my first HTC root.
quattroa430 said:
OK, so now the question becomes what method for S-OFF should I use? I would like to be able to make it look like I never rooted the phone if need be if at all possible. I heard good things about rumrunner for 3.17. am i correct that this would be the best method or is there a better one? again sorry its been too long and this is my first HTC root.
Click to expand...
Click to collapse
Since you are on 3.17 rumrunner is the only method you can use
OK so first install TWRP then SU then S-OFF? also i factory reset my phone the other day and now on some apps I have this weird menu bar at the bottom. it happens on my facebook app and bank app. it doesnt show up in Kik or play or sms apps. any ideas? i would like to remove that
quattroa430 said:
OK so first install TWRP then SU then S-OFF? also i factory reset my phone the other day and now on some apps I have this weird menu bar at the bottom. it happens on my facebook app and bank app. it doesnt show up in Kik or play or sms apps. any ideas? i would like to remove that
Click to expand...
Click to collapse
Yes unlock your bootloader if you have not already
Install twrp
Flash SU
Then S-OFF(make sure you read all the pre-requisetes before starting rumrunner
As fo the weird menu it may disappear if you flash a custom rom
Ok so I came across another issue. I cant seem to get busybox to install. I would like to install cyanogenmod 10 and qbking mentions needing s-off to do so. Is that correct? It is a bit of a pain being on 3.17 but I guess there isnt much I can do. Any advice for installing busybox? Thanks again
I successfully installed Busybox on 3.17 last night. As far as having to be S-off to flash CM, no, you don't have to be, but it makes life easier. Hit the top link in my sig and read my Hboot guide if you haven't already done so.
Sent from my HTC EVO 4G LTE
I read your hboot guide. Very informative. Rumrunner requires busybox and for whatever reason I cannot install busybox. Could you possibly eexplain what choices you made that worked? I tried installing to bin and xbin. Should I install to a custom location instead? If so where should I? I would like to be s-off and have cyanogen lol. Thanks again guys!
quattroa430 said:
I read your hboot guide. Very informative. Rumrunner requires busybox and for whatever reason I cannot install busybox. Could you possibly eexplain what choices you made that worked? I tried installing to bin and xbin. Should I install to a custom location instead? If so where should I? I would like to be s-off and have cyanogen lol. Thanks again guys!
Click to expand...
Click to collapse
I'm not really sure what to tell you since I was already S-off when I installed it. Where did you read that it was required prior to running Rumrunner?
Sent from my HTC EVO 4G LTE
It was on the pocketables website. search "rumrunner HTC EVO 4g LTE" everytime I seem to try to install busybox my phone crashes.
Are you running just the stock rooted factory rom?
You could try Captain_Throwbacks 3.17 rooted rom or SharkieRom 3.17
Try this. Its a TWRP flashable zip of the latest Busybox (v1.20.2). See if that straightens things out with your issue. Make sure you have a backup handy just in case.
https://www.dropbox.com/s/g16xuqbzbmzz8yz/busybox-signed.zip
You can use a file manager like Root Explorer and go to /system/xbin/ and look to make sure you see the Busybox file. If it's there you're good to go:thumbup: (I did not develop the Busybox file-I simply took the file and make it into a flashable zip. Big thanks to Rootlinux for showing me how it's done).
Sent from my HTC EVO 4G LTE
FinZ28 said:
Try this. Its a TWRP flashable zip of the latest Busybox (v1.20.2). See if that straightens things out with your issue. Make sure you have a backup handy just in case.
https://www.dropbox.com/s/g16xuqbzbmzz8yz/busybox-signed.zip
You can use a file manager like Root Explorer and go to /system/xbin/ and look to make sure you see the Busybox file. If it's there you're good to go:thumbup:
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Worked like a charm. Busybox is installed right where you said it should be. Now to run rumrunner and gain s-off. Thank you guys for all the help and support thus far!
quattroa430 said:
Worked like a charm. Busybox is installed right where you said it should be. Now to run rumrunner and gain s-off. Thank you guys for all the help and support thus far!
Click to expand...
Click to collapse
Glad it worked for you:thumbup:
Sent from my HTC EVO 4G LTE
S-OFF Issue
Ok now I can't seem to gain S-OFF using rumrunner. I downloaded the correct version for the EVO 4G LTE and I am running native Ubuntu 13.10 32bit. It works for a while until it gets to the pouring stages
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
YesDo you understand the implications of this warning?
(Yes/No)
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (21/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (21/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)...
WTF: What are you doing?
Idk what I am doing wrong here. I couldnt even get it to work right using windows so I had to break out the laptop.
It gets to that point every time then fails and reboots the phone.
Software version: 3.17.651.4
Android Version: 4.1.1
Kernal Version: 3.4.10-gf5d846c
Is there anything else needed to help figure this out? Tis getting a wee bit frustrating. Can I S-OFF off if i flash cyanogen or any other rom?
Tried running Captain_Throwbacks stock rooted 3.17 and got the same result at the same exact point while running rumrunner. Going to try Sharkie next. Any tips are greatly welcomed!
Don't have much to offer since I haven't used Rumrunner. Having said that, make sure you're using a USB 2.0 port and not 3.0, and that you're using a fairly stock Sense ROM. Also make sure that you're phone is recognized with both ADB & Fastboot. Seems most of the issues I've seen have to do with the connection. If it fails, try try again. You also might want to check out the Rumrunner thread in original development.
Just a thought, but have you looked at your bootloader and made sure that you're still S-on? Reason I ask is because on Moonshine the "WTF: What are you doing?" message actually meant that the process was successful. Not sure if Rumrunner is the same.
Sent from my HTC EVO 4G LTE
Sorry for being a noob in advance I really would like to root this phone, and have been trying for like the past 3-4 months trying everything from z4 root the app to hasoon2000's all-in-one toolkit, and I still cannot seem to root it. If anyone thinks they can help me or if you would like to try please msg me. I appreciate you reading this thank you
nzgx beast said:
Sorry for being a noob in advance I really would like to root this phone, and have been trying for like the past 3-4 months trying everything from z4 root the app to hasoon2000's all-in-one toolkit, and I still cannot seem to root it. If anyone thinks they can help me or if you would like to try please msg me. I appreciate you reading this thank you
Click to expand...
Click to collapse
Go read the S-off after 2014 OTA thread under development. All steps, information and links are there.
therreid said:
Go read the S-off after 2014 OTA thread under development. All steps, information and links are there.
Click to expand...
Click to collapse
Also verify the build version that is currently on your phone. I would assume you have the latest OTA (2.19), if so, then therreid is spot on. If you're earlier, then you have a few additional options, but it might be easiest for you to install the OTA and follow those instructions.
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Still dont understand.-.
I've read them but like my drivers apparently aren't installed, my phone isn't recognized on my computer, and this is all confusing lol. Do any of you know where to find like a video to help me
Here are the drivers:
http://forum.xda-developers.com/showthread.php?t=2089508
Okay...
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Click to expand...
Click to collapse
okay so what exactly is s-off? and what do drivers do and how do i know which to get? and how to temp root?
kimba99 said:
actually the root&s-off method described in the "[S-OFF] after 2014-OTA" thread ... should work on (near) all rom/firmware-builds and not just 2.19
Click to expand...
Click to collapse
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Sent from my TouchPad using Tapatalk
puhleez said:
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Click to expand...
Click to collapse
actually temp-root shouldn't go away after reboot at all! ... but rather leave the device in an unstable status (android booted with status-bar, but no lockring and partial screen-flickering going on/off etc) ... temp-root script should QUIT on its own IF it was sueccessful
... and only AFTER THAT ... start rumrunner (which reboots the device like 5-6 times i think). that's at least the way it works in windows.
only as a note: after s-off completed, the device will still be _unstable_ (as temp-root is still active and the device therefore unstable) ... so best would be to flash (thereby: install) a _new rom_ (as desired) directly after replacing the hboot & the recovery
kimba99 said:
actually temp-root shouldn't go away after reboot at all! ... but rather leave the device in an unstable status (android booted with status-bar, but no lockring and partial screen-flickering going on/off etc) ... temp-root script should QUIT on its own IF it was sueccessful
... and only AFTER THAT ... start rumrunner (which reboots the device like 5-6 times i think). that's at least the way it works in windows.
only as a note: after s-off completed, the device will still be _unstable_ (as temp-root is still active and the device therefore unstable) ... so best would be to flash (thereby: install) a _new rom_ (as desired) directly after replacing the hboot & the recovery
Click to expand...
Click to collapse
OK, thought that if reboot took place, temp-root was lost. So, when I ran rumrunner, it would just timeout and fail. I'll try to get the exact details later.
Anyway, thanks for your reply. May try again today using Windows to see if it works any differently.
EDIT: here's what happened under Windows.
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (12/120)
Waiting
Test 2: Booting device
Waiting for ADB (20/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (29/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
just saw above, that you guys referenced the __hasoon2000's all-in-one toolkit__ ... as for root (well, better said: [s-off]) in the "[s-off] after 2014-ota" thread, i wrote to use mdmovers script-kit! ... the hasoon2000 kit might be outdated (in terms of temp-root) ... i didn't check the details, but for clarity, please do AS IT'S WRITTEN down ... do not deviate from the (fairly easy) route given in that thread!
puhleez said:
I tried to make this work on Linux without success. Rumrunner reboots the device causing temp root to go away. Does the windows version do anything differently?
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
I was finally able to get the method oiutlined by kimba99 to work using Linux, but you are correct, the initial adb & fastboot connection tests cause the phone to lose the temp-root and go back to my normal lock screen with ring and icons(in a usable state).
I know i sound conflicted but i tested it several times.
Here is the weirdness.
What finally got it to work was "attempting" using my win8 system. The win8 failed due to windows losing the device. I used drivers from HTC and then used drivers from the link provided. While rumrunner ran I would get a pop-up saying an unrecognized device was plugged in and then rumrunner would timeout being it could no longer talk to the phone. After 3 failed attempts on windows it got late so I rebooted my laptop into Ubuntu so i could use rumrunner to remove the temp-root and make it usable again as it had done 5 previous times.
Suddenly rumrunner was able to go past the root checks. The only difference than before is that while trying on windows my device went from LOCKED to TAMPERED to TAMPERED LOCKED.
Anyways, everything worked as after that just as advertised.
]