Database Develop

[Q] HTC One M7 firmware help!

Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!

When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?

aooga said:
When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?
Click to expand...
Click to collapse
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.

olimoh8464 said:
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.
Click to expand...
Click to collapse
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...

Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?

olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
... run it from desktop while phone in bootloader. no need to run boot image ...

olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
RUU must match your CID number.
I add you here link to a good thread:
http://forum.xda-developers.com/showthread.php?t=2358738
tetakpatalked from Nexus 7 flo

Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk

Thank you for the advice and the link! I will go try this now and let you know how I get on!

aooga said:
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
... did i say something different than what you are saying ...

@aooga Angel's point was S-On, I think.
tetakpatalked from the legendary i9000

olimoh8464 said:
Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!
Click to expand...
Click to collapse
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app

Devilish_Angel said:
... did i say something different than what you are saying ...
Click to expand...
Click to collapse
Uh..yeah. You said:
when bootloader is unlocked and phone s-on, no ruu will work
Click to expand...
Click to collapse

bored_stupid said:
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?

olimoh8464 said:
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?
Click to expand...
Click to collapse
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C:\Users\milo\Desktop\Newest>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(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: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

OMG My phone literally did the same exact thing today!! I woke up, a few things were force closing so I decided that I would just reboot the phone...... Big mistake, once I did that, the phone just stayed in the booting up animation. So I figured hey what ever ill just reflash the ROM in TWRP.......Nope, couldn't boot into recovery either, the phone would flash the TWRP screen then just reset itself. Again, I thought no biggie ill just reinstall TWRP. This (again) proved to be useless, after multiple (successful) install's the phone still refused to boot into TWRP. So I finally got CWM to install, a noticed a few things at the bottom of the screen about something not being mounted properly, I didn't pay that much attention to it, i just wanted my phone back at that point. I tried to wipe my phone for a fresh flash, but as soon as the wipe began the phone reset itself. At this point I was on the brink of throwing this thing into the torrential down-pour that god decided to place in my city.
Next I tried to install Viper ROM because I knew it had a wipe functionality built into it's Aroma installer. Went through all the checklists got to the start install screen, clicked next, and then began to wipe......... and then reset again........
So finally I got TWRP reinstalled, and go install a fresh ROM and and immediately met with a screen full of : "Unable to Mount XXXXXXX" (Picture attached). So then I figure alright well my last resort has to be to use a RUU. Found this nice little thread (http://forum.xda-developers.com/showthread.php?t=2316726) and decided to use the FUU (4.19.401.11 Full Wipe). Unfortunately all that did was move my HBoot from 1.4 (or something like that) to 1.5 (or something like that), put the tamper flag back, and bring back the annoying red text at the bottom of the phone at boot (the thing about development build, blah blah blah). I reinstalled TWRP yet again hoping for the best, but still nothing. It cant seem to mount anything (what ever that means).
So now im here, stuck using my old One X. Any suggestions or answers or criticism would be very much appreciated.
Thank you!!!!!

olimoh8464 said:
C:\Users\milo\Desktop\Newest>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(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: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks

olimoh8464 said:
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks
Click to expand...
Click to collapse
Did you check the MD5
4961fdbbadba53c9640f3638f56faec1
When you say nothing happens.. Doesn't it even try to run?
Sent from my HTC One using XDA Premium 4 mobile app

HTC One Unresponsive Need Advice

I have a Tmobile HTC One M7. It was awesome! However, I wanted to root it. So I successfully unlocked the bootloader, installed TWRP and then proceeded to attempt to root. Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it, none of which worked and I have lost track of what I did in the process of trying to root and then subsequently trying to fix. I know there were some wipe cache, wipe dalvik cache, install zip from SD, I may have even tried to flash a custom ROM without the thing being rooted. I have been reading for days, trying this, trying that to no avail. The phone is brand new, without a scratch. It will power up like normal, but when it gets to the lock screen where you swipe the little lock in the bottom tray to use the phone it will not respond at all! It recognizes the network because it is displayed in the notifications bar up top, it can see the signal strength, it knows what time it is, it knows what the date is, but it will not get past the damn lock screen. ADB sideload works. I was able to push a zip and flashed it, even said android is upgrading when I rebooted, but it did not solve my problem. It will not power off, but when I hold the power button down, to turn it off the back arrow < and home symbol flash and after about 10 seconds a dialog box pops up that says to restart your phone continue to press and hold the power button and starts a countdown. Once the countdown gets to zero it restarts. If I hold the volume down button while doing this it will go into the boatloader and I can get into recovery. Apparently there is no backup to restore because when I try a restore I get the same exact same thing. I thought I had done one, I must have erased it somehow. I have been trying to resolve this for weeks now and am at my wits end. Any suggestions please !?!? Otherwise this things going in the trash.

pbyers said:
I have a Tmobile HTC One M7.
Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it,
Any suggestions please !?!? Otherwise this things going in the trash.
Click to expand...
Click to collapse
1- relax
2- try and remember what went wrong... you could check your downloads to see what things you downloaded, maybe that will help you remember
3- what recovery do you have (name and version number)
4- post a "fastboot getvar all" (excluding IMEI and s/n)
if need be: Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)

nkk71 said:
1- relax
2- try and remember what went wrong... you could check your downloads to see what things you downloaded, maybe that will help you remember
3- what recovery do you have (name and version number)
4- post a "fastboot getvar all" (excluding IMEI and s/n)
if need be: Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
Click to expand...
Click to collapse
I don't know what posting a "fastboot getvar all" means. I am a complete newbie! I can get to the bootloader with no problem. It's been weeks since I fouled this thing up and do not know how to check my downloads. I have TWRP recovery. Not sure which name and number, will check when I get home. Will RUU help me?

pbyers said:
I don't know what posting a "fastboot getvar all" means. I am a complete newbie! I can get to the bootloader with no problem. It's been weeks since I fouled this thing up and do not know how to check my downloads. I have TWRP recovery. Not sure which name and number, will check when I get home. Will RUU help me?
Click to expand...
Click to collapse
1 - relax
2 - slow down. don't try ten things in a row.
3- search and read.
4- you have a perfectly good $500 phone so before you throw it in the trash PM me I'll take it and even pay for shipping
5- it really sounds like you are very close to a working phone but you are just a little impatient and inexperienced (see items 1 2 and 3)
6- don't RUU *yet* until you've checked to see if something simpler will do.
Look, if you already put TWRP on there, you probably had fastboot working on your computer at some point. You're going to need fastboot to fix this. Running the command fastboot getvar all is not too hard for you to accomplish. Google how to do it and post the results (minus your personal info like serial number and IMEI) here.
PS quick clarification on terminology for HTC phones, root doesn't mean what you seem to think it means.
To get root permissions in the OS
You unlock the bootloader
That allows you to flash a custom recovery
Then in recovery you either
a) flash a ROM that is already "rooted"
or
b) flash a zip that "roots" your existing ROM
In the HTC world you do not "root" an entire phone, you only root a ROM.
Sent from my HTC One using XDA Free mobile app

