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

Root S off is here!

Granite1 said:
Absolute truth there EM.

I didn't boot into Ubuntu because I need to know how the Windows method will work. Most folks will go that route. :)

I now have a better understanding of the driver issues and complexities with Windows. :p

The big thing really was to keep the screen on. Once the screen timed out on the phone the connection was lost. I should have selected to keep the screen on in developer settings. :o

Also, welcome to the dark side Scotty! :D
Click to expand...


Ahhh very good call mister granite! Right you are,most folks will want to go windows route. I've kind of given up as folks move up to win 8/8.1 since I don't have that,I can't help them anyway :o you have gained some valuable insight on the process :cool:
 
scotty85 said:
Ahhh very good call mister granite! Right you are,most folks will want to go windows route. I've kind of given up as folks move up to win 8/8.1 since I don't have that,I can't help them anyway :o you have gained some valuable insight on the process :cool:
Click to expand...

My machines are still on Windows 7, so it's bearable. I hear Windows 8 is a heck of a lot worse.

Ultimately, EM is right. Load up a Live CD, or Dual Boot and it eliminates a whole pile o' gibberish.

Open a terminal session in Ubuntu, issue commands, profit! No messin around. :)
 
I got caught reading all the procedures till about 4am, then I started tinkering with the all-in-one utility to get unlock, and then went to bed angry and unfulfilled LOL.

Anyhoo, in a nutshell, I need to:

Unlock Bootloader (think I will do this manually)
Get temproot (do I?)
Run Firewater
Pop champagne?

Is this correct?
 
Tre Lawrence said:
I got caught reading all the procedures till about 4am, then I started tinkering with the all-in-one utility to get unlock, and then went to bed angry and unfulfilled LOL.

Anyhoo, in a nutshell, I need to:

Unlock Bootloader (think I will do this manually)
Get temproot (do I?)
Run Firewater
Pop champagne?

Is this correct?
Click to expand...

almost ;)

if you have a variant that you can htcdev unlock then you dont need temp root. so:
-unlock bootloader
-temporarily or permantly install recovery(more info in http://androidforums.com/one-m8-all-things-root/845182-htc-one-m8-root-thread.html)
-use recovery to install superuser
-run firewater
-pop champagne! :D
 
scotty85 said:
almost ;)

if you have a variant that you can htcdev unlock then you dont need temp root. so:
-unlock bootloader
-temporarily or permantly install recovery(more info in http://androidforums.com/one-m8-all-things-root/845182-htc-one-m8-root-thread.html)
-use recovery to install superuser
-run firewater
-pop champagne! :D
Click to expand...

Downloaded Firewater, but am stumped at the second command:

adb wait-for-device push firewater /data/local/tmp

I get "cannot 'stat' firewater: no such file or directory."

Does the Firewater dl need to be in a specific file?
 
Now stuck in the last line... I really need to re-prime myself on adb commands:

chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater

One line? Two?

ETA: continually get "bad mode."
 
Finally made it through, and got this.

whelp, this sucks, firewater can not work on your device
no amount of reflashing, retrying, or ruuing will fix...
DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!!
if we are able to fix this issue, it will be announced
bye bye.....sorry it didn't work out.

What the heck...
 
Tre Lawrence said:
Finally made it through, and got this.

whelp, this sucks, firewater can not work on your device
no amount of reflashing, retrying, or ruuing will fix...
DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!!
if we are able to fix this issue, it will be announced
bye bye.....sorry it didn't work out.

What the heck...
Click to expand...

hmm... what variant do you have? what is your build number?

did you meet all the prerequesites? no lock screen,working data connection,etc? have the phone awake so you could grant any superuser requests?

ill have to dig around and see if there have been updates on some devices that have broken the exploit :(

in the mean time,might want to consider trying it on linux, its pretty easy to make a bootable ubuntu cd. failing that,hopefully granite will be along and have some pointers on making it work on windows.
 
scotty85 said:
hmm... what variant do you have? what is your build number?

did you meet all the prerequesites? no lock screen,working data connection,etc? have the phone awake so you could grant any superuser requests?

ill have to dig around and see if there have been updates on some devices that have broken the exploit :(

in the mean time,might want to consider trying it on linux, its pretty easy to make a bootable ubuntu cd. failing that,hopefully granite will be along and have some pointers on making it work on windows.
Click to expand...

Seems like some hardware simply doesn't take; I have Sprint Build 1.54.651.

Thanks for the help...
 
Per data connection, I have not yet activated the phone, but wi-fi is live. I don't think that should have anything to do with it, no?
 
Wifi will work, mine was on Wifi when I did it.

Did you flash recovery, AND flash a rooted ROM?

A rooted rom is needed for Firewater to work.

Make sure you go under Settings / Developer Options / Select "Stay Awake", and USB Debugging.

Make sure when you issue the first command "adb reboot" Don't wait for the phone to boot to issue the second command, just run it.

"chmod 755 /data/local/tmp/firewater/data/local/tmp/firewater" This command needs to be entered just like this.

Honestly, I would run this again. Maybe try and load up a Live CD of Ubuntu to see if drivers are the culprit. Lastly, I don't think the device needs to be activated, but I'm not 100% on that. I believe the current S-off method involves the Qualcomm radio software/hardware, so there's a chance it needs to be activated to work.
 
Granite1 said:
Wifi will work, mine was on Wifi when I did it.

Did you flash recovery, AND flash a rooted ROM?

A rooted rom is needed for Firewater to work.

Make sure you go under Settings / Developer Options / Select "Stay Awake", and USB Debugging.

Make sure when you issue the first command "adb reboot" Don't wait for the phone to boot to issue the second command, just run it.

"chmod 755 /data/local/tmp/firewater/data/local/tmp/firewater" This command needs to be entered just like this.

Honestly, I would run this again. Maybe try and load up a Live CD of Ubuntu to see if drivers are the culprit. Lastly, I don't think the device needs to be activated, but I'm not 100% on that. I believe the current S-off method involves the Qualcomm radio software/hardware, so there's a chance it needs to be activated to work.
Click to expand...

*walks backwards in shame and embarrassment, hoping no one sees him*
 
Tre Lawrence said:
Just tried several times... no go over Viper. :(

I am going to activate the device, and try again.
Click to expand...

Crap, what is going on!! :mad:

When you get ADB working can you type in "adb devices" and see if it will list your device serial #?

Maybe ADB isn't working right. :confused:
 
You must log in or register to reply here.
Back
Top Bottom