Database Develop

[Q] Bricked GPE HTC One - blue grey screen

Phone: HTC One GPE
OS: was 4.3
HBOOT: 1.54
S-ON
Tampered
Unlocked
I got the 4.4 OTA and attempted to install it. It got to the TWRP screen and started installing something that I couldn't stop.
It rebooted to the Google screen, but then it got to a blue grey screen that a couple of others have seen.
I cannot get back into TWRP but I can get into fastboot.
bootloader - cannot connect to adb from my mac (do not have access to a windows machine)
fastboot - can access
$ ./fastboot-mac getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.18.3263.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.06.1700.10
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HTXXXXXXX
INFOimei: XXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: GOOGL001
INFObattery-status: good
INFObattery-voltage: 4242mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
I cannot sideload or get into a recovery. What can I do?

Same issue here as well... I will watch this post, and happened the same way as you. Fastboot still works, phone will not connect to computer.

Can you flash custom recovery like TWRP or CWM? looks like your main version didn't update to 4.4 as it is 3.58, but you are on 3.06..
Also try to issue a fastboot clear cache command and reboot?
What

SaHiLzZ said:
Can you flash custom recovery like TWRP or CWM? looks like your main version didn't update to 4.4 as it is 3.58, but you are on 3.06..
Also try to issue a fastboot clear cache command and reboot?
What
Click to expand...
Click to collapse
I was able to re-flash TWRP 2.6.1.0 (this was the one that was on when I first installed TWRP).
When you say clear cache - what do you mean?
Do you mean
Code:
fastboot -w
Code:
-w erase userdata and cache

There's a very good reason as to why your not supposed to install OTA's via custom recoveries
Sent from my Nexus 10 using Tapatalk 4

