• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root S off is here!

For what its worth,my m8 was completely stock,htcdev unlocked,supersu installed. It was on WiFi and not active(no sim card installed)

I hate to say it,but it sure sounds like you're having the same hardware issue as the t mobile crowd :(

Have you tried it on ubuntu?

edit:
looks like youre not th only one haveing issue... look thru the last few pages here: http://forum.xda-developers.com/showthread.php?t=2708527
 
  • Like
Reactions: Tre Lawrence
Upvote 0
root@htc_m8whl:/ # cd /data/local/tmp
cd /data/local/tmp
root@htc_m8whl:/data/local/tmp # ls -l
ls -l
-rwxr-xr-x root root 4519496 2014-05-03 14:18 firewater

Was almost hoping something would be amiss there for a quick answer but its not. File exists and permissions are correct. Will do some more digging.
 
Upvote 0
I don't think that output matters, for reasons that I won't go in to (respect the exploit).

Timing looks important, do the adb reboot, then copy the commands as a list, all at once, into your terminal window. Try without waiting for the reboot to complete.

See if that helps.

Thanks, Early.

Tried this... was actually faster. Got the same result.

Some other points/questions for folks: do HTC drivers still need to be installed?

Also, I checked my SuperSU logs, and nothing shows up. Is that to be expected with an ADB SU operation?

Thanks y'all...
 
  • Like
Reactions: scotty85
Upvote 0
Thanks, Early.

Tried this... was actually faster. Got the same result.

Some other points/questions for folks: do HTC drivers still need to be installed?

Also, I checked my SuperSU logs, and nothing shows up. Is that to be expected with an ADB SU operation?

Thanks y'all...

Per http://firewater-soff.com/instructions/ - drivers installed, sync removed. In Windows, without the right drivers, you won't get a reboot.

SuperSU isn't likely to log an adb shell su.

Did you put all of the commands into the single copy / paste, including the reboot?
 
Upvote 0
Per http://firewater-soff.com/instructions/ - drivers installed, sync removed. In Windows, without the right drivers, you won't get a reboot.

SuperSU isn't likely to log an adb shell su.

Did you put all of the commands into the single copy / paste, including the reboot?

No, I did the reboot first, then copied the rest.

Will try it with all copied in.
 
  • Like
Reactions: scotty85
Upvote 0
sounds more and more like the hardware issue is affecting the sprint phones too. youre not alone,there is some discussion of it here: Just so you know S-Off works - xda-developers jump to the last pages and read backwards ;)

firewater is one of the fastest s off's ive ever done. i didnt pay any particular attention to timing,just enterd the commands on my old ubuntu 12.04 laptop and it worked and was over before i knew it. they have stated that the binary is stable,so the issues youre experincing seem to point to the incompatible hardware.

