Database Develop

[SOLVED] RUU Problem

Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
So here is my fix..
I flashed a bone stock rom with no root found here... or restore nandroid. I usually make a nandroid backup before i flash su.zip. but anyway, after the restore i booted into the bootloader and types fastboot oem lock. then i proceeded to reboot, but my device kept booting into bootloader. i tried fastboot erase cache which didn't help. so i grabbed the firmware from this thread http://forum.xda-developers.com/showthread.php?t=2368907 . In the bootloader type...
fastboot oem reboot RUU
now you should be in a black screen with the htc logo
fastboot flash zip /navigate/to/zip/file
you will get fail the first time(pre-hboot update: please flush immediately)
just make sure your device is still in the RUU mode(black screen with htc logo, if not redo first step)
fastboot flash zip /navigate/to/zip/file
it should proceed to flash and get flash successful!
oh you might get a loading bar underneath the htc logo. this is normal. just make sure that in the terminal it said successful.
unplug and hold the power till it restarts.
now you are bone stock with stock recovery. this is the closest I've came to being stock since there currently isn't a RUU tool for the latest firmware. hope this helps. BIG THANKS TO bigdaddy619 for the input!

Techno Droid said:
Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
Click to expand...
Click to collapse
s-off should let you ruu any image

Techno Droid said:
Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
Click to expand...
Click to collapse
The Software Version - 1.29.651.10 refers to the software version of the rom you are running if you were to flash a rom based on 1.31.651.2 your software version in settings would reflect that.
Since you are s-on your phone most likely came with 1.31.651.2 why are you trying to go backwards? If you just want to go back to stock there is a stock 1.31.651.2 rom(rooted and unrooted) in Indirects thread.

bigdaddy619 said:
The Software Version - 1.29.651.10 refers to the software version of the rom you are running if you were to flash a rom based on 1.31.651.2 your software version in settings would reflect that.
Since you are s-on your phone most likely came with 1.31.651.2 why are you trying to go backwards? If you just want to go back to stock there is a stock 1.31.651.2 rom(rooted and unrooted) in Indirects thread.
Click to expand...
Click to collapse
BC I need to send it back to sprint and plus in want to learn the process so I know exactly what im doing. Is there and ruu for the version my boot loader reflects?
Sent from my One using Tapatalk 2

Techno Droid said:
BC I need to send it back to sprint and plus in want to learn the process so I know exactly what im doing. Is there and ruu for the version my boot loader reflects?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
There is not an RUU for 1.31.651.2
I would suggest unlocking again
flash twrp 2.5.0.0
flash the Stock(no root) 1.31 rom in Indirect's thread
then relock again(your bootloader will say RE-LOCKED not LOCKED)

I kinda figured that I just had a brain fart about it. But when I flash a stock rom and relock bootloader it won't boot up I just keep booting into the bootloader. So if in was on an earlier version of 1.29.651.10 I would be able to relock and be stock, right?
Sent from my One using Tapatalk 2

Techno Droid said:
I kinda figured that I just had a brain fart about it. But when I flash a stock rom and relock bootloader it won't boot up I just keep booting into the bootloader. So if in was on an earlier version of 1.29.651.10 I would be able to relock and be stock, right?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Did you check the MD5 on the stock rom you were trying to flash maybe it was a bad download?

In was on it running and all. Then I proceeded and relocked. Or did I do something wrong here?
Sent from my One using Tapatalk 2

Techno Droid said:
In was on it running and all. Then I proceeded and relocked. Or did I do something wrong here?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Check PM

Same Issue As Techno Droid - ! SOS ! - 7 day old brick
Hi all,
I'm hoping someone can assist me here, its been a week now without my phone due to my botched attempts to flash a custom rom. I have the exact same situation as TechnoDroid's initial post, and same exact fails. I tried Techno Droids fix, but am getting the following error from this command:
fastboot oem reboot RUU
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.003s.
I've flashed the 1.31 stock ROM from Indirect's thread, and re-locked the bootloader, but I always get an OS that has no apps and begins a system boot loop after a few minutes.
Also, if I can find a compatible nandroid backup and flash it through TWRP would that be a possible fix?
Any help is greatly appreciated, I'll be looking into purchasing a backup phone from my MVNA, but would really like to unbrick this one since I paid full boat for an unlocked version!
- cheers

