Develop Bugs

[Q] Goldcard & RUU

Hello XDA,
I have here a HTC Desire HD and it's Vodafone Branded, but that doesn't need to be a problem.
I want to make an Goldcard so I can flash Stock rom, because it's soft-bricked by trying to make a goldcard and trying tools that doesn't work.
I know the tools from: http://forum.xda-developers.com/showthread.php?t=2169515 but they are forwarding me to http://psas.revskills.de/?q=goldcard to request an goldcard image file, but that site is down.
I got the tool from Revskills but I don't understand it to make an goldcard.
I have also done this earlier by an other Desire HD and that one runs custom rom now and works well and I want to do this also to my current HTC Desire HD.
Now the only problem is, the HTC Desire HD is not booting to OS, it restarts over and over and I can only enter Recovery and Fastboot(also bootloader ofc.)
How can I get this done ?

Turkdale said:
Hello XDA,
I have here a HTC Desire HD and it's Vodafone Branded, but that doesn't need to be a problem.
I want to make an Goldcard so I can flash Stock rom, because it's soft-bricked by trying to make a goldcard and trying tools that doesn't work.
I know the tools from: http://forum.xda-developers.com/showthread.php?t=2169515 but they are forwarding me to http://psas.revskills.de/?q=goldcard to request an goldcard image file, but that site is down.
I got the tool from Revskills but I don't understand it to make an goldcard.
I have also done this earlier by an other Desire HD and that one runs custom rom now and works well and I want to do this also to my current HTC Desire HD.
Now the only problem is, the HTC Desire HD is not booting to OS, it restarts over and over and I can only enter Recovery and Fastboot(also bootloader ofc.)
How can I get this done ?
Click to expand...
Click to collapse
You phone can not be stuck in a bootloop for trying to create a goldcard, which is done in in the sdcard and not in the device itself. Besides, the tools provides you another tool to create a goldcard, quoting:
...IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:
Create a goldcard using this tool: http://d-h.st/VMw, once you have the .img file patch it using the SimpleGoldCard Tool included in the tools folder. (you need a working phone for this)
Find a RUU which main version is supported and higher than yours and flash it in the PD98IMG.zip way, that is what is the goldcard for. If you have a .exe RUU, then extract the rom.zip file using this method: http://www.xda-developers.com/xda-tv...-an-ruu-xdatv/
Re run the tool and you will be able to update the hboot and unlock it...
Click to expand...
Click to collapse
What did you flash to get your device in that state? To create a goldcard you will need a working phone, so you can use the other DHD to do it.

glevitan said:
You phone can not be stuck in a bootloop for trying to create a goldcard, which is done in in the sdcard and not in the device itself. Besides, the tools provides you another tool to create a goldcard, quoting:
What did you flash to get your device in that state? To create a goldcard you will need a working phone, so you can use the other DHD to do it.
Click to expand...
Click to collapse
I tried to use AAHK for HTC Desire HD, but the website of the developer of it, is offline.
Now the phone starts, after HTC splashscreen, I see Vodafone Splash Screen and after that It keeps rebooting from HTC splashscreen.
How can I solve this ? Factory reset and format data/factory reset @ recovery doesn't solve the issue.

Turkdale said:
I tried to use AAHK for HTC Desire HD, but the website of the developer of it, is offline.
Now the phone starts, after HTC splashscreen, I see Vodafone Splash Screen and after that It keeps rebooting from HTC splashscreen.
How can I solve this ? Factory reset and format data/factory reset @ recovery doesn't solve the issue.
Click to expand...
Click to collapse
Of they did not...in fact they made things worse as you deleted the usb debugging drivers from the phone. Hack Kit hasn't been online for about 6 months now and so is support.
Your only way to get out of that is to flash a RUU.

glevitan said:
Of they did not...in fact they made things worse as you deleted the usb debugging drivers from the phone. Hack Kit hasn't been online for about 6 months now and so is support.
Your only way to get out of that is to flash a RUU.
Click to expand...
Click to collapse
Yes I understand that, but the problem is that I can't find a RUU that works for my HBOOT version. I tried 2 RUU's. If you can find a working one, it won't be a problem anymore.