id still try it on ubuntu,if you havent. if it fails there as well,looks like youll have to keep your fingers crossed for the guys(beaups and fuses) to find a work around :(
 
Upvote 0
I take it there's still no joy. :(

Oops... sorry, yep, no joy yet... :(

Thankfully, I can enjoy Viper.

sounds more and more like the hardware issue is affecting the sprint phones too. youre not alone,there is some discussion of it here: Just so you know S-Off works - xda-developers jump to the last pages and read backwards ;)

firewater is one of the fastest s off's ive ever done. i didnt pay any particular attention to timing,just enterd the commands on my old ubuntu 12.04 laptop and it worked and was over before i knew it. they have stated that the binary is stable,so the issues youre experincing seem to point to the incompatible hardware.

id still try it on ubuntu,if you havent. if it fails there as well,looks like youll have to keep your fingers crossed for the guys(beaups and fuses) to find a work around :(

Don't know what the heck I did with my Ubuntu CD, so its time for a new USB stick. That's always a positive.

Guys, words can't express my appreciation. Guys like y'all make Android the platform that it is.
 
Upvote 0
Code:
[SIZE=2][SIZE=2][SIZE=2]C:\miniadb_v1031>adb devices[/SIZE]
[SIZE=2]List of devices attached[/SIZE]
[SIZE=2]HT44ASF04401 device[/SIZE]
 
[SIZE=2]C:\miniadb_v1031>adb reboot[/SIZE]
[SIZE=2]C:\miniadb_v1031>adb wait-for-device push firewater /data/local/tmp[/SIZE]
[SIZE=2]2155 KB/s (4522136 bytes in 2.049s)[/SIZE]
 
shell@htc_m8whl:/ $ su
su
[/SIZE]shell@htc_m8whl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
shell@htc_m8whl:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|shell@htc_m8whl:/ $
[/SIZE]

Unlocked, TWRP, SU installed, Windows Vista ('cause Ubuntu wouldn't find device)
USB Debugging on, Lock screens off

What am I missing?

Ok, so I tried again
Had to type: chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Which got me to: root@htc_m8whl:/ #
Then: /data/local/tmp/firewater
It ran.
Then whelp'd me. GRRRRRRRRRRRRRR!!!!!!!!!!!:mad::mad::mad::mad::mad:
:banghead::banghead::banghead::pcguru:
 
Upvote 0
Code:
[SIZE=2][SIZE=2][SIZE=2]C:\miniadb_v1031>adb devices[/SIZE]
[SIZE=2]List of devices attached[/SIZE]
[SIZE=2]HT44ASF04401 device[/SIZE]
 
[SIZE=2]C:\miniadb_v1031>adb reboot[/SIZE]
[SIZE=2]C:\miniadb_v1031>adb wait-for-device push firewater /data/local/tmp[/SIZE]
[SIZE=2]2155 KB/s (4522136 bytes in 2.049s)[/SIZE]
 
shell@htc_m8whl:/ $ su
su
[/SIZE]shell@htc_m8whl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
shell@htc_m8whl:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|shell@htc_m8whl:/ $
[/SIZE]

Unlocked, TWRP, SU installed, Windows Vista ('cause Ubuntu wouldn't find device)
USB Debugging on, Lock screens off

What am I missing?

Ok, so I tried again
Had to type: chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Which got me to: root@htc_m8whl:/ #
Then: /data/local/tmp/firewater
It ran.
Then whelp'd me. GRRRRRRRRRRRRRR!!!!!!!!!!!:mad::mad::mad::mad::mad:
:banghead::banghead::banghead::pcguru:

Crap chief, that sucks. Sorry my man, try to be patient. The devs are working on a fix for this.

You can still enjoy all of the roms out there as a consolation. :)
 
  • Like
Reactions: Chief YYZ and dan55
Upvote 0
Code:
[SIZE=2][SIZE=2][SIZE=2]C:\miniadb_v1031>adb devices[/SIZE]
[SIZE=2]List of devices attached[/SIZE]
[SIZE=2]HT44ASF04401 device[/SIZE]
 
[SIZE=2]C:\miniadb_v1031>adb reboot[/SIZE]
[SIZE=2]C:\miniadb_v1031>adb wait-for-device push firewater /data/local/tmp[/SIZE]
[SIZE=2]2155 KB/s (4522136 bytes in 2.049s)[/SIZE]
 
shell@htc_m8whl:/ $ su
su
[/SIZE]shell@htc_m8whl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
shell@htc_m8whl:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|shell@htc_m8whl:/ $
[/SIZE]

Unlocked, TWRP, SU installed, Windows Vista ('cause Ubuntu wouldn't find device)
USB Debugging on, Lock screens off

What am I missing?

Ok, so I tried again
Had to type: chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Which got me to: root@htc_m8whl:/ #
Then: /data/local/tmp/firewater
It ran.
Then whelp'd me. GRRRRRRRRRRRRRR!!!!!!!!!!!:mad::mad::mad::mad::mad:
:banghead::banghead::banghead::pcguru:

I feel your pain... :(
 
  • Like
Reactions: Chief YYZ
Upvote 0
hi Chief,
did you manage to sort it?

No, figured I'd wait to hear if there was an update on the hardware thing.
No S-Off is annoying, but I'm still running Viper and that's good enough for now.

Not that I know of. There is a difference in some of the hardware configurations that is causing this. The developers are working on incorporating this into the S-off tool, just have to be patient. :(

Hmmm., that really sucks, You don't have the HK version do you? (I know I am jumping into this kinda late so don't shoot me if I missed something) I have Sprint and FW worked fine on mine.

Standard gunmetal hardware version 0005. Bought at Best Buy last weekend. Model 831C, not sure if that's the same on all Sprint M8's.

Anybody have any good links on specific S-ON/S-OFF differences on this phone/bootloader(is there more than one version out, don't remember seeing any OTA bootloader update info.) Any way to permanently change permissions on /storage without S-OFF? Some annoying navigation in apps won't let me set paths for downloads and such without using /sdcard2, causing duplicates in gallery and other places.
 
Upvote 0
Maybe just a point of curiosity, but I am still wondering about the actual steps. Since I got Firewater to attempt to run, and got the whelp message, I doubt it changes anything for me.

From Firewater:

Code:
[FONT=Courier New]adb reboot [/FONT][B]<--important!!!![/B]
adb wait-for-device push firewater /data/local/tmp
adb shell
chmod 755 /data/local/tmp/firewater
su
/data/local/tmp/firewater
I had to type:

Code:
adb reboot [B]<--important!!!![/B]
adb wait-for-device push firewater /data/local/tmp
adb shell
chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
 su
/data/local/tmp/firewater
So I had to add /data/local/tmp/firewater a second time to the third to last line with a space, it did not work without the space. Granite had mentioned earlier to run it all together, but I needed a space and then still had to type /data/local/tmp/firewater on a different line. Anybody know why that is?

Update: Ok so in going thru all this I realized my original post had su and chmod backwards. I typed it wrong the first time, but redid it after copying the DOS window. I did have some problems copying to clipboard in the DOS window, so my post only had my very first attempt. I'm pretty sure I redid it correctly afterward and after adding the space and duplicate /data/tmp/local/firewater, but I will retry again and update.
Nevermind that, seems I copied the weaksauce instructions by mistake in this post, but that leads me to ask: Why are chmod and su reversed in the 2 methods?
 
  • Like
Reactions: dan55
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones