Database Info

[ROOT] 1.85 - New, working method - ACT NOW, MAY NOT LAST FOREVER!

Silly HTC. THIS EXPLOIT MAY NOT LAST FOREVER. ATT COULD KILL THIS. DO IT NOW.
Warning: If something goes wrong, whatever you do, do NOT install the update that this process finds. If you DO, you will be stuck on 2.20 with no chance for root (currently)
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
After the device reboots:
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed....
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Congrats, you have root. Install supersu and busybox installer from the market (or Play store).
If you pledged a bounty in the bounty thread, note the instructions here:
Please pay bounty to make a wish foundation
http://www.wish.org/help/donate
Please choose the "Make a Wish Foundation of America" (don't select a chapter). You can use Paypal as well.
Special thanks to designgears as well for being my tester and also writing the one click. He has several hours of work in this project as well. Consider a donation to him, too - http://rootzwiki.com/store
ADDED: Please let me know if this works for you!
ADDED: If you already pushed the wrong binary it's easiest just to start over with the correct binary.

SWEEEEEEEEEEET!
You have just made a lot of people. SCC/FGFD

where do we get the su binary. I have a supersu zip to gain root after unlock

Great job guys!!!

Do terminal apps need root to run? Can I do this with terminal and avoid ADB?

I got "no updates found" and permission denied...
-rw------- system system 1196598 2012-05-25 12:36 local.prop

beaups you are the ****ing best!!!

AWESOME. Thank you so much!
Where do we get su binary?
I'm thinking maybe from a rooted phone? I have a rooted HTC Inspire.

shgadwa said:
AWESOME. Thank you so much!
Where do we get su binary?
I'm thinking maybe from a rooted phone? I have a rooted HTC Inspire.
Click to expand...
Click to collapse
I added the link to op

shgadwa said:
AWESOME. Thank you so much!
Where do we get su binary?
I'm thinking maybe from a rooted phone? I have a rooted HTC Inspire.
Click to expand...
Click to collapse
It's in the op
Sent from my HTC One X using Tapatalk 2

2nd line after adb shell i get no device found. USB debugging is enabled.

Very awesome. Hard work and dedication finally paid off. Thanks to who all that contributed to this.

Omg. Awesome. Who discovered this exploit?

My brother, give us your PayPal so we can donate. This is awesome.

Anyway to put the setting up of ADB in lamens terms for some of us that aren't familiar? I am ok with the commands, I just don't know how to get ADB to command prompt and where to place the files.
---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------
gunnyman said:
Omg. Awesome. Who discovered this exploit?
Click to expand...
Click to collapse
beaups and dg

I updated to op to fix a wrong instruction.

when I put in the first line it says device not found. It's weird I can boot into boot into bootloader and everything but can't do that line

gunnyman said:
Omg. Awesome. Who discovered this exploit?
Click to expand...
Click to collapse
Once we get a few success stories I'll be claiming bounty (charity).

OMG GOOD JOB!!!! Im already rooted but im proud of you guys!!! GOOD JOB!! Hopefully Me and a Simonsimons will be releasing S=OFF SOON! fingers crossed

SkizzMcNizz said:
when I put in the first line it says device not found.
Click to expand...
Click to collapse
Try again, updated instructions.

HTC One X Root Assistance

Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!

blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
check pm

beaups said:
check pm
Click to expand...
Click to collapse
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?

smartnphone said:
Could you help me too X( ? I got my HOX last night at 8pm; I traded my rooted S2 Skyrocket for it.
Been looking for the past day through forums and google. It's so different from Samsung's phones, but a nice change indeed.
I'm on 1.85 and tried those two methods also. I'm not very familiar with ADB. From reading all night and this morning, I believe I root, unlock bootloader, flash recovery, flash custom roms?
Click to expand...
Click to collapse
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium

abhipati said:
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?

smartnphone said:
Thanks. I used this for ADB http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
I remember using it for my S2, but I don't quite understand the directions for the http://forum.xda-developers.com/showthread.php?t=1709296 method. Could you dumb it down for this HOX noob?
Click to expand...
Click to collapse
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.

A cool username said:
I'll try to help! all of the following is my interpretation of the rooting method described here: http://forum.xda-developers.com/showthread.php?t=1709296
What you need:
HOX on ATT 1.85
su binary from http://dl.dropbox.com/u/don'tusemeimabadsubinary
EDIT: The su binary above has issues. Use this one instead: http://dl.dropbox.com/u/9060692/su
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Download correct su file (assuming you don't have a problem with this step )
Put su in same directory as ADB. Get to adb command prompt and cd into that directory
Quote from Butters619: cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
NEW - pull sim card
NEW - do factory reset
NEW - when reset is complete, do not replace sim, do NOT connect to wifi. Go through setup, go to settings, enable USB debugging. When that's done:
Enter these commands in adb:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
(If you get file doesn't exist after the FIRST command don't worry - they may not be there)
Now, on the phone, go to settings and check for software update. It will tell you you need to connect to network. Now, replace the SIM OR connect to wifi. Have it check for software update again. When it's done, do NOT click "yes" or "ok" on the phone. Simply:
Enter these commands in adb:
adb shell ls -l /data/local.prop
IF AND ONLY IF you get "file not exists" or anything like that then set your phone's date 2 days ahead and reboot the phone and start over. If you get file info, you're golden. Proceed...
Enter these commands into adb:
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Reboot via adb by entering this command: adb reboot
After phones reboots
Enter these commands in adb:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
You should be rooted.
Click to expand...
Click to collapse
Thanks. Yeah i've been trying it alld ay but it can't find where my SU is. it's in the same location as the ADB stuff i believe C:\android-sdk-windows. Seem like some of the senior members are willing to go through teamviewer to help the ones who can't do it. I'll try asking them :/

Sorry I couldn't be of any help, but please let me know if/how you get this to work just in case this happens to me when I get my one x.
Sent from my Touch Pro 2 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
blinkbomber said:
Hey guys. I just got my HOX and have been trying to root it. The software update keeps popping up and I keep refusing, so no worries there. I've got 1.85 right now and have been attempting the methods found here and here, but they just aren't working. I'd prefer to use the manual method. Someone willing to help a guy get started with all this would be the greatest person ever, just saying!
Click to expand...
Click to collapse
I wonder if the one who actually started this thread got his/her phone to work...???
Sent from my Touch Pro 2 using xda app-developers app

Someone think they can help me root the phone? I'm on 1.85 and I believe I finally got adb to recognize my device but after that I don't think I'm doing it right
Sent from my SGH-I777 using XDA Premium App

[Root] RockMyMoto (Yes, even the first OTA)

This will void your warranty, like all root exploits. Use this at your own risk. Do not take OTAs on rooted devices unless you know what you are doing, as it may cause a bootloop or a soft brick.
RockMyMoto is designed for MotoXs that have recieved the Camera update, patching PwnMyMoto. If you are unsure of your firmware, try PwnMyMoto first.
First step is to install Cydia Impactor, by Saurik. http://www.cydiaimpactor.com/ This is required. You will also need adb installed and working, and be comfortable with the command line. Your phone must be on the same network as your PC.
Figure out the ip address of your phone:
adb shell getprop dhcp.wlan0.ipaddress
Click to expand...
Click to collapse
unzip RockMyMoto-{version}.zip and push the exploit and su to /sdcard/:
adb push su /sdcard/
adb push RockMyMoto.jar /sdcard/
Click to expand...
Click to collapse
Run Impactor and select "# start telnetd as system on port 2222", then hit start.
Once the process is complete, run telnet:
telnet {your phone's ipaddress} 2222
Click to expand...
Click to collapse
Run the exploit through telnet
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
The exploit will tell you to use adb to reboot:
adb reboot
Click to expand...
Click to collapse
Run the exploit through telnet for the second time, it will reboot on it's own:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Run the exploit through telnet for the third time, it will not reboot:
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
Click to expand...
Click to collapse
Wait 0-60 seconds, for su to install, then install SuperSu from the market.
Enjoy!
Known issues:
If you have AP isolation mode enabled in your AP (aka WiFi router) you won't be able to connect to your phone via telnet, disable isolation.
Windows users having trouble see here

Amazing! Trying now...

You are the man!!!!!!!!!!
Sent from my XT1060 using Tapatalk

Doing this now. Wonderful job jcase.
Edit: It works.

OMG It worked like a charm! Thank you jcase!!!
one thing though
adb push RockMyMoto-1.0.zip /sdcard/
Click to expand...
Click to collapse
should have been
adb push RockMyMoto.jar /sdcard/
which should have been extracted with su from the zip.

Okay. I have never rooted like this before. Adb = command prompt? Do I need the SDK? Or just the rockmymoto and the other program?
Sent from my XT1060 using Tapatalk

holyevilcow said:
OMG It worked like a charm! Thank you jcase!!!
one thing though
should have been
adb push RockMyMoto.jar /sdcard/
which should have been extracted with su from the zip.
Click to expand...
Click to collapse
Thanks, fixed

Quick question, does this method force us to reboot recovery for system r/w like pwnmymoto?

d4mi3n said:
Quick question, does this method force us to reboot recovery for system r/w like pwnmymoto?
Click to expand...
Click to collapse
yes it does

Works on windows perfectly. AWESOME WORK !

You never cease to amaze. Nice work bro,

Thanks a ton
Sent from my Nexus 7 using Tapatalk

Major Kudoos to Jcase and saurik. Up and running like a boss.

Thanks jcase! Followed your steps and worked like a charm.
Sent from my XT1058 using XDA Premium 4 mobile app

I haven't taken the update so could I just unfreeze apps, unroot, uninstall root apps, take the update, then run this? I don't want to RSD a third time today.
Sent from my Moto Ghost

Thanks bro, amazing work as usual!
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 03:22 AM ---------- Previous post was at 03:13 AM ----------
Also if anyone is not by a PC you can just type getprop and whatever command to get the info you need using terminal emulator. Just don't type adb shell before getprop. And just typing getprop in terminal emulator will list your whole build.prop or you can just type getprop ro.secure & hit enter & that will tell you whether your s-off or not by listing a 0 or a 1. That was just a example if you just want to find out just 1 line like jcase first command to get your ipaddress. You would just type getprop dhcp.wlan0.ipaddress & hit enter & terminal emulator will list your sensitive data if your not by a PC
Sent from my XT1058 using XDA Premium 4 mobile app

thanks bro! worked beautifully

does anyone know of a way to get the native tethering working after rooting this way on a camera updated vz moto x? thanks
edit: this works: http://forum.xda-developers.com/showthread.php?t=2443562

Quote:
adb push su /sdcard/
adb push RockMyMoto.zip /sdcard/
When I do this step I get an error about no such directory. Please help
---------- Post added at 02:48 AM ---------- Previous post was at 02:38 AM ----------
Now says "read only file system"
---------- Post added at 03:09 AM ---------- Previous post was at 02:48 AM ----------
Okay got past that.
Know saying telnet is not reconized as command
---------- Post added at 03:50 AM ---------- Previous post was at 03:09 AM ----------
Okay I finally got it!! Yay Root!

When I try the telnet action, I get an error that the 'link failed File exists'. If I try to proceed to the next step, same error. My router is an Asus router and I made sure Isolation was unchecked, and there was a setting for telnet (never used this before) and I tried both on and off for that one.
Anybody have a clue how I can get through this?
Thanks!

[Q] SuperSu Installation fails, cannot root

Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks

Backup important pics, videos, and docs that are located in your phone storage. You will need to Odin flash the VRUCML1 tar then run Saferoot. You can download the 1+ GB file from my link below. Unzip it then use Odin to flash the entire tar or tar.md5. Doing this will format your phone's storage.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 4

shark_dude said:
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Click to expand...
Click to collapse
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.

buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?

shark_dude said:
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
Click to expand...
Click to collapse
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.

buhohitr said:
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
Click to expand...
Click to collapse
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?

shark_dude said:
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
Click to expand...
Click to collapse
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.

buhohitr said:
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
Click to expand...
Click to collapse
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?

shark_dude said:
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
Click to expand...
Click to collapse
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Nice work! Thanks for finding that fix.
Sent from my SCH-I535 using Tapatalk 2

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Gotcha, thanks again! I appreciate the prompt responses :good:

i cnt see $ prom
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.

DrunkenZombie said:
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
Click to expand...
Click to collapse
Just continue with the following command:
/system/xbin/su hit enter, you should see the # prompt. Then do the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.

[Q] Weaksauce/Firewater/S-Off Issues

I'll try and be as specific as possible as I hate having to resort to new threads when so many are out there, but I'm really at a loss.
Factory new phone (Verizon m8) or as close too it as possible.
Have tried multiple times installing Weaksauce and SU with the binaries but the binaries never install. Always fail and ask for reboot. The root is activated upon reboot after a minute or so. Rootchecker says root is activated and I have granted permission for a number of apps (Root Checker, Root Explorer, adb shell). I have uninstalled and reinstalled via the instructions and always the same issue of the binaries not installed.
Since the root was activated I have attempted to install firewater anyway.
I was unable to get the push command to work so instead I moved the firewater file into the /data/local/tmp manually with Root Explorer.
I attempt the firewater installation however get the following error when I input the chmod 755 command:
adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
I have given SU privileges to the adb shell and accepted the prompt on my phone. Upon running the last command in the firewater instructions it executes, chugs, but then states the "whelp, firewater doesn't work on your device, yadadada".
I notice when I do the adb reboot command and the phone reboots the "HTC MTP Device" driver always fails when coming back from an adb reboot. I have installed the HTC Sync for the drivers and removed the Sync program. Could this be a driver issue? Or something else? I'm not sure why the chmod 755 command is not permitted? Is that potentially the issue as well?
I can wipe the phone to new if needed. Any assistance would be appreciated.

going through the same exact thing. I have a fresh verizon device and i checked to make sure everything matched up. and they do. Firmware, HBOOT, RADIO, everything.
I get to chugging and then bam..sorry this wont work on your phone etc. Whats also funny is this phone has a brighter clearer display and has a weird serial id. seomthing like FFA something when my original is HT something. Ive also factory reset 12 times.

Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.

Shadow Death said:
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Click to expand...
Click to collapse
adb reboot bootloader yields the following:
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I'll take a look at this sunshine. Thanks for pointing me in the right direction. Any further info from anyone else would be appreciated

jtbndy said:
adb reboot bootloader yields the following:
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I'll take a look at this sunshine. Thanks for pointing me in the right direction. Any further info from anyone else would be appreciated
Click to expand...
Click to collapse
My phone yields the identical information.. Rooted soff'd and all custom romd up time and time again.

Shadow Death said:
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
Click to expand...
Click to collapse
"Sounds like your phones have the newer boot loader" Are you saying Firewater was patched on the newer M8's with updated ones?

S1L3nTShaDoWz said:
"Sounds like your phones have the newer boot loader" Are you saying Firewater was patched on the newer M8's with updated ones?
Click to expand...
Click to collapse
I just exchanged phones with HTC and was still able to use Firewater
Sent from my HTC6525LVW using XDA Premium HD app

jtbndy said:
I'll try and be as specific as possible as I hate having to resort to new threads when so many are out there, but I'm really at a loss.
Factory new phone (Verizon m8) or as close too it as possible.
Have tried multiple times installing Weaksauce and SU with the binaries but the binaries never install. Always fail and ask for reboot. The root is activated upon reboot after a minute or so. Rootchecker says root is activated and I have granted permission for a number of apps (Root Checker, Root Explorer, adb shell). I have uninstalled and reinstalled via the instructions and always the same issue of the binaries not installed.
Since the root was activated I have attempted to install firewater anyway.
I was unable to get the push command to work so instead I moved the firewater file into the /data/local/tmp manually with Root Explorer.
I attempt the firewater installation however get the following error when I input the chmod 755 command:
adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
Unable to chmod /data/local/tmp/firewater: Operation not permitted
I have given SU privileges to the adb shell and accepted the prompt on my phone. Upon running the last command in the firewater instructions it executes, chugs, but then states the "whelp, firewater doesn't work on your device, yadadada".
I notice when I do the adb reboot command and the phone reboots the "HTC MTP Device" driver always fails when coming back from an adb reboot. I have installed the HTC Sync for the drivers and removed the Sync program. Could this be a driver issue? Or something else? I'm not sure why the chmod 755 command is not permitted? Is that potentially the issue as well?
I can wipe the phone to new if needed. Any assistance would be appreciated.
Click to expand...
Click to collapse
Did you follow the instructions here to the letter? http://firewater-soff.com/instructions/
If you could not push firewater to your device, it would indicate that weaksauce root is not working - or you did not wait long enough for it to re-root after the adb reboot. Or you did not catch the root request for an adb shell on your phone because the screen was off....
Make sure you use the second instructions, the Weaksauce method, not the root or temp root method.

berndblb said:
Did you follow the instructions here to the letter?
If you could not push firewater to your device, it would indicate that weaksauce root is not working - or you did not wait long enough for it to re-root after the adb reboot. Or you did not catch the root request for an adb shell on your phone because the screen was off....
Make sure you use the second instructions, the Weaksauce method, not the root or temp root method.
Click to expand...
Click to collapse
The only process I could not complete during the weaksauce root was installing the binaries with SU. It fails every time. I've uninstalled via the weaksauce instructions many times adb rebooted, and still the binaries will never install. Since I can move files around with Root Explorer is there any way to manually install the binaries?
If the root did not take, why does Root Checker say that I have root access a few minutes after reboot? I'm also able to grant SU permissions when asked for it (and approved the SU permission for Root Checker and adb shell).
Seems to me the issue lies with whatever the chmod command does and why that's not permitted or that the MTP drivers fail to install upon reboot.

jtbndy said:
The only process I could not complete during the weaksauce root was installing the binaries with SU. It fails every time. I've uninstalled via the weaksauce instructions many times adb rebooted, and still the binaries will never install. Since I can move files around with Root Explorer is there any way to manually install the binaries?
If the root did not take, why does Root Checker say that I have root access a few minutes after reboot? I'm also able to grant SU permissions when asked for it (and approved the SU permission for Root Checker and adb shell).
Seems to me the issue lies with whatever the chmod command does and why that's not permitted or that the MTP drivers fail to install upon reboot.
Click to expand...
Click to collapse
you can't update binaries till your s-off. Just use weaksauce an download SuperSU from play store don't even open. Then run firewater commands to get s-off then uninstall weaksauce an SuperSU flash twrp an then flash SuperSU for root an you all set.
sent from my red HTC M8 using the free XDA app cause the paid one keeps f/c non stop?

Tigerstown said:
you can't update binaries till your s-off. Just use weaksauce an download SuperSU from play store don't even open. Then run firewater commands to get s-off then uninstall weaksauce an SuperSU flash twrp an then flash SuperSU for root an you all set.
sent from my red HTC M8 using the free XDA app cause the paid one keeps f/c non stop?
Click to expand...
Click to collapse
Without opening SuperSU I still get the same errors (HTC MTP Device Driver fail on adb reboot and the same error for chmod 755 command) as I did before including the firewater whelp message.

jtbndy said:
Without opening SuperSU I still get the same errors (HTC MTP Device Driver fail on adb reboot and the same error for chmod 755 command) as I did before including the firewater whelp message.
Click to expand...
Click to collapse
Fastboot turned off?
Sent from my HTC6525LVW using XDA Premium HD app

Fastboot has been off every attempt.

jtbndy said:
Fastboot has been off every attempt.
Click to expand...
Click to collapse
backup your phone and then do a factory reset then do the process all over again? This might be the way to go. ONce you are back up, install weaksauce then supersu from play store. then go ahead and try the firewater. If no go, then try sunshine but I know its $25 but its easier to use than using firewater.

Can I chime in and ask if this should be done on ART or Dalvik? Or if that even matters

EKnofsky said:
Can I chime in and ask if this should be done on ART or Dalvik? Or if that even matters?
Click to expand...
Click to collapse
Both times I have done it has been on dalvik. Hope that helps.
Sent from my HTC6525LVW using XDA Premium HD app

lucky_strike33 said:
Both times I have done it has been on dalvik. Hope that helps.
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
Thank you very much, I am switching over to Dalvik to test and see if anything works for me.
I have the same bootloader version as was mentioned earlier
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I will report back if firewater works or if SunShine does.

EKnofsky said:
Thank you very much, I am switching over to Dalvik to test and see if anything works for me.
I have the same bootloader version as was mentioned earlier
HBoot-3.16.0.0000
Radio-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
I will report back if firewater works or if SunShine does.
Click to expand...
Click to collapse
Try Firewater first since its free. Good luck.
Sent from my HTC6525LVW using XDA Premium HD app

lucky_strike33 said:
Try Firewater first since its free. Good luck.
Sent from my HTC6525LVW using XDA Premium HD app
Click to expand...
Click to collapse
I ran the SunShine app from http://theroot.ninja/ and it allowed me to S-OFF. At what point was I supposed to pay?

EKnofsky said:
I ran the SunShine app from http://theroot.ninja/ and it allowed me to S-OFF. At what point was I supposed to pay?
Click to expand...
Click to collapse
After it says your phone can be s off and unlocked. Then takes you to PayPal to pay
Sent from my HTC6525LVW using XDA Premium HD app