Database Develop

[Q] HTC One relocked, can't flash (signature error)

Hey All,
I hope you guys can help me, I'm completely lost in all these threads and posts. I've spent hours on this, literally hours...
I have a HTC One M7 (bought in Belgium) which I wanted to return to stock because of a faulty speaker (I just rooted the standard image). So I relocked the bootloader to flash an RUU. I tried flashing several European RUUs from the xda collection, but nothing worked. I also tried a zipped firmware, and it also fails. I always get this error:
FAILED remote: 12 signature verify fail
I'm stuck in fastboot, it doesn't boot into the OS anymore, only fastboot.
Getvar output:
C:\ADT\sdk\platform-tools>fastboot 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.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I try to flash the RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
Strange thing is, when I check the zip's android-info:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
...
So I don't get anymore why it would fail a signature check...
I also tried flashing a newer version, this didn't work either. What makes matters worse, the battery keeps uncharging as I continue to struggle...
Tell it to me straight, doctor... Is my HTC doomed to be a paperweight?

What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this : http://www.androidruu.com/?developer=M7
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish

ckpv5 said:
What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this :
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
Click to expand...
Click to collapse
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.

dwarfstrider said:
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.
Click to expand...
Click to collapse
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
More info : http://forum.xda-developers.com/showthread.php?t=2358738

ckpv5 said:
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
[/url]
Click to expand...
Click to collapse
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...

dwarfstrider said:
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...
Click to expand...
Click to collapse
Search for ERROR 158 may help you.
What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0, maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU, not running the RUU in Admin Privilege mode.
Maybe someone else have better idea, have to wait for that.

What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0
- No, I locked using fastboot oem lock with USB cable.
maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU
- Afaik, I never installed a custom hboot myself. I get the red text warning at the white HTC screen.
not running the RUU in Admin Privilege mode.
- Nope, the RUU runs with admin privileges in Win 7
Maybe someone else have better idea, have to wait for that.
- Let's hope so :laugh:

