Develop Bugs

[q] m8 european developer edition, stock, unlocked and tampered with s-on

Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.

w69 said:
Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.
Click to expand...
Click to collapse
If it is a true developer edition, you might try backing up, running one of the Developer Edition RUU's to get back to 100% stock, and then see if you can get the OTA update. If this was a conversion, make sure the CID/MID are correct (which requires S-off).

w69 said:
Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.
Click to expand...
Click to collapse
If its truly the Dev Edition, on the stock ROM and stock recovery, you should get OTA.

insert coin
redpoint73 said:
If its truly the Dev Edition, on the stock ROM and stock recovery, you should get OTA.
Click to expand...
Click to collapse
bro i doubt its stock because it is also showin insert coin. are insert coin roms stock or custom??

w69 said:
Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.
Click to expand...
Click to collapse
lock the bootloader and flash then newest RUU
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Then simply unlock the bootloader
flash TWRP recovery and SuperSU and a kernel if you need system r/w

w69 said:
bro i doubt its stock because it is also showin insert coin. are insert coin roms stock or custom??
Click to expand...
Click to collapse
Then why did you state in the thread title and OP "stock"?
InsertCoin is a custom ROM and not stock. So you need to return to a stock ROM to install OTA.
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
clsA said:
lock the bootloader and flash then newest RUU
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Click to expand...
Click to collapse
1540 is US Dev Edition, and the OP has Euro DE. The RUU likely will not run with incorrect CID, MID. And not sure this is the stock baseline he would want to be on.

Htc one m8 CID: 002, european, stock demo rom (receiving ota)
redpoint73 said:
Then why did you state in the thread title and OP "stock"?
InsertCoin is a custom ROM and not stock. So you need to return to a stock ROM to install OTA.
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
1540 is US Dev Edition, and the OP has Euro DE. The RUU likely will not run with incorrect CID, MID. And not sure this is the stock baseline he would want to be on.
Click to expand...
Click to collapse
ok i changed the custom insert coin rom to this demo rom unfortunately. yet my device is S-on, unlocked boot loader, its cid is 002, european model. the problem is i cant flash any other rom on this demo version rom. i only need a 100% stock rom (sense) to receive ota updates in future. plz reply asap cant use my phone the demo app comes again and again.

w69 said:
ok i changed the custom insert coin rom to this demo rom unfortunately. yet my device is S-on, unlocked boot loader, its cid is 002, european model. the problem is i cant flash any other rom on this demo version rom. i only need a 100% stock rom (sense) to receive ota updates in future. plz reply asap cant use my phone the demo app comes again and again.
Click to expand...
Click to collapse
Whats a Demo Rom ?
do you have TWRP installed ?
Install this >> http://www.androidrevolution.org/downloader/download.php?file=One_M8_2.22.401.4_odexed.zip
That will get the phone working and Sunshine should get you s-off

clsA said:
Whats a Demo Rom ?
do you have TWRP installed ?
Install this >> http://www.androidrevolution.org/downloader/download.php?file=One_M8_2.22.401.4_odexed.zip
That will get the phone working and Sunshine should get you s-off
Click to expand...
Click to collapse
yes i have twrp-2.8.1.0 installed. demo roms are those roms like in shops they have demo phones with playing demo videos again again in it. this rom is only supporting 2G. i used this link http://forum.xda-developers.com/showthread.php?t=2735235 and copied the odexted zip to twrp. it runs successfully but after that phone is in same old condition. is it true that the odexted rom is not installing because im S_ON??
and tell me if i S_OFF will i get ota updates with the odexted rom? sunshine needs 25$. well havnt tried firewater on this demo rom. and bro the link u sent is not working.

w69 said:
is it true that the odexted rom is not installing because im S_ON??
Click to expand...
Click to collapse
Don't know where you obtained that info, but its false. S-off is not needed to install any ROMs.
If the phone is a demo unit, you should have stated that right away in your top post. On a previous HTC device (One X) I believe the demo unit was very difficult, if not impossible to make fully functioning. But no idea if the same is true for the M8 demo unit you have.

