HTC one M7 continuously reboots till battery drains - One (M7) Q&A, Help & Troubleshooting

I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>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.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks

hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>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.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
Did you do a factory reset? If so you will need to reflash the rom.

zelendel said:
Did you do a factory reset? If so you will need to reflash the rom.
Click to expand...
Click to collapse
i have tried doing factory reset but it stops giving a red triangle with an exclamation mark.
i would be glad if you can guide me to the steps regarding reflashing the rom.

hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>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.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
waiting for assistance

hammaad110 said:
waiting for assistance
Click to expand...
Click to collapse
Search the site. Everything you need has already been posted.

zelendel said:
Search the site. Everything you need has already been posted.
Click to expand...
Click to collapse
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.

hammaad110 said:
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.
Click to expand...
Click to collapse
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.

zelendel said:
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.
Click to expand...
Click to collapse
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.

hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
Then something is wrong with your driver set up. Check the threads in this section of other ways to get it working. I know that if you had HTC sync installed that it would cause these issues. I have never had this issue where what I discribed above didnt fix

hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device

nkk71 said:
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device
Click to expand...
Click to collapse
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
you should redo all the unlocking procedure try that

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
not sure what you mean, but:
fastboot commands work in bootloader (FASTBOOT USB on the phone screen), adb does not
adb commands work in custom recovery
adb commands work in booted up phone with USB debuggin enabled

hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
hammaad110 said:
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.

nkk71 said:
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.
Click to expand...
Click to collapse
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)

nkk71 said:
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)
Click to expand...
Click to collapse
From our pm's
Then it may be because you need to update hboot first.
Are you running the ruu to fix a bootloop problem?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
From our pm's
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe

nkk71 said:
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe
Click to expand...
Click to collapse
I don't know the bootloader color sorry maybe @hammaad110 can post a picture for us?
I may have a go at capturing the otas if I can make time for it. I won't be capturing them all though may be just the 2.xx and 3.xx with Stock nandroids that would be enough for using the RUU at least and possibility of a reset zip.
Besides I already have the necessary files to make the change to O2. So I wouldn't trouble yourself with that. It was my idea so I wouldn't expect you to go to the trouble of making it happen
As for the bootloader unlocking problem I remember a similar case, although weather we came to a solution is sketchy in my memory. I seem to remember flashing the current firmware fixed the problem. I'll look through my posts and pm's to try to find it so I can clarify it. If that was the case I'll probably capture the ota's to help this guy out and maybe a few others.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Related

