Database Develop

Anyone tried rumrunner for radio s off?

Rumrunner has a tool for the HTC one v,wich is very similar hardware. It may work on the sensation xl.
Install a rom with an insecure kernel,and run the one v tool.
I tried it on htc flyer,no harm will be done if the tool doesn't work.
Just wanted to throw it out there if no one has tried it
http://rumrunner.us/
Sent from my HTC PG09410 using xda app-developers app

scotty1223 said:
Rumrunner has a tool for the HTC one v,wich is very similar hardware. It may work on the sensation xl.
Install a rom with an insecure kernel,and run the one v tool.
I tried it on htc flyer,no harm will be done if the tool doesn't work.
Just wanted to throw it out there if no one has tried it
Sent from my HTC PG09410 using xda app-developers app
Click to expand...
Click to collapse
I tried it and it didnt work for me. i sued it in Ubuntu.
I set it up just fine but it didnt s-off me.
i got s-off using the XL Multitool

alexfadhili2 said:
I tried it and it didnt work for me. i sued it in Ubuntu.
I set it up just fine but it didnt s-off me.
i got s-off using the XL Multitool
Click to expand...
Click to collapse
how far did it get,and what errors did it give you?
i assume the xl multitool is just intalling the patched hboot?

I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work
Sent from my Sensation XL using xda app-developers app

alexfadhili2 said:
I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work
Sent from my Sensation XL using xda app-developers app
Click to expand...
Click to collapse
Did you already have the patched hboot installed?
Sent from my HTC6435LVW using Tapatalk

Yes sir.
Sent from my Sensation XL using xda app-developers app

alexfadhili2 said:
Yes sir.
Sent from my Sensation XL using xda app-developers app
Click to expand...
Click to collapse
Then it probably worked, and you just do not know it. it is not installing a new hboot on the one v
If you install a stock hboot you may well find that you are still s off
If you do not want to do that, you can dump p7 for me and I can look at the radio flag
Sent from my HTC6435LVW using Tapatalk