redpoint73 said:
Don't know where you obtained that info, but its false. S-off is not needed to install any ROMs.
If the phone is a demo unit, you should have stated that right away in your top post. On a previous HTC device (One X) I believe the demo unit was very difficult, if not impossible to make fully functioning. But no idea if the same is true for the M8 demo unit you have.
Click to expand...
Click to collapse
i have no ideo what was it. i got it from ebay. it had a custom rom 4.4.2 insert coin.i was not receiving fota thats y i thought to shift to full stock. on a facebook page of htc one M8 someone sent me a link to flash it and said its full stock rom. i flashed it with twrp but i came out demo. now im stuck. someone told if me i flash a custom rom again it will be fixed even if its S-ON. kindly tell me a good updated custom rom which doesnot require S-OFF.

w69 said:
on a facebook page of htc one M8 someone sent me a link to flash it and said its full stock rom.
Click to expand...
Click to collapse
Sounds like you just got some random advice, with an unknown link and flashed it. Why on earth would you do such a thing? Stick to XDA, at least here you can go by reputation (number of thanks, Recongnized Contibutor, or Recognized Dev titles).
w69 said:
someone told if me i flash a custom rom again it will be fixed even if its S-ON. kindly tell me a good updated custom rom which doesnot require S-OFF.
Click to expand...
Click to collapse
As I just said in my last response, you do not need S-off to flash any ROMs. If you want help, you need to start actually paying attention to the help that is being given to you. You are also making it very hard to help you, by not giving enough info, and just leaking it out little by little.
You say you can't flash any other ROMs, but that isn't enough information. What happens when you try to flash? Does it fail with an error message? Or flash successful, but doesn't boot? What other ROMs have you tried?
If you want to return to stock to receive OTAs, you will need to find and flash the appropriate nandroid and stock recovery for our CID. Stock backup collection can be found sticky at the top of the General section. There are also various guides on how to return to stock, if you need them just search.

redpoint73 said:
Sounds like you just got some random advice, with an unknown link and flashed it. Why on earth would you do such a thing? Stick to XDA, at least here you can go by reputation (number of thanks, Recongnized Contibutor, or Recognized Dev titles).
As I just said in my last response, you do not need S-off to flash any ROMs. If you want help, you need to start actually paying attention to the help that is being given to you. You are also making it very hard to help you, by not giving enough info, and just leaking it out little by little.
You say you can't flash any other ROMs, but that isn't enough information. What happens when you try to flash? Does it fail with an error message? Or flash successful, but doesn't boot? What other ROMs have you tried?
If you want to return to stock to receive OTAs, you will need to find and flash the appropriate nandroid and stock recovery for our CID. Stock backup collection can be found sticky at the top of the General section. There are also various guides on how to return to stock, if you need them just search.
Click to expand...
Click to collapse
Thanx a lot for your help and concern. now i have installed android revolution rom. i think its good. will see for L rom in future. but the problem was that i found exact rom and rocovery for my device which is 401 wwe european having cid 002 latest HBoot . flashed it and flashing was successful but when i reboot the device its still the same. means the flash didnt work. yes u are right i was leaking out info a little. it was because i knew my device a little and i didnt know what is the current status of my device. now after reasearch of few days my mind is clear. thanx for your help and interest again. this page is a blessing for beginners like me.

w69 said:
Thanx a lot for your help and concern. now i have installed android revolution rom. i think its good. will see for L rom in future. but the problem was that i found exact rom and rocovery for my device which is 401 wwe european having cid 002 latest HBoot . flashed it and flashing was successful but when i reboot the device its still the same. means the flash didnt work. yes u are right i was leaking out info a little. it was because i knew my device a little and i didnt know what is the current status of my device. now after reasearch of few days my mind is clear. thanx for your help and interest again. this page is a blessing for beginners like me.
Click to expand...
Click to collapse
I glad you got it working .. sorry about the dead link, i wish Mike would leave the old version on his site longer

[Q] Stuck with a pretty much unusable phone abroad

hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks

Run the ruu for your cid and revert to stock

rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
Click to expand...
Click to collapse
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.

rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
You flashed firmware for your specific device in the firmware/RUU thread before clean flashing to the update on viper? Like iElvis said you are describing what some users have posted in a few threads where users checked the 1.40 kernel and 1.40 in base(I think, I haven't flashed viper), but didn't properly flash the firmware for their device via fastboot or RUU back to stock to get official OTA(if OTA was released from HTC for users specific device.). Hope you get it sorted out
Do you have a back up of your system before viper update? (1.90 or below) or back up ROM ?
---------- Post added at 11:05 PM ---------- Previous post was at 10:46 PM ----------
iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
Correct me if I'm wrong, but I thought viper allowed user (sprint for example) to run their "1.40 base" on old firmware, they just had to select 1.32 kernel in aroma and would lose out on newer features

that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..

iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
im pretty sure, yes. Because It shows so in Download mode and in the about section of settings of my phone. I came across pre update error 1.90 and it fixed itself when the phone rebooted in downlaod mode.

Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it

rpimentel1 said:
that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..
Click to expand...
Click to collapse
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243

rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
EDIT:Are you on tmobile?Because than you need to flash back 1.32 firmware, as our installer will install older tmobile kernel in order for wifi calling to work, or you need to manual flash international boot.img if you want to keep 1.40 firmware.

BUBBA DUB'S said:
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
ivicask said:
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
Click to expand...
Click to collapse
kash20 said:
Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it
Click to expand...
Click to collapse
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?

rpimentel1 said:
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?
Click to expand...
Click to collapse
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545

BUBBA DUB'S said:
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Click to expand...
Click to collapse
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.

rpimentel1 said:
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.
Click to expand...
Click to collapse
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:

BUBBA DUB'S said:
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:
Click to expand...
Click to collapse
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???

rpimentel1 said:
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???
Click to expand...
Click to collapse
Check out this link it might help , also in the first link I posted I think I saw someone reference what you are asking but I'm not 100% sure.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698

[SOLVED] T-Mobile M8 Stuck In Recovery With ReLocked Bootloader and No ROM!

The title basically says it all but I'll describe what I did so hopefully you guys can help.
Today I got tired of the ROM I was running and I figured I'd update my firmware before I flashed a new one just cause I hadn't done it in months. So I went and followed this guide: http://forum.xda-developers.com/showthread.php?t=2696282
I used this firmware: https://www.androidfilehost.com/?w=files&flid=32788
My CID is T-MOB010 just like the firmware's and I thought it would be a pretty simple thing, so I got to work.
First I rebooted to fastboot USB and did fastboot getvar all to make sure everything lined up, then I relocked the bootloader and did fastboot oem rebootRUU, all successfully.
Then I flashed the firmware and it all went great but I forgot to flash it a second time. I'm not sure if it's required, but anyway...
After it flashed successfully I did a fastboot reboot and my phone tried to reboot but it stalled on the white HTC splash screen, then went black, then the splash screen returned, then black, then it went into the stock recovery.
The stock recovery functions just fine and I attempted to just clear the cache and reboot but it did the exact same thing.
I don't currently have a stock Nandroid or RUU on my phone and I'm not even sure I have a way to get one on there besides using someone else's phone to put one on my SD.
Can anyone help me out? Is it even possible to get out of this? My bootloader is relocked and my phone can't get S-OFF (tried awhile ago multiple times). As of now I am all out of ideas/experience so I'm hoping you guys can help me. Thank you!!
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Update: Once I got into hboot all was well, I just flashed TWRP again and got it going. Thanks everyone for the help!

Did you get it going again?

_jakeryan said:
I don't currently have a stock Nandroid or RUU on my phone
Click to expand...
Click to collapse
Just use the official RUU.exe which runs from a PC (with phone connected), not from the phone.
http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will also update your firmware.
Also, the firmware you linked is not the latest. Its the Android 4.4.4 firmware. The 5.0 (Lollipop) firmware would be 4.20.531.4

hack14u said:
Did you get it going again?
Click to expand...
Click to collapse
I did! Thank you redpoint for the help anyway!

_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Maybe add 'solved' to the topic? If that's still a thing.

_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Its not what your top post says, so its not clear whether you were trying to put the RUU.exe on the phone (which is incorrect), unsuccessful in putting on the phone or running an RUU.zip, or did the latter in addition to trying to run the RUU.exe from the PC (which was not originally mentioned). If the last one didn't work, it would help to have more details on failure mode, error messages, etc.
---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------
_jakeryan said:
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Click to expand...
Click to collapse
So is your issue resolve or not? Able to get a ROM or nandroid on the phone and flash/restore it?
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
voidzero said:
Maybe add 'solved' to the topic? If that's still a thing.
Click to expand...
Click to collapse
Not everyone does it, but its certainly good to do, and still done from time to time. Its helpful so folks don't click on a link, intending to help someone that doesn't need the help anymore.

Same kinda problem.
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??

morgansgrandad said:
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
Click to expand...
Click to collapse
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.

redpoint73 said:
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
Click to expand...
Click to collapse
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!

morgansgrandad said:
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
Click to expand...
Click to collapse
You shouldn't be assuming what RUU to run. What is your CID and hboot number? What RUU did you try to run?

HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe

morgansgrandad said:
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
Click to expand...
Click to collapse
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.

redpoint73 said:
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
Click to expand...
Click to collapse
Thanks redpoint73. Looks like that's the only way to go!!

By looking at the radio, you need the Euro Version RUU. Looks like we gotta be detectives sometimes, lol.

Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??

morgansgrandad said:
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
Click to expand...
Click to collapse
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/

hack14u said:
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
I'm downloading that now. BUT...........
Because of all my faffing on!! there's NO OS on the phone.
I'm really struggling now:crying:

This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.

And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne

morgansgrandad said:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
Click to expand...
Click to collapse
What hack14u neglected to mention, is that to run another version's RUU, you need s-off ($25 by sunshine), and then you need to change your MID and CID.
Relocking the bootloader (to run RUU) renders the phone with no OS, this is by design.
---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------
morgansgrandad said:
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
Click to expand...
Click to collapse
Hang in there, modding phones can often be an exercise in frustration. But the phone is quite recoverable, as long as you perform the correct steps.
A nandroid is not a flashable zip (such as a ROM). It needs to be restored in a very different way, its described in Post 3 of the stock nandroid thread (assuming that is where you go it from) under Question & Answers.
To summarize, you need to:
1) Unpack the zipk, which is a number of folders
2) Move the folders to the proper location on the phone's internal storage (removable SD is also possible, if you setup TWRP to back and restore to that location)
The exact location if very important (its described in Post 3 of the stock nandroid thread), since when restoring a nandroid, TWRP will not see the file to restore if you have it wrong. This is in direct contrast to installing a ROM zip, in which TWRP allows you to browse anywhere on the storage to find the file to flash.
3) Choose the menu option to RESTORE, not INSTALL