fastboot erase cache
for good measure I'd do
fastboot erase userdata as well [note that this will wipe your device!]
your /system is likely trashed due to the borked OTA. So the best we can do with an s-on device and no official RUU for the GPE is write the system files from recovery using a rom.zip or a clean nandroid (couldn't find one). This rom seems to be the least tampered with: http://forum.xda-developers.com/showthread.php?t=2341395
before booting the rom the first time, reboot to bootloader.
you now need to flash the firmware.zip from the OTA.
fastboot rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
should be good to go after that.
illwon said:
I was able to re-flash TWRP 2.6.1.0 (this was the one that was on when I first installed TWRP).
When you say clear cache - what do you mean?
Do you mean
Code:
fastboot -w
Code:
-w erase userdata and cache
Click to expand...
Click to collapse

ipfreelytech said:
fastboot erase cache
for good measure I'd do
fastboot erase userdata as well [note that this will wipe your device!]
your /system is likely trashed due to the borked OTA. So the best we can do with an s-on device and no official RUU for the GPE is write the system files from recovery using a rom.zip or a clean nandroid (couldn't find one). This rom seems to be the least tampered with: http://forum.xda-developers.com/showthread.php?t=2341395
before booting the rom the first time, reboot to bootloader.
you now need to flash the firmware.zip from the OTA.
fastboot rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
should be good to go after that.
Click to expand...
Click to collapse
Am I reading that right? flash firmware.zip twice?

yes. I know it looks retarded in sequence like that. it's because your updating hboot. it starts updating then reboots itself to flush and then you continue the flashing.
illwon said:
Am I reading that right? flash firmware.zip twice?
Click to expand...
Click to collapse

ipfreelytech said:
yes. I know it looks retarded in sequence like that. it's because your updating hboot. it starts updating then reboots itself to flush and then you continue the flashing.
Click to expand...
Click to collapse
Still having trouble...
Code:
./fastboot-mac erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
Tried to skip that and install from zip using TWRP, but that fails.
Code:
Setting permissions...
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard.. (cuts off)
Error flashing zip '/sdcard/bigxie_m7_GPe_KRT16 (cuts off)
Updating partition details...
Failed
I appreciate your help, but I'm completely lost now...

yeah, apparently hboot on the One won't allow the erase userdata command. Other devices do allow that.
The partition details message is not a good one. I got that one time while flashing the gpe conversion ruu on an ATT one. The fast fix was to run the official ATT RUU and then run the conversion RUU. For your GPE there is no official RUU.
illwon said:
Still having trouble...
Code:
./fastboot-mac erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
Tried to skip that and install from zip using TWRP, but that fails.
Code:
Setting permissions...
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard.. (cuts off)
Error flashing zip '/sdcard/bigxie_m7_GPe_KRT16 (cuts off)
Updating partition details...
Failed
I appreciate your help, but I'm completely lost now...
Click to expand...
Click to collapse

So what does this mean? Am I completely hosed? I have to wait for the official RUU?
ipfreelytech said:
yeah, apparently hboot on the One won't allow the erase userdata command. Other devices do allow that.
The partition details message is not a good one. I got that one time while flashing the gpe conversion ruu on an ATT one. The fast fix was to run the official ATT RUU and then run the conversion RUU. For your GPE there is no official RUU.
Click to expand...
Click to collapse

If you can get to TWRP, can you do adb push romname.zip /sdcard/ and install another custom rom?

No - I tried what ipfreely mentioned on the previous page to install the "vanilla" rom, didn't work.
SaHiLzZ said:
If you can get to TWRP, can you do adb push romname.zip /sdcard/ and install another custom rom?
Click to expand...
Click to collapse

[SOLVED] Soft Bricked - Need Help!

Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode and in RUU mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!

awer25 said:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt

alray said:
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
Click to expand...
Click to collapse
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.

awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
Click to expand...
Click to collapse
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
Click to expand...
Click to collapse
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?

alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
Thank you for that explanation. I got into RUU mode by doing fastboot oem rebootRUU, which took me to a black screen with silver HTC. That may not be RUU mode...I'm just guessing.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
edit: Wait, there is also a 3.22.1540.1 ruu.zip on htcdev.com so try it first.
fastboot oem rebootRUU
fastboot flash zip <name_of_file>.zip
fastboot flash zip <name_of_file>.zip
fastboot reboot
Click to expand...
Click to collapse
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.

awer25 said:
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
Click to expand...
Click to collapse
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.

alray said:
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
Click to expand...
Click to collapse
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!

awer25 said:
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
Click to expand...
Click to collapse
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on.
Click to expand...
Click to collapse
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...

alray said:
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
Click to expand...
Click to collapse
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.

awer25 said:
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
Click to expand...
Click to collapse
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''

alray said:
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
Click to expand...
Click to collapse
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!

awer25 said:
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
Click to expand...
Click to collapse
Try the ruu.exe on windows 7.

alray said:
Try the ruu.exe on windows 7.
Click to expand...
Click to collapse
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.

awer25 said:
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
Click to expand...
Click to collapse
I got it! I had to relock my bootloader for some reason. Then, the Windows RUU installed fine.
Thank you alray for your help!

Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?

-marco- said:
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
Click to expand...
Click to collapse
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.

awer25 said:
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
Click to expand...
Click to collapse
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s

-marco- said:
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
finished. total time: 0.066s
Click to expand...
Click to collapse
-marco- said:
I am at work in the office and at some point I look at my phone and I see it rebooted on its own. now it's stuck forever on the HTC one beats audio loading screen.
I didn't even touch anything before. Tried to reboot but it just gets stuck there.
Click to expand...
Click to collapse
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?

nkk71 said:
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
Click to expand...
Click to collapse
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!

-marco- said:
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
Click to expand...
Click to collapse
Well first I would recommend you update recovery to TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
since they are more compatible when flashing 4.4 ROMs (make sure to check MD5 on the files, that site doesn't play nice with download managers!)
Code:
[B]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader[/B]
-> enter recovery
Second, in TWRP, make a nandroid backup, you may need it later *** (please check below)
Third, put a ROM on the phone (in custom recovery):
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HT34xxxxxxxx recovery <- you need to be in recovery
[B]adb push <name of rom>.zip /sdcard/[/B] <- this will take about 5 mins without any progress
and install the ROM, don't select WIPE during installation, and you should have your million $ question solved... all apps, data, etc should be there, but if you get apps crashing it's because of the "dirty-flash"
As to which ROMs you can use for the above procedure, there's is a 100% stock version of 4.19.401.9 here: http://forum.xda-developers.com/showthread.php?t=2224752
I'm personally using ARHD 52.0 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (stock but with improvements, and rooted)
I haven't checked if there's a 100% stock 4.20.707.6 ROM around, so you could do some googling and see.
Hope that helps
*** once you've done the backup, you can try wiping "data, cache, dalvik", and then restore the nandroid... sometimes that works
if not keep the nandroid, as it has all the information, and you can use Nandroid Manager (in play store) to extract individual information, if need be.
Good Luck

[SOLVED] Flashed wrong ROM, neither ROM nor recovery are working

Hi everybody,
I've been flashing custom ROMs for years now, but now I screwed up -.-
I've got a One M7UL and accidentally flashed a Sprint ROM .. Now the only thing left working is fastboot.
If I try to boot into TWRP recovery (tried different versions already) the splashscreen will appear and crash back into bootloop. If I try to boot into clockwork recovery, it will boot but throw various errors 'E:Can't mount /cache/[..]' .. as soon as I try to do anything @ clockwork, it will crash back into bootloop.
I thought about flashing a RUU, but the bootloader is unlocked but still s-on. Modelid: PN0170000 Cidnum: VODAP102. I think the device has to be s-off to flash a RUU.exe, correct ? How about a RUU.zip ? oO Is there a way to get the device s-off without having ADB working ? How do I find a working RUU for this device, because I've read that I need a '1.xx.161.xx' for it's a Vodafon-brand and I won't find a damn usable RUU for it .. Is there a way to use a different RUU ?
help would be MUCH appreciated
thx & greets
hendi

Ok, got ADB working at the damaged clockword recovery .. but sideloading another ROM won't work and it seems like Revone S-OFF only works with a booted 4.2.2 ROM -.-
Any suggestions ?

Here's the output off 'getvar all':
(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.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4246mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.052s

If I could get my hands on another HTC ONE M7ul PN0710000/VODAP102 would I be able to build my own RUU ?
Help would be really appreciated ^^

Have you tried fastboot erase cache?
Sent from my GT-I9305 using xda app-developers app

nateboi81 said:
Have you tried fastboot erase cache?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
yep, sadly without any success.. I also tried different versions of TWRP & clockwork recovery.
thx for the reply

doomhendi said:
If I could get my hands on another HTC ONE M7ul PN0710000/VODAP102 would I be able to build my own RUU ?
Help would be really appreciated ^^
Click to expand...
Click to collapse
it's been a while but i think the old developer edition RUU may work
this is the one for hboot 1.44
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/

clsA said:
it's been a while but i think the old developer edition RUU may work
this is the one for hboot 1.44
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
Click to expand...
Click to collapse
hey there
Don't I need a RUU with the version 1.xx.161.xxx because of the s-on + Vodafon-branding ? oO

doomhendi said:
hey there
Don't I need a RUU with the version 1.xx.161.xxx because of the s-on + Vodafon-branding ? oO
Click to expand...
Click to collapse
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in

clsA said:
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in
Click to expand...
Click to collapse
ah, cool that's good to know oO - I am already downloading

doomhendi said:
ah, cool that's good to know oO - I am already downloading
Click to expand...
Click to collapse
Sorry I was doing some more reading ..that RUU requires CID 11111111 and MID PN0712000, I'll keep looking

clsA said:
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in
Click to expand...
Click to collapse
Sorry, didn't read, but if s-on, then don't start fashing things not for your phone... High chance you won't be able to unlock bootloader again!
If s-off, then ok.
Sent from my HTC One using Tapatalk

clsA said:
Sorry I was doing some more reading ..that RUU requires CID 11111111 and MID PN0712000, I'll keep looking
Click to expand...
Click to collapse
big thanks, pal

nkk71 said:
Sorry, didn't read, but if s-on, then don't start fashing things not for your phone... High chance you won't be able to unlock bootloader again!
If s-off, then ok.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
hey, yeah I am afraid it's still s-on .. but I didn't try to flash it so far.
How can I manually lock the bootloader again ? oO I've just tried method 1 from your guide (http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3) but the bootloader still says it's unlocked oO
I haven't tried yet, but 'fastboot oem lock' should do the trick .. Now I just need a fitting RUU oO
Damn it, I'm kinda flashoholic since the good old Windows Mobile 6.51 Pro-times .. but I never took the wrong ROM xX
You guys really seem to know what you are doing .. the wrong ROM seems to have messed up at least the cache partition, may be there is another way than flashing a RUU, to fix this ? If I would be able to get clockwork recovery to install a working rom, it should reconstruct everything or at least give me the opportunity to s-off the device oO
I would be really grateful for some help
I just got an idea: Is it possible to tweak an developers RUU ? oO
Sorry for all the questions, I just really want to get that baby up an running again ^^

doomhendi said:
hey, yeah I am afraid it's still s-on .. but I didn't try to flash it so far.
How can I manually lock the bootloader again ? oO I've just tried method 1 from your guide (http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3) but the bootloader still says it's unlocked oO
I haven't tried yet, but 'fastboot oem lock' should do the trick .. Now I just need a fitting RUU oO
Damn it, I'm kinda flashoholic since the good old Windows Mobile 6.51 Pro-times .. but I never took the wrong ROM xX
You guys really seem to know what you are doing .. the wrong ROM seems to have messed up at least the cache partition, may be there is another way than flashing a RUU, to fix this ? If I would be able to get clockwork recovery to install a working rom, it should reconstruct everything or at least give me the opportunity to s-off the device oO
I would be really grateful for some help
I just got an idea: Is it possible to tweak an developers RUU ? oO
Sorry for all the questions, I just really want to get that baby up an running again ^^
Click to expand...
Click to collapse
sure you can try
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
sure you can try
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
sorry, may be you misunderstood me: The bootloader is open & s-on. I've tried to flash different versions of TWRP & Clockwork Recovery via fastboot, including erase cache.. TWRP won't even start and Clockwork will start but throw multiple 'Can't Mount / Open /cache/[...]' errors and crash as soon as I try to do anything

doomhendi said:
sorry, may be you misunderstood me: The bootloader is open & s-on. I've tried to flash different versions of TWRP & Clockwork Recovery via fastboot, including erase cache.. TWRP won't even start and Clockwork will start but throw multiple 'Can't Mount / Open /cache/[...]' errors and crash as soon as I try to do anything
Click to expand...
Click to collapse
try and flash the stock recovery and do a factory reset
then try and flash TWRP again
Stock recovery's are here >> http://d-h.st/users/guich/?fld_id=29380#files

clsA said:
try and flash the stock recovery and do a factory reset
then try and flash TWRP again
Stock recovery's are here >> http://d-h.st/users/guich/?fld_id=29380#files
Click to expand...
Click to collapse
damn, sorry I've spent the whole day and night, reading how to possibly fix this and already tried to flash stock recovery .. The recovery won't start at all. It doesn't matter if I try to start via 'Factory Reset' or 'Recovery'.
According to the errors clockwork recovery throws, I guess the partition table got (partly?) messed up oO
*edit* Of cause I've tried again, following the link you've just sent me - thx for the effort

doomhendi said:
damn, sorry I've spent the whole day and night, reading how to possibly fix this and already tried to flash stock recovery .. The recovery won't start at all. It doesn't matter if I try to start via 'Factory Reset' or 'Recovery'.
According to the errors clockwork recovery throws, I guess the partition table got (partly?) messed up oO
*edit* Of cause I've tried again, following the link you've just sent me - thx for the effort
Click to expand...
Click to collapse
do you know how to start stock recovery ?

clsA said:
do you know how to start stock recovery ?
Click to expand...
Click to collapse
After flash, erase cache & reboot-bootloader, I've tried 'Factory Reset' @ Hboot and the 'usual' way via the bootloader oO

Boot Looped Incredible S... Last Try

Hey guys,
Last year I rooted my Incredible S and installed one of the CyanogenMods. Everything seemed to work fine until this spring when it started bootlooping on me. At first I could bootup and after running my phone for a few hours it would start looping. So I got a new battery which I thought would solve the problem, it didn't. Now I can't even boot up anymore without hitting the loop. I can only enter HBOOT.
I've tried following a few guides but I can't get anything going. Buying a new phone Friday but before thought I might as well post here. Any help?
-Revolutionary-
VIVO PVT SHIP S-OFF - RL
HBOOT-6.13.1002
RADIO-3805.6.03.16_M
eMMC-boot
Apr 1 2011, 18:34:39
I can enter fastboot but recovery and factory reset start a loop.
Thanks guys!

What recovery do you use?
Can you enter it?
If yes.. Just download one of your fav's roms, but it in your SD-Card, Wipe Everything, and Flash the rom (&GApps if AOSP) and reboot..
If No, Connect your Phone To PC and fastboot flash recovery recovery.img" :laugh:
Let me know if worked

Download and install a recovery, i recommend 4ext
See if u can enter it then...
I must tell ya, never give up, i remember myself forgetting to flash boot.img and having my dad almost killing me ^^

Thanks for the responses!
@Mohamed Ab M I cannot enter recovery off of hboot. I can flashboot and I tried to flash "recovery-clockwork-5.0.2.0-inc.img" but nothing improved. Is there something else I can try?
@oziboy Do you have a link for 4ext? I see the website but it looks like an app? Also, how do I wipe everything if fastboot is my only option right now?
Haven't given up yet but I only have until Friday!
Edit: Is there any chance this might have something to do with the radio?

ok tried two different things. Downloaded the recovery.img of 4ext from this thread: http://forum.xda-developers.com/showthread.php?t=1377751 and fastboot flashed it. Nothing changed.
So I tried flashing a different radio... still no go.
Not sure what else I can try?

Well.. I can think of one thing :|
Try doing these commands in fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Maybe something is wrong in system.. I don't know
Btw dose it say "success" when you flash a recovery? Or it fails?
And if It didn't work... Try running an RUU :| and you will lose everything:|

Mohamed Ab M said:
Well.. I can think of one thing :|
Try doing these commands in fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Maybe something is wrong in system.. I don't know
Btw dose it say "success" when you flash a recovery? Or it fails?
And if It didn't work... Try running an RUU :| and you will lose everything:|
Click to expand...
Click to collapse
I don't mind losing everything, already backed up contacts and messages when I could still access the OS.
Can you recommend a good RUU to try? What is an RUU? Thanks for the help!

Then for a ruu go here http://androidruu.com/getdownload.p...33U_3831.18.00.11_M_release_266013_signed.exe
This should be the ruu that you need assuming your phone is a WWE, if you phone isnt WWE then use this to see what version is for you, make sure u only use vivo and not vivow
If the link to installation in beginning didnt work, that link was a link to the old thread of the RUU'S but anyway i posted the links for ya
Now all you gotta do is download the ruu , get ur phone to fastboot and do fastboot oem lock and then run the ruu on your computer and then go here for the rest http://forum.xda-developers.com/showthread.php?t=1359555

Got into fastboot and entered "fastboot oem lock" but kept getting an error, command error or something.
Downloaded 4 different ruus and got the "rom.zip" file and renamed it to "update.zip" and tried "fastboot update update.zip" on all of them.... no luck. Something about wrong signature or something.
Thanks for everyone's help but I don't see anyway out here!

jwads said:
Got into fastboot and entered "fastboot oem lock" but kept getting an error, command error or something.
Downloaded 4 different ruus and got the "rom.zip" file and renamed it to "update.zip" and tried "fastboot update update.zip" on all of them.... no luck. Something about wrong signature or something.
Thanks for everyone's help but I don't see anyway out here!
Click to expand...
Click to collapse
And u tried to run the ruu.exe without extracting the rom?
It saved my incredible s and my one x+
And to flash a rom.zip u need fastboot flash all rom.zip i think

This is actually doing something! I didn't realize I could run the RUU when plugged into fastboot. Fingers crossed here....
I got two working but both still resulted in a bootloop. Which convinces me the problem must be hardware or something. Oh well, it was a good device in its day.
Thank you for all your help!

Bootlooping is not a hardware failure..
Can you flash a recovery now? And use it?

Erm, now try extracting rom.zip and fastboot erase all and fastboot flash all rom.zip
Then id it does t work, flash the stock recovery from somewhere, only then you can use update.zip, this just came to my mind
If after flashing stock recovery try fastboot oem lock again and then go run the ruu.exe again
If it doesnt work then, then you gotta fastboot flash boot.img manually, this file is located in the rom.zip
If that doesnt work, try update.zip again with stock recovery
Must tell ya, its not hardware
You gotta give up only when your mobo is fried, and thats what i did on my htc one x+...

In the previous step I got S-ON set back on, does that change anything? Because now it seems that fastboot erase all doesn't work
erasing 'all'...
FAILED <remote: not allowed>
Trying the other steps you gave...
edit: I extracted a recovery_signed.zip file from the rom.zip file and tried to flash it using flashboot. Getting a signature error, though I know it is the correct RUU I am getting it from.
FAILED <remote: signature verify fail>

Try fastboot oem lock again, im 100 percent sure thats the command to lock it, i had almost the same issues when i failed my first try at rooting xD
Aight have you tried fastboot flash all rom.zip?
And then manually flash boot.img from the rom.zip?

None of those are working, getting errors on all them.
My HBOOT is not reading this, does this change anything?
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011.18:34:39

jwads said:
None of those are working, getting errors on all them.
My HBOOT is not reading this, does this change anything?
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011.18:34:39
Click to expand...
Click to collapse
Hboot is successfully downgraded, now follow this guide http://forum.xda-developers.com/showthread.php?t=2118187
From step 9

I can't follow that guide because I can't get into the android os to turn on usb debugging. My problem is still the boot loop.

oziboy said:
Hboot is successfully downgraded, now follow this guide http://forum.xda-developers.com/showthread.php?t=2118187
From step 9
Click to expand...
Click to collapse
When I run the program it just sits at "waiting for device..."

jwads said:
When I run the program it just sits at "waiting for device..."
Click to expand...
Click to collapse
Lol sorry for that one, i sent you to some adb thingy while ur in fastboot, i totally read over it xD
Anyway niw try unlocking again thru htcdev.com and then flash a recovery and get into it

[Q] Brick or saveable? Red triangle - SOLVED!

I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.

Well... There is one thing you could do.
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Click to expand...
Click to collapse
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
2.Flash a custom recovery.
You flash a custom recovery like this using fastboot.
Code:
fastboot flash recovery <recoveryName>.img
3.Use TWRP to copy the ROM zip file to your internal storage.
4.Do a nandroid backup.
5.Do an advanced wipe (Wipe data, system, cache and dalvik cache partitions).
6.Do a factory reset (Wipe Data/Factory reset).
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
7.Flash your preferred ROM.
8.Tell me if it worked and enjoy!

squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!".
Click to expand...
Click to collapse
This screen is the stock recovery main page.
Volume up and power work, and give 5 fails to mount the sd card.
Click to expand...
Click to collapse
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Click to expand...
Click to collapse
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
Is there anything else I can do with it? or is it just a paperweight now?
Click to expand...
Click to collapse
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant
Click to expand...
Click to collapse
Yes rogers are M7_UL too.
so you can just go ahead and root your phone then flash a ROM of your choice.
Click to expand...
Click to collapse
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
-Windows computer (WIndows 8.1 is fine).
Click to expand...
Click to collapse
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
Click to expand...
Click to collapse
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.

alray said:
This screen is the stock recovery main page.
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
Yes rogers are M7_UL too.
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
Click to expand...
Click to collapse
The last HTC device that lasted 3 years with me was the One X (my AT&T M7 either got bricked or had battery issue) and I never tried to get it S-OFF'ed since I really did no't see any use for it back in the day plus its screen was having problems anyway. This is new knowledge for me thanks!
and to the OP, if you need more help the quote button is your friend.
Good luck!

The Android Manual said:
The last HTC device that lasted 3 years with me was the One X
Click to expand...
Click to collapse
Wow mine (Tegra version) only lasted 13 months, had the infamous wifi issue (repaired myself) , overheat issue and motherboard finally died. I was very reluctant to buy htc again but finally I'm very satisfied with my M7.

Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.

squidstings said:
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
Click to expand...
Click to collapse
You can try the Roger's RUU in this post. You will need to follow the instructions in the OP. I believe in your case, since there is no 6.xx version for Roger's you can go directly to the Lollipop version.

The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
Click to expand...
Click to collapse
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.

squidstings said:
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
Click to expand...
Click to collapse
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.

alray said:
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
Click to expand...
Click to collapse
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0

squidstings said:
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.

mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM? is one custom and the other carrier generated?). I managed to get the identifier token last night, but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.

mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
I downloaded the ruu from the link on XDA but the .zip won't extract.

squidstings said:
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM?
Click to expand...
Click to collapse
A RUU stands for Rom Update Utility. Its an official file from HTC that flashes many partitions like the system partition (the rom/OS), the recovery partition, bootloader, radio partition, touch drivers, IR drivers...... well all partitions that are not specific to your phone and that will make it stock again. The only partition that are not flashed when using a RUU are those containing unique info about your phone like the MFG partition containing your IMEI number, Serial number, Date of manufactures etc.
A rom is only the /system partition flashed using a custom recovery. So when you flash a ROM (eiither custom or stock) you only flash the system partition and all other are kept like they was before the flash.
but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
Click to expand...
Click to collapse
You don't need usb debugging when flashing a RUU. USB debuging is only needed to use ADB commands when booted in the OS. A RUU is flashed using FASTBOOT commands when booted in the bootloader.
squidstings said:
I downloaded the ruu from the link on XDA but the .zip won't extract.
Click to expand...
Click to collapse
This is explained in the same post from where you have downloaded the file.... You might want to read the OP of the thread you are downloading files from :good: Not trying to be rude btw but lack of reading can sometime makes the situation worst. so just for you here it is again: The ruu are encrypted so they can't be extracted or opened and don't need to be, only flash it on your phone.
This is a collection of lollipop ruu.zip files for our beloved htc one m7 801.
I cannot test all of these files so any feedback will be welcome.
Also I have no responsibility if you phone explodes after flashing any of these files, I am just the uploader.
As many in this thread, ask about zip corruption, zip are not corrupted they are encrypted and can't open normally , they need decryption check md5 and dont try to unzip them
Click to expand...
Click to collapse
and instruction how to flash the ruu are posted just below these warnings, just click on the "show more" button.
---------- Post added at 05:12 PM ---------- Previous post was at 04:54 PM ----------
@squidstings
Might be easier to just unlock the bootloader, flash a recovery and then a rom like suggested at post #2
Youv said you already have your identifier token, go ahead and submit it to htcdev.com/bootloader (must create and account first). They will reply with an e-mail containing a file named Unlock_code.bin. Download and save the file in the same folder where you have adb and fastboot installed on your computer.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.

Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.[/QUOTE]
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
C:\Android>
I did read everything. got a bit confused by different methods and files suggested (maybe just different wording for the same proceedure?). I've been looking for ROMs and RUUs all day. after I've fixed this phone (hopefully) i want to root my m7.

squidstings said:
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Click to expand...
Click to collapse
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired

alray said:
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
Click to expand...
Click to collapse
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!

squidstings said:
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
Click to expand...
Click to collapse
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.

mb_guy said:
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
Click to expand...
Click to collapse
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.

squidstings said:
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
Click to expand...
Click to collapse
Ok, let me try again.
If you want to flash a rom,
1) unlocked bootloader (you have)
2) Flash custom recovery like twrp (I don't see that you have done this) so may be easier to go the ruu route.
3) Use custom recovery to install rom. I like the arhd ones
If you want to flash the RUU
1) relock the bootloader
2) flash the ruu, once this is done and the phone rebooted and running it will be at 7.17.631.7, go to settings about and check for system updates. You should receive an OTA which is 7.17.631.35. Install it.
3) You can leave the phone like this, or re-unlock the bootloader and flash a custom recovery like twrp. This will give you the ability to do nandroid backups, root the phone or install custom roms if you want.
Either method should work, the choice is yours
Hope this is clearer.