Develop Bugs

I need RUU for HTC_001

Hello,
Could somebody help me find the correct RUU for READCID:HTC_001
I guess it is on here somewhere, but done a brief search and found nothing, in a rush.
Your help would be much obliged
Thank you
Js3ph

js3ph said:
Hello,
Could somebody help me find the correct RUU for READCID:HTC_001
I guess it is on here somewhere, but done a brief search and found nothing, in a rush.
Your help would be much obliged
Thank you
Js3ph
Click to expand...
Click to collapse
RUU 1.29.401.11 is what youneed. You will find it here http://forum.xda-developers.com/showthread.php?t=1543604.

bobsie41 said:
RUU 1.29.401.11 is what youneed. You will find it here http://forum.xda-developers.com/showthread.php?t=1543604.
Click to expand...
Click to collapse
Thank you very much
Just for future reference, how do I know exactly what RUU to get ?

js3ph said:
Thank you very much
Just for future reference, how do I know exactly what RUU to get ?
Click to expand...
Click to collapse
Any one in this form: x.xx.401.xx
The 401 is the part that differs with different cid's.

Hi guys n gals!
I need help lol.
I want to send in my phone for repair under warranty so I'm trying to unroot, as you do...
The problem I'm having is finding the right files, RUU and also the right version to go with the right kernel. Also which order to do things.
I have been looking at a lot of tutorials and posts, a lot of which have dead links to the files they refer to.
My CID is HTC_001. So I believe I need to have the RUU with 401 in the version no. I have located this file RUU_Endeavor_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe which seems to be available.
My hboot is 1.39 and I'm not sure how this affects things?
I'm currently running venom x version 4.0.7 with stock kernel.
I don't want to take up a lot of anyone's time, but just to let me know what the right files are and if available, where to get them.
Thanks a million.
Actually this is a newer version from the same place RUU_Endeavor_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
Would this be a better option?

Give us the outcome of the command:
fastboot getvar all
Sent from my HTC One X

n1kos said:
Give us the outcome of the command:
fastboot getvar all
Sent from my HTC One X
Click to expand...
Click to collapse
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Colin>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.401.31
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4152mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.828s
C:\Documents and Settings\Colin>
Thanks

The ruu you last posted looks like the one you need.
Sent from my One X using xda premium

magnetboard said:
The ruu you last posted looks like the one you need.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Thanks, I'm downloading it now. Is there anything else I need to be careful with? Like which stock recovery do I need?
And as for re-locking the bootloader, that has to be done last right?

To run an ruu you need locked or relocked bootloader.
Fastboot oem lock
Once you dl the ruu put the phone in fastboot usb and right click the .exe run it as administrator. Let the ruu to complete and you are back on stock.
Sent from my HTC One X

n1kos said:
To run an ruu you need locked or relocked bootloader.
Fastboot oem lock
Once you dl the ruu put the phone in fastboot usb and right click the .exe run it as administrator. Let the ruu to complete and you are back on stock.
Sent from my HTC One X
Click to expand...
Click to collapse
Just done this, recovery flashed bootloader relocked and now when running ruu it says battery is below 30%. I made sure I charged it fully before starting so it must be wrong. Any ideas?

Charge the phone to full and do the process
Sent from my HTC One X

n1kos said:
Charge the phone to full and do the process
Sent from my HTC One X
Click to expand...
Click to collapse
It was fully charged. Now I can only get into the bootloader, will it charge there?
Never mind I shut it down and am charging now...

colinmc8 said:
It was fully charged. Now I can only get into the bootloader, will it charge there?
Never mind I shut it down and am charging now...
Click to expand...
Click to collapse
Ok I was charging with the phone off till the led went green. Tried to run the ruu again and same problem, I don't think its charging when its off?
Any suggestions?

ok I really could use some brainy persons help with this!
I just re-unlocked the bootloader and now I´m back in venom but I think with stock recovery.
I tried running the ruu again with the phone fully charged and it still says the battery is below 30%. How can this be???
Please help me someone, I have spent all day trying to sort this and none the wiser for my efforts!
Thanks.

