Database Develop

[Q] Can't boot to recovery, can't s-off

Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.

eisteh said:
Hi,
two weeks ago I sent in my HTC One (O2 Germany branded) because it had a stuck pixel and today I got a brand new replacement phone.
I wanted to get back on to my old ROM etc pretty fast and thought I'd use the AIO Toolkit to unlock/s-off/etc this time instead of doing all on my own.
First thing I did was getting a new unlock token and then unlock the phone, use AIO to flash recovery (bootloader still showed unlocked which I didn't notice at that time of the process) and directly went to s-off to convert my phone to a google edition phone afterwards.
Then things started to visibly not work. Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Then I thought about using recovery and just flash a custom ROM for now and do the firmware part later, when I noticed that recovery isn't working, too.
I'm pretty clueless now, I have relocked and unlocked my phone again, tried to flash all sorts of recoveries (both CWM and TWRP, newest and older versions), tried to revone again (still the above mentioned errors). I also searched a bit on the forums here and found nothing of value (few things which were said to help - still no success).
Fastboot getvar all also drops an error:
C:\Android SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34VW908233
(bootloader) imei: 354436054362833
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I'm not a noob, I read carefully what to do when I get a new device, I know where to look for everything here and I've been flashing ROMs and doing all this stuff on my HTC devices for quite some time now. And yes, I have upgraded my HTC drivers.
It's possible that I missed something though. Nobody is perfect. I'm gratefull for every piece of help I get from you people.
Click to expand...
Click to collapse
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?

herwegan said:
Strange.. all i can see here is that in getvar all is no error, this "failed"message appears everytime.
So basically now the only thing you can access is the bootloader?
Click to expand...
Click to collapse
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.

eisteh said:
Ok, then I don't have to be worried about the getvar all..
No, I can also boot the Stock ROM fine. I'm just not able to go custom at all.
Also, which might be of interest: Selecting factory reset in the recovery does NOTHING. Phone reboots, everything is still there. Software reset (from the ROM) works fine.
Click to expand...
Click to collapse
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.

iElvis said:
I suspect revone borked something. It's a hack; it happens. You probably need to RUU back to stock, as it sounds like you've messed up something important in your system settings.
Click to expand...
Click to collapse
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...

eisteh said:
And as there seems to be no RUU for HTC One O2 Germany.. I'm doomed?
EDIT: As recovery wasn't working before revone, maybe there already was a problem with the phone? I was so happy to get my phone back and now it's even worse than before...
Click to expand...
Click to collapse
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).

herwegan said:
You couldchange your cid to htc___001 and flash the open europe RUU 1.28 and at least see if it helps. Then change cid back to O2 germany (not 100% sure if this is possible).
Click to expand...
Click to collapse
Which would require s-off which doesn't work.