HTC M8 from Three UK stuck

Hello everyone.
I have an M8 with a corrupted software.
Always stuck on HTC logo.
Sometimes when it boots, it shows "3" , which means it's from Three UK.
I looked everywhere but couldn't find the corresponding RUU, except on http://www.htcdev.com/devcenter/downloads , but it's only around 500 MB !
It's in zip format.
I can go to the bootloader, but it doesn't accept to FACTORY-RESET (gets stuck on HTC screen)
Software status: Official
RELOCKED
Any ideas?
Thanks in advance.

I unlocked the bootloader in order to try to install another RUU.
Now it shows "UNLOCKED" .

I installed twrp and superuser (I guess).
According to the thread here http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I have to install the sunshine.apk which I can not because my phone doesn't boot except to the bootloader !
What to do here?

majdykhrais said:
I looked everywhere but couldn't find the corresponding RUU, except on http://www.htcdev.com/devcenter/downloads , but it's only around 500 MB !
It's in zip format.
Click to expand...
Click to collapse
That isn't an RUU, its kernel source, and not going to be of any help to you.
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
majdykhrais said:
I unlocked the bootloader in order to try to install another RUU.
Now it shows "UNLOCKED" .
Click to expand...
Click to collapse
Unlocking the bootloader will not allow you to run another version's RUU. I don't know why you think that, but its not correct information.
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
majdykhrais said:
I installed twrp and superuser (I guess).
According to the thread here http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I have to install the sunshine.apk which I can not because my phone doesn't boot except to the bootloader !
What to do here?
Click to expand...
Click to collapse
S-off is not the correct path, to do what you want (nor should it be necessary - save yourself $25). As you've figured out, you need a working OS to s-off; but working OS is the reason you want to s-off. So you have a Catch-22 dead end.
If there is no RUU, unlocked bootloader and TWRP are good things to have done. Now restore the 6.13.771.4 stock nandroid backup, using the file and instruction here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

