Hello guys,
I apologise if I have created a duplicate thread for this issue-but I HAVE looked everywhere to find a solution to this. I am not a 100% expert so please excuse me if I am being a time-wasting nerd.
However, in a few words, the problem I am having is:
I bought HTC DROID DNA (from the states-brand new) and I managed to unlock the bootloader (S-Off) using the info from these threads and for some really silly reason I decided and managed to relock it. Now it is showing ''Relocked'' and ''S-ON''.
I have tried everything I could find so far to unlock the bootloader (i.e. S-Off) (rumrunner,moonshine, traditional method(since I ve got the original unlock token)).
Can anyone please, please let me know how to S-Off as I would like to install a custom ROM since I can't get any updates in the UK-(which I don't see coming anytime soon anyway.)
Thanks very much.
Harry
stifer said:
Hello guys,
I apologise if I have created a duplicate thread for this issue-but I HAVE looked everywhere to find a solution to this. I am not a 100% expert so please excuse me if I am being a time-wasting nerd.
However, in a few words, the problem I am having is:
I bought HTC DROID DNA (from the states-brand new) and I managed to unlock the bootloader (S-Off) using the info from these threads and for some really silly reason I decided and managed to relock it. Now it is showing ''Relocked'' and ''S-ON''.
I have tried everything I could find so far to unlock the bootloader (i.e. S-Off) (rumrunner,moonshine, traditional method(since I ve got the original unlock token)).
Can anyone please, please let me know how to S-Off as I would like to install a custom ROM since I can't get any updates in the UK-(which I don't see coming anytime soon anyway.)
Thanks very much.
Harry
Click to expand...
Click to collapse
Why don't you look at the sticky at the top of the Q&A section. It is the same section you posted your question in!
RLGL said:
Why don't you look at the sticky at the top of the Q&A section. It is the same section you posted your question in!
Click to expand...
Click to collapse
I have. I tried to do what it says there, i.e. CID shows 1111111 and then trying to flash the unlock token but it is not working, it says Error for some reason.
stifer said:
I have. I tried to do what it says there, i.e. CID shows 1111111 and then trying to flash the unlock token but it is not working, it says Error for some reason.
Click to expand...
Click to collapse
tried firewater?
RLGL said:
tried firewater?
Click to expand...
Click to collapse
Thanks, I have just tried that, but get stuck at ''su'' step. I 've looked it up and it says that you need some sort of temp root? which I don't understand what exactly it is. So still stuck.
stifer said:
Thanks, I have just tried that, but get stuck at ''su'' step. I 've looked it up and it says that you need some sort of temp root? which I don't understand what exactly it is. So still stuck.
Click to expand...
Click to collapse
it took 30 seconds to find the following using the search function:
Default [Guide] Firewater S-Off
Disclaimer
License: Firewater S-Off is the result of many hours of hard work by beaups and fuses. The firewater binaries you download may not be shared, rehosted, bat’d, integrated into a one-click, repackaged, hotlinked, or otherwise distributed or reused. The source code and methods in firewater are closed and private.
Temproot is a hack-up build of android_run_root_shell which appears to be a work of hikezoe and fi01. Original source can be downloaded HERE, our modified mess will be made available on this website soon.
This software is provided free of charge for personal non-commercial use. For commercial use or redistribution a WRITTEN agreement with the authors is required.
Support: support for firewater s-off is available at #firewater on the freenode and andirc networks. Please make sure you meet all of the requirements before contacting support.
Official website: http://firewater-soff.com/
Welcome to Firewater
What firewater can do for you:
S-Off your HTC device
Unlock yout bootloader
There are two methods which can be used to achieve S-Off:
Method n.1: to be used with and HTCDev unlocked/rooted device;
Method n.2: temp-root method, to be used if you don't want to unlock your device through HTCDev (it may not work with all devices);
Prerequisites
Working adb on your PC (Windows, Linux, OSX, etc. are all supported);
HTC drivers installed and working
HTC sync removed (not closed - REMOVED)
All other phone software removed or disabled (Samsung Kies, PDANet, etc.)
A working internet connection on your device (Wifi, 3G, 4G, etc. are all supported). There is no way around this requirement, don’t ask;
USB debugging enabled on your device;
Your device must be HTCDEV unlocked/rooted or have a working temproot. A temproot that works with many modern (not all) HTC devices is provided below;
Do not attempt to run firewater from a terminal emulator on your device. You MUST use adb along with a PC;
A supported device. Firewater *should* work with most modern QUALCOMM based HTC devices, including (but not limited to) the HTC One, HTC Droid DNA, HTC One S, HTC One Max and many others.
Instructions: method n.1 (normal, rooted device method)
Once you confirm you meet the above pre-requisites, it’s time to get started.
Ensure device is booted to android with usb debugging enabled
USB 2.0 ports are preferred. You should not be connected using any hubs which may cause connectivity issues;
Ensure that lock screen security is disabled on your device (no passcode lock, no pattern lock, no face lock);
Download Firewater Search the download from the official site;
Push, prepare and execute Firewater:
Code:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with;
Allow the exploit to do its work;
Profit.
Instructions: method n.2 (temp-root method)
This method may allow firewater to work on a fully stock/HTCDev locked device. This method is being provided as a convenience. Do NOT seek support if this temproot does not work for you.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred. You should not be connected using any hubs which may cause connectivity issues;
Ensure that lock screen security is disabled on your device (no passcode lock, no pattern lock, no face lock);
Download firewater Search the download from the official site;
Download temproot Search the download from the official site;
Push, prepare and execute temproot and Firewater:
Code:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb push temproot /data/local/tmp
adb shell
chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/firewater
/data/local/tmp/temproot
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with;
Allow the exploit to do its work;
Profit.
Donate
Donate to Firewater developers
Donate to me (if you appreciate the guide; thank you!)
Thanks for that. I did try that, and now it says '' Tampered'' and ''Relocked'' and ''S-ON''. I don't understand why this is happening.
I had a similar issue. To resolve, I used the PC to RUU back to stock then started over with firewater.
Good luck.
Icyman said:
I had a similar issue. To resolve, I used the PC to RUU back to stock then started over with firewater.
Good luck.
Click to expand...
Click to collapse
Thanks again for your reply. I tried that just now. Still showing tampered, relocked and s-on. This is unbelievable. I don't think I 'll ever be able to unlock this bootloader and I don't know why!c
stifer said:
Thanks again for your reply. I tried that just now. Still showing tampered, relocked and s-on. This is unbelievable. I don't think I 'll ever be able to unlock this bootloader and I don't know why!c
Click to expand...
Click to collapse
Did you use the unlock bin from HTC?
Icyman said:
Did you use the unlock bin from HTC?
Click to expand...
Click to collapse
The first time I unlocked it which was almost a year ago I used the unlock key, tried the same two weeks ago but did not succeed. I hope this is the answer to what you asked me. (sorry if I misunderstood- I am not an expert)
thanks very much Icyman
stifer said:
The first time I unlocked it which was almost a year ago I used the unlock key, tried the same two weeks ago but did not succeed. I hope this is the answer to what you asked me. (sorry if I misunderstood- I am not an expert)
thanks very much Icyman
Click to expand...
Click to collapse
You need to use the same bin file after ruu.
But I think firewater should work too.
I used firewater on 4 phones. I only had problems when I missed a step. Try again from the beginning. From stock after ruu.
Icyman said:
You need to use the same bin file after ruu.
But I think firewater should work too.
I used firewater on 4 phones. I only had problems when I missed a step. Try again from the beginning. From stock after ruu.
Click to expand...
Click to collapse
Hi Icyman, That is what I did, I flashed the original RUU and then deactivated fast reboot, enabled debug. mode, installed weaksauce-1.01 and finally went ahead with firewater. (device always hungs with firewater in the end and I have to hold the power button down for 60s as it says-not sure if that makes a difference)
Will try again as you suggest though.
I really appreciate your help. Thanks very much.
stifer said:
Hi Icyman, That is what I did, I flashed the original RUU and then deactivated fast reboot, enabled debug. mode, installed weaksauce-1.01 and finally went ahead with firewater. (device always hungs with firewater in the end and I have to hold the power button down for 60s as it says-not sure if that makes a difference)
Will try again as you suggest though.
I really appreciate your help. Thanks very much.
Click to expand...
Click to collapse
I never used weaksauce on DNA. Maybe that's the problem.
Icyman said:
I never used weaksauce on DNA. Maybe that's the problem.
Click to expand...
Click to collapse
That's the only way I can apply temproot and then firewater, I can't find the original temproot file anywhere and I thought that weaksauce is the updated version of the temproot file. If you could send me the temproot file somehow that would be great,-just to see if it could work...
Any further advice guys? Please?!!! I've got this phone but the outdated software makes it useless.
Related
I tried a while ago to unlock my bootloader using HTCDev when it first came out, would get to the part where the confirmation screen should pop up on your phone screen to unlock the bootloader but the screen never showed after multiple attempts, so frustrated, I gave up and told my self I'd come back later. Well later came around a few days ago and I attempted to unlock the bootloader again with the same results as the first time, get to the point where I'm supposed to confirm on my phone screen but it never shows. Did some research to find out the OTA version of the update to ICS could have possibly been the problem, but before I went any further I did a full backup of my phone using Carbon, then did a factory reset from the fastboot menu. Now the problem is, after I did the factory reset my computer no longer recognizes my phone when I plug it in. It can't find HTC sync on my computer even though it is, adb devices shows nothing, same with fastboot devices in fastboot mode. My computer recognized the phone just fine up until the factory reset. So I guess my question is, what caused this to happen and how can I fix it? Also, maybe some help unlocking my bootloader? I think I have to flash the RUU but my phone is 2.95.651 and I don't think it lets you go backwards unless you are S-OFF?
Edit: I guess I should mention that I've tried uninstalling and reinstalling the HTC drivers, usb debugging is enabled and Fast Boot in the power options is disabled, I'm also using the USB cord supplied with my phone, tried different USB ports, performed a second factory reset, made sure all my SDK stuff was up to date, and scoured these forums for 2 days now trying to figure it out (apologies if I missed the one thread with all the answers I need, I did try though). Additionally, in fastboot when I plug in my USB cord it switches to fastboot usb, but nothing shows up on devices, which I find really odd.
Anybody have any ideas/solutions for this?
Yep,
http://androidforums.com/showthread.php?p=5810229
I used srs root to gain a root shell followed scotty85's instructions to set mainver low via adb shell then used the brick downgrade hboot method and followed it up with 1.13 ruu and finished with revolutionary
Post #50 is my instructions and scotty85 are a few posts back
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
embersanenders said:
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
Click to expand...
Click to collapse
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
thewraith420 said:
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure if they use the same hboot or not. I was able to flash 2.89 RUU in the temproot state on hboot 1.58.0000. After the flash I retried unlocking the bootloader through HTCdev and it worked flawlessly. Then I was able to root it and juopnutbear s-off, which applied juopnutbear hboot 1.58.5858. It seems like temprooting the phone using your method and flashing a 2.89 RUU might be the workaround for people who have trouble using HTCdev due to the OTA update.
I should also mention someone suggested this method on phandroid forums (scott actually, I believe) on a different thread and so I tried it. I was going to link his post here but I haven't met the link post requirement yet. So as a disclaimer, this isn't my idea, it just worked so I posted here.
Now that I'm home from work I figured I could give a more detailed list of what I did to root my Evo 3D, I feel the information above gets a little confusing with so many different places to go. As previously stated I had trouble unlocking my bootloader using HTCdev, it would get to the step where you confirm on your phone the unlock but never show up, I found this was usually caused by updating your phone to ICS using the OTA as compared to an RUU. Somehow something gets messed up and your phone never wants to confirm, hopefully this will help people who don't want to brick/downgrade hboot in order to be able to root their phones but can't unlock from HTCdev do to this error. Anyway, on to it.
1. Download SRSRoot
A 2.89 RUU
The files from [Guide] Quick And Dirty Evo 3D/V Root & S-OFF (Sprint and Virgin Mobile Only)
2. Run SRSRoot
3. SmartRoot
4. Follow the steps until your phone restarts and you just have a status bar at the top (this is your 'temproot')
5. Close SRSRoot (you may have to kill in the task manager, or at least I did to get it to completely quit mid-steps)
6. Navigate to the folder where the files from the 'QnD' guide and open the cmd link in the Root folder.
7. Type, or copy & paste the following in order (not the stuff in brackets like this, these are notes);
adb devices (should return your phones serial number, indicating drivers are working, and you're connected)
adb push misc_version /data/local/tmp/misc_version
adb shell (should change your prompt to a #, if not, have your phone awake and watch the screen to grant superuser permissions when you enter su (not likely applicable here))
chmod 777 /data/local/tmp/misc_version (have your phone awake and be watching it, in case superuser needs you to grant permission (again, not likely applicable))
/data/local/tmp/misc_version -s 1.00.000.0
exit (exit again if your prompt changes to a $)
8. Run your 2.89 RUU exe (it should run and reinstall 2.89 to stock, you may lose information, unsure about that though, so back ups are always recommended)
9. Restart your phone after the install if it doesn't happen automatically
10. Retry unlocking using HTCdev method
Hopefully at this point the bootloader actually unlocks for you and you can start at Step 2 of the 'QnD' guide to get root access and S-Off.
Big thanks to thewraith420 for the temproot method and scotty85 over at phandroid for the mainver change directions.
The reason I asked if 2.89 used the 1.58 hboot is just to further understand why it worked I think that setting the mainver is what let you run the ruu. And it didn't complain about the hboot because they use the same one. Nicely done getting the info together.
Sent from my PG86100 using Tapatalk 2
misc_version location
embersanenders said:
adb push misc_version /data/local/tmp/misc_version
Click to expand...
Click to collapse
I was encountering the same issue as you for the HTC bootloader unlock, so thanks so much for this info, it worked like a charm. It might be helpful for others to know that you can find the misc_version referenced by downloading the file scotty85 mentions in his post on guide-how-manually-downgrade-firmware-build-6-01-605-05 (Sorry, I'm unable to post the link)
Mod edit: Firewater has been shut down server-side and is no longer supported. Try Sunshine.
It claims to S-off any HTC device that is rooted/unlocked.
*Works with Hboot 2.47
Home
welcome to firewater
what firewater can do for you:
S-OFF Your HTC device
Unlock your bootloader
Prerequisites
Working adb on your PC. Yes, that means OS X, linux, Windows, etc. are all supported.
HTC drivers installed and working
HTC sync removed (not closed – REMOVED)
All other phone software removed or disabled (Samsung Kies, PDANet, etc.)
A working internet connection ON YOUR DEVICE - wifi, 3g, 4g, etc. are all supported. There is no way around this requirement, don’t ask.
USB debugging enabled on your device
Your device must be HTCDEV unlocked/rooted or have a working temproot. A temproot that works with many modern (not all) HTC devices is provided below.
Do not attempt to run firewater from a terminal emulator on your device. You MUST use adb along with a PC.
A supported device. firewater *should* work with most modern QUALCOMM BASED HTC devices, including (but not limited to) the htc one, droid dna, one s, one max, and many others.
Instructions (normal, rooted device method)
Once you confirm you meet the above pre-requisites, it’s time to get started.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred.
You should not be connected using any hubs which may cause connectivity issues
Ensure that lock screen security is disabled on your device.
no passcode lock
no pattern lock
no face lock
Download firewater HERE - _http://firewater-soff.com/firewaterdownload-3
Push, Prepare, and Execute firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with
Allow the exploit to do its work.
Profit
Instructions (temp-root method)
This method may allow firewater to work on a fully stock/htcdev locked device. This method is being provided as a convenience. Do NOT seek support if this temproot does not work for you.
Ensure device is booted to android with usb debugging enabled.
USB 2.0 ports are preferred.
You should not be connected using any hubs which may cause connectivity issues
Ensure that lock screen security is disabled on your device.
no passcode lock
no pattern lock
no face lock
Download firewater HERE - _http://firewater-soff.com/firewaterdownload-3
Download temproot HERE - _http://firewater-soff.com/temprootdownload
Push, Prepare, and Execute temproot and firewater:
adb reboot <–important!!!!
adb wait-for-device push firewater /data/local/tmp
adb push temproot /data/local/tmp
adb shell
chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/firewater
/data/local/tmp/temproot
/data/local/tmp/firewater
Agree to the terms and conditions you are prompted with
Allow the exploit to do its work.
Profit
_http://firewater-soff.com/instructions/
ps: i am not a member of firewater team
Support
Support for firewater s-off is available at #firewater on the freenode and andirc networks. Please make sure you meet all of the requirements before contacting support.
Click to expand...
Click to collapse
For those in HBOOT 2.49, please revert to stock 1.19.xxx ROM and try this - more instructions http://forum.xda-developers.com/showthread.php?t=2765383
LOLZ
worked a treat, many thanks, cheers again
DANIELWHITT said:
worked a treat, many thanks, cheers again
Click to expand...
Click to collapse
Good to know mate, so your hboot is version 2.47 which you were not able to unlock before. is that correct?
pradeepvizz said:
Good to know mate, so your hboot is version 2.47 which you were not able to unlock before. is that correct?
Click to expand...
Click to collapse
I was s off in the old hboot but put it back to stock for a repair, once on the new h boot rumrunner wouldn't work, however this did and an awful lot faster as well.
DANIELWHITT said:
I was s off in the old hboot but put it back to stock for a repair, once on the new h boot rumrunner wouldn't work, however this did and an awful lot faster as well.
Click to expand...
Click to collapse
Now you are lucky! when you say new hboot, whats the version please? i suppose its 2.47 and also is your phone the international unlocked model T6UL ?
pradeepvizz said:
Now you are lucky! when you say new hboot, whats the version please? i suppose its 2.47 and also is your phone the international unlocked model T6UL ?
Click to expand...
Click to collapse
Hboot is 2.47 and int one max t6up
DANIELWHITT said:
Hboot is 2.47 and int one max t6up
Click to expand...
Click to collapse
Thanks!
help
I can't seem to get the temp root to work , I have a verizon HTC one 4.3 , last 2 commands are not working for me ,anyone mind helping me out via PM
It worked!!!
Thanks a lot! It worked like a charm...
Tried rumrunner but without success. Firewater did it in under 30 seconds! Amazing!
I have a German Telekom based One Max with 2.46 hboot (T6UL).
Thanks for your work!
OMG! Thank you so much. i have max one UK hboot 2.47 and this worked in less that 2 mins. now s-off'd
thank you
Tampered message also gone too!
will relock now and see if fingerprint scanner enables.
:laugh:
Edit: re-locked bootloader and now fingerprint scanner works too! also if i unlock, i dont ever get the tampered message again!
thank you so much.
has anyone tested on the HTC One? i dont see a thread there for that but OP says that it should work
Worked like a charm on HTC One (m7ul/International) - ****ing speedy and easy - once I dusted off my adb hahaha.
sns0582 said:
I can't seem to get the temp root to work , I have a verizon HTC one 4.3 , last 2 commands are not working for me ,anyone mind helping me out via PM
Click to expand...
Click to collapse
Use rumrunner on VZW One Max, worked like a charm for me. Fully bone stock when I ran it, worked first try.
Sent from my HTC One Max
thank you
verizon htc one 4.3 hboot 1.55 want temproot
I tried the commands to temp root ,not working on my HTC one , any ideas if it's just I have files in wrong area , I have them in my adb folder ,
sns0582 said:
I tried the commands to temp root ,not working on my HTC one , any ideas if it's just I have files in wrong area , I have them in my adb folder ,
Click to expand...
Click to collapse
is your device must be HTCDEV unlocked?
pradeepvizz said:
is your device must be HTCDEV unlocked?
Click to expand...
Click to collapse
Yes... Your device must be HTCDEV unlocked and rooted.
Worked like a charm on my International One Max, thank you!
im trying to temp root to s off and unlock
pradeepvizz said:
is your device must be HTCDEV unlocked?
Click to expand...
Click to collapse
. If I read correctly it states I need to temp root to s-off , is there a way to HTC dev unlock 4.3 hboot 1.55 on Verizon,
[S-OFF] after the 2014-OTA ... the incredible _has_ been achieved & is fully working
You might not believe me pals, BUT the incredible and unbelievable HAS BEEN achieved!!!
Full radio [S-OFF] ... on a previously [S-ON & LOCKED]
Droid Incredible 4G LTE - with 2014-OTA (ver. 2.19.605.2)
Credits and terms:
This is NOT my own exploit ... but rather accomplished with the guidance from team "FacePalm" (namely: beaups & dr_drache) ... Full testing and 1st run by myself only ... actual [S-OFF] used the "rumrunner universal" exploit ... but needs a prior TEMP-ROOT (i used the " Inc4GUnlockV61-Windows.zip" kit by mdmower available in our Dinc4G-dev section, link added below) .
As usual: While this process shouldn’t be too risky, bricks can happen. None of me or the actual coders will be accountable. => If you are worried, don’t do it. <=
Again a rather simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, it's not my own work ... i just pass the details along, but still DO NOT ... steal, repackage, 1-click, or whatever method described herein ... for the rest: all disclaimers from "rumrunner.us" do apply!!!
TEMP-ROOT (at least) ... is needed, without it the exploit will NOT work!!! (at least no need for supercid :cyclops ... apart from that, both parts (temp-root & actual s-off exploit) work on Linux _and_ Windows *cough*
1) Once you have confirmed you have "Temp-Root" on your 2.19.605.2 fireball:
http://forum.xda-developers.com/showthread.php?t=2214653 ... for the temp-root script (by mdmower)
2) Download the HTC Universal RUMRUNNER (0.5.0) and unzip it in your working directory:
http://rumrunner.us/downloads-2/
3) follow the RUMRUNNER instructions _closely_ as listed at:
http://rumrunner.us/instructions/
4) wait for a ... longer time until ... rumrunner finishes with: "rumrunner done! hope you enjoyed the rum!"
you are now proper: radio [S-OFF] on your 2.19.605.2 fireball
OPTIONAL:
5) flash ENG-hboot 1.15.1111 ... obtainable from DirtyRacun webpage:
http://unlimited.io/fireball.htm
6) flash custom recovery (e.g. TWRP 2.6.3.0h ... the updated KK4.4 capable version from MDMOWER)
http://mdmower.cmphys.com/category/fireball/
(note that the recent 2.6.3.0k-m (currently?) cannot backup/restore "android-secure" anymore, but 2.6.3.0h is also KK4.4-ready & still can do it) ... ... link to TWRP2.6.3.0h in 2nd post
mdmower fixed this issue in TWRP2.6.3.0.n from 2014-03-03
7) reboot ... ENJOY & REJOICE
8) hit the THANKS-button below
:laugh::laugh::laugh: if it helped you (to achieve the unachievable :laugh::laugh::laugh
thanks for reading ........... (thx again to dr_drache & beaups tips and guidance, temp-root script by mdmower & s-off exploit by rumrunner, 1st testing of this combination "me, myself & i" => SUCCESSFUL)
...
6b) linked the "mdmower: TWRP2.6.3.0h" _only_ for convenience as it is currently NOT available from mdmowers site: (_last_ version able to backup the _AndSec-partition_ as well / already KK4.4-capable)
link remoded as this issue was FIXED by mdmower in his recent TWRP2.6.3.0n build from 2014-03-03
spacer ... just in case ^^
Gonna try it this weekend! Thanks!!!!!
I'm going to give it a try tonight. Thanks!!!!!!!!!!
Sent from my Incredible 4G LTE using XDA Premium 4 mobile app
kimba99 said:
8) hit the THANKS-button below :laugh::laugh::laugh: if it helped you (to achieve the unachievable) :laugh::laugh::laugh
Click to expand...
Click to collapse
Already s-off, but this is fantastic news for those who are not (yet). Thanks!
Sent from my Fireball using Xparent Blue Tapatalk MegaSuperb Pro
I haven't be able to find Dinc4G_UnlockV61-Windows.zip Any chance someone can point me there?
I think you meant http://forum.xda-developers.com/showthread.php?t=2214653
I just got done with it. I had to run it a couple times. It failed the first time around. But the phone is now s-off
Thanks,
Here you go.
http://forum.xda-developers.com/showthread.php?p=39763697
Sent from my ADR6410LVW using xda app-developers app
@tj13 & @spazmcghee ... yep, that's the right one ... it was getting late yesterday night, but i gonna add the link to the first post in case other ppl need to find it as well.
kimba99 said:
@tj13 & @spazmcghee ... yep, that's the right one ... it was getting late yesterday night, but i gonna add the link to the first post in case other ppl need to find it as well.
Click to expand...
Click to collapse
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
tj13 said:
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
Click to expand...
Click to collapse
Yes.....that is mdmower's unlock script.
tj13 said:
The name of the temp root I used is Inc4GUnlockV61-Windows.zip . I believe this is actually the file name you meant to use. I searched for Dinc4G_UnlockV61-Windows.zip and nothing came up.
Click to expand...
Click to collapse
yeah, right ... seems like i renamed the script after download (quite some while ago), corrected the name in the start-post & ... added a remark about TWRP-2.6.3.0h
I wasn't able to make this work. Anyone else able to? Never appeared to achieve root. Guessing it's because the rumrunner rebooted the device. Tried the Linux version of mdmower script for temp root. Already updated to latest OTA.
Sent from my TouchPad using Tapatalk
puhleez said:
I wasn't able to make this work. Anyone else able to? Never appeared to achieve root. Guessing it's because the rumrunner rebooted the device. Tried the Linux version of mdmower script for temp root. Already updated to latest OTA.
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
It worked for me. You need the temp root script to successfully do the temp root. The phone will appear to hang on boot after you have temp root. Once s-off is achieved you will need to do a factory reset.
The process does take a long time and several reboots. The PC you are working from also needs internet. The software unlocks the boot-loader. I believe it needs to obtain the unlock code from htcdev.com.
One more thought. If you run the issued the command "adb devices" does your device show up. If it doesn't you need to install the drivers.
tj13 said:
It worked for me. You need the temp root script to successfully do the temp root. The phone will appear to hang on boot after you have temp root. Once s-off is achieved you will need to do a factory reset.
The process does take a long time and several reboots. The PC you are working from also needs internet. The software unlocks the boot-loader. I believe it needs to obtain the unlock code from htcdev.com.
One more thought. If you run the issued the command "adb devices" does your device show up. If it doesn't you need to install the drivers.
Click to expand...
Click to collapse
So based on what everybody is saying I actually had temp root since I had the status bar with no lock ring. I guess the issue was with rumrunner then.
I also tried to get an unlock from htcdev but encountered an error 160 invalid MID I think.
Device appears under adb devices.
Thanks for the reply.
Sent from my TouchPad using Tapatalk
USB debug is enabled?
Sent from my Incredible 4G LTE using XDA Premium 4 mobile app
Ran temproot, the phone booted to statusbar, no unlock-ring.
Tested sudo ./adb shell and had #: access, able to cd into /data/data etc and list files.
Ran rumrunner script, script reboots to fastboot as test1, then reboots for ADB as test2. When it reboots, it's no longer in temp-root. Script is removing temproot in beginning test phases thus script fails when it finds out later that it has no SU access. Any way around this? Or any other way to achieve SU on latest OTA to be able to run rumrunner's script properly?
Thanks
stevey500 said:
Ran rumrunner script, script reboots to fastboot as test1, then reboots for ADB as test2. When it reboots, it's no longer in temp-root. Script is removing temproot in beginning test phases thus script fails when it finds out later that it has no SU access. Any way around this? Or any other way to achieve SU on latest OTA to be able to run rumrunner's script properly?
Click to expand...
Click to collapse
rumrunner is NO script, but rather a pre-compiled binary! so no chance to edit
did you make sure to follow "rumrunners instructions"? seems like you ran it on linux (most successful ppl here did it on Win, albeit Win8.x _might_ be problematic as well):
Code:
1) 32-bit Linux (Ubuntu is preferred)
•Live CD’s are fine.
•Live USB is fine.
•Native install is fine.
•VM’s are unsupported.
•64-bit Linux may work with 32 bit libraries, but is unsupported.
2) A _working internet_ connection (on your linux system!)
3) USB _debugging enabled_ on your device (in developers options)
4) Fastboot _disabled_ on your device (settings -> battery -> UNcheck “fast boot”)
otherwise ... try on a Win7 machine, only HTC drivers _installed_ (NO HTC-Sync installed, but completely removed/deinstalled!!), NO other phone software installed (Kies, PDAnet etc) ... firewalls / internet security _disabled_, otherwise network filtering could get you stuck ... same restrictions 2), 3) & 4) from linux-rumrunner also apply!
maybe it's your linux firewall that intercepts the needed bits???
good luck
kimba99 said:
rumrunner is NO script, but rather a pre-compiled binary! so no chance to edit
did you make sure to follow "rumrunners instructions"? seems like you ran it on linux
maybe it's your linux firewall that intercepts the needed bits???
good luck
Click to expand...
Click to collapse
Thanks for the response!
I ran it in 32 bit ubuntu Linux, all files on my home directory. No firewall, direct connection to ISP. I followed their guide exactly except putting the phone into temp-root before I started.
The rumrunner binary in linux appears to find the phone, reboot to bootloader, finds bootloader, reboots to find ADB... at this point is when I realize rumrunner has removed temp-root as I can see home-screen icons and unlock ring, and later on waiting a few minutes further, rumrunner says no SU and cannot continue.
I will try to run rumrunner binary in windows 7 with only HTC drivers installed, open firewall, boot back up into temp-root and see what it does. :good:
dunno, maybe the "temp-root" for linux and win are different ... but for win when the "temp-root" script finished successfully, i started the rumrunner "soju" and it worked flawlessly. previously i tried rumrunner w/o "temp-root" and ended where you were: no SU/root or unsafe kernel found = cannot continue.
so maybe the prob is with your temp-root script rather than with the actual rumrunner?
kimba99 said:
dunno, maybe the "temp-root" for linux and win are different ... but for win when the "temp-root" script finished successfully, i started the rumrunner "soju" and it worked flawlessly. previously i tried rumrunner w/o "temp-root" and ended where you were: no SU/root or unsafe kernel found = cannot continue.
so maybe the prob is with your temp-root script rather than with the actual rumrunner?
Click to expand...
Click to collapse
Cool, maybe that is the case then. I'll try windows temp-root & windows rumrunner with HTC drivers as soon as I have a moment to try. Hope it works! This phone is a sluggish borderline unbearable crapper with HTC's stock firmware. I know it's got to be ten folds more tolerable with CM11's latest release for it.
I really appreciate the responses.
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.
]
I recently got a HTC Droid DNA on Verizon and it's been stressful getting to the point where I can install custom ROMs from stock. More so than on any of the previous HTC devices I've owned. I've had to glean information from different sources very carefully to achieve this since the majority of the guides out there are outdated, misleading and even brick-bait. This guide is meant to help the recent converts to the Droid DNA go through this process smoothly and safely.
If you follow instructions TO THE LETTER and CAREFULLY and meet ALL the prerequisites for every resource on this post you should have not problems.
Credit goes to the owners and developers of all the resources following most notably beaups, fuses, WindyCityRockr and jcase. These guys have made our device much more powerful and fun to use. None of it is mine. I am neither a dev nor a coder. I just know how to type in basic, decent English
As usual, following this guide is voluntary. You are responsible for your bricked device. Turn on your brain before your proceed. Your warranty will be voided. I suggest you read through the ENTIRE guide and follow the links to all the resources listed before you actually attempt this. If at any point in any of the guides you realize you do not have or have not downloaded any of the resources listed, make sure your get EVERYTHING you need before you proceed. Your best bet is to have a working connection on both your device and computer while you do this.You will need ADB setup and running properly. Pay close attention and note when you have to change a file name and WHERE you need to put the file on your computer before every step.
If that scared you, read no further. Thank you for stopping by.
If any of that excited you, welcome. Proceed.
1. Make sure you actually own a HTC Droid DNA from Verizon Wireless. Not a clone or a lookalike or a butterfly. Make sure ADB is intalled and setup properly on your computer.
2. Start by following (STEP BY STEP AND OMITTING NOTHING. NOTE THE PREREQUISITES) Beaups guide to achieving S-Off using firewater here http://firewater-soff.com/ I followed the guide to gain temproot FIRST and after that followed the steps that apply to a rooted device. I'm not sure it says this in the guide but make sure you copy the temproot and firewater files to your ADB folder immediately after you download them. This guide allows you unlock your bootloader WITHOUT HTC Dev
3. Follow Phaded's guide to installing a custom recovery from here http://forum.xda-developers.com/showthread.php?t=2318159
You can get TWRP's latest recovery image here http://techerrata.com/browse/twrp2/dlx Once again, omit nothing. Meet all the requirement before you do a single thing. Download every file and check the MD5 before your proceed. I renamed the TWRP recovery image to "recovery.img" since that is easier to type in a command line and copied the image file to the ADB folder on my computer.
If you have followed every instruction to the letter, you should have S-Off, an unlocked bootloader, root, custom revocery and SU.
4. If you like, you can download the WinDroid Universal HTC Toolkit, select your phone type, wait for it to download the appropriate binaries, confirm that it recognizes your device in ADB and fastboot modes and you can use it to perform various operations including update your recovery, issue ADB and fastboot commands and flash a new ROM. You can find that here http://forum.xda-developers.com/showthread.php?t=2437614
5. Find a ROM of your choice and flash to your heart's content :victory:
Congratulations.
Once again, I take no credit. All I wanted to do was consolidate information that was scattered in different sources to make this easier. Hope this helps someone out there.
I'm pretty sure I've seen this method a few days ago but you made it a bit easier for me (because spanish is my main language).
I can't wait to get my droid dna. This will be my first htc device so I'm going try this method. Thanks a lot!
i don't see anything related to bootloader unlock... am i missing it?
sidgallup said:
i don't see anything related to bootloader unlock... am i missing it?
Click to expand...
Click to collapse
Firewater takes care of that.
I share your frustrations. I'm going through that now, because only now have i decided to root my phone after almost 2 years of having the phone.
I must ask, would these instructions work with the latest OTA?
Yes, they should. Make sure you use the latest version of Firewater though. Once Firewater does it's thing, you're basically home free.
I can't get firewater to run on my insurance replacement. I tried all the methods on firewater's page.
After running the last command it doesn't bring up any prompt like step 5 says
okeydokeydeelio said:
I can't get firewater to run on my insurance replacement. I tried all the methods on firewater's page.
After running the last command it doesn't bring up any prompt like step 5 says
Click to expand...
Click to collapse
Are you on 4.09.605.5? That one has the anti firewater patch. Try sunshine. It may work. theroot.ninja
Sent from my HTC6500LVWBLU using XDA Free mobile app
No it's on 4.09.605.1
I can get limited root access with weaksauce but in cmd I can't get anywhere like I could on the old firmware
okeydokeydeelio
Have you tried Sunshine?
okeydokeydeelio said:
I can't get firewater to run on my insurance replacement. I tried all the methods on firewater's page.
After running the last command it doesn't bring up any prompt like step 5 says
Click to expand...
Click to collapse
I had the same issue on Windows. I tried numerous Windows machines and had the same issue as you. But once I got home and plugged into my linux box, I was s-off and unlocked within minutes. Try a Linux system instead of Windows. And make sure you are S-ON or firewater will not do anything.
--X
I.M.famous XMAN said:
I had the same issue on Windows. I tried numerous Windows machines and had the same issue as you. But once I got home and plugged into my linux box, I was s-off and unlocked within minutes. Try a Linux system instead of Windows. And make sure you are S-ON or firewater will not do anything.
--X
Click to expand...
Click to collapse
It's a refurb so it is s-on I'll try booting into linux and trying firewater. If that doesn't work I'll pay for sunshine
okeydokeydeelio said:
It's a refurb so it is s-on I'll try booting into linux and trying firewater. If that doesn't work I'll pay for sunshine
Click to expand...
Click to collapse
On a stock 4.09.605.1 using Windows 7, I was able to use firewater by following the instructions on http://forum.xda-developers.com/showthread.php?t=2742127 . To address any problems that may arise, read the entire thread.
paraglyder said:
On a stock 4.09.605.1 using Windows 7, I was able to use firewater by following the instructions on http://forum.xda-developers.com/showthread.php?t=2742127 . To address any problems that may arise, read the entire thread.
Click to expand...
Click to collapse
I will have wait and see if anyone can crack the latest update. My daughter had my phone the other day and brought it to me because it rebooted. She allowed it to update not knowing I didn't want to let it