Database Develop

Converted TMobile USA to GPE. can't flash other RUU's

Hey guys,
I have a tmobile usa htc one that I converted to GPE. I did so through a GPE RUU zip file. I used the command fastboot flash zip "RUU zip file here".zip. My phone successfully converted and a dark bootloader replaced my white bootloader with the red warning sign.
Now the problem is when I try to flash another RUU zip... lets say Stock Tmobile HTC one, or Developers ROM RUU, I always got an error message. I know I can flash a sense based rom onto my phone, but I want the option to revert back to stock, Developers edtion.
How do I go on about this? someone help :crying:
I'd greatly appreciate it.

itsmarkiemark said:
Hey guys,
I have a tmobile usa htc one that I converted to GPE. I did so through a GPE RUU zip file. I used the command fastboot flash zip "RUU zip file here".zip. My phone successfully converted and a dark bootloader replaced my white bootloader with the red warning sign.
Now the problem is when I try to flash another RUU zip... lets say Stock Tmobile HTC one, or Developers ROM RUU, I always got an error message. I know I can flash a sense based rom onto my phone, but I want the option to revert back to stock, Developers edtion.
How do I go on about this? someone help :crying:
I'd greatly appreciate it.
Click to expand...
Click to collapse
maybe you should start by posting your ''fastboot getvar all'' minus imei/sn and give us a link to the ruu that failed to install. Also:
I always got an error message
Click to expand...
Click to collapse
doesnt say much. you should write down that exact error code you get.

alray said:
maybe you should start by posting your ''fastboot getvar all'' minus imei/sn and give us a link to the ruu that failed to install. Also:
doesnt say much. you should write down that exact error code you get.
Click to expand...
Click to collapse
I tried to flash this:
http://www.htc1guru.com/dld/ruu-zip...157-04_release_336982_signed_2_decrypted-zip/
& this
http://www.htc1guru.com/dld/ruu-zip...r_brightstarus_wwe_3-22-1540-1-decrypted-zip/
my get varinfo is
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Private dont mind this, I added this to block my serialno
(bootloader) imei: Private dont mind this, i added this to block my imei
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4206mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
and the error message when trying to flash RUUs is this:
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip RUU Zip M7_UL_JB_50_Brigh
tstarUS_WWE_1.29.1540.3.zip
target reported max download size of 1526722560 bytes
error: cannot load 'RUU': No error

itsmarkiemark said:
fastboot flash zip RUU Zip M7_UL_JB_50_Brigh
tstarUS_WWE_1.29.1540.3.zip
target reported max download size of 1526722560 bytes
error: cannot load 'RUU': No error
Click to expand...
Click to collapse
''fastboot flash zip RUU name_of_file.zip'' is not a valid command...
you need to flash this way:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip -----> yes again
fastboot reboot-bootloader

alray said:
''fastboot flash zip RUU name_of_file.zip'' is not a valid command...
you need to flash this way:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip -----> yes again
fastboot reboot-bootloader
Click to expand...
Click to collapse
Even if RUU is apart of the zip name? Because I just copy and pasted the name of the file onto the commandline.
And yes the command you gave me is how I converted to GPE. I also just copy and pasted the zip file name into the command. I just don't remember if the GPE zip had Ruu in the start of the name
Anyways;
I'll just rename the zip file to see what happens
Thanks

itsmarkiemark said:
Even if RUU is apart of the zip name? Because I just copy and pasted the name of the file onto the commandline.
And yes the command you gave me is how I converted to GPE. I also just copy and pasted the zip file name into the command. I just don't remember if the GPE zip had Ruu in the start of the name
Anyways;
I'll just rename the zip file to see what happens
Thanks
Click to expand...
Click to collapse
yes try renaming it to something simpler without space

