Database Develop

[Q] no bootloader version? help needed!

D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH397
(bootloader) imei: 35585
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4016mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>
Is there something wrong with my phone? anything missing i cant seem to find my (bootloader) version-main: in order to flash back stock rom. im s-on
and which RUU can i download?
http://www.androidruu.com/index.php?developer=M7

Judging by your CID your phone belongs to the WWE region. For the moment you can't flash any RUU.
If you still want to run an RUU do the following:
1.HTC-dev boot loader unlock
2.s-off
3.Downgrade hboot to 1.44.
4.Download 1.28.401.7 RUU and run it while on fastboot.
You can also lock the bootloader after you gain s-off
Sent from my HTC One using Tapatalk

Ivanovic said:
Judging by your CID your phone belongs to the WWE region. For the moment you can't flash any RUU.
If you still want to run an RUU do the following:
1.HTC-dev boot loader unlock
2.s-off
3.Downgrade hboot to 1.44.
4.Download 1.28.401.7 RUU and run it while on fastboot.
You can also lock the bootloader after you gain s-off
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. I cant seem to s-off using rumrunner for some reason, im pretty sure my fastboot works. I am able to flash custom recovery. However, it appears not to work error:adb. check usb debug. My usb debudding is on though.

Windows 7 or 8? Maybe you should try and install some other drivers!
P.S are you on custom Rom?
Sent from my HTC One using Tapatalk

Ivanovic said:
Windows 7 or 8? Maybe you should try and install some other drivers!
P.S are you on custom Rom?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
windows 8! I am able to flash custom recovery so my connection should be fine right?

I guess so. Btw I was wrong before. Just saw that your MID is not European and most probably is for the Australian variant. In that case 1.29.980.2 is for you
Sent from my HTC One using Tapatalk

Ivanovic said:
I guess so. Btw I was wrong before. Just saw that your MID is not European and most probably is for the Australian variant. In that case 1.29.980.2 is for you
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm not sure which variant. Its a singapore bought phone

Here is the correct RUU http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
Now for the adb thing. Try to reinstall drivers from the android development subforum just in case and try again. Are you using the command on fastboot or while the phone is in normal mode?
If this is not working then I guess it's better to flash a close to stock Rom like ARHD
Sent from my HTC One using Tapatalk

Ivanovic said:
Here is the correct RUU http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
Now for the adb thing. Try to reinstall drivers from the android development subforum just in case and try again. Are you using the command on fastboot or while the phone is in normal mode?
If this is not working then I guess it's better to flash a close to stock Rom like ARHD
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i tried it in fastboot! alright i'll try downloading the ruu and see how it goes! thank you so much. Any idea why theres no main firmware version showing up?
From what i heard its not possible to flash a ruu while my phone is s-on is that true? If only i can get it to s-off arhhh.

Which Rom are you using ?
Sent from my HTC One using Tapatalk

Ivanovic said:
Which Rom are you using ?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
currently running sinless gpe 4.3.1. thought of going back to stock to update to latest firmware and all via ota first since i cant seem to be able to s-off.

For the s-off procedure it's better to flash a close to stock Rom like ARHD 31.0.
I believe that after that you will be able to s-off just fine!
Sent from my HTC One using Tapatalk

i've tried it twice last night :/ flashed arhd 31.6. Couldnt get rumrunner to work. turned off all security stuff,

http://www.htc1guru.com/downloads/stock-rom-downloads/
any idea which one i might be able to try flash? thank you
==================== 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....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit

Try this http://d-h.st/23V and let me know.
Sent from my HTC One using Tapatalk

Ivanovic said:
Try this http://d-h.st/23V and let me know.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I am running a windows 8 OS. Do i still try that?
Edit* tried it same results. I am able to get SH****** when i key in fastboot devices

Have the device in normal mode, open a command window and run "adb shell"
What do you get?
Sent from my HTC One using Tapatalk

Ivanovic said:
Have the device in normal mode, open a command window and run "adb shell"
What do you get?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>adb shell
error: device offline
D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>
o wait i had to accept something on my phone.
edit*
[email protected]:/ $

Try once again with a stockish Rom. It must work. There must be something broken regarding adb in that Rom you are using
Sent from my HTC One using Tapatalk

Ivanovic said:
Try once again with a stockish Rom. It must work. There must be something broken regarding adb in that Rom you are using
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
alright i'll reflash arhd 31.6 now and try adb shell again?
is there a reason why my phone doesnt display a main firmware?

[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

RELOCKED bootloader ! Getting RUU Error 155

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.

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] Need information about current state of this phone I bought.