dancesWitShoes said:
Hi all,
I'm hoping someone can assist me here, its been a week now without my phone due to my botched attempts to flash a custom rom. I have the exact same situation as TechnoDroid's initial post, and same exact fails. I tried Techno Droids fix, but am getting the following error from this command:
fastboot oem reboot RUU
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.003s.
I've flashed the 1.31 stock ROM from Indirect's thread, and re-locked the bootloader, but I always get an OS that has no apps and begins a system boot loop after a few minutes.
Also, if I can find a compatible nandroid backup and flash it through TWRP would that be a possible fix?
Any help is greatly appreciated, I'll be looking into purchasing a backup phone from my MVNA, but would really like to unbrick this one since I paid full boat for an unlocked version!
- cheers
Click to expand...
Click to collapse
Check PM

BD619 said:
Check PM
Click to expand...
Click to collapse
having the same issue: stock deodexed flashed but unable to get ruu,, tsk (Sprint HTC One 1.29.651.10!)
pls help,,

stuck in boot mode

hi guys, I am stuck in boot mode after removing cyanogen mod, I have tried installing the RUU.exe but it will not complete - I think the reason for this is that S-ON. I can't seem to find a solution to achieve S-off anywhere without having to be into the phones OS.
I have tried pushing the rom to my phone but I just keep getting 'no device found'
The usb recognises the phone but the adb commands do not work at all
any further info suggested would be massively appreciated.
edit:
got adb commands working by following this guide
(not allowed to post links yet)

progress so far:
I have managed to sideload a relevant ROM but it has now been saying 'installing update' for quite a while and I am not sure whether to touch it
on another note, the image verification thing on this forum is very, very annoying.

ok so I sideloaded a ROM and it aborted the installation, totally at a loss now

grantymc said:
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
Click to expand...
Click to collapse
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.

