[Q] HTC One Soft-Brick, Bootloader Relocked. - One (M7) Q&A, Help & Troubleshooting

Hi everybody from XDA, first time posting here !
Let me explain the problem I have :
Two days ago, my HTC One was booting on Android 4.3, I was on a ROM Stock from ORANGE, with root access, recovery by TWRP on...
And then it started to crash when booting, didn't knew why ! So I tried to flash another ROM on my device (Android_Revolution_HD-One_53.0) Android 4.4.2 with Sense 6.0, but I locked the bootloader before booting on the ROM. I have now a scary message on my bootloader :
*** RELOCKED ***
**** Security Warning !*****
Click to expand...
Click to collapse
I tried to unlock my bootloader via htcdev.com, but everytime I have that message :
sending 'unlocktoken' <0 KB>... FAILED <status read failed <Too many links>>
Click to expand...
Click to collapse
I don't know how to resolve that problem, please, anybody, may you help me ?
I give you my device specification down there :
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4D.18.3250.18
version-cpld: None
version-microp: None
version-main: 2.24.73.8
version-misc: PVT SHIP S-ON
serialno: HT37TW908613
imei: <HIDDEN>
meid: <HIDDEN>
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG202
battery-status: good
battery-voltage: 4296mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d959c75800
hbootpreupdate: 11
gencheckpt: 0
Done!
Thank you for everybody reading this post
KoxinHell

KoxinHell said:
Hi everybody from XDA, first time posting here !
Let me explain the problem I have :
Two days ago, my HTC One was booting on Android 4.3, I was on a ROM Stock from ORANGE, with root access, recovery by TWRP on...
And then it started to crash when booting, didn't knew why ! So I tried to flash another ROM on my device (Android_Revolution_HD-One_53.0) Android 4.4.2 with Sense 6.0, but I locked the bootloader before booting on the ROM. I have now a scary message on my bootloader :
I tried to unlock my bootloader via htcdev.com, but everytime I have that message :
I don't know how to resolve that problem, please, anybody, may you help me ?
I give you my device specification down there :
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4D.18.3250.18
version-cpld: None
version-microp: None
version-main: 2.24.73.8
version-misc: PVT SHIP S-ON
serialno: HT37TW908613
imei: <HIDDEN>
meid: <HIDDEN>
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG202
battery-status: good
battery-voltage: 4296mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d959c75800
hbootpreupdate: 11
gencheckpt: 0
Done!
Thank you for everybody reading this post
KoxinHell
Click to expand...
Click to collapse
Power off the phone manually and try it again?
If it doesn't work, try to gain S-OFF using firewater temproot, and then you can unlock bootloader using ADB commands, if your phone is S-OFF.

SaHiLzZ said:
Power off the phone manually and try it again?
If it doesn't work, try to gain S-OFF using firewater temproot, and then you can unlock bootloader using ADB commands, if your phone is S-OFF.
Click to expand...
Click to collapse
I tried like 40 times to power off and doing it again, but it seems that the device is frozen... I still have the original unlock_code.bin sent by HTCDev by the way !
What do you think about that : If I flash my firmware by using fastboot oem rebootRUU, will it change the bootloader with a new firmware or am I wrong ?
Thanks for your attention
KoxinHell
Edit : I can use fastboot, but I can't use adb because the device is not recognized !

KoxinHell said:
And then it started to crash when booting, didn't knew why !
Click to expand...
Click to collapse
this could mean hardware failure...
however, please generate a new unlock code using htc dev, try different computer, cable, usb port, etc.

I had the same problem and I followed this tutorial I fix my problem tried
http://forum.xda-developers.com/showthread.php?t=2475914
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked

My device is S-ON and I can't use adb options ! I can only use Fastboot !

Why you can only use Fastboot? Whether S-ON or S-OFF shouldn't be important for ADB.

When I use "adb devices" my devices is not recognized ! But when I do : "fastboot devices" my device is shown !

For adb your phone needs to be booted to android or recovery. If your phone is turned off or in a bootloop, adb won't work

donkeykong1 said:
For adb your phone needs to be booted to android or recovery. If your phone is turned off or in a bootloop, adb won't work
Click to expand...
Click to collapse
Yes I arleady know that ^^ But I can't boot on android or recovery, I can access only to the bootloader ! So adb doesn't works..