Hi,
I purchased an HTC One M7 over the internet. It arrived with CyanogenMod on it, but to use my SIM with it, I had to flash AT&T's stock ROM onto the phone. I know little about actually dealing with Phone ROMs & other software things, so I'm unsure what I currently have on this phone.
If I do a factory reset, SuperSU Installer is always an app pre-installed. If I update it and try to root the device, after it reboots, a red triangle with exclamation point comes up with a phone under it. Then after some time, or if I manually do it, it reboots and enters a reboot loop until I go to the boot loader and Factory Reset it again. I read somewhere that this comes up to show that the Recovery is write-protected or something similar.
When booting to the bootloader, this is the information that appears:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
HBOOT
<commands>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
I don't have a warranty to begin with, so I don't particularly care if the TAMPERED message comes up.
If I try and flash CyanogenMod onto the phone using CM's desktop & phone program/app, when the phone reboots, it goes to the bootloader which causes the program on my desktop computer to lose track of the phone.
So, now to my question: What state is this phone in? i.e. Is it rooted? If it is, what is installed on it aside from HBOOT & AT&T's stock ROM, if anything? If it's not, is it because I used AT&T's stock ROM?
My ultimate goal is to get CyanogenMod back on this phone correctly, but everything I've tried with that has hit some roadblock (their desktop program/phone app combo failing, installing TWRP failing, etc.) Any help is appreciated.
Thanks,
Tremor.

Your phone is still S-ON. To be free to do what you want you need to get to S-OFF, methinks.

cichlidiot said:
Your phone is still S-ON. To be free to do what you want you need to get to S-OFF, methinks.
Click to expand...
Click to collapse
Thanks.
That's one thing I was curious about though. If I require S-OFF to install CM, then did my installing of AT&T's ROM cause it to switch to S-ON since it had CM on it before? Just curious.

TremorPV said:
Hi,
I purchased an HTC One M7 over the internet. It arrived with CyanogenMod on it, but to use my SIM with it, I had to flash AT&T's stock ROM onto the phone. I know little about actually dealing with Phone ROMs & other software things, so I'm unsure what I currently have on this phone.
If I do a factory reset, SuperSU Installer is always an app pre-installed. If I update it and try to root the device, after it reboots, a red triangle with exclamation point comes up with a phone under it. Then after some time, or if I manually do it, it reboots and enters a reboot loop until I go to the boot loader and Factory Reset it again. I read somewhere that this comes up to show that the Recovery is write-protected or something similar.
When booting to the bootloader, this is the information that appears:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
HBOOT
<commands>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
I don't have a warranty to begin with, so I don't particularly care if the TAMPERED message comes up.
If I try and flash CyanogenMod onto the phone using CM's desktop & phone program/app, when the phone reboots, it goes to the bootloader which causes the program on my desktop computer to lose track of the phone.
So, now to my question: What state is this phone in? i.e. Is it rooted? If it is, what is installed on it aside from HBOOT & AT&T's stock ROM, if anything? If it's not, is it because I used AT&T's stock ROM?
My ultimate goal is to get CyanogenMod back on this phone correctly, but everything I've tried with that has hit some roadblock (their desktop program/phone app combo failing, installing TWRP failing, etc.) Any help is appreciated.
Thanks,
Tremor.
Click to expand...
Click to collapse
Ok can you boot the phone to the bootloader connect fastboot usb, then in the fastboot command line type
Code:
fastboot getvar all
This will give an output of all the version information for the device. Post it here after removing your IMEI and Serial numbers. You don't want to advertise those
And no you don't need s-off to flash roms, and flashing stock at&t did not and cannot set s-on again.
Let's start with the getvar and take it from there :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

If it goes to boot loader then it sounds like your missing a good recovery image. Flash the recovery and then flash a rom.
Stay away from PC installers and ROM manager.

Danny201281 said:
Ok can you boot the phone to the bootloader connect fastboot usb, then in the fastboot command line type
Code:
fastboot getvar all
This will give an output of all the version information for the device. Post it here after removing your IMEI and Serial numbers. You don't want to advertise those
And no you don't need s-off to flash roms, and flashing stock at&t did not and cannot set s-on again.
Let's start with the getvar and take it from there :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Yes, I entered the bootloader, then I switched to Fastboot which gave me a screen like this:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
FASTBOOT
<commands>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I move the selection down to REBOOT or any other command, FASTBOOT changes to FASTBOOT USB and stays that way.
However, my PC says the USB device malfunctioned, and running the "fastboot getvar all" command does this:
Code:
< waiting for device >
When the HTC One is on and plugged in, it shows up just fine as "My HTC One" under Android USB Devices in Device Manager, so the drivers work.
zelendel said:
If it goes to boot loader then it sounds like your missing a good recovery image. Flash the recovery and then flash a rom.
Stay away from PC installers and ROM manager.
Click to expand...
Click to collapse
It only goes to bootloader when I hold down the Volume Down button.
Not sure how to do that. Still learning.

