Related
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
skylineGTR_34 said:
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
Click to expand...
Click to collapse
Wait. So you were s off, then went s on, and are attempting to go s off again? What hboot are you on?
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
CoryTallman said:
Wait. So you were s off, then went s on, and are attempting to go s off again? What hboot are you on?
Click to expand...
Click to collapse
Yes exactly. I am using the same hboot version which is 1.44
Also hboot is still unlocked my be thats the problem ?
At what point in the process are you getting the error?
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
CoryTallman said:
At what point in the process are you getting the error?
Click to expand...
Click to collapse
./revone -P after this commad it waits about 2 seconds and says revone failed (error code -6)
skylineGTR_34 said:
./revone -P after this commad it waits about 2 seconds and says revone failed (error code -6)
Click to expand...
Click to collapse
I may be wrong, but if you've already s off'd, I don't believe you need to do that step. Try skipping on to:
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Click to expand...
Click to collapse
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
I tried every way, no luck.
similar problem
I'm also stuck with "error code = -6" following the ./revone -P step, but since buying the phone from new I've never had it s-off. I've followed every step to a T with absolutely no luck... not sure if there's any binary/kernal stuff that's stopping me getting s-off access...I don't know enough about all that yet.
Anyway if anyone has any advice or has found a way round this issue it'd be awesome to hear from you.
Cheers
Clough85 said:
I'm also stuck with "error code = -6" following the ./revone -P step, but since buying the phone from new I've never had it s-off. I've followed every step to a T with absolutely no luck... not sure if there's any binary/kernal stuff that's stopping me getting s-off access...I don't know enough about all that yet.
Anyway if anyone has any advice or has found a way round this issue it'd be awesome to hear from you.
Cheers
Click to expand...
Click to collapse
If the phone is new, there is no s-off exploit for it. Previous exploits have been patched. There might be hope if you have a US phone as there is a way to revert to earlier firmware provided you're still on hboot 1.44.
Grand rthrues
iElvis said:
If the phone is new, there is no s-off exploit for it. Previous exploits have been patched. There might be hope if you have a US phone as there is a way to revert to earlier firmware provided you're still on hboot 1.44.
Click to expand...
Click to collapse
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
reach777 said:
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
Click to expand...
Click to collapse
Yes it does, and if you took that update, even with hboot 1.44, the exploit has been patched and you have to wait until the revone team finds a new method.
skylineGTR_34 said:
I made s off before using the revone method. I wanted to turn back to stock(I decided to sell the phone at that time) and again I used the revone to remove tampered sign and get my hboot locked.
I am currently using my phone but no matter how much I tried I am stuck with error code -6 as a result cannot s-off again. Is there a solution for this? I tried on stock, stock rooted, custom roms and different kernels. I also tried the moonshine with stock rom but no luck again. If there is any one could solve this please help.
Click to expand...
Click to collapse
1. Check that you have hboot 1.44
2. You can try 'Android Terminal Emulator' from PlayStore. and run the same commands there. you need to have the file on the root of your device.
reach777 said:
is this have to do with the ota att send out earlier this month? if so i updated my device, but im still on hboot 1.44.
Click to expand...
Click to collapse
There may still be a way if your phone is on stock AT&T. I have not tried this but this might work for you.
http://forum.xda-developers.com/showthread.php?t=2398717
engage fica1di
dgtiii said:
Yes it does, and if you took that update, even with hboot 1.44, the exploit has been patched and you have to wait until the revone team finds a new method.
Click to expand...
Click to collapse
Thanks for the clarification.
iElvis said:
There may still be a way if your phone is on stock AT&T. I have not tried this but this might work for you.
http://forum.xda-developers.com/showthread.php?t=2398717
Click to expand...
Click to collapse
Thanks for the info but that sounds scary to do. I'm still a noob at this i think i'll wait for the rev team to find a workaround.
Hi,
I have been attempting to get S-off on my ATT HTC ONE
HBOOT 1.44
Software 1.26.502.15
Sense 5.0
Android 4.1.2
Unlocked and rooted, on a completely stock ROM
Have tried Revone numerous times and first I was getting error code 2, and now I get error code 6, checked multiple threads for poss solutions and none have worked.
I have tried using the PC, and a terminal window on the phone with no success
Anyone have any suggestions? I would really like to convert it to a google play edition and move on with my life haha.
Ive also tried some of the all in one toolkits and still nothing
godzilla_753 said:
Hi,
I have been attempting to get S-off on my ATT HTC ONE
HBOOT 1.44
Software 1.26.502.15
Sense 5.0
Android 4.1.2
Unlocked and rooted, on a completely stock ROM
Have tried Revone numerous times and first I was getting error code 2, and now I get error code 6, checked multiple threads for poss solutions and none have worked.
I have tried using the PC, and a terminal window on the phone with no success
Anyone have any suggestions? I would really like to convert it to a google play edition and move on with my life haha.
Ive also tried some of the all in one toolkits and still nothing
Click to expand...
Click to collapse
You could try using a different method, such as moonshine or the one I used, Rumrunner. You might need to use another ROM but I'm not 100% sure if that'll help.
JasSingh93 said:
You could try using a different method, such as moonshine or the one I used, Rumrunner. You might need to use another ROM but I'm not 100% sure if that'll help.
Click to expand...
Click to collapse
Ive actually tried rumrunner and moonshine as well, cant remember off the top of my head what the errors were, but I can retry tonight after work and post my results. I was on a different ROM initially when I was getting error code 2, but my kernal was all jacked as well, I didnt have a working camera or wifi so I booted up a new stock ROM and now I get the error code 6...
godzilla_753 said:
Ive actually tried rumrunner and moonshine as well, cant remember off the top of my head what the errors were, but I can retry tonight after work and post my results. I was on a different ROM initially when I was getting error code 2, but my kernal was all jacked as well, I didnt have a working camera or wifi so I booted up a new stock ROM and now I get the error code 6...
Click to expand...
Click to collapse
I'm not sure what to suggest, which ROM are you using at the moment, just a normal stock one? I was using ViperOne when I managed to gain S-OFF. I was on HBOOT 1.54.
At what stage of the process do you get the error?
JasSingh93 said:
I'm not sure what to suggest, which ROM are you using at the moment, just a normal stock one? I was using ViperOne when I managed to gain S-OFF. I was on HBOOT 1.54.
At what stage of the process do you get the error?
Click to expand...
Click to collapse
Yep normal stock rom. When I enter:
SU
cd /data/local/tmp
chmod 755
./revone -P
gives me failed: error code -6
never reboots. Ive tried rebooting manually from this point, reopening a command window and moving on to the ./revone -s 0 -u command it says successful but it is still S-on when loading into bootloader
godzilla_753 said:
Yep normal stock rom. When I enter:
SU
cd /data/local/tmp
chmod 755
./revone -P
gives me failed: error code -6
never reboots. Ive tried rebooting manually from this point, reopening a command window and moving on to the ./revone -s 0 -u command it says successful but it is still S-on when loading into bootloader
Click to expand...
Click to collapse
Found this online. http://androidtechy.com/index.php/gadgets/phones/82-htc-one-is-granted-s-off-by-revolutionary.html
Download revone (above) and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and:
cd /data/local/tmp
chmod 755 revone
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
Might you have missed the "revone" after the 755 command? Also try switching to superuser again after the chmod command as the link suggests, since you have root it may help.
JasSingh93 said:
Found this online.
Download revone (above) and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and:
cd /data/local/tmp
chmod 755 revone
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
Might you have missed the "revone" after the 755 command? Also try switching to superuser again after the chmod command as the link suggests, since you have root it may help.
Click to expand...
Click to collapse
Sorry I was typing from memory, I typed it just as you said, with the revone after chmod 755. Ill try the SU again really fast and report back.
EDIT: nope no luck still.
godzilla_753 said:
Sorry I was typing from memory, I typed it just as you said, with the revone after chmod 755. Ill try the SU again really fast and report back.
EDIT: nope no luck still.
Click to expand...
Click to collapse
You mentioned you tried reboot manually and proceeding to s-off. Did you try running revone -P and when it fails, perform a full reboot and running the same command again? I assume your fast boot setting is off and USB debugging on, correct?
JasSingh93 said:
You mentioned you tried reboot manually and proceeding to s-off. Did you try running revone -P and when it fails, perform a full reboot and running the same command again? I assume your fast boot setting is off and USB debugging on, correct?
Click to expand...
Click to collapse
Im currently at work, and just running all this thru a terminal command window, but yes fast boot off, usb debugging on.
I guess to do that Id have to be using the PC to do the reboots after putting in the commands.
godzilla_753 said:
Im currently at work, and just running all this thru a terminal command window, but yes fast boot off, usb debugging on.
I guess to do that Id have to be using the PC to do the reboots after putting in the commands.
Click to expand...
Click to collapse
I've been doing some research and apparently your software was from an OTA update and prevents the S-OFF exploit. You may need to downgrade your version for the s-off methods to work.
Have a look at this: http://forum.xda-developers.com/showthread.php?p=45487258#post45487258
"The issue is with 1.26.502.15 not HBOOT. Downgrade from 1.26.502.15 to 1.26.502.10 then upgrade to 1.26.502.12. The HBOOT will still be 1.44. (S-OFF using revone works)."
Sounds like a common problem with this software version.
Revone
godzilla_753 said:
Hi,
I have been attempting to get S-off on my ATT HTC ONE
HBOOT 1.44
Software 1.26.502.15
Sense 5.0
Android 4.1.2
Unlocked and rooted, on a completely stock ROM
Have tried Revone numerous times and first I was getting error code 2, and now I get error code 6, checked multiple threads for poss solutions and none have worked.
I have tried using the PC, and a terminal window on the phone with no success
Anyone have any suggestions? I would really like to convert it to a google play edition and move on with my life haha.
Ive also tried some of the all in one toolkits and still nothing
Click to expand...
Click to collapse
plzz send me revone its not downloading now if u have plzz send me
[email protected]
I have an AT&T HTC One that I have successfully bootloader unlocked and rooted.
I cannot get it to S-OFF
I have hboot 1.44 so I have tried both revone and Moonshine.
I have tried with the stock ROM (don't know what version): ./revone -P would give me error ID 2 and Moonshine would try 10 times with a failure of Don't drink and Shine!
I have tried with Android Revolution based on 4.4: ./revone -P would give me error ID 1 and Moonshine was unable to pass the 2nd ADB test (phone would freeze after rebooting)
I have tried with stock roms based on 4.2 and even on 4.1: ./revone -P would give me error ID -6 and Moonshine would try 10 times with a failure of Don't drink and Shine! I read that -6 was a matter of persistence, but I tried a hundred time on two different roms and had no success.
I read something somewhere that past a certain firmware, the exploit that allowed both revone and Moonshine to function was already patched. Is it impossible to S-OFF my phone now? I'm not 100% sure where to check my software version, but I am on the 4.1.2 Stock-based rom now and under About -> Software Information the Software number shows as 1.26.502.15
Anyone help?
ZippyDan said:
I have an AT&T HTC One that I have successfully bootloader unlocked and rooted.
I cannot get it to S-OFF
I have hboot 1.44 so I have tried both revone and Moonshine.
I have tried with the stock ROM (don't know what version): ./revone -P would give me error ID 2 and Moonshine would try 10 times with a failure of Don't drink and Shine!
I have tried with Android Revolution based on 4.4: ./revone -P would give me error ID 1 and Moonshine was unable to pass the 2nd ADB test (phone would freeze after rebooting)
I have tried with stock roms based on 4.2 and even on 4.1: ./revone -P would give me error ID -6 and Moonshine would try 10 times with a failure of Don't drink and Shine! I read that -6 was a matter of persistence, but I tried a hundred time on two different roms and had no success.
I read something somewhere that past a certain firmware, the exploit that allowed both revone and Moonshine to function was already patched. Is it impossible to S-OFF my phone now? I'm not 100% sure where to check my software version, but I am on the 4.1.2 Stock-based rom now and under About -> Software Information the Software number shows as 1.26.502.15
Anyone help?
Click to expand...
Click to collapse
have you tried rumrunner s-off
boroboy69r said:
have you tried rumrunner s-off
Click to expand...
Click to collapse
Of course I ran across rumrunner in my searches here http://forum.xda-developers.com/showthread.php?t=2488772
But according to this post, the hboot must be version 1.54 or 1.55. It specifically says I must use revone or Moonshine if I am running 1.44. So I haven't tried it yet but I guess it can't hurt ...
ZippyDan said:
Of course I ran across rumrunner in my searches here http://forum.xda-developers.com/showthread.php?t=2488772
But according to this post, the hboot must be version 1.54 or 1.55. It specifically says I must use revone or Moonshine if I am running 1.44. So I haven't tried it yet but I guess it can't hurt ...
Click to expand...
Click to collapse
Check date of bootloader, if it's before June 2013 then use the following ROM to get S-Off, using revone:
Android_Revolution_HD-One_9.4.zip 970.8 MB
https://mega.co.nz/#!aZkF2IIC!UIL4ww1y-bhTq4sQOEVjsi89pmI2GkwCPLMRDlNrrjM
MD5: 06c863ce41b0d5001290737a31e198a1
if the date of bootloader is June 2013 or later then it's a patched version, there's a downgrade method linked here: http://forum.xda-developers.com/showthread.php?t=2431515
nkk71 said:
Check date of bootloader, if it's before June 2013 then use the following ROM to get S-Off, using revone:
Android_Revolution_HD-One_9.4.zip 970.8 MB
https://mega.co.nz/#!aZkF2IIC!UIL4ww1y-bhTq4sQOEVjsi89pmI2GkwCPLMRDlNrrjM
MD5: 06c863ce41b0d5001290737a31e198a1
if the date of bootloader is June 2013 or later then it's a patched version, there's a downgrade method linked here: http://forum.xda-developers.com/showthread.php?t=2431515
Click to expand...
Click to collapse
Thanks so much nkk. Looks like that is exactly my problem. My hboot shows July 5, 2013, so off to follow that guide and I'll let you know what happens.
ZippyDan said:
Thanks so much nkk. Looks like that is exactly my problem. My hboot shows July 5, 2013, so off to follow that guide and I'll let you know what happens.
Click to expand...
Click to collapse
you can also RUU to android 4.3 hboot 1.55 sense your AT&T and then rumrunner will work
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
clsA said:
you can also RUU to android 4.3 hboot 1.55 sense your AT&T and then rumrunner will work
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I tried this but I kept getting error 155 when running the RUU program. I think that is because I had to relock my bootloader first and I didn't know that. Anyway, I got it working with hboot 1.44 now so I think that is better.
nkk71 said:
Check date of bootloader,
if the date of bootloader is June 2013 or later then it's a patched version, there's a downgrade method linked here: http://forum.xda-developers.com/showthread.php?t=2431515
Click to expand...
Click to collapse
Well with persistence I finally got this to work.
There is another link farther down in your link which I think has easier to understand instructions:http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55
However, the real key comes in step 3.
I got stuck on step 3 for a while because your link shows three different options for downloading. I assumed that all three were the same. Actually option A and C are the same (http://d-h.st/qEY). They seem to be a TWRP backup. I checked the md5 of my download and unzipped this file to the TWRP backup directory on my phone. But no matter what I tried it always failed to restore.
I finally figured out that option B is a different download (https://mega.co.nz/#!vwJGhYjb!A6D3TjhtSxhPOQwYJZR373gH418YeN3hTfC6uSgJSZA) and it is actually a ClockworkMod backup even though it is labeled as TWRP. So I flashed ClockworkMod to my recovery and unzipped this download to the ClockworkMod backup directory on my phone. I was then able to successfully restore this backup and downgrade my phone to 1.26.502.10.
After that I just had to relock my bootloader, and use the RUU file to get to 1.26.502.12.
I then unlocked the bootloader again, flashed TWRP to my recovery again, and used that to root the 1.26.502.12 install.
I was then able to finally use revone successfully to S-OFF the phone, remove the tampered tag from the bootloader, and set my SUPERCID.
Finally, I installed Android Revolution 41 mod running Android 4.4 and everything is working great!
Thanks!
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.
Hi
I can't make S-Off on my HTC One M7 - CID - HTC__032
The problem is in adb shell when I write in cmd :
chmod 755 /data/local/tmp/firewater
And then the process doesn't start, I see
Viperone:# or sth like this but I have root rights on adb. Tried on two PCs, one with Windows 7 and second on Windows 8.1, all 64-bit.
How to solve this problem?
You do realise after that command u have to type /data/local/tmp/firewater for it to start?
oopsss i didnt realise that
OK, thanx now got S-Off
Good to hear
nateboi81 said:
You do realise after that command u have to type /data/local/tmp/firewater for it to start?
Click to expand...
Click to collapse
I did exactly what you said and nothing happens in my case.
I have hboot 1.57 and all drivers,fastboot and adb are working perfect.
I tried using cm with their s-off kernel and on latest arhd with elementalx kernel without any luck.
Do you have any advice for me?
s-0ff
You may have too new a bootloader for Firewater.
Might need to spend $25 to get in done via Sunshine.
Google 'Sunshine s-0ff' and you will find their site.
I have used it, and it works easy. After that, you can install
a custom recovery, root it, and use stock software or find a custom
rom. I like the custom roms far better than stock. You may too!