Develop Bugs

Bell Canada HTC One M8 Restore Project

Greetings- I have an M8 running CM12 (nightly)
main 4.20.666.1
hboot 3.19.0.0.0000
S-On
CM12 nightly
twrp2.6
SuperSU
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to. My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Tried Firewater and got the PIE error.
You guys are doing a great job here- I've learned alot lurking and hope to continue...
cheerss

Superflous said:
I'm hoping to restore to upgrade but the *$$*%*$ S-On issue won't allow me to.
Click to expand...
Click to collapse
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Superflous said:
My original recovery is corrupt/gone and I just wonder if anyone has any (good) ideas?
Click to expand...
Click to collapse
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Superflous said:
Tried Firewater and got the PIE error.
Click to expand...
Click to collapse
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).

redpoint73 said:
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Click to expand...
Click to collapse
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.

ckpv5 said:
Already moved my stock recovery collection to here : http://forum.xda-developers.com/showpost.php?p=60211779&postcount=4
All in one place and easier to find I guess.
Click to expand...
Click to collapse
Certainly great to have it in one place, and thanks for doing so!

redpoint73 said:
What exactly are you trying to do, that you think s-on is preventing? Unless I'm missing something, I don't think there is anything you are trying to do, that would be impeded by s-on.
Stock recovery for your main version is posted by ckpv5 here: http://forum.xda-developers.com/showpost.php?p=58947150&postcount=4708
Firewater was discontinued by the developer 6 months ago (online service, so no longer works).
Sunshine is the only current s-off method, if you really need s-off (not clear that you do).
Click to expand...
Click to collapse
tx for recovery link, sorry if it wasn't explained right but i want to restore my phone back to Bell firmware and lollipop . I spoke with the Root ninja via email ans Sunshine won't work on my phone(their words). I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware. If this isn't right I would sure appreciate the path to the correct way to put my phone back to original. Tx for you help

Superflous said:
I have tried to install the "firmware_M8SD_4.20.666.1_Modified_Bell_Canada.zip" but it fails and locks me up in the blue CM head until I reset, then reverts back to CM12. I'm just getting into this but if I understand correct you need S-off to flash firmware.
Click to expand...
Click to collapse
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.

redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
'
so then I'm looking for a stock ROM from the carrier for firmware 4.20.666.1

tx again Redpoint
redpoint73 said:
Somewhat correct. If the firmware is official (signed and encrypted) and for your CID, it will flash with s-on.
However, once the firmware has been modified in any way (as the one you tried clearly is) or otherwise not signed, you can't flash it unless you have s-off.
But I don't think flashing firmware is what you really want. You might be mixing up firmware with software (ROM). Firmware are the partitions that don't get changed when you flash a ROM. Firmware includes hboot, radio, and some other modules (WiFi, media, etc.). Since you need s-off to flash an "unofficial" firmware, and you are still s-on, you should still be on the stock firmware. And therefore, no need to "return to stock" since you still are stock.
What I think you mean, is that you want to return to stock ROM (since you are on CM12) and stock recovery. None of which require s-off. After that you can relock the bootloader. But it will always say RELOCKED instead of LOCKED, as the latter requires s-off. If you are selling or giving the phone away, RELOCKED should be sufficient for most folks. Although I highly recommend disclosing that the bootloader was previously unlocked, root, etc. to the new owner.
Click to expand...
Click to collapse
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers

Superflous said:
As a followup- tx for taking the time to explain- I have set the phone back to stock and happy to have learned some.
You are one of the good ones'
Cheers
Click to expand...
Click to collapse
You're very welcome. Glad to see it worked out well for you.
Please click the "Thanks" button for any posts you found helpful.

HTC One M8s OTA not working

