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?

So confused - OTA Updates & Rooted/Modified M7 - please help!

Hi all,
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
What I've tried:
Getting S-OFF (no luck whatsoever with any tools)
Flashing stock recovery and kernel
Flashing stock recovery and kernel and applying the OTA manually via recovery
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update.
Someone, please guide me in the right direction! Step by step maybe?
Keep in mind there is no way I can't get S-OFF.
Huge thanks to anyone that can help. I'd be eternally in your debt!!

SmokinWaffle said:
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
Click to expand...
Click to collapse
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
What I've tried:
Getting S-OFF (no luck whatsoever with any tools) Any error message when trying to S-OFF? You must use the correct tool for your hboot version (probably firewater) + combination of the correct rom + kernel
Flashing stock recovery and kernel --> You must have stock recovery for ota, ota will not install using a custom one.
Flashing stock recovery and kernel and applying the OTA manually via recovery --> appyling the ota manually from stock recovery require s-off
Click to expand...
Click to collapse
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update
Click to expand...
Click to collapse
.
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Keep in mind there is no way I can't get S-OFF.
Click to expand...
Click to collapse
still not sure about this, unless you get the "whelp" message from firewater...
post the output of fastboot getvar all except the imei number and serialno

alray said:
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
Click to expand...
Click to collapse
Yep!
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Click to expand...
Click to collapse
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
alray said:
still not sure about this, unless you get the "whelp" message from firewater...
Click to expand...
Click to collapse
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
alray said:
post the output of fastboot getvar all except the imei number and serialno
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.

SmokinWaffle said:
Yep!
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
Click to expand...
Click to collapse
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752

alray said:
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
I'm guessing the ARHD steps are to try to get S-OFF?

SmokinWaffle said:
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
Click to expand...
Click to collapse
forget the ruu, your phone version is higher than the ruu. flashing a ruu (4.11.401.10) with a lower version than on your phone(4.11.401.11) require s-off.
I'm guessing the ARHD steps are to try to get S-OFF?
Click to expand...
Click to collapse
No, this is the latest stock rom(5.11.401.10) for your phone model (MID: PN0710000 and CID:HTC__001) including android 4.4.2 and sense 6.0
You can flash this stock odexed rom(5.11.401.10) from custom recovery, then flash the stock recovery(5.11.401.10) over the custom one and your phone will be stock and ready to take future ota update. You may also want to update firmware to 5.11.401.10

So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved

SmokinWaffle said:
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
Click to expand...
Click to collapse
stock kernel in included in the rom (boot.img) so if you don't flash any other kernel it should be fine.
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
Click to expand...
Click to collapse
firmware is all the low level code required for your phone hardware to works with the software (OS)
when speaking about HTC phone, firmware.zip include HBOOT(bootloader), BOOT(kernel), Recovery, Radio and some other stuff. if you want your phone to be 100% stock you need both stock rom + stock firmware to match the same version i.e 5.11.501.10
normally, the firmware is updated at the same time the rom version is updated (from an ota update) If you flash a rom, the rom will be updated but not the firmware.
Updating the firmware manually can be dangerous is you don't know what you are doing and flashing the wrong file. You can update firmware using this command from bootloader (with the correct firmware.zip package in the same folder you have adb and fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
also it looks like flashing a 5.x.xxx.x firmware over a 3.x.xxx.x firmware will brick your phone. from what i see, your phone should be on a 4.x.401.x version at the moment, so it theory it should be fine.

Fails on:
>>>setting permissions
set_metadata_recursive: some changes failed
E:Error in /data/media/0/one_5.11.401.10_odexed.zip
(status 7)
Tried 3 different versions of cwm. Bad rom download?
Thinking about it I just re read your above post, could it be because the firmware isn't matched? I read your 'it should be fine' as 'dont update the firmware' not 'its fine to update' which I think is what you meant...
Firmware is 4.19.401.11 however the rom is 5.11.401.10. Can't believe I overlooked this, guess firmware needs to be 5.11.401.10 for the rom to take?