alexfadhili2 said:
I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work
Click to expand...
Click to collapse
The same things EXACTLY happened to me.
I am on Runny-Kitkat 4.4.2 V8 and those are my data before and after the process:
*** UNLOCKED ***
RUNNYMEDE PVT SHIP S-ON
HBOOT-1.28.0006
RADOI-3831.18.00.26_M
eMMC-BOOT
Apr 24 2012,18:59:39
My output:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (3/120)
Waiting
Test 2: Booting device
Waiting for ADB (6/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit

Hasan.Z said:
The same things EXACTLY happened to me.
I am on Runny-Kitkat 4.4.2 V8 and those are my data before and after the process:
*** UNLOCKED ***
RUNNYMEDE PVT SHIP S-ON
HBOOT-1.28.0006
RADOI-3831.18.00.26_M
eMMC-BOOT
Apr 24 2012,18:59:39
My output:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (3/120)
Waiting
Test 2: Booting device
Waiting for ADB (6/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit
Click to expand...
Click to collapse
ahhhh,the tool did not run. the test 1 and test 2 reboots do not count.
when it works,the tools output should be this:
Code:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (18/120)
Waiting
Test 2: Booting device
Waiting for ADB (38/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (17/120)
Waiting for ADB (38/120)
must ferment longer...
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1).....................
Waiting for ADB (39/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
[email protected]:~/Downloads$
you may need to be on a different rom. when i ran it on the flyer,i had similar issues until i installed a sense 4 ICS rom. it would not work on the flyer due to lack of a new enouf kernel since the xl went to ICS it should theoretically work.
if anyone feels adventurous,try it with different roms,and/or dump mmcblk0p7 and ill make sure the board layout is the same:
adb shell
su (if needed to get a # prompt)
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
upload the file that appears on your sd card and pm me a link to it

alexfadhili2 said:
I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work.
Click to expand...
Click to collapse
This is my dump file.

HTC Hboot 1.56 on Android 4.2

Guys, I need help on this, currently im stuck on Android 4.2 hboot 1.56 and i cant downgrade it on, like 1.44 etc.. etc.. The thing is my friend of mine just flash it on Stock_Odex_2.24.709.1_Final.Zip, because i flash Android revolution hd, without soff it 1st, so the end result of it stuck on the htc logo(bootlooped) before my phone runs on new android 4.4 it runs smooth, having no problems, whatsoever, by the way my phone now is experiencing random restarts, i just cant see any way to soff my phone, here's my latest data on bootloader:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56 0000
RADIO-4A.25.3263.21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014 12:32:09.0
A while ago i performed soju, but failed, It say's
1.> flash an unsecure kernel that's compatible with your ROM and retry rumrunner preffered and most reliable method
2.> flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issiue for you!!!
Better luck next time!!!! bye
Press ENTER to exit
Pls. is there someone or any reliable tutorials out their like youtube, etc.. etc..
Any help will be highly appreciated!!
Thanks!!

ryan_antisocial said:
Guys, I need help on this, currently im stuck on Android 4.2 hboot 1.56 and i cant downgrade it on, like 1.44 etc.. etc.. The thing is my friend of mine just flash it on Stock_Odex_2.24.709.1_Final.Zip, because i flash Android revolution hd, without soff it 1st, so the end result of it stuck on the htc logo(bootlooped) before my phone runs on new android 4.4 it runs smooth, having no problems, whatsoever, by the way my phone now is experiencing random restarts, i just cant see any way to soff my phone, here's my latest data on bootloader:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56 0000
RADIO-4A.25.3263.21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014 12:32:09.0
A while ago i performed soju, but failed, It say's
1.> flash an unsecure kernel that's compatible with your ROM and retry rumrunner preffered and most reliable method
2.> flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issiue for you!!!
Better luck next time!!!! bye
Press ENTER to exit
Pls. is there someone or any reliable tutorials out their like youtube, etc.. etc..
Any help will be highly appreciated!!
Thanks!!
Click to expand...
Click to collapse
Try to use firewater and short instruction

Mutasek24 said:
Try to use firewater and short instruction
Click to expand...
Click to collapse
Thanks for the updates!! Well I just did what i said, Here's what happend:
C:\Users\Anne\Desktop\New folder (3)\platform-tools>adb reboot
C:\Users\Anne\Desktop\New folder (3)\platform-tools>adb wait-for-device push fir
ewater /data/local/tmp
3891 KB/s (4519496 bytes in 1.134s)
C:\Users\Anne\Desktop\New folder (3)\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.5.11 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
********** 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. **********
[email protected]:/ #
Sadly, it failed, It seems to be that, It only supports hboot 1.55, but mine is hboot 1.56 :crying: is there any otherway? Thanks again!!

Aghhhhhh!!!!!
I'm quite desperate about this hboot 1.56!! should i sell my phone because of this? aghhh...

Is there anyone or someone, Succesfully SOFF their htc one hboot 1.56?

It's got nothing to do with the hboot version. Firewater uses an exploid that requires a certain cpu version. You have an older version so it just won't work. Maybe in the future they will do something about it who knows. But for now you are stuck
Sent from my HTC One using XDA Premium 4 mobile app

nateboi81 said:
It's got nothing to do with the hboot version. Firewater uses an exploid that requires a certain cpu version. You have an older version so it just won't work. Maybe in the future they will do something about it who knows. But for now you are stuck
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouch!! how about other stock rom? to upgrade my older version from 4.2 to 4.4 version of android, aside from this my phone keeps on restarting

You don't need s off to be able to install roms. Are you doing a wipe before installing different roms. What recovery and version are you using?
Sent from my HTC One using XDA Premium 4 mobile app

nateboi81 said:
You don't need s off to be able to install roms. Are you doing a wipe before installing different roms. What recovery and version are you using?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply! im using PhilZ Touch 6 CWM Base version: v6.0.4.5
are you sure its ok to just flash rom's like Android Revolution HD 53.0, etc.. etc..? even im running on Android 4.2, S-ON w/ hboot 1.56, the last time i did this i brick my phone, stuck on htc logo, aside from this my phone keeps on restarting while im using it, thats why i want to use other rom's

ryan_antisocial said:
thanks for the reply! im using PhilZ Touch 6 CWM Base version: v6.0.4.5
are you sure its ok to just flash rom's like Android Revolution HD 53.0, etc.. etc..? even im running on Android 4.2, S-ON w/ hboot 1.56, the last time i did this i brick my phone, stuck on htc logo, aside from this my phone keeps on restarting while im using it, thats why i want to use other rom's
Click to expand...
Click to collapse
In order to flash ARHD 53 you need TWRP recovery. Version 2.6.3.3. or higher. You don't need s-off

Yep what he said
Sent from my HTC One using XDA Premium 4 mobile app

donkeykong1 said:
In order to flash ARHD 53 you need TWRP recovery. Version 2.6.3.3. or higher. You don't need s-off
Click to expand...
Click to collapse
Can i still flash it even my phone is stuck on android 4.2? coz ARHD is based on android 4.4,

Yes you can. Just do a full wipe in recovery first
Sent from my HTC One using XDA Premium 4 mobile app

And be sure you have TWRP 2.6.3.3 or higher verzion of recovery. Recomended 2.6.3.3

[Q] S-OFF 1.56 Problems

Currently I'm running ARHD 71.1 with ElementalX 14.10 on my HTC One ul. Its rooted and HTCDev unlocked. The full getvar is attached.
The problem is I can't for the love of God get S-OFF. Before I tried Bulletproof, Elemental 14.12.and even used stock ROM.
But whatever I do I can'T seem.to S-OFF.
I tried Firewater and that used to at least start but now it keeps on saying /data/local/tmp/firewater not found.
I've tried rumrunner but that kept on giving me FATAL: download updated ...from romrunner.us. Then I uninstalled Avast, reinstalled the drivers and it passed that part. But then I got upto 8 pours and it said wait 30 seconds...retry...
Does anyone have any idea what the problem may be? Developer options are on, USB debugging is on, Lock screen is off and ADB + Fastboot is working fine
Please if anyone could help me it would be awesome

ss4adib said:
Currently I'm running ARHD 71.1 with ElementalX 14.10 on my HTC One ul. Its rooted and HTCDev unlocked. The full getvar is attached.
The problem is I can't for the love of God get S-OFF. Before I tried Bulletproof, Elemental 14.12.and even used stock ROM.
But whatever I do I can'T seem.to S-OFF.
I tried Firewater and that used to at least start but now it keeps on saying /data/local/tmp/firewater not found.
I've tried rumrunner but that kept on giving me FATAL: download updated ...from romrunner.us. Then I uninstalled Avast, reinstalled the drivers and it passed that part. But then I got upto 8 pours and it said wait 30 seconds...retry...
Does anyone have any idea what the problem may be? Developer options are on, USB debugging is on, Lock screen is off and ADB + Fastboot is working fine
Please if anyone could help me it would be awesome
Click to expand...
Click to collapse
Try ARHD 31.6, seems the be the prefered one for the job.

Fain11 said:
Try ARHD 31.6, seems the be the prefered one for the job.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll see what happens.
Sorry for the noobish question but downgrading my ROM to 4.3 from 4.4.2 shouldn't cause problems, right?

ss4adib said:
Thanks for the suggestion. I'll see what happens.
Sorry for the noobish question but downgrading my ROM to 4.3 from 4.4.2 shouldn't cause problems, right?
Click to expand...
Click to collapse
I don't think so.
And if you still can't get S-Off, try download a nandroid backup for your device and use the firewater method. It worked for me.
Hope this helps

SBColasito said:
I don't think so.
And if you still can't get S-Off, try download a nandroid backup for your device and use the firewater method. It worked for me.
Hope this helps
Click to expand...
Click to collapse
Which nandroid backup do you suggest?

ss4adib said:
Which nandroid backup do you suggest?
Click to expand...
Click to collapse
Best is the one of your original rom, if u made one.

ss4adib said:
Which nandroid backup do you suggest?
Click to expand...
Click to collapse
I can't find any newer version of nandroid backup for your device. Just try using a stock ROM guru reset: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Just flash it and try the firewater method.
I hope this helps

SBColasito said:
I can't find any newer version of nandroid backup for your device. Just try using a stock ROM guru reset: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Just flash it and try the firewater method.
I hope this helps
Click to expand...
Click to collapse
That would not include an secured kernel?

That's what I used at first

ss4adib said:
That's what I used at first
Click to expand...
Click to collapse
Well I tried going back to ARHD 31.6 but still I get the same errors
Then I installed ElementalX but my phone stopped turning on so I just restored back to what I had.
I don't think S-OFF is gonna work on this phone

ss4adib said:
Well I tried going back to ARHD 31.6 but still I get the same errors
Then I installed ElementalX but my phone stopped turning on so I just restored back to what I had.
I don't think S-OFF is gonna work on this phone
Click to expand...
Click to collapse
What ElementalX kernel version u used? The latest is not for ARHD 31.6.
U need Sense 5.5 Android 4.3 ElementalX kernel "ElementalX-m7-8.4":
http://www.androidfilehost.com/?fid=23269279319202557
Elemental X thread http://forum.xda-developers.com/showthread.php?t=2249774 downolad section.

Fain11 said:
What ElementalX kernel version u used? The latest is not for ARHD 31.6.
U need Sense 5.5 Android 4.3 ElementalX kernel "ElementalX-m7-8.4":
http://www.androidfilehost.com/?fid=23269279319202557
Elemental X thread http://forum.xda-developers.com/showthread.php?t=2249774 downolad section.
Click to expand...
Click to collapse
God damn I'm an idiot. Thanks I'll try this out later when I'm not busy

ss4adib said:
God damn I'm an idiot. Thanks I'll try this out later when I'm not busy
Click to expand...
Click to collapse
What error do you receive when using firewater?
If you get the message "whelp this sucks.........." there is nothing you can do as the message says.
You must wait till new exploit will work for M7 (maybe SunShine will be updated for us).

Also wait until Sushine gets free.
U can also try ARHD and Bulletproof Kernel, or a ViperRom as firewater gets some positive feedback, see here:
http://forum.xda-developers.com/showthread.php?t=2632351&page=114

Well this is what rumrunner says:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (26/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (27/120)
must ferment longer...
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)...........................
pouring (2)............................
pouring (3)............................
pouring (4)...........................
pouring (5)............................
pouring (6)............................
pouring (7)............................
pouring (8)............................
Wait 30 seconds, power on device, pray, run rumrunner again.
Press ENTER to exit
Click to expand...
Click to collapse
and this is firewater:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd: C:\
The filename, directory name or volume label syntax is incorrect.
C:\WINDOWS\system32>cd C:\mini-sdk
C:\mini-sdk>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\mini-sdk>adb wait-for-device push firewater /data/local/tmp
5059 KB/s (4522136 bytes in 0.872s)
C:\mini-sdk>adb shell
[email protected]:/ # su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
sh: /data/local/tmp/firewater: not found
127|[email protected]:/ #
Click to expand...
Click to collapse
Whats wrong????

ss4adib said:
Well this is what rumrunner says:
and this is firewater:
Whats wrong????
Click to expand...
Click to collapse
Rumrunner will not work with hboot 1.56.
Post result from Firewater in Firewater thread.
Did u ensure device is booted to android with usb debugging enabled?
U typed by mistake "/data/local/tmp/firewater" twice? Reboot both device and computer and try again?
Unroot and try methode 2.

Fain11 said:
Rumrunner will not work with hboot 1.56.
Post result from Firewater in Firewater thread.
Did u ensure device is booted to android with usb debugging enabled?
U typed by mistake "/data/local/tmp/firewater" twice? Reboot both device and computer and try again?
Unroot and try methode 2.
Click to expand...
Click to collapse
I typed it to show you what happens

ss4adib said:
I typed it to show you what happens
Click to expand...
Click to collapse
What if u copy "firewater" file to /data/local/tmp?
adb reboot (<--- important!!!!)
And then copy "firewater" file to /data/local/tmp with a root file explorer
then:
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater
I dont have any other ideeas.

No OS installed (Hboot 1.57)

I have an HTC One M7 with Hboot 1.57.0000
It was working perfectly on stock 4.4.2 ROM. But when I tried to S-Off it, I accidentally deleted the stock OS. Now currently the phone is not rooted, relocked and there is TWRP installed on it. I tried finding RUU for it but couldnt succeed. Here is what's appearing on bootloader screen:
***TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.707.3
eMMC-boot 2048MB
Apr 25 2014,21:3259.0
I also tried flashing custom ROM ie CM11 using adb sideload but it didn't work.
Kindly provide me with a link to either stock ROM which can be flashed with S-On or with a link to RUU.
Thanks.

sirius_gamer said:
I have an HTC One M7 with Hboot 1.57.0000
It was working perfectly on stock 4.4.2 ROM. But when I tried to S-Off it, I accidentally deleted the stock OS. Now currently the phone is not rooted, relocked and there is TWRP installed on it. I tried finding RUU for it but couldnt succeed. Here is what's appearing on bootloader screen:
***TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.707.3
eMMC-boot 2048MB
Apr 25 2014,21:3259.0
I also tried flashing custom ROM ie CM11 using adb sideload but it didn't work.
Kindly provide me with a link to either stock ROM which can be flashed with S-On or with a link to RUU.
Thanks.
Click to expand...
Click to collapse
There is no ruu for your phone version. push a rom to your phone using adb push if sideload doesnt work from recovery and install it. CM11 require TWRP 2.7.1.1 to flash correctly and all other 4.4+ roms require twrp 2.6.3.3 or 2.6.3.4 to flash correctly.
To use the sideload method you need at least adb 1.0.29 (latest is 1.0.31) but adb push will works fine everytime.

alray said:
There is no ruu for your phone version. push a rom to your phone using adb push if sideload doesnt work from recovery and install it. CM11 require TWRP 2.7.1.1 to flash correctly and all other 4.4+ roms require twrp 2.6.3.3 or 2.6.3.4 to flash correctly.
To use the sideload method you need at least adb 1.0.29 (latest is 1.0.31) but adb push will works fine everytime.
Click to expand...
Click to collapse
Both adb push and adb sideload are not working. Previously sideload was working but now it has stopped. It gives an error adb sideload complete Failed. When can we expect a RUU for my phone version? :'(
Is there any way by which I can S-off my phone in current state? Only then I can use currently available RUU.

sirius_gamer said:
Both adb push and adb sideload are not working. Previously sideload was working but now it has stopped. It gives an error adb sideload complete Failed. When can we expect a RUU for my phone version? :'(
Click to expand...
Click to collapse
there was no .707 RUU released ever so don't expect any RUU to be released for that version. What was the error when using adb push?

alray said:
there was no .707 RUU released ever so don't expect any RUU to be released for that version. What was the error when using adb push?
Click to expand...
Click to collapse
I tried a few more times and finally adb push worked. Now I've installed 2.24.401.1_Stock_Odex_Not_Rooted_m7_signed_081513_011518.zip
Thanks a lot dear for helping me.
P.S Now how can I update to 4.4.2 i-e Sense 6?

sirius_gamer said:
I tried a few more times and finally adb push worked. Now I've installed 2.24.401.1_Stock_Odex_Not_Rooted_m7_signed_081513_011518.zip
Thanks a lot dear for helping me.
P.S Now how can I update to 4.4.2 i-e Sense 6?
Click to expand...
Click to collapse
your phone must be full stock to take ota updates so no, you can't unless you flash an updated custom rom, like arhd or viper

alray said:
your phone must be full stock to take ota updates so no, you can't unless you flash an updated custom rom, like arhd or viper
Click to expand...
Click to collapse
Can I install ViperOne 6.2.1 with S-On?

sirius_gamer said:
Can I install ViperOne 6.2.1 with S-On?
Click to expand...
Click to collapse
you can install any rom you want with s-on except GPE roms.

alray said:
you can install any rom you want with s-on except GPE roms.
Click to expand...
Click to collapse
Sir I have now installed ViperOne 6.2.1. I then tried to S-Off using firewater, it didn't work. Then I saw a post in which a guy said that one should first install a kernel like Element to make firewater work. So I installed ElementalX and then again tried firewater. It is again giving me the same error.
Code:
C:\Users\Ahmed\Desktop\HTC One Toolkit - Squabbi - 3.1.2>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Ahmed\Desktop\HTC One Toolkit - Squabbi - 3.1.2> adb wait-for-device pu
sh firewater /data/local/tmp
4880 KB/s (4522136 bytes in 0.904s)
C:\Users\Ahmed\Desktop\HTC One Toolkit - Squabbi - 3.1.2> adb shell
[email protected]/# su
su
[email protected]/#
C:\Users\Ahmed\Desktop\HTC One Toolkit - Squabbi - 3.1.2>adb shell
[email protected]/# su
su
[email protected]/# chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]/# /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.7.24 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** 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. **********

sirius_gamer said:
Code:
********** 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. **********
Click to expand...
Click to collapse
Then firewater will not work for your phone. you could try sunshine s-off or s-off via a java card

The never ending quest for 1.57 s-off

Hello all,
I have been trying desperately to s-off my One ever since I got it back from repairs. I have unlocked and rooted but the damn s-off is proving elusive.
I have tried about 4 different roms and 3 kernels to try get firewater to work. Reading up on any other 1.57 s-off threads seems to be sporadic. It'll maybe work for some under various circumstances. I was getting a second "chugging" but then it would freeze for more than 2 mins (I gave it 5, just to be sure). I then tried rumrunner, but that would go to 8 iterations before telling me to pray and try again.
so i tried firewater again, but now I get:
==================== firewater S-OFF 8.0.8.10 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
C:\Android\adb>
Click to expand...
Click to collapse
Is it literally just a constant trial and error battle I must face or has anyone found a more surefire way of getting s-off?
Any help is appreciated.

icanttinkofaname said:
Hello all,
I have been trying desperately to s-off my One ever since I got it back from repairs. I have unlocked and rooted but the damn s-off is proving elusive.
I have tried about 4 different roms and 3 kernels to try get firewater to work. Reading up on any other 1.57 s-off threads seems to be sporadic. It'll maybe work for some under various circumstances. I was getting a second "chugging" but then it would freeze for more than 2 mins (I gave it 5, just to be sure). I then tried rumrunner, but that would go to 8 iterations before telling me to pray and try again.
so i tried firewater again, but now I get:
Is it literally just a constant trial and error battle I must face or has anyone found a more surefire way of getting s-off?
Any help is appreciated.
Click to expand...
Click to collapse
You might have to try Sunshine S-OFF but it will cost you $25 USD!

25 bucks is nothing. And it works. It is so quick and easy