eisteh said:
Revone was granted root for the preparation process, everything went fine, I rebooted. Then, s-off failed. Now root started to drop errors (was something with memory can't be allocated) and revone gave me -1 and -6 errors.
Click to expand...
Click to collapse
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?

crushalot said:
After you ran revone -P, did you reboot with a manual hold of the power button or with adb command? Should use the power button.
I have found that the revone process works better when you don't change to su before ANY of the commands.
Also I have found that a lot of revone issues were adb related and changing to a different USB port or PC helped. On a few systems it worked much better to do all the commands with a terminal emulator on the device rather than an ADB shell session.
Perhaps see if any of those tips helps with a successful s-off.
Regarding your SU app issues, try to clear data from whatever SU app you are using and then reboot and then open the app and make sure it doesn't need the SU binaries updated.
Sometimes it can take 15-20 attempts to get revone to work. How much did you try?
Click to expand...
Click to collapse
Yes, I did a manual reboot.
Revone is said to work without SU and therefore uses it's integrated rooting process. I'm not rooted otherwise, I'd rather have my recovery working and flash a custom ROM then
I tried to run revone like 10 times (on my old device it took me exactly one try), I will consider your tipps and try again.

[Q] I need help Please Rogers HTC One stuck in h-boot

Hi everyone,
Im kind of new to the android world and stupid for me i did things without being absolutely certain. So i have an unlocked originally Rogers Htc one and i had it under the google play edition rom with cwm recovery installed, unlocked bootloader and all that good stuff. I needed to send it in for warranty purposes so i wanted to try to put it back to stock sense 5 rom. i followed tons upon tons of videos and i ended finding an RUU that might have worked so i relocked my bootloader and followed the processes but every time i did typed the "fastboot flash zip firmware.zip" command it would go 75% of the way and then stop but in the command window it said successful. Unlocked my bootloader again but i forgot that it wipes everything so now i dont even know if i have cwm installed to flash any rom at all. So basically i think my phone is bricked :'( im crying my head off. If anyone has any input on how i can convert this htc one back to stock and working or even any custom rom just so it can work please let me know im really scared at this point. Thankyou for reading

SaadQamer said:
Hi everyone,
Im kind of new to the android world and stupid for me i did things without being absolutely certain. So i have an unlocked originally Rogers Htc one and i had it under the google play edition rom with cwm recovery installed, unlocked bootloader and all that good stuff. I needed to send it in for warranty purposes so i wanted to try to put it back to stock sense 5 rom. i followed tons upon tons of videos and i ended finding an RUU that might have worked so i relocked my bootloader and followed the processes but every time i did typed the "fastboot flash zip firmware.zip" command it would go 75% of the way and then stop but in the command window it said successful. Unlocked my bootloader again but i forgot that it wipes everything so now i dont even know if i have cwm installed to flash any rom at all. So basically i think my phone is bricked :'( im crying my head off. If anyone has any input on how i can convert this htc one back to stock and working or even any custom rom just so it can work please let me know im really scared at this point. Thankyou for reading
Click to expand...
Click to collapse
Can you still boot in bootloader?
if you can, you can flash a custom recovery (TWRP or CWM) again so you can install a custom rom.
it would be best if you can do fastboot getvar all and post the result here so everyone can have a clearer view on what RUU you need. will definitely help to help you properly.

Are you able to get into fastboot? If you can get into fastboot, you'll be able to flash a custom recovery, and then from there on you can either mount USB storage or use adb sideload to flash a rom onto your phone.

Thyankyou for responding
thanks for responding, if bootloader is the menu with fastboot and factory reset and those options then yes i can boot into that because my phone is off right now and i can hold vol. down and power to go into that. not sure how i can flash a custom rom though or even a recovery any help with that would be greatly appreciated as well. the phone is currently blinking with an orange light leaving me to assume the battery is deal so i cant even turn it on at the moment but i will post the getvar command when it does thankyou so much, by the way the phone is an htc one rogers just for clarification.

getvar
when i typed in fastboot getvar all i got this
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34GW901697
(bootloader) imei: 354439053152296
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3760mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.064s
again any help with these will be greatly appreciated

please help! htc one possible boot loop of death.

edit and tldr
ok so i recieved the phone from htc with a bootloop out of the box
instead of sending it back i was a numpty and decided to sort it myself and unlocked it to flash a rom
i accidentially deleted all the data
managed to get my winsows 8 laptop working today and got drivers working smoothly to the point i was able to sideload a rom so the phone finally had life from being a brick
my issue is no matter what rom i load it boots to splash screen, hangs at a black screen with the status bar at the top and battery and time then reboots and repeats.
i want help to get my phone back to life and stable with a workable rom and no bootlooping
i dont know what the issue is
i dont have s off
rumrunner wont work
i cannot boot into phone to allow debugging or disable fast boot
please help
device info
C:\Documents and Settings\fresh\Desktop\one\data>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: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(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: 4327mV
(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.328s
i will offer a small sum for who ever gets me a working phone. small exchange for a paperweight !

Deleted. Op edited post to include cash reward. Dont want to look like im helping to receive money.

hi there, thank you for the reply, i have done steps 1, id already done that but ive done it again and installed the sdk into a folder in c drive for ease. the only problem is that when i click on fastboot in xp it comes up with a cmd windows a lot of writing comes down and then it just closes :/
ive already voided the warranty as ive somehow managed to unlock the bootloader and ive flashed cmw now what i need to do is somehow get s off and sideload a rom

another issue i have is that because i cant use fastboot the way youve said, ive downloaded an all in one tool from this forum, when i click a process it dosent do anything for me, but what it does so, is open a cmd window in which im able to type in fast boot commands i did the getvar all command and here is what you requested
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\fresh\Desktop\one\data>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: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(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: 4327mV
(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.328s
C:\Documents and Settings\fresh\Desktop\one\data>

Deleted

garyfl said:
ok so i think this is going to be a little long winded
basically, i got a htc one given to me by htc,
Click to expand...
Click to collapse
Why don't you think they would give you a new working one?... :s (this is just a rhetorical question)

thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu

the ruu you have linked indicates i need s off, which i am having trouble doing, could you guide me ? i am thinking when i have fixed my windows 8 laptop tommorow this is going to be a smoother process. it also says i need hboot 1.44 and have to flash this

garyfl said:
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
Click to expand...
Click to collapse
If you don't solve it before I get a lil bit of time, I can try for tonight but can't promise it as it's still hectic here at work, I'll log in remotely and have a look at things if you want, and try to help you get it sorted.
In the meantime, you can take a picture of the hboot or fastboot screen that you get to with power + vol down and post it, and that will help you get the information from us for more information on the phone.
Also post a shot of the correspondence from HTC with your personal information removed/redacted/left out and that will also help us help you.
DO NOT ATTEMPT S - OFF with the knowledge and hardware that you're working with, you first need to use adb and fastboot some and be familiar with it before even going there. I'm not saying not ever, I'm saying not until you've resolved this and the phone's running good.

Deleted

when i run rumrunner with my version 2.24.401.1 it just says run again and read. so obviously failing. i did everything before i typed fastboot devices and got my device code, then getvar ver to get my number and downloaded appropriately but rum runner dosent work. so no s off. i give up.

sorry didnt read your reply, well it didnt initialise so no s off anyway

garyfl said:
sorry didnt read your reply, well it didnt initialise so no s off anyway
Click to expand...
Click to collapse
Take a picture of the hboot screen and post it for us

im sorry i cant take a pic atm no cameras, what i can do is write eveything out as it looks in detail for you
***tampered*** <--- in dark grey
***unlocked*** <--- in pink
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENdsp-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00.54:00.14313
FASTBOOT USB <--- in red
then its just the vol up and down with selecable bootloader, reboot, reboot bootloader, power down at the bottom. i have rooted many phones in the past, desire hd, one x, galaxy note, galaxy s4, its just the trouble i am facing i think is using xp

can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.

garyfl said:
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
Click to expand...
Click to collapse
flash twrp/cwm recovery to your one
open the sideload feature of the customer recovery on your phone and connect to your computer usb
download this and put the downloaded file together with your adb and fastboot folder
then adb sideload or adb push the dowloaded guru reset to your One
once it is done, you can install the guru reset zip using the custom recovery install option

right just to update i have some semi good news and fell im getting somewhere
got my windows 8 laptop up and running today and installed all drivers and adp corrdctly, this accounts for the intel usb 3 mod too. adb and fastboot were recognising the device.
ive succesfully got out of brick mode and managed to get a rom to sideload to the deviice, the rom being viper rom in question, installed successfully, only issue is i have a wierd bootlooping issue where it does actually boot to lockscreen but when i pull lockscreen up with my finger it shows htc splash screen.
having ago with android revolution now.
wondering if i have to flash a boot.img or something
can anyone advise ?
ive spent countless days on this

regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,

garyfl said:
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
Click to expand...
Click to collapse
the guru ruu.zip for 2.24.401.1 is sideloading now

guys, the guru stock installed but now im back to the very beginning of the way i recoieved my phone. bootloops to the black screen with bar at top with date and battery, then after a while restarts, please someone help me

[Q] Just need stock recovery. No root. No ROM. S-ON

I am computer stupid. More so with phones. This is my brothers old phone. It has TWRP installed. Not rooted. No custom ROM.
All I want to do is get back the stock recovery so I can get this annoying "System update available" message to stop popping up all the time. The update is for software version 6.07.1540.1. Looks like it would upgrade to 4.4.3 as well.
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 23 2014,00:42:43.0
That is what the bootloader has on it. It is the developer edition if that changes anything. I am using it currently on Straight Talk.
Android Version is 4.4.2
Sense Version is 6
Software number is 5.11.1540.9
I will provide any other details you may need. I am sorry if this has been covered before, which I am sure it has. I have read thread after thread and haven't learned anything.
Please explain like I am a mentally disabled 3 year old. If it is complicated I will hire you as a private tutor to walk me through it.
Thank you in advance for your help. I do apologize if this question is redundant. I just don't understand the other threads answers out there.

cptplatty said:
I am computer stupid. More so with phones. This is my brothers old phone. It has TWRP installed. Not rooted. No custom ROM.
All I want to do is get back the stock recovery so I can get this annoying "System update available" message to stop popping up all the time. The update is for software version 6.07.1540.1. Looks like it would upgrade to 4.4.3 as well.
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 23 2014,00:42:43.0
That is what the bootloader has on it. It is the developer edition if that changes anything. I am using it currently on Straight Talk.
Android Version is 4.4.2
Sense Version is 6
Software number is 5.11.1540.9
I will provide any other details you may need. I am sorry if this has been covered before, which I am sure it has. I have read thread after thread and haven't learned anything.
Please explain like I am a mentally disabled 3 year old. If it is complicated I will hire you as a private tutor to walk me through it.
Thank you in advance for your help. I do apologize if this question is redundant. I just don't understand the other threads answers out there.
Click to expand...
Click to collapse
Ok let's start with some preliminary basics so I can understand exactly what I'm dealing with here
Do you know what adb is, and how to use it?
Do you know what fastboot is and how to use it?
What Operating system do you have on your pc? Windows 8 or 7, Linux, or if your using a Mac, Mac osx?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok let's start with some preliminary basics so I can understand exactly what I'm dealing with here
Do you know what adb is, and how to use it?
Do you know what fastboot is and how to use it?
What Operating system do you have on your pc? Windows 8 or 7, Linux, or if your using a Mac, Mac osx?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
no to adb. yes to fastboot. I can make the bootloader say "fastboot usb". I have the fastboot stuff on my windows 8 laptop.
I am using windows 8 on this laptop but have his windows 7 laptop that he used which should still have all the tools needed to put TWRP on there.

cptplatty said:
no to adb. yes to fastboot. I can make the bootloader say "fastboot usb". I have the fastboot stuff on my windows 8 laptop.
I am using windows 8 on this laptop but have his windows 7 laptop that he used which should still have all the tools needed to put TWRP on there.
Click to expand...
Click to collapse
Ok well it's better to use Windows 7, Windows 8 drivers can be problematic and may confuse things.
Do you know if your brother has used ota updates since unlocking the bootloader? The reason I ask is that unlocking the bootloader wipes some important pre-loaded apps from the device. And will cause the update to fail and soft-brick the phone.
Your brother may have known this so it's possible he restored the complete stock Rom previously but it's better to know before hand.
Can you connect fastbootusb then in the fastboot command line type
Code:
fastboot getvar all
Then post the output here. Please Edit out the imei and Serial no from the information before posting.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

I know he intended to put a custom ROM on but never did. All he did was install TWRP. There have been no OTA updates that came out since he did that. This one is the first. He did root through TWRP once but ran into a boot loop and restored through TWRP to before the Root and always has said no when TWRP ask if you want to root.
He is in the military and stayed with me while he was back for a while. I am also calling him in between post and asking him questions.
Here is what you asked for
C:\Users\Eric\Desktop\htc one\fastboot>fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s

cptplatty said:
I know he intended to put a custom ROM on but never did. All he did was install TWRP. There have been no OTA updates that came out since he did that. This one is the first. He did root through TWRP once but ran into a boot loop and restored through TWRP to before the Root and always has said no when TWRP ask if you want to root.
He is in the military and stayed with me while he was back for a while. I am also calling him in between post and asking him questions.
Here is what you asked for
C:\Users\Eric\Desktop\htc one\fastboot>fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Click to expand...
Click to collapse
Ok good thanks. So are you against using a custom Rom? It may be the easiest way to update the phone at this point and will solve the problem of the annoying update notification.
Or would you prefer to keep it stock?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok good thanks. So are you against using a custom Rom? It may be the easiest way to update the phone at this point and will solve the problem of the annoying update notification.
Or would you prefer to keep it stock?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I would like to keep it stock because I plan on selling it on eBay soon. Maybe. Stock phones bring in more cash than custom ROM phones.
Though if it is too difficult to bring to stock, I will ROM it and just keep it. As I understand it, if it's a good ROM it can help keep it up to par with current phones a little longer than a stock ROM would.

How hard will it be to get the stock recovery. Your questions make it seem like it is going to be quite an undertaking.
If that is the case, then yes I will custom ROM it.
Though I would like to know what the process would be for the stock recovery. Just to see if it would be something I could do. It does not have to be a detailed explanation. Just something to get a better idea of.

cptplatty said:
How hard will it be to get the stock recovery. Your questions make it seem like it is going to be quite an undertaking.
If that is the case, then yes I will custom ROM it.
Though I would like to know what the process would be for the stock recovery. Just to see if it would be something I could do. It does not have to be a detailed explanation. Just something to get a better idea of.
Click to expand...
Click to collapse
cptplatty said:
I am computer stupid.
Please explain like I am a mentally disabled 3 year old.
Click to expand...
Click to collapse
That's why all the questions, I'm just trying to understand exactly what you expect the end result to be since the procedures are quite different depending on what you want to end up with.
To be honest getting a stock recovery is easy very easy. But restoring the stock pre-load data is not. You need a complete stock Rom including the pre-loaded apps or the OTA update will soft-brick your phone. Normally not difficult to recover from but in some cases has caused irreversible effects.
Returning to stock for sale or Warranty is whole different ball game. For that you first need to make the device s-off.
Currently it is s-on so you won't be able to set the bootloader back to ****LOCKED**** and you won't be able to remove the ****TAMPERED**** flag on the bootloader screen. There for the buyer or repair center would know that the phone was tampered with at some point.
You can use a reset zip to restore the stock software but the only one I can find for your device is older than your current firmware and again will cause problems when installing ota updates.
Once again because the phone is s-on you cannot downgrade the firmware only HTC signed firmware updates are possible with s-on.
This I'd why I suggested a custom Rom. You can simply flash a custom 4.4.3 Rom and that's that. The ota update notification will be gone and the phone will be running the latest software.
Custom roms generally are better in performance than Stock roms and yes you can normally get custom roms for newer software releases than were ment for the device. Although official support has not ended for the HTC One so there are still updates to come.
If you do want to return to stock to sell the phone your first priority is achieving s-off. Then take a look at this guide. http://forum.xda-developers.com/showthread.php?t=2541082.
The procedure for flashing a recovery weather it is stock or custom is the same and very simple. Download your chosen recovery. (which will be a .img file) put the .img file in your fastboot folder on your pc.
Now connect fastbootusb in the bootloader and in the command line type
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Obviously changeing "nameofrecovery".img for the actual name of the recovery file.
Or last and probably best option would be to achieve s-off. Then you can do pretty much whatever you want to it.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[Fixed] Bricked Hboot 1.44 with RUU 1.31 (Explanation on how solved in OP)

[Fixed][Solution]
This should work for anyone who soft bricked there device but still has the 1.44 HBoot to allow them to still flash a recovery. I did not come up with any of this but was helped by nkk71 who showed me the way. I dealt with this problem for over 2 days now non-stop trying to fix it only missing 1 step that made all the difference.
This method is for a HTC One (M7) Sprint Variant:
-Be sure to use HTCDev to unlock your phone and flash a custom recovery. (I used TWRP)
-Be sure to have all the adb and fastboot exe files needed. If you bricked your phone you most likely already do but if not there are tons of links on the forums to help you get all the information you need from them.
-Check to make sure what RUU your phone is at by going into fastboot and using a cmd window type: fasboot getvar all. This will display your phones information. If you happen to be at 1.31 like my phone was you will need to do the next step, if not then find your recovery.
- Fix your version main to say 1.29.651.10 by editing the misc partition
Boot into recovery
In the recovery mount your device. I mounted all parts in TWRP.
Open a cmd window and doucle check that your device is connected by typing: adb devices
(If it shows a set up numbers and letters and then says recovery then that is your device.)
Now type: adb shell
type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
type: adb reboot bootloader
Once it loads back into the bootloader click on fastboot and check to see if your device is connected by typing: fastboot devices
If you see you device type: fastboot oem lock (This will relock your device)
- Now you are ready to run the RUU. (After it runs your phone is back to stock)
If any of this is confusing, there are links below that were used to get me through this. If you need to do this I wish you luck.
Original Post:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.

toxicfumes22 said:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output

nkk71 said:
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
Click to expand...
Click to collapse
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.059s
2) Yes on Sprint, but with no activation on this phone now.
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
BTW, Thank you for the response.

toxicfumes22 said:
BTW, Thank you for the response.
Click to expand...
Click to collapse
Sure, no problem.
toxicfumes22 said:
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
2) Yes on Sprint, but with no activation on this phone now.
Click to expand...
Click to collapse
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
toxicfumes22 said:
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
Click to expand...
Click to collapse
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
toxicfumes22 said:
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
Click to expand...
Click to collapse
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction

nkk71 said:
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
Click to expand...
Click to collapse
Nice trick, still learning a lot from you

alray said:
Nice trick, still learning a lot from you
Click to expand...
Click to collapse
it's an "old trick", i take no credit at all for it ... as long as hboot version is the same, fixing the version-main (using adb or even the "misctool" <- it's somewhere on xda, dont have a link handy atm) should work fine
extract:
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version... [I]<- this is where it would fail, without that fix[/I]
(bootloader) checking hboot version... [I]<- this is where it would fail if hboot is higher[/I]
(bootloader) start image[boot] unzipping & flushing...

nkk71 said:
Sure, no problem.
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
Click to expand...
Click to collapse
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.

toxicfumes22 said:
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
Click to expand...
Click to collapse
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.

New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.

toxicfumes22 said:
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
Click to expand...
Click to collapse
yes should work fine now, give it a try.

alray said:
yes should work fine now, give it a try.
Click to expand...
Click to collapse
nkk71 said:
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
Click to expand...
Click to collapse
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.

toxicfumes22 said:
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
Click to expand...
Click to collapse
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk

nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
All thanks for you
My only contribution here was to say "give it a try" :laugh:

alray said:
All thanks for you
My only contribution here was to say "give it a try" [emoji23]
Click to expand...
Click to collapse
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk

nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
I copied and pasted, its exactly what I used. If it's wrong let me know and I'll fix though.
Another update though is I am now Unlocked with S-Off w/o Tampered. Basically what I wanted.
Now should be my last questions, but it's a good idea to update to the newest firmware correct?
Firmware will never be able to stop me from achieve what I just did to fix the phone correct?

nkk71 said:
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
Yup, I was going to not do a thing until I had a response. I was just worried I'd somehow mess it up. Just one confirmation that it looked good was enough to give me confidence.