[Q] Please Help Me Revert to 4.3 or Prior! - HTC Droid DNA

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