Please help .might really be bricked

I unlocked and installed twrp and 4.4.3 gpe rom on an att m8. Then tried to update to 4.4.4 and my phone went into bootloop. I booted to bootloader and now its a black screen and hboot 3.18.0.0000. Now when I try to load recovery , the twrp image comes up blinks a couple times and goes into boot loop. I've tried reflashing recovery but it doesn't seem to help.
I cant seem to get anything to work. All I can do is play around with the bootloader and fastboot
help please

this is my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

I also cant run the 1.58 ruu because my hboot is 3.18 and my cid is cws__001.
this totally sucks

First of all delete your serial and IMEI asap. And try this fastboot command :
Fastboot erase cache
Then enter the recovery

Mr Hofs said:
First of all delete your serial and IMEI asap. And try this fastboot command :
Fastboot erase cache
Then enter the recovery
Click to expand...
Click to collapse
failed remote not allowed
any other ideas

Failed remote not allowed is in most cases an indication that the bootloader is locked/relocked

First unlock your phone . Download a compatible kernel for your att m8 4.4.x.
Extract kernel.zip and flash boot.img with adb in fastboot.

Mr Hofs said:
Failed remote not allowed is in most cases an indication that the bootloader is locked/relocked
Click to expand...
Click to collapse
its unlocked, I was able to install phillz recovery but it still bootloops. I do have enough time to wipe/format real quick. any ideas?

amirsardari said:
First unlock your phone . Download a compatible kernel for your att m8 4.4.x.
Extract kernel.zip and flash boot.img with adb in fastboot.
Click to expand...
Click to collapse
I am unlocked and I downloaded a att 1.58 rom and flashed the boot.img . it took but im still boot looping

Try this
http://forum.xda-developers.com/showthread.php?p=54200899
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 08:34 AM ---------- Previous post was at 08:32 AM ----------
I use it to completely restore to stock again. Just read the ENTIRE INSTUCTIONS, i am on at&t also.
Sent from my HTC One_M8 using Tapatalk

joshzdad2013 said:
Try this
http://forum.xda-developers.com/showthread.php?p=54200899
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 08:34 AM ---------- Previous post was at 08:32 AM ----------
I use it to completely restore to stock again. Just read the ENTIRE INSTUCTIONS, i am on at&t also.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
thanks. but fails after signature check. I think this is done for

I'm thinking without s-off, having a 3.18 hboot and cws__001 cid this phone is going in the garbage today

hugebulge said:
I'm thinking without s-off, having a 3.18 hboot and cws__001 cid this phone is going in the garbage today
Click to expand...
Click to collapse
If cwm Philz is working take another Rom and flash it...what's the problem? Or all recoveries are broken? There are also complete stock Roms take one of them root it and s-off...if Firewater doesn't work use sunshine, it's really worth it to pay 25$ if you say that phone is going into garbage...means you want to buy another one...except try to s-off it and yea...also if you want to update the Rom via official ota you need always the stock recovery otherwise it will never work...

One-M8-Master said:
If cwm Philz is working take another Rom and flash it...what's the problem? Or all recoveries are broken? There are also complete stock Roms take one of them root it and s-off...if Firewater doesn't work use sunshine, it's really worth it to pay 25$ if you say that phone is going into garbage...means you want to buy another one...except try to s-off it and yea...also if you want to update the Rom via official ota you need always the stock recovery otherwise it will never work...
Click to expand...
Click to collapse
philz works for 8 seconds then bootloops and twrp just blinks then bootloops. I cant flash any rom so their is no chance of firewater or sunshine. thanks for the 25$ offer but I think ill call htc and pay to have the motherboard replaced or just smash it to pieces and buy another phone.
Is their any way of changing the cid without s-off? I think I remember getting supercid on the m7 without s-off