alray said:
yes try renaming it to something simpler without space
Click to expand...
Click to collapse
tried flashing wwith a simple name and I got this
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip DeveloperEdition.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1004448 KB)...
OKAY [ 33.872s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 37.590s
I guess it doesnt like my model ID?

itsmarkiemark said:
tried flashing wwith a simple name and I got this
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip DeveloperEdition.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1004448 KB)...
OKAY [ 33.872s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 37.590s
I guess it doesnt like my model ID?
Click to expand...
Click to collapse
If you want to flash the dev edition ruu, you'll need to change mid to dev edition (PN0712000)
---------- Post added at 04:14 AM ---------- Previous post was at 04:11 AM ----------
itsmarkiemark said:
tried flashing wwith a simple name and I got this
C:\Users\mm\Desktop\Android\HTC ONE>fastboot flash zip DeveloperEdition.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1004448 KB)...
OKAY [ 33.872s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 37.590s
I guess it doesnt like my model ID?
Click to expand...
Click to collapse
its easy to do with s-off, just use this tool

alray said:
If you want to flash the dev edition ruu, you'll need to change mid to dev edition (PN0712000)
---------- Post added at 04:14 AM ---------- Previous post was at 04:11 AM ----------
its easy to do with s-off, just use this tool
Click to expand...
Click to collapse
right now im using the htc one toolkit. I think i can change the model id.
just to be clear is the meid from getvar info the model ID?
btw is there a list thread with a full list of MID and CID? because ive tried looking all around XDA and google.
just in case I want to go back to Tmobile stock.

itsmarkiemark said:
right now im using the htc one toolkit. I think i can change the model id.
just to be clear is the meid from getvar info the model ID?
btw is there a list thread with a full list of MID and CID? because ive tried looking all around XDA and google.
just in case I want to go back to Tmobile stock.
Click to expand...
Click to collapse
not meid, modelid.
you always need to match mid and cid to the ruu you want to use. when you download the ruu from htc1guru.com the required mid and cid are listed in the download page.
htc cid list here
htc one mid almost all listed here here
so for dev edition you need cid: BS_US001 and MID PN0712000
I'll recommand you use that tool I linked to you to change mid.
for cid just do this
Code:
fastboot oem writecid BS_US001
fastboot reboot
from htc1guru.com:
File Size 1.1 GiB
Downloads 3759
Comments Developer Edition
modelid: PN0712000
cid: BS_US001
MD5 ed60a68fe040ea4437cdd7e56c9fae0c
Support Ask Questions and find General Support info for this file here: http://forum.xda-developers.com/showthread.php?t=2428276
Click to expand...
Click to collapse

alray said:
not meid, modelid.
you always need to match mid and cid to the ruu you want to use. when you download the ruu from htc1guru.com the required mid and cid are listed in the download page.
htc cid list here
htc one mid almost all listed here here
so for dev edition you need cid: BS_US001 and MID PN0712000
I'll recommand you use that tool I linked to you to change mid.
for cid just do this
Code:
fastboot oem writecid BS_US001
fastboot rebot
Click to expand...
Click to collapse
Thanks... will try this right now
but one last question. will 4GLTE work if i change the CID? I never payed attention what were my MID and CID were before I flashed the GPE RUU. but its obvious that the CID didnt change since its still tmo-010. I was under the impression that flashing a RUU will change everything. I guessing it doesnt since I need to change the CID and MID to flash the Developer RUU

thanks! I did your steps and RUU is flashing as we speak.
appreciate the help. You have my many thanks!

itsmarkiemark said:
thanks! I did your steps and RUU is flashing as we speak.
appreciate the help. You have my many thanks!
Click to expand...
Click to collapse
np, if you appreciated the help please click the ''thanks'' button bellow my posts

alray said:
np, if you appreciated the help please click the ''thanks'' button bellow my posts
Click to expand...
Click to collapse
already did mate:highfive:

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

[Q] Can't S-ON?

After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!

Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.

Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.

nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.

Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)

nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?

Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.

nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.

Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware

nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.

Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe

nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.

Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.

nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-

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

[Q] (Q) Lollipop soft brick help please

