Database Develop

[Q] Stuck on HBoot during Unroot

Hello,
Last week I rooted my HTC One and installed the Android Revolution HD ROM. Although I loved it, I needed to get back to stock ROM. I followed a YouTube video to unroot my mobile and now it's stuck on HBoot screen. I've tried various RUU and Recover.zip's but no go. Please help!!
Thank you in advance.
Details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W901515
(bootloader) imei: 354435054464524
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4014mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0

Which RUU did you try and how did it fail?
Your version-main is they key.

Stuck on HBoot during unrooting - HTC One
BenPope said:
Which RUU did you try and how did it fail?
Your version-main is they key.
Click to expand...
Click to collapse
Hello Ben,
Thank you for writing. I'd like you to know that I'm not very techie... This RUU 'RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16' failed, and these recoveries: 2013-03-30.16.15.27, and a few more. I've been looking for my One's version main (1.29.707.17) and don't seem to have any luck. Thank you for your assistance.
Is there anyway I could downgrade or install a custom ROM? Anything to bring One back to life....
Currently, One is stuck on this screen: **Tampered** **Relocked** **Security Warning*

You'll need twrp recovery to install this backup
http://bugsylawson.com/files/file/1841-m7-twrp-nandroid-backup-cid-htc-044-12970716/

Stuck on HBoot during unrooting - HTC One
BenPope said:
You'll need twrp recovery to install this backup
Started download. Thanks, Ben. Could you point me to a step-by-step article for this recovery please?
Also, when I click 'Recovery', the phone just reboots...
Click to expand...
Click to collapse

Look in the original development section for the twrp recovery thread?
Also try
fastboot erase cache
That should sort your recovery out.

Stuck on HBoot during unrooting - HTC One
BenPope said:
Look in the original development section for the twrp recovery thread?
Also try
fastboot erase cache
That should sort your recovery out.
Click to expand...
Click to collapse
Thank you, Ben. You give me hope!! I had almost given up
I'll try the recover and revert shortly. Thanks again!