hugebulge said:
philz works for 8 seconds then bootloops and twrp just blinks then bootloops. I cant flash any rom so their is no chance of firewater or sunshine. thanks for the 25$ offer but I think ill call htc and pay to have the motherboard replaced or just smash it to pieces and buy another phone.
Is their any way of changing the cid without s-off? I think I remember getting supercid on the m7 without s-off
Click to expand...
Click to collapse
No other way...but you can try something.....I think there are different twrp or Philz images because of the different variants of the phone...so try to get the real one for your device..maybe that should be the problem...if not try fastboot erase cache ..but I think it's more because of the wrong image..
All those things are user issues so no need to bash HTC or the phone because you are doing things wrong

One-M8-Master said:
No other way...but you can try something.....I think there are different twrp or Philz images because of the different variants of the phone...so try to get the real one for your device..maybe that should be the problem...if not try fastboot erase cache ..but I think it's more because of the wrong image..
All those things are user issues so no need to bash HTC or the phone because you are doing things wrong
Click to expand...
Click to collapse
I 100% agree with you that it is completely my fault and not HTC. Im not bashing HTC at all, I'm going to buy another m8. Smashing would just make me happy after spending 9 hours so far trying every possibility over and over.
It is totally bricked though. I had another m8 before this phone and upgraded the same way but it was s-off and I didn't have this problem. Firewater didn't work on this phone. The problem is that something is corrupted and their is no correct ruu for 3.18 hboot with CWS__001.

HTC One M8 Telus OTA Firmware.zip

Hey so I had converted my M8 to GPe but am now selling it so I'm putting it back to Sense. Everything's working except for the wifi which I had issues with in the past from not flashing the Telus firmware.zip again from a 4.4.4 OTA file. At this link http://d-h.st/BfV the OTA file is there but there's only two fake looking download buttons that Chrome says both are malicious. One downloads an .exe and the other gets outright blocked. Can anyone help me out with finding the OTA file for Telus?
Thanks, I'm selling the phone in a few hours and am freaking as the wifi doesn't currently work! :/

Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.

Hendrycks said:
Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.
Click to expand...
Click to collapse
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?

Seanie280672 said:
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?
Click to expand...
Click to collapse
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!

Hendrycks said:
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!
Click to expand...
Click to collapse
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.

Seanie280672 said:
first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts.
Click to expand...
Click to collapse
Sometimes is a full package, sometimes its not. You're right, that sometimes if not all modules were updated (from the preceding OTA) typically its not a full package (only includes the parts that were updated).
Flashing firmware zips without knowing exactly what you are doing is really dangerous. I've seen folks flash a "partial" firmware, that didn't contain all the bootloader modules; only 2 of the 3, and the one that wasn't updated didn't correspond to the 2 that were. BRICK

Seanie280672 said:
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.
Click to expand...
Click to collapse
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?

Hendrycks said:
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?
Click to expand...
Click to collapse
Did you change your CID and MID on your phone before flashing the dev edition firmware ?

Seanie280672 said:
Did you change your CID and MID on your phone before flashing the dev edition firmware ?
Click to expand...
Click to collapse
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip

Hendrycks said:
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip
Click to expand...
Click to collapse
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.

Seanie280672 said:
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.
Click to expand...
Click to collapse
If the RUU was an .exe how can I edit it?

Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?

Hendrycks said:
Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?
Click to expand...
Click to collapse
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.

Seanie280672 said:
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.
Click to expand...
Click to collapse
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.

Hendrycks said:
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.
Click to expand...
Click to collapse
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.

Seanie280672 said:
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.
Click to expand...
Click to collapse
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?

Hendrycks said:
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?
Click to expand...
Click to collapse
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.

Seanie280672 said:
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.
Click to expand...
Click to collapse
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?

Hendrycks said:
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?
Click to expand...
Click to collapse
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.

Seanie280672 said:
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.
Click to expand...
Click to collapse
Sounds good thanks

HTC ONE M8 stuck in bootloop

