Database Develop

[Q] Returning to stock for warranty repair

Hi All,
I want to return ENTIRELY to stock so that it is untraceable that I ever wasn't on stock. I have to send my phone to HTC for repair and do not want to be charged for the repairs.
I appreciate there are many threads for this, mainly this one: http://forum.xda-developers.com/showthread.php?t=2358738
However I wanted to confirm this will work for me and be untraceable. I understand I can provide you with information about my phone which may be required?
Any assistance greatly appreciated.

Jimzoaar said:
Hi All,
I want to return ENTIRELY to stock so that it is untraceable that I ever wasn't on stock. I have to send my phone to HTC for repair and do not want to be charged for the repairs.
I appreciate there are many threads for this, mainly this one: http://forum.xda-developers.com/showthread.php?t=2358738
However I wanted to confirm this will work for me and be untraceable. I understand I can provide you with information about my phone which may be required?
Any assistance greatly appreciated.
Click to expand...
Click to collapse
you can also check out my guide: http://forum.xda-developers.com/showthread.php?t=2541082
and see if that makes sense to you
Let me know if you have questions.

nkk71 said:
you can also check out my guide: http://forum.xda-developers.com/showthread.php?t=2541082
and see if that makes sense to you
Let me know if you have questions.
Click to expand...
Click to collapse
Thank you.
Currently backing up, will kick it off after. Should this be undetectable by HTC?

Jimzoaar said:
Thank you.
Currently backing up, will kick it off after. Should this be undetectable by HTC?
Click to expand...
Click to collapse
if you have s-off, you'll be able to run a full ruu (and possibly restore a nandroid backup, depending on which method you're using), and be able to remove TAMPERED set the phone to LOCKED and even go S-On, if you really insist.
==> result, the phone is 100% "out of the box"
If you are going to go S-On, please follow the guide properly, because it has to be done at a specific point in time, too soon is BAD, too late is BAD!
if you need more help, post a "fastboot getvar all" (remove IMEI and s/n), either here or in the guide and i'll help out as best i can.