TremorPV said:
Yes, I entered the bootloader, then I switched to Fastboot which gave me a screen like this:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
FASTBOOT
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I move the selection down to REBOOT or any other command, FASTBOOT changes to FASTBOOT USB and stays that way.
However, my PC says the USB device malfunctioned, and running the "fastboot getvar all" command does this:
Code:
< waiting for device >
When the HTC One is on and plugged in, it shows up just fine as "My HTC One" under Android USB Devices in Device Manager, so the drivers work.
It only goes to bootloader when I hold down the Volume Down button.
Not sure how to do that. Still learning.
Click to expand...
Click to collapse
Sounds like a driver problem on the pc side. Check your drivers are installed correctly. Your phone should appear in device manager as "My HTC" Edit :- I see the drivers are working when the phone is on and then fail see this FAQ post Q (2) to fix your drivers after the malfunction message http://forum.xda-developers.com/showthread.php?p=52135024
What operating system do you have on your pc Windows 7, 8 or 8.1. / Mac OSX?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Sounds like a driver problem on the pc side. Check your drivers are installed correctly. Your phone should appear in device manager as "My HTC" Edit :- I see the drivers are working when the phone is on and then fail see this FAQ post Q (2) to fix your drivers after the malfunction message http://forum.xda-developers.com/showthread.php?p=52135024
What operating system do you have on your pc Windows 7, 8 or 8.1. / Mac OSX?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Will do. (at work atm)
Windows 8.1 64 bit, using WIndows 7 64 bit drivers.

TremorPV said:
Will do. (at work atm)
Windows 8.1 64 bit, using WIndows 7 64 bit drivers.
Click to expand...
Click to collapse
That's what I was afraid of, I can't speak from personal experience as I use Windows very little and if I do it's Windows 7. But to the best of my knowledge Windows 8 and 8.1 are a bit finicky when it comes to adb/fastboot especially if your on hboot 1.44.
There's a thread here you may find helpful there are a few solutions discussed here http://forum.xda-developers.com/showthread.php?t=2347317
Personally I prefer Linux. When all else fails Linux doesn't see my guide here it contains everything you need to know to use Linux without installing it on your pc. Just boot from a usb stick, no drivers require. Just Linux and adb/fastboot http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
That's what I was afraid of, I can't speak from personal experience as I use Windows very little and if I do it's Windows 7. But to the best of my knowledge Windows 8 and 8.1 are a bit finicky when it comes to adb/fastboot especially if your on hboot 1.44.
There's a thread here you may find helpful there are a few solutions discussed here http://forum.xda-developers.com/showthread.php?t=2347317
Personally I prefer Linux. When all else fails Linux doesn't see my guide here it contains everything you need to know to use Linux without installing it on your pc. Just boot from a usb stick, no drivers require. Just Linux and adb/fastboot http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Figured. I had heard they worked with 8, but I guess not.
Awesome.
Me too. If only all of my games worked on Linux. Will try this and get back to you.

TremorPV said:
Figured. I had heard they worked with 8, but I guess not.
Awesome.
Me too. If only all of my games worked on Linux. Will try this and get back to you.
Click to expand...
Click to collapse
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.