Hey guys
I know there are similar posts out there but none who describe my exact problem^^
It's like this: Earlier today, I wanted to go back to stock, fully. Which means I downloaded the stock backup and put it on my phone with TWRP. Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
As far, as good, everything worked just fine. And to have it completely back to stock (except for the still unlocked bootloader) I came up with the glorious idea of restoring to factory settings using the options in the phone's settings... aaaand now I'm stuck in the bootloop.
I meanwhile figured out how to enter the bootloader (volume up + power til screen turns fully black, then volume down) and I'm also able to access stock recovery through that... I of course tried factory resetting it through the bootloader and the recovery, I also took the sim card out as somewhere was suggested... but ultimately, it always goes back to the bootloop.
When connecting to the PC I hear the connecting sound... but that's it. It doesn't show up and thus I also can't access it through fastboot/adb
I ran out of ideas myself, do you have any?^^
Thanks!

M4C00kie said:
Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
Click to expand...
Click to collapse
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
M4C00kie said:
I also can't access it through fastboot/adb
Click to expand...
Click to collapse
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
adb requires being in OS or recovery (and I'm not sure if stock recovery supports adb). And for the most part, fastboot is what you need to recover.
Need more info to help further. What CID version of the phone? If OS version number is shown on hboot screen, post it here. What are the version numbers or the stock nandroid, and the stock recovery you installed? If you can get fastboot work, do fastboot getvar all, and post the output.

redpoint73 said:
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
Click to expand...
Click to collapse
That's because I was using an older guide... good to know^^
redpoint73 said:
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
Click to expand...
Click to collapse
That's what's strange... on the phone, it's showing FASTBOOT USB and it even makes this sound when connecting... fastboot commands still don't work though: "error: device not found"
the CID number is HTC__102, he version number of the stock nandroid and recovery was 4.16.401.10
regarding the OS number: on the hboot screen there's just written OS- <- is this the place where it's supposed to be?
thanks a lot for helping!

OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
C:\Users\aaron_000\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.25.2145000
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
my version & radio number are matching the ones in this RUU
so...
what now?^^ before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
oh, and would doing this even help in my current situation?
Thanks for helping

M4C00kie said:
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
Click to expand...
Click to collapse
Did you do anything different to get it working?
M4C00kie said:
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=f...4a4f68918d8199)
Click to expand...
Click to collapse
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
M4C00kie said:
before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
Click to expand...
Click to collapse
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
M4C00kie said:
oh, and would doing this even help in my current situation?
Click to expand...
Click to collapse
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!

redpoint73 said:
Did you do anything different to get it working?
Click to expand...
Click to collapse
I might have confused adb and fastboot... pretty sure it was working all along
redpoint73 said:
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
Click to expand...
Click to collapse
I initially posted this on another forum... realised too late that this one here was more appropriate and posted it here xD
redpoint73 said:
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
redpoint73 said:
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
Click to expand...
Click to collapse
done.
redpoint73 said:
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
Click to expand...
Click to collapse
deleted it. thanks for all your help so far!

M4C00kie said:
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
Click to expand...
Click to collapse
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.

redpoint73 said:
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
Click to expand...
Click to collapse
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ or should I rather download a zip version of it?

M4C00kie said:
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ ?
Click to expand...
Click to collapse
As long as "fastboot" is selected in bootloader it will work.

redpoint73 said:
As long as "fastboot" is selected in bootloader it will work.
Click to expand...
Click to collapse
it worked!!
never heard a sweeter sound before than the HTC boot sound^^
thank you so much for all your help!

Variant System Version OTA Update Error

After a long wait I finally got my ota update to Nougat.
But there is another problem, I cant finish the update because my phone showed that error.
I'm on stock M9 in bootloader it says software status official, locked, and s-on. No root, as I have checked it using root checker. Recovery is there.
I never modified my phone. And its fine back when I updated from lollipop to mm via ota, there is no problem.
And as far as I know, my phone is on correct mid and cid, SKU 708, mid 0PJA10000 exactly the same with mid engraved on my phone, and cid HTC__044
But when I update mm to nougat, this variant system version error shows up
I have tried to flash RUU of my current firmware, but still nothing.
Please help me, where did I do wrong? or how can I solve this problem?