SmokinWaffle said:
Tried 3 different versions of cwm. Bad rom download?
Click to expand...
Click to collapse
No you are using CWM thats the problem. always use TWRP 2.6.3.3

alray said:
No you are using CWM thats the problem. always use TWRP 2.6.3.3
Click to expand...
Click to collapse
Huh?
Is this a requirement of ARHD or....?
Just seems odd
Edit: success!! All seems to work. Thank you. She's overjoyed!!!

[Q] Bricked my HTC one ( S-ON),Tried many methods still doesn't work

The cidnumber of my phone is : VODAP021 and it is a s-on rooted phone.
Yesterday I just root my HTC one followed the steps on the htcdev website. And then didn't check the status of my phone( s-on or s-off). After installing a custom ROM , The HTC one strike on the HTC screen and rebooted again and agin.
I have tried many methods like relock the phone and flash the ruu rom , but no matter how many times I tried, it is failed on the step of signature
checking. I post the output below :
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
PS:
I really download the zip from the htc1guru website and use the command :
fastboot oem rebootRUU
fastboot flash zip
.
Thank you guys first cause this is the first time I post thread here.

yimuxia said:
The cidnumber of my phone is : VODAP021 and it is a s-on rooted phone.
Yesterday I just root my HTC one followed the steps on the htcdev website. And then didn't check the status of my phone( s-on or s-off). After installing a custom ROM , The HTC one strike on the HTC screen and rebooted again and agin.
I have tried many methods like relock the phone and flash the ruu rom , but no matter how many times I tried, it is failed on the step of signature
checking. I post the output below :
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
PS:
I really download the zip from the htc1guru website and use the command :
fastboot oem rebootRUU
fastboot flash zip
.
Thank you guys first cause this is the first time I post thread here.
Click to expand...
Click to collapse
Which ruu are you tring to flash? Afaik there is no RUU availabe for vodap021
your bootloop issue is probably because you have flashed an incompatible rom or because you have flashed a rom with the wrong recovery version.
please answer all questions below
What rom have you tried to flash? (name, version and link)
What recovery are you using (name and version)
post the output of "fastboot getvar all" minus the IMEI and SERIALNO
What RUU are you trying to flash?

Sorry for late replying
alray said:
Which ruu are you tring to flash? Afaik there is no RUU availabe for vodap021
your bootloop issue is probably because you have flashed an incompatible rom or because you have flashed a rom with the wrong recovery version.
please answer all questions below
What rom have you tried to flash? (name, version and link)
What recovery are you using (name and version)
post the output of "fastboot getvar all" minus the IMEI and SERIALNO
What RUU are you trying to flash?
Click to expand...
Click to collapse
Sorry for the late replying, I was working before. - -# .
1: Firstly after rooting my HTC one , I tried CM rom for HTC one (cm-10.2.1-m7ul.zip).
The phone rebooted itself again and again and failed to enter the system.
Then I searched on xda and tried Guru Reset M7 2.24.980.2 followed others instruction. The ruu is from the website of htc1guru(sorry I am still not able to post outside links)
2: The recovery I am using is : openrecovery-twrp-2.7.1.1-m7.img And enter my recovery on my phone, I can see the information below:
CLockworkMod Recovery v6.0.3.3
3: Below is the information by using fastboot getvar all commnd:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.980.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: minus XD
(bootloader) imei: minus XD
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3850mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I am so glad you guys reply me .I just get the phone three days before - - #.

need help
need help , Still cant open my phone yet~

yimuxia said:
need help , Still cant open my phone yet~
Click to expand...
Click to collapse
not sure what you want to accomplish, but if you just want to get your phone up and running for now
grab a ROM from the Development section
flash correct recovery, push the rom, and install it; instructions inthe Frequently Asked Question sticky on page 3

nkk71 said:
not sure what you want to accomplish, but if you just want to get your phone up and running for now
grab a ROM from the Development section
flash correct recovery, push the rom, and install it; instructions inthe Frequently Asked Question sticky on page 3
Click to expand...
Click to collapse
Thank you for replying , I will try this first after work today !
thank you !