Can you do a printout of your Phone via fastboot mode with
fastboot getvar all
please.

hacktrix2006 said:
Can you do a printout of your Phone via fastboot mode with
fastboot getvar all
please.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.52.27
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.161.5
(bootloader) serialno: HT0BWRX11664
(bootloader) imei: *secret*
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: VODAPE17
(bootloader) battery-status: good
(bootloader) battery-voltage: 3679mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.008s

I would hide the IMEI if i was you.
Use http://forum.xda-developers.com/showthread.php?t=2288012 which is from glevitan to make a goldcard then once you have done that download the right RUU run the .exe and in %temp% look for rom.zip
once you have done this place rom.zip in the same folder as fastboot and adb then open command prompt and cd into the directory that fastboot and adb is in.
Then type the following with the goldcard in the phone.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (Just to make sure)
fastboot reboot
This should then fix your phone.

Thank you very much for your tip en help. Didn't notice about the IMEI I would try your advice tonight when I'm home and will keep you updated.
Sent from my GT-I9300 using xda premium

hacktrix2006 said:
I would hide the IMEI if i was you.
Use http://forum.xda-developers.com/showthread.php?t=2288012 which is from glevitan to make a goldcard then once you have done that download the right RUU run the .exe and in %temp% look for rom.zip
once you have done this place rom.zip in the same folder as fastboot and adb then open command prompt and cd into the directory that fastboot and adb is in.
Then type the following with the goldcard in the phone.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (Just to make sure)
fastboot reboot
This should then fix your phone.
Click to expand...
Click to collapse
I am not sure that flashing that way will fix the device as the goldcard is in the sdcard and not the device. To locate the goldcard in the device he would need to have temp root access.
He needs to flash the ruu in the PD98IMG.zip way from the root of the sdcard.

Goldcard works both ways also if he is S-ON which he is he can't use the PD98IMG.zip way on the fastboot oem rebootRUU way to flash