Bumping this because I got the same thing too.
My device is not even rooted!

Did you guys flash a RUU for your current firmware and try to download the OTA, again?

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I did, but the problem stays there.

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I dont know how to flash the RUU.
But anyway, is there a way to check whether i can flash the OTA on my own?

vglaksana said:
I did, but the problem stays there.
Click to expand...
Click to collapse
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
-marco- said:
I dont know how to flash the RUU.
Click to expand...
Click to collapse
Well, there is a thread pinned above all the other threads in this section that is even called "ReadMe" and people still tend to completely ignore it...
-marco- said:
But anyway, is there a way to check whether i can flash the OTA on my own?
Click to expand...
Click to collapse
If you can't flash an OTA via the software update function then you can't flash it via fastboot, either. Your phone doesn't pass the security checks that google implemented with android 5 so the method you use for flashing the OTA doesn't matter.
Flash a RUU and re-try to install the OTA. If that still doesn't matter then please copy and paste your fastboot getvar all output here (without your IMEI!), as well.

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
Here it is
C:\Users\Vito G. Laksana\Desktop\New folder>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114,10801_97.64.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC 044
all: inished. total time: 0.016s
Above is getvar all from before I flashed my current RUU. I believe it wouldn't change anything, as I can't get fastboot getvar all working now.

vglaksana said:
(bootloader) cid: HTC 044
Click to expand...
Click to collapse
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah my bad. The correct CID is HTC__044, as I mentioned in the thread first post.
I just using image to text converter because I have screencap of the output and didn't see that straight away.

Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for helping me figuring out the problem.
If that is the problem, then why I have successfully update from lollipop to mm?
Yes i did buy it second hand, he said that the phone is from Singapore, and from the getvar output it is make sense that my phone came from Singapore.
Soo...I believe my only option is to S-OFF and convert to other version to get the update, is that correct?

I just re-read your opening post. Looks like I missed the part with the engraving. The US variant has a different engraving than the one you mentioned. So my assumption is probably wrong.
Since I have no clue what might cause your problem I actually don't see any other solution than getting S-OFF and converting the phone.
If there was a publicly available 4.x RUU for your SKU you could have asked Sneakyghost whether he creates a firmware package for you. By flashing that (S-OFF needed) you would have been able to use the 4.x RUU although you never installed the corresponding OTA. This way you could have kept your SKU. However, I haven't seen a public download link for such a RUU, yet. Therefore, you'll need to convert to a different SKU if you want the latest firmware.
Since you're still on firmware 3.x you need to flash one of Sneakyghost's 4.x packages before you can flash a 4.x RUU of the SKU that you want to convert to. Or you use a 3.x RUU for converting and try to install the OTA of the new SKU, afterwards. (The latter will probably take longer in total.)
Alternatively, you can wait some more days and see if some else has a better idea.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
I rebooted into bootloader to get the getvar but it doesnt work.
adb lists no devices.
Also, see the enclosed pic. that's as far as i managed to get.

Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
booted to system: adb sees device but says it's offline
booted to dl mode: adb can't see the device.
anyway, i took picture of what dl mode looks like. Attached.

Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
apparently i had a problem with drivers. i have fixed it now, that's why it gave empty devices.
Ok went back to bootloader mode. run fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54GYJ05021
all:
finished. total time: 0.132s
this is instead the same taken from dl mode:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
all:
finished. total time: 0.006s
what now?

Mhm, there's nothing strange in that output, either.
Can you flash a RUU and re-try installing the OTA? If that doesn't fix the problem then the only other option is converting the phone as I already suggested to vglaksana.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you flash a RUU and re-try installing the OTA?
Click to expand...
Click to collapse
can you point me to a guide on how to do this?
and also where can i find my relevant RUU?
thanks.

I already did so in my first reply to you.
Sent from my HTC One M9 using XDA Labs