[SOLVED]Hard bricked HTC one m7 any help?

Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly (before, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone went into bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
EDIT1: 8. rewritten version-main from 4.19.xxxxxx to 1.00.000.0 (via HTC One All-In-One Toolkit by Hasoon2000) in an desperate attempt to fix ruu flashing, no luck as well (i think that even broke more things )
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 3544************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi

uuzi said:
Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly my phone (before brick, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone was in a bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 354436054678733
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi
Click to expand...
Click to collapse
First of all and as I'm sure you've discovered going back to S-on is never a good fix for anything except warranty
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before. Don't know if this is a hardware issue. Flashing firmware may solve it but with s-on and super cid I'm not even sure thats possible or which firmware you can use with your version main that way. Going back to s-on may well have been the nail in the coffin here I'm afraid.
If your able to boot recovery you can push a rom to flash but you need to fix the firmware first as I fear that's the cause of your bootloop. Hopefully @nkk71 @clsA or @majmoz have somthing to add here :good:

oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.

uuzi said:
oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.
Click to expand...
Click to collapse
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP

uuzi said:
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
Click to expand...
Click to collapse
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
i'm not really sure right now, i'm trying again now

Danny201281 said:
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before.
Click to expand...
Click to collapse
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
uuzi said:
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP
Click to expand...
Click to collapse
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?

Result:
Code:
C:\unbrick>fastboot oem rebootRUU
(bootloader) Start Verify: 3
OKAY [ 0.030s]
finished. total time: 0.031s
C:\unbrick>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 32.802s]
writing 'zip'...
(bootloader) signature checking...
FAILED (status read failed (Unknown error))
finished. total time: 801.973s

nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?
Click to expand...
Click to collapse
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery

nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
Click to expand...
Click to collapse
Yeah I got that after he had said he'd changed it manually. Just caught me off guard thought it was something bigger. :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 05:01 PM ---------- Previous post was at 04:57 PM ----------
uuzi said:
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery
Click to expand...
Click to collapse
What about TWRP 2.6.3.3 If it's still working maybe you can flash ARHD to get it booting maybe.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!

uuzi said:
OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!
Click to expand...
Click to collapse
Glad to here your back up good job :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Ever played whack-a-mole on hardbrick mode?

Got this HTC One M7.
CID-SPCS_001 <--So I understand it to be Sprint originally.
Phone had OS wiped, and I'm having a helluva time getting it back to usable condition.
I've made some minor progress, but this entire situation has been ridiculous. Probably put 40 hours into this joke, and now doing it just for the challenge.
Finally started to use Terminal on my Mac and managed to get the recovery updated to TWRP v2.8.7.0
I can get fastboot to work. Figured that out. It will register to my Mac in recovery mode. It will register in sideload (adb devices) mode. It seems the next hurdle is that it won't accept the .zip when I try to send it over in sideload.
When I enter "./adb sideload filename.zip" Terminal responds with "transferring filename.zip" but when switches to "Total xfer: 0.00x" within 2 seconds. It doesn't actually transfer the file at all, as is obvious with the 0.00x.
When I try to sideload, it says "ADB sideload complete" at the top, with "failed" in red letters underneath.
I can't figure out what the issue is. The zip file I'm trying to use is a Sprint RUU I found. Might be an issue since I'm using a mac. I compressed it and renamed it xxx.zip
M7_WLS PVT SHIP S-OFF RH
CID-SPCS_001
HBOOT- 1.44.000
RADIO - 1.00.20.0315
OpenDSP- v26.120.274.0202
eMMC-boot
Solutions please?

So now my problem is that I can't find a typical .zip file. I'm coming from playing with samsung Galaxy phones, so everything was a nice, neat .zip file.
For this phone, I keep finding "RUUs" that say they are zip files, but they are just big folders. Not a zip file at all.
So, I thought "what if I compress it into a zip myself?"
But when I try to install that, the phone says .zip is corrupt

demonblod said:
So now my problem is that I can't find a typical .zip file. I'm coming from playing with samsung Galaxy phones, so everything was a nice, neat .zip file.
For this phone, I keep finding "RUUs" that say they are zip files, but they are just big folders. Not a zip file at all.
So, I thought "what if I compress it into a zip myself?"
But when I try to install that, the phone says .zip is corrupt
Click to expand...
Click to collapse
RUUs are zip files, but you need to flash them via fastboot with your phone in RUU mode. Also if you try to unzip them, you will get "corrupted zip" error, so unziping is a big NO. You don't really need a RUU, you can sideload a ROM.zip and flash it from your recovery. Difference between a RUU and a ROM is that RUU contains h-boot, recovery, actual ROM, boot.img, firmware... In short, a full software set, while ROM.zip contains only ROM and kernel software. Oh, and RUUs are encrypted

donkeykong1 said:
RUUs are zip files, but you need to flash them via fastboot with your phone in RUU mode. Also if you try to unzip them, you will get "corrupted zip" error, so unziping is a big NO. You don't really need a RUU, you can sideload a ROM.zip and flash it from your recovery. Difference between a RUU and a ROM is that RUU contains h-boot, recovery, actual ROM, boot.img, firmware... In short, a full software set, while ROM.zip contains only ROM and kernel software. Oh, and RUUs are encrypted
Click to expand...
Click to collapse
Ok. I understand most of what you said. I know that ROMs are the OS and RUU is everything included. I've been looking *everywhere* for a basic ROM, can't find one. Can't find anything other than RUUs. And I've looked on, probably, 50 different website, forum threads, etc etc trying to find this solution.
A couple issues:
1) I've NEVER heard or seen "RUU mode". Again, in 15 or 20 different "how to unbrick your HTC One M7" threads, nobody has ever mentioned 'RUU mode'.
2)Can't find a ROM.zip anywhere
3)when I download the "RUU.zip" it's shows up as an unzipped folder in my downloads. And Terminal won't let me flash, or push, or sideload a folder. It must be a single file. Which is why I compressed it myself upon download, in order to make it a single .zip file

