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?

[Solved] Need Help with S-On

Hey guys need ur help with going back to stock.Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP. Now my device is S-ON with bootloader locked and with custom recovery.I tried to use revone-0.2.1 to S-OFF and then unlock my bootloader but after few tries it says successful but when i checked the bootloader it shows S-ON and tampered.I even used firewater thta was also unsuccessful so please i need urgent help.
P.S My phone is still rooted.

You don't need to soff to flash stock recovery. You need unlocked bootloader. Unlock it using aio kit and you can flash stock recovery after that. You cannot flash recovery with a locked bootloader.
Sent from my All Metal HTC One.
Android 4.4.2 - Sense 6.0

well i tried using revone's option of unlocking bootloader shows error code -1
Hboot is 1.44
and if ur talking about using the unlock bin code i need stock recovery for that.Can someone provide me a signed stock recovery as i tried to flash a recovery from ruu but it shows signature verification failure.

Bump need urgent help

Slim Shady said:
Bump need urgent help
Click to expand...
Click to collapse
what's your current "fastboot getvar all" (except IMEI and s/n)

nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s

Slim Shady said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
finished. total time: 0.044s
Click to expand...
Click to collapse
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP
Click to expand...
Click to collapse
the RUU already has stock recovery, so why would you have TWRP there?
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.

nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
nkk71 said:
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
the RUU already has stock recovery, so why would you have TWRP there?
Click to expand...
Click to collapse
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.

Slim Shady said:
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Click to expand...
Click to collapse
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.

Thats what I thought... restoring via RUU restores the recovery also.

nkk71 said:
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Click to expand...
Click to collapse
Not even able to access twrp now. Is there any way u can help me ???

Slim Shady said:
Not even able to access twrp now. Is there any way u can help me ???
Click to expand...
Click to collapse
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.

nkk71 said:
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
Click to expand...
Click to collapse
tried firewater not working asking to start the process again saying nasty chaser , then tried revone it reports success but when i check the bootloader it says s-on i just don't know what to do.

What happens when you choose recovery from bootloader?

finally success took a leap of faith used unlock token from htc and it worked yay.
Thanks to all the people who advised me and helped me troubleshoot.

can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?

Slim Shady said:
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Click to expand...
Click to collapse
can you check my guide on how to do it: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method using this http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
this is a decrypted ruu.zip, so it only works with S-OFF.

got a new problem tampered text is not going away
getting error code -2 with revone

Slim Shady said:
got a new problem tampered text is not going away
Click to expand...
Click to collapse
WHY?? (how about more details next time )
EDIT: read the guide!!

nkk71 said:
WHY?? (how about more details next time )
EDIT: read the guide!!
Click to expand...
Click to collapse
Actually issue was dd commands and revone wasn't working for tampered so tried the guru rest and voila it worked.Now atlast everything's back to stock now i can give htc my phone and tell them to change it or repair it cause of the imsi issue im facing with the phone which happened after i got jtag brick repair.

[Solved] - Returning to Stock with hboot 1.57.0000?

Hi,
I'm trying to return my HTC One m7 to stock.
I followed this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
and didn't realise this wouldn't work for HBOOT 1.57.
Subsequently my bootloader status currently shows as
*** Tampered ***
**** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
Radio-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048mb
Click to expand...
Click to collapse
How can I remove the tampered state and return this to locked? All the guides I've been able to find only show how to do it for HBOOT 1.44 up to 1.55.
Edit: Solved this by following alray's advice to use nkk71's superguide: http://forum.xda-developers.com/showthread.php?t=2541082

WastedJoker said:
Hi,
I'm trying to return my HTC One m7 to stock.
I followed this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
and didn't realise this wouldn't work for HBOOT 1.57.
Subsequently my bootloader status currently shows as
How can I remove the tampered state and return this to locked? All the guides I've been able to find only show how to do it for HBOOT 1.44 up to 1.55.
Click to expand...
Click to collapse
you first need to achieve s-off and then follow nkk71's guide to return stock (link in my signature)

