Hi all,
First, I've searched and done external research to this issue, so I hope this isn't a redundant post.
I've had a DNA since Jan 2013. It's served me really well! I'm fond of it, especially because I was able to couple it with my unlimited data plan and PDANET's wi-fi hotspot feature. It was great, because I could do it while tethering my desktop and still access stuff over wifi.
Then, the KitKat update. When I updated and realized what had happened (that the wi-fi functionality aside from bluetooth was disabled), I was pissed, and decided to just root my phone. Which proved not easy (I tried cyanogenmod). So, then I tried figuring out how to unlock the bootloader, which doesn't seem possible now. I've also tried installing an older RUU for the DNA that was listed on this site, but it gives me an error at the ROM installation point.
Is there ANY workaround to reverting my DNA to the last update? I called Verizon/HTC and they're like, "you're on your own."
I just want my wi-fi hotspot back, and I'll do what is necessary to restore it. KitKat really screwed me over. I'm sure it's great, but it didn't help me.
did you unlock your phone before updating to KK?
Sent from my SM-T210 using XDA Premium 4 mobile app
I did not. I've tried figuring out how to since this update but haven't been successful. It seems Verizon/HTC are making it particularly difficult for users to actually change the software and firmware of the products they've purchased.
smartz_24 said:
did you unlock your phone before updating to KK?
Sent from my SM-T210 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For almost all HTC devices, you need s-off to downgrade RUUs.
Try the temp root option for the m8 (I read somewhere it works on the DNA) then use firewater
Sent from my HTC6435LVW using xda app-developers app
Uzephi said:
For almost all HTC devices, you need s-off to downgrade RUUs.
Try the temp root option for the m8 (I read somewhere it works on the DNA) then use firewater
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Okay, so I tried getting temp root and s-off with firewater as it was described for the M8 but ADB fails after first reboot. Sigh...
eidos6 said:
Okay, so I tried getting temp root and s-off with firewater as it was described for the M8 but ADB fails after first reboot. Sigh...
Click to expand...
Click to collapse
I can confirm that the M8 Weaksauce and Firewater will work to get s-off so you'll be good here eventually. Where exactly is it adb loosing the device? Maybe let us know what commands your running. And were you able to get the temp root with Weaksauce?
I followed a video on how to use Weaksauce to gain temproot, and while it did say I had root via Root Check, when I tried to complete the rest of the instructions listed for method 2 on the firewater s-off website the process failed after adb shell. I couldn't even get the prompt to agree to the terms and conditions of the program.
Is it possible that the 4.4 update to the DNA made this process no longer valid? Any help is appreciated!
eidos6 said:
I followed a video on how to use Weaksauce to gain temproot, and while it did say I had root via Root Check, when I tried to complete the rest of the instructions listed for method 2 on the firewater s-off website the process failed after adb shell. I couldn't even get the prompt to agree to the terms and conditions of the program.
Is it possible that the 4.4 update to the DNA made this process no longer valid? Any help is appreciated!
Click to expand...
Click to collapse
No, just yesterday used firewater on my DNA with the 4.4 OTA. Also worth noting i used method 1 for firewater, the normal/rooted method. But if its failing on "adb shell", then it doesn't matter because the first three steps are the same.
When you entered the "adb shell" command, what is the error message you get? Maybe take a screenshot of your cmd lines if you can.
sum182 said:
No, just yesterday used firewater on my DNA with the 4.4 OTA. Also worth noting i used method 1 for firewater, the normal/rooted method. But if its failing on "adb shell", then it doesn't matter because the first three steps are the same.
When you entered the "adb shell" command, what is the error message you get? Maybe take a screenshot of your cmd lines if you can.
Click to expand...
Click to collapse
Hi, well that's good news for me if you did this on your 4.4 DNA yesterday! What exactly did you do? I'm at work atm, but I'll be home later tonight with details about where the process kept failing. It might be I don't have the proper drivers for my DNA (I have Windows 7 Ultimate running on a 64-bit AMD quad-core processor), but I thought I did have the correct ones. I can reboot the phone via usb and fastboot, btw, but whenever it was rebooting Windows changed the identity of the device from DNA to an ambiguous Android device.
Anyhow, more later. Thanks for the help!
sum182 said:
No, just yesterday used firewater on my DNA with the 4.4 OTA. Also worth noting i used method 1 for firewater, the normal/rooted method. But if its failing on "adb shell", then it doesn't matter because the first three steps are the same.
When you entered the "adb shell" command, what is the error message you get? Maybe take a screenshot of your cmd lines if you can.
Click to expand...
Click to collapse
As I'm a new user I can't post links for screenshots.
Here is the text for following the steps for firewater's site:
After reboot I get:
adb wait-for-device push firewater /data/local/tmp
annot stat 'fiewater':no such file or directory
adb shell
u
hmod 755 /data/local/tmp/firewater
/data/local/tmp/firewateru
hmod 755 /data/local/tmp/firewater
[email protected]:/#su
system/bin/sh: su:not found
27|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
[email protected]:/ $
It just fails. Thoughts?
eidos6 said:
As I'm a new user I can't post links for screenshots.
Here is the text for following the steps for firewater's site:
After reboot I get:
adb wait-for-device push firewater /data/local/tmp
annot stat 'fiewater':no such file or directory
adb shell
u
hmod 755 /data/local/tmp/firewater
/data/local/tmp/firewateru
hmod 755 /data/local/tmp/firewater
[email protected]:/#su
system/bin/sh: su:not found
27|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
[email protected]:/ $
It just fails. Thoughts?
Click to expand...
Click to collapse
Alright, so it gets into the shell fine, however it couldn't find firewater whenever you tried to push it to the device. Do you have it in the same folder as adb? that would be step 1, make sure its in the same folder as adb and make sure you spell everything right. Follow method 1 for normal/rooted devices. Thats what I used for mine (even though it was rooted with weaksauce)
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
Here's what your cmd line should look like (execpt the file paths obv) A quick note, when you execute the "su" command, it'll prompt you on your phone to grant it superuser permissions, so make sure to grant them to it.
{
"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"
}
sum182 said:
Alright, so it gets into the shell fine, however it couldn't find firewater whenever you tried to push it to the device. Do you have it in the same folder as adb? that would be step 1, make sure its in the same folder as adb and make sure you spell everything right. Follow method 1 for normal/rooted devices. Thats what I used for mine (even though it was rooted with weaksauce)
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
Here's what your cmd line should look like (execpt the file paths obv) A quick note, when you execute the "su" command, it'll prompt you on your phone to grant it superuser permissions, so make sure to grant them to it.
Click to expand...
Click to collapse
Thanks so much for this walk-through. It took me moving some files around and removing a conflicting driver on my PC, but I was successfully able to get S-Off last night!
Now I just need to find the 4.2 or 4.3 RUU for the DNA (basically so I can use my wi-fi hotspot again)...orrr, maybe go for Root?
I was having the issue with su not found as well, but now that is working fine... for some reason firewater won't run
I get su to run and chmod, but then when i run the file nothing happens
hopefully someone else has seen this because if I am stuck on stock I might just shoot myself :crying:
EDIT: I've looked at this closely, and I'm seeing that once I run firewater it disappears from /data/local/tmp
...this is killing me
Hi....Have you tried the "temroot" at the bottom of this page
http://firewater-soff.com/instructions/
I did my DNA only this morning on my Mac it took about 20 mins
Good luck
ps. i was messing about for 3 days looking for a fix then as a last resort i deleted my fastboot/adb folder and downloaded the latest version
Hope this helps
Oadbylad said:
Hi....Have you tried the "temroot" at the bottom of this page
http://firewater-soff.com/instructions/
I did my DNA only this morning on my Mac it took about 20 mins
Good luck
ps. i was messing about for 3 days looking for a fix then as a last resort i deleted my fastboot/adb folder and downloaded the latest version
Hope this helps
Click to expand...
Click to collapse
Thanks for the response. Yes, I did try updating the SDK. I've also tried on different computers and getting the same issue: firewater disappears as soon as I try to run it. I spent 6 hours on this the other night and just gave up. I should mention also that I have RUU'd and run firewater successfully before this. I ran it after the RUU, prior to the kit kat update and it ran flawlessly. Only thing I can think of is that it has something to do with the new OTA.
Anyway, got so fruatrated i bought a Moto X that night so I'll be selling my DNA. Been ready to move on from HTC for a while anyway.
Sent from my HTC6435LVW using Tapatalk
Re that OTA update i'll be watching out for that...and knocking it back cheers for the heads up
I have exactly the same problem.
firewater gets delete inmediately, so I can't run it.
the first time worked well but I got a lot of dots and no bottles.
Edit:
I downloaded firewater directly to the phone from the site. I kept the internet on all the times (WIFI)
Worked very well
Related
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
If you don't have adb and fastboot on your PC
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
I don't have a simple bundde for Mac, would welcome a link if anyone has one.
Download my universal misc_version and unzip to obtain the misc_version file.
Download tacoroot
Place both the misc_version and tacoroot.bin files in the same directory as adb
Procedure
Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
Run the following adb commands
Code:
adb push tacoroot.bin /data/local
adb push misc_version /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
Simultaneously press Volume Up, Volume Down and Power
Reboot your device
Run the following command
Code:
adb shell /data/local/tacoroot.bin --root
Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
Run the following command:
Code:
adb shell /data/local/misc_version -s [COLOR="Red"]2.00.405.3[/COLOR]
Note that the number in RED is the version number retrieved in step 1.
Reboot to fastboot:
Code:
adb reboot bootloader
Run your RUU ( if on linux or mac, see other similar threads from me on how to RUU on those OSes )
Special Thanks
jcase for providing the tacoroot.
Nice release globatron! I was actually looking at Tacoroot for this last night but didn't really want to go into it too much and decided against using it. Glad to see I wasn't the only one with the idea for it though.
heh, Gave jcase the updated misc_version so he has it on the github radme for tacoroot already but didn't want to release the procedure until I has actually tested misc_version to run on at least a few HTC emmc devices and with multiple version string lengths.
Even if you didn't release this today, I probably would have started on it tonight, I'm a bored teenager with too much time. Still, keep up the good work. If you want me to make a script for you or anything, let me know and I'll get to work on it. (also, you know you can actually have adb from the recovery so you dont need to hit the buttons on it, just have it wait then adb reboot (or even adb shell reboot))
Of course I know that but that's not the what the buttons is about here.
What are the points of the button?
Sent by breaking the sound barrier
To ensure with absolute certainty that a log will be created.
Ah, you want the button presses to be logged to ensure it's done the job. Alright, fair enough.
Glad to TacoRoot in use!
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
globatron said:
Thanks for the spice jcase, just realized I had a typo in the procedure....jcase *provided*, not tested (well that too), tacoroot.
Click to expand...
Click to collapse
is the typo msc_version being misc_version
thanks Kevin, fixed that.
yep, didnt notice it until someone tried to do my procedure today lol... copy and paste my friend lol. Plus I just need to know one thing. This brings you down to GB but still keeps you locked right? You still technically have to use HTC unlock to bring it back to 1.13.000 correct?
Part1: correct, you've never unlocked if you do this.
Part2: No, you don't have to unlock at all during this procedure.
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
kevinrocksman said:
so to go from the 1.14 hboot to 1.13 u dont need to htc unlock?
Click to expand...
Click to collapse
That's correct.
globatron said:
This procedure applies to both flyers and view
Required downloads
First download the Gingerbread RUU for your device from this thread.
the download link takes me to the flyer RUU, i understand the view & flyer are the same except the 3g/4g network on the View. i just want to make sure i download the correct RUU for my View. what verision do i need? this one "RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed.exe"
agian thank you for the support
Click to expand...
Click to collapse
That one is fine. Express is the board name or the view so an RUU with express (not expresskt) in the name is what you need.
Hello, thanks for the downgrade help. Upgraded to honeycomb and hated it so I followed your instructions and everything went exactly as described until the middle of the RUU upgrade itself where it stopped and gave me an
ERROR[140]: BOOTLOADER VERSION ERROR
The ROM Update utility cannot update your android phone
Please get the correct ROM update utility and try again.
It won't successfully reboot now. When I go back to bootloader mode the recover screen shows
*** LOCKED ***
express pvt ship s-on rl
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
emmc-boot
oct 25 2011, 16:35:13
used RUU_Express_Sprint_WWE_1.22.651.1
Its completely stock, was notified of the new update by htc and installed it over wifi. Thanks in advance for any help
What appears to have happened here is that somewhere along the way something didn't work fully and you failed to set the version to the same as or lower than the RUU you used.
I would need to see the output of :
Code:
fastboot getvar version-main
to be absolutely certain of this. If that is the case then becasue you are completely stock the best course of action would be for you to return it for repair. Tell the technical support people that this happened when you tried to take the OTA update to HoneyComb. The alternative will require you to use the HTC unlock.
One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Post in q&a not development !
crossmanbx said:
One month after i bought it, my ShooterU has got a MB replacement (RMA)
And now it's impossible for me to unlock bootloader with the htcdev method.
Is there another way to make it possible (Evo3d with stock ICS) ?
Thank you for helping me, i'm furious with it.
Click to expand...
Click to collapse
HTCDev unlock method doesn't work on phones with replaced motherboards. You're out of luck, sorry.
it's called bad blocks. nothing you can do about it ...
Can't you use juopunutbear and do the wire trick?
00mpollard said:
Can't you use juopunutbear and do the wire trick?
Click to expand...
Click to collapse
I think it's a good idea to try the juopunutbear, but i need to have temp root at least.
And all temp root i find are made for Gingerbread.
Does anyone know a temp root method for ICS ?
Thank you
Questions and non-development related should be posted in the appropriate sections. This thread is not dev related, so I'm moving it.
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
crossmanbx said:
So there isn't another method to unlock my bootloader ? Htcdev is the only way to do this ? What does it mean ?
My evo 3d is unrootable ? The bootloader still be blocked forever ?
Please help me not to sell it ! Thank you
Click to expand...
Click to collapse
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
kgs1992 said:
Unless Unlimited.io releases a version of controlbear that works on just temp root, nothing can be done.
Such a method already exists for the HTC Sensation.
Click to expand...
Click to collapse
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
ramjet73 said:
I don't believe there's a temp root technique that works on the Evo 3D anyway, but if you know of one some users here have been looking for it for other reasons, especially one that works with ICS.
The Evo 3D is definitely not the same phone as the Sensation and has different capabilities and limitations.
ramjet73
Click to expand...
Click to collapse
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Click to expand...
Click to collapse
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
ramjet73 said:
Never heard of that for the Evo 3D. If you can post a link I'll give it a try if it's compatible with the CDMA Evo 3D. Mostly people are looking for it so they can backup a stock unrooted ROM with Titanium Backup before they root and S-OFF.
ramjet73
Click to expand...
Click to collapse
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
kgs1992 said:
Instructions are above. But it needs to be tried on LOCKED S-ON E3D.
Temp root is unstable, the only thing you can see on the phone is the statusbar.
You can't use the phone till temproot is removed, only use adb commands.
You can probably adb pull /data & restore it later.
Click to expand...
Click to collapse
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
ramjet73 said:
I'm out of thanks right now, but appreciate your posting that.
Being S-OFF already via JuopunutBear I'm not as anxious to try it since it requires going back to S-ON, but maybe someone who is currently S-ON on an Evo 3D would be willing to test. I'm assuming that it shouldn't matter if the phone is a GSM or CDMA model based on the commands above.
ramjet73
Click to expand...
Click to collapse
Yes, that's right, it doesn't matter.
That is basically the TPSparkyRoot exploit, but I've modified it slightly.
Hope it does work.
If it doesn't, whoever tries it, please post the error message.
kgs1992 said:
I agree. Only speculating.
Doesn't TPSparkyRoot work?
Try this:
To root:
Code:
adb shell "rm /data/local/tmp.orig"
adb shell "mv /data/local/tmp /data/local/tmp.orig"
adb shell "rmdir /data/local/tmp"
adb shell "ln -s /data /data/local/tmp"
adb shell "rm /data/local.prop"
adb shell "chmod 777 /data/local/"
adb shell "echo ro.kernel.qemu=1 > /data/local/local.prop"
adb reboot
adb shell "chmod 777 /data/local/local.prop"
adb shell "mv /data/local/local.prop /data/local.prop"
adb reboot
It's okay if the "adb shell rm" or "adb shell rmdir" commands fail.
To unroot:
Code:
adb shell "rm /data/local.prop"
adb shell "rm /data/local/tmp"
adb shell "mv /data/local/tmp.bak /data/local/tmp"
Click to expand...
Click to collapse
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
johnmarshton said:
i am willing to test this.i have gsm evo 3d with hboot 1.5(OTA ICS),LOCKED S-ON.but i have some questions:
1)when i execute those commands should i be in fastboot usb or just connect the phone in charging mode and with usb debugging checked?
2)if i sucesfully temp root what can i do in order to perm root my phone?
THANKS!!!
Click to expand...
Click to collapse
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
kgs1992 said:
1) adb access required. Hence, charging mode with USB Debugging enabled.
2) You cannot permanently root without an unlocked bootloader or S-OFF.
Click to expand...
Click to collapse
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
johnmarshton said:
then,if i succesfully obtain temp root,what can i do?can i unlock my bootloader,downgrade hboot?what can i do?thanks!
Click to expand...
Click to collapse
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
kgs1992 said:
Very little. You can probably make backup of your data.
You can get root access via adb shell. But what you can do is limited.
The most this will establish is whether or not the E3D can be temprooted or not.
Click to expand...
Click to collapse
Could he push an "su" binary to the system partition while he has temp root?
ramjet73
So, im stuck at the phase where rumrunner kept pouring shots and after 7 tries it stated to run it again. i know it said it doenst work on all custom rom, and i running stock rooted rom ( does that mean its custom rom?). is that the reason rumrunner wont run for my sprint htc one max phone?
i tried firewater and it also didnt S-off my phone.
im running android 4.4.2 with hboot 2.49
tampered unlocked and custom rooted stock rom.
HtcEvo4gLTE said:
So, im stuck at the phase where rumrunner kept pouring shots and after 7 tries it stated to run it again. i know it said it doenst work on all custom rom, and i running stock rooted rom ( does that mean its custom rom?). is that the reason rumrunner wont run for my sprint htc one max phone?
i tried firewater and it also didnt S-off my phone.
im running android 4.4.2 with hboot 2.49
tampered unlocked and custom rooted stock rom.
Click to expand...
Click to collapse
Rumrunner won't work with hboot 2.49 ..
u must use firewater only for s-off now
what step of firewater do you have problem?
blue8 said:
Rumrunner won't work with hboot 2.49 ..
u must use firewater only for s-off now
what step of firewater do you have problem?
Click to expand...
Click to collapse
i tried firewater. it doesnt work. i use the first step stock rooted rom. so i dont need temp root. but it didnt s-off my phone.
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
The first bottle is open
chugging.....
[email protected]:/#
it just stop from there.
HtcEvo4gLTE said:
i tried firewater. it doesnt work. i use the first step stock rooted rom. so i dont need temp root. but it didnt s-off my phone.
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
The first bottle is open
chugging.....
[email protected]:/#
it just stop from there.
Click to expand...
Click to collapse
Did you try different HTC driver?
Check these post
Code:
http://forum.xda-developers.com/showpost.php?p=52770187&postcount=12
Code:
http://forum.xda-developers.com/showpost.php?p=52777681&postcount=14
blue8 said:
Did you try different HTC driver?
Check these post
Code:
http://forum.xda-developers.com/showpost.php?p=52770187&postcount=12
Code:
http://forum.xda-developers.com/showpost.php?p=52777681&postcount=14
Click to expand...
Click to collapse
i did. still didnt work. i was reading about that too. people claim to got it working with older driver.
*cry*
Hello everyone I'm a new VZW One Max owner and this device has proven to be the most complicated ive experienced so far in terms of Rooting/Bootloader unlocking/and S-off. (I'm temp rooted with weaksauce 1.0.1)
I cant seem to get the bootloader unlocked via HTCdev, and the firewater and rumrunner do not work for me either .
It seems like every method to help accomplish the above requires an unlocked bootloader, and after reading several threads the tool of choice is firewater.
While reading the thread for firewater I noticed it said it is for HBOOT 2.47, there was a note at the bottom of the thread for 2.49 HBOOT users but while following the instructions from that thread one of the steps was to unlock the bootloader via HTCdev :silly: . And install the Stock HTC 1.19xxxx
How can that be done in my situation?
Ive attached errors i've been experiencing from firewater and rumrunner.
***For rumrunners I'm using the custom device specific download. But i've seen all types of errors from flashing a new kernel to using a more updated version.
Verizon HTC One Max Android Version 4.4.2 with HBOOT 2.49
Thanks for any steps in the right direction!
ceo4eva said:
Hello everyone I'm a new VZW One Max owner and this device has proven to be the most complicated ive experienced so far in terms of Rooting/Bootloader unlocking/and S-off. (I'm temp rooted with weaksauce 1.0.1)
I cant seem to get the bootloader unlocked via HTCdev, and the firewater and rumrunner do not work for me either .
It seems like every method to help accomplish the above requires an unlocked bootloader, and after reading several threads the tool of choice is firewater.
While reading the thread for firewater I noticed it said it is for HBOOT 2.47, there was a note at the bottom of the thread for 2.49 HBOOT users but while following the instructions from that thread one of the steps was to unlock the bootloader via HTCdev :silly: . And install the Stock HTC 1.19xxxx
How can that be done in my situation?
Ive attached errors i've been experiencing from firewater and rumrunner.
***For rumrunners I'm using the custom device specific download. But i've seen all types of errors from flashing a new kernel to using a more updated version.
Verizon HTC One Max Android Version 4.4.2 with HBOOT 2.49
Thanks for any steps in the right direction!
Click to expand...
Click to collapse
If you still need help with this, I recently did this on a Verizon One Max, double check the following:
Fastboot mode is off in the power/battery settings
No lock screen security enabled, pattern, pin, face, nothing should be on
Leave the screen on a long timeout, or no timeout for this process, adb may prompt RSA checks you'll need to grant permissions to.
Remove all super user apps, busybox installer apps, supersu, superuser, whatever
Then:
Run weaksauce app
Install supersu from play store or you can adb install the apk if you have the updater zip or apk on your PC
After you have su (# prompt instead of $ after typing su) in adb shell turn off WiFi, leave mobile data on:
adb shell
su
If you see it change to # then proceed, if not, reboot and run weaksauce again, wait for a minute and try the commands again.
Exit adb shell (type exit and hit enter twice)
Push firewater to /data/local/tmp
adb push firewater /data/local/tmp
Set 755 permissions on firewater:
adb shell
su (if not on # prompt, it should still be there)
chmod 755 /data/local/tmp/firewater
Run firewater (still in shell, don't close the terminal or exit from su/#):
/data/local/tmp/firewater
Last time it froze the first time, then the second try it went through on the second bottle. If you see no improvement after 3 minutes hold power for 60 seconds until it reboots the device, then start again from the weaksauce running part.
Hope this helps. I did it over team viewer with another user and this is what finally got it to get it all finished.
Rumrunner doesn't work with verizon 2.49 that I can tell, it'll be weaksauce and firewater.
Hello again,
I am trying to S-Off a HTC One Max. So I'm using firewater. However, when i write adb shell then su, nothing happens, I'm not getting the SuperSU permission on my phone.. I've tried different ports and everthing, YES I did adb reboot and i did push firewater, both worked. just this weird thing about the su that isn't working, i tried supersu 1.94, 1.99 and now I gotthe 2.02 and yet, nothing.
any help?
PampaZiya said:
Hello again,
I am trying to S-Off a HTC One Max. So I'm using firewater. However, when i write adb shell then su, nothing happens, I'm not getting the SuperSU permission on my phone.. I've tried different ports and everthing, YES I did adb reboot and i did push firewater, both worked. just this weird thing about the su that isn't working, i tried supersu 1.94, 1.99 and now I gotthe 2.02 and yet, nothing.
any help?
Click to expand...
Click to collapse
Which carrier are you on? What happens when you open the SU app? What ADB/fastboot are you using?