demonblod said:
Ok. I understand most of what you said. I know that ROMs are the OS and RUU is everything included. I've been looking *everywhere* for a basic ROM, can't find one. Can't find anything other than RUUs. And I've looked on, probably, 50 different website, forum threads, etc etc trying to find this solution.
A couple issues:
1) I've NEVER heard or seen "RUU mode". Again, in 15 or 20 different "how to unbrick your HTC One M7" threads, nobody has ever mentioned 'RUU mode'.
2)Can't find a ROM.zip anywhere
3)when I download the "RUU.zip" it's shows up as an unzipped folder in my downloads. And Terminal won't let me flash, or push, or sideload a folder. It must be a single file. Which is why I compressed it myself upon download, in order to make it a single .zip file
Click to expand...
Click to collapse
According to your CID, your phone is a Sprint one. If you want ROMs, go to sprint development thread. There is a number of ROM zips for you there.
As for RUU mode, in terminal type "fastboot oem rebootRUU" and your phone will go into RUU mode. That's a black screen with silver HTC logo. From there you flash RUU.zip using fastboot commands. But I would like you to post your fastboot getvar all output excluding your IMEI and serian no, so we can get more info on your phone and link you to correct ROM or RUU
---------- Post added at 04:51 AM ---------- Previous post was at 04:50 AM ----------
demonblod said:
Ok. I understand most of what you said. I know that ROMs are the OS and RUU is everything included. I've been looking *everywhere* for a basic ROM, can't find one. Can't find anything other than RUUs. And I've looked on, probably, 50 different website, forum threads, etc etc trying to find this solution.
A couple issues:
1) I've NEVER heard or seen "RUU mode". Again, in 15 or 20 different "how to unbrick your HTC One M7" threads, nobody has ever mentioned 'RUU mode'.
2)Can't find a ROM.zip anywhere
3)when I download the "RUU.zip" it's shows up as an unzipped folder in my downloads. And Terminal won't let me flash, or push, or sideload a folder. It must be a single file. Which is why I compressed it myself upon download, in order to make it a single .zip file
Click to expand...
Click to collapse
According to your CID, your phone is a Sprint one. If you want ROMs, go to sprint development thread. There is a number of ROM zips for you there.
As for RUU mode, in terminal type "fastboot oem rebootRUU" and your phone will go into RUU mode. That's a black screen with silver HTC logo. From there you flash RUU.zip using fastboot commands. But I would like you to post your "fastboot getvar all" output excluding your IMEI and serian no, so we can get more info on your phone and link you to correct ROM or RUU

