Just tried and I got a temp root with Weaksauce from the M8 forums, which allowed me to run firewater for S-Off on the 4.4.2 ota.
1.) Install the necessary drivers
2.) Install and gain temp root with weaksauce, from this thread: http://forum.xda-developers.com/showthread.php?t=2699089
3.) After obtaining Temp root (TuneInRadio will appear in your notification bar if its running) Run Firewater (normal, rooted device method) and your golden: http://firewater-soff.com/instructions/
Make sure to follow all the instructions for Weaksauce and Firewater.
sum182 said:
Just tried and I got a temp root with Weaksauce from the M8 forums, which allowed me to run firewater for S-Off on the 4.4.2 ota.
1.) Install the necessary drivers
2.) Install and gain temp root with weaksauce, from this thread: http://forum.xda-developers.com/showthread.php?t=2699089
3.) After obtaining Temp root (TuneInRadio will appear in your notification bar if its running) Run Firewater (normal, rooted device method) and your golden: http://firewater-soff.com/instructions/
Make sure to follow all the instructions for Weaksauce and Firewater.
Click to expand...
Click to collapse
kewl... @JustinCase
Works great. Returned to full stock 3.06 S-On, took OTA, and ran weaksauce + firewater no problem. Much easier than the original facepalm & htcdev.
pyroguysf said:
Works great. Returned to full stock 3.06 S-On, took OTA, and ran weaksauce + firewater no problem. Much easier than the original facepalm & htcdev.
Click to expand...
Click to collapse
Thanks for the additional confirmation. Yea, this was actually one of the easier unlocks/s-offs I've had in a while. Thanks to the devs of those wonderful programs.
sum182 said:
Thanks for the additional confirmation. Yea, this was actually one of the easier unlocks/s-offs I've had in a while. Thanks to the devs of those wonderful programs.
Click to expand...
Click to collapse
Can confirm this worked for me as well. Anyone figure out a working wifi hotspot solution for us very rare rooted, unlimited, kit kat users? Wireless tether apk seems to fail for me.
Worked fantastic for me! Easiest way to root and s-off yet! Custom romantic now up and running. I used flashify to install TWRP.
HOLY, GOD, THANK YOU. I just did this with my old DNA, worked flawlessly. Even checked for OTA updates right beforehand and it said it was up to date. So this even worked on the newest update. THANK YOU SO MUCH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry guys, I've been away forever and ever.
Does this mean I can once again gain root access for the DNA?!
Edit: Rooted, unlocked.
So happy I found this thread haha.
tried this today with my DNA but can't get my mac to see the device via adb, can anyone help me troubleshoot this? Thanks!!!
dbstudios said:
tried this today with my DNA but can't get my mac to see the device via adb, can anyone help me troubleshoot this? Thanks!!!
Click to expand...
Click to collapse
Debugging enabled?
xxfallacyxx said:
Debugging enabled?
Click to expand...
Click to collapse
Yea it is, I've even tried switching it off and on again and reconnecting the phone and still nothing. ADB does perform the action but comes up with nothing in the list.
dbstudios said:
tried this today with my DNA but can't get my mac to see the device via adb, can anyone help me troubleshoot this? Thanks!!!
Click to expand...
Click to collapse
Same problem here but on a Windows 7 machine. USB debugging enable, most recent windows drivers installed, uninstalled and re-installed. No matter what I do, ADB does not see my phone. Really frustrating because it has worked on this same computer previously before the Kit Kat update.
I can't get this to work. I am S-OFF from old OTA soff method, took the latest OTA now I am relocked and SOFF, but not able to flash any recovery due to relocked status. I can't unlock.
I tired weaksauce method and it says already rooted, but its not. I reset the phone to try again with no luck.
I tried to change the CID and that didnt work.
Tried to run earlier RUU and won't let me. Is there a PH98IMG of the latest OTA?
Thanks.
edit: http://forum.xda-developers.com/droid-dna/help/solved-flash-recovery-relocked-s-off-t2804435
4.42 weaksauce wont work Please help
I can not gain root access S-off on my replacement phone Verizon sent me. Any help would be greatly appreciated. If i have not included enough information my apologies as I normally figure these things out and have not had to post before. If this is not an appropriate thread to post in please redirect me. Also my boot loader is throwing tampered flag but is still locked S-on.
Sweet....Worked here too. Two things for anyone having issues....When you install SuperSU, you don't need to run it. It'll say installation failed if you do, but that's nothing to worry about. Second, after you do the adb reboot, wait 1-2 minutes after the reboot completes before you run the next command. You need to give time for temp root to be regranted.
Time to unlock the bootloader...
---------- Post added at 05:36 PM ---------- Previous post was at 05:02 PM ----------
Ok, so something else. After doing the above, if you run SuperSu it will tell you that you need to update your su binary and recommends you use TWRP to do it. So I cancelled out and installed Rom Installer from the play store and used it to flash TWRP 2.7.1. Then rebooted (not sure if necessary), then reran SuperSU. This time when it prompted me I told it to go ahead and update itself using TWRP. It did just that and all is good now.
Works Like Greased Lightning!!
Thanks SOOOOOO Much for providing this guide for S-Off for all of us who (stupidly) Allowed VZW to push the 4.4 Update to our Droid DNA's!!
This worked So easily, the Very First time! Follow both the weaksauce Guide and the firewater Guide EXPLICITLY and you will have no problems at all! Thanks to all of the devs who made this possible!
Droidel said:
I can't get this to work. I am S-OFF from old OTA soff method, took the latest OTA now I am relocked and SOFF, but not able to flash any recovery due to relocked status. I can't unlock.
I tired weaksauce method and it says already rooted, but its not. I reset the phone to try again with no luck.
I tried to change the CID and that didnt work.
Tried to run earlier RUU and won't let me. Is there a PH98IMG of the latest OTA?
Thanks.
edit: http://forum.xda-developers.com/droid-dna/help/solved-flash-recovery-relocked-s-off-t2804435
Click to expand...
Click to collapse
you dont need to be unlocked to install a recovery.
pack up your recovery image with an android info text document.
use fastboot/ruu mode to install the recovery zip file.
if you really want to use htcdev,you can also change your cid. if 11111111 or 22222222 dont work,try 33333333 or HTC__001(just remember to change it back when youre done)
Ok well i figured out my problem
solomonerwin said:
I can not gain root access S-off on my replacement phone Verizon sent me. Any help would be greatly appreciated. If i have not included enough information my apologies as I normally figure these things out and have not had to post before. If this is not an appropriate thread to post in please redirect me. Also my boot loader is throwing tampered flag but is still locked S-on.
View attachment 2873959
View attachment 2873960
View attachment 2873961
View attachment 2873962
Click to expand...
Click to collapse
I hope this helps. I had to uninstall all updates for tunein radio after that i still could not get supersu to down load the binaries so i installed superuser instead and it worked just fine. By no means am i saying this is the correct way to do it i am just telling you what worked for me.
s off firmware 3.06.605.4
can the above said firmware device be s offed??
ps: im new to xda
thanks for sharing this info. Now im s-off on Android 4.4.2, however... is it possible to flash custom ROMs wiha locked bootloader? that's all i want, otherwise ill just sell the phone and buy a Nexus 5.
Related
I picked up a bolt from a friend and it is apparently still on 1.12.605.9 firmware, never been rooted and still has s-on. How do I root this damn thing because I have tried every site, forum, and I cannot find a download link that works to do the old root method. I rooted my personal bolt and s-off with no problem. But this one is not connected at the moment either so I can't get it to do any ota's to get it up to date. Any help would be appreciated. Thank you in advance.
Sent from my ADR6400L using xda premium
Root Old Software for HTC Thunderbolt
I had the instructions up before I realized the software version being 1.12.605.9.
I'm slow sometimes. =l
I tried doing a search for you, but I really couldn't find anything either.
Hopefully it will push an OTA here shortly and upgrade to 2.11.605.9 or 2.11.605.19 so you can use the revolutionary method.
are you sure the phone is not rooted and running a custom rom based on 1.12.605.9? unless its been turned off and sitting ona shelf it should have OTAed several times from that,as 1.12.605.9 was the first minor update the TB got,from its shipping firmware of 1.12.605.6.
-check your app drawer for the superuser icon
-check hboot for 1.04.2000 eng s-off hboot
if you truly are not allready rooted,im not sure what to think- theres no way a stock phone would have survived that long with no updates. nonetheless,all you need to do is run an RUU for a newer build number. literally anything between what you nave and 2.11.605.5 should get you 1.04 or 1.05 hboot. you dont wantto go newer,as youll then have to downgrade back to 605.5,or youll have to run fre3vo first to temp root.,then run revolutionary.
thunderbolt RUUs:
http://www.filefactory.com/f/c8e2d3df241214b3/
and here:
http://androidforums.com/thunderbol...underbolt-root-unroot-thread.html#post3272390
edit:
if you want to do the old school root,theres a link to the old root method post here:
http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
it should contain a link to jcases original instructions,and i could upload the exploits file is the links are broken.
but,it would prolly be alot easier to just run a newer RUU and then run revolutionary
scotty1223 said:
are you sure the phone is not rooted and running a custom rom based on 1.12.605.9? unless its been turned off and sitting ona shelf it should have OTAed several times from that,as 1.12.605.9 was the first minor update the TB got,from its shipping firmware of 1.12.605.6.
-check your app drawer for the superuser icon
-check hboot for 1.04.2000 eng s-off hboot
if you truly are not allready rooted,im not sure what to think- theres no way a stock phone would have survived that long with no updates. nonetheless,all you need to do is run an RUU for a newer build number. literally anything between what you nave and 2.11.605.5 should get you 1.04 or 1.05 hboot. you dont wantto go newer,as youll then have to downgrade back to 605.5,or youll have to run fre3vo first to temp root.,then run revolutionary.
thunderbolt RUUs:
http://www.filefactory.com/f/c8e2d3df241214b3/
and here:
http://androidforums.com/thunderbol...underbolt-root-unroot-thread.html#post3272390
edit:
if you want to do the old school root,theres a link to the old root method post here:
http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
it should contain a link to jcases original instructions,and i could upload the exploits file is the links are broken.
but,it would prolly be alot easier to just run a newer RUU and then run revolutionary
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I took a picture of the hboot screen, maybe this explain a little more. The phone has a cracked screen so it wasnt used since they first got it not long after release, I guess. I double checked and it is not rooted. I am downloading the 605.5 RUU now and will try that and see what happens. I will report back with results. Thank you for you response.
Sent from my ADR6400L using xda premium
With a 1.04 h boot revolutionary will work for getting s off.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
With a 1.04 h boot revolutionary will work for getting s off.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I tried to use revolutionary but only get "waiting for device". I have the drivers installed because I rooted and got s-off on my other bolt. I am just trying to get this one up to date and fix the screen so I can sell it.
Sent from my ADR6400L using xda premium
I had that problem to when I tried the revolutionary tool. I had to manually input the commands for it to work. The other thing is when the prompt appears asking to launch something for HTC. Don't hit yes or no. Just leave it there.
Sent from my ADR6400L using Tapatalk 2
dizzyman1180 said:
I tried to use revolutionary but only get "waiting for device". I have the drivers installed because I rooted and got s-off on my other bolt. I am just trying to get this one up to date and fix the screen so I can sell it.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
did you forget to enable usb debugging? do you still have the sdk instaLLEd? if so open a cmd window,cd to your adb directory,and then enter "adb devices" if your drivers are working and the phone is in charge only mode,usb debugging on,youll get your serial number back.
you may need to find the device in device manager,and manually update drivers. you can also try rebooting the pc,and different usb cables and ports. uninstall htc sync,pda net,or anything else that can communicate with your phone.
if you need to reinstall them: revoutionary hboot drivers
as the guys said,you dont need to run the RUU. revolutionary will work fine on what you have,i was under the impression your firmware was hboot 1.03
I got it all worked out. Reinstalled the drivers, phone connected and have revolutionary s-off, root and latest firmware. I appreciate everyone's help, we have some awesome ppl in the thunderbolt community. I am definitely learning a lot lately. Thank you again.
Sent from my ADR6400L using xda premium
I'm glad these guys could help you.
I had to send them to you.
Great people in the community for sure.
Thanks guys!
Now to replace your screen, it's not that difficult and you'll have a like new phone!
Google will find someone who'll do it for you or instructions for do-it-yourself.
1st let me say I hope this is the right form to ask this program nor I am not complaining about the developers work my issue is I ran the program (RegawMOD) 3 times with no success, fortunately i haven't bricked my phone yet, but when i re-ran it it shows my phone is unlocked but i haven't acheieved root. What are the steps to relocking the regawMOD until an updated has been released. It was my fault for not reading the entire thread before attempting a root that was not designed for my update. Any thoughts and help would be greatly appreciated.
:highfive:
BTW posted this note within the thread i downloaded the quick root from but i figured it better to come here just also, thanks again.
Your unlocked, Regawmod did what it should have.
Fastboot flash a recovery and you're golden.
Since you rook the OTA Regaw couldn't do it all for you
Sent from my EVO using Tapatalk 2
Rxpert said:
Your unlocked, Regawmod did what it should have.
Fastboot flash a recovery and you're golden.
Since you rook the OTA Regaw couldn't do it all for you
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thanks, just for clarification for me since i am kinda slow
I thought i needed to see the SU app notification to be rooted. Since I didn't see it after i got the "pushing error" i thought it wasn't fully rooted just unlocked. But if all i have to do is download a recovery without SU and it gives me ability to flash i will do that. Thanks again
PSS; I just attempt to run titanium backup and it tells me i don't have root... ???
RamesisX said:
Thanks, just for clarification for me since i am kinda slow
I thought i needed to see the SU app notification to be rooted. Since I didn't see it after i got the "pushing error" i thought it wasn't fully rooted just unlocked. But if all i have to do is download a recovery without SU and it gives me ability to flash i will do that. Thanks again
PSS; I just attempt to run titanium backup and it tells me i don't have root... ???
Click to expand...
Click to collapse
Since you took ota, regaws method did not give you root. The previous post mentioned getting a recovery so you can then in turn push SU or flash a rom with SU built in.
sent from my LTEvo
RamesisX said:
1st let me say I hope this is the right form to ask this program nor I am not complaining about the developers work my issue is I ran the program (RegawMOD) 3 times with no success, fortunately i haven't bricked my phone yet, but when i re-ran it it shows my phone is unlocked but i haven't acheieved root. What are the steps to relocking the regawMOD until an updated has been released. It was my fault for not reading the entire thread before attempting a root that was not designed for my update. Any thoughts and help would be greatly appreciated.
:highfive:
BTW posted this note within the thread i downloaded the quick root from but i figured it better to come here just also, thanks again.
Click to expand...
Click to collapse
I wasn't on the ota and had the same problem. All I had to do from that point was download supersu. The binary was already on my phone as well as Twrp. Then installed busybox.
Sent from my EVO using Tapatalk 2
RamesisX said:
1st let me say I hope this is the right form to ask this program nor I am not complaining about the developers work my issue is I ran the program (RegawMOD) 3 times with no success, fortunately i haven't bricked my phone yet, but when i re-ran it it shows my phone is unlocked but i haven't acheieved root. What are the steps to relocking the regawMOD until an updated has been released. It was my fault for not reading the entire thread before attempting a root that was not designed for my update. Any thoughts and help would be greatly appreciated.
:highfive:
BTW posted this note within the thread i downloaded the quick root from but i figured it better to come here just also, thanks again.
Click to expand...
Click to collapse
The previous poster has got it...install SuperSU and Busybox from the market. Open SuperSU app and update binaries. If that still doesn't work, try rootchecker to see if you really have root access. Check this thread:
http://forum.xda-developers.com/showthread.php?t=1791837
Sent from my EVO LTE
I did all that was suggested and it seems as though I don't have root access just an unlocked phone. Next question how can i relock regawmod and use a different rooting method, or restore to orginal lock status? I know this is a bit much to ask, but i lost here. My orginal Evo root and flashed like crazy with no issues now i am in no mans land it seems with rooting status on 4g lte
RamesisX said:
I did all that was suggested and it seems as though I don't have root access just an unlocked phone. Next question how can i relock regawmod and use a different rooting method, or restore to orginal lock status? I know this is a bit much to ask, but i lost here. My orginal Evo root and flashed like crazy with no issues now i am in no mans land it seems with rooting status on 4g lte
Click to expand...
Click to collapse
If your bootloader is already unlocked, no reason to re lock it...you're halfway there. What software version are you on? Have you checked out zedomax's method for gaining root access?
http://forum.xda-developers.com/showthread.php?t=1671577
Do you have a custom recovery installed (TWRP)? If so, you should be able to flash a stock ROM that already has root.
Sent from my EVO LTE
Regaw was going to work on his unlocker today to update it for the new OTA.
Now that you are unlocked there is absolutely no reason to re-lock it. I will tell you how to do it though:
http://www.youtube.com/watch?v=5yS7yy4XVA4
The smart way to go from here:
All you need to do is setup fastboot on your computer, reboot your phone into fast boot, and push the recovery.img manually.
For step by step instructions check here
http://androidforums.com/evo-4g-lte-all-things-root/597083-ota-update-root-possible-yet.html
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
Rxpert83 said:
Ok I did a little picture tutorial. Sorry they are so small I can re-upload
Here is an example of my "android" folder. Note its named platform tools here because I was meddling in development for a while. The title of the folder doesnt matter. You just need fastboot.exe and your recovery.img in the same folder.
Note, I do not have the recovery in my folder. You will need it. I also have a lot of crap in there you probably wont have
Shift+right click somewhere near the bottom where there's white space and select open command line.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that all you need to do is enter the correct command to flash. Note: You can copy and paste the correct code.
Keep in mine my "android" folder is named differently, so the words in my command prompt may look different. As long as you use the Shift+right click method to open the command prompt you will be in the correct folder
This image may help clear up whats going on:
Click to expand...
Click to collapse
This may help as well
Great!!!! since i am working now i will follow these steps when i home, I will let you know how it works out. Once again thanks for you help it is truly appreciated.
http://androidforums.com/attachment...90-adb-guide-updated-12-05-2011-sdk-tools.zip
That mini-sdk will be everything you need to run fastboot. Really all you need to do is download TWRP, extract the recovery.img, place it in the folder with the rest of the tools, shift right click , open command window there, and then enter the command above
First off, my question is whether im stuck with hboot 2.09 until they release a RUU, or is there a magical way to downgrade?
Sorry, I've got quite the situation to explain.
I was running 2.13.651.1 rooted stock rom + TWRP 2.3, (had hboot 1.12) but I wanted to bust out the new jellybean update. So, I unrooted and attempted to install but it kept booting into twrp and if I used twrp, it gave me an error of assert failed status 7(couldnt find a cid or something) So i flashed over the stock recovery and attempted to upgrade but it failed with a red triangle(!). I then figured it was because it was upset about the build, so I RUU'd down to 1.13.651.1 and the updates worked great. I stopped at 2.13.651.1 and was going to dirtyracun to s-off but i first decided to test the jellybean update. Well I soon realized that i had really screwed up because now Im stuck with hboot 2.09, and there doesnt appear to be anyway to flash an older version. Am i mistaken ?
Its pretty messed up right now. bootloops into the bootloader when its relocked, and carries a security warning. But if i unlock it, it boots up to the os fine.
Also, I noticed that if I try and use the 1.13 RUU , while its unlocked ( i know it doesnt work) , it detects that the firmware version is 2.13. However, if i start the ruu from the bootloader, it detects the firmware as 3.15.. interesting. I wasnt sure if the hboot was skewing the version detection or not.
If any of you geniuses can provide any shed of light, please do.
-Thanks.
P.S , I have a android backup from twrp, but it cant seem to boot after and it fails to mount the sdcard ? When it did complete successfully(once), it wouldnt boot, the screen went black. Even a factory reset didnt seem to fix it, but for some reason it works now if unlocked.
Jessman123 said:
First off, my question is whether im stuck with hboot 2.09 until they release a RUU, or is there a magical way to downgrade?
Sorry, I've got quite the situation to explain.
I was running 2.13.651.1 rooted stock rom + TWRP 2.3, (had hboot 1.12) but I wanted to bust out the new jellybean update. So, I unrooted and attempted to install but it kept booting into twrp and if I used twrp, it gave me an error of assert failed status 7(couldnt find a cid or something) So i flashed over the stock recovery and attempted to upgrade but it failed with a red triangle(!). I then figured it was because it was upset about the build, so I RUU'd down to 1.13.651.1 and the updates worked great. I stopped at 2.13.651.1 and was going to dirtyracun to s-off but i first decided to test the jellybean update. Well I soon realized that i had really screwed up because now Im stuck with hboot 2.09, and there doesnt appear to be anyway to flash an older version. Am i mistaken ?
Its pretty messed up right now. bootloops into the bootloader when its relocked, and carries a security warning. But if i unlock it, it boots up to the os fine.
Also, I noticed that if I try and use the 1.13 RUU , while its unlocked ( i know it doesnt work) , it detects that the firmware version is 2.13. However, if i start the ruu from the bootloader, it detects the firmware as 3.15.. interesting. I wasnt sure if the hboot was skewing the version detection or not.
If any of you geniuses can provide any shed of light, please do.
-Thanks.
P.S , I have a android backup from twrp, but it cant seem to boot after and it fails to mount the sdcard ? When it did complete successfully(once), it wouldnt boot, the screen went black. Even a factory reset didnt seem to fix it, but for some reason it works now if unlocked.
Click to expand...
Click to collapse
yes, i am sorry to say that you are stuck with hboot 2.09.
tekno4ever said:
yes, i am sorry to say that you are stuck with hboot 2.09.
Click to expand...
Click to collapse
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Jessman123 said:
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Click to expand...
Click to collapse
not sure, but i know its coming down the pipe.
Same here
***Tampered***
***Relocked***
Jewel PVT Ship S-Off Rl
CID-SPCS_001
HBoot-2.09.0000
Radio-1.12.11.1119
OpebDSP-V31.1.0.45.0815
eMMC-boot
Oct 18 2012
So far after having the dirty racun take the tamper away when i was @ HBoot 1.12. But being stupid i downloaded the full zip PJ with recovery etc.
I was also panicking.
So here is the deal
The phone is now relocked and has stock recovery which is useless.
What i did was the following.
download the latest recovery file. Open the cmnd window and follow the instructions of how to unlock the bootloader. after you have unlocked the bootloader, restart, and go back into bootloader, it should say unlocked. now in fastboot usb run the (flash) the recovery. Reboot. Then install the rom...
if you need help let me know... but as of now we are stuck with the ***TAMPERED*** ***UNLOCKED**** until someone does a RUU
Jessman123 said:
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Click to expand...
Click to collapse
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Look at your bootloader. Its s-off. Flash your favorite recovery and then your favorite Rom. Or wait for the newest ruu
You should still be s-off so your hboot shouldn't matter too much
Sent from my EVO using xda premium
Well, I was able to get it to re-install my backup successfully. So I am now back where I started before my tampering, just with hboot 2.09. Its fully functional now, I was just eager to get Jellybean .
There is something I've never understood. I *thought* I had unlocked my bootloader when I first got my phone by using HTC's instructions. When I used theirs, it shows Unlocked, however, right below it states S-ON still. I am able to flash whatever I want when it says unlocked, so I assumed it had done its job. But I wasn't sure, so this is why I was going to do the Dirty Racun in the first place.
My goal was simply to achieve the update but keep my precious root, and with all my things left untouched like the typical OTA.
@EVOMIKE025 - I haven't had much time to play directly with Linux, but I have dealt with other Linux devices, so I'm sure I might be competent enough to handle your secrets, but there is only one way to find out! However, I'm kinda nervous of messing with the phone without a RUU available right now. I just couldn't get the OTA to function, and I think it was because of TWRP getting in the way of its reboot. If I have to bite the bullet and re-install everything and my root access, I may do it. I haven't had much time though, this all happened on a sunny day with spare time. Unfortunately a simple upgrade turned into this.
EVOMIKE025 said:
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Click to expand...
Click to collapse
how did you unlock 2.09 hboot with s-off? I accidently hit the install and couldnt stop it from rebooting and installing persistently. Didnt want to brick the phone so i let it go. Now im "dev rooted" and i cant do ****. Can you help me out?
how did you unlock 2.09 hboot with s-off? I accidently hit the install and couldnt stop it from rebooting and installing persistently. Didnt want to brick the phone so i let it go. Now im "dev rooted" and i cant do ****. Can you help me out?
Click to expand...
Click to collapse
Personally, when I wanted to re-lock it, I used "fastboot flash oem-lock" and when I wanted to unlock it again, I flashed the "Unlock_Code.bin" back over that I got from the HTC Dev. That's how i was able to flop around on the locking and re-locking. Don't know if that helps? :fingers-crossed:
guess I'm stuck!
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
bradhary said:
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
Click to expand...
Click to collapse
Unless I've misunderstood android the last 3yrs, RUU has nothing to do with root. (Unless I'm misinterpreting your meaning in 1st paragraph. where it seems you're associating the 2). RUU will not help with root.
Once you're unlocked thru HTC dev, you can fastboot flash custom recovery (TWRP). With custom recovery installed, you can flash superuser (root) binaries and install superuser or superSU.
Check the thread in development by regaw_lienad for more info and file links. Or you can Google chainsDD superuser for his website with the binaries zip (while I'm at it, wow, all us android users have a lot of thanking to do to chainsDD).
Sent from my EVO using xda premium
bradhary said:
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
Click to expand...
Click to collapse
Everything you need to flash recovery and SU is here
Thank you
bigdaddy619 said:
Everything you need to flash recovery and SU is here
Click to expand...
Click to collapse
Got it done! Thanks to all! Especially you my friend, hope I don't leave anyone out! Should I update the superSu? I clicked on it to see if it would open and it did, just asked iff I wanted to update..I really don't want to mess it up allready!
Thanks again, Brad.
PS, It was the new 2.3.3.0 that did it!
SU binary needs to be updated. continue?
bradhary said:
Got it done! Thanks to all! Especially you my friend, hope I don't leave anyone out! Should I update the superSu? I clicked on it to see if it would open and it did, just asked iff I wanted to update..I really don't want to mess it up allready!
Thanks again, Brad.
PS, It was the new 2.3.3.0 that did it!
Click to expand...
Click to collapse
when I hit continue, my phone just does a reboot... Any one..
I think I got it???
Sorry to be a pain! And sorry to the OP for hijacking! Got the wifi to work, phone says it's rooted but the supersu is still out of date and will reboot if I try to update. If anyone has any ideas as to what I could try next, thank you in advance! I will roll like it is as it seems to be working. :good:
bradhary said:
when I hit continue, my phone just does a reboot... Any one..
Click to expand...
Click to collapse
The reboot when updating super user binaries is a known issue introduced in hboot 2.09.....its basically HTC messing with the developers' capabilities of customizing etc....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.pocketables.com/2012/12/...rs.html?utm_source=dlvr.it&utm_medium=twitter
Sent from my EVO using xda app-developers app
EVOMIKE025 said:
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Click to expand...
Click to collapse
Downgrading the bootloader is one of the few ways to make your phone completely, unusably bricked right? If anyone has a way to downgrade 2.09 to 1.19 SAFELY AND WITHOUT MAKING THE PHONE A PERMANENT PAPERWEIGHT or and preferably, not to mention unlikely, s-off 2.0.9, please share and I will be more pleased than a person who won a million bucks.
got it done!
Thanks to everyone I figured it out! I reflashed with the newer superSu, 3.2. all is good, shows good root, backed up and ready to start geeking!
trying to unlock bootloader before I root, however the htcdev site is giving me an error. MID not allowed, error 160. I am 100% sure I copied the token and followed their instructions 100%. Using Verizon HTC one Max version
Okay with some searching, it seems verizon can't unlock via htcdev. I have to use runrunner. However it also gives me issues. Im running from the same location I would run the fastboot, however im getting an error here too.
USB Debugging is on, im in fastboot mode Bootloader screen on the phone.
Says debugging on? Drivers? no adb connection to device
But I have both of these installed...
If I'm not mistaking the Verizon variant can be unlocked via rumrunner. Check the Rumrunner thread to make sure.
Sent from my HTC0P3P7 using Tapatalk
well I can see my device in adb devices & fastboot devices, however still can't be detected in RumRunner..
1624 5598453
Rydis said:
well I can see my device in adb devices & fastboot devices, however still can't be detected in RumRunner..
Click to expand...
Click to collapse
Same here, i don't know why!
Okay, got rumrunner to see it. Dumb me..didn't swipe to allow the computer footprint access in with usb debuggin ^^
sigh..seems it can't unlock 4.3. Just says im not rooted and quits..dont think im able to root and unlock this device..how terrible..
Rydis said:
trying to unlock bootloader before I root, however the htcdev site is giving me an error. MID not allowed, error 160. I am 100% sure I copied the token and followed their instructions 100%. Using Verizon HTC one Max version
Okay with some searching, it seems verizon can't unlock via htcdev. I have to use runrunner. However it also gives me issues. Im running from the same location I would run the fastboot, however im getting an error here too.
USB Debugging is on, im in fastboot mode Bootloader screen on the phone.
Says debugging on? Drivers? no adb connection to device
But I have both of these installed...
Click to expand...
Click to collapse
Use rumrunner dont use htcdev. Go to android development. Its not that hard if you follow the directions. Im new to the htc world. I have owned samsung galaxy devices up untill about 1 week ago. Good luck. Remeber read read and re read.
OneMAX ⚠VZW⚠ sOFF ~BL-is ?? >ROM? VipE® ? tWRp recoVErY ?
mwebb34 said:
Use rumrunner dont use htcdev. Go to android development. Its not that hard if you follow the directions. Im new to the htc world. I have owned samsung galaxy devices up untill about 1 week ago. Good luck. Remeber read read and re read.
OneMAX ⚠VZW⚠ sOFF ~BL-is ?? >ROM? VipE® ? tWRp recoVErY ?
Click to expand...
Click to collapse
read my last post. RumRunner doesn't work with latest 4.3 Verizon HTC One Maxes. Neither does Firewater. Only 4.2 And you can't downgrade to 4.2. It will brick your device.
Rydis said:
read my last post. RumRunner doesn't work with latest 4.3 Verizon HTC One Maxes. Neither does Firewater. Only 4.2 And you can't downgrade to 4.2. It will brick your device.
Click to expand...
Click to collapse
Well....i got my vzw one max about a week ago and it came stock 4.3 it took me awhile but i used rumrunner and i never had any problems at all. Sorry you are having issues i hope you get it.
OneMAX ⚠VZW⚠ sOFF ~BL-is ?? >ROM? VipE® ? tWRp recoVErY ?
mwebb34 said:
Well....i got my vzw one max about a week ago and it came stock 4.3 it took me awhile but i used rumrunner and i never had any problems at all. Sorry you are having issues i hope you get it.
OneMAX ⚠VZW⚠ sOFF ~BL-is ?? >ROM? VipE® ? tWRp recoVErY ?
Click to expand...
Click to collapse
how did you get runrummer to work? It went through all the the steps, then when it got to the end, said device isn't rooted. How did you get around that?
Not to be rude. Im sure it will work. You might need to read again and write down the steps on paper thats what i had to do. Also go to android development and those guys will help you thats what i had to do.
mwebb34 said:
Not to be rude. Im sure it will work. You might need to read again and write down the steps on paper thats what i had to do. Also go to android development and those guys will help you thats what i had to do.
Click to expand...
Click to collapse
There are no actual steps besides things you need anyway.
Drivers..HTC Sync uninstalled. USB Debugging and no lock screen. Run program.
But it is trying to S-off but it can't because its not rooted..and its not rooted because its locked. There is no guide that shows how to unlock with rumrunner.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as evident by the picture..
Rydis said:
There are no actual steps besides things you need anyway.
Drivers..HTC Sync uninstalled. USB Debugging and no lock screen. Run program.
But it is trying to S-off but it can't because its not rooted..and its not rooted because its locked. There is no guide that shows how to unlock with rumrunner.
Click to expand...
Click to collapse
Go to origanl android development the guide is over there.
Rydis said:
as evident by the picture..
Click to expand...
Click to collapse
did you uncheck fastboot in power settings before running rumrunner?
I have the VZW One Max I played with firewater on mac and firewater & rumrunner on linux ubuntu 32&64 bit and linux mint to no avail. Then I tried rumrunner on windows and was all done in 15 minutes.
Yes, fastboot is disabled
Rydis said:
Yes, fastboot is disabled
Click to expand...
Click to collapse
and you extracted before running soju.exe?
Disabled all antivirus and firewalls?
joshm.1219 said:
and you extracted before running soju.exe?
Click to expand...
Click to collapse
Yep, its extracted (in same directory as my adb). Fastboot Disabled. No antivirus/firewall. USB Deubgging is on, using original cable. Using Latest Verizon version of rumrunner. Installed HTC sync for drivers, then uninstalled sync.
Did you install android sdk
OneMAX ⚠VZW⚠ sOFF ~BL-is ?? >ROM? VipE® ? tWRp recoVErY ?
Has anyone been able to root the 4.4.2 ota update on the dna?
You are unlocked and s-off, just flash a custom recovery of your choice and flash the supersu zip
Sent from my HTC6500LVW using XDA Free mobile app
Jrsoccer did you get rooted yet?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
CHRIST STARZ said:
Jrsoccer did you get rooted yet?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I cant seem to get rooted. I don't know of any workaround for the root on 4.4.2 for the dna.
Have you tried Uzephi's suggestion?
Follow this
jrsoccer20 said:
I cant seem to get rooted. I don't know of any workaround for the root on 4.4.2 for the dna.
Click to expand...
Click to collapse
Do a google search for firewater s-off HTC.
I just got a DNA, it is stock with 4.4.2. I was able to temp root and s-off with the firewater method. Follow these instructions to the letter (type your adb commands as they appear on the instructions..if it looks like a space in between letters then it is a space) Also, follow the Weaksauce method on Firewaters page. It is the second set of instructions.
Make sure firewater is in your adb directory too and you should have no problem.
Now I need to flash a custom recovery and install a stock rooted rom
I posted this in the rumrunner thread but also wanted to post here too to make sure you guys see it that are having problems getting s-off with the stock 4.4.2.
I just got s-off using weaksauce+firewater. I think it was the cables that prevented me from getting it to work before. I was using the cable that came with the phone and the one that came with my rezound and they didn't work. So I decided to get all the cables I have and try all of them to see if by chance it would work, and the first cable I tried worked like a charm. So don't give up guys, keep trying until it works because it does with 4.4.2 stock.
Need help not sure what is wrong
I am thinking about re-flashing using RUU but not sure that would help. I can not gain root access S-off on my replacement phone Verizon sent me. Any help would be greatly appreciated. If i have not included enough information my apologies as I normally figure these things out and have not had to post before. If this is not an appropriate thread to post in please redirect me. Also my boot loader is throwing tampered flag but is still locked S-on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm interested to know how to root the DNA as i am on stock 4.4.2
Coming from a 4.4.2 Moto x where the only root was to temporary through adb commands, where root is disabled on reboot.
Is the DNA method the same? root disabled on reboot?
jwalkinc said:
Do a google search for firewater s-off HTC.
I just got a DNA, it is stock with 4.4.2. I was able to temp root and s-off with the firewater method. Follow these instructions to the letter (type your adb commands as they appear on the instructions..if it looks like a space in between letters then it is a space) Also, follow the Weaksauce method on Firewaters page. It is the second set of instructions.
Make sure firewater is in your adb directory too and you should have no problem.
Now I need to flash a custom recovery and install a stock rooted rom
Click to expand...
Click to collapse
Can't get supersu to work after I install weaksauce.
Root
jwalkinc said:
Do a google search for firewater s-off HTC.
I just got a DNA, it is stock with 4.4.2. I was able to temp root and s-off with the firewater method. Follow these instructions to the letter (type your adb commands as they appear on the instructions..if it looks like a space in between letters then it is a space) Also, follow the Weaksauce method on Firewaters page. It is the second set of instructions.
Make sure firewater is in your adb directory too and you should have no problem.
Now I need to flash a custom recovery and install a stock rooted rom
Click to expand...
Click to collapse
I can get weaksauce to say the phone is rooted but i cant get supersu to work. Just keeps saying it failed. I was able to install cwm and have the custom recovery but i still dont seem to be rooted. I cant get su commands to work in adb.
jrsoccer20 said:
I can get weaksauce to say the phone is rooted but i cant get supersu to work. Just keeps saying it failed. I was able to install cwm and have the custom recovery but i still dont seem to be rooted. I cant get su commands to work in adb.
Click to expand...
Click to collapse
U have to flash the one in recovery. Google super su and the latest apk download will pop up. Flash that in recovery And u should b golden
Actually if u have recovery just Flash a rooted Rom. Good to go.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
jrsoccer20 said:
Can't get supersu to work after I install weaksauce.
Click to expand...
Click to collapse
What type of errors are you receiving?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
An update
solomonerwin said:
I am thinking about re-flashing using RUU but not sure that would help. I can not gain root access S-off on my replacement phone Verizon sent me. Any help would be greatly appreciated. If i have not included enough information my apologies as I normally figure these things out and have not had to post before. If this is not an appropriate thread to post in please redirect me. Also my boot loader is throwing tampered flag but is still locked S-on.
View attachment 2869038
View attachment 2869039
View attachment 2869040
View attachment 2869050
Click to expand...
Click to collapse
Not sure why but after reverting to an older version of tune in radio and clearing the cache the weak sauce work around started working. But i cannot update the binaries on supersu. when i open supersu two pop ups come on top the first i haven't been able to read and the second is to update binaries it fails the update however and says reboot and try again i have tried several times to correct this with no succes help would be greatly appreciated because at this time i am seriously contemplating destroying this phone and calming insurance. I think Iwould rather have no phone then a stock phone.