Related
I'm trying to get s-off but revone is keep failing with error code 1.
My One is a developer edition and hboot 1.44
Any idea? Thanks!
pirateye said:
I'm trying to get s-off but revone is keep failing with error code 1.
My One is a developer edition and hboot 1.44
Any idea? Thanks!
Click to expand...
Click to collapse
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Ktan188 said:
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Click to expand...
Click to collapse
It worked! Thanks a lot! :highfive:
Thanks for this I was having the same problem I'm downloading the 4.2.2 rom and doing the backup. I hope this works for me too
Ktan188 said:
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Click to expand...
Click to collapse
Finally.. after hours of Googling an answer! Thanks so much.
Thanks a LOT!!!! I was really hating my device, didn't know what the problem is.
I will try it, finally found an answer...
Thanks...will try your method now.
Thanks!
Thank you very much for the help in this thread
i tried this one via a recovery.
but failed.. Even the Phone didn't boot and also cannot go back in recovery.
the phone is Bricked again flashed the ROM Sprint.
hBoot : 1.55.0000
OS: 3.05.651.5
[email protected] said:
i tried this one via a recovery.
but failed.. Even the Phone didn't boot and also cannot go back in recovery.
the phone is Bricked again flashed the ROM Sprint.
hBoot : 1.55.0000
OS: 3.05.651.5
Click to expand...
Click to collapse
1- be careful about the advice you get here, most of us are on M7_U / UL models not Sprint
2- revone only works on hboot 1.44
3- all s-off methods need a booted up rom!! not recovery!!!
4- use http://rumrunner.us/ or http://firewater-soff.com/ to get s-off on hboot 1.54+
5- if you're not sure what you're doing, do a little bit of research first (reading is preferred IMHO, over videos) until you are comfy with what you're doing.
the firewater also didnt work..
and nor Rumrunner
[email protected] said:
the firewater also didnt work..
and nor Rumrunner
Click to expand...
Click to collapse
Thanks for sharing as little information as possible.
1- do you know what s-on / s-off is? and what you can and cannot do with it? and whether you actually need it??
2- are you locked/unlocked (I'm talking about bootloader)
3- how about you start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
4- what ROM you're running
5- a copy/paste of rumrunner and/or firewater output
nkk71 said:
Thanks for sharing as little information as possible.
1- do you know what s-on / s-off is? and what you can and cannot do with it? and whether you actually need it??
2- are you locked/unlocked (I'm talking about bootloader)
3- how about you start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
4- what ROM you're running
5- a copy/paste of rumrunner and/or firewater output
Click to expand...
Click to collapse
-> yeah i know what the S-ON and S-OFF stands for.
-> yeah i need to flash a Raido.img so as to make Phone to work for SIM based for CDMA.
-> i tried flashing the radio, after rooting and unlocking, but Mr. Kapil Sir said that you have to first s-off, then u can flash radio.img
-> i am using 4.3.android. sw version : 3.05.651.5
-> firewater does nothing, where as rumrunner Pouring.... got for 8 times and asked to run after 30 seconds again for a luck to s-off.
==================== 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......
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
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
executed the above exe for 3 times but same ans...
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35XXXXxxX164
(bootloader) imei: 9XXXXXXXXXXX499
(bootloader) meid: 99XXXXXXXXXX49
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.133s
[email protected] said:
-> yeah i know what the S-ON and S-OFF stands for. okay, fair enough
-> yeah i need to flash a Raido.img so as to make Phone to work for SIM based for CDMA. interesting
-> i tried flashing the radio, after rooting and unlocking, but Mr. Kapil Sir said that you have to first s-off, then u can flash radio.img I'm not familiar with Mr. Kapil Sir, or his radio flashing techniques... then again on the M7_U/UL you can flash radios without the need to be s-off, and I would assume the same for all M7 models
-> i am using 4.3.android. sw version : 3.05.651.5 not what i asked
-> firewater does nothing, where as rumrunner Pouring.... got for 8 times and asked to run after 30 seconds again for a luck to s-off. also not what i asked
Click to expand...
Click to collapse
okay, point taken Sir.
Sorry for not getting what u asked but tried my best to answer the Q's asked.
anyways Sorry again.
so what next..?
---------- Post added at 02:56 AM ---------- Previous post was at 02:50 AM ----------
Was trying to Flash a radio...
Please Check,
hope u might get the way out...
WHile S-ON
F:\Mobiles\Android\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
F:\Mobiles\Android\fastboot>fastboot flash radio CT3G_radio.zip
target reported max download size of 1526722560 bytes
sending 'radio' (18824 KB)...
OKAY [ 2.381s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.342s
while S-OFF got with firewater worked and helped to S-OFF
F:\Mobiles\Android\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.055s]
finished. total time: 0.056s
F:\Mobiles\Android\fastboot>fastboot flash radio CT3G_radio.zip
target reported max download size of 1526722560 bytes
sending 'radio' (18824 KB)...
OKAY [ 2.381s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 2.427s
for sure it works after S-OFF .
but the minor mistake can led for failure and did a big mistake - a dump i m...
ok will correct.... hope u too have missed the correction..
but the think was
fastboot flash zip CT3G_radio.zip
where as i was writing
fastboot flash radio CT3G_radio.zip
so please dont sleep like me and do thinks..
sorry for diverting... but a good lesson for silly mistakes...
nkk71 said:
1- be careful about the advice you get here, most of us are on M7_U / UL models not Sprint
2- revone only works on hboot 1.44
3- all s-off methods need a booted up rom!! not recovery!!!
4- use http://rumrunner.us/ or http://firewater-soff.com/ to get s-off on hboot 1.54+
5- if you're not sure what you're doing, do a little bit of research first (reading is preferred IMHO, over videos) until you are comfy with what you're doing.
Click to expand...
Click to collapse
Hi
I am wondering if you can help me.
I am getting this error..revone failed (error code = -1) after runing ./revone -s 0 -u
(No 6 on http://forum.xda-developers.com/showthread.php?t=2314582)
***TAMPERED***
UNLOCKED
H-Boot 1.44
ROM 4.1.2
S-On
I am trying to get S-OFF so that I can remove the TAMPERED line.
I had success with ./revone -P and rebooted as per instructions.
However after reboot and running ./revone -s 0 -u
I get this
-------------------------------------
[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
______________________________________________
Any suggestions. Been trying to get to stock so I can return my device for the last 10 hours....so frustrating..
Thank you.
globalgpj said:
Hi
I am wondering if you can help me.
I am getting this error..revone failed (error code = -1) after runing ./revone -s 0 -u
(No 6 on http://forum.xda-developers.com/showthread.php?t=2314582)
***TAMPERED***
UNLOCKED
H-Boot 1.44
ROM 4.1.2
S-On
I am trying to get S-OFF so that I can remove the TAMPERED line.
I had success with ./revone -P and rebooted as per instructions.
However after reboot and running ./revone -s 0 -u
I get this
-------------------------------------
[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
______________________________________________
Any suggestions. Been trying to get to stock so I can return my device for the last 10 hours....so frustrating..
Thank you.
Click to expand...
Click to collapse
can you post a fastboot getvar all (excluding IMEI and s/n)
edit: and what ROM are you running
nkk71 said:
can you post a fastboot getvar all (excluding IMEI and s/n)
edit: and what ROM are you running
Click to expand...
Click to collapse
Hi Nkk71,
I got an even bigger problem now.
I was planning on returning my M7 to get the dreaded purple haze camera fixed. Got the GRA from the company already.
I tried to get the device to S-OFF after I got it S-On as the TAMPERED writing appeared again.
I tried revone and it always failed on line 6 ./revone -s 0 -u.
I went to try firewater and it said it couldn't do it and said to reboot.
As i rebooted into a stock rom, I went to Settings, got and error message and it asked if I wanted to send the error to HTC, I clicked no, then it went into a reboot and has been stuck on a WHITE boot screen (HTC One) and won't do anything.
I can't shut it down (tried holding down the power button 2 min+), I can boot into bootloader, I can't do anything either if I put my usb cable in either adb or fastboot, it is really FROZEN !!!!
Have I bricked my phone
I even tried to install the RUU but it failed as it needs to have a working USB connection.
It seems that all I can do is wait til the battery dies naturally.
Any advice ?
After 20 minutes still frozen boot screen. I can see the amber light on behind the speaker screen.
-------------------------------------------------------------------------
***TAMPERED***
UNLOCKED
S-ON
CID - HTC__001
H-Boot 1.44
ROM 4.1.2 (stock)
I'm running this stock ROM, RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed
and have TWRP installed.
globalgpj said:
Hi Nkk71,
I got an even bigger problem now.
Any advice ?
Click to expand...
Click to collapse
Firstly and most importantly: calm down, take it easy, chill out, and relax.... you are now panicking and starting to rush things!!
Once you've relaxed a bit:
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
and then let's see that "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
Firstly and most importantly: calm down, take it easy, chill out, and relax.... you are now panicking and starting to rush things!!
Once you've relaxed a bit:
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
and then let's see that "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Thanks a million !!! It worked.. I heard that before, but forgot all about it. You don't hear much about that trick these days.
Yeah , no brick
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4060mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.049s
-------------------
Should I try the Moonshine S-Off software to try and S-Off the device ?
http://forum.xda-developers.com/showthread.php?t=2291087
Hi Guys,
I am in a bit of a pickle.
I decided to Install Cyanogenmod today to see what the fuss was all about - I managed to do this successfully but then after using it for a while actually didn't like it and preferred using Sense 5.
I tried to flash stock to my HTC One (UK M7ul) via the RUU method but this failed twice.
The phone is currently will only boot into Bootloader regardless of what I try so will not even boot into Cyanogenmod at all, when ever i click recovery as CWM was installed the phone will flash for a second saying starting recover and then go straight back into bootloader.
I am currently on Bootloader 1.55 with S-On - Phone is locked and will not allow me to unlock it.
I really need some help to get my phone fully functional again on HTC Sense Stock Firemware.
CID: HTC__001
MID: PN0710000
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4304mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Davidpearl said:
Hi Guys,
I am in a bit of a pickle.
I decided to Install Cyanogenmod today to see what the fuss was all about - I managed to do this successfully but then after using it for a while actually didn't like it and preferred using Sense 5.
I tried to flash stock to my HTC One (UK M7ul) via the RUU method but this failed twice.
The phone is currently will only boot into Bootloader regardless of what I try so will not even boot into Cyanogenmod at all, when ever i click recovery as CWM was installed the phone will flash for a second saying starting recover and then go straight back into bootloader.
I am currently on Bootloader 1.55 with S-On - Phone is locked and will not allow me to unlock it.
I really need some help to get my phone fully functional again on HTC Sense Stock Firemware.
CID: HTC__001
MID: PN0710000
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVE
(bootloader) imei: REMOVE
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4304mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
good thing you posted a ''fastboot getvar all'' but never post IMEI and SN, remove them from your post.
To restore the phone back to stock with a ruu, you need to be s-off to downgrade hboot to 1.44. So you will have to unlock bootloader from htcdev, install twrp custom recovery, flash arhd 31.6, s-off with rumrunner, downgrade hboot and then run the ruu.
all details can be found in this guide.
flash twrp recovery, and then type fastboot erase cache
Then try booting into recovery, and adb push this rom.. http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Thanks for the help guys - I have issues with my computer not recognising my phone.
I have managed to unlock it again and am trying to get either one of the two methods you guys suggested to work.
The adb push command or side load is not working in TWRP.
Dunno how I am going to get this file on there?
Davidpearl said:
The adb push command or side load is not working in TWRP.
Dunno how I am going to get this file on there?
Click to expand...
Click to collapse
usb otg cable
copy the zip @SaHiLzZ linked to a usb drive then connect to phone via usb otg cable and mount it in twrp
alray said:
usb otg cable
Click to expand...
Click to collapse
Guess I am going to have to make one.
Female USB A to Micro USB right?
Davidpearl said:
Guess I am going to have to make one.
Female USB A to Micro USB right?
Click to expand...
Click to collapse
it cost like 2$ on ebay
and yed you can make one if you don't care cutting 2 usb cables
dont forget pin 4 of micro connector must be connected to gnd
GOT IT WORKING!!!!! I reinstalled CWM and that worked via side loading the image.
up and running all is right with the world!
IS there anything I need to do now as matter of good practie?
The bootloader is currently still inlocked - S-On is still activated and I still have the *tampered* logo.
Do I need to A) Lock the boot loader?
Should i turn S-Off?
How do I get rid of the tampered logo so its fully stock and I can get it repaired from HTC again?
Davidpearl said:
IS there anything I need to do now as matter of good practie?
The bootloader is currently still inlocked - S-On is still activated and I still have the *tampered* logo.
Do I need to A) Lock the boot loader?
Should i turn S-Off?
How do I get rid of the tampered logo so its fully stock and I can get it repaired from HTC again?
Click to expand...
Click to collapse
detail on how to go back 100% stock without tempered flag can be found in the guide in linked to you i my previous post
alray said:
detail on how to go back 100% stock without tempered flag can be found in the guide in linked to you i my previous post
Click to expand...
Click to collapse
I get this error when trying to S-Off my device? what do i need to do?
==================== 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 (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (36/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (37/120)
must ferment longer...
ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
Have you tried rooting it? Watch the screen, it will ask for su permissions
Seems that root is missing. Install SuperSu
Uxepro said:
Seems that root is missing. Install SuperSu
Click to expand...
Click to collapse
I rooted it today and got all the way to the last step and its saying this:
==================== 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 (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (36/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)...........
.........................................
..........
pouring (2)...........
..................................
.
pouring (3)...........
....................................
pouring (4)...........
...................................
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred 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 thi
s issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
What do I do?
Davidpearl said:
I rooted it today and got all the way to the last step and its saying this:
==================== 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 (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (36/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)...........
.........................................
..........
pouring (2)...........
..................................
.
pouring (3)...........
....................................
pouring (4)...........
...................................
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred 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 thi
s issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
What do I do?
Click to expand...
Click to collapse
Tried again and got this:
==================== 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 (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (35/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
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
SaHiLzZ said:
Have you tried rooting it? Watch the screen, it will ask for su permissions
Click to expand...
Click to collapse
Uxepro said:
Seems that root is missing. Install SuperSu
Click to expand...
Click to collapse
Hey guys, any idea?
Do I need to install a Custom Rom to unlock S-Off and then re-flash Stock firmware?
Davidpearl said:
Hey guys, any idea?
Do I need to install a Custom Rom to unlock S-Off and then re-flash Stock firmware?
Click to expand...
Click to collapse
did you flash an unsecured kernel?
"(bootloader) version-main: 3.62.401.1" or just install ARHD 31.6 http://forum.xda-developers.com/showthread.php?t=2183023 which has all the prerequisites.
if you're having problems with Windows, try Ubuntu Live USB: http://forum.xda-developers.com/showthread.php?t=2606577
nkk71 said:
did you flash an unsecured kernel?
"(bootloader) version-main: 3.62.401.1" or just install ARHD 31.6 http://forum.xda-developers.com/showthread.php?t=2183023 which has all the prerequisites.
if you're having problems with Windows, try Ubuntu Live USB: http://forum.xda-developers.com/showthread.php?t=2606577
Click to expand...
Click to collapse
I am using the Guru_Reset_3.62.401.1 from the link - I assume that this Stock rom is secured?
I could flash ARHD 51.0 and I may even stay on that if the perform is much superior..... at least If I S-Off on that I can fully stock if there are any issues.
ARHD 51 is basically Kitkat with Sense on it right?
Thanks for all your help it is greatly appreciated.
Davidpearl said:
I am using the Guru_Reset_3.62.401.1 from the link - I assume that this Stock rom is secured?
I could flash ARHD 51.0 and I may even stay on that if the perform is much superior..... at least If I S-Off on that I can fully stock if there are any issues.
ARHD 51 is basically Kitkat with Sense on it right?
Thanks for all your help it is greatly appreciated.
Click to expand...
Click to collapse
Use ARHD 31.6 (because it's inline with your firmware 3.62.401.1), then use rumrunner to get S-Off
I have T mobile HTC ONE.
I tried to go back to stock T Mobile version. But getting RUU.exe error 155.
Tried RUU :
RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed
RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
My HTC ONE is RELOCKED bootloader.
C:\Users\_Dj_\Desktop\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
Tried to Downgrade hboot to original 1.44 but failed .
C:\Users\_Dj_\Desktop\OneDrivers_Fastboot\Fastboot>fastboot flash zip orig_hboot
_1.44.0000_M7_RUUmode.zip
target reported max download size of 1514139648 bytes
sending 'zip' (486 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.281s
Click to expand...
Click to collapse
If I tried to flash any img, zip it always shows FAILED (remote: signature verify fail) By This I can't S OFF my HTC one. :crying:
I can't install recovery due to signature verify fail. So...
Any Idea ? How Can I fix it ?
Divyashwar said:
I have T mobile HTC ONE.
I tried to go back to stock T Mobile version. But getting RUU.exe error 155.
Tried RUU :
RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed
RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
My HTC ONE is RELOCKED bootloader.
Tried to Downgrade hboot to original 1.44 but failed .
If I tried to flash any img, zip it always shows FAILED (remote: signature verify fail) By This I can't S OFF my HTC one. :crying:
I can't install recovery due to signature verify fail. So...
Any Idea ? How Can I fix it ?
Click to expand...
Click to collapse
You need to have unlocked the bootloader to change recovery and S-off to change hboota ( downgrade)
Mutasek24 said:
You need to have unlocked the bootloader to change recovery and S-off to change hboota ( downgrade)
Click to expand...
Click to collapse
Yeah ! I just did this bro ! .
fastboot flash unlocktoken Unlock_code.bin
Now, Bootloader is unlocked and have recovery TWRP.
Going for S-OFF now.
soon update more...
Thank you
Cannot able to get S-OFF .
I'm On 4.4.2 hboot 1.56
I used rumrunner !
but its not working ....
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
so, any idea ? how to get S-Off ?
Thank you
Divyashwar said:
Cannot able to get S-OFF .
I'm On 4.4.2 hboot 1.56
I used rumrunner !
but its not working ....
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
so, any idea ? how to get S-Off ?
Click to expand...
Click to collapse
1- go back edit your post and remove IMEI, you shouldnt be sharing that
2- (bootloader) version-main: 4.19.531.10 -> what ROM are you running? recommend a rooted ROM with unsecured kernel such as ARHD 52.0
3- try http://firewater-soff.com/
nkk71 said:
1- go back edit your post and remove IMEI, you shouldnt be sharing that
2- (bootloader) version-main: 4.19.531.10 -> what ROM are you running? recommend a rooted ROM with unsecured kernel such as ARHD 52.0
3- try http://firewater-soff.com/
Click to expand...
Click to collapse
Yes ! I'm on Android_Revolution_HD-One_52.0
It not working....
I think ARHD 52 using Stock kernal
Divyashwar said:
Yes ! I'm on Android_Revolution_HD-One_52.0
It not working....
I think ARHD 52 using Stock kernal
Click to expand...
Click to collapse
ARHD has stock kernel but unsecured so that's OK.
but, firewater not working either?
nkk71 said:
ARHD has stock kernel but unsecured so that's OK.
but, firewater not working either?
Click to expand...
Click to collapse
Thank you !
Firewater works
C:\Users\_Dj_\Desktop\OneDrivers_Fastboot\Fastboot>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\_Dj_\Desktop\OneDrivers_Fastboot\Fastboot>adb push firewater /data/loca
l/tmp
3795 KB/s (4347896 bytes in 1.118s)
C:\Users\_Dj_\Desktop\OneDrivers_Fastboot\Fastboot>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 0.4.0 ==============================
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
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..........
that firewater was good and hot, throwing out the empties
=========================================================================
==== device is now s-off. Don't forget to send us all your money =====
=========================================================================
=============== paypal: [email protected] =======================
=========================================================================
[email protected]:/ # Yes
sh: Yes: not found
127|[email protected]:/ #
Click to expand...
Click to collapse
Divyashwar said:
Thank you !
Firewater works
Click to expand...
Click to collapse
:good::good:
Now remember: once S-Off stay S-Off (unless you need to send it to warranty or sell it, in which case going from S-Off to S-On needs to be done at an exact point in time!!!)
also with S-Off, there is no need to lock/relock bootloader to flash stuff!!!
nkk71 said:
:good::good:
Now remember: once S-Off stay S-Off (unless you need to send it to warranty or sell it, in which case going from S-Off to S-On needs to be done at an exact point in time!!!)
also with S-Off, there is no need to lock/relock bootloader to flash stuff!!!
Click to expand...
Click to collapse
Thanks for info !
Last question !
If I want to go back to stock !
Then I need to just run RUU.exe ? or need some more steps ?
Divyashwar said:
Thanks for info !
Last question !
If I want to go back to stock !
Then I need to just run RUU.exe ? or need some more steps ?
Click to expand...
Click to collapse
If you're going for a downgrade RUU.EXE then you need to downgrade hboot separately first, if you are on hboot 1.55+
May I recommend you take a look at my guide on how to return to stock: http://forum.xda-developers.com/showthread.php?t=2541082
(in particular the FAQs, especially if you are on Win8.1)
If you're keeping the phone, you can skip the LOCKED part and the S-On part (those are for people returning for warranty, or selling the phone).
Let me know if you have questions
Cheers
Hi all, I have a problem after send my ONE to claim violet/red camera
Now I want to root ONE again (I already root before) but in this time I wipe wrong partition that cause me have "no os install"
My hboot = 1.56 / S-ON / TWRP = 2.6.3.3
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA355W908122
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__044
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I try to read many many forums to make my ONE is back to normal, I have some question to ask what I need to do ?
I need to change S-ON to S-OFF (But now I cannot and I have tried for moonshell, rumrunner and firewater)
- all of method above need some ROM right?
If need some ROM can I install ROM in TWRP with "adb sideload" or "adb push" right?
Or I can help my ONE with another method that easily way that I want to do?
Please sugguestion I need all comment and Thank you very much sir.
RobbieKeane said:
Hi all, I have a problem after send my ONE to claim violet/red camera
Now I want to root ONE again (I already root before) but in this time I wipe wrong partition that cause me have "no os install"
My hboot = 1.56 / S-ON / TWRP = 2.6.3.3
I try to read many many forums to make my ONE is back to normal, I have some question to ask what I need to do ?
I need to change S-ON to S-OFF (But now I cannot and I have tried for moonshell, rumrunner and firewater)
- all of method above need some ROM right?
If need some ROM can I install ROM in TWRP with "adb sideload" or "adb push" right?
Or I can help my ONE with another method that easily way that I want to do?
Please sugguestion I need all comment and Thank you very much sir.
Click to expand...
Click to collapse
instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
clsA said:
instructions
Click to expand...
Click to collapse
Thank you very much I will try and update sir.
My hope come again
[email protected] InsertCoin ADDICT [email protected]~
We can do anything (If we want :3)
I have no luck
Unlock Bootloader ---> OK
Install recovery TWRP 2.6.3.3 ---> OK
adb sideload ---> Failed (I use adb push instead)
Install ROM in TWRP ---> Failed
When install ROM swipe to install after that they show message "Failed to install"
Can I install with RUU.exe?
RobbieKeane said:
I have no luck
Unlock Bootloader ---> OK
Install recovery TWRP 2.6.3.3 ---> OK
adb sideload ---> Failed (I use adb push instead)
Install ROM in TWRP ---> Failed
When install ROM swipe to install after that they show message "Failed to install"
Can I install with RUU.exe?
Click to expand...
Click to collapse
The RUU is very old you need s-off
http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
Try and flash the rom again
this time in TWRP / wipe / advanced wipe / format data
reboot recovery and try and flash the Rom again.
are you sure the rom is complete ? ARHD 31.6 - 1,161,504 KB
MD5: B4EDA0171BF3BFED779C2107EF6C6F76
clsA said:
The RUU is very old you need s-off
http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
Try and flash the rom again
this time in TWRP / wipe / advanced wipe / format data
reboot recovery and try and flash the Rom again.
are you sure the rom is complete ? ARHD 31.6 - 1,161,504 KB
MD5: B4EDA0171BF3BFED779C2107EF6C6F76
Click to expand...
Click to collapse
Thank you for your suggest but now I cannot install any rom or zip file in TWRP it's say "Failed to install".
I don't know how to fixed it and how to diagnose or debug what happen T__T.
I have htc one m7 international, Rooted S-off , sense 6. Stock Rom
I don't know what happened!!! My touchscreen isn't working in the centre of the screen! Is it hardware problem !? Or any other solution!?
Well it depends. Did you do anything or did it just stop working?
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
Well it depends. Did you do anything or did it just stop working?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well honesty i dont remember! I had modaco toolkit and many more Modules! N also that sound module...but i dont think sound plugin would affect touch!! N yeah recently my cell was booting up n like after 2 mins it was rebooting...so i just restored my backup which was taken after rooting :/
akshayy29 said:
Well honesty i dont remember! I had modaco toolkit and many more Modules! N also that sound module...but i dont think sound plugin would affect touch!! N yeah recently my cell was booting up n like after 2 mins it was rebooting...so i just restored my backup which was taken after rooting :/
Click to expand...
Click to collapse
you probably restored a 1.xx ROM/nandroid and your firmware is 2.xx+; in the 2.xx+ firmware the touchscreen drivers were updated and don't work with a 1.xx ROM
use a 2.xx+ ROM then the touchscreen will work again.
EDIT: sorry, just reread the OP, only in the centre of the screen?
yeahh only in the centre of the screen...means horizontally!!! So should I reflash the stock Rom !?
akshayy29 said:
yeahh only in the centre of the screen...means horizontally!!! So should I reflash the stock Rom !?
Click to expand...
Click to collapse
yes, why not try? (different ROMs, etc.)?
also try (in dialer) *#*#3424#*#* and run the Line Drawing Test
PS: please do not send me any PMs with a timer
nkk71 said:
yes, why not try? (different ROMs, etc.)?
also try (in dialer) *#*#3424#*#* and run the Line Drawing Test
PS: please do not send me any PMs with a timer
Click to expand...
Click to collapse
I did line drawing test ... See the screenshot below!! There are gap between some lines!! That happens!! (´･_･`) so is it hardware problem or should I try Roms!?
akshayy29 said:
I did line drawing test ... See the screenshot below!! There are gap between some lines!! That happens!! (´･_･`) so is it hardware problem or should I try Roms!?
Click to expand...
Click to collapse
Could very well be a hardware problem. I don't see any reason why wouldn't want to try an ruu (or at least a different ROM), and see if that works better... it's all up to you.
nkk71 said:
Could very well be a hardware problem. I don't see any reason why wouldn't want to try an ruu (or at least a different ROM), and see if that works better... it's all up to you.
Click to expand...
Click to collapse
If by chance its hardware problrm...My device is still in warranty but as I have unlocked boot loader n rooted n status is tempered my warranty must be destroyed! But I'm still S-on and on stock rom. Is there any chance I can get my phone back to unroot relocked boot loader n tempered status off!? Do service centres check the tampered [email protected]??? I browsed a little n found that only unroot...by unroot I mean reflashing the Rom might be enough! N yeahh I'll try Ruu + different rom! ? Thanks!
akshayy29 said:
If by chance its hardware problrm...My device is still in warranty but as I have unlocked boot loader n rooted n status is tempered my warranty must be destroyed! But I'm still S-on and on stock rom. Is there any chance I can get my phone back to unroot relocked boot loader n tempered status off!?
Click to expand...
Click to collapse
Yes follow nkk71's guide linked in his/my signature
Do service centres check the tampered [email protected]???
Click to expand...
Click to collapse
yes they do check the flag, phone must be 100% stock including bootloader locked (not relocked) and no tampered flag.
alray said:
Yes follow nkk71's guide linked in his/my signature
yes they do check the flag, phone must be 100% stock including bootloader locked (not relocked) and no tampered flag.
Click to expand...
Click to collapse
yeah i was trying to S-off since im on HBoot 1.57 I tried firewater as many suggested. but i got these error
D:\HTC>adb devices
List of devices attached
MB352W909733 device
D:\HTC>adb reboot
D:\HTC>ad wait-for-device push firewater /data/local/tmp
'ad' is not recognized as an internal or external command,
operable program or batch file.
D:\HTC>adb wait-for-device push firewater /data/local/tmp
4198 KB/s (4522136 bytes in 1.051s)
D:\HTC>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.6.3 ===========================
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
Type 'Yes' or 'No'
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, h
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, h
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, h
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. **********
Click to expand...
Click to collapse
My Htc one details :
bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.707.104
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: ************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4223mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Please help :'(
I'm trying to go back to stock but i failed every time
I tested this solutions:
Android Revolution HD 31.6 with Custom Recovery 2.6.3.3 with firewater S-OFF and with rumrunner
with rumrunner i got this error:
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 (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (17/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
with firewater i got this output:
Code:
==================== firewater S-OFF 8.0.6.26 ===========================
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. **********
[email protected]:/ #
my output from "fastboot getvar all"
Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3951mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
maybe anyone can help?
Exactly i'm the same problem and with stock rom ruu IMEI and baseband is unknown and auto-reboot and with custom rom auto-reboot is removed but imei and baseband are unknown
in One X i flash boot boot.img and imei is back , but in One is'nt
please help , thank you
sorry for my bad english
Unfortunately you are stuck then. Just like me with my warranty replacement phone. I can't s off. There is an app called sunshine that is used to s off the m8. They say there may be support for the m7 in the future. That's really our only hope
Sent from my HTC One using XDA Premium 4 mobile app
Evolutios said:
I'm trying to go back to stock but i failed every time
I tested this solutions:
Android Revolution HD 31.6 with Custom Recovery 2.6.3.3 with firewater S-OFF and with rumrunner
with rumrunner i got this error:
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 (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (17/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
with firewater i got this output:
Code:
==================== firewater S-OFF 8.0.6.26 ===========================
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. **********
[email protected]:/ #
my output from "fastboot getvar all"
Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3951mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
maybe anyone can help?[/QUOTE
Will not work. You must wait to appear another exploit
Click to expand...
Click to collapse
but there are people who can s-off the hboot 1.56
but not everyone , only a few people
Evolutios said:
I'm trying to go back to stock but i failed every time
I tested this solutions:
Android Revolution HD 31.6 with Custom Recovery 2.6.3.3 with firewater S-OFF and with rumrunner
Click to expand...
Click to collapse
Crown Clown said:
Exactly i'm the same problem
Click to expand...
Click to collapse
did you try rumrunner in Ubuntu 32bit ? sometimes the PC is the problem
clsA said:
did you try rumrunner in Ubuntu 32bit ? sometimes the PC is the problem
Click to expand...
Click to collapse
i haven't
Crown Clown said:
i haven't
Click to expand...
Click to collapse
If you get the "whelp this sucks....." message then you can't s-off no matter what you do (as the measure says). I'm in the same boat with you and I wait a new exploit like SunShine to be available for M7.
I had the same problem on HBOOT 1.56
Was rooted and bootloader unlocked.
RumRunner & Revone did not work.
Firewater did not work at first either.
What I did was changed the CID to GOOGL001 then I ran Firewater again and it finally worked. Flashed the GE RUU and everything is good.
Phone went from AT&T to GE Rom and got all the updates.
hardstyle123 said:
I had the same problem on HBOOT 1.56
Was rooted and bootloader unlocked.
RumRunner & Revone did not work.
Firewater did not work at first either.
What I did was changed the CID to GOOGL001 then I ran Firewater again and it finally worked. Flashed the GE RUU and everything is good.
Phone went from AT&T to GE Rom and got all the updates.
Click to expand...
Click to collapse
How did you changed CID being S-ON? If you changed CID you were already S-OFF.
cyrusct82 said:
How did you changed CID being S-ON? If you changed CID you were already S-OFF.
Click to expand...
Click to collapse
this is my question too , how did ?!??!?!?!?!?
Crown Clown said:
this is my question too , how did ?!??!?!?!?!?
Click to expand...
Click to collapse
This may help some people, it is possible to change CID without s-off, however very risky and very dangerous, this is how we used to do it on my previous HTC One SV in order to even get s-off, not sure though if this is the same address between both phones mmcblk0p4, so you do this at your own risk, and if you brick, don't come to me.
you have to know that you are pulling your bootloader from your device, yes that's your BOOTLOADER, modifying it and then flashing it back.
http://forum.xda-developers.com/showthread.php?t=2264322
Have pretty much similar problem, running Viper One
tried Firewater, followed the step like
adb reboot
then
adb wait-for-device push firewater /data/local/tmp
then
adb shell
then
su
then
chmod 755 /data/local/tmp/firewater
then
/data/local/tmp/firewater
then
yes
Click to expand...
Click to collapse
But it doesn't S-OFF my device
instead, in the command prompt, an infinite loop of "y" appeared, and nothing happen.
Then, tried to redo the procedure, stucked in the booting logo after adb reboot command, but somehow is able to boot via the bootloader
Any tips?
alwinwh said:
Have pretty much similar problem, running Viper One
tried Firewater, followed the step like
But it doesn't S-OFF my device
instead, in the command prompt, an infinite loop of "y" appeared, and nothing happen.
Then, tried to redo the procedure, stucked in the booting logo after adb reboot command, but somehow is able to boot via the bootloader
Any tips?
Click to expand...
Click to collapse
try typing Yes instead of yes, iirc it is case sensitive
nkk71 said:
try typing Yes instead of yes, iirc it is case sensitive
Click to expand...
Click to collapse
yea, finished that alr, thx anyway
now trying to return stock, stucked at flashing ruu, the cmd said
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\19>adb reboot-bootloader
C:\Users\19>fastboot oem writecid HTC__044
...
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.069s]
finished. total time: 0.069s
C:\Users\19>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.043s
C:\Users\19>adb reboot-bootloader
C:\Users\19>adb reboot-bootloader
C:\Users\19>adb reboot-bootloader
C:\Users\19>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Users\19>fastboot flash zip ruu.zip
error: cannot open 'ruu.zip'
C:\Users\19>fastboot flash zip ruu.zip
error: cannot open 'ruu.zip'
C:\Users\19>cd c:\android-sdk-windows
c:\android-sdk-windows>fastboot flash zip ruu.zip
error: cannot open 'ruu.zip'
c:\android-sdk-windows>fastboot flash zip ruu.zip,zip
error: cannot open 'ruu.zip,zip'
c:\android-sdk-windows>fastboot flash zip
unknown partition 'zip'
error: cannot determine image filename for 'zip'
c:\android-sdk-windows>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
got my ruu from http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
sorry it its kind of out of topic
turning my handset to the service center on monday, speaker issue
alwinwh said:
yea, finished that alr, thx anyway
now trying to return stock, stucked at flashing ruu, the cmd said
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\19>adb reboot-bootloader
C:\Users\19>fastboot oem writecid HTC__044
...
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.069s]
finished. total time: 0.069s
C:\Users\19>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.043s
C:\Users\19>adb reboot-bootloader
C:\Users\19>adb reboot-bootloader
C:\Users\19>adb reboot-bootloader
C:\Users\19>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Users\19>fastboot flash zip ruu.zip
error: cannot open 'ruu.zip'
C:\Users\19>fastboot flash zip ruu.zip
error: cannot open 'ruu.zip'
C:\Users\19>cd c:\android-sdk-windows
c:\android-sdk-windows>fastboot flash zip ruu.zip
error: cannot open 'ruu.zip'
c:\android-sdk-windows>fastboot flash zip ruu.zip,zip
error: cannot open 'ruu.zip,zip'
c:\android-sdk-windows>fastboot flash zip
unknown partition 'zip'
error: cannot determine image filename for 'zip'
c:\android-sdk-windows>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
got my ruu from http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
sorry it its kind of out of topic
turning my handset to the service center on monday, speaker issue
Click to expand...
Click to collapse
"error: cannot open 'ruu.zip'" = MyFileNameIsWrong
use DIR command in command prompt to check filenames (and extension), and make sure MD5 on your downloads is correct
nkk71 said:
"error: cannot open 'ruu.zip'" = MyFileNameIsWrong
use DIR command in command prompt to check filenames (and extension), and make sure MD5 on your downloads is correct
Click to expand...
Click to collapse
what is DIR command?
And checked the MD5 matched, now tryng to figure it out
btw my cpu only have USB 3.0 port, is it fine?
alwinwh said:
what is DIR command?
And checked the MD5 matched, now tryng to figure it out
btw my cpu only have USB 3.0 port, is it fine?
Click to expand...
Click to collapse
USB2 is very preferred, Windows 8.1 is a deal-breaker
check my guide's FAQ section: http://forum.xda-developers.com/showthread.php?t=2541082
DIR lists the directory contents in windows command prompt, similar to "ls" in unix
nkk71 said:
USB2 is very preferred, Windows 8.1 is a deal-breaker
check my guide's FAQ section: http://forum.xda-developers.com/showthread.php?t=2541082
DIR lists the directory contents in windows command prompt, similar to "ls" in unix
Click to expand...
Click to collapse
well just completed mine, with USB 3.0
Thanks for the answer anyway
Is now stock with S-OFF
Running Win 7