Stuck on HBoot during unrooting - HTC One
mirali7 said:
Thank you, Ben. You give me hope!! I had almost given up
I'll try the recover and revert shortly. Thanks again!
Click to expand...
Click to collapse
Ben, bad news. I did a quick read on TWRP and ran these commands. It failed. Since I couldn't find a img file, I used a .win. Please tell if I made a mistake. (new in Android world...)
fastboot.exe erase cache
erasing 'cache'... OKAY [ 0.519s]
finished. total time: 0.520s
fastboot.exe flash recovery system.ext4.win
sending 'recovery' (932728 KB)... OKAY [104.691s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 174.315s

Flashing random files is probably a bad idea. You need stock recovery.

Stuck on HBoot during unrooting - HTC One
BenPope said:
Flashing random files is probably a bad idea. You need stock recovery.
Click to expand...
Click to collapse
How do I perform a stock recovery? Please assist

RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16 is a developer RUU .. Your device MID (PN0711000) and CID (HTC__038) suggest it's an asian device ..
try installing this and update via OTA .. and remember, do not install any RUU other than x.xx.709.x ..

Do s-off and flash the ruu, that will give you full stock
Sent from my HTC One™

Rocker19943 said:
Do s-off and flash the ruu, that will give you full stock
Sent from my HTC One™
Click to expand...
Click to collapse
Rocker, can I do a S-Off when I'm stuck on the **Tampered** **Relocked** **Warning Security** screen? How? Please assist.

mirali7 said:
Rocker, can I do a S-Off when I'm stuck on the **Tampered** **Relocked** **Warning Security** screen? How? Please assist.
Click to expand...
Click to collapse
Thank you, Shahriar. Will try the same and revert

S-off
mirali7 said:
Thank you, Shahriar. Will try the same and revert
Click to expand...
Click to collapse
You need S-off and then need to change your CID to 11111111. That's the super CID and then
you can flash any stock firmware.
CC

I had Warning Security screen, i didnt know the reason of it, but it disappeared after unlocking bootloader again, so now try to unlock it using htcdev binary and your phone will boot up normally! Then do your job, but if you want to lock it again, use revone

Rocker19943 said:
I had Warning Security screen, i didnt know the reason of it, but it disappeared after unlocking bootloader again, so now try to unlock it using htcdev binary and your phone will boot up normally! Then do your job, but if you want to lock it again, use revone
Click to expand...
Click to collapse
Rocker, I'm 2 weeks into Android and I'm unsure of how to unlock using HTC Binary. Can you point me to a helpful article please?

rhtzshahriar, I downloaded the RUU but am unable to run it. The exe just doesn't start up. I've tried double-clicks, from cmd, run-as administrator. Rebooted laptop as well. Please advice

mirali7 said:
rhtzshahriar, I downloaded the RUU but am unable to run it. The exe just doesn't start up. I've tried double-clicks, from cmd, run-as administrator. Rebooted laptop as well. Please advice
Click to expand...
Click to collapse
Hi, I've started to download the following files:
RUU_M7_U_JB_50_hTC_Asia_TW_1.20.709.101_Radio_4A.13.3227.06_10.27.1127.01_release_307831_signed_2_4.exe
PN07IMG_M7_U_JB_50_hTC_Asia_TW_1.29.709.4.zip
Please see the screenshots of my phone. I'm unable to write anything from fastboot. But fastboot can read\detect my phone (fastboot devices). Any assistance is highly appreciated.

cc999 said:
You need S-off and then need to change your CID to 11111111. That's the super CID and then
you can flash any stock firmware.
CC
Click to expand...
Click to collapse
Hi, I'm unable to S-Off the device. When I run adb push revone /data/local/tmp/ - I get "device not found" error. Please assist

Phone is soft bricked, attempts to fix haven't work

Yesterday, I attempted to install a new rom. I had been using CM11 nightlies up till this point, and after being annoyed about certain aspects of my phone not working. I wanted to try something new.
I found ViperOne, and went to install it, thinking that it'll be the standard, run-of-the-mill install with no problems to be had. After getting through the install procedure and attempting to reboot to system, my phone dropped me back off at the bootloader. Thinking that I had forgotten to wipe something, I went into the recovery, wiped data, dalvik cache, and the cache, and attempted the install again. Once again, my phone dropped me off at the bootloader.
I thought, maybe I had a bad download. Re-downloaded the rom, same result. "Oh, I'll just try something else then". I found a Google Play Edition rom for my device, and decided to try that. It got stuck in a bootloop. After some googling, I attempted wiping the data/cache/dalvik cache again hoping it would help. Nope, still stuck in bootloop.
At this point (and after having running into a very similiar situation before) I decided to go for broke. I did a full wipe of the phone, and sideloaded CM10.1.3 (only stable CM rom for this device afaik). As it was installing, I noticed an error. "Unable to mount /data". I've had this problem before, and the way I fixed it last time was to install and run a stock rom. At this point in time, I was also getting frustrated and decided to put the stock rom back on my phone so it would at least be functional.
I found a stock rom and installed it just fine. The phone didn't even get stuck in a bootloop either. However, once the phone had finally booted up, I found that the touchscreen was unresponsive. I remember having this issue the last time I tried to use a stock rom. After a little bit of research, I had found that the problem stems from installing the wrong version of the rom. It was suggested on one of the websites to put "fastboot getvar version-main" into adb to find out what version I needed. It returns "version-main: ".
It was at this point that I remembered that I had made a backup of my phone before I attempted rooting. After some searching around, I managed to find it. That being said, I have no idea what to do with it. The folder where I made the backup contains a handful of .win files and some md5 checksums.
Since then I have been attempting seemingly random RUU versions in hopes of stumbling across the right one. It's been 5 hours, and I haven't had any success.
I would greatly appreciate any and all help that can be provided. If you guys need additional information (I'm not sure what I should include), let me know. I know some of the more basic ADB commands and their functions, so bear with me if I ask some questions about how to do certain things.

Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all

BD619 said:
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
BTW I removed
serialno:
imei:
meid:

BD619 said:
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
Click to expand...
Click to collapse
I've tried several different RUU's, including the one's I could find here, and none of them have worked. Not sure if it really matters, but I attempted the 4.06.651.4 RUU earlier, but it failed.
BD619 said:
BTW I removed
serialno:
imei:
meid:
Click to expand...
Click to collapse
Why shouldn't those be shared? Are they considered sensitive information?

Ooops for got the link
http://forum.xda-developers.com/showthread.php?t=2503646
Yes they could be considered sensitive.

BD619 said:
Yes they could be considered sensitive.
Click to expand...
Click to collapse
I have no idea what those numbers represent. Why are important?

crazy-asian said:
I have no idea what those numbers represent. Why are important?
Click to expand...
Click to collapse
I have always been told not to include those...could be a way for someone to hack your device but that's just my guess.
http://en.wikipedia.org/wiki/Mobile_equipment_identifier

I had this happen to me also. Ends up i had to flash a new firmware on the phone and it booted right up. Also make sure you are using twrp recovery when you flash this rom. I used cwm and think that is where all my problems started. Hope ya get it worked out and may not be your problem but is exactly what happened to me and have i fixed it.

BD619 said:
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
I had tried all but one of those in that list. That one that I hadn't used yet appears to be working. Thank you so much for the help.

Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.

crazy-asian said:
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
Click to expand...
Click to collapse
I'm running BadSeed Sixth Sense
But it's all personal preference everyone will have a different opinion.

Fastboot, on the phone side, isn't connecting to my computer.

crazy-asian said:
Fastboot, on the phone side, isn't connecting to my computer.
Click to expand...
Click to collapse
Are you in bootloader?

BD619 said:
Are you in bootloader?
Click to expand...
Click to collapse
Yes, and it is in fastboot mode.

crazy-asian said:
Yes, and it is in fastboot mode.
Click to expand...
Click to collapse
When you type fastoot devices you don't get a response?

BD619 said:
When you type fastoot devices you don't get a response?
Click to expand...
Click to collapse
correct

crazy-asian said:
correct
Click to expand...
Click to collapse
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly

BD619 said:
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
Click to expand...
Click to collapse
Didn't solve the problem, phone still isn't in "fastboot USB"

crazy-asian said:
Didn't solve the problem
Click to expand...
Click to collapse
Try a different port(usb2 are best)
Try a different cable
Different PC
If you have android sdk setup try updating it.

[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 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.

help IMEI baseband unkown no network with hboot 1.54 S-ON

hi all, I have htc one m7 international CID : GOOGl001, and have unkown IMEI baseband also no network with hboot 1.54 s-on working 5.02 lollipop custom rom , rooted
I tried to s-off with rumrunner, but it tells me error and try to change the rom
i tried Android revolution and another rom but did not work,
so IF there is a way or custom rom that work with rumrunner please tell me, or if there a way to get the IME and baseband while S-on while be great waiting for the help

Can you please post the output of
Code:
fastboot getvar all
Please remove your serial number and IMEI before posting :good:
Unknown IMEI and Baseband is normally a hardware related problem. In some cases flashing an ruu or firmware package can fix it. But failing that it's most likely hardware.
Thing is the GPE bootloader is a tricky one. As your s-on you will need to re-lock your bootloader to flash an ruu. But the GPE has a bug that prevents unlocking again.
So it would be best to get s-off first if possible. After checking the getvar we can assess your options :good:
Sent from my HTC One M9 using Tapatalk

really very thankfull for you and your reply here the output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3880mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

konan2010 said:
really very thankfull for you and your reply here the output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3880mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
It's unlikely rumrunner will work with your firmware. But you can try it with this stock rom if you like https://www.androidfilehost.com/?fid=24407100847292669
Flash the stock rom with twrp then try s-off with rumrunner.
If it still doesn't work your only option will be Sunshine App to s-off but it cost $25 and I can't guarantee you'll be able to fix it with s-off. So I'll leave that decision with you.
Or you can relock the bootloader to flash an ruu with s-on. But again I can't guarantee it will solve the problem. And you won't be able to unlock your bootloader through normal means. Because of a bug with the GPE bootloader.
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
It's unlikely rumrunner will work with your firmware. But you can try it with this stock rom if you like https://www.androidfilehost.com/?fid=24407100847292669
Flash the stock rom with twrp then try s-off with rumrunner.
If it still doesn't work your only option will be Sunshine App to s-off but it cost $25 and I can't guarantee you'll be able to fix it with s-off. So I'll leave that decision with you.
Or you can relock the bootloader to flash an ruu with s-on. But again I can't guarantee it will solve the problem. And you won't be able to unlock your bootloader through normal means. Because of a bug with the GPE bootloader.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
thanks for your fast reply, I locked it and relocked and it worked ok with me, would you provide me with RUU work for my phone? and will give it a try and thanks again

konan2010 said:
thanks for your fast reply, I locked it and relocked and it worked ok with me, would you provide me with RUU work for my phone? and will give it a try and thanks again
Click to expand...
Click to collapse
Did you flash the stock rom before relocking the bootloader?
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
Did you flash the stock rom before relocking the bootloader?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
not yet I will download and try it when do it will tell you

i made full format, and format cashe ,and works fine and now when using rumruner, it worked further step than other rom but give me the following error:
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Click to expand...
Click to collapse

konan2010 said:
i made full format, and format cashe ,and works fine and now when using rumruner, it worked further step than other rom but give me the following error:
Click to expand...
Click to collapse
Yeah probably to do with your firmware, HTC started patching firmware against rumrunner after jellybean.
Also just to confirm, you are able to Relock and Unlock the bootloader? This is good the bug must have been fixed with the new hboot :good:
So keep the stock rom on your device. Relock your bootloader and flash this firmware with fastboot. https://www.androidfilehost.com/?fid=24340319927533616
Copy the firmware file into your fastboot folder. Connect fastboot usb in the bootloader then flash the firmware with the following commands.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 6.04.1700.13_FULL_firmware.zip < ---- First flash will fail with pre-update so repeat command.
fastboot flash zip 6.04.1700.13_FULL_firmware.zip
fastboot reboot-bootloader
Wait for the bootloader and select recovery. The screen will go black and after some seconds show a red triangle with an exclamation mark.
Hold power and press volume up to reveal the stock recovery menu. Select Factory reset from the stock recovery. When it's complete reboot the device. :fingers-crossed:
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
Yeah probably to do with your firmware, HTC started patching firmware against rumrunner after jellybean.
Also just to confirm, you are able to Relock and Unlock the bootloader? This is good the bug must have been fixed with the new hboot :good:
So keep the stock rom on your device. Relock your bootloader and flash this firmware with fastboot. https://www.androidfilehost.com/?fid=24340319927533616
Copy the firmware file into your fastboot folder. Connect fastboot usb in the bootloader then flash the firmware with the following commands.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 6.04.1700.13_FULL_firmware.zip < ---- First flash will fail with pre-update so repeat command.
fastboot flash zip 6.04.1700.13_FULL_firmware.zip
fastboot reboot-bootloader
Wait for the bootloader and select recovery. The screen will go black and after some seconds show a red triangle with an exclamation mark.
Hold power and press volume up to reveal the stock recovery menu. Select Factory reset from the stock recovery. When it's complete reboot the device. :fingers-crossed:
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot i done exactly and all went ok, then I tried installed rumruner and gave me the same error
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit

konan2010 said:
Thanks a lot i done exactly and all went ok, then I tried installed rumruner and gave me the same error
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Click to expand...
Click to collapse
You cannot use rumrunner because your firmware won't allow it to work. To get s-off you must use sunshine app.
Does your device still suffer unknown IMEI and baseband after you flashed the firmware? If so then your problem is hardware related. You could use sunshine to get s-off but you may be spending money for nothing. If the firmware didn't fix it then it's unlikely an ruu will. Is the device still under warranty?
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
You cannot use rumrunner because your firmware won't allow it to work. To get s-off you must use sunshine app.
Does your device still suffer unknown IMEI and baseband after you flashed the firmware? If so then your problem is hardware related. You could use sunshine to get s-off but you may be spending money for nothing. If the firmware didn't fix it then it's unlikely an ruu will. Is the device still under warranty?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
no it is not underwaranty, is there a way to install ruu with locked bootloader and s-on?

konan2010 said:
no it is not underwaranty, is there a way to install ruu with locked bootloader and s-on?
Click to expand...
Click to collapse
Only ruu I can find is here https://www.androidfilehost.com/?fid=24369303960689836
But it says it's unsigned. Unsigned RUU won't flash with s-on. It needs to be official HTC signed.
Sent from my HTC One M9 using Tapatalk

thanks I will try that one may it work
https://www.androidfilehost.com/?fid=24369303960689828

konan2010 said:
thanks I will try that one may it work
https://www.androidfilehost.com/?fid=24369303960689828
Click to expand...
Click to collapse
didnot work and i tried s-off using firewater it give me the following erro
[email protected]:/ # chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
error: only position independent executables (PIE) are supported.
Click to expand...
Click to collapse
do you have any idea about it?

konan2010 said:
didnot work and i tried s-off using firewater it give me the following erro
do you have any idea about it?
Click to expand...
Click to collapse
Firewater was discontinued. It relied on an online resource that is no longer available. With hboot 1.56 and above Sunshine is the only way to get s-off.
Unless you know someone with an XTC clip.
Sent from my HTC One M9 using Tapatalk

I really have no idea why people started loosing their IMEIs. I met two guys with the same problem like me.

Danny201281 said:
Firewater was discontinued. It relied on an online resource that is no longer available. With hboot 1.56 and above Sunshine is the only way to get s-off.
Unless you know someone with an XTC clip.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I have hboot 1.54 can be solved by anyway except sunshine?is there no way to downgrade it with s-on?
Gudio142 said:
I really have no idea why people started loosing their IMEIs. I met two guys with the same problem like me.
Click to expand...
Click to collapse
I really now I can say I hate HTC for what is happening to us

konan2010 said:
I have hboot 1.54 can be solved by anyway except sunshine?is there no way to downgrade it with s-on?
I really now I can say I hate HTC for what is happening to us
Click to expand...
Click to collapse
No to downgrade firmware you must have s-off, but as I said I don't think it's going to help you. I believe your problem is hardware related.
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
No to downgrade firmware you must have s-off, but as I said I don't think it's going to help you. I believe your problem is hardware related.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
thanks for reply guess the phone is useless now