Develop Bugs

[Q] Someone Help

I need help before i snap this thing over my knee. lol
Right i am very tech savvy but still a bitt noob when it comes to flashing etc. So basically, i rooted, several times my one x and finally landed
on the viper x rom and upon using the multi shot on my camera it caused a fatal error on my inbuilt SD and bricked my phone. I am now trying to
restore to official vodafone RUU so i can return this thing as this is the second time this has happened now.
However i am getting error 140 Bootloader error. Can someone please help.
C:\onexroot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0000
(bootloader) version-baseband: 1.1204.105.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.161.4
(bootloader) serialno: HT24DW118008
(bootloader) imei: 359188049780711
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) devpower: 70
(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
Thanks
Kris

I'm guessing you've relocked your bootloader and flashed stock recovery before trying to flash the RUU?
Plus a quick search shows Error 140 means the RUU you're trying to flash has an older bootloader than the one on the phone.
Are you sure the RUU you have matches your version on your phone? (2.17.161.4)

Brownie2k said:
I'm guessing you've relocked your bootloader and flashed stock recovery before trying to flash the RUU?
Plus a quick search shows Error 140 means the RUU you're trying to flash has an older bootloader than the one on the phone.
Are you sure the RUU you have matches your version on your phone? (2.17.161.4)
Click to expand...
Click to collapse
Nope the RUU is older something like 1.4.xxxx the problem is there doesnt seem to be any RUU above 2 let alone 2.17 does this mean im goosed? and yeah ive relocked boot loader flashed stock recovery although it will let let me flash boot.img i just get access denied when i try that.

You can't flash a boot.img with a locked bootloader as far as i know.
That will be why you're getting the Error 140, the bootloader on the RUU is older than the one on your phone. You can only flash the equivilent or higher bootloader.
I know there is a few OTA's out there for carriers, but not sure if it'll help you. I'm sure someone else with more knowledge of flashing RUU's will be able to help more.

Probably a silly question, but don't you have a CW backup from before flashing Viperx that you can restore via recovery? It's the way I went back to stock and possibly the best thing you can do if you have a rooted phone...

Kutusov said:
Probably a silly question, but don't you have a CW backup from before flashing Viperx that you can restore via recovery? It's the way I went back to stock and possibly the best thing you can do if you have a rooted phone...
Click to expand...
Click to collapse
Well.... Thats the funny bit. Its was saved to the sd card *facepalm* Which has now corrupted and had to be formatted so no more backup. The bit I am stuck on is how i get back to stock firmware. The only RUU with a higher hboot than current is HTC ONE X EUROPE but that one wont flash because the CID doesn't match and i don't know how to fix. Hate my life! lol

Unlock bootloader
Flash latest cwm you can mount sd card and Copy a rom over
Flash boot.img
Flash rom fixed
Heres a tool to help you with every step
http://forum.xda-developers.com/showthread.php?t=1734365
Heres stock rom
http://forum.xda-developers.com/showthread.php?t=1546970
Sent from my HTC One X using xda premium
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
And my fav
http://forum.xda-developers.com/showthread.php?t=1705334
Sent from my HTC One X using xda premium

joewong1991 said:
Unlock bootloader
Flash latest cwm you can mount sd card and Copy a rom over
Flash boot.img
Flash rom fixed
Heres a tool to help you with every step
http://forum.xda-developers.com/showthread.php?t=1734365
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hey cheers bro for advice but that isnt what im trying to do. The handset is needing to be returned to vodafone and im trying to get it back onto the official vodafone UK endeavouru rom and unroot but the the offieal RUU are only running around about 1.21.x.x.x.x but the viper x rom has but me on 2.17.161.4 which means the RUU is failing because of bootloader error, im still a bit confused on this but it seems i cant downgrade and my handset is NTEGRA 3 international version which mean no S-OFF, no super CID and no HBOOT access hence, pardon the language.. F**cked phone...

No worrys but why do you wont to send it back?
Sent from my HTC One X using xda premium

joewong1991 said:
No worrys but why do you wont to send it back?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Because the guys at Vodafone will just charge me 350 quid if i send it in with a customer rom and custom bootloader on it lol I need it back to stock.

klashnikoff said:
Because the guys at Vodafone will just charge me 350 quid if i send it in with a customer rom and custom bootloader on it lol I need it back to stock.
Click to expand...
Click to collapse
But i dont see why you wont to send it back all you have done is formatted your sd card and lost all you backups i would just install a new rom and start from fresh
Sent from my HTC One X using xda premium

joewong1991 said:
But i dont see why you wont to send it back all you have done is formatted your sd card and lost all you backups i would just install a new rom and start from fresh
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Are sorry i miss read, though it said why dont you, erm because i have one of the faulty ones. Issue with wifi disconnects if you move the phone, spoke to HTC who said some of the One X UK editions have been know to have wifi issues and to contact vodafone for replacement, i was going to just live with it but this is now the 4th maybe 5th time the SD card has currupted, twice was before i even rooted it so theres something wrong me thinks. Thats was why i rooted because i though maybe it was the bloatware damaging the files on the phone but nope looks like ive got a dodgy phone. lol.

klashnikoff said:
Are sorry i miss read, though it said why dont you, erm because i have one of the faulty ones. Issue with wifi disconnects if you move the phone, spoke to HTC who said some of the One X UK editions have been know to have wifi issues and to contact vodafone for replacement, i was going to just live with it but this is now the 4th maybe 5th time the SD card has currupted, twice was before i even rooted it so theres something wrong me thinks. Thats was why i rooted because i though maybe it was the bloatware damaging the files on the phone but nope looks like ive got a dodgy phone. lol.
Click to expand...
Click to collapse
Mate, no matter what you do, HTC will be able to see that you were messing with the phone. Your bootloader will be "RELOCKED", instead of "LOCKED" as in the original unit.
So, whatever the problem is within the phone, they have a reason to charge you for the repair, as the warranty will be void. I even believe it's said on htcdev website, during the unlocking process.

[email protected]|-|oR said:
Mate, no matter what you do, HTC will be able to see that you were messing with the phone. Your bootloader will be "RELOCKED", instead of "LOCKED" as in the original unit.
So, whatever the problem is within the phone, they have a reason to charge you for the repair, as the warranty will be void. I even believe it's said on htcdev website, during the unlocking process.
Click to expand...
Click to collapse
Oh Im well aware of that but this is a contract phone, HTC dont need to touch it, Voda do which coincidently their techs dont check to see whether it is locked/relocked just whether there is custom software on there. I must of had about 6 different handsets rooted then re locked and repaired by vodafone.

klashnikoff said:
HTC dont need to touch it, Voda do which coincidently their techs dont check to see whether it is locked/relocked just whether there is custom software on there.
Click to expand...
Click to collapse
Good for you, mate! Then, search for stock boot.img, stock recovery, and proper RUU, and you're good to go!

[email protected]|-|oR said:
Good for you, mate! Then, search for stock boot.img, stock recovery, and proper RUU, and you're good to go!
Click to expand...
Click to collapse
Well this is what i need help on, im still a bit stumped understanding bootloaders and allsorts, my hboot number is 1.12.0000
but my main version is 2.17.161.4 and when im trying to use the RUU all i get is error message 140 saying that im basically trying to restore to a previous bootloader and this is what im stuck on because the RUU is "Footballs" RUU and is the most recent vodafone UK one. What am i doing wrong. This is where nobody helps me. Thanks for talking to me btw you dont understand how much i apprectaiate this. Oh and ive tried flashing boot.img and system.img before locking and then using RUU but it when i flash system it just says failed :/

klashnikoff said:
Well this is what i need help on, im still a bit stumped understanding bootloaders and allsorts, my hboot number is 1.12.0000
but my main version is 2.17.161.4 and when im trying to use the RUU all i get is error message 140 saying that im basically trying to restore to a previous bootloader and this is what im stuck on because the RUU is "Footballs" RUU and is the most recent vodafone UK one. What am i doing wrong. This is where nobody helps me. Thanks for talking to me btw you dont understand how much i apprectaiate this. Oh and ive tried flashing boot.img and system.img before locking and then using RUU but it when i flash system it just says failed :/
Click to expand...
Click to collapse
Oh, now I see your main issue! Sorry, I disregarded the root cause of your trouble...
What you need is proper RUU only. But, that's easier said than done. Did you search filecatory.com or htcruu.com. There are plenty of RUU's there. But you MUST run 2.17 RUU. So, if Vodaphone didn't release 2.17 update, .. You know what I mean.
The other way you could go is finding custom rom with 1.29 base, flashing that one, then flashing stock boot.img, stock recovery, RELOCKING bootloader (don't forget this!), and then running RUU. Shortly, bringing your base to the one of RUU's.

Aww this is getting wierd now, so im looking down the avenue that we have discussed i remembered i can extract roms from the RUU itself which is how i repaired my phone last time but when i 7-zip into the ROM (bearing in mind this is the latest RUU aswell) the HBOOT .img file is 0.95.0000 ....So how the hell did i get onto 1.12.0000 ?? I havnt ran any RUU or anything and surely the ViperX Rom cant update my hboot image... can it? And the RUU which i am trying to use is the software i was on before i re-rooted.... oh god my head hurts....

I have no idea how you got 1.12 hboot, really. You are right, ViperX should not have anything to do with hboot...
If I were you I wouldn't mess too much with extracting the ROM from RUU. Again, what RUUs did you find? What is their base?

[email protected]|-|oR said:
I have no idea how you got 1.12 hboot, really. You are right, ViperX should not have anything to do with hboot...
If I were you I wouldn't mess too much with extracting the ROM from RUU. Again, what RUUs did you find? What is their base?
Click to expand...
Click to collapse
I have found a few with a 1.21 and 1.22 ans a few 1.29 base but it will not flash the system.img it just fails which apperntly seems to be a common occurance because the system files are to big.

[Q] Wondering...

I know i need to pay for sunshine to get S-Off,i'm considering doing it sometime soon,but just asking,would firewater work if i flashed rom to earlier version of android,like 4.4.0 or so? Also would it need to be official or could costume rom work too? Sorry for another annoying S-Off question. :angel:

No does not work.

SynoX4 said:
Sorry for another annoying S-Off question. :angel:
Click to expand...
Click to collapse
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.

redpoint73 said:
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.
Click to expand...
Click to collapse
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?

SynoX4 said:
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?
Click to expand...
Click to collapse
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.

xunholyx said:
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.
Click to expand...
Click to collapse
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.

SynoX4 said:
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.
Click to expand...
Click to collapse
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.

xunholyx said:
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.

SynoX4 said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.
Click to expand...
Click to collapse
Here's the RUU you need. It'll bump you to Lollipop.

xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Awesome,thanks. I'll update when it downloads,shouldn't be too long.

xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Error 132 signature something... I did lock bootloader before doing it.
Will do nandroid recovery to android 4.4.3,lock again and try.

SynoX4 said:
Awesome,thanks. I'll update when it downloads,shouldn't be too long.
Click to expand...
Click to collapse
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.

xunholyx said:
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.
Click to expand...
Click to collapse
Thing is,that requires s-off which i don't have...

SynoX4 said:
Thing is,that requires s-off which i don't have...
Click to expand...
Click to collapse
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.

xunholyx said:
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.
Click to expand...
Click to collapse
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?

SynoX4 said:
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?
Click to expand...
Click to collapse
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.

xunholyx said:
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.
Click to expand...
Click to collapse
Alright,thanks for all your help.

Trying to revert to stock, soft-bricked my phone

Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone, now the only thing I have is an s-on unlocked bootloader and twrp. All the roms I tried installing using TWRP keep saying that the updater binary failed or something. When I try to do RUU, it just doesn't work. Can anyone help me restore functionality to my phone?

Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
TheOnlyLite said:
Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone
Click to expand...
Click to collapse
Did you think that would return your phone to stock?

redpoint73 said:
Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
Did you think that would return your phone to stock?
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I just tried a bunch of random ones online tbh. I can't find any that match my phone's CID or MID even thought my CID is 1111111.
I have twrp 2.8.1.0 right now.
I am just trying to get the os working for now because everything I tried flashing didnt work.

You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

redpoint73 said:
You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.

TheOnlyLite said:
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Click to expand...
Click to collapse
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
TheOnlyLite said:
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
Click to expand...
Click to collapse
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
TheOnlyLite said:
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.
Click to expand...
Click to collapse
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.

redpoint73 said:
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.
Click to expand...
Click to collapse
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd? The exe keeps saying "The Firmware Update Utility cannot update your Android phone." and when I flash using adb or fastboot, it just fails.
edit: Actually I don't even know. I'm pretty dumb when it comes to this kinda stuff. What do you suppose I do step by step? I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.

TheOnlyLite said:
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd?
Click to expand...
Click to collapse
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
TheOnlyLite said:
when I flash using adb or fastboot, it just fails.
Click to expand...
Click to collapse
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
TheOnlyLite said:
I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.
Click to expand...
Click to collapse
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.

redpoint73 said:
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.
Click to expand...
Click to collapse
Sorry for being so vague about everything. So I guess all the RUUs that I tried flashing failed because of bootloader. I just relocked it and it worked. It was giving me error: 99 or unknown error when I tried any RUU including stock ones. And right now I just want my phone to work again haha. Now that I have that, I would like to return my phone to non-rooted, because some apps/games I have detect root somehow and I would like to use my phone to access them. After getting a working OS on my phone, how would I be able to return it to stock, and maybe install cyanogenmod?
Thanks for the help.
edit: Actually nevermind. My phone is unrooted now lol. Again thanks for the help

So you were able to successfully RUU? If so, which one?
TheOnlyLite said:
Again thanks for the help
Click to expand...
Click to collapse
There's a button for that.

redpoint73 said:
So you were able to successfully RUU? If so, which one?
There's a button for that.
Click to expand...
Click to collapse
So I flashed the 5.0.1 rom on that first link you provided with the official stock roms, but I'm sure the other ones would have worked. I was severely outdated with the one I flashed and had to update like 10 times to get back to the most recent ota lol.

Boot Loop directly into Fastboot Carrier Unlocked HTC One M8

Morning,
I've been into this phone for two days now, the phone would not Update OTA to Android 6 it was on stock 4.4.4 so I figured I'd install the RUU from HTC's site, I unlocked the bootloader and acquired S-OFF, I tried several RUU's (GEp, UNlocked/dev, android 5, 6, even tried to go back to stock 4.4, I know I'm doing many things wrong so I now ask for direction) since I knew nothing about CID and MID, the exe's did not work and the zips would flash via fastboot oem rebootRUU I even (regrettably) flashed several firmwares as it stands now with most hopes lost my phone has this values:
Bootloader is "relocked" since it was said to be required for RUU.
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_whl
(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: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, I can no longer unlock the bootloader using my Unlock_code.bin file, nor can I install a recovery image I get a "FAILED (remote:" error each time.
Thanks.

This is really bad. This looks to be a result of improper research by your part, and I hope the damage is not permanent (although it may possibly be).
Reason I say this, is that your product ID (m8_whl) indicates you have the Sprint version M8. This version is fairly unique (along with Verizon M8) in that its designed to work on the Sprint CDMA network (along with GSM networks). Due to this, the Sprint version has different partitioning and different radios from most other "GSM" M8 versions. And one should never attempt to convert a Sprint M8 to any other version; by flashing another version's RUU or firmware.
I also do not recommend ever changing the MID on the Sprint device (from its original MID), as there is no valid, safe reason to do so (for reasons mentioned above).
Mods with s-off can be extremely dangerous, as they can result in bricking your phone. You may already have a permanent radio brick (as we've seen happen after folks have flashed another version's RUU or firmware to a Sprint M8). The moment you started having trouble flashing an RUU, you should have backed off, and come here for help. Guessing, and trying multiple random things (like RUUs/firmwares) on these devices, especially with s-off, is a recipe for disaster.
When you say "boot loop" do you mean the phone is actually restarting itself over and over to fastboot? Or it simply can't boot to OS, and goes to fastboot (and if you manually reboot it, it goes again to fastboot)?
---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------
Herzchell said:
Bootloader is "relocked" since it was said to be required for RUU.
Click to expand...
Click to collapse
This is only a requirement when s-on. Relocking the bootloader to RUU not needed when s-off. With s-off, you can RUU with the bootloader unlocked.
---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------
Herzchell said:
nor can I install a recovery image I get a "FAILED (remote:" error each time.
Click to expand...
Click to collapse
You can try it a million times, and it won't make a difference. You can't install custom recovery with bootloader locked or relocked. That is the exact reason to have a locked bootloader, to prevent custom recovery from being installed.

Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?

Herzchell said:
Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.

Herzchell said:
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.
Click to expand...
Click to collapse
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"

Herzchell said:
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"
Click to expand...
Click to collapse
error 24 means one of the following
1- the .zip is corrupted
2- the .zip is an OTA package ( and it can't be flashed in fastboot mode )
3- android-info.txt have something wrong ( if this is the meant error you will need to change the cid and mid )
so you can tell which one of those is the meant error
about cid it's correct that it eliminate the needs of a specific cid ( and in some cases it passes the mid check )

ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
Click to expand...
Click to collapse
Since the OP is SuperCID, I believe he can pick either. Same model hardware, the only difference is software.
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Herzchell said:
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
Most US carriers, you can only OTA update if connected to that specific carrier (in this case, Sprint).
That being the case, your best bet is to RUU to latest Marshmallow image, as ahmed instructed.
And since RUU is a fully image (not just an update "patch") it doesn't matter the current configuration (as long as CID, MID checks pass or bypassed). Meaning you don't need to install any "older" RUUs before the current MM one.

Thanks,
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
You have both been very helpful.

Herzchell said:
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
Click to expand...
Click to collapse
Did this phone have an issue with the speaker before you started messing around with it?

HTC M9 Unlocking Bootloader

Hi im trying to unlock my bootloader on the M9 ...i have recieved the unlock token but once i have done the 'fastboot flash unlocktoken Unlock_code.bin' command it goes to the warning screen to select yes or no (up & down on volume > power to select) but i cannot use the volume buttons or power to do anything and the red warning writing that you see when you fastboot oem rebootRUU is at the bottom of this option screen still covering the other writing?
Here's a getvar:
D:\>htc_fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: Removed
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
Execution time is 15(ms)
Also, while i'm here...going by the firmware version number, am i able to get the OTA nougat update? there are no automatic updates from thee phone (your phone is up to date) but can i manually flash it to this phone?
I'm S-On at the moment with a locked bootloader and no custom recovery as of yet.
Thank you
EDIT: sorry for posting this in the wrong section! i have only just noticed, will not do it again :/

Supercid is not recognised anymore that is why you can't get updates. Looks like that phone has been previously rooted then relocked.
You'd have to root it, change the cid then return back to stock to get updates. From what I've read you're not missing much with nougat. I'm not going to bother updating.
Beamed in by telepathy.

Thanks for the advice.. i ended up using Sunshine S-Off to unlock the Bootloader & S-Off then i changed the CID back to the HTC__32 and flashed the stock ROM ...its just updating now with a security patch ...iv'e got a feeling its going to be exactly how it was but we'l see ...... i will back up device before the suggestion of the N update...if that happens :-/
Thanks again
Devices:
HTC M9
HTC M8

Craig_CFC said:
Thanks for the advice.. i ended up using Sunshine S-Off to unlock the Bootloader & S-Off then i changed the CID back to the HTC__32 and flashed the stock ROM ...its just updating now with a security patch ...iv'e got a feeling its going to be exactly how it was but we'l see ...... i will back up device before the suggestion of the N update...if that happens :-/
Thanks again
Devices:
HTC M9
HTC M8[/QUO
Sunshine apps requires $25 but i dont wanna pay .is there any other method to make it free..+??
Click to expand...
Click to collapse

nagen2001 said:
Craig_CFC said:
Thanks for the advice.. i ended up using Sunshine S-Off to unlock the Bootloader & S-Off then i changed the CID back to the HTC__32 and flashed the stock ROM ...its just updating now with a security patch ...iv'e got a feeling its going to be exactly how it was but we'l see ...... i will back up device before the suggestion of the N update...if that happens :-/
Thanks again
Devices:
HTC M9
HTC M8[/QUO
Sunshine apps requires $25 but i dont wanna pay .is there any other method to make it free..+??
Click to expand...
Click to collapse
There is no free method. Your options are Sunshine or a Java clip. I suppose you might be able to find an XDA user who had purchased a Java clip who lives near you and is willing to help you.
Click to expand...
Click to collapse