Hi all,
My friend handed me his HTC One M7 the other day and it was looping at the beginning Android / HTC screen from boot, he took the lollipop update but it failed somewhere along the way and this is how it's ended up.
The device is not rooted and is not bootloader unlocked, i've tried to flash a few RUU files to bring it back to life but the vast majority of them only get as far as 1/5 checking header.
I'm more than happy to root the device and install a custom rom but I wasn't sure if it needed to be bootable to do so, afaik the bootloader unlocking doesn't require to have the device on, infact I don't think you need to have the OS to get a custom recovery either? Anyway, i'd like for him to retain his warranty so if there's a way for him to get it back to stock HTC then i'd prefer to do that.
If that's not possible and unlocking the bootloader, installing a custom rom is then I'll do that.
Any help would be greatly appreciated.
Many thanks.
PS: I have had the m7 before but I didn't have it when android 5 was available so i'm a little out of touch with what may go wrong.

dladz said:
Hi all,
My friend handed me his HTC One M7 the other day and it was looping at the beginning Android / HTC screen from boot, he took the lollipop update but it failed somewhere along the way and this is how it's ended up.
The device is not rooted and is not bootloader unlocked, i've tried to flash a few RUU files to bring it back to life but the vast majority of them only get as far as 1/5 checking header.
I'm more than happy to root the device and install a custom rom but I wasn't sure if it needed to be bootable to do so, afaik the bootloader unlocking doesn't require to have the device on, infact I don't think you need to have the OS to get a custom recovery either? Anyway, i'd like for him to retain his warranty so if there's a way for him to get it back to stock HTC then i'd prefer to do that.
If that's not possible and unlocking the bootloader, installing a custom rom is then I'll do that.
Any help would be greatly appreciated.
Many thanks.
PS: I have had the m7 before but I didn't have it when android 5 was available so i'm a little out of touch with what may go wrong.
Click to expand...
Click to collapse
Connect the phone to your computer, Boot it in bootloader mode select "fastboot" mode and make sure "fastboot usb" is shown in red. Open a fastboot command prompt:
Code:
fastboot getvar all
post the output here but make sure to hide the imei and serialno before posting.

Thanks mate I'm in bed at the moment but will do after work tomorrow,, Appreciate your help, im guessing this is to see what firmware is installed? Or hboot? I'll come back tomorrow, Many thanks.

dladz said:
Thanks mate I'm in bed at the moment but will do after work tomorrow,, Appreciate your help, im guessing this is to see what firmware is installed? Or hboot? I'll come back tomorrow, Many thanks.
Click to expand...
Click to collapse
Firmware, hboot, CID, MID, S-ON/S-OFF, M7_UL/M7_U

Checking header 1/5..ill give you a clue...your ruu that you going to flash,it has to match firmware that is on it now...as you are s-on,you cant change firmware.so,try with other ruu's,some that maches firmware number..not older,not newer.
And like others said,give them "getvar all" info.
Sent from my HTC One using XDA Free mobile app

Chaps you are both legends, I'm just running round getting ready for work. I'll jump on this when I get home. Appreciate your help. Thanks.

alray said:
Connect the phone to your computer, Boot it in bootloader mode select "fastboot" mode and make sure "fastboot usb" is shown in red. Open a fastboot command prompt:
Code:
fastboot getvar all
post the output here but make sure to hide the imei and serialno before posting.
Click to expand...
Click to collapse
C:\ANDROID SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W909506
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3596mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Here you go mate.
currently downloading this https://www.androidfilehost.com/?fid=95832962473396760 it's for version 6.09.401.11 which was listed.
Unless there's something i'm supposed to do.