alray said:
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
Click to expand...
Click to collapse
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
(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.63.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W914634
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

grantymc said:
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
Click to expand...
Click to collapse
Ruu.zip are not installed with a custom recovery/sideloaded!! It must be flashed via fastboot ruu mode. Anyway this ruu is not for your phone, its a .401 base and you need a .61 base ruu of same version or higher than 3.63.61.1 but afaik there is no ruu for your phone... BTW the 1.20.401.1 ruu is a pre-release version without OTA updates so it a bad idea to use it.
grantymc said:
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
Click to expand...
Click to collapse
Either because of a bad rom/download or because your recovery version is outdated. Flash twrp 2.6.3.3 or 2.6.3.4. Also clear cache every time your flash something and md5 check your roms/recovery before you flash them.
grantymc said:
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
Click to expand...
Click to collapse
S-OFF is not require to flash a custom rom like CM only if you want to convert your phone using a ruu not intended for your version.

[Q] RUU stuck at "checking headers"

I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(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: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(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.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.

XDA Dev said:
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(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: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(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.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
Click to expand...
Click to collapse
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!

SaHiLzZ said:
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
Click to expand...
Click to collapse
Haha, thanks, I guess nearly 3 years of lurking on these forums taught me something about posting.
I was using a Windows Vista SP2 PC to try this. I've just tried it on my Mac running Windows 7 SP1 with bootcamp, the RUU file (which still checks out with the correct MD5 hash) starts the installshield wizard normally, but as soon as I accept the terms and conditions, the program closes and nothing opens again. I checked on task manager, the process closes shortly after accepting the terms. I tried restarting and looking up for a solution but I couldn't find anything that worked.
Is Vista really the only reason it's stuck at checking headers? I know Vista is rather despised by a lot of people, but by 2014 it did get better. I'd rather use that machine because on my Mac running Windows 7 the RUU could not start up because I've made the Windows partition too small. (It has around 3gb free now whereas the vista machine has more than 150).

Sorry for the double post, but it's probably my last one on this thread.
Even if my boot loader was re-locked, I tried running the firewater program to get s-off, and it worked. (As a bonus it re-unlocked my boot loader without wiping the phone, but I re-locked it again to get the ruu working).
Then I tried downgrading to hboot 1.44, but for some reason it kept giving an error like "failed: remote 42 custom id check fail." I decided to try the sense 5.0 ruu anyway (on my vista PC), and it worked! The phone now says "relocked" but tampered is gone of course, and I have hboot 1.44, android 4.1 and htc sense 5.0, but still s-off.
The first update popped up (and it's not android 4.4 with sense 6, it's something in between) so I'm going to update until no more updates are available. Then I'm going to re-unlock the boot loader because I want to root my phone, and then set up all my stuff. When a new update comes out, I can just flash the original recovery, apply the update and then re-flash twrp to root again.
Thank you for the suggestion to install the older ruu. I'm still stumped on why the newer one didn't work (it would have caused much less hassle), but whatever. At least my phone is much cleaner now. It feels good to have it like this again, I'm not against custom roms but I like the stock software too.
I'm using my iPhone to write this, but trust me, my htc is in full working order now.
Until next problem I can't solve myself
Sent from my iPhone using Tapatalk

Thanks for updating back. Don't S-ON.

SaHiLzZ said:
Thanks for updating back. Don't S-ON.
Click to expand...
Click to collapse
Yeah, I'm not going to. I've updated to android 4.3 now and I'm still downloading updates--it updated hboot to 1.55 but I still have s-off, so I believe it stays s-off if I don't run the command to (I guess irreversibly) go back to s-on, which I don't even know. (I didn't do s-off before because I didn't care about the extra privileges and was afraid of bricking my phone, but now that I have it I don't mind so I'm keeping it).
Sent from my iPhone using Tapatalk

[Q] One M7 GPE 5.0.1 No IMEI, Baseband

Hi everyone,
So, I upgraded my wifes M7 to a 4.4.4 GPE ROM from a Rogers stock ROM. I unlocked the bootloader from HTCDev and then got S-OFF with firewater. All went swimmingly, until we got the two OTAs for Lollipop. About 4 days ago, the service went out on the phone. In settings, there is no IMEI or Baseband listed, they both say unknown. I checked in fastboot with the getvar all command and the IMEI is there. I tried flashing the radio from the 5.0.1 OTA file, but it says "command rejected" to which it SOUNDS like my S-OFF isn't there anymore, even though the getvar and fastboot screen show it S-OFF.
Here is the getvar output:
C:\Users\Jeff>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: H**************
(bootloader) imei: 3************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3848mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.114s
So, where do I go from here... It's pretty coincidental that this happened RIGHT around the time that the M7s had the audio bug, but this doesn't sound like the same issue. I think reflashing the radio would work, but it keeps kicking me back, and I've read around here and am unsure of how to re-SOFF the phone. Any help would be appreciated. My wife is not beyond putting the Rogers RUU back on and just waiting for an official GTC update to Lollipop... if that's easier.
Thanks everyone.

First of all try to wipe all phone(full stock reset) and install android gpe 5.0.1 in recovery(you can find it on forum easy) than write me and say if you still have wrong baseband and imei(also probably your phone is not abble to read simcard numbers?)

If fastboot displays the proper imei, best guesses sounds like there is something wrong with the rom or radio that is causing it to report the incorrect imei.
If you have a custom recovery installed (since it appears you are s-off) you could just backup that current rom, wipe/factory reset it to see if it works and if it was something that borked up during the update.
If it still reports the incorrect imei after factory reset, try flashing some known working rom (cm11, omni, etc) and see if everything's working fine in there. Restore your backup after you are done.
That would confirm it's a software-related issue and you can proceed from there.

Tried Factory Reset
So I tried a factory reset from fastboot... no nice. I actually have the stock recovery on the unit so I could receive OTAs from google and not have to jigger around with anything (since it's my wifes phone) ... I THINK I'm S-OFF, but the fact that I couldn't flash a radio.img file in fastboot has me worried that the 5.0.1 update may have partially rescinded it, and I don't want to make things worse by something borking in the middle of a flash.
Would an RUU be the way to go here? Or just try stuffing TWRP onto it and try CM11 ...

if you confirm it's soff, or just even htcdev unlocked (as fastboot would say) you can always flash back stock recovery if you decide to change your mind.
You can extract the recovery img from a working stock rom/ruu, in the meantime flashing twrp/philz opens you for advanced recovery options.
You just flash the recovery in fastboot mode.
fastboot flash recovery twrp-etc.img
fastboot flash recovery nameofstockhtcrecovery.img
As for the radio, not sure what to say. Perhaps try extracting it (from your update file if possible) and flash it from there?

Still no dice
So I flashed TWRP and CM11 ... still no baseband or IMEI. I found a few flashable zips for radio images and still nothing.
I relocked my bootloader, and tried to push a Rogers RUU signed exe, to which I got Error 158 Image Error. No other information is given. I am going down in versions, but as far as I can see, my S-OFF is still in effect.

ssign said:
So I flashed TWRP and CM11 ... still no baseband or IMEI. I found a few flashable zips for radio images and still nothing.
I relocked my bootloader, and tried to push a Rogers RUU signed exe, to which I got Error 158 Image Error. No other information is given. I am going down in versions, but as far as I can see, my S-OFF is still in effect.
Click to expand...
Click to collapse
fastboot oem writecid 11111111
Now you can flash any RUU
Flash your Rogers RUU (after you confirm the md5 matches), and report back :good:

Update: Cannot flash RUU
Hi Again,
So I set SuperCID and tried to reflash the RUU. It got a little further, but hung on the "checking headers" but for almost an hour... so I reset the phone since I had to leave for XMas plans. Now, it gives me an error 155 Image Error when I try to use it. I've seen elsewhere that might need to downgrade my hboot? Since I'm on 1.57.0000? Any ideas about that? Thanks

HTC One M7 e801 bootup blankscreen

First of all, I got my m7 unlocked and stuffs. Then my supersu keep on appearing error for stop responding
Therefore I realize maybe my supersu was too old or something based on the tutorial, the zip was older version. I flashed with update-supersu.zip , thats where my nightmare begin.
I reboot after flashing it, HTC logo bootup appear then went on blankscreen. I tried to wiped data and factory reset still the same
Next I was trying to flash full firmware thought it should bring back my m7 to life, not successful, and tried different rom(Google stock rom), it all shows
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: not allowed)
Click to expand...
Click to collapse
I don't know what to do anymore, what did i miss to flash any rom or simply have my m7 works again, please help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader)
(bootloader)
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4102mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bf7e9305
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse

first of all, i figure out a few things here, maybe someone could help with my informations
If was planning to make it S-OFF but with Hboot 1.61 i will need to pay $25 for sunshine, X.
So the only way is that I flash stock M7_U 7.18.709.102 (HTC_Asia_TW), im not sure whats the correct way to do that. Or flash something ruu? I have no idea about that
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
what am I suppose to do? while the meantime im downloading the zip and its freaking slow, take very long (if someone got a better download website) due to the mirror
my recovery mode, fastboot and bootloader are functioning which is something im still happy for.
Please if someone could help me out

fungrian said:
first of all, i figure out a few things here, maybe someone could help with my informations
If was planning to make it S-OFF but with Hboot 1.61 i will need to pay $25 for sunshine, X.
So the only way is that I flash stock M7_U 7.18.709.102 (HTC_Asia_TW), im not sure whats the correct way to do that. Or flash something ruu? I have no idea about that
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
what am I suppose to do? while the meantime im downloading the zip and its freaking slow, take very long (if someone got a better download website) due to the mirror
my recovery mode, fastboot and bootloader are functioning which is something im still happy for.
Please if someone could help me out
Click to expand...
Click to collapse
Sometimes downloading things requires patience.
Im not sure exactly how S-ON flashing works but i did hear somewhere that something to do with boot image gets involved

I found out the best way to bring back my m7 is to use RUU method, but when i try to flash zip it shows "failed"
./fastboot-mac flash zip PN07IMG.zip
sending 'zip' (1975775 KB)...
FAILED (remote: 02 data length is too large)
Click to expand...
Click to collapse
FAILED (remote: 02 data length is too large)
maybe the RUU is not right for my phone?
Don't know whether is it i downloaded wrong rom file for my device

fungrian said:
I found out the best way to bring back my m7 is to use RUU method, but when i try to flash zip it shows "failed"
FAILED (remote: 02 data length is too large)
maybe the RUU is not right for my phone?
Don't know whether is it i downloaded wrong rom file for my device
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a RUU if it's a Lollipop version (version starting with 7.xx.xxx.x). Others fastboot versions won't work.
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
fungrian said:
saw from somewhere saying "if you are s on, you will have to do this seperate boot image install every time you want to flash a new rom"
Click to expand...
Click to collapse
Does not apply to the M7, the boot partition isn't write protected like previous htc devices.