Hi,
I recently managed to root my HTC One M8s with TWRP recovery and everything works perfectly, except that I can't install the new OTA (1.16.401.1).
After searching I have flashed my recovery back to the stock for my version (which is 1.11.401.1) and tried applying the OTA again, but it still fails.
I downloaded the recovery from this website: ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/HTC%20Recovery/ (I can't post URLs yet).
Below is the error I receive when trying to update on stock recovery, TWRP recovery also gave the same error when I tried updating there.
(Code -1)
E:Find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.105.019
Verifying current sytem...
Package expects build fingerprint of htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/531284.2:user/release-keys or htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys;
This device has htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/53128
E:Error in @/cache/recovery/block.map
(Status 7)
From what I can see my build fingerprint is incorrect, but I have no idea how to fix it...

Seems to me it's likely that you've altered some system files while rooted and the Ota doesn't like it.
Now, I don't own an M8s...i have an M8, but I'd say the easiest route would be to flash your stock ruu again. After that the OTA should work.
It's that or figure out what system changes have been made and correct it. Xposed can mess you up, Uninstalled system apps can stop the Ota... MODS that changed system files... Etc. The Ota us looking for a stock system, then it updates it.
Good luck!

Thanks for the answer, I will see if I can try this solution tomorrow. I just have 2 questions:
What does the RUU do exactly? Should I see it as a complete stock reset of my phone?
And can I simply flash it using fastboot or is there a special method for a RUU?
My previous phone had an automated root and I always updated with OTA afterwards so I never flashed before now.

Im on the same boat. Tried to sim unlock by rooting and playing with CID but didnt work, now ive a rooted m8s and no ota. Tried to ruu but kept getting an error something like not enough space although i had 10gb free, cleared cache rebooted. Cant even factory reset. If anyone know how to unroot it and bring it back to stock that would be fantastic. Kind of want to delete the "flag" too make it "LOCKED" and "OFFICIAL" incase for warranty. Any ideas?

You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?

voidzero said:
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
Click to expand...
Click to collapse
When I got my phone I updated with OTA to version 1.11, after that I flashed TWRP recovery and rooted my phone. Now that OTA 1.16 is out I tried to update but couldn't, so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
Manual OTA flash worked on my previous phone with root which was an ASUS Padfone Infinity A80 as ASUS would release them on their own website for you.
Apparently HTC does not do this, or I am not looking in the right place.
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash original recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.

Codyksp said:
(...) so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
(..)
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash custom recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
(...)
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Click to expand...
Click to collapse
If you restore a RUU, and afterwards don't flash your recovery and boot partitions, You will see "Software status: official" in fastboot.
Now here's the trick: if you just boot a custom recovery with "fastboot boot my_recovery.img" (TWRP for example) then it will boot TWRP, but you can make the modifications to your system partition without losing "Software status: official" in fastboot.
So: If you just boot your recovery with 'fastboot boot' and don't flash anything, you can make all the modifications you want and still be able to install OTAs later, I think. I've rooted my phone, even installed XPosed, done all kinds of funky things to it but Fastboot still shows me that I'm on official software.
How does that sound?

So since there is no decent guide at all about flashing RUU for a HTC One M8s (the s makes a difference!). I have assumed that I need to have the bootloader locked first, as I unlocked it. According to all the M8 guides I have to gain S-OFF before I can lock the bootloader again. So I followed a guide to wipe with TWRP and flash a ROM called InsertCoin so that I can S-OFF my phone.
Now after going through the ROM's setup my phone is stuck in a bootloop, constantly trying to boot up. There is NO way at all for me to get it to stop, it just keeps booting the entire time. Not a single combination of buttons is working. Good thing the battery is non removable. How am I supposed to fix this? I've tried every volume up/down/power combination possible. The phone just boots to the HTC - Power by Android screen, shuts off after about 5 seconds and then repeats the same thing over and over. I can't turn it off and I can't get to the bootloader either.
What I need is a guide that tells me all the steps required to get an HTC One M8s (NOT M8!) back to 100% stock. This means, stock ROM, stock recovery, locked bootloader and S-ON. I am getting extremely frustrated by the lack of information and the amount of redicilous things I need to do just so I can root my phone and have OTA as well.
All I want is root on my phone for 1 app that I use with my car radio and I want to be able to update to the newest OTA afterwards, is that really so much to ask?
I am fine with installing a custom ROM with root and easy updates too, as long as the damn phone will boot after installing it and it's actually made for the M8s.

Deleted......

Well I finally managed to get the damn thing to the bootloader, and I've used "fastboot oem lock" to relock my bootloader. It now shows ***Software status: Modified ***, *** RELOCKED *** and ***Security Warning ***.
I will now have to go to my parents where my laptop is to be able to copy the RUU to my SD card, from what I understand it has to be named 0PKVIMG.zip and then it should automatically install.

Now the phone says it can't find the image or the image is incorrect.... It searches for, 0PKVDIAG.zip, 0PKVDIAG.nbh, 0PKVIMG.zip or 0PKVIMG.img. and it seems to find 0PKVIMG.zip and loads it but it cannot find the .img file and does absolutely nothing. Am I supposed to have both?

So it turns out that the RUU zip from http://ruu.lalleman.net/HTC_M8S%28QL_UL%29/RUU/ is actually not correct and I had to use rom.zip which was inside the folder. The phone is now running the "update" as it calls it. Fingers crossed...

Yes, possible you need to use rom.zip inside the zip, depending on the version, but I think this applies to 1.16 which I advice against using for reasons previously specified.
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
By the way, I did write an RUU restoration thread specifically for this subject. Did you not find it?

Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.

Codyksp said:
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Click to expand...
Click to collapse
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.

Mr Hofs said:
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Click to expand...
Click to collapse
So in that case I just unroot it before updating then?

Codyksp said:
So in that case I just unroot it before updating then?
Click to expand...
Click to collapse
Read my post again...... "a never rooted rom" so that means you need a stock rom before its ever been rooted. NOT an unrooted one because it leaves traces which will cause the ota to fail !
People should learn to create a nandroid backup before flashing ANY mods/superuser.zip/roms etc......etc

Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
I would say that M8 roms wouldn't be compatible, and could even mess up your device badly. Sorry!

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
Your point of view is a bit off if you ask me. Developers (in this case HTC) do not have to support custom modding of your phone. They support the device in the state you buy it !
If you want to mod it that's YOUR call not theirs. Do some homework before modding it. Getting a phone back to stock for future updates is relatively easy but many people don't read first how to as they think it's not important.
HTC has no obligation at all towards you regarding custom software !
And indeed M8 roms do NOT work on your M8s !

Need help with Stagefright OS patch

Hello XDA :x
I know the thread title is very vague but i had no clue what to put there, sorry about that :x
I'm terrible at talking, but I hope you guys understand what I'm saying /:
A week ago, I downloaded the latest snapshot of CM12.1, with intentions of using it instead of stock htc rom.
(The CM download is not very relevant to my problem but I thought I should give a background to how I arrived to my current situation)
So I flashed latest TWRP, ***<foolishly forgot to make a nandroid backup>*** and tried flashing CM12.1 snapshot and it didnt work. I tried other CM variants, and MaximusHD but nothing worked. So I just sat there with no OS.
Luckily (not really), I had a nandroid backup from a month or two ago because I used to frequently flash ROMs. The nandroid backup was 4.16.401.10, and my current OS (before trying to install - and according to my bootloader) is 4.16.401.13
I had no choice but to restore the previous version, which is Lollipop 5.0.1 without stagefright update.
Things became confusing... my OS version according to Software Information is 4.16.401.10, and the OS on bootloader still was .13
I've attempted all of the following:
1) OTA through phone itself: It downloads the update, then says the files are corrupt (no matter how many times I try)
2) This one is too obvious, but i tried it anyway -> the official RUU of .10 didnt work
3) Flashing firmware.zip from the .13 update using RUU feature in fastboot
Nothing has worked. I'm still .13 on bootloader, and .10 while the phone is on. And the software status is modified.
Please help me get my actual OS back to .13, things are getting really frustrating
HTC ONE M8
Unlocked
S-ON (currently cant afford S-OFF)
HTC__J15

