Database Develop

No service, No IMEI, Keep rebooting every time...

Hello to all ! I have a problem and I hope somebody could help me....; When I press Power its boot normally until the main screen with lock , the wrote NO SERVICE when I am trying to unlock it the screen become blank with green HTC on middle after a minute phone reboot itself and that is over and over again.... its like he couldn't load the system....anyway when I press the power button it says as usual in Android Power off,restart or Air plane mode and if you press air plane mode and reboot you can unlock it normally , but still no service no imei and radio-module version and keep rebooting ... All those steps where with S-on and locked bootloader... After that I disable Security (Thanks a lot to Hasoon 200) and unlock boot loader... i put about 5 customs all have the same issue except GE version it still not give imei and radio module but there is no trouble with reboot ... Can anyone help me or guide me in what direction to dig? Thanks a lot
P.S Sorry for my bad English...
P.P.S Htc ONE M7 UL PN07100 A07
Hboot 1.44
Radio 4a.13.3231.27

Horatio. said:
Hello to all ! I have a problem and I hope somebody could help me....; When I press Power its boot normally until the main screen with lock , the wrote NO SERVICE when I am trying to unlock it the screen become blank with green HTC on middle after a minute phone reboot itself and that is over and over again.... its like he couldn't load the system....anyway when I press the power button it says as usual in Android Power off,restart or Air plane mode and if you press air plane mode and reboot you can unlock it normally , but still no service no imei and radio-module version and keep rebooting ... All those steps where with S-on and locked bootloader... After that I disable Security (Thanks a lot to Hasoon 200) and unlock boot loader... i put about 5 customs all have the same issue except GE version it still not give imei and radio module but there is no trouble with reboot ... Can anyone help me or guide me in what direction to dig? Thanks a lot
P.S Sorry for my bad English...
P.P.S Htc ONE M7 UL PN07100 A07
Hboot 1.44
Radio 4a.13.3231.27
Click to expand...
Click to collapse
get S-OFF and try updating your firmware