nkk71 said:
if you have s-off, you'll be able to run a full ruu (and possibly restore a nandroid backup, depending on which method you're using), and be able to remove TAMPERED set the phone to LOCKED and even go S-On, if you really insist.
==> result, the phone is 100% "out of the box"
If you are going to go S-On, please follow the guide properly, because it has to be done at a specific point in time, too soon is BAD, too late is BAD!
if you need more help, post a "fastboot getvar all" (remove IMEI and s/n), either here or in the guide and i'll help out as best i can.
Click to expand...
Click to collapse
Excellent, thank you.
I am S-OFF. I will provide full details below.
Sorry, I wasn't too clear in my original question, can you also confirm that once I FULLY go back to stock (s-on included) and HTC repair it, that i can then go back to rooted with a custom ROM?
Please see details below:
(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.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3942mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Also, just to confirm, that now I am S-off I can proceed with downgrading the HBOOT by runing the 1.44 exe?
Many thanks.

Jimzoaar said:
Excellent, thank you.
I am S-OFF. I will provide full details below.
Sorry, I wasn't too clear in my original question, can you also confirm that once I FULLY go back to stock (s-on included) and HTC repair it, that i can then go back to rooted with a custom ROM?
Click to expand...
Click to collapse
You should be able to unlock it again using HTCdev, and then rumrunner S-Off.
Jimzoaar said:
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
finished. total time: 0.068s
Also, just to confirm, that now I am S-off I can proceed with downgrading the HBOOT by runing the 1.44 exe?
Many thanks.
Click to expand...
Click to collapse
Yes, you can go ahead and continue following the guide.
Best to use the CWM recovery I posted in post #7 as other versions have some issues when used in "fastboot boot CWM.img" mode.
As for the S-On part, please follow the guide exactly, you go S-Off to S-On, after the 1st successful OTA update, but BEFORE any update to 3.xx; because in 3.xx (hboot 1.55) going S-Off to S-On will result in a "tamper detected - rebooting" and TAMPERED is back.
By the way, from what I've read, the UK carriers & repair centers are very lenient, and don't really care about S-Off etc. especially if it's a hardware issue; but then again it's your decision.

nkk71 said:
You should be able to unlock it again using HTCdev, and then rumrunner S-Off.
Yes, you can go ahead and continue following the guide.
Best to use the CWM recovery I posted in post #7 as other versions have some issues when used in "fastboot boot CWM.img" mode.
As for the S-On part, please follow the guide exactly, you go S-Off to S-On, after the 1st successful OTA update, but BEFORE any update to 3.xx; because in 3.xx (hboot 1.55) going S-Off to S-On will result in a "tamper detected - rebooting" and TAMPERED is back.
By the way, from what I've read, the UK carriers & repair centers are very lenient, and don't really care about S-Off etc. especially if it's a hardware issue; but then again it's your decision.
Click to expand...
Click to collapse
Thanks for your prompt and detailed response.
Just to clarify, I presume you mean Android 3.x.x. I hope you understand me questioning this because obviously the HTC one was shipped with Android4.0+. Am I right in querying whether this is still going to work?
Many thanks.

Jimzoaar said:
Thanks for your prompt and detailed response.
Just to clarify, I presume you mean Android 3.x.x. I hope you understand me questioning this because obviously the HTC one was shipped with Android4.0+. Am I right in querying whether this is still going to work?
Many thanks.
Click to expand...
Click to collapse
no, 3.x.x refers to the software number, not the android version. If ur going to complete stock and if u are gonna change S-OFF TO S-ON, then change it to S-ON bfor u install the 4.3 update. Preferably, as soon as the RUU restore completes, do the S-ON procedure first.

nkk71, i would appreciate your help as well if you could help me to identify which RUU to download because I am really confused with so many versions of RUU. I would like to go back to stock to claim warranty on the camera's purple tint issue. BTW, im running on TWRP recovery.
Thank you in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW9*****
(bootloader) imei: 3558590502*****
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4142mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

raghav kapur said:
no, 3.x.x refers to the software number, not the android version. If ur going to complete stock and if u are gonna change S-OFF TO S-ON, then change it to S-ON bfor u install the 4.3 update. Preferably, as soon as the RUU restore completes, do the S-ON procedure first.
Click to expand...
Click to collapse
Where can I check this? I am patient and will gladly check at multiple steps to ensure I am doing it at the correct one.
Also, I will be using the CWM nandroid method, can you confirm you mean after step one when I have installed the Sense 5 RUU?

nkk71 said:
if you have s-off, you'll be able to run a full ruu (and possibly restore a nandroid backup, depending on which method you're using), and be able to remove TAMPERED set the phone to LOCKED and even go S-On, if you really insist.
==> result, the phone is 100% "out of the box"
If you are going to go S-On, please follow the guide properly, because it has to be done at a specific point in time, too soon is BAD, too late is BAD!
if you need more help, post a "fastboot getvar all" (remove IMEI and s/n), either here or in the guide and i'll help out as best i can.
Click to expand...
Click to collapse
Please see below response when trying to flash the 1.44 HBoot (this is with s-off)
Do you have any ideas?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.246s]
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: 0.732s

Jimzoaar said:
Where can I check this? I am patient and will gladly check at multiple steps to ensure I am doing it at the correct one.
Also, I will be using the CWM nandroid method, can you confirm you mean after step one when I have installed the Sense 5 RUU?
Click to expand...
Click to collapse
see, you will be able to check this only once ur RUU restore is complete. Once u can boot into the stock firmware, go to Settings-About-Software Information-Software Number.
---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------
hmgan said:
nkk71, i would appreciate your help as well if you could help me to identify which RUU to download because I am really confused with so many versions of RUU. I would like to go back to stock to claim warranty on the camera's purple tint issue. BTW, im running on TWRP recovery.
Thank you in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW911268
(bootloader) imei: 355859050240456
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4142mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
go to this link http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/