Stop worrying so much about that stagefright patch. They did put out a patch but didn't solve it exactly with that patch.
Just stay on .10 and wait a bit longer for newer updates. You are not missing much to nothing at all !

Mr Hofs said:
Stop worrying so much about that stagefright patch. They did put out a patch but didn't solve it exactly with that patch.
Just stay on .10 and wait a bit longer for newer updates. You are not missing much to nothing at all !
Click to expand...
Click to collapse
Im not worried about the patch, its just that I might be selling my phone soon and if I do, the guy isnt exactly familiar with ROMs and the bootloader; and I dont wanna be a jerk haha.
Also, aren't updates incremental? Like, step-by-step as in you go from .10 to .13, you cant jump over an update?
Also,thanks for replying

Well you can get a stock .13 backup here
http://forum.xda-developers.com/showthread.php?t=3086860
Restore that one and flash back the stock recovery also. Then it's stock as the backup has never been rooted before.

Mr Hofs said:
Well you can get a stock .13 backup here
http://forum.xda-developers.com/showthread.php?t=3086860
Restore that one and flash back the stock recovery also. Then it's stock as the backup has never been rooted before.
Click to expand...
Click to collapse
wwwwwoah.
i just realized that I've been trying to do the OTA for .13 while on .10 recovery :x
god i hate being a noob.