Thanks
redpoint73 said:
That isn't an RUU, its kernel source, and not going to be of any help to you.
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
Unlocking the bootloader will not allow you to run another version's RUU. I don't know why you think that, but its not correct information.
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
S-off is not the correct path, to do what you want (nor should it be necessary - save yourself $25). As you've figured out, you need a working OS to s-off; but working OS is the reason you want to s-off. So you have a Catch-22 dead end.
If there is no RUU, unlocked bootloader and TWRP are good things to have done. Now restore the 6.13.771.4 stock nandroid backup, using the file and instruction here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Thanks for the info.
I know TWRP and S-OFF won't help me here, but I just wanted to show what I've done.
One question, why to restore 6.13.771.4?
How will I know it's the correct one for my phone, and not a part of the pre-installed corruption?

majdykhrais said:
One question, why to restore 6.13.771.4?
How will I know it's the correct one for my phone, and not a part of the pre-installed corruption?
Click to expand...
Click to collapse
This is the main version given in your screenshot in your top post. And you'll see from the stock nandroid collection, that its the correct version number for your CID (carrier version).
Simply put, this is the stock Marshmallow ROM for your M8 version.
Somebody likely made the backup with a working OS. Yours has become damaged or corrupt (most likely) just on your phone. Not every phone with this software number is going to be broken!

didn't work!
redpoint73 said:
This is the main version given in your screenshot in your top post. And you'll see from the stock nandroid collection, that its the correct version number for your CID (carrier version).
Simply put, this is the stock Marshmallow ROM for your M8 version.
Somebody likely made the backup with a working OS. Yours has become damaged or corrupt (most likely) just on your phone. Not every phone with this software number is going to be broken!
Click to expand...
Click to collapse
excellent turorial.
I followed the steps one by one,
didn't get any errors,
but it didn't work.
I got the HTC screen, then "3" screen, then stuck on HTC One screen!
Any ideas?

majdykhrais said:
excellent turorial.
I followed the steps one by one,
didn't get any errors,
but it didn't work.
I got the HTC screen, then "3" screen, then stuck on HTC One screen!
Any ideas?
Click to expand...
Click to collapse
a strange thing I noticed,,
on command prompt on my pc, I can't see the new folder containing the unzipped file, while I can see it through the windows-explorer!

majdykhrais said:
a strange thing I noticed,,
on command prompt on my pc, I can't see the new folder containing the unzipped file, while I can see it through the windows-explorer!
Click to expand...
Click to collapse
Any particular reason why you are looking in command prompt? Since the steps don't use command prompt (unless you adb push the files).
What version TWRP?
Can you post a screenshot of what the TWRP backup folder structure (on the phone) looks like in Windows Explorer? Not sure what we can be missing here. But its worth a look.
Also, you might try the a Lollipop backup. It should work fine with the MM firmware. Although it may cause an issue with OTA updates (mixing LP ROM with MM firmware), at least it (should) get the phone up and running.

twrp backup
redpoint73 said:
Any particular reason why you are looking in command prompt? Since the steps don't use command prompt (unless you adb push the files).
What version TWRP?
Can you post a screenshot of what the TWRP backup folder structure (on the phone) looks like in Windows Explorer? Not sure what we can be missing here. But its worth a look.
Also, you might try the a Lollipop backup. It should work fine with the MM firmware. Although it may cause an issue with OTA updates (mixing LP ROM with MM firmware), at least it (should) get the phone up and running.
Click to expand...
Click to collapse
no reason for command prompt, but I just was there and noticed this.
TWRP 2.8.7.0-m8 according to the turorial.
I want to try Lollipop since it was the o.s. when my phone was working properly before I upgrade to 6 and get the wifi problem.
any specific Lollipop version?
I just want a stable version.
thanks

twrp
majdykhrais said:
no reason for command prompt, but I just was there and noticed this.
TWRP 2.8.5.0-m8 according to the turorial.
I want to try Lollipop since it was the o.s. when my phone was working properly before I upgrade to 6 and get the wifi problem.
any specific Lollipop version?
I just want a stable version.
thanks
Click to expand...
Click to collapse
here's a screen shot
the path on my laptop was the same.

sorry,
I used twrp-2.8.7.0-m8

I'm confused about what you are talking about anymore. Did you sell the phone or not?
http://forum.xda-developers.com/showpost.php?p=66116673&postcount=1498
If this is a different phone, you need to give details.
Fastboot getvar all