Jimzoaar said:
Please see below response when trying to flash the 1.44 HBoot (this is with s-off)
Do you have any ideas?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.246s]
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: 0.732s
Click to expand...
Click to collapse
yes, no problem, just change CID (you're going to have to do it anyway for the RUU):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
then downgrade hboot will work just fine.

nkk71 said:
yes, no problem, just change CID (you're going to have to do it anyway for the RUU):
fastboot oem writecid HTC__001 <- two underscores
fastboot reboot-bootloader
then downgrade hboot will work just fine.
Click to expand...
Click to collapse
I am now recieving the below after changing CID to HTC__001, thank you for your previous response, any ideas on this?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.247s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.284s

Jimzoaar said:
Thanks for your prompt and detailed response.
Just to clarify, I presume you mean Android 3.x.x. I hope you understand me questioning this because obviously the HTC one was shipped with Android4.0+. Am I right in querying whether this is still going to work?
Many thanks.
Click to expand...
Click to collapse
I'm referring to the base version, which starts at
1.xx (for Android 4.1.2)
2.xx (for Android 4.2.2)
3.xx (for Android 4.3)
---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------
Jimzoaar said:
I am now recieving the below after changing CID to HTC__001, thank you for your previous response, any ideas on this?
Click to expand...
Click to collapse
didnt see any output.
---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------
Jimzoaar said:
I am now recieving the below after changing CID to HTC__001, thank you for your previous response, any ideas on this?
C:\Users\james.mildren>fastboot flash zip C:\Users\james.mildren\Desktop\1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.247s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.284s
Click to expand...
Click to collapse
have you "fastboot oem rebootRUU"?
Don't want to sound nasty or anything, but please make sure you've read through the guide once or twice (including post #7 which has command outputs and examples).

nkk71 said:
I'm referring to the base version, which starts at
1.xx (for Android 4.1.2)
2.xx (for Android 4.2.2)
3.xx (for Android 4.3)
---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------
didnt see any output.
---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------
have you "fastboot oem rebootRUU"?
Don't want to sound nasty or anything, but please make sure you've read through the guide once or twice (including post #7 which has command outputs and examples).
Click to expand...
Click to collapse
Not nasty at all, believe it or not I actually work in IT support and understand your frustrations when people don't listen. A small note though, obviously I seem to have hit a stumbling block on most steps, I know this sounds incredibly noobish, but also that is what these guides are aimed at, it may be reiterating that you either need to be in or re enter the RUU mode for certain steps, as obviously applying different fixes to bespoke problems leaves you in a different place to the guide which relys on it going smoothly.
Anyway, you are a genius, as expected, and that has worked. I will let you know of any more issues, thank you again for your help.

Jimzoaar said:
Not nasty at all, believe it or not I actually work in IT support and understand your frustrations when people don't listen. A small note though, obviously I seem to have hit a stumbling block on most steps, I know this sounds incredibly noobish, but also that is what these guides are aimed at, it may be reiterating that you either need to be in or re enter the RUU mode for certain steps, as obviously applying different fixes to bespoke problems leaves you in a different place to the guide which relys on it going smoothly.
Anyway, you are a genius, as expected, and that has worked. I will let you know of any more issues, thank you again for your help.
Click to expand...
Click to collapse
no problem, let me know how everything goes.
Good luck and remember not to rush things

nkk71 said:
no problem, let me know how everything goes.
Good luck and remember not to rush things
Click to expand...
Click to collapse
So I have now changed my CID and flashed CWM recovery, when trying to push the backup i get the follow:
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
push: c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.tar.b -> /d
ata/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b
failed to copy 'c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.t
ar.b' to '/data/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b'
: No such file or directory
Any ideas?

Jimzoaar said:
So I have now changed my CID and flashed CWM recovery, when trying to push the backup i get the follow:
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\james.mildren>adb push c:\users\james.mildren\desktop\2013-04-20.21.00.
00 /data/media/clockwordmod/backup/2013-04-20.21.00.00
push: c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.tar.b -> /d
ata/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b
failed to copy 'c:\users\james.mildren\desktop\2013-04-20.21.00.00/system.ext4.t
ar.b' to '/data/media/clockwordmod/backup/2013-04-20.21.00.00/system.ext4.tar.b'
: No such file or directory
Any ideas?
Click to expand...
Click to collapse
1- you mean booted into CWM not "flashed CWM recovery" right!!
2- are you using CWM 6.0.4.5 (the one i suggested in post 7), other versions have some issues with certain adb commands in "boot" mode
3- try updating adb & fastboot: http://goo.gl/T6InE
4- I recommend you put all files & folders in a short path, such as "C:\ADB" that would avoid long filename problems
try those and let me know

nkk71 said:
1- you mean booted into CWM not "flashed CWM recovery" right!!
2- are you using CWM 6.0.4.5 (the one i suggested in post 7), other versions have some issues with certain adb commands in "boot" mode
3- try updating adb & fastboot: http://goo.gl/T6InE
4- I recommend you put all files & folders in a short path, such as "C:\ADB" that would avoid long filename problems
try those and let me know
Click to expand...
Click to collapse
1 - Sorry, yes I did try the original way (booting into CWM not flashing) and when i got the aforementioned error I tried flashing, for your info I have now reflashed TWRP and am using CWM only to boot from.
2 - No I wasnt, I was user 6.0.4.6, I have now downgraded and still receive the same error.
3 - Fully updated
4- I am for the most part using my desktop, I know it just leads to more chance of an error but I have made sure there are no typos.
Just a quick query, I cannot perform the adb push when in CWM recovery....is that right? When I am in CWM my HTC does not show on the list of attached devices either. I have to boot into system before the push returns the above error, is that correct?

[Q] FAILED (remote: 24 parsing android-info fail)

Dear Friends,
I have searched everywhere but can not find a solution for this, i have unlocked bootloader and S-OFF
But no matter what I try I still get this error FAILED (remote: 24 parsing android-info fail) i am really confused tried relocking, changing cid nothing seems to fix it
Here is my phone
(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.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.061s
Click to expand...
Click to collapse
And here is what i am getting
C:\fastboot\HTCOneRoot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.044s]
finished. total time: 0.045s
C:\fastboot\HTCOneRoot>fastboot flash zip ruu.zip
sending 'zip' (1176263 KB)...
OKAY [ 45.993s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 65.433s
Click to expand...
Click to collapse
Any help or guidance is really appreciated

zouzousaade said:
Dear Friends,
I have searched everywhere but can not find a solution for this, i have unlocked bootloader and S-OFF
But no matter what I try I still get this error FAILED (remote: 24 parsing android-info fail) i am really confused tried relocking, changing cid nothing seems to fix it
Here is my phone
And here is what i am getting
Any help or guidance is really appreciated
Click to expand...
Click to collapse
what ruu are you using? can you provide a link?

@alray no matter what i try its only the ruu*.exe that work, now i want to install an ruu*.zip the files i am tried are http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ and http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ or any ota flash, any guidance my friend is realllllyyyyyy apreciated

zouzousaade said:
@alray no matter what i try its only the ruu*.exe that work, now i want to install an ruu*.zip the files i am tried are http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ and http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ or any ota flash, any guidance my friend is realllllyyyyyy apreciated
Click to expand...
Click to collapse
those are "installable" zips through custom recovery, they cannot be flashed in fastboot; there's a video here: http://www.htc1guru.com/downloads/stock-rom-downloads/
on how to install them.
EDIT: flashable ruu.zip are here: http://www.htc1guru.com/downloads/ruu-zip-downloads/
EDIT 2: sorry, i meant this one would be for you: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/

nkk71 said:
those are "installable" zips through custom recovery, they cannot be flashed in fastboot; there's a video here: http://www.htc1guru.com/downloads/stock-rom-downloads/
on how to install them.
EDIT: flashable ruu.zip are here: http://www.htc1guru.com/downloads/ruu-zip-downloads/
EDIT 2: sorry, i meant this one would be for you: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Click to expand...
Click to collapse
Thank you dear friend reading more to distinguish between them

zouzousaade said:
Thank you dear friend reading more to distinguish between them
Click to expand...
Click to collapse
Well easy enough:
* Guru Reset ROMs, are installed the same way as any other ROM, by selecting "install zip" in custom recovery (CWM or TWRP)
* ruu.zip, are flashed in ruu mode:
fastboot oem rebootRUU
fastboot flash zip <name of ruu>.zip
fastboot flash zip <name of ruu>.zip <- yes TWICE
fastboot reboot-bootloader

nkk71 said:
those are "installable" zips through custom recovery, they cannot be flashed in fastboot; there's a video here: http://www.htc1guru.com/downloads/stock-rom-downloads/
on how to install them.
EDIT: flashable ruu.zip are here: http://www.htc1guru.com/downloads/ruu-zip-downloads/
EDIT 2: sorry, i meant this one would be for you: http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
Click to expand...
Click to collapse
Sir nkk71, can you help me with my problem, what RUU should i use in RUU mode, my getvar is
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.079s
any help will be much appreciated

grins814 said:
Sir nkk71, can you help me with my problem, what RUU should i use in RUU mode, my getvar is
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
any help will be much appreciated
Click to expand...
Click to collapse
No need to "Sir" around here, we're (usually) a friendly bunch
I don't know of any 4.20.707.6 (or higher ruu's... there could be but i havent looked), otherwise you need to s-off (to be able to downgrade) and use:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
EDIT, or this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...0-13_10-33-1150-01_release_311678_signed-zip/
unless if you can find an RUU which is 4.20.707.6 or higher.

nkk71 said:
No need to "Sir" around here, we're (usually) a friendly bunch
I don't know of any 4.20.707.6 (or higher ruu's... there could be but i havent looked), otherwise you need to s-off (to be able to downgrade) and use:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
EDIT, or this ruu.zip: http://www.htc1guru.com/dld/ruu-zip...0-13_10-33-1150-01_release_311678_signed-zip/
unless if you can find an RUU which is 4.20.707.6 or higher.
Click to expand...
Click to collapse
the problem here now is that my phone is stuck in HTC logo so i cant S-OFF my phone, do you have any other ways to get S-Off @nkk71, i also tried to install custom rom using TWRP and it says "error flashing zip '/sdcard/rom.zip"

grins814 said:
the problem here now is that my phone is stuck in HTC logo so i cant S-OFF my phone, do you have any other ways to get S-Off @nkk71, i also tried to install custom rom using TWRP and it says "error flashing zip '/sdcard/rom.zip"
Click to expand...
Click to collapse
bad/corrupt zip, that's all. did you check MD5 of the rom you downloaded?

nkk71 said:
bad/corrupt zip, that's all. did you check MD5 of the rom you downloaded?
Click to expand...
Click to collapse
so there is still a way to repair my phone? "your giving me hope" :fingers-crossed: i have winmd5 app here but i really dont understand how to use it.
---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------
im currently downloading 3 different RUU's now.
- RUU Zip M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.1150.01_release_312087_signed_2_4_decrypted.zip
- RUU Zip M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed.zip
- RUU_M7_UL_JB_50_hTC_Asia_WWE_1.26.707.5_Radio_4A.13.3231.20_10.30.1131.05_release_309365_signed_2_4_2.exe
hope 1 of this 3 will solve my problem. i rooted my phone out of curiosity, not knowing the exact steps.

grins814 said:
so there is still a way to repair my phone? "your giving me hope" :fingers-crossed: i have winmd5 app here but i really dont understand how to use it.
Click to expand...
Click to collapse
okay, so you have an "(bootloader) product: m7_ul"
so from the beginning
1- do you have TWRP 2.6.3.3+?
http://techerrata.com/browse/twrp2/m7
or
http://techerrata.com/browse/twrp2/m7ul
2- what ROM are you trying to flash?
3- just run WinMD5.EXE and drag and drop the ROM you're trying to install, it'll give you a funky number... you compare that to the place you downloaded the ROM from to make sure the zip isnt corrupt
^^ BTW: I did say "friendly bunch" (usually)... the least you could do is http://www.lmgtfy.com/?q=how+do+i+check+md5
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
grins814 said:
im currently downloading 3 different RUU's now.
- RUU Zip M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.1150.01_release_312087_signed_2_4_decrypted.zip
- RUU Zip M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed.zip
- RUU_M7_UL_JB_50_hTC_Asia_WWE_1.26.707.5_Radio_4A.13.3231.20_10.30.1131.05_release_309365_signed_2_4_2.exe
hope 1 of this 3 will solve my problem. i rooted my phone out of curiosity, not knowing the exact steps.
Click to expand...
Click to collapse
you can download as many ruu's as you like, but if you're S-On ..... NONE of them will work (these are lower than your current version, and you cannot downgrade without S-OFF)
and
out of curiosity, not knowing the exact steps
Click to expand...
Click to collapse
==> do a little bit of reading!!

nkk71 said:
okay, so you have an "(bootloader) product: m7_ul"
so from the beginning
1- do you have TWRP 2.6.3.3+?
http://techerrata.com/browse/twrp2/m7
or
http://techerrata.com/browse/twrp2/m7ul
2- what ROM are you trying to flash?
3- just run WinMD5.EXE and drag and drop the ROM you're trying to install, it'll give you a funky number... you compare that to the place you downloaded the ROM from to make sure the zip isnt corrupt
^^ BTW: I did say "friendly bunch" (usually)... the least you could do is http://www.lmgtfy.com/?q=how+do+i+check+md5
Click to expand...
Click to collapse
i get it now, so this funky numbers called checksum posted under each download link most match the checksum of the files i downloaded. ok then ill try some ruu that i downloaded. thanks

grins814 said:
i get it now, so this funky numbers called checksum posted under each download link most match the checksum of the files i downloaded. ok then ill try some ruu that i downloaded. thanks
Click to expand...
Click to collapse
yes, but
1- you can't flash an RUU in TWRP, you can only flash ROMs
2- you can't downgrade without S-Off
I think it's time for you to catch up on some reading

nkk71 said:
okay, so you have an "(bootloader) product: m7_ul"
so from the beginning
1- do you have TWRP 2.6.3.3+?
http://techerrata.com/browse/twrp2/m7
or
http://techerrata.com/browse/twrp2/m7ul
2- what ROM are you trying to flash?
3- just run WinMD5.EXE and drag and drop the ROM you're trying to install, it'll give you a funky number... you compare that to the place you downloaded the ROM from to make sure the zip isnt corrupt
^^ BTW: I did say "friendly bunch" (usually)... the least you could do is http://www.lmgtfy.com/?q=how+do+i+check+md5
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
you can download as many ruu's as you like, but if you're S-On ..... NONE of them will work (these are lower than your current version, and you cannot downgrade without S-OFF)
and
==> do a little bit of reading!!
Click to expand...
Click to collapse
my bad for not taking this rooting thing seriously, so the only way for me to repair my phone is to find a ruu that is 4.20.707.6 or highr? hope an update in ruu's will be available soon. my phone is dead for 4 days now.

grins814 said:
my bad for not taking this rooting thing seriously, so the only way for me to repair my phone is to find a ruu that is 4.20.707.6 or highr? hope an update in ruu's will be available soon. my phone is dead for 4 days now.
Click to expand...
Click to collapse
get a custom ROM, for example: ARHD 53.0 http://forum.xda-developers.com/showthread.php?t=2183023
install that using TWRP, at least you'll have a functioning phone. until you figure out the rest.

i was just thinking maybe the reason i was getting this error "error flashing zip '/sdcard/rom.zip" is because my phone is S-ON and that the ruu i was trying ti install is not compatible with my phone. by the way, what is the bases of having a older version or newer version since it has 7 digits in it. what i know is that for S-OFF phones having 4.20.707.6 can install other ruus as long as it is x.xx.707.x, am i right? what are the possible higher version of my phone? 4.20.707.8 something or 4.21.707.1? just an, example
---------- Post added at 07:15 PM ---------- Previous post was at 07:11 PM ----------
nkk71 said:
get a custom ROM, for example: ARHD 53.0 http://forum.xda-developers.com/showthread.php?t=2183023
install that using TWRP, at least you'll have a functioning phone. until you figure out the rest.
Click to expand...
Click to collapse
maybe i could ask @mike1986. if he has a custom rom compatible with my version. by the way, thanks for your help @nkk71

grins814 said:
i was just thinking maybe the reason i was getting this error "error flashing zip '/sdcard/rom.zip" is because my phone is S-ON and that the ruu i was trying ti install is not compatible with my phone. by the way, what is the bases of having a older version or newer version since it has 7 digits in it. what i know is that for S-OFF phones having 4.20.707.6 can install other ruus as long as it is x.xx.707.x, am i right? what are the possible higher version of my phone? 4.20.707.8 something or 4.21.707.1? just an, example
---------- Post added at 07:15 PM ---------- Previous post was at 07:11 PM ----------
maybe i could ask @mike1986. if he has a custom rom compatible with my version. by the way, thanks for your help @nkk71
Click to expand...
Click to collapse
mate,
1- ARHD 53.0 is compatible with your phone, otherwise I wouldnt have suggested it !!
2- S-On / S-Off doesn't affect custom ROMs... you can deal with S-Off later
3- "i was getting this error error flashing zip '/sdcard/rom.zip" -> is because it's either NOT A ROM, or a bad download.... you CANNOT use TWRP for RUU
so in conclusion, for the time being at least, maybe longer(?), just to have a working phone: download ARHD 53.0
put that on your phone, and install using TWRP
when asked to "Wipe user partition" -> select WIPE

grins814 said:
i was just thinking maybe the reason i was getting this error "error flashing zip '/sdcard/rom.zip" is because my phone is S-ON
Click to expand...
Click to collapse
Your main problem is you do it the wrong way.
You cannot fastboot flash zip ROM.zip.
The same thing with your problem of trying to install an AT&T ROM to your ASIA WWE device.
What you need to do is :
1. Re-unlock your bootloader if it is relocked
2. Make sure you flash a right recovery for Intl one either M7_u or M7_ul
3. Download a ROM.zip either you want to use my 4.20.707.6 ROM.zip or ARHD or any ROM.zip but it must be the intl version not AT&T
4. You need to put the ROM.zip that you downloaded onto the sdcard
a- either use ADB sideload
b- or ADB push in recovery (but you must have the correct driver install to your PC and right ADB version too)
c- or the easiest way is use the OTG function in the recovery with an OTG cable where you put the ROM.zip on a flash drive.
5. In recovery, make a full wipe and select install and browse to the ROM.zip to install

ckpv5 said:
Your main problem is you do it the wrong way.
You cannot fastboot flash zip ROM.zip.
The same thing with your problem of trying to install an AT&T ROM to your ASIA WWE device.
What you need to do is :
1. Re-unlock your bootloader if it is relocked
2. Make sure you flash a right recovery for Intl one either M7_u or M7_ul
3. Download a ROM.zip either you want to use my 4.20.707.6 ROM.zip or ARHD or any ROM.zip but it must be the intl version not AT&T
4. You need to put the ROM.zip that you downloaded onto the sdcard
a- either use ADB sideload
b- or ADB push in recovery (but you must have the correct driver install to your PC and right ADB version too)
c- or the easiest way is use the OTG function in the recovery with an OTG cable where you put the ROM.zip on a flash drive.
5. In recovery, make a full wipe and select install and browse to the ROM.zip to install
Click to expand...
Click to collapse
still didnt work on my phone. :crying:

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

HTC One M7 e801 bootup blankscreen

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

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

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

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

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