This is what my phone looks like atm:
i.imgur.com/ bX9MFM3.jpg
(can't post pics/links yet, sorry)
Please guys, help a fella out... I will be forever grateful

Update: I unlocked my phone again with the unlock bin from HTCDev and now it boots again...
I suppose I need to do S-OFF with revone since I'm at 1.44, but unsure. Damn this stuff is confusing.

You will need to flash new firmware I saw a hierarchy of htc one's Ruu firmware list on android revolution site.
Just check in the name of the correct ruu you downloaded and try to match the numbers of your Ruu with the list given there. I hope it may help you or if you get confused Pm me.
Sent from my HTC One using XDA Premium 4 mobile app

OK, I solved it.
So I did an S-OFF with revone, then locked and removed tampered (also revone).
Then I flashed a good RUU. It took ages to find a good one, followed another thread (2325010) on the forum which I can't link because of the restrictions .
Then I used thread 1672425 to put S-ON again and now my One it back to full stock!

[Q] RUU is stuck at "Checking Header", can't go back to stock

Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
F:\fastboot>fastboot getvar all
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.09.401.1
version-misc: PVT SHIP S-OFF
serialno: SH35JWxxxxx
imei: 354436056xxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4279mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-f361905d64
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.064s
Click to expand...
Click to collapse
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
OKAY [ 67.418s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 67.608s
Click to expand...
Click to collapse
Can anyone point me in the right direction here? I don't really know what else to try.

fBx said:
Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
Can anyone point me in the right direction here? I don't really know what else to try.
Click to expand...
Click to collapse
you already have a thread here: http://forum.xda-developers.com/showthread.php?t=2796167 for the same issue. why a 2nd one?
btw you don't need to relock bootloader to flash ruu when the phone is s-off.

Would it work to flash a nandroid backup of an original german unbranded phone via CWM?

fBx said:
Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
Can anyone point me in the right direction here? I don't really know what else to try.
Click to expand...
Click to collapse
I have the same problem, How did you fix?

maxwilliam100 said:
I have the same problem, How did you fix?
Click to expand...
Click to collapse
try to flash the firmware first

alray said:
try to flash the firmware first
Click to expand...
Click to collapse
Thanks for the tip @alray
I'm downloading the firmware and will defenately follow directions form this link
trjlive (dot) com/guide-install-firmware-htc-one-m7/
In the meantime here is the info from my phone
HTML:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxx
imei: xxxxxxxxxxxxxxxx
meid: 99000146508682
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: 11111111
battery-status: good
battery-voltage: 3947mV
partition-layout: Generic
ecurity: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-371c4f408e
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.072s

maxwilliam100 said:
Thanks for the tip @alray
I'm downloading the firmware and will defenately follow directions form this link
trjlive (dot) com/guide-install-firmware-htc-one-m7/
In the meantime here is the info from my phone
HTML:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: 11111111
battery-status: good
battery-voltage: 3947mV
partition-layout: Generic
ecurity: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-371c4f408e
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Wait, you have a sprint phone? Hope you ar enot trying to flash this 4.19.401.9 ruu for GSM phones?
Btw you have s-off, you can use every ruu intended for sprint variant m7wls (x.xx.651.x RUU). Do not attempt to flash ruu for GSM variants. You should also set back your cid to its original value (SPCS_001).
And remove your S/N, IMEI and MEID numbers from your above post, these are sensitive data you want to keep for yourself.

alray said:
Wait, you have a sprint phone? Hope you ar enot trying to flash this 4.19.401.9 ruu for GSM phones?
Btw you have s-off, you can use every ruu intended for sprint variant m7wls (x.xx.651.x RUU). Do not attempt to flash ruu for GSM variants. You should also set back your cid to its original value (SPCS_001).
And remove your S/N, IMEI and MEID numbers from your above post, these are sensitive data you want to keep for yourself.
Click to expand...
Click to collapse
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg

maxwilliam100 said:
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
Click to expand...
Click to collapse
your fastboot getvar and bootloader revels you have a Sprint phone .. Use Only Sprint Files
http://forum.xda-developers.com/sprint-htc-one

maxwilliam100 said:
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
Click to expand...
Click to collapse
M7_WLS = Sprint = CDMA phone = different partition table = flash a ruu not for sprint and you'll end with a bricked phone.
use a x.xx.651.x ruu for cid SPCS_001 and mid PN0720000 only
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
and do not use windows 8 to flash it or you'll be stuck
use windows 7, MacOs or linux.

alray said:
M7_WLS = Sprint = CDMA phone = different partition table = flash a ruu not for sprint and you'll end with a bricked phone.
use a x.xx.651.x ruu for cid SPCS_001 and mid PN0720000 only
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
and do not use windows 8 to flash it or you'll be stuck
use windows 7, MacOs or linux.
Click to expand...
Click to collapse
@maxwilliam100
theirs also
Sprint 4.xx RUU
https://www.androidfilehost.com/?fid=23329332407573774
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856

Thank you very much @alray and @clsA
I'm now downloading this ruu and since its at zip then i think i will have to rename the zip file to ruu.zip and flash from
fastboot oem rebootRUU
fastboot flash zip ruu.zip
Click to expand...
Click to collapse
Is there anything else that i should be aware of?

maxwilliam100 said:
Thank you very much @alray and @clsA
I'm now downloading this ruu and since its at zip then i think i will have to rename the zip file to ruu.zip and flash from
Is there anything else that i should be aware of?
Click to expand...
Click to collapse
you may have to do the fastboot flash zip ruu.zip 2 times

clsA said:
you may have to do the fastboot flash zip ruu.zip 2 times
Click to expand...
Click to collapse
Thanks Guys,
After three weeks of googling every available thing and failure, i came here as my last hope... PM random people on the internet and youtube..... without any success
Many thanks to @alray and @clsA
:highfive:

[SOLVED] Reverting back to stock with RUU - Error 158 Image Error

Hi!
So I have a problem with my M7 and I need to return it to stock so that I can send it back to HTC for repair. I have downloaded the "RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2" from here (multiple times to check if I had a corrupted download or something like that).
Every time I run the RUU it reboots it to the black HTC screen then gives me the error message
Code:
ERROR [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
My bootloader is Unlocked (though I have tried it with Relocked). I first tried with SuperCId then I did
Code:
fastboot oem writecid O2___001
(that's 3 underscores - I think that is right!) to put it back to the O2 UK cid and I get the same error. Below is what
Code:
fastboot getvar all
returns.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.063s
I'm almost certain that this is the correct RUU I should be using.
Can anybody help or tell me why it's going wrong? Thanks in advance!

One thing I forgot to mention - I have previously flashed an RUU zip file from here when I had super cid to unbrick my device. Might that have something to do with it?

HapticThreek said:
One thing I forgot to mention - I have previously flashed an RUU zip file from here when I had super cid to unbrick my device. Might that have something to do with it?
Click to expand...
Click to collapse
Your version main says your on a 401 ruu, your trying to run a 206 ruu, I would change the cid back to HTC__001 and run the 401.ruu personally.
158 error specifies wrong ruu

Seanie280672 said:
Your version main says your on a 401 ruu, your trying to run a 206 ruu, I would change the cid back to HTC__001 and run the 401.ruu personally.
158 error specifies wrong ruu
Click to expand...
Click to collapse
That sounds like it's because I flashed the wrong RUU before then. I thought with super cid I should be able to flash any RUU?
Do you know if there's any way to get my version main back to 206 (which I'm fairly sure it was before I flashed the first ruu), or to get the O2 UK ruu to reflash the version main?
The reason I ask is because the phone has already been sent to HTC for repair once so they would probably know what software was on it when it was returned to me.
Thanks
EDIT: the cid was always O2___001 before I got supercid to unbrick phone. I have used this RUU previously on this phone successfully.

HapticThreek said:
That sounds like it's because I flashed the wrong RUU before then. I thought with super cid I should be able to flash any RUU?
Do you know if there's any way to get my version main back to 206 (which I'm fairly sure it was before I flashed the first ruu), or to get the O2 UK ruu to reflash the version main?
The reason I ask is because the phone has already been sent to HTC for repair once so they would probably know what software was on it when it was returned to me.
Thanks
EDIT: the cid was always O2___001 before I got supercid to unbrick phone. I have used this RUU previously on this phone successfully.
Click to expand...
Click to collapse
You could try setting super cid first, run the O2 ruu and after its finished then set the phone to the O2 cid, or, you could pull the firmware zip from the ruu, force flash that and then run the ruu.

Seanie280672 said:
You could try setting super cid first, run the O2 ruu and after its finished then set the phone to the O2 cid, or, you could pull the firmware zip from the ruu, force flash that and then run the ruu.
Click to expand...
Click to collapse
Thanks, I'll give the second one a shot first. Will the firmware.zip be in the temp folder/rom.zip?

HapticThreek said:
Thanks, I'll give the second one a shot first. Will the firmware.zip be in the temp folder/rom.zip?
Click to expand...
Click to collapse
Yes, when you run the ruu it unpacks itself to a temp folder on your pc, right before you accept the license agreement, find the temp.folder and pull the firmware.zip from the Rom

Seanie280672 said:
Yes, when you run the ruu it unpacks itself to a temp folder on your pc, right before you accept the license agreement, find the temp.folder and pull the firmware.zip from the Rom
Click to expand...
Click to collapse
When I go to extract the rom.zip file I get the message that the archive is corrupt and that CRC data failed in dzdata_32g.img and dzdata_64g.img.
I have tried this on multiple downloads which I have verified the md5 hashes. Using winrar to extract - should I be using something else?
EDIT - quick search tells me its because its encrypted - will look for decrypting solutions

HapticThreek said:
When I go to extract the rom.zip file I get the message that the archive is corrupt and that CRC data failed in dzdata_32g.img and dzdata_64g.img.
I have tried this on multiple downloads which I have verified the md5 hashes. Using winrar to extract - should I be using something else?
EDIT - quick search tells me its because its encrypted - will look for decrypting solutions
Click to expand...
Click to collapse
Yeah, sorry for the slow reply, its because its encrypted, try this
http://forum.xda-developers.com/showthread.php?t=2084470

Seanie280672 said:
Yeah, sorry for the slow reply, its because its encrypted, try this
http://forum.xda-developers.com/showthread.php?t=2084470
Click to expand...
Click to collapse
Hi, thanks very much. So I have extracted the rom.zip, for some reason it split it into 5 zip files. Unfortunately for me none of these zips contained the firmware.zip file you spoke about (or any other zip file).
I think what happened is it extracted what was in the zips too. One of the extracted zips contained the following files:
adsp.img
android-info.txt
cir.img
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
ramdisk.img
rcdata.img
recovery_signed.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
splash1.nb0
tp_SYN3202.img
tz.img
Am I right in thinking this is the firmware zip file? ( I hope! lol )

HapticThreek said:
Hi, thanks very much. So I have extracted the rom.zip, for some reason it split it into 5 zip files. Unfortunately for me none of these zips contained the firmware.zip file you spoke about (or any other zip file).
I think what happened is it extracted what was in the zips too. One of the extracted zips contained the following files:
adsp.img
android-info.txt
cir.img
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
ramdisk.img
rcdata.img
recovery_signed.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
splash1.nb0
tp_SYN3202.img
tz.img
Am I right in thinking this is the firmware zip file? ( I hope! lol )
Click to expand...
Click to collapse
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/

Seanie280672 said:
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/
Click to expand...
Click to collapse
Hi, so I did that and followed the guide, unfortunately hasn't worked. get the following when I run fastboot flash zip firmware.zip:
Code:
sending 'zip' (41218 KB)...
OKAY [ 3.118s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 3.396s
Does it need to be re-encrypted or something?
EDIT - actually think the firmware.zip is already encrypted still. trying to see if I can decrypt it.
trying to unzip it gives me "invalid compressed data to inflate" error
EDIT 2 - seems like I'm getting the same issue as this dude http://forum.xda-developers.com/showpost.php?p=49519579&postcount=155. Will look for a different way to decrypt rom.zip

Seanie280672 said:
Yup that's firmware.zip, all the system files etc, just zip those files back up into one zip, name it firmware.zip and flash it, don't forget to flash it twice, make sure on the 2nd time it says successful at the end, if it says anything else do not restart your phone, it will brick, you will need to find another firmware to flash whilst the phone is still in RUU mode.
see here: http://trjlive.com/guide-install-firmware-htc-one-m7/
Click to expand...
Click to collapse
So managed to decrypt properly and flash. Woohoo!
Here is the new output for fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3830mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-44d68d6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s
Version main now has the 206 in it so hopefully when I get to try the RUU again tomorrow it works, fingers crossed and thanks for all your input so far, you've been really helpful!
EDIT - should have waited til tomorrow to flash this firmware - touch screen is non functional now! bah. Hopefully ruu works tomorrow!

SOLVED
Well, the RUU worked this time and I now have a fully stock phone to return.
Thanks for all your help and pointing me in the right directions. Will hit the thanks button on your posts!

[Q] Cyanogen to clean sense 6 kitkat

Hi,
I`ve had my fun tuning my htc one, but i`ve no clue how to get it to normal m7 phone with sense 6 lol.
I`ve got TWRP and running the OTA rom does not do anything. Am I trying with the incorrect rom or what?
Thanks for any feedback!

sycorax1337 said:
Hi,
I`ve had my fun tuning my htc one, but i`ve no clue how to get it to normal m7 phone with sense 6 lol.
I`ve got TWRP and running the OTA rom does not do anything. Am I trying with the incorrect rom or what?
Thanks for any feedback!
Click to expand...
Click to collapse
First, we will need to see a fastboot getvar all with the imei and serialno removed. This is needed to know which variant/version of the HTC One M7 you have, so we can point you in the right direction.
Second, OTA's are update files for stock roms with stock recovery for specific versions. If you don't have the correct combination then it will not run properly.
Third, here is a guide for going back to stock. You probably don't want to go to 100% stock but it shows you the proper steps.

majmoz said:
First, we will need to see a fastboot getvar all with the imei and serialno removed. This is needed to know which variant/version of the HTC One M7 you have, so we can point you in the right direction.
Second, OTA's are update files for stock roms with stock recovery for specific versions. If you don't have the correct combination then it will not run properly.
Third, here is a guide for going back to stock. You probably don't want to go to 100% stock but it shows you the proper steps.
Click to expand...
Click to collapse
Sorry, my bad
Code:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__001
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0

sycorax1337 said:
Sorry, my bad
Code:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: H3G__001
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I can not find a RUU for your phone but I did find a GURU Stock Reset: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
Guru Reset file are simply Stock ROM’s packaged with the nice graphical interface of the aroma installer. They include the stock radio and stock recovery, so if you are still S-on then this is best way to reset to stock. It can’t change your firmware but it can get the stock ROM installed with the stock recovery so that you can get OTA updates and it should also remove the Tampered text from your bootloader.
Click to expand...
Click to collapse
There is an OTA at this site for your phone.
I would try to get S-OFF before doing the Stock Reset it would give you more flexibility. If firewater doesn't work to get S-OFF then view this post about a service in the UK.

majmoz said:
I can not find a RUU for your phone but I did find a GURU Stock Reset: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
There is an OTA at this site for your phone.
I would try to get S-OFF before doing the Stock Reset it would give you more flexibility. If firewater doesn't work to get S-OFF then view this post about a service in the UK.
Click to expand...
Click to collapse
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?

sycorax1337 said:
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
Click to expand...
Click to collapse
Try the sideload method. Make sure HTC Drivers are installed and ADB is already working. If not, then check out this FAQ Post.
1. Reboot into TWRP
2. In TWRP, hit ADVANCED and find SIDELOAD
3. Swipe to start the SIDELOAD
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. Type adb devices and it should show your device connected and say SIDELOAD
6. Your ZIP file should already be in your adb folder
7. You are now ready to push the zip.....
8. Type adb sideload nameofzip.zip
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. If adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery

sycorax1337 said:
After installing that GURU stock reset, and updating to sense 5.5, the phone stuck in a reboot loop.
I can get to TWRP within recovery, but I cant push any ROM to the phone so I can use it. Tried the push command, in fastboot mode and command prompt prints message device not found. What am I missing?
Click to expand...
Click to collapse
You can't use that guru reset file, it's too low for your hboot version, the only way you can use it is to downgrade your hboot and the only way you can do that is to get s-off, the otas are putting you into a bootloop because they are trying to upgrade your hboot and as you already have the latest hboot they can't complete that task.
Your stuck with custom roms unless you can get your phone s-off, or find a nandroid backup of your latest rom.
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
as for your driver problem, see FAQ 2 here by nkk71 http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

Mate I have same problem like you. No way to bring a phone to life. I try a custom and lot of ruu, but nothing with some ruu i got error 155, and 130. With CyanogenMod, using sideload i got error on the phone, and nothing instal.
Hire is my getvar all.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.00
INFOversion-baseband: 4T.27.321
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4331mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e47fb74b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.069s
C:\ADB>
People help us to get alive our phones...

Errornt said:
Mate I have same problem like you. No way to bring a phone to life. I try a custom and lot of ruu, but nothing with some ruu i got error 155, and 130. With CyanogenMod, using sideload i got error on the phone, and nothing instal.
Hire is my getvar all.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.57.00
INFOversion-baseband: 4T.27.321
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4331mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-e47fb74b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.069s
C:\ADB>
People help us to get alive our phones...
Click to expand...
Click to collapse
First, remove the imei and serialno from your original post!
Second, I have had problems running RUU because the hboot was too high. Since, you are S-OFF you can downgrade your hboot then install the RUU. This post will explain the procedure. When the RUU executes it will change your hboot to that of the RUU.

Ok thx mate, I downgrade my Hboot to 1.44.000. Here is log.
Code:
C:\ADB>fastboot flash zip 1.29.401.12_hboot_1.44.zip
sending 'zip' (501 KB)... OKAY [ 0.261s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,50
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
OKAY [ 2.339s]
finished. total time: 2.602s
C:\ADB>
Then I try flash firmware above in this theard, and got faill in CMD, hire is log.
Code:
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 48.690s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.696s
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 48.494s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.753s
C:\ADB>fastboot flash zip C:\adb\firmware.zip
sending 'zip' (733251 KB)... OKAY [ 66.921s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 74.199s
Is it possible to my eMMC-boot is death. There is no size text. Look @ picture.
After i flash a new HBOOT text has gone 2048MB

Did you put your phone into ruu mode before trying to flash the firmware ?
Code:
fastboot oem rebootRUU

Seanie280672 said:
Did you put your phone into ruu mode before trying to flash the firmware ?
Code:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Yes mate, the black screen with HTC text.
Can somebody tell me what region is my phone, i buy it from internet and I dont know what RUU to download, to try flash it.

Errornt said:
Yes mate, the black screen with HTC text.
Can somebody tell me what region is my phone, i buy it from internet and I dont know what RUU to download, to try flash it.
Click to expand...
Click to collapse
Well your on 401 which is WWE Europe, same as the hboot you flashed, so you need to flash an ruu or a firmware which is 4.xx.401.xx however I see what your problem is, you have super cid, 401 android-info.txt doesn't have super cid in it, change your cid to HTC__001 then reboot bootloader and try flash the firmware zip again.

Seanie280672 said:
Well your on 401 which is WWE Europe, same as the hboot you flashed, so you need to flash an ruu or a firmware which is 4.xx.401.xx however I see what your problem is, you have super cid, 401 android-info.txt doesn't have super cid in it, change your cid to HTC__001 then reboot bootloader and try flash the firmware zip again.
Click to expand...
Click to collapse
Ok so i need to change my cid to HTC__001 and then flash Some WWE Europe RUU, can you give me a link of some ruu that you thing its good for me. (thx).
Sorry for my bad English.
Edit: I edited my CID to HTC__001 so now I need good RUU to flash it. I woud like to have a orginal rom, but i will be happy if I get my phone on with any custom rom if not with oem.

Errornt said:
Ok so i need to change my cid to HTC__001 and then flash Some WWE Europe RUU, can you give me a link of some ruu that you thing its good for me. (thx).
Sorry for my bad English.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
You may need to find the 4.19.401.9 firmware and flash that first.

I got ERROR 158 IMAGE ERROR, when i try to flash this RUU.
My radio is 4T, and this RUU is 4A is that problem?

Errornt said:
I got ERROR 158 IMAGE ERROR, when i try to flash this RUU.
My radio is 4T, and this RUU is 4A is that problem?
Click to expand...
Click to collapse
Nope, you need to find the corrisponding firmware and flash that first like I said before , you need 4.19.401.9 firmware.zip, flash that first then run the ruu

Seanie280672 said:
Nope, you need to find the corrisponding firmware and flash that first like I said before , you need 4.19.401.9 firmware.zip, flash that first then run the ruu
Click to expand...
Click to collapse
Can you give me more details how to make that to flash 4.19.401.9 firmware.zip, and how to flash it, with cmd? fastboot? Should be unlocked or relocked? when flashing that firmware, and can you help me to find that firmware on the net, because i dont know what i need to search. :angel:

Errornt said:
Can you give me more details how to make that to flash 4.19.401.9 firmware.zip, and how to flash it, with cmd? fastboot? Should be unlocked or relocked? when flashing that firmware, and can you help me to find that firmware on the net, because i dont know what i need to search. :angel:
Click to expand...
Click to collapse
You will have to wait till I get home from work in a few hours for all of that or do a bit of reading and searching

what firmware are you after?

Display mesed up.

Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
C:\sdk tools\sdk-tools>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: HT354W913005
(bootloader) imei: 356378050014257
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3925mV
(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.078s
C:\sdk tools\sdk-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.051s
C:\sdk tools\sdk-tools>fastboot flash zip aman.zip
target reported max download size of 1526722560 bytes
sending 'zip' (479 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.125s]
finished. total time: 2.375s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk tools\sdk-tools>fastboot oem writecid BS_US001
...
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.063s]
finished. total time: 0.063s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?

General Al Capo said:
Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?
Click to expand...
Click to collapse
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
Click to expand...
Click to collapse
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery

clsA said:
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery
Click to expand...
Click to collapse
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54

General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
your phone was Google play edition ... I hope you did not relock the bootloader, their is no way to unlock a bootloader on the GPe
the fastboot flash zip aman.zip may have been the fatal mistake. If you can not flash another hboot over it your screwed as far as I can tell.
Maybe @alray or @Danny201281 or @nkk71 can help you

General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZ...ew?usp=sharing.
Click to expand...
Click to collapse
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.

alray said:
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.
Click to expand...
Click to collapse
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.

General Al Capo said:
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.
Click to expand...
Click to collapse
Uninstall HTC Sync leave the driver
What happened to the Google play RUU.zip I linked you too?
Your not ready to flash the Developer RUU yet.
Get the phone back working with the RUU I linked first.
I use Windows 8.1 every day it only affects HTC One with hboot 1.44
You have hboot 1.54 it should work fine

clsA said:
You have hboot 1.54 it should work fine
Click to expand...
Click to collapse
Not after he flashed the modded hboot. He is now on Hboot 1.43 so he will need win 7

The problem is everytime i write fastboot oem rebootRUU the device restarts.

General Al Capo said:
The problem is everytime i write fastboot oem rebootRUU the device restarts.
Click to expand...
Click to collapse
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).

alray said:
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).
Click to expand...
Click to collapse
I did that.At the end it says error-please get the correct rom utility.

General Al Capo said:
I did that.At the end it says error-please get the correct rom utility.
Click to expand...
Click to collapse
still not answered my crucial question from post #5 :
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
Click to expand...
Click to collapse
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.

Andriod info of RUU
modelid: PN0712000
cidnum: BS_US001
cidnum: BS_US002
mainver: 7.17.1540.7
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
getvar all
C:\abc\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT ENG S-OFF
(bootloader) serialno: HT354W913005
(bootloader) imei: 356378050014257
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.130s
C:\abc\sdk-tools>
Click to expand...
Click to collapse
alray said:
still not answered my crucial question from post #5 :
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.
Click to expand...
Click to collapse
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.

General Al Capo said:
Andriod info of RUU
getvar all
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.
Click to expand...
Click to collapse
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?

alray said:
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?
Click to expand...
Click to collapse
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.

General Al Capo said:
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.
Click to expand...
Click to collapse
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.

alray said:
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.
Click to expand...
Click to collapse
Thanks for your help:good:.Will try this RUU after downloading it.

The RUU you gave me worked like a charm.Thank you for your assistance.

General Al Capo said:
The RUU you gave me worked like a charm.Thank you for your assistance.
Click to expand...
Click to collapse
glad to know everything is fine now. Don't forget if you want to convert your device again to another version, use the method clsA posted at first page. Very much easier and safer. The whole procedure is now done using a GUI (aroma installer) from a custom recovery.