I had that <too many links> error, but simple comand repeat always worked for me. So, you could try it yourself. When it gives you the error, just do fastboot flash command again and see what happens

When I send the command :
fastboot flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
I could wait for hours and hours, because when I unplug my device, the error "too many links" appears !

/UP\ I flashed my firmware last night, I can now access to the recovery, but as I did a factory reset, there isn't any recovery on the device now, my phone can boot aswell, but same as recovery,My bootloader is still ***RELOCKED***. I don't have any ROM installed on ! When I try to flash a recovery, I have a (error signature verify fail)...
I'm waiting for any suggestions !
KoxinHell

You can't flash a recovery without the bootloader unlocked. Did you get another token from the htcdev site
Sent from my HTC One using XDA Premium 4 mobile app

nateboi81 said:
You can't flash a recovery without the bootloader unlocked. Did you get another token from the htcdev site
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In fact, I tried a lot of time to get a new token from htcdev, is it wrong ?

Related

[Q] Help! Stuck at bootscreen with no ROM... Bricked?

Hi,
Ive got a HTC One here with the problem mentioned in the title. The phone is completely stock, locked bootloader, not rooted, S-ON.
The phone does not get past the HTC screen at all, it stays there for a few seconds and turns off. I can get into the bootloader, but cannot get adb to work. However fastboot is working fine.
Ive tried to unlock the bootloader so that I can try to get a custom recovery and install a ROM that way, but everytime I try to unlock it it restarts and gets stuck again. Comes up as locked once back into the bootloader.
Tried flashing an RUU, but the ones Ive tried bring up a singature failed error, I assume due to the locked bootloader.
Searched, looked, and read through many threads/posts for the past few hours and I cant find anything to help me.
This is what getvar all brings up...
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Please help! Im stuck...just like my phone is!
Install custom recovery
Then you have 2 options
ADB sideload
USB otg both work good
I recommend twrp recovery
Then connect usb then Mount usb with custom Rom in it flash your Rom
Otherwise if you have ruu exe file with same version 3.62.401.1 in your getvar you can install in fastboot mod
HTC One 1.56 S-Off MaximusHD 33
selim97 said:
Hi,
Ive got a HTC One here with the problem mentioned in the title. The phone is completely stock, locked bootloader, not rooted, S-ON.
The phone does not get past the HTC screen at all, it stays there for a few seconds and turns off. I can get into the bootloader, but cannot get adb to work. However fastboot is working fine.
Ive tried to unlock the bootloader so that I can try to get a custom recovery and install a ROM that way, but everytime I try to unlock it it restarts and gets stuck again. Comes up as locked once back into the bootloader.
Tried flashing an RUU, but the ones Ive tried bring up a singature failed error, I assume due to the locked bootloader.
Searched, looked, and read through many threads/posts for the past few hours and I cant find anything to help me.
This is what getvar all brings up...
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4320mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Please help! Im stuck...just like my phone is![/QUOTE
What RUU did you try. Link please
With S-On you can flash RUU same version or higher, it will not allow you to flash RUU lower version
Have you tried a hard reset from within the bootloader or fastboot erase cache or the bright light trick. If that fails are you still within warranty, if so send it in for service.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
One of the RUU was an older version, that didnt work for obvious reasons. I then found one for the same version I have but it was called Guru Reset, so I think it may have been slightly modified, that didnt work either.
I have already tried the suggestions you mentioned but its not working. Anything I select from within the bootloader just reboots the phone over again, except fastboot.
I have just found and flashed a newer version of the RUU exe at http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
This seemed to be working, it even said it was complete. But the phone did not reboot itself, I switched it on, and ran into the same problem. Tried erasing cache, again nothing. Tried manually flashing the zip, but I get an error about data length is too large. No idea what is going wrong here.
Unfortunately no warranty.
This is what getvar brings up after the flash...
Code:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.19.401.9
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4282mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
Im desperate to get this fixed! Please help!
Bootloader ? Locked or unlocked ?
Unlock bootloader with HTCdev
Flash custom recovery
Flash guru reset
HTC One 1.56 S-Off MaximusHD 33
yatin kumar said:
Bootloader ? Locked or unlocked ?
Unlock bootloader with HTCdev
Flash custom recovery
Flash guru reset
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
Bootloader is locked, cannot be unlocked as mentioned in first post. The phone just reboots itself after I select yes to unlock bootloader.
What can be done?
selim97 said:
Bootloader is locked, cannot be unlocked as mentioned in first post. The phone just reboots itself after I select yes to unlock bootloader.
What can be done?
Click to expand...
Click to collapse
try firewater s off 2nd method
It supports many HTC phone
HTC One 1.56 S-Off MaximusHD 33
yatin kumar said:
try firewater s off 2nd method
It supports many HTC phone
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
Thanks for the input... but that unfortunately wont work either because adb is not working for me, I can only get fastboot to work.
Any other suggestions?
Phone is dead. Throw it away.
SaHiLzZ said:
Phone is dead. Throw it away.
Click to expand...
Click to collapse
Really!? No possible way around this then??
The phone may not be dead, but he combination of locked bootloader and S-ON may be too much. You really need to fix one or the other somehow..
Try the download from here and check MD5 once downloaded
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
How did you try to install the zip manually. Post links and steps please.
PS. adb will only work in booted os or recovery.
Sent from my Nexus 7 using XDA Premium HD app
selim97 said:
Thanks for the input... but that unfortunately wont work either because adb is not working for me, I can only get fastboot to work.
Any other suggestions?
Click to expand...
Click to collapse
I don't really know about this but try search flashing Rom in fastboot
But it not gonna work as s on
Last way service center with paying
HTC One 1.56 S-Off MaximusHD 33
bored_stupid said:
Try the download from here and check MD5 once downloaded
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
How did you try to install the zip manually. Post links and steps please.
PS. adb will only work in booted os or recovery.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That one seems to have the same MD5 as the one Ive already tried...but no worries I am downloading it right now and will give it a go. Willing to try anything to get it back to life!
I extracted the zip and tried flashing using this guide http://forum.xda-developers.com/showthread.php?t=2497614
I get an error saying the data length is too large, no idea what that means.
Thanks for the help so far, if you have any other ideas/suggestions please do let me know.
NxNW said:
The phone may not be dead, but he combination of locked bootloader and S-ON may be too much. You really need to fix one or the other somehow..
Click to expand...
Click to collapse
I know
When I tried unlocking the bootloader it went through to the phone and came up allowing me to select yes or no, but as soon as I press the power button to confirm my selection thats it back to a bootloop.
Try flashing the rom.zip again only this time, try this
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip. (yes twice).
Rename rom.zip to name of the file name.
Sent from my Nexus 7 using XDA Premium HD app
bored_stupid said:
Try flashing the rom.zip again only this time, try this
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip. (yes twice).
Rename rom.zip to name of the file name.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Hi,
Downloaded RUU from the link you provided, MD5 matched. Ran the RUU, but same problem of not being able to boot up.
Followed your instructions on flashing the rom.zip, but I get the same error of data length is too large.
I noticed on the guru website something about encrypted and decrypted zips, maybe the zip needs additional steps before being flashed, maybe thats why Im getting the errors with the zip?
Because you are S-On the RUU needs to be signed
You cannot flash an unsigned RUU
It also needs to be specifically for your phone.
Sent from my Nexus 7 using XDA Premium HD app

[Q] Help M7 stuck in fastboot

Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>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: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.
thintin said:
Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>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: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.
Click to expand...
Click to collapse
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.
Seanie280672 said:
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.
Click to expand...
Click to collapse
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Click to expand...
Click to collapse
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l
thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Click to expand...
Click to collapse
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l
Click to expand...
Click to collapse
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.
Seanie280672 said:
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.
Click to expand...
Click to collapse
Sure, I appreciate your help with this
<<<< Identifier Token Start >>>>
5A5F19A2F517CC2BEA0DDADB1C3924C7
FA7846F59B3E38FC5897B053899BA233
824B607DDBDD9CE31E453E48CBE4EF5C
8ECD29487C09FE311D30DA91386C56C5
FF130E636BA23977B05905925EB17FC6
3EBBCC1BFCB2383B1A7DAFDCBFBE0AA7
8DA65BF8F702E6F44F24743AFA8573EB
AE8D23E995EED6E7CBC5981CEBBAFC66
694176C863DB9858CC535ED2D3EC609C
043196ED2CDF60AC13DEBBB636AA348E
E748366B4CA16747C0593C363D6B98E2
81C2699B2D1D979E7ACAC97D4187788E
85AEA5F27B48A9F8278A0B49D0D3838B
92E2EDFE6B16EEEDE98F322D92294ED0
E43D1945184BBF8A0CB9661B92CB9E38
040AAF8857A0FC1A4C7682ACF8120340
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
I'm s-on BTW in case that makes a difference; never been s-off.
thintin said:
Sure, I appreciate your help with this
I'm s-on BTW in case that makes a difference; never been s-off.
Click to expand...
Click to collapse
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?
Seanie280672 said:
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?
Click to expand...
Click to collapse
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?
thintin said:
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?
Click to expand...
Click to collapse
yes defiantly, download the attachment and click the link on the email to continue the instructions.
Seanie280672 said:
yes defiantly, download the attachment and click the link on the email to continue the instructions.
Click to expand...
Click to collapse
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.
thintin said:
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.
Click to expand...
Click to collapse
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?
Seanie280672 said:
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?
Click to expand...
Click to collapse
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1
thintin said:
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1
Click to expand...
Click to collapse
ok good, also could you post a link to the O2 RUU you downloaded earlier
Seanie280672 said:
ok good, also could you post a link to the O2 RUU you downloaded earlier
Click to expand...
Click to collapse
GRRR!
Following firewater instructions...
adb reboot <–important!!!!
Click to expand...
Click to collapse
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
adb wait-for-device push firewater /data/local/tmp
Click to expand...
Click to collapse
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.
thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.
Click to expand...
Click to collapse
try this version of adb and fastboot instead, sounds like its out of date and also check your device manager, make sure it says MyHTC when your phone is plugged in: http://forum.xda-developers.com/showthread.php?t=2588979
thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
Click to expand...
Click to collapse
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.
majmoz said:
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.
Click to expand...
Click to collapse
Don't worry, I didn't type the important! bit
I'm not sure how much more time I want to spend trying to reset this device, maybe I'll just return it to O2 as it is and see if they even care that it's been unlocked!
I'll try the link you suggested and report back :tired:
Hi.
I think my guardian angel must have had a hand in this because I was only trying to reset the phone to return it due to the microphone not working. After all of these failed attempts I factory reset the current rom and bingo! Microphone working again and no need to return to O2
But thanks for all of the help you offered, I would have a lot less hair and more wrinkles without you.

HTC one M7 continuously reboots till battery drains

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

[Q] M7 softbrick (or not?) - help needed!

Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(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.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance for any good advice!!
tormagj said:
I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision
Click to expand...
Click to collapse
Its 7.19.401.22
nor the reason for the update
Click to expand...
Click to collapse
bug fixes
but just followed my usual steps.
Click to expand...
Click to collapse
Won't work for this ota, you must be 100% stock.
Thanks in advance for any good advice!![
Click to expand...
Click to collapse
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
alray said:
Its 7.19.401.22
flash the 7.19.401.22 ruu, it will update and fix your phone.
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
Click to expand...
Click to collapse
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two
unbricked htc one m7
tormagj said:
Hi guys!
I've been trying to get my dear One M7 alive now for 4-5 evenings. Really thought it was bricked for good, but finally made some progress. Here's what happened:
S-OFF, rooted since always but on stock/OTA from HTC. Been updating through OTAs just flashing back stock recovery before update and then switching back. I've been using CWM. I was already on the Lollipop 5.0.2 with Sense 6.0 (sofware revision 7.19.401.2) but received another minor OTA couple of weeks ago. Didn't make note of the new revision, nor the reason for the update but just followed my usual steps. Everything seemed to go as usual, but once booting back up after the update the phone got stock on the boot animation (the htc one w/beats audio just after the sound).
Immediately tried a restore from a backup I have, but continued in the same situation. Tried several/different wipes (even the data partition in the end), but no luck. Tried the best I could to search for info, but all I could find was what I'd already done. Tried to download some RUU's but the files seems corrupted and I cannot get it working. I tried to switch to TWRP, taking a new backup (of my restored, but still not working CWM-backup). Same situation. Then I tried to flash a Cyanogenmod version, and was close to giving up when it didn't work as well. Luckily I tried a couple of times more (perhaps after throwing the phone in the wall a few times) and just out of nowhere it suddenly booted and seems to be working normally. Full of hope I tried a restore again, but back to boot animation. Tried to download a clean stock install file I found on XDA with the same version as mine, but just get stuck again. Once I restore the Cyanogenmod backup, it boots perfectly.
Perhaps I am missing something obvious, but I've been doing these things for many years know (starting with the Desire @ nikez), and this just seems odd. I could seriously need some help to get it back working again as I like the stock Sense 6.0 with Lollipop.
For info some details (btw; I verified it against the data I noted just after my original Lollipop OTA early this year, and it is still identical, so i don't see any vitals have changed):
(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.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **removed**
(bootloader) imei: **removed**
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4081mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
**************************************************************************************************
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
tormagj said:
Thanks alot alray, I'll test it and report back if I manage to fix my beloved phone. I guess I didn't see that "second generation" in post two
Click to expand...
Click to collapse
@alray - that freaking worked like a charm! Thanks a lot, a donation is on it's way, really thought my beloved phone was gone.
Installed the RUU version 7.19.401.22 as indicated, and that did the trick. I got an error message about HBOOT while flashing it, tried it twice since I saw it mentioned in several threads but the message continued. However, the phone booted normally afterwards so I couldn't care less right now
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device XXXX.
Also tried desperately to restore the data partition from my cwm backup, but then the phone wouldn't boot again. Last resort now will be to manually restore some of the apps through Titanium from my cwm - but what the heck, lost data is better than lost phone.
Although a minor update, seems like HTC did some serious changes since a lot of the normal stuff doesn't work. Any idea of what??
Anyways, thanks again - really appreciated!
rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Hi @rakeshrinawa,
I should probably leave it to the pro's to help you out, but I would suggest the following (sure somebody will correct me if I'm on thin ice here):
- Boot into fastboot, open a command prompt and write "fastboot getvar all". Then you'll see the same variables that I posted above, amongst other the version of your software, your CID and some other information that might be useful for the guys helping.
- Look at the selection posted by @alray here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (either first or second post).
- You need to find the RUU that fits your phone (correct CID and version), and keep in mind the note in the top:
When you update you must go one step at a time. For example if you are on 6.xx.xxx.xx then you can flash 7.xx.xxx.xx . But if you are on 5.xx.xxx.xx then you cannot flash the 7.xx.xxx.xx you must first flash a 6..xx.xxx.xx.
Click to expand...
Click to collapse
- The trick is to find the right file, but I'm not the right guy to tell you which one. Once you have it, just follow the "How to flash" instructions step by step and hopefully you'll have an almost new phone again just like I had.
- I see your S-ON, so take note of the instructions saying you need to relock the bootloader (item 4 in How to flash). Or perhaps you could just as well S-OFF it ​
I am sure it's possible to solve your issue, keep on trying! Good luck!
rakeshrinawa said:
hello sir,
I have htc one m7 sprint manufactured in new zealand.The problem started when I by mistake deleted all the partitions like delvin cache,system,internal
storage,etc in the factory reset option of the bootloader.My phone has unlocked bootloader and latest twrp installed before the problem occurred and android
version 4.2 installed which i think has been deleted as it says when rebooting from the bootloader and it rebooted normally just stucks at hTC logo.
I have installed fastboot,adb(not working properly) by sdk tools on windows 7 32 bit pc and also htc sync manager and latest java.
I request you to reply me as soon as possible as i have just lost my all the patience doing all the methods suggested on the like fastboot,etc and
typing the commands.You are my last hope,please help me.
Htc one bootloader details are:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0315
OpenDSP-v26.120.274.020
eMMC-boot
May 8 2013,16:30:08:1
I have only basic knowledge of android tools and computer.
Thanks a lot for your time and i am waiting for your reply.
Click to expand...
Click to collapse
Relock your bootloader
Code:
fastboot oem lock
and flash the old sprint ruu:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
fastboot reboot
Then you should update your phone to latest version before unlocking the bootloader, flashing a custom recovery/rom (if you are planning to)
thanks for your reply dear
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
---------- Post added at 02:20 AM ---------- Previous post was at 02:07 AM ----------
[/COLOR @alray
I think i have the wrong version of twrp on my phone so adb sideload is not working and i just download your files and simply flash them and will they make my phone work even when i have performed format data and by factory reset in the bootloader?
rakeshrinawa said:
@alray
Actually this is the only info my bootloader is showing as I have formatted data in the factory reset option.The model no of the phone is PN072(SPRINT) and before this problem,ANdroid 4.2 was installed and now i have installed TWRP 2.6.3.0 and again formatted data and now adb sideload is not working,kindly suggest me the correct softwares which can make my htc one m7 work and do my normal things and can u send me step by step list of softwares to be installed like twrp and adb on my pc as i have 32bit windows 7 on my pc.
Thanks a lot for your reply dear friend and you guys are just amazingly helpful.Keep it on.
Click to expand...
Click to collapse
Step you need to do posted above
RUU also posted above
you'll also need adb / fastboot either by downloading the android sdk (SDK Tools only) or minimal adb and fastboot
Save the ruu in the same folder you have installed minimal adb and fastboot or if installed the android sdk, make sure the ruu is in \Android SDK Tools\platform-tools.
Start a command prompt: Start menu --> program --> minimal adb and fastboot --> minimal adb and fastboot.exe or if using the sdk, go to \Android SDK Tools\platform-tools hold shift and right click in the folder and select "start a cmd prompt here".
Reboot your phone in bootloader / fastboot usb mode (make sure "fastboot usb" is shown in red)
then type:
Code:
fastboot oem lock
fastboot reboot-bootloader
This will relock your bootloader, required to flash the ruu
Code:
fastboot oem rebootRUU
once rebooted in ruu mode (black screnn with silver htc logo):
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
First flash will report "flush image again immediately, so do the same command again:
Code:
fastboot flash zip ruu_m7_wls_jb_50_sprint_1.29.651.10.zip
Wait for the ruu to flash then when you see sucessful message:
Code:
fastboot reboot
HI
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks
rakeshrinawa said:
@alray
I have HTC ONE M7 sprint variant with model no.PN072 which supports both gsm and cdma and I Was not able to use wcdma or 3g mode when using Android version 4.2.
So keeping all these things,and spending 10 hours in downloaading your files,will they work on my htc and won't create future problems like in google updates etc?
---------- Post added at 05:53 AM ---------- Previous post was at 05:14 AM ----------
[/COLOR @alray
I am sorry to say that before I read your reply,I was actually following instructions from
http://forum.xda-developers.com/showthread.php?t=2503646
and so I have flashed the firmware 5.03.651.3 s-on which is of 39886 bytes and now my new details of bootloader are:
***TAMPERED***
***RELOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v26.120.274.0202
OS-5.03.651.3
eMMC-boot 2048MB
May 15 2014,16:31:22.1
and my fastboot getvar all details are:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 1.01.20.0515
version-cpld: None
version-microp: None
version-main: 5.03.651.3
version-misc: PVT SHIP S-ON
serialno: ***REMOVED***
imei: ***REMOVED***
meid: ***REMOVED***
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4262mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
AND when I downloaded the odex file mentioned by him in the 8c step,I got the error of
remote 12:signature verify failed
and tried then,but got the same error again.
My bootloader is still relocked.
now tell me what should I do?
Hope you bear my stubbornness and Reply.....
Thanks
Click to expand...
Click to collapse
flash the 5.03.651.3 ruu posted in that thread.
hi
alray said:
flash the 5.03.651.3 ruu posted in that thread.
Click to expand...
Click to collapse
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
What should I do now,Please help me,I am totally exhausted.
rakeshrinawa said:
I flashed it with fastboot and it says signature verify failed,tried again and got the same message.
Click to expand...
Click to collapse
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU
hello
alray said:
Its says signature verify fail because you are trying to flash a rom (stock odexed) using fastboot, you must flash this rom using a custom recovery which will require to unlock the bootloader again so the simplest is to keep your bootloader relocked and flash the RUU
Click to expand...
Click to collapse
****
ok then can you send me the link of ruu file i have to flash as adb is not working in my phone and I can unlock my bootloader if you have a solution after that.
waiting for your reply.
rakeshrinawa said:
****
ok then can you send me the link of ruu file i have to flash
Click to expand...
Click to collapse
lol I think we have some communication issues here :laugh:. The RUU is in the same thread you linked me at post #10. All sprint RUU are listed at the beginning of that thread (in the first few lines of the OP), you need the 5.03.651.3 RUU, download it and lauch it (double click, its an .exe file). Make sure your phone is in bootloader when you launch the ruu.

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.

Categories

Resources