kamilmirza said:
get S-OFF and try updating your firmware
Click to expand...
Click to collapse
I tried it gave a bootloader error and now I have TEMPERED IN bootloader menu and cannot turn s-on off(((((

Horatio. said:
I tried it gave a bootloader error and now I have TEMPERED IN bootloader menu and cannot turn s-on off(((((
Click to expand...
Click to collapse
lol dont worry about the TEMPERED
follow this guide: http://forum.xda-developers.com/showthread.php?t=2365506

TEMPERED is normal

kamilmirza said:
lol dont worry about the TEMPERED
follow this guide: http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
Cannot S-OFF it says Revone Failed Code Error =1 or segmentation fault (core dumped) ....

Horatio. said:
Cannot S-OFF it says Revone Failed Code Error =1 or segmentation fault (core dumped) ....
Click to expand...
Click to collapse
try rumrunners
follow this guide: http://forum.xda-developers.com/showthread.php?t=2488772

kamilmirza said:
try rumrunners
follow this guide: http://forum.xda-developers.com/showthread.php?t=2488772
Click to expand...
Click to collapse
Strange things most of custom roms it allow to install but official RUU denies .....

Horatio. said:
Strange things most of custom roms it allow to install but official RUU denies .....
Click to expand...
Click to collapse
get your main ver ROM from here: http://forum.xda-developers.com/showthread.php?t=2428276
flash it and then try rumrunners S-OFF using the guide i gave you before by electronical

kamilmirza said:
get your main ver ROM from here: http://forum.xda-developers.com/showthread.php?t=2428276
flash it and then try rumrunners S-OFF using the guide i gave you before by electronical
Click to expand...
Click to collapse
Tried with Guru Reset with Aroma installer same thing only when I type ./ revone -P it says segmentation fault (core dumped) ....As about Rum runner ....
==================== 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
Type 'Yes' or 'No'
(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 (31/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (31/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.......
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

Horatio. said:
Tried with Guru Reset with Aroma installer same thing only when I type ./ revone -P it says segmentation fault (core dumped) ....As about Rum runner ....
==================== 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
Type 'Yes' or 'No'
(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 (31/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (31/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.......
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
Click to expand...
Click to collapse
which ROM you flashed?
go into bootloader and tell me the OS
the error says that the ROM you flashed is not compatible
Sent from my HTC One using Tapatalk

kamilmirza said:
which ROM you flashed?
go into bootloader and tell me the OS
the error says that the ROM you flashed is not compatible
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks a lot .... You see My phone Is rebooting every 30 second or minute thats why rumrunner cannot run properly, But I found method Thats work )))0 I am S-off again and putting RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and the main problem is again no service no imei reboot.....

Horatio. said:
Thanks a lot .... You see My phone Is rebooting every 30 second or minute thats why rumrunner cannot run properly, But I found method Thats work )))0 I am S-off again and putting RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and the main problem is again no service no imei reboot.....
Click to expand...
Click to collapse
have you tried any other SIM?
why don't you try any custom ROM?
have you flashed the latest firmware?
Sent from my HTC One using Tapatalk

kamilmirza said:
have you tried any other SIM?
why don't you try any custom ROM?
have you flashed the latest firmware?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Its not in the sim because he must work without sim ok to navigate in internet or use as camera but it keep rebooting ..... about custom firmware I tried Venom-Revolutin_Googke-Dark Jelly-Maximus-Coins.....
Last ota you mean

Horatio. said:
Its not in the sim because he must work without sim ok to navigate in internet or use as camera but it keep rebooting ..... about custom firmware I tried Venom-Revolutin_Googke-Dark Jelly-Maximus-Coins.....
Last ota you mean
Click to expand...
Click to collapse
flash the latest FIRMWARE (for 4.4) from this thread: http://forum.xda-developers.com/showthread.php?t=2365506
then try custom ROMs
Sent from my HTC One using Tapatalk

kamilmirza said:
flash the latest FIRMWARE (for 4.4) from this thread: http://forum.xda-developers.com/showthread.php?t=2365506
then try custom ROMs
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Just tried says FAILED Remote not allowed... Still trying
Got It ... Flashing REvolution Firmware....

Horatio. said:
Just tried says FAILED Remote not allowed... Still trying
Got It ... Flashing REvolution Firmware....
Click to expand...
Click to collapse
dude its a safety precaution you just have to enter the same command again and you'll get it
kindly read the whole procedure first then do it
Sent from my HTC One using Tapatalk

kamilmirza said:
dude its a safety precaution you just have to enter the same command again and you'll get it
kindly read the whole procedure first then do it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Put the latest firmware.... Flashed Revolution HD One ..... Hangs on HTC screen will try other custom rom
After 3 or four restart Revolution starts ....Same thing no imei rebooting ..... 30% downloading Viper one 4.2

Horatio. said:
Put the latest firmware.... Flashed Revolution HD One ..... Hangs on HTC screen will try other custom rom
After 3 or four restart Revolution starts ....Same thing no imei rebooting ..... 30% downloading Viper one 4.2
Click to expand...
Click to collapse
go into fastboot USB
and type "fastboot getvar all"
and paste it all here, remove serial and imei before pasting
Sent from my HTC One using Tapatalk

kamilmirza said:
go into fastboot USB
and type "fastboot getvar all"
and paste it all here, remove serial and imei before pasting
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__A07
(bootloader) battery-status: good
(bootloader) battery-voltage: 4208mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
On Viper one same thing (((

[Solved] Soft Brick HTC One (M7ul) Recovery won't boot

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

Q: find it impossible to find the info I need.

First of all, I've never updated my firmware. I've unlocked my bootloader through the HTC provided steps, I'm on hboot 1.44.
Now for the problems:
I've searched high and low, I cannot find a RUU, ROM or recovery for a Dutch T-Mobile HTC One.
Revone never works, it just gets stuck every single time on (gaining root access).
All I want is to get either S-OFF or simply return to complete stock (not worried about tamperflag).
Anyone who can help out?

seshmaru said:
First of all, I've never updated my firmware. I've unlocked my bootloader through the HTC provided steps, I'm on hboot 1.44.
Now for the problems:
I've searched high and low, I cannot find a RUU, ROM or recovery for a Dutch T-Mobile HTC One.
Revone never works, it just gets stuck every single time on (gaining root access).
All I want is to get either S-OFF or simply return to complete stock (not worried about tamperflag).
Anyone who can help out?
Click to expand...
Click to collapse
I s-off my new phone (hboot 1.44) last night with rumrunner here's the steps I took. Unlocked Bootloader - flash TWRP - Flashed ARHD 31.6 - booted up the phone and went through a quick install with no accounts setup. ran rumrunner and about 10 min later it was all done. Note .. turn off Sleep on the phone or set it to 10 min. don't leave the phone unattended on the second pour superSU ask for permission two times .. choose yes
==================== 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 (10/120)
Waiting
Test 2: Booting device
Waiting for ADB (29/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (10/120)
Waiting for ADB (29/120)
must ferment longer...
chilling..................
smells lovely in here....
heh, just a shot glass for this one....
bottles are packed, here we go, shhhhhh....
pouring (1)..................................
pouring (2).................................
pouring (3)...........
Waiting for ADB (32/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
Click to expand...
Click to collapse
C:\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT34************ device
C:\fastboot>adb shell
[email protected]:/ # echo -ne '\x00' | dd of=/dev/block/mmcb
ock/mmcblk0p7 bs=1 seek=4265988
1+0 records in
1+0 records out
1 bytes transferred in 0.009 secs (111 bytes/sec)
[email protected]:/ # exit
exit
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT3***********
(bootloader) imei: 354**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4203mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.065s
Click to expand...
Click to collapse
here's the files I used
TWRP 2.6.3.3 - http://techerrata.com/browse/twrp2/m7
ARHD - http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
RumRunner - http://rumrunner.us/

seshmaru said:
First of all, I've never updated my firmware. I've unlocked my bootloader through the HTC provided steps, I'm on hboot 1.44.
Now for the problems:
I've searched high and low, I cannot find a RUU, ROM or recovery for a Dutch T-Mobile HTC One.
Revone never works, it just gets stuck every single time on (gaining root access).
All I want is to get either S-OFF or simply return to complete stock (not worried about tamperflag).
Anyone who can help out?
Click to expand...
Click to collapse
what are you trying to do?
you don't need s-off - if you have unlocked bootloader just flash custom recovery (I recommend TWRP) then flash custom rom.
guide to do those things are found here: http://forum.xda-developers.com/showthread.php?t=2438026

cr1960 said:
what are you trying to do?
you don't need s-off - if you have unlocked bootloader just flash custom recovery (I recommend TWRP) then flash custom rom.
guide to do those things are found here: http://forum.xda-developers.com/showthread.php?t=2438026
Click to expand...
Click to collapse
Pretty sure I need to have S-OFF to update firmwares and switch to GPe no? I do have TWRP flashed.
And thanks clsA I'll try that.

seshmaru said:
Pretty sure I need to have S-OFF to update firmwares and switch to GPe no? I do have TWRP flashed.
And thanks clsA I'll try that.
Click to expand...
Click to collapse
see, you didn't mention anything about GPE in the OP.....

cr1960 said:
see, you didn't mention anything about GPE in the OP.....
Click to expand...
Click to collapse
What my desired outcome is shouldn't be important, I stated that I need S-OFF.
On a side note, is it possible to flash SixthSense 2.1 without S-OFF? The thread itself isn't very clear.
EDIT: Tried it and it does let you.
Anyhow, time to try rumrunner.

[Q] touchScreen ain't working

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 :'(

[Q] S-OFF failed with firewater and rumrunner with hboot 1.56

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