Phone stock in bootloop after flashing custom rom

So I installed ViperOne M9, the latest version, everything went fine, the download didn't fail, but after rebooting the phone just boots to the bootloader. I can access recovery mode, and download mode but I can't do anything else. I'm not sure what went wrong, though I suspect it might have been that my phone wasn't updated to the latest firmware, I thought it was but I think it wasn't. I made a TWRP backup and placed it on my SD Card but it doesn't seem to be reading it since nothing shows up in there.
In summary I switched to ViperOne M9 from stock, my bootloader is unlocked and my phone is rooted. Its S-On, and it seems to be rebooting every so often. Can anyone help me, this is my first time flashing a custom ROM and everything seemed to be going well until this step.

ArgusPMC said:
[...]
ViperOne M9, the latest version
[...]
S-On
[...]
Click to expand...
Click to collapse
You need the Android M firmware for the latest Viper version. Not every SKU got that update already. What's your current firmware version (stated in Download Mode in the line with "OS" at the beginning)?
Edit: Pressing and holding the power button and both volume buttons at the same time (for a certain amount of seconds I always forget - was it something around 30?) should end the bootloop and make your phone return to Bootloader Mode.

My current firmware is 2.10.709.180. I looked into the Backup and RUU collection too, though I wasn't sure about what to do with that. I did see a TWRP backup for version 2.10.709.1, but I'm not sure if that's the same as the firmware version I have, give those two digits at the end with my phone. Otherwise I guess I could use an RUU if I understood correctly, but I got that I should look for a specific one for my phone.
My CID is also HTC__621 if that helps anything. I'm also not sure about S-ON, should I go S-OFF, I know there's an app that does it for $25, and if it is better for custom ROMs then I have no issue paying that.