donkeykong1 said:
According to your CID, your phone is a Sprint one. If you want ROMs, go to sprint development thread. There is a number of ROM zips for you there.
As for RUU mode, in terminal type "fastboot oem rebootRUU" and your phone will go into RUU mode. That's a black screen with silver HTC logo. From there you flash RUU.zip using fastboot commands. But I would like you to post your fastboot getvar all output excluding your IMEI and serian no, so we can get more info on your phone and link you to correct ROM or RUU
....again.... whenever I download the supposed RUU.zip it's a folder, not a zip file, and terminal won't flash it as it's not a file. I've tried 2 different RUUs.
This is likely my fault as I got my first Mac 2 weeks ago, and have no prior experience. Maybe that's just how OS X handles .zip files? IDK.
wow. That RUU mode actually worked. That's amazing. Thanks. Finally some progress. First time I've ever seen anyone mention that. Like I said, I've looked through at least 10 "how to unbrick" threads with no mention of that. They always mention to download an RUU though.
Here's what I got when I did "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36YS9A0146
(bootloader) imei: 990001469823272
(bootloader) meid: 99000146982327
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.059s
Click to expand...
Click to collapse

demonblod said:
donkeykong1 said:
According to your CID, your phone is a Sprint one. If you want ROMs, go to sprint development thread. There is a number of ROM zips for you there.
As for RUU mode, in terminal type "fastboot oem rebootRUU" and your phone will go into RUU mode. That's a black screen with silver HTC logo. From there you flash RUU.zip using fastboot commands. But I would like you to post your fastboot getvar all output excluding your IMEI and serian no, so we can get more info on your phone and link you to correct ROM or RUU
....again.... whenever I download the supposed RUU.zip it's a folder, not a zip file, and terminal won't flash it as it's not a file. I've tried 2 different RUUs.
This is likely my fault as I got my first Mac 2 weeks ago, and have no prior experience. Maybe that's just how OS X handles .zip files? IDK.
wow. That RUU mode actually worked. That's amazing. Thanks. Finally some progress. First time I've ever seen anyone mention that. Like I said, I've looked through at least 10 "how to unbrick" threads with no mention of that. They always mention to download an RUU though.
Here's what I got when I did "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36YS9A0146
(bootloader) imei: 990001469823272
(bootloader) meid: 99000146982327
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.059s
Click to expand...
Click to collapse
I'm uploading RUU.zip to my dropbox and I'll send you the link as soon as it uploads. Let's hope it will stay in zip format this time [emoji4]
Click to expand...
Click to collapse

donkeykong1 said:
demonblod said:
I'm uploading RUU.zip to my dropbox and I'll send you the link as soon as it uploads. Let's hope it will stay in zip format this time [emoji4]
Click to expand...
Click to collapse
wow. that would be amazing. Thanks.
So, the phone is originally sprint (?) from what I understand, but it's also a world phone? My end goal is to be able to use this on AT&T.
So I'm trusting you to guide me to the right RUU, because I clearly can't get it straight.
Also, to confirm, when I get this file from you, I do
go into fastboot
./fastboot oem rebootRUU
./fastboot flash recovery filename.zip
?
Click to expand...
Click to collapse

