It's alright. I just flashed the insecure kernel in the development section and I'm good to go. Thanks.
Last edited:
Hmm. Can you run an app that asks for root permission? Like root checker to make sure you have root access. Make sure SuperSU is up to date as well.
It says to use USB 2.0 and also in the thread someone says to make sure you use USB 2.0...... My question is what if your computer doesn't have that? My laptop only has USB 3.0 and would like to do this but don't want to brick my phone.
Has anybody tried and suceeded with these steps using a 3.0 jack.
Has anybody tried and suceeded with these steps using a 3.0 jack.
I get all the way to being able to run firewater. I say Yes and it starts. It gives me the 2 minute disclaimer 3 times or so then says the first bottle is open then chugging. After that the phone reboots and the shell closes. When I adb reboot Bootloader is says S-On still so something in firewater isn't working for me. Using weaksouce root, verizon HTC One M8.
mchief298
Senior Member
May have to try it a couple of times. Did that to me, too. Worked on the 2nd try.
Sent from my VK810 4G using XDA Premium HD app
Are you positive you are on USB 2.0? I forgot that my desktop was entirely USB 3.0 except for 2 ports in the rear so I originally had it on USB 3.0 and it failed.
Yes, my laptop has a single USB 3 and one USB 2 and I am on the USB 2 port. I have tried it twice now. I will try it a couple more times I guess.
Verify md5 sums and try again. I disabled zip signature verification and it worked for me.
Hmm. All that command does is move the file over to the android phone. Try to do that manually. Download the file manually to your internal sdcard and then move it to tmp via root explorer or similar utility. Then continue the steps as normal.
There are reports of people who have and sad to say, they said it will fail, but no reports of bricks though.
Yep, some people have to try it multiple times. I'll update the guide.
Nevermind. Got it working. S-off!!!! waited a year for my s4's bootloader to be unlocked and s-off was achieved on this device in less than 2 weeks. Amazing. Thanks for everything.
Last edited:
It makes sense that su would fail there, since su calls the program su. Without root, firewater will never work. Try hard rebooting the phone and see if weaksauce comes back okay.
Yeah, some browsers corrupt zips as they are being downloaded. So make sure you have a good zip. I use winrar to test archives I suspect of being bad.
No need for a VM. It can be done natively. Just download the mac sdk (linked in the guide) and use terminal instead of command prompt.
I got S-Off and custom recovery, thanks! I installed SuperSU and it works. However, the first time an app asks for SU permission, it pauses and takes like 15-20 seconds or so instead of immediately asking (and the app hangs while waiting). Is there a way to fix this? After granting permission, there is no delay in using the app.
Yeah, I have that happen sometimes too, but not that often. Try updating the su binary and rebooting the phone. Otherwise, you may have to contact the SuperSU developer.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
73How to Achieve Permanent Root and S-Off:
To get permanent root, you need to S-Off. So lets start with that first. This process will NOT wipe your device. It also works for OS X users. This guide will work on software version 1.55.605.2 (which as of 04/19/2014 is the latest OTA) and below.
--- S-OFF Instructions ---First, you'll need to download adb, enable its use and setup debugging.
- adb is part of the android SDK. You can download it here (OS X users must scroll down and download the OS X version). It does not need to be installed, just unzip it into its own folder. You can also download a zip that contain only adb and fastboot.
- once you have adb, you'll need to download the drive for your M8, which can be had from HTC's driver page:
http://www.htc.com/us/software/htc-sync-manager/.
Then install it. It will install the driver necessary for adb to work. After the installation is finished, uninstall HTC Sync immediately (do this regardless of whether or not you need it; you can reinstall it later if you still want it). This will leave the driver package installed, but remove HTC sync. - Now, back to the phone. Disable all security you have on, including PINs, Pattern Locks, passwords, etc. If you have an exchange forced security policy, you will need to disable the account. You can readd it later.
- Enable access to developer options. Jump into the Settings. Then you’re going to scroll down to the bottom and tap on ‘About’, next tap on ‘Software Information’. Now you’ll need to tap on ‘More’, which will give you a new menu. Now just tap on the build number 9 times and you’ll enable Developer options.
- Go into developer options menu and enable USB Debugging.
- Next, go to Security page and enable "Unknown sources".
- Now install weaksauce from here:
http://xdaforums.com/showthread.php?t=2699089 - If you followed the directions correctly, you should have SuperSU installed and root access. (You can use superuser as well).
- Plug in your phone into your computer. Its best to use the factory cable provided with the phone. Use a USB 2.0 type port if possible (USB3.0 ports typically have a blue tab; I have personally used a USB 3.0 Device on Windows 8.1u to perform this without any problems, but your mileage may vary).
- Your phone will ask if you if you trust your computer (RSA). Choose "Always Allow".
- Ensure adb is working by opening a command prompt (terminal on OS X), navigate to the adt-bundle-[XXXXX]/sdk/platform-tools and typing "adb devices" without quotes. Your phone should show up. Ensure the working directory is the directory that adb is in. Otherwise, transferring firewater may fail. On Windows, you can shift-right-click inside the folder adb is in and click open command prompt to open a cmd in that directory.
- Now go download firewater from here:
http://firewater-soff.com/instructions/ Make sure to use the weaksauce method (second method). Do NOT use the temproot method.
The firewater file should be called "firewater" without any quotes or extensions (like .bin). Ensure your browser did not partially download or corrupt it.** Make sure its in the same folder as adb. Then follow directions on the firewater site. Be aware the yes/no prompt is case sensitive, so make sure to answer it with an uppercase Y as in "Yes" not "yes". During the process, you will need to enable adb shell to get root. Make sure your phone screen is on so you can see the root request. Grant it and the S-Off process will continue. Otherwise, it will hang there and eventually time out. Sometimes, the process will fail and the phone will reboot. This is okay. Just restart the process. It can sometimes take multiple tries. - When completely successfully, you now have S-OFF. Your phone's bootloader is also unlocked in the process; you do NOT need to perform any additional steps to unlock the bootloader. However, you do not have permanent root. The root that weaksuace provides goes away on reboot and must be reapplied again on startup.
Getting permanent root:
-Flash a custom recovery and flash a zip with su.
-[Optional] Return to stock recovery This option is for people who don't want a custom recovery.
Be aware, once rooted and S-Off'ed, you do NOT need the kernel module that enables system write access*. All system changes will survive hard reboots (adb reboot).
-- Recovery Rooting: --- Move the supersu zip onto your internal sdcard. It can be downloaded here:
http://xdaforums.com/showthread.php?t=1538053
You can use Superuser as well. Its your preference, but this guide uses SuperSU. - Uninstall weaksauce. It's no longer needed.
- Uninstall SuperSU. It will be reinstalled when you flash the supersu zip. If you have SuperSU Pro installed, you can leave that in place, as that app only holds a key.
- From adb, type:
adb reboot bootloader - Flash a custom recovery. CWM and TWRP are available. Use the fastboot method. Follow the directions here:
TWRP - http://teamw.in/project/twrp2/226
CWM - http://xdaforums.com/showthread.php?t=2708520 - Reboot into Recovery
- Flash the supersu zip you downloaded.
- Reboot and you're done. You have s-off and permanent root.
-- Manual Root --Perform all steps noted in section "Recovery Rooting" above.
-Download the stock recovery:
http://xdaforums.com/showthread.php?t=2723112
-Ensure the stock recovery img file is in the same folder as fastboot.
-Run the following command from command line: "fastboot flash recovery stockrecovery.img" without the quotes.
-Wait for the process to finish
-Reboot the phone. You now have the stock recovery along with root. With the stock recovery installed, you can now accept OTAs provided you haven't modified/deleted any stock system files. Any new OTAs you take will remove any files/folders you added to the system partition and will remove your root. However, with S-off, this can be undone. If you lost loot after taking an OTA, simply start from the beginning of the section "Recovery Rooting".
-- Common Tweaks --This is unnecessary if you are on a More Everything plan or are paying for hotspot/tethering. You can force enable the native tethering application:
All of these are optional and are NOT required. However, you may find some benefit to them.-- Wifi Tether Enabled --
http://xdaforums.com/showthread.php?t=2708548
-- Device Wipe after ten attempts --I really dislike this "feature". Here is how to disable it. This works regardless if you enabled the security or its mandated by an exchange policy.
I use Root Explorer to make this change, but you can use any text editor. Make sure to mount system as R/W. Root explorer can do this from within the app.
Edit this file:
/system/customize/ACC/default.xml
change this:
to thisCode:<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">10</item>
Reboot and its disabled.Code:<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">0</item>
-- Power Saver Mode --Enable "Power Saver" mode using these directions. It's disabled and hidden by default.
http://xdaforums.com/showthread.php?t=2701909
-- *Unsecured Kernel --By default, the stock kernel prevents write access to /system. S-off and root should allow you to makes changes to system. However, some people have reported difficulties using ROM toolbox and other mods (like changing boot animations). In some cases, these issues can be resolved by flashing an insecure kernel:
http://xdaforums.com/showthread.php?t=2708686
-- HTC Sense Broswer --The stock ROM now includes Chrome as the default browser and omits the Sense Browser. Users who prefer the Sense Browser can download it here:
http://xdaforums.com/showthread.php?t=2708597
-- HTC Flashlight --The stock HTC flashlight app.
http://xdaforums.com/showthread.php?t=2697025
-- Disable HTC Sync Virtual CDROM --This disables the virtual CD-ROM from mounting.
http://xdaforums.com/showthread.php?t=2709386
-- Donations --Don't forget to donate to the developers involved in getting you here. Donations for firecracker go to firewaterdevs@gmail.com (paypal). Donations for weaksuace go to HTCWeakSauce@gmail.com (paypal). If I missed anyone, let me know.13FAQBeen getting some interesting PMs. Here is some of the popular questions.
Do I need a Java card for this?
No. You just need a PC/Mac, a USB 2.0 cable and the M8. Since a public S-off method is now available, that method is obsolete and its not recommended anymore.
Do I have to change or reset my CID?
No, that is only necessary for people who s-off'ed via a Javacard.
Do I need to do any of this if I S-off'ed via Javacard?
No, this method ends with the same result.
Can I reverse this and return to completely stock?
Yes, absolutely none of the stuff done here is permanent. You can unroot, relock the bootloader, and S-On as many times as you want. You can flash an HTC RUU to return to completely stock in one go. Note: Be careful with S-On'ing a device. If you S-On a device via a newer RUU and that RUU has no known exploits, you may not be able to S-Off again until an exploit is found.
Do I need to unlock my bootloader after this?
No, the firewater exploit will S-Off and unlock your bootloader.
Will this work on a Mac?
Yes, please read the directions more carefully.
Will this work on USB 3.0 ports as that is all I have?
Usually. On OS X, I've had success using a USB 3.0 port (since recent MBPs only include USB 3). On Windows, the answer seems to be maybe, depending on your OS. Your best bet would be to try on a Windows 8,8.1,8.1u1 machine as that OS includes native support for USB 3.0; that way you aren't relying on vendor specific driver support like on Win7 or below. I have personally done this exploit on USB3 on a Surface Pro.
Will this brick my phone?
There is always a chance, but I have honestly never heard of such a thing happening. Worst case is usually a full reset of the phone.
Will this wipe/format the external SDcard?
No.
How do I flash this via ODIN?
This has absolutely nothing to do with ODIN. That is for Samsung devices. You should not even have ODIN running when do any part of this guide.
How to I convert to a Google Play edition ROM?
Wait for a developer to make one. I will post a link here if/when that happens.
See here:
http://xdaforums.com/showthread.php?t=2716306
Does this affect Google Wallet or ISIS?
Yes and no. Google wallet works just fine. ISIS will detect its rooted and refuse to work. You'll need to shield root from ISIS to use it. Directions on how to do that can be found via google.
Will this work on non-Verizon HTC M8's?
Yes, though you will need to use a different recovery.
Will this unlock my device for other carriers?
No....because your device is already unlocked in its stock form. AWS band rules force Verizon to keep all their LTE devices unlocked.
Will this jailbreak my device?
No. Wrong type of phone.
I can get red triangle exclamation mark with a black screen. How do I fix this?
You are in the stock recovery. Hold power and volume up and you will get a menu. You can choose reboot system now to get out of there.322
Absolutely. Everything in this guide can be reversed. You can return everything back to stock via an RUU.
You do not. I have modified and added a few system files and they have persisted through several hard reboots.