hacktrix2006 said:
I would hide the IMEI if i was you.
Use http://forum.xda-developers.com/showthread.php?t=2288012 which is from glevitan to make a goldcard then once you have done that download the right RUU run the .exe and in %temp% look for rom.zip
once you have done this place rom.zip in the same folder as fastboot and adb then open command prompt and cd into the directory that fastboot and adb is in.
Then type the following with the goldcard in the phone.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (Just to make sure)
fastboot reboot
This should then fix your phone.
Click to expand...
Click to collapse
I did try this and just getting this:
Code:
sending 'zip' (293949 KB)...
OKAY [ 49.289s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(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: 89.611s

right that means the goldcard was not made successfull
"FAILED (remote: 42 custom id check fail)
the card is not valid or the process is not done correctly"
which means you need to try another sdcard and remake the goldcard.
I take it you have no custom recovery? If you really need help PM with a Teamviewer ID and password. I will then try and help.

hacktrix2006 said:
right that means the goldcard was not made successfull
"FAILED (remote: 42 custom id check fail)
the card is not valid or the process is not done correctly"
which means you need to try another sdcard and remake the goldcard.
I take it you have no custom recovery? If you really need help PM with a Teamviewer ID and password. I will then try and help.
Click to expand...
Click to collapse
I can't make a goldcard because the phone isn't booting, it has a bootloop. Could you please provide me support by Google Talk(Hangout) or something else what would be faster and easier to communicate ?
I won't share your private account details like your username, but It would be easier for me and you to talk to each other.

If you could wait till tomorrow i can get you the HTC Dev bootloader in a oem rebootRUU .zip and give you instructions on how to restore the phone fully with S-Off as well.
I am on GMT timezone and its late. PM me tomorrow and i will give you my google hangout or better still get teamviewer installed so i can remotely do the whole thing for you.

hacktrix2006 said:
If you could wait till tomorrow i can get you the HTC Dev bootloader in a oem rebootRUU .zip and give you instructions on how to restore the phone fully with S-Off as well.
I am on GMT timezone and its late. PM me tomorrow and i will give you my google hangout or better still get teamviewer installed so i can remotely do the whole thing for you.
Click to expand...
Click to collapse
I'm a IT guy and ofcourse I have Teamviewer and I will be glad if you can help me tomorrow... It will be finally again that's someone is connecting to me by Teamviewer hahaha and I'm also on GMT timezone, 1:56 here (Netherlands) I will PM you now for tomorrow, with my Gmail for Hangout

I have added you will not be around till after 11:00am like, best to teamviewer in that way i can just restore your phone to working order and have S-OFF

[Q] Soft brick - can't push ROM to phone

Hello,
I am trying to fix my issue and have done a ton of reading but can't figure out where to go from here. I've had my phone rooted for months and tried to flash a newer custom ROM today and it ended up locking my phone into a boot loop. I was able to get out of it and had to re install a recovery tool (have installed both CWM and TWRP and they work fine). But I can't actually get a ROM back onto my phone because I don't have one on the SD card and I can't get one to it. I just want to put a stock ROM back onto it at this point.
I can't boot into windows to access the SD card because whenever I boot the phone normally it just goes back to boot looping. I have tried ADB push when in recovery to put a ROM on the SD card and I continually get permission denied when I try to do that. I have tried ADB sideloader and I can't get that to work either. How can I go about getting a ROM to my phone so I can flash it via CWM/TWRP?
Fastboot works fine and I can flash recoveries no problem. ADB appear to work but I can't understand why I can't just get push to work. Any help would be greatly appreciated.
HTC One M7 on Verizon.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.

NotATreoFan said:
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
Click to expand...
Click to collapse
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached

factor00 said:
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
Click to expand...
Click to collapse
What about fastboot?

NotATreoFan said:
What about fastboot?
Click to expand...
Click to collapse
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!

factor00 said:
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
Click to expand...
Click to collapse
I haven't done anything RUU in a while, so I don't want to steer you wrong. But I believe you can use decrypted to get everything up and running. Check the general forum for a guide on returning to stock.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Just remember to keep s-off while running the ruu

[Q] [RUU] Error: 152. Unable to Restore TMob One M8

Hi, thanks for reading.
I was running the latest version of CM on my One M8. Decided I wanted to revert to stock ROM to regain HTC camera and wifi calling functionality. Figured an RUU would be the easiest way.
Here's where I probably screwed up. Downloaded and ran the RUU for ver. 2.xxx from HTC. Forgot to relock bootloader, but it rebooted early back into CM no problem. Relocked bootloader. Ran again.
I should have known to pause when I saw that my version was 1.5xx but it seemed fine with updating versions as part of the process.
Then it failed again, error 152. Was able to reboot into CM again this time.
I did some googling and reading and saw one guy say that he was able to fix by simply running the RUU again once it was in the "four exclamation marks in triangles" screen, which is where I was after the next try, so I ran again. Another error 152.
So finally I realized maybe I needed the 1.5xx RUU. DL'd that, tried running, "error, wrong version." Because now it thinks my phone is on ver 2.xxx.
Now I can't get the phone to boot into recovery or into bootloader. No clue where to go from here. I'd really appreciate your help. Gosh I screwed up.
The last lines in the RUU log (1.5xx) are:
Code:
<T205408><DEBUG><OUT>Execution time is 6(s)</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
and the prior try, RUU log 2.xx:
Code:
<T202916><DEBUG><OUT>(bootloader) [RUU]WP,system,37</OUT>
</DEBUG></T202916>
<T202917><DEBUG><OUT>(bootloader) [RUU]WP,system,42</OUT>
</DEBUG></T202917>
<T202939><DEBUG><OUT>(bootloader) ...... Failed</OUT>
</DEBUG></T202939>
<T202941><DEBUG><OUT>(bootloader) current_image_number=0</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>Execution time is 216(s)</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAIL51 partition update fail</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T202941>
<T203947><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203947>
<T203948><DEBUG><OUT />
</DEBUG></T203948>
</LOG>
Thanks.
Update 1: can recognize device using "fastboot devices" but not "adb devices." haven't tried pushing/pulling anything yet. Saw someone in another thread tried installing via command line. Not sure which .zip I should use, as there are a ton of options on XDA, or if this is what I should try next.
Update 2: there are seemingly two versions of the "four exclamation points" screen: one is dim and has the orange led showing and the other is bright without led. Bright without LED is what I got after "flashboot reboot-bootloader". Worried that the bright one may deplete battery.
3: Since I can't otherwise boot into a recovery, should I try to flash a recovery?
4: Not sure if this is useful but:
Code:
getvar version-main is indeed listed as 2.22.531.5
phone CID T-MOB010
phone MID 0P6B13000
5: Phone was S-ON. Wasn't able to get S-OFF using the free method.
6: Was reading another thread with similar error (but One X), this seemed to be useful to the one guy:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ###
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
7: Tried to flash a stock recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery Tmo-M8-2
.22.531.5-recovery.img
target reported max download size of 1830612992 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.533s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.430s
8: Tried to create some RUU .zips per this method http://forum.xda-developers.com/showthread.php?t=2534428 but the zips say that archive is corrupted. EDIT: MD5's for the .exe's do check out.
9: Used a zip repair to repair those RUU .zip's. Noticed that their android-info files have "hbootpreupdate:12" but my phone has "hbootpreupdate:11" might that be an issue?
Sad Edit: I tried some stuff, nothing seemed to work. Freshly downloaded from an alternative mirror the 2.2xx RUU and booted into RUU via fastbooth before running it. Everything said it went perfectly "CONGRATULATIONS ROM UPDATED! Rebooting!" etc.
My phone is bricked. Never woke up from that reboot. My computer keeps trying to recognize the device via usb, but nothing.

I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?

grim489 said:
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
Click to expand...
Click to collapse
Yeah I tried unlocking the bootloader while fastboot was still recognizable, but it wouldn't work.
Not sure about the unsigned zips thing. Would that also go for the RUU? I thought those were signed/straight from HTC.
I'll try it once more, but it should have been fully charged last time I gave it a try. Computer shows an intermittent "QHSUSB_Bulk" but not sure where to go from there. Found threads for other HTC phones and tried their methods, but it got to the point where the one guy was supposed to go through Ubuntu to manually install individual .imgs to the phone, but I think he had somehow managed to get fastboot to work.

Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.

grim489 said:
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
Click to expand...
Click to collapse
Yeah it's especially weird because I thought with S-ON it was supposed to be hard/impossible to override ?boot.ini (not sure, don't quote me on that) anyway. But yep, won't boot at all.

Help!! destroyed my HTC one M8

My HTC one M8 system UI keeps crashing every time i boot up the phone
How i got to this position
For some reason i was not able to download anything to the phone (yes, there was space available), so i decided to factory reset the phone. unfortunately that was no help. From there i decided to use twrp recovery to wipe everything, Me being a smart guy wiped everything, including the system ( and no i did not make a back up anything ). After got a hold of a mirco sd card and flashed a version of a htc one system file i found at http://forum.xda-developers.com/showthread.php?t=2694994 . I got the phone to boot up ( not booting up from before without a system), but the system UI keeps crashing every time i boot up the phone. Found a thread in xda with the same problem, http://forum.xda-developers.com/showthread.php?t=2694994, and the solution is to get a hold of the stock recovery (not sure if it will work for me). Finally i jump over to an other thead, http://forum.xda-developers.com/showthread.php?t=2701376, saying i need to find out my cidnum. I used fast boot to get it and my version of cidnum is BS_US001 which i could not find on the list.
Long story short
Couldnt download on my phone
wiped my system by mistake (no backs)
flash android revolution hd version of kitkat
system ui keeps crashing
think stock recovery will fix it
getting a random cidnum is BS_US001 and am not sure which stock recovery to flash
Please help !!!!
thank you

Post your fastboot getvar all minus serial no. & imei no.
This will help to find the right ROM for you

ckpv5 said:
Post your fastboot getvar all minus serial no. & imei no.
This will help to find the right ROM for you
Click to expand...
Click to collapse
Please see below.
I found that there is a nandroid back up, on the below thread but how can i flash it. cannot really do anything to the phone.
looking to go stock, if possible
http://forum.xda-developers.com/showthread.php?t=2701376
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: BS_US001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0

Just run RUU to have everything back to stock.
Download RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - command fastboot oem lock
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed

ckpv5 said:
Just run RUU to have everything back to stock.
Download RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - command fastboot oem lock
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed
Click to expand...
Click to collapse
I will give this a try in the morning
I will let you know how it goes, thanks for the help

ckpv5 said:
Just run RUU to have everything back to stock.
Download RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - command fastboot oem lock
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed
Click to expand...
Click to collapse
I tried running the program twice, but it failed both times.
it couldnt update the system after erasing eveyrthing.

What error ?
If RUU is not an option for you
you also can fastboot flash the RUU in zip format.
Download the RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2-decrypted.zip from here : https://www.androidfilehost.com/?fid=95897840722644595
Rename it to RUU.zip
Download the htc_fastboot.exe here : http://forum.xda-developers.com/showthread.php?t=2735235
Put device in bootloader mode, then run command:
fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip[/COLOR]

ckpv5 said:
What error ?
If RUU is not an option for you
you also can fastboot flash the RUU in zip format.
Download the RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2-decrypted.zip from here : https://www.androidfilehost.com/?fid=95897840722644595
Rename it to RUU.zip
Download the htc_fastboot.exe here : http://forum.xda-developers.com/showthread.php?t=2735235
Put device in bootloader mode, then run command:
fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip[/COLOR]
Click to expand...
Click to collapse
"what error?" ------ not sure to be honest, it just failed while it was trying to write the system.
Tried your new suggestion and got this error
sending 'zip'... (1494067 KB) OKAY
sending time = 42.386 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 42(s)

Getting back to stock for OTA update

Hello fellow XDA users!
I just bought my m8 and it came with Software status modified, bootloader unlocked, philz touch, S-on but Super CID.
The problem now is that i can't OTA and it is still in kitkat
So I started to work on it tonight, and I can't get it back to stock :
I have flashed TWRP, made a boot backup to create necessary folders, and downloaded a stock nandroid backup for my main version, 3.28.401.6.
Wiped the phone, restored the rom, flashed stock recovery and here in bootloader my software status is still modified, so no OTA possible.
Suppose it has something to do with superCID, but i can't modify it anymore as I'm not s-off and I don't know what is the stock CID for the phone, just bought it.
Sorry to create another boring thread about OTA updates btw, but I just can't understand what I'm doing wrong here (coming from a samsung device, but I've been reading a lot here, and still no luck about my situation.)
http://forum.xda-developers.com/showthread.php?t=2701376 this is the thread where I downloaded the Nandroid, if it has any importance... It is the one rooted but which has apparently no effect on OTA
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845 this seems interesting as I could maybe flash a RUU of same version to become unmodified but i'll ask you before doing anything stupid
Thank you all for your future answers
EDIT : Here are info from getvar all if you need (removed serialno and imei)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s

WoBble12 said:
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) security: on
Click to expand...
Click to collapse
With the above current CID/MID ... you can only update to Marshmallow either with T-MOB US RUU or Developer Edition RUU as both work on MID 0P6B13000
You current software 3.28.401.6 won't do any good as that is workable for OTA when your MID is 0P6B10000
So if you want a EU version, you need to spend USD25 to S-Off the device, else just go for Developer Edition RUU.
Step 1 : install 6.12.1540.4 firmware
You can get the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Step 2 : install 6.12.1540.4 RUU
Download : http://www.htc.com/us/support/htc-one-m8/news/

Ok, thank you for the quick reply!
I was mistaken by the back plate of the device saying OP6B100, so didn't verify the mid in the adb log...
Now for a few questions, what are the differences between the dev version and the European one? Anything related to getting signal or something?
If I just update fw and rom with your two links, it will work even with my software status says "modified"? And Will it change back to official status?
Are updates going to be better if I go s-off and european again or is it the exact same version?

1. I don't see any significant difference with EU and Dev Ed except the obvious radio config.
But both worked fine for me in Asia region.
2. You should get the official status.
3. I don't see a point to S-Off as there is no more further OTA offered by HTC.
Once you updated to Marshmallow, you can always unlock the bootloader and install any custom ROM that you like. Most important is to have Marshmallow firmware (or at least Lollipop), doesn't matter whether it is EU or Dev Ed.

Ok, thanks again for the replies! Will try dev software, and if it doesn't work I'll pay for s-off

Ok so... I tried to update firmware, followed the tutorial, but i'm stuck at flashing the RUU. I went to the link you sent me, downloaded the 1.4 GB file, and now I have a zip file and a .exe file. The .exe will just start, say me it installs installshield, ask me to agree with the terms of licence, and close.
So I searched a bit, and i tried to flash the RUU as I did for the firmware, but now rebooting just leads me to a black screen, and the RUU fails.
please tell me what I did wrong so I can fix it.
Here is the ADB output :
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s

You can't use generic fastboot.exe to flash the RUU.zip, you need to use htc_fastboot.exe
Read this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your RUU.zip (not the one in the guide)

sorry to bother for this but what is my RUU.zip you are talking about?
And i've tried with HTC fastboot and no luck neither...

You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Can you post your current fastboot getvar result ? Need to see that you successfully installed the firmware.zip

ckpv5 said:
You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Click to expand...
Click to collapse
Ok, just saw this at the moment on another thread, was going to try with the %temp% method, the command you made bold was the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.zip file that I renamed to be able to flash it more easily lol, what a noob I am ^^ so i'm going to extract this rom.zip and flash it, hope it works now! all fastboot commands have to be replaced with "htc fastboot" now, or only the flashing one?
Once again, thank you! (Using the thanks button at each of your posts too, don't worry )
yes, I verified in bootloader it says OS-6.12.1540.4 !!! Win! now just estracting the Rom from the temp folder!

htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)

ckpv5 said:
htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)
Click to expand...
Click to collapse
I've done the 1st method, and now after a flash that went well, i'm stuck in bootloader, with os version bein written in red and showing two times the version number, second one in parenthesis.
Instead of having options to power down etc, I only have a orange RUU option which is selected but I can't validate with power button, and in ADB I did command to reboot to bootloader but not doing anything now...