HTC ONE M8 security warning in FASTBOOT mode

Hi every one I have htc one m8 now 2-3 years, I rooted and unlocked bootloader, on stock firmware which is : 4.18.708.12 and now I have system updates that I cant update cuz im rooted , so I relocked bootloader and tried to update , still when i try it goes to fastboot with this : system software modified, security warning and it doesnt update nor perform a factory reset, can some one help me out here? id be glad I need this help asap

You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.

redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back

madshark2009 said:
I want my phone to be back to stock like it came from the company, with the original ruu and firmware signatures, if i install stock rom and stock recovery that way im still rooted in which case I dont want it, I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you no longer have warranty, anyway. HTC warranty is only valid for 1 year.

redpoint73 said:
If that is what you wanted, then no mention was made of that in your OP (which you should have done). You should be specific about what you want, and not make it harder for folks trying to help you.
You are incorrect (that after installing the stock ROM, you will still be rooted). Installing the stock ROM will remove root. That's the whole point of the thread I linked.
If there is an RUU for your version number, just use it to return to almost full stock. When I say "almost", its because the bootloader will only say RELOCKED instead of LOCKED. The only way to make it say LOCKED (after its been unlocked) is with s-off. And if you don't already have s-off, it will cost you $25 by sunshine. Probably not worth the cost, as you most likely don't have a warranty, anyway. HTC warranty is only valid for 1 year.
Click to expand...
Click to collapse
and how do i decide which RUU is suitable for my device?
android 5.0.1
software number : 4.18.708.12
I must point out that I never installed a custom rom nor recovery I just unlocked bootloader and rooted and thats it so how do I find my ruu and what to do if i dont?

Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
madshark2009 said:
and how do i decide which RUU is suitable for my device?
software number : 4.18.708.12
how do I find my ruu and what to do if i dont?
Click to expand...
Click to collapse
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.

redpoint73 said:
Its not actually clear what you are trying to do. Return to stock to update? Or something else? Your later post says return to stock for warranty, but no way you have warranty at this point. Is something wrong with the phone? Or just trying to return the phone to stock to sell or trade it?
Can't really provide proper guidance unless we know your intent.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
You look for an RUU for that version number you just posted.
If no RUU, the process I linked for you in the first place will return you to full stock, with the exception of bootloader will be UNLOCKED. Or you can make it RELOCKED. Not really much different from what an RUU would give you.
Click to expand...
Click to collapse
I didnt mean to get my warrenty back, I meant to get back to stock just like when getting back to original phone status like it came from the company, so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand I might need your further help perferably vie Direct message, but just to save all the efforts, Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
(sorry i am new thats why i ask a lot )