If I'm not mistaking your firmware version belongs to the first of the two updates that install Android M on the Taiwanese version (SKU 709) of the M9. So you probably only installed the preparing one and not the Android M one itself. Unfortunately no one contributed a backup for that version and I don't have enough time at the moment to create one. Since you're S-ON you can't use any of the RUUs either because S-ON prevents you from downgrading or changing to a different SKU. And there is no RUU for your firmware version which is accessible for free.
I would recommend installing one of the Android L custom roms (e.g. Viper One M9 3.5). After that you have four options:
Wait and hope that someone creates and uploads a backup you could use. (Can be combined with option 2)
Wait for an Android M RUU for your SKU. (There's no guarantee that there ever will be one.)
Get S-OFF via Sunshine so that you could use one of the older RUUs for the SKU 709. (They can be found in my google sheet.)
Use this RUU service.
If I were you I would choose option three since S-OFF makes getting back to stock so much easier and you're independent from others uploading a backup that corresponds to your current firmware since you can use any RUU you want with S-OFF. But don't feel pushed by me to choose option 3 (since that's not my intention). It's completely your choice.

I'll just go S-OFF, seems like the easiest solution. I was going to do it anyway, so I might as well do it now.
EDIT: Thanks, your solution worked out for me, now I've just got to use the RUU I downloaded and with that I can go ahead and get the Android M firmware I need.

AT&T HTC M8 in desperate need of help, device wrecked/FUBAR

So roughly two years ago I decided to root my phone. I flashed TWRP, got S-OFF, and root. Well somebody hacked my phone and I freaked out. They were remotely downloading and inventorying all my devices' files, serial numbers, hardware info, accessing my camera, I mean everything, it was truly frightening the level of which whomever was doing this was able to to do it. I freaked out, went into TWRP, and started deleting everything that looked suspicious. I deleted my OS and probably a bunch of other things I shouldn't have on accident through TWRP. My device still has TWRP recovery functioning. I tried using ADB on my Windows 10 PC but I have no idea what I'm doing. I kept getting errors to the effect of "wrong version" etc. Being unable to use ADB I resorted to copying Viper OS to a flash card and I used TWRP to install it from flash. Once installed it "ran" but my Wifi radio did not work at all. When I tried to enable it in settings it stayed grey. Figuring I screwed up royally again, I decided to copy and paste a folder I created in 2014 with a TWRP recovery. It had the OS, cache, etc backed up. After using TWRP recovery it said I had no OS again. I'm freaking out, my phone is trashed, and I don't want to do anything else without a babysitter. I just want my original phone back, no custom roms, nothing. I don't want to turn S-ON because I know there is a possibility of bricking and quite frankly, I'm an idiot. Somebody just please walk me through what I need to do to get a fully functioning OS back on my phone. SD card methods preferred, as I can't get ADB to work or I'm too stupid to use it. I saw something mentioned that the firmware may need updating and that may have been the cause for the WiFi issue, since all I did was install Viper through a .zip through TWRP.

I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2

lgally80 said:
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
Click to expand...
Click to collapse
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!

xunholyx said:
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
Click to expand...
Click to collapse
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Update 1:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Update 2:
Opened the original OS Viper I flashed, it was a .zip with boot also, so going to leave this new one alone and go ahead and flash as a whole...
Update 3:
Flashed as whole, last screen on install said successful, rebooted. On HTC screen, waiting to see what happens... 3 minutes into waiting...
Update 4:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed. You deserve just as many blowjobs as you do internets. Don't know what was wrong with that last Viper ROM but this did it. Many thanks. Not even going to bother with the new TWRP and everything else, my phone works as is and that's that. +1 for you mate.

lgally80 said:
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Click to expand...
Click to collapse
I did say to flash the ROM first to get back your OS, so.....
Anyway, that recovery version won't work until you update your firmware. Try 2.8.7.0 first, update your firmware, then you can use the 3.x.x.x recovery
I should have been clearer in my instructions

lgally80 said:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Click to expand...
Click to collapse
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
lgally80 said:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed.
Don't know what was wrong with that last Viper ROM but this did it.
Click to expand...
Click to collapse
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.

redpoint73 said:
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
Click to expand...
Click to collapse
Yes I probably "should" update TWRP and my firmware, buuuut....
If it ain't broke, don't fix it.
Also in reply to your comments:
1. Flashing ViperOneM8_6.1.0.zip caused WiFi loss. Maybe Bluetooth also, don't remember. Flashing ViperOneM8_2.5.0.zip and now my phone is 100% functioning.
2. That "Old" firmware works fine now that it matches the ROM requirements, all radios functioning stable for several days now. I don't mind staying on older releases.
3. Nah I'm good, I use this M8 as a tool or entertainment device at home, and nothing else. It has no service, no AT&T signal here. Hasn't had service since 3 years after public release.
Anyway, thank you everyone who contributed. Anyone who's just showing up:
The Lesson of the Day - If your Hardware Radios do not function, the solution is your ROM probably requires a different Firmware revision than the one installed.
Cheers.