When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip

ckpv5 said:
When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip
Click to expand...
Click to collapse
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 8.033s
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange :/

Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange​
Can you use the power button to select it to get to RUU mode then fastboot reboot-bootloader or press & hold buttons method ?

ckpv5 said:
Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
Click to expand...
Click to collapse
I don't have the rom on micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?

WoBble12 said:
I don't have the rom one micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?
Click to expand...
Click to collapse
Run command fastboot reboot-bootloader
to get to bootloader
check the OS now written in red or green
if red, reflash firmware.zip not rom/RUU.zip
if green .. just reboot and wait for awhile and see how it goes.
if it is stuck after 10 minutes .. reflash RUU/rom zip

I'm now on marshmallow! Tastes sweet lol!
Can't test the signal at the moment as I have to cut my micro SD to the right size, and I have no time for it. I will do this tomorrow , and reply back here to say if it worked. Anyway, couldn't have done this without you so big thanks for this and big thanks to all the XDA community!

WoBble12 said:
....I have to cut my micro SD to the right size....
Click to expand...
Click to collapse
Hehe .. I believe you wanted to say to cut SIM card, not microSD
Great to know you managed to update.

Yes of course, simcard ^^
So I can now say that the phone is working and I have signal through my card.
Only weird thing is that after installing a few apps, system is taking up 8+ gig's of storage, which seems really big to me. But hey, it's a 32gig's one so I'm not afraid