Danny201281 said:
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.
Click to expand...
Click to collapse
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: >number<
(bootloader) imei: >number<
(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: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat

TremorPV said:
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: >number<
(bootloader) imei: >number<
(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: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat
Click to expand...
Click to collapse
The failed message is normal with Hboot 1.44 you will always get that until you update hboot.

Danny201281 said:
The failed message is normal with Hboot 1.44 you will always get that until you update hboot.
Click to expand...
Click to collapse
Ah. Good to know.
So in my journey to learn, I decided I wanted to try updatig HBOOT. Which, from what I've read, requires S-OFF, so I went to Firewater. Unfortunately, I didn't realize I needed S-OFF & Firewater, and did the following with S-ON:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip hboot_firewater>version<.zip
Which failed. My phone still works and can get to the fastboot/HBOOT screen, so from what I can tell, no harm was done.
Running firewater based on the instructions on their webpage doesn't really do anything. It pushes the firewater file to the /tmp on the device, but won't run it. Not sure why. Specifically, this happens:
Code:
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
That goes fine. This is where the strange things start:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $ su /data/local/tmp/firewater
That's exactly as it appears in the Terminal. While it's doing this, I get lots of pop ups on Linux about how it's unable to mount the Android Phone. I check my phone after doing the above commands, and it's on the stock AT&T ROM I installed.
There's nothing mentioned about Firewater and nothing has happened AFAIK. Firewater's page says there should be a prompt or something, but there's not.

TremorPV said:
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: >number<
(bootloader) imei: >number<
(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: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat
Click to expand...
Click to collapse
Ok so let's get you phone booting again.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Download this and place it in your fastboot folder. Rename it recovery.img
Flash your recovery with fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now select recovery from the bootloader menu. Now we can push the Rom.
Download this stock Rom drop it in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/did/guru_reset_m7_1-26-502-12-zip/
And push to the phone with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes when it's done install the Rom with twrp recovery.
---------- Post added at 07:37 PM ---------- Previous post was at 07:27 PM ----------
Oh so you have a Rom booting? Ok I'm a little busy for the next hour. If you want to go s-off don't update anything just yet.
Getting s-off will be harder after you update
Use this toolkit to get s-off with revone as your on hboot 1.44 http://forum.xda-developers.com/showthread.php?t=2364445

Danny201281 said:
Ok so let's get you phone booting again.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Download this and place it in your fastboot folder. Rename it recovery.img
Flash your recovery with fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now select recovery from the bootloader menu. Now we can push the Rom.
Download this stock Rom drop it in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/did/guru_reset_m7_1-26-502-12-zip/
And push to the phone with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes when it's done install the Rom with twrp recovery.
---------- Post added at 07:37 PM ---------- Previous post was at 07:27 PM ----------
Oh so you have a Rom booting? Ok I'm a little busy for the next hour. If you want to go s-off don't update anything just yet.
Getting s-off will be harder after you update
Use this toolkit to get s-off with revone as your on hboot 1.44 http://forum.xda-developers.com/showthread.php?t=2364445
Click to expand...
Click to collapse
ARGH. Didn't read the whole post before doing anything. Finished flashing the recovery.img to the recovery before I finished your post. I needed a different recovery anyway as I don't like the current one, so yay at least. I didn't boot into recovery though, so hopefully I'm fine.
It's fine. Take your time. I've got all day.
Yes, I would like S-OFF just so I can update HBOOT so that if I want to tinker with my phone in the future it will be easier to do. I may not like CyanogenMod, so trying out Kit Kat and other things will be easier (I imagine) without whatever is making it hard to deal with this phone.

Danny201281 said:
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.
Click to expand...
Click to collapse
Same here. Give me my games and a few apps and good bye Windows lol

TremorPV said:
ARGH. Didn't read the whole post before doing anything. Finished flashing the recovery.img to the recovery before I finished your post. I needed a different recovery anyway as I don't like the current one, so yay at least. I didn't boot into recovery though, so hopefully I'm fine.
It's fine. Take your time. I've got all day.
Yes, I would like S-OFF just so I can update HBOOT so that if I want to tinker with my phone in the future it will be easier to do. I may not like CyanogenMod, so trying out Kit Kat and other things will be easier (I imagine) without whatever is making it hard to deal with this phone.
Click to expand...
Click to collapse
Ok so cool, flashing recovery won't cause any issues with s-off later on, so you can flash what ever recovery you preffer.
Hboot can be updated without s-off but once you do it gets much harder to s-off as HTC have implemented patches into the newer firmware to try and prevent it. unless you wanna pay $25 for Sunshine app which should work regardless.
Getting s-off with revone is by far the easiest way to do it for free if your on hboot 1.44 Personally I've never used revone all devices I s-offed were already on higher hboot versions so had to use other methods. So you should read through the link I posted to get that done but it sounds fairly simple using that toolkit. Once your s-off the sky's the limit pretty much.

Danny201281 said:
Ok so cool, flashing recovery won't cause any issues with s-off later on, so you can flash what ever recovery you preffer.
Hboot can be updated without s-off but once you do it gets much harder to s-off as HTC have implemented patches into the newer firmware to try and prevent it. unless you wanna pay $25 for Sunshine app which should work regardless.
Getting s-off with revone is by far the easiest way to do it for free if your on hboot 1.44 Personally I've never used revone all devices I s-offed were already on higher hboot versions so had to use other methods. So you should read through the link I posted to get that done but it sounds fairly simple using that toolkit. Once your s-off the sky's the limit pretty much.
Click to expand...
Click to collapse
Sweet.
Figured. Sounds just like when I jailbroke my old PSP-2000.
I tried that tool, but this is what happened:
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb reboot
error: more than one device and emulator
Revone & Firewater both say this. This tool does not have a Linux version unfortunately.

TremorPV said:
Sweet.
Figured. Sounds just like when I jailbroke my old PSP-2000.
I tried that tool, but this is what happened:
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb reboot
error: more than one device and emulator
Revone & Firewater both say this. This tool does not have a Linux version unfortunately.
Click to expand...
Click to collapse
What output do you get from adb devices?