dladz said:
C:\ANDROID SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W909506
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3596mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Here you go mate.
currently downloading this https://www.androidfilehost.com/?fid=95832962473396760 it's for version 6.09.401.11 which was listed.
Unless there's something i'm supposed to do.
Click to expand...
Click to collapse
Would recommend to simply flash the latest ruu (7.19.401.2) which will fix and update the phone to the latest version.
Instructions and file here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
Would recommend to simply flash the latest ruu (7.19.401.2) which will fix and update the phone to the latest version.
Instructions and file here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
I did actually try that one mate, that's how i got the 1/5 checking headers problem, and it simply doesn't go any further, i'll give it another whirl but as far as i can remember it was that version.
brb after checking.
Actually I didn't flash one of these but the version does ring a bell. Downloading now mate.
The previous one i mentioned i flash via fastboot flash zip but it still loops, 20 mins until that one downloads. Will let you know and thank you by the way.

dladz said:
I did actually try that one mate, that's how i got the 1/5 checking headers problem, and it simply doesn't go any further, i'll give it another whirl but as far as i can remember it was that version.
brb after checking.
Actually I didn't flash one of these but the version does ring a bell. Downloading now mate.
Click to expand...
Click to collapse
Im almost sure you were trying to flash the 4.xx.401.x version not the one I have linked above.

alray said:
Im almost sure you were trying to flash the 4.xx.401.x version not the one I have linked above.
Click to expand...
Click to collapse
I flashed this one https://www.androidfilehost.com/?fid=95832962473396760 which is 6.09.401.11 but it didn't work, not to worry anyway, i'll give the one you linked to a whirl too, just waiting for it to download, 10 mins left.

dladz said:
i'll give the one you linked to a whirl too, just waiting for it to download, 10 mins left.
Click to expand...
Click to collapse
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot

alray said:
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
Oh really? Why didn't i know this !? See I've been gone from HTC for far too long, should be getting the M9 soon though. One of my contracts expires soon, i've got a few, need to check on them. You thinking of getting the M9 ? Think Samsung has made a mistake going with the Exynos.
Ok it's downloaded, i'll grab that fastboot and give it a whirl. Fingers crossed.

alray said:
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
Ok i got this
C:\HTC Fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\HTC Fastboot>fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.4
01.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip
sending 'zip'... (43287 KB) OKAY
sending time = 2.844 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 9(s)
C:\HTC Fastboot>
Rebooting.
EDIT: Bootloop mate.

dladz said:
Oh really? Why didn't i know this !? See I've been gone from HTC for far too long, should be getting the M9 soon though. One of my contracts expires soon, i've got a few, need to check on them. You thinking of getting the M9 ? Think Samsung has made a mistake going with the Exynos.
Click to expand...
Click to collapse
I'll might grab the M9 later this year when the price will drop a bit. I'm still satisfied with my M7 and doesn't feel like I need something more.
Ok it's downloaded, i'll grab that fastboot and give it a whirl. Fingers crossed
Click to expand...
Click to collapse
Dont forget you'll need the dll files in the same folder where you have htc's fastboot and the ruu. You can simply replace fastboot.exe with htc's fastboot in your sdk folder were the required dll files are
---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------
dladz said:
Ok i got this
C:\HTC Fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\HTC Fastboot>fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.4
01.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip
sending 'zip'... (43287 KB) OKAY
sending time = 2.844 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 9(s)
C:\HTC Fastboot>
Click to expand...
Click to collapse
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
alray said:
Would recommend to simply flash the latest ruu (7.19.401.2)
Click to expand...
Click to collapse

alray said:
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
Click to expand...
Click to collapse
Just copied the HTC fastboot into the SDK platforms and tools folder, reflashing now.

dladz said:
Just copied the HTC fastboot into the SDK platforms and tools folder, reflashing now.
Click to expand...
Click to collapse
read my post above you are flashing the wrong ruu. You need 4.19.401.2 not 4.19.401.102

alray said:
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
Click to expand...
Click to collapse
Ah, idiot. Sorry
Couldn't see a european one though? This device is unlocked, wouldn't it have the providers software on otherwise?

Ok downloading, sorry mate, my eyes are failing me, getting old.

Ok so I think it's all done mate, looks like it's going to load up, I mean the script has finished running but the green bar is still onscreen.