I'm almost there but because I'm on hboot 1.44 and using Win 8.1, I can't move to s-on.
I'll try the final step (fastboot oem writesecureflag 3) from my work pc tomorrow which is on win 7.

WastedJoker said:
I'm almost there but because I'm on hboot 1.44 and using Win 8.1, I can't move to s-on.
I'll try the final step (fastboot oem writesecureflag 3) from my work pc tomorrow which is on win 7.
Click to expand...
Click to collapse
you can use a linux live usb (instructions are in the FAQ section of my guide)
how were you able to do all the other steps with Win8.1??; if you were following my guide the hboot downgrade would only be one of the first steps.

I used your guide to get back to 1.44 then revone to remove tampered and unlocked states. I also used firewater to get s-off for part of the steps.
I didn't realise i could downgrade the hboot so that's basically where i was going wrong.

WastedJoker said:
I used your guide to get back to 1.44 then revone to remove tampered and unlocked states. I also used firewater to get s-off for part of the steps.
I didn't realise i could downgrade the hboot so that's basically where i was going wrong.
Click to expand...
Click to collapse
depending on which method you are using, once hboot is downgraded to 1.44, that would only be the first "fastboot flash zip ruu.zip", the second one also needs to be completed
I'm not sure at what stage and method you are at, but going s-on sounds like a very bad idea at the moment

Currenttly I have ARHD 53 installed.
Bootloader is *** LOCKED *** with hboot 1.44.
My CID is 1111111 and I'll be using an o2 UK RUU.
The linux live cd method is handy but I'll just wait til I get to work tonight to work in bootloader from my win7 machine there.
According to this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/ I only need to get back to s-on then flash the RUU.
but according to your guide I have to flash RUU first then s-on is optional?

WastedJoker said:
Currenttly I have ARHD 53 installed.
Bootloader is *** LOCKED *** with hboot 1.44.
My CID is 1111111 and I'll be using an o2 UK RUU.
The linux live cd method is handy but I'll just wait til I get to work tonight to work in bootloader from my win7 machine there.
According to this guide: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/ I only need to get back to s-on then flash the RUU.
but according to your guide I have to flash RUU first then s-on is optional?
Click to expand...
Click to collapse
my guide uses decrypted ruu.zip(s), which can only be flashed with S-OFF. and I leave going from S-OFF to S-ON as the last step, just in case something didn't work correctly.
if you are going to use the 4.20.206.16 RUU.EXE then you can/should go S-ON first, and hope it works (the 4.xx RUUs have been known to sometimes give trouble depending on the PC configuration)

nkk71 said:
my guide uses decrypted ruu.zip(s), which can only be flashed with S-OFF. and I leave going from S-OFF to S-ON as the last step, just in case something didn't work correctly.
if you are going to use the 4.20.206.16 RUU.EXE then you can/should go S-ON first, and hope it works (the 4.xx RUUs have been known to sometimes give trouble depending on the PC configuration)
Click to expand...
Click to collapse
Your way makes a lot of sense! I'll get the RUU from your guide links