As if I'd never touched it

Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
smartiejoe said:
Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
Click to expand...
Click to collapse
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
alray said:
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
Click to expand...
Click to collapse
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(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: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
smartiejoe said:
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(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: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
alray said:
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
Click to expand...
Click to collapse
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
smartiejoe said:
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
Click to expand...
Click to collapse
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
S-OFF is a gift and should never be taken for granted. If you throw it away it may not be available to you again.
S-ON is an operation I would defer until I learned that I actually *need* to send in the phone to someone who cares if it is S-ON or not.
S-ON is always the last step in any "going back to stock " process, the very last thing before the phone leaves your possession. And even then the step is usually optional. Warranty repair people often don't care, eBay doesn't care, it's just really rare that there is *any* actual benefit.
Sent from my HTC One using xda app-developers app
alray said:
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
Click to expand...
Click to collapse
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible. Decent battery life, decent speed, and not too much hassle to return to complete stock if necessary.
I'll take your advice on what you think is best!
smartiejoe said:
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible.
Click to expand...
Click to collapse
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
smartiejoe said:
not too much hassle to return to complete stock if necessary.
Click to expand...
Click to collapse
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
alray said:
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
Click to expand...
Click to collapse
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
smartiejoe said:
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
Click to expand...
Click to collapse
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
alray said:
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Click to expand...
Click to collapse
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
smartiejoe said:
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
Click to expand...
Click to collapse
have you checked md5?
Maybe you could try another usb cable or another usb port
alray said:
have you checked md5?
Maybe you could try another usb cable or another usb port
Click to expand...
Click to collapse
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
smartiejoe said:
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
Click to expand...
Click to collapse
Try another usb cable. You could also try the 1.28.401.7 ruu
alray said:
Try another usb cable. You could also try the 1.28.401.7 ruu
Click to expand...
Click to collapse
I just read somewhere that hboot 1.44 might be needed, and I have 1.54. So I shall flash 1.44 and see if it works then!
EDIT: When trying to flash hboot 1.44 it won't even send the 501kb zip file, even through a brand new usb cable. Updating drivers now to see if that works

[Q] HTC One not booting and not going into recovery. Plz help.

My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,
anirudhgargi said:
My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,
Click to expand...
Click to collapse
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache
stovie_steve said:
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache
Click to expand...
Click to collapse
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen
anirudhgargi said:
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen
Click to expand...
Click to collapse
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?
S-on , Bootloader locked. Complete Stock.
stovie_steve said:
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?
Click to expand...
Click to collapse
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks
anirudhgargi said:
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks
Click to expand...
Click to collapse
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI
GetVar All Output.
stovie_steve said:
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI
Click to expand...
Click to collapse
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.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: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
anirudhgargi said:
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.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: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?
Rooted when it was 4.1 on At&t. But never then.
stovie_steve said:
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?
Click to expand...
Click to collapse
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?
anirudhgargi said:
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?
Click to expand...
Click to collapse
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader
Ohh ! i don't have a Window machine also handy
stovie_steve said:
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader
Click to expand...
Click to collapse
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.
anirudhgargi said:
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.
Click to expand...
Click to collapse
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either
Many thanks, i will update after doing all those steps.
stovie_steve said:
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either
Click to expand...
Click to collapse
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
ANirudh
anirudhgargi said:
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
Anirudh
Click to expand...
Click to collapse
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?
Which Custom rom to flash for next step.
anirudhgargi said:
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?
Click to expand...
Click to collapse
I have unlocked the bootloader and got a custom recovery (twrp) . I am still s-on. To do S-off
i need to have a working android , for that i need a custom rom. Can anybody tell which rom can be good , i have already the latest Stock 4.4 with "S-ON" and unlocked bootloader.
I cannot flash a htc rom directly as i am S-on and have latest update. To download a version lower (RUU avail) i need to do s-off.
My final aim to get back to Stock 4.4 Sense 6 . This way i approached my HTC one hit a boot loop and not coming out after all methods.

[Q] Is this phone bricked?

Afternoon peeps.
A friend at work has just dropped a HTC One (m7) onto my desk asking if i can bring it back to life. Allegedly whilst flashing the ROM the USB cable detached.
Any who, the phone is stuck on the bootloader. It's TAMPERED, RELOCKED, HBOOT-1.55
I cannot unlock the phone with the HTC unlock token or fastboot oem unlock
The former recycles power but still says RELOCKED, the latter gives me (ERR Command error !!!)
If I run fastboot oem rebootRUU the phone cycles power then returns to the bootloader.
I've tried running "RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe". This states I'm on image 3.63.61.1 so i'm guessing it can communicate in some ways but sadly it fails to push the image after rebooting the phone back into Bootloader (I assume it's going for the oem recovery here?)
Any suggestions or is it dead in the water?
elmuziko said:
Afternoon peeps.
A friend at work has just dropped a HTC One (m7) onto my desk asking if i can bring it back to life. Allegedly whilst flashing the ROM the USB cable detached.
Any who, the phone is stuck on the bootloader. It's TAMPERED, RELOCKED, HBOOT-1.55
I cannot unlock the phone with the HTC unlock token or fastboot oem unlock
The former recycles power but still says RELOCKED, the latter gives me (ERR Command error !!!)
If I run fastboot oem rebootRUU the phone cycles power then returns to the bootloader.
I've tried running "RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe". This states I'm on image 3.63.61.1 so i'm guessing it can communicate in some ways but sadly it fails to push the image after rebooting the phone back into Bootloader (I assume it's going for the oem recovery here?)
Any suggestions or is it dead in the water?
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" make sure to remove imei and serialno before posting it.
alray said:
Post the output of "fastboot getvar all" make sure to remove imei and serialno before posting it.
Click to expand...
Click to collapse
Thanks for responding so quickly. Find the results below :
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.63.61.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4163mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b0a25cb2
hbootpreupdate: 11
gencheckpt: 0
elmuziko said:
Thanks for responding so quickly. Find the results below :
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.63.61.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4163mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b0a25cb2
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
elmuziko said:
Afternoon peeps.
(...)
Allegedly whilst flashing the ROM the USB cable detached.
(...)
It's TAMPERED, RELOCKED, HBOOT-1.55
Click to expand...
Click to collapse
Interesting. How could he flash a rom if the bootloader was relocked? Did he relocked the bootloader after the failed rom flash?
I cannot unlock the phone with the HTC unlock token or fastboot oem unlock
The former recycles power but still says RELOCKED, the latter gives me (ERR Command error !!!)
Click to expand...
Click to collapse
fastboot oem unlock method only works for GPE variant of the M7. All other variants must use htcdev.com method.
You said that the phone is rebooting and still locked when flashing the unlock token. Does it hang at "entering recovery" screen after selecting "yes" to unlock then it reboot or it reboot right after selecting "yes" to unlock (not hanging at "entering recovery" screen)?
If I run fastboot oem rebootRUU the phone cycles power then returns to the bootloader.
Click to expand...
Click to collapse
not good. Phone should reboot to a black screen with silver "HTC" logo when running fastboot oem rebootRUU. Its might confirm a bootloader issue....
I've tried running "RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe". This states I'm on image 3.63.61.1 so i'm guessing it can communicate in some ways but sadly it fails to push the image after rebooting the phone back into Bootloader (I assume it's going for the oem recovery here?)
Click to expand...
Click to collapse
Your phone is on .61 firmware CID is ORANG001 (orange UK) and MID is PN0710000. The .401 ruu versions are for CID HTC__001 (carrier unlocked/international), will not work on this phone. You need a .61 ruu and because the phone is s-on, it must the same version or higher (can't downgrade). So you need 3.63.31.1 or above (e.g 4.xx.61.x or 7.xx.61.x). Unfortunately, I can not find any ruu for this version.
The issue with the bootloader stuck at relocked might be the result of relocking the phone with a custom recovery still installed. Stock recovery is needed to unlock the bootloader. Normally this issue can be solved by flashing the same version firmware.zip (3.63.61.1) in ruu mode which will rewrite stock recovery and then enable the phone to be unlocked again. Problem: 1: you need to access ruu mode (which doesn't work) 2: You need the 3.63.31.1 stock firmware.zip (which i can't find on the usual hosting websites).
Make sure you have the latest sdk tools 1.0.32. the command "adb version" will tell you that.
Also make sure you have the latest HTC drivers installed.
Then try to unlock the bootloader again using htcdev.com method. Try to get a new unlock_code.bin by submitting to unlock token again.
Try other usb ports, usb cable.
If you really can't unlock the bootloader or access ruu mode, im afraid there is nothing to do except to send to phone to HTC for repair.
alray said:
Interesting. How could he flash a rom if the bootloader was relocked? Did he relocked the bootloader after the failed rom flash?
Click to expand...
Click to collapse
Yeah so I'm told. When it failed to flash he went through a heap of options including locking the loader for some reason; I have no idea why.
alray said:
fastboot oem unlock method only works for GPE variant of the M7. All other variants must use htcdev.com method.
You said that the phone is rebooting and still locked when flashing the unlock token. Does it hang at "entering recovery" screen after selecting "yes" to unlock then it reboot or it reboot right after selecting "yes" to unlock (not hanging at "entering recovery" screen)?
Click to expand...
Click to collapse
I get the prompt for unlocking, hit yes then the screen goes blank for a few seconds, a white HTC screen then the bootloader with RELOCKED still as the status.
alray said:
The issue with the bootloader stuck at relocked might be the result of relocking the phone with a custom recovery still installed. Stock recovery is needed to unlock the bootloader. Normally this issue can be solved by flashing the same version firmware.zip (3.63.61.1) in ruu mode which will rewrite stock recovery and then enable the phone to be unlocked again. Problem: 1: you need to access ruu mode (which doesn't work) 2: You need the 3.63.31.1 stock firmware.zip (which i can't find on the usual hosting websites).
Click to expand...
Click to collapse
Thanks for looking, I appreciate it. What sites do you use so I can keep an eye on it in the future? I handed it back to him yesterday as a write off and he doesn't seem to care having bought a Nexus 6 recently; with that in mind I might buy it off him with the look to fixing it at a later point.
Thanks again, appreciate your help and advice.

HTC One m7 sprint Bricked??

Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(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: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(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: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.

Soft bricked T-Mobile HTC One M7 no OS, no recovery, locked bootloader

Tried to go back to stock from another ROM, so relocked bootloader, then ran the latest T-Mobile RUU. The RUU failed and now I'm left with a useless phone. Help is appreciated.
EDIT: It also says "Security Warning" in the bootloader.
Wish39 said:
Tried to go back to stock from another ROM, so relocked bootloader, then ran the latest T-Mobile RUU. The RUU failed and now I'm left with a useless phone. Help is appreciated.
EDIT: It also says "Security Warning" in the bootloader.
Click to expand...
Click to collapse
What RUU did you flash (can you provide a link)? Can you post the output of
Code:
fastboot getvar all
Please remove your serial and imei numbers before posting.
Sent from my HTC One M9 using Tapatalk
Danny201281 said:
What RUU did you flash (can you provide a link)? Can you post the output of
Code:
fastboot getvar all
Please remove your serial and imei numbers before posting.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Got the RUU here: http://www.htc.com/us/support/htc-one-t-mobile/news/
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Wish39 said:
Got the RUU here: http://www.htc.com/us/support/htc-one-t-mobile/news/
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
OK so it's definitely the correct ruu, did you relock your bootloader before flashing it? I just read back and see you did relock bootloader.
What was the error message when it failed?
Sent from my HTC One M9 using Tapatalk
Danny201281 said:
OK so it's definitely the correct ruu, did you relock your bootloader before flashing it? I just read back and see you did relock bootloader.
What was the error message when it failed?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I get Error 155: Unknown error
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Wish39 said:
I get Error 155: Unknown error
Click to expand...
Click to collapse
Error 155 normally is caused by flashing with s-on and unlocked or trying to downgrade firmware with s-on.
It could be due to some outside interference. If you have HTCsync installed it's a good idea to uninstall it.
When you launched the ruu was the device in the bootloader connected with fastbootusb?
What version of windows are you using?
Do you have the latest HTC drivers installed?
https://www.dropbox.com/s/j92rdbh4k2phce4/HTC-Mobile-Driver-v4.17.0.001.zip?dl=0
Sent from my HTC One M9 using Tapatalk
fireball0093 said:
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Click to expand...
Click to collapse
Ok so to be sure, I did the whole HTCDev process again. Then I dropped the new .bin file into the fastboot folder, opened up adb, and connected the phone when it was in fastboot mode. I ran fastboot flash unlocktoken Unlock_code.bin only for it to fail ("data transfer failed" it said) and the bootloader froze. What is wrong here?
Wish39 said:
Ok so to be sure, I did the whole HTCDev process again. Then I dropped the new .bin file into the fastboot folder, opened up adb, and connected the phone when it was in fastboot mode. I ran fastboot flash unlocktoken Unlock_code.bin only for it to fail ("data transfer failed" it said) and the bootloader froze. What is wrong here?
Click to expand...
Click to collapse
Hmm. Let me quick boot into my bootloader to quick check something. Did you use the volume buttons to select Fastboot in the bootloader? Also I always run fastboot devices just to make sure it's connected, that may have been an issue. I know it might sound redundant but maybe switch the USB port and change the cord if you have a spare one. I have one that acts up from time to time
Edit:
Did you use the ADB prompt or the Fastboot prompt?
Danny201281 said:
Error 155 normally is caused by flashing with s-on and unlocked or trying to downgrade firmware with s-on.
It could be due to some outside interference. If you have HTCsync installed it's a good idea to uninstall it.
When you launched the ruu was the device in the bootloader connected with fastbootusb?
What version of windows are you using?
Do you have the latest HTC drivers installed?
https://www.dropbox.com/s/j92rdbh4k2phce4/HTC-Mobile-Driver-v4.17.0.001.zip?dl=0
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
HTC Sync Manager is uninstalled.
Yes the phone was connected via fastboot when I ran the RUU.
I am using Windows 10.
I just installed the drivers provided by you, so lets see if this works...
fireball0093 said:
Hmm. Let me quick boot into my bootloader to quick check something. Did you use the volume buttons to select Fastboot in the bootloader? Also I always run fastboot devices just to make sure it's connected, that may have been an issue. I know it might sound redundant but maybe switch the USB port and change the cord if you have a spare one. I have one that acts up from time to time
Edit:
Did you use the ADB prompt or the Fastboot prompt?
Click to expand...
Click to collapse
I used Minimal ADB and Fastboot to do this, and I know it works because I used it to unlock the bootloader on my phone. Only this time it can't send the file to the phone.
And yes I selected "Fastboot" in the bootloader menu and when I plug it into the computer it says "Fastboot USB" on the screen.
Wish39 said:
HTC Sync Manager is uninstalled.
Yes the phone was connected via fastboot when I ran the RUU.
I am using Windows 10.
I just installed the drivers provided by you, so lets see if this works...
Click to expand...
Click to collapse
:fingers-crossed: everything seems to be in place. It should flash
Sent from my HTC One M9 using Tapatalk
fireball0093 said:
If you still have the Unlock_code.bin file that HTC sent you for unlocking the bootloader, flash that again in Fastboot and then install a custom recovery after that process is done, and finally flash a custom ROM to at least get it working again. If you don't have the file then follow the steps on htcdev.com That's my advice that I can give, hopefully it can help
Edit:
I bet the command to flash it would help too, my apologies. It's fastboot flash unlocktoken Unlock_code.bin This is also all assuming that you unlocked it through their dev website. If you didn't, then you probably can go through their dev site to unlock it again.
Click to expand...
Click to collapse
Keeps on failing everytime I try to unlock the bootloader
It says something like (data transfer failure-too many links) or whatever.
Wish39 said:
Keeps on failing everytime I try to unlock the bootloader
It says something like (data transfer failure-too many links) or whatever.
Click to expand...
Click to collapse
I took a look at some other threads with people getting that error and they all said they simply switched USB ports, or if you have USB 3.0 to switch it to USB 2.0
fireball0093 said:
I took a look at some other threads with people getting that error and they all said they simply switched USB ports, or if you have USB 3.0 to switch it to USB 2.0
Click to expand...
Click to collapse
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Wish39 said:
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Click to expand...
Click to collapse
Glad it worked!
Wish39 said:
Dude! Thanks! I just plugged the phone into the back USB ports on my PC and it successfully unlocked the phone's bootloader! Thanks!
Although that means my PC's front USB ports are screwed up...
Click to expand...
Click to collapse
This would also explain the error with your ruu. Should have thought to mention about usb ports.
Your front ports are probably USB1.0 either that or connected to the mainboard through some type of hub. Both will cause problems with fastboot.
Sent from my SM-T230 using Tapatalk

Categories

Resources