NxNW said:
1 - relax
2 - slow down. don't try ten things in a row.
3- search and read.
4- you have a perfectly good $500 phone so before you throw it in the trash PM me I'll take it and even pay for shipping
5- it really sounds like you are very close to a working phone but you are just a little impatient and inexperienced (see items 1 2 and 3)
6- don't RUU *yet* until you've checked to see if something simpler will do.
Look, if you already put TWRP on there, you probably had fastboot working on your computer at some point. You're going to need fastboot to fix this. Running the command fastboot getvar all is not too hard for you to accomplish. Google how to do it and post the results (minus your personal info like serial number and IMEI) here.
PS quick clarification on terminology for HTC phones, root doesn't mean what you seem to think it means.
To get root permissions in the OS
You unlock the bootloader
That allows you to flash a custom recovery
Then in recovery you either
a) flash a ROM that is already "rooted"
or
b) flash a zip that "roots" your existing ROM
In the HTC world you do not "root" an entire phone, you only root a ROM.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
My results are below. Can you please help me if you can? It's killing me to not have my phone working. Thanks!
C:\Users\Paul\Desktop\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(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: 4110mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
C:\Users\Paul\Desktop\OneDrivers_Fastboot\Fastboot>

pbyers said:
My results are below. Can you please help me if you can? It's killing me to not have my phone working. Thanks!
C:\Users\Paul\Desktop\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(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: 4110mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
C:\Users\Paul\Desktop\OneDrivers_Fastboot\Fastboot>
Click to expand...
Click to collapse
Please lock your bootloader, reboot the phone in Bootloader mode (phone should show fastboot USB on your screen) and run this RUU. http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
If it fails, don't close RUU software, go to c:\ruulog\ruu****.log and paste the contents here.

SaHiLzZ said:
Please lock your bootloader, reboot the phone in Bootloader mode (phone should show fastboot USB on your screen) and run this RUU. http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
If it fails, don't close RUU software, go to c:\ruulog\ruu****.log and paste the contents here.
Click to expand...
Click to collapse
I will try this evening, thanks for your help. How do I run the RUU?
Thanks,
Paul

Thank You!!!
SaHiLzZ said:
Please lock your bootloader, reboot the phone in Bootloader mode (phone should show fastboot USB on your screen) and run this RUU. http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
If it fails, don't close RUU software, go to c:\ruulog\ruu****.log and paste the contents here.
Click to expand...
Click to collapse
You saved me! I cannot thank you enough!!!!!! I have a working HTC One now.

pbyers said:
You saved me! I cannot thank you enough!!!!!! I have a working HTC One now.
Click to expand...
Click to collapse
Then hit my thanks button
Also advance edit the first post to add [SOLVED]

SaHiLzZ said:
Then hit my thanks button
Also advance edit the first post to add [SOLVED]
Click to expand...
Click to collapse
I will gladly do it if I knew how, navigating this forum is proving challenging! Please forgive. I am new Just let me know how and I will.
Thanks!

[Q] M7 RUU failed stuck on RUU Boot

Hi, I bought a used m7 which was rooted and tried to return to stock. However the RUU installer failed and im now stuck with in bootloader which says TAMPERED and RELOCKED
here is fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXX
(bootloader) imei:
(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: 3887mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Can anyone tell me which ruu installer i should use or give any other suggestions?
Thanks

zirbenaum said:
Hi, I bought a used m7 which was rooted and tried to return to stock. However the RUU installer failed and im now stuck with in bootloader which says TAMPERED and RELOCKED
here is fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXX
(bootloader) imei:
(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: 3887mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Can anyone tell me which ruu installer i should use or give any other suggestions?
Thanks
Click to expand...
Click to collapse
do you know how to use adb and fastboot, also do you have drivers installed on your computer ?

Seanie280672 said:
do you know how to use adb and fastboot, also do you have drivers installed on your computer ?
Click to expand...
Click to collapse
yes i have drivers installed and i got the this info with fastboot. adb doesn't seem to recognize the phone though.

zirbenaum said:
yes i have drivers installed and i got the this info with fastboot. adb doesn't seem to recognize the phone though.
Click to expand...
Click to collapse
adb wont work in the bootloader, heres where the fun starts:
ADB commands only work in a booted rom or in a custom recovery, they don't work in the bootloader
Fastboot commands only work in the bootloader, they don't work in a booted rom or recovery.
phew.....glad we got that bit out of the way
first thing is first, can you start downloading this, its your reset rom file, but the servers are a little slow, that's why I say start, when its finished downloading, rename it to rom.zip for ease, and put it in the same folder on your computer where adb and fastboot files are please, heres the file: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
whilst that is downloading, you will need to goto HTC Dev and unlock your bootloader, just follow the instructions they give you, its a piece of cake, and as you already have adb and fastboot, you wont need to download the 3 files later on that they tell you to download: http://www.htcdev.com/bootloader/
your flags will then turn to UNLOCKED and TAMPERED, this is normal, nothing to worry about.
report back when done.

Seanie280672 said:
report back when done.
Click to expand...
Click to collapse
Ok i unlocked the bootloader and the phone booted! whew
Thank you so much!
It is till in rooted state tough but i guess it's better than bricked.

zirbenaum said:
Ok i unlocked the bootloader and the phone booted! whew
Thank you so much!
It is till in rooted state tough but i guess it's better than bricked.
Click to expand...
Click to collapse
the phone booted ? lol, that's strange, we're not finished yet lol, strange that it didn't boot whilst relocked but booted whilst unlocked.

Seanie280672 said:
the phone booted ? lol, that's strange, we're not finished yet lol, strange that it didn't boot whilst relocked but booted whilst unlocked.
Click to expand...
Click to collapse
Well I am not complaining The download takes more than two hours. What should i do after it is done?

zirbenaum said:
Well I am not complaining The download takes more than two hours. What should i do after it is done?
Click to expand...
Click to collapse
you could try one of the alternative links on that site, however, if your happy with your phone the way it is now then you wont need that file.
just scroll down the page a little and theres 2 alternative download links.

the ksn
Seanie280672 said:
you could try one of the alternative links on that site, however, if your happy with your phone the way it is now then you wont need that file.
just scroll down the page a little and theres 2 alternative download links.
Click to expand...
Click to collapse
I was hoping to get it in vanilla state but after this nightmare maybe it is better to leave it as it is until ive done some more research

zirbenaum said:
I was hoping to get it in vanilla state but after this nightmare maybe it is better to leave it as it is until ive done some more research
Click to expand...
Click to collapse
whats vanilla state ?, sorry im not familiar with that term, guess we can both teach each other something here

shall
Seanie280672 said:
whats vanilla state ?, sorry im not familiar with that term, guess we can both teach each other something here
Click to expand...
Click to collapse
Its software that is not customized. Wikipedia says:
Computer software, and sometimes also other computing-related systems like computer hardware or algorithms, is called Vanilla when not customized from its original form, meaning that it is used without any customizations or updates applied to it.
http://en.wikipedia.org/wiki/Vanilla_software
Maybe actual vanilla would be stock android without any htc customizatios though.

zirbenaum said:
Its software that is not customized. Wikipedia says:
Computer software, and sometimes also other computing-related systems like computer hardware or algorithms, is called Vanilla when not customized from its original form, meaning that it is used without any customizations or updates applied to it.
http://en.wikipedia.org/wiki/Vanilla_software
Maybe actual vanilla would be stock android without any htc customizatios though.
Click to expand...
Click to collapse
ahh I see, now that's where we were heading originally, to get pure stock rom you will need to download that file I linked you too earlier, and as your phone is booting now, just copy the file to your internal storage not into the adb and fastboot folder.
i'll tell you what to do next if you want to proceed.

Seanie280672 said:
ahh I see, now that's where we were heading originally, to get pure stock rom you will need to download that file I linked you too earlier, and as your phone is booting now, just copy the file to your internal storage not into the adb and fastboot folder.
i'll tell you what to do next if you want to proceed.
Click to expand...
Click to collapse
well the download is going to take forever and it is already 1 am here so maybe i have to do this some other time. But you can give the instuction and i'll do this later.
You have been very helpful, thank you again.

zirbenaum said:
well the download is going to take forever and it is already 1 am here so maybe i have to do this some other time. But you can give the instuction and i'll do this later.
You have been very helpful, thank you again.
Click to expand...
Click to collapse
when the file has finished downloading, check the MD5 and file size before copying it to your phone, just to make sure its not corrupt.
then what you will have to do, is copy that file you are downloading to your internal storage, then reboot your phone to the bootloader and plug it into the computer,. make sure it says fastboot usb on the screen.
then download this file: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
and put it in the same folder as adb and fastboot on your computer, open a command window (CMD) in that folder by holding control + shift + right mouse click in any white area of that folder and select open a command window here, then type the following commands one at a time, wait for each command to finish before issuing the next.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
once that is done, unplug your phone and enter recovery using the volume buttons to navigate and the power button to select.
when in recovery goto wipe and just swipe to factory reset, do not advanced wipe.
when done, goto install and in the list it gives you, select the file you downloaded and copied to your internal storage, swipe to begin the install, follow the instructions, and when it gives you the options, select yes wipe data, yes install stock radio and yes install stock recovery.
once installation is complete, it will ask you to reboot, when you select reboot, if the screen goes black (this doesn't always happen, most times it reboots without any problems), just hold down the power button until the lights on the bottom flash 10 to 15 times and then the phone will boot to full stock rom with OTA ability.
I know this sounds long and confusing, but you will see as you go along its easy, just don't skip any steps.
if you have any problems, just report back here, but if you follow my instructions it should run like clockwork.

Download official ruu from here http://www.htc1guru.com/downloads/ruu-file-downloads/ check the CID ... CID codes are given vit RUU .yrs is HTC_Y13 So try yur cid supported ruu. bootloader must b locked.

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

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.