WastedJoker said:
Your way makes a lot of sense! I'll get the RUU from your guide links
Click to expand...
Click to collapse
for O2, you'd need to use the CWM restore method, which is a bit longer.
But here's a thought, why not stay S-OFF, try the 4.20 RUU.EXE on the Win7 PC you have, if it works then you can downgrade hboot again, go S-ON and run it again.
(because I don't recommend you go from S-Off to S-On on hboot above 1.54, as i mentioned in my guide)
if you do want to use the CWM method of my guide, let me know, and I'll link the files you'll need
EDIT: remember to change your cid back to the original, before any of this

nkk71 said:
for O2, you'd need to use the CWM restore method, which is a bit longer.
But here's a thought, why not stay S-OFF, try the 4.20 RUU.EXE on the Win7 PC you have, if it works then you can downgrade hboot again, go S-ON and run it again.
(because I don't recommend you go from S-Off to S-On on hboot above 1.54, as i mentioned in my guide)
if you do want to use the CWM method of my guide, let me know, and I'll link the files you'll need
EDIT: remember to change your cid back to the original, before any of this
Click to expand...
Click to collapse
I'll use the CWM restore method then (http://forum.xda-developers.com/showpost.php?p=47794219&postcount=5 - posting this link for my own reference)

WastedJoker said:
I'll use the CWM restore method then (http://forum.xda-developers.com/showpost.php?p=47794219&postcount=5 - posting this link for my own reference)
Click to expand...
Click to collapse
I've posted the files you'll need directly in my thread:
http://forum.xda-developers.com/showthread.php?p=54857652&postcount=1068

nkk71 said:
I've posted the files you'll need directly in my thread:
http://forum.xda-developers.com/showthread.php?p=54857652&postcount=1068
Click to expand...
Click to collapse
I'm stuck at this step:
Step 3: restore nandroid
fastboot boot CWM.img
Error in cmd:
fastboot boot cwm.img
downloading 'boot.img'...
OKAY [ 1.120s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.120s
What's going on here?

WastedJoker said:
I'm stuck at this step:
Step 3: restore nandroid
fastboot boot CWM.img
Error in cmd:
fastboot boot cwm.img
downloading 'boot.img'...
OKAY [ 1.120s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.120s
What's going on here?
Click to expand...
Click to collapse
You are locked / relocked, that comes later in CWM restore method.
If you don't wanna use unlock token, check the last few pages in my thread about masked firmware and adb commands to unlock

nkk71 said:
You are locked / relocked, that comes later in CWM restore method.
If you don't wanna use unlock token, check the last few pages in my thread about masked firmware and adb commands to unlock
Click to expand...
Click to collapse
I had the bin file handy and just tried the unlock:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
Gonna look in your thread for those other methods
here's my getvar:
fastboot getvar all
(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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(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.076s
I retried the unlocking and it worked this time.
Weird.

WastedJoker said:
I had the bin file handy and just tried the unlock:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
Gonna look in your thread for those other methods
here's my getvar:
fastboot getvar all
(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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(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.076s
Click to expand...
Click to collapse
I'm on my mobile, so can't help you right now, but it should be on one of the last pages.
Also after a getvar all on hboot 1.44 bootloader will freeze, so you need to unplug and replug the USB cable

nkk71 said:
I'm on my mobile, so can't help you right now, but it should be on one of the last pages.
Also after a getvar all on hboot 1.44 bootloader will freeze, so you need to unplug and replug the USB cable
Click to expand...
Click to collapse
Yeah, I saw that on your thread.
I'm back on track now - just pushing the nandroid. Thank you so much for your help, you've been amazing!

WastedJoker said:
Yeah, I saw that on your thread.
I'm back on track now - just pushing the nandroid. Thank you so much for your help, you've been amazing!
Click to expand...
Click to collapse
Ah good luck then, cause I'm getting some bad looks here, texting right now

nkk71 said:
Ah good luck then, cause I'm getting some bad looks here, texting right now
Click to expand...
Click to collapse
All done, thanks again

WastedJoker said:
All done, thanks again
Click to expand...
Click to collapse
Nice :laugh:
could you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title

HTC One rooted - Return for Warranty [SOLVED]

Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help

nurogo said:
Hi,
I have a HTC One that is rooted, and has the problem with the camera (Pink in dark places).
I've have MIUI custom rom, but to return for warranty i need to have the oficila rom.
What do i need to do for restore to the official rom, to turn s-on, and delete all races of a root phone.
I've only changed the software, not the CID.
MY CID is HTC_304.
Thanks for all the help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need

nkk71 said:
http://forum.xda-developers.com/showthread.php?t=2541082
please post a "fastboot getvar all" (excluding IMEI and s/n) and i'll check which files you need
Click to expand...
Click to collapse
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks

nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4232mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks
Click to expand...
Click to collapse
Anyone, please?

nurogo said:
Anyone, please?
Click to expand...
Click to collapse
use the 1.28.401.7 RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
follow guide linked by nkk71

nurogo said:
Thanks,
Here is the data of "fastboot getvar all":
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) security: on
Thanks
Click to expand...
Click to collapse
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked

nkk71 said:
I thought you said you were S-OFF, but you are actually S-ON, so bootloader can only show RELOCKED
so two choices:
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
B) RELOCK bootloader (though you may have a hard time with a RELOCKED bootloader for warranty):
fastboot oem lock (to RELOCKED bootloader)
then use the ruu.exe alray linked
Click to expand...
Click to collapse
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?

nurogo said:
Thanks for all the help.
If I have understood correctly, i will not be able to get s-on after installing the stock rom.
I have to put s-off in order to install the stock rom?
Then to put in s-on, always appears relocked?
There are possibilities to install the stock rom without removing the S-ON?
Click to expand...
Click to collapse
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.

nkk71 said:
no, sorry if I confused you.
for bootloader to say LOCKED (the same way it was when you first got it), you need to get S-OFF.
with S-OFF, you can set it back to LOCKED, and completely "out of the box", (using the ruu.zip process with the file i linked earlier), and can even go back S-ON (as mentioned in my guide) and it will still say LOCKED.
but without S-OFF, you can only get bootloader to show RELOCKED.
I hope that makes it a bit clearer.
Click to expand...
Click to collapse
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7

nurogo said:
Thanks,
Now i get it.
This is the guide i must follow, right?
A) Get S-OFF using firewater, rumrunner, or revone
then follow RUU.ZIP method (post #4) in my guide using: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
Click to expand...
Click to collapse
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"

nkk71 said:
yes, first get s-off - should be easy enough considering your current getvar output, you have plenty of options, once you have s-off, you can use ruu.zip method to return to 100% "out of the box"
Click to expand...
Click to collapse
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?

nurogo said:
Tried to put s-off, but it gives the error:
revone failed (error code = 1)
Why this error? What i did wrong?
Click to expand...
Click to collapse
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.

nkk71 said:
what date is show in bootloader, if it is before June 2013, then install the ROM mentioned here:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and try revone again, otherwise use rumrunner or firewater if revone is giving you a hard time.
Click to expand...
Click to collapse
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4

nurogo said:
Done...
Now i have s-off...
Now, what do i have to do is follow step by step the post #4 of your guide, correct?
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=4
Click to expand...
Click to collapse
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway

nkk71 said:
yes correct, follow instructions in the guide, if you already have a custom recovery installed:
1) use adb commands to remove TAMPERED and set LOCKED
2) flash the following ruu.zip: RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7
3) bootup once to make sure everything is OK, do not take OTA updates
4) if you believe S-ON is necessary for warranty, then go S-ON
after that you can take any OTAs you like,
but why bother since it's going to repair. where they will most like update it anyway
Click to expand...
Click to collapse
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?

nurogo said:
Thanks for all the help,
After do all that, how do i remove all traces of custom rom's (folders, files, TWRP, etc..)?
is there a way to format the phone, removing all that (like formating a hard drive)?
Click to expand...
Click to collapse
The ruu will take care of that, it will wipe everything off your phone, including anything on the virtual sdcard
Sent from my HTC One using Tapatalk

Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...

nurogo said:
Ok.. Here's the situation
Removed TAMPERED and now it says LOCKED
But when i try to copy the ruu.zip it says:
load_file: could not allocate 1034027008 bytes
error: cannot load "ruu.zip": Not enough space..
How can i solve this?
I have 20GB free of space...
Click to expand...
Click to collapse
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk

nkk71 said:
Cannot load = MyFileNameIsWrong
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Check it, but it stays the same..
Look at the image

nurogo said:
Check it, but it stays the same..
Look at the image
Click to expand...
Click to collapse
type dir in the command window
you probably see it's names RUU.zip.zip

Display mesed up.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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