demonblod said:
donkeykong1 said:
wow. that would be amazing. Thanks.
So, the phone is originally sprint (?) from what I understand, but it's also a world phone? My end goal is to be able to use this on AT&T.
So I'm trusting you to guide me to the right RUU, because I clearly can't get it straight.
Also, to confirm, when I get this file from you, I do
go into fastboot
./fastboot oem rebootRUU
./fastboot flash recovery filename.zip
?
Click to expand...
Click to collapse
I don't think it will work on at&t, but I don't know much about US networks. I'm uploading a Sprint RUU for you, so you get your phone to boot up. Commands are the right ones except the last one. It's fastboot flash zip "name of the zip".zip
---------- Post added at 07:46 AM ---------- Previous post was at 07:25 AM ----------
https://www.dropbox.com/s/t7vl6fvklo9hhms/Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip?dl=0
Here's a link to your RUU. Fingers crossed it ends up in zip format ?
Click to expand...
Click to collapse

donkeykong1 said:
demonblod said:
I don't think it will work on at&t, but I don't know much about US networks. I'm uploading a Sprint RUU for you, so you get your phone to boot up. Commands are the right ones except the last one. It's fastboot flash zip "name of the zip".zip
---------- Post added at 07:46 AM ---------- Previous post was at 07:25 AM ----------
https://www.dropbox.com/s/t7vl6fvklo9hhms/Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip?dl=0
Here's a link to your RUU. Fingers crossed it ends up in zip format
Click to expand...
Click to collapse
thank you very much for the effort. Appears in my downloads as a simple folder :/
Click to expand...
Click to collapse

I figured out the issue.
Apparently Safari has an "open downloaded automatically" feature set as default. As a result, it opens the .zip file and decompresses it to do so. Got it as a .zip this time!!

If you're ready for the next round in this never ending game of whack-a-mole, here it is.
Downloaded the .zip. It stayed a .zip.
./fastboot oem rebootRUU <---went to black screen with silver HTC logo (check)
./fastboot flash zip filename.zip <--- says sending 'zip'
after about, 40 seconds it says, I get this
sending 'zip' (1032712 KB)...
OKAY [ 41.658s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 41.929s
oh yeah, btw, I can't get into recovery anymore for some reason. When I try, it just loops.

---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
[/COLOR]
demonblod said:
If you're ready for the next round in this never ending game of whack-a-mole, here it is.
Downloaded the .zip. It stayed a .zip.
./fastboot oem rebootRUU <---went to black screen with silver HTC logo (check)
./fastboot flash zip filename.zip <--- says sending 'zip'
after about, 40 seconds it says, I get this
sending 'zip' (1032712 KB)...
OKAY [ 41.658s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 41.929s
oh yeah, btw, I can't get into recovery anymore for some reason. When I try, it just loops.
Click to expand...
Click to collapse
Can you try this RUU?
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36YS9A0146
(bootloader) imei: 990001469823272
(bootloader) meid: 99000146982327
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(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

donkeykong1 said:
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
[/COLOR]
Can you try this RUU?
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
Click to expand...
Click to collapse
Wow. You're amazing. It worked. Thanks so much. I've got it up and running stock Sprint software. I actually thought it would just be some nice looking paperweight for sale on eBay for parts.
Thanks for sticking with me through this. It was pretty frustrating

demonblod said:
Wow. You're amazing. It worked. Thanks so much. I've got it up and running stock Sprint software. I actually thought it would just be some nice looking paperweight for sale on eBay for parts.
Thanks for sticking with me through this. It was pretty frustrating
Click to expand...
Click to collapse
No problem mate! Happy hollidays! [emoji4] [emoji106]

donkeykong1 said:
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
[/COLOR]
Can you try this RUU?
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
Click to expand...
Click to collapse
donkeykong1 said:
No problem mate! Happy hollidays! [emoji4] [emoji106]
Click to expand...
Click to collapse
Now I just need to figure out how to get it to work on AT&T. Supposedly it's a world phone, and it has a sim chip insert on the side. I put the SIM chip in and it asked me to select my network. I chose AT&T but nothing happened

demonblod said:
Now I just need to figure out how to get it to work on AT&T. Supposedly it's a world phone, and it has a sim chip insert on the side. I put the SIM chip in and it asked me to select my network. I chose AT&T but nothing happened
Click to expand...
Click to collapse
Unfortunately, I can't help you with that much. I will do some reading and get back to you if that means something to you