madshark2009 said:
I didnt mean to get my warrenty back
Click to expand...
Click to collapse
But its exactly what you posted:
madshark2009 said:
I wanna get back to original LB and Unrooted with warrenty back
Click to expand...
Click to collapse
I strongly suggest you take a bit more time thinking about what you post, and making sure its properly typed, (lack of proper capitalization, spelling and punctuation makes your posts a pain to read, to say the least) and conveys what you want it to. Otherwise, you're just making it harder for folks to understand and help you.
Any time you think you are saving by typing quickly, is being lost x10 by me having to ask you to clarify what you mean.
madshark2009 said:
so I understood that flashing stock rom and recovery will help me with geting back and stat updating normally, but the precess seems too complicated to understand
Click to expand...
Click to collapse
The process isn't complicated. If you managed to unlock the bootloader and root the phone, you can certainly accomplish restoring the stock ROM and stock recovery. On that same note, it can be fairly said that anyone that is unable restore the phone by that method; probably shouldn't have unlocked the bootloader and rooted to begin with. Or look at it a slightly different way: you should never root a device without knowing how to return it to stock.
The guide looks long, mostly because its written in a very highly detailed, step-by-step manner (some folks seem to like that). But it just boils down to downloading the proper file, unzipping the folders, putting them in the right location on the phone, and restoring in TWRP.
If you have issues on a particular step, feel free to post again here, or the TWRP stock backup thread we are discussing.
madshark2009 said:
Id perfer the RUU flashing, and since you said none original RUU that has the same number of my version , that means I can install any one I want? whats the difference between RUUs and how do I choose the perfect one
Click to expand...
Click to collapse
I never said there was no RUU for your version number; or did you determine that yourself (your wording isn't clear)? I don't definitely know if there is or not; I was leaving it up to you to search. But doing a quick search myseld, it looks like NO.
If you looked, and there is no RUU for your version, you certainly cannot run any RUU you like. In fact, you can't run any RUU at all, unless its intended for your version, CID, MID.

redpoint73 said:
You need stock ROM, and stock recovery to update by OTA.
Return to stock ROM and stock recovery using this thread (which will then allow you to update): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Relocking the bootloader isn't necessary to OTA (only to RUU or flash signed firmware.zip) and didn't help you matters. You'll need to unlock it again in order to perform the process linked above.
Factory reset also won't help your condition, so there isn't a point in doing so. Factory reset is a bit of a misnomer, all it does is wipe user data. It won't restore a previous OS, nor remove root, etc.
Click to expand...
Click to collapse
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen

madshark2009 said:
I downloaded signed firmware that has the same CID and MID but marshmellow not lolipop (I had lolipop and flashed marshmallow firmware) and now phone is stuck at black screen
Click to expand...
Click to collapse
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.

redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
yes thats what it means! what can i do now?

redpoint73 said:
Why did you flash signed firmware? Its not a ROM, not an RUU. Nobody told you to do this.
Black screen, as in the screen doesn't come on? Not a good sign.
Click to expand...
Click to collapse
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?

madshark2009 said:
yes thats what it means! what can i do now?
Click to expand...
Click to collapse
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.

redpoint73 said:
How did you flash the firmware? By fastboot, or SD card method?
What's the exact file name for what you flashed?
Any error messages?
Did it tell you to flash again (very common, but actually says "flush image immediately"), and if so, did you flash it again?
Try holding power button and vol up for a minute or more, and see if there is any change.
Click to expand...
Click to collapse
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares and now when I rebooted as instructed it gets stuck at black screen after HTC logo on white screen and so I thought I could fix this by flashing twrp but now it says bootloader signatures veryfication error, so I cant proceed to the installation ..

madshark2009 said:
i found my version number in TWRP backup 4.18.708.12_ckpv5 can i use this to flash through ADB? because I cant flash TWRP recovery after what i did it says error bootloader signatures veryfication.. what are my options man?
Click to expand...
Click to collapse
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?

redpoint73 said:
You have to get the phone back on, in one mode or another, before you can do anything.
No, you can't flash the stock TWRP backup with adb. Its a TWRP backup, and you have to restore it with TWRP.
You can't flash custom recovery with the bootloader locked. That is why you have signature verification error. You need to unlock the bootloader again, which I already told you. And you need to be in bootloader-fastboot mode to flash it, anyway. I thought you said the screen wasn't coming on?
Click to expand...
Click to collapse
yes it got a black screen.
to Unlock bootloader I need what exactly?

madshark2009 said:
flashed by fastboot the way its mentioned in the thread you sent me.. on how to flash marshmallow signed firmwares
Click to expand...
Click to collapse
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
madshark2009 said:
yes it got a black screen.
to Unlock bootloader I need what exactly?
Click to expand...
Click to collapse
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).

redpoint73 said:
I told you to restore a stock ROM and stock recovery from the thread (Post #1). I said nothing about flashing a signed firmware (Post #5) which is not part of returning to stock.
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
You can't do anything with the phone off.
I asked you to try something in Post #13 above. Please read everything I post, and stop jumping around and trying random things. Read carefully, and proceed with caution and attention. Rushing around isn't going to help anything, and may do permanent damage to the phone (if you haven't already).
Click to expand...
Click to collapse
so what are my options now?

madshark2009 said:
so what are my options now?
Click to expand...
Click to collapse
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.

redpoint73 said:
Your options are to read more carefully.
I seriously do not like repeating myself; especially having to repeat myself when I say "read more carefully" and try what I already told you several posts ago.
Click to expand...
Click to collapse
ok it worked now im back to stock..
but now there are no software updates available
PS: I did exactly what the post said! now i am back to stock rom with stock recovery and when i go to check updates it says my device is up to date (on lolipop 5.0.1) but before I had 6.0.1 marshmallow available now its not.