Hi guys,
Verizon HTC One M8 rooted, S-off,with CWM, running the old digital high GPE 4.4.4.
HBOOT 3.16.0
RADIO 0.89.20.0321
10G storage
I did the firewater procedure when I first got the phone with no problems. Now I am trying to install the new LolliGPE on here and getting nothing but headaches. I have tried to install TWRP(different versions) via Flashify AND fastboot, but when it reboots, it stays on the white HTC One screen-"loading recovery". I have done this multiple times, and then adb reboot, install CWM via flashboot, and no problems. I don't know what else to do, and don't wanna mess my phone up especially as the next step is updating RUU, etc. I'm thinking I may have to update hboot, I just don't want to do anything un-neccesary to brick my phone. Any ideas? Thanks!!
Your older hboot requires an older version of TWRP. Plus, on older TWRP versions, depending on which TWRP version exactly, the CDMA M8 variants had a different TWRP recovery image (as recovery is stored on a different partition location for that version versus the "GSM" or non-CDMA M8). So you need to be really careful (I think a brick is even possible).
I'd suggest updating to the current Verizon Lollipop firmware before proceeding. Your hboot is ancient, and will cause all sorts of issues. After that, the current version TWRP 2.8.7 should install fine.
Thanks for the reply..
So update Hboot first, then install TWRP, then RUU, then ROM?
dl12458 said:
So update Hboot first, then install TWRP, then RUU, then ROM?
Click to expand...
Click to collapse
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Great, the update worked!!
I have one final question regarding the LolliGPE ROM (if you have any experience with it). Since I am now on 5.0.1, I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Forum
http://forum.xda-developers.com/showthread.php?t=2716306
redpoint73 said:
Shouldn't be a need to flash new hboot, RUU will do that.
Further, you don't want to install TWRP before the RUU; as RUU will wipe it out with stock recovery, anyway.
So in general, you want to:
1) Backup your personal data, RUU will wipe the phone including internal storage.
2) RUU
3) Install TWRP
4) Flash the custom ROM of your choice
Although it should be noted that some folks have had trouble installing TWRP after installing the OTA (the one with Stagefright fix in particular), at least on "GSM" versions of the M8. So you might research and see if VZN folks are having the same issue on the RUU with Stagefright fix that you linked in your PM to me. But at least in browsing the last few pages of the thread, I don't see any mention of TWRP issues (and some confirmations of TWRP working okay):
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
dl12458 said:
I tried installing the LolliGPE ROM, and once it is through with its inital bootup, Google prompts me to download a 600mb update. I allow to it to, but then it just gets stuck. It doesn't download anything, and I cannot procede any further. Do I need to flash the Verizon firmware listed, even though the RUU updated?
Click to expand...
Click to collapse
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
dl12458 said:
Great, the update worked!!
Do I need to flash the Verizon firmware listed, even though the RUU updated? I used the following to try and flash the VZN firmware 1. "fastboot oem rebootRUU" (Phone goes into RUU mode) 2."fastboot flash zip firmware.zip", but I get a response "cannot load firmware.zip" Any ideas?? Thanks again!!
Click to expand...
Click to collapse
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Update- I was trying to install the 5.0.1 update, and when I tried the 5.1 it worked!! Thanks for your help.
redpoint73 said:
I don't use that ROM, or any GPE ROMs, for that matter. So I'll be of limited help on this one.
What I can say, I've seen another post or 2 reporting a similar issue: GPE or AOSP custom ROM installed, will prompt to download an update upon setup (with no option to do otherwise), then phone is stuck.
So you might check the ROM thread, to see if others reported this. Or other help threads, as I've mentioned, I know others have posted this same issue; and that thread(s) may have some insight on a fix.
This issue is pretty weird. You won't normally see a custom ROM accept any type of OTA update, and certainly not a "forced" one like this at startup. In general, custom ROMs won't play well with any type of official OTA update (and updates are often disabled for this reason). And it seems you had no choice to bypass it, which is also odd.
Again, I'm not sure what is going on with the forced "update". But I doubt flashing firmware will fix anything.
The error "cannot load" when trying to fastboot flash a file, almost always means the file is not present (meaning not located where it should be, or named wrong). You need to have the desired firmware zip in the same folder where fastboot.exe is located (assuming you are using a PC). And for the command you listed, the firmware actually/literally has to be named "firmware.zip" (with no quotes). If the firmware file is named something else, you either need to rename the file to "firmware.zip" or use the actual exact file name in the fastboot command. Another common problem, is on Windows, folks often have the option enabled to hide file extensions (this is typically enabled by default, and I highly recommended you turn this off). So if you already renamed the file, it may actually be named "firmware.zip.zip" even though Windows will display it as "firmware.zip". If you see a lot of file types with not extensions at all, its very likely you have the option enabled to hide file extensions.
But again, I'm not sure that flashing the firmware is going to help.
If you can't find an easier fix for the "forced" update and stuck on boot screen; my thought would be to try flashing another ROM. Or at worst, RUU to stock again, and try another ROM.
Click to expand...
Click to collapse
Related
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 !
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Hi,
Did you try to reflash your recovery and try to install another rom like ViperOne M8? Or if you want i can send you the stock ROM Android 6.0
Laurens54321 said:
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Click to expand...
Click to collapse
You seem to be going about things rather haphazardly:
1) Not sure exactly what "some OTAs" refers to. But there is typically only one OTA that will properly work. That being the one that is for your CID (carrier version) and for the next software version (can't skip any).
2) Along the same lines, you can't just flash any RUU. It has to be for your CID and MID (Error 130 usually means wrong MID), and equal or greater version number than main version on the phone (no "downgrading" unless you have s-off).
3) "messing around with stuff that didnt work" doesn't tell us anything about how you got to the current condition. You need to be specific and detailed, if you want us to be able to tell what you did, and how to recovery.
4) You can't unroot and OTA, it has to be a stock (never rooted) ROM and stock recovery.
5) boot.img in itself probably won't help your situation. And signature verify fail usually means you tried to flash without the bootloader unlocked (which won't work).
Are you S-OFF? If so, this works;
1) Download 0P6BIMG.zip. You'll have to Google
"dottat @ XDA M8 RUU" to get the file as I haven't
made at least ten posts here and can't post links yet.
2) Place 0P6BIMG.zip on an SD card formatted fat32 ONLY.
3) Boot your phone, allow HBOOT to recognize 0P6BIMG.zip
and follow the prompts.
RESULT: This will land you on STOCK kitkat 1.55.605.2
pre-rooted with stock recovery.
----------------------------------------------------------------
CREDIT: dottat @ XDA
Alright, I will start at the beginning. I plugged my phone into my PC. HTC Sync manager popped up and told me there was an update for my device. So I was excited knowing it was the Marshmallow update. Everything was going smooth until my cable disconnected while it was installing. It failed and my phone was doing nothing. So like an idiot, I rebooted it.. Now my phone will not go past the HTC logo on boot. I tried wiping the cache partition from Android Recovery but no luck. I'm not really sure what to do at this point. My phone was not rooted, and it is *Locked*. I just want my phone back.. Any help would be so much appreciated, because I'm pretty unsure of what to do.
By the way I am not worried about saving what is on the phone. It's the HTC One M8 (Verizon).
Hi,
I'm a beginner here myself but based on what I read lately it might be possible to go into fastboot mode and flash a Lollipop RUU file.
You'll need a couple of tools on your PC (adb and fastboot) and a step by step guide, both easy to find with a quick search. The harder part is to locate the appropriate file to flash, at least I have trouble with that piece...
Good luck !
Gnondpom said:
it might be possible to go into fastboot mode and flash a Lollipop RUU file.
Click to expand...
Click to collapse
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
redpoint73 said:
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
Click to expand...
Click to collapse
OS # is (6.21.605.3) The update was just about finished before it disconnected. So I believe you are correct. I don't mind data loss, would rather just get the device functional again.
It is S-ON, it was never modified in any way. I will check out the links and see what I can do. Thank you for all the info!:good:
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.
HTC 10
S-Off CID
BS_US001
Android 7.0 July 1, 2017 security patch
Kernel [email protected] #1 SMP PREMEPT
Baseband [email protected]_76.02_F
Build 2.51.617.1 8.0_g CL942117 release-keys
Bootloader unlocked and rooted with SU
TWRP 3.1.1
Recently installed Viper10 5.11.0 ROM. Trying to return to stock but cannot. I have tried running several HTC RUU exe files (including RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.41.617.3 RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21
PMEWL_2.51.617.32_NoWipe_TWRP3110).
Nothing works. The RUU files start InstallShield Wizard but when it gets end of the progress bar, the wizard stops and nothing else happens. I've Run As Admin and disabled AV/Firewall. Nothing.
I've tried to install zip versions of same RUU files, both using Fastboot and moving to internal/card storage of the phone. No ZIP file will return unit to stock.
Using the RUU should be the best option but the RUU file always fails when the Wizard's progress bar gets to the end. Why does the RUU fail every time?
Refer to this thread to change your CID to verizon.
https://forum.xda-developers.com/verizon-htc-10/how-to/guide-convert-unlocked-to-verizon-t3380615
adamocca said:
HTC 10
S-Off CID
BS_US001
Android 7.0 July 1, 2017 security patch
Kernel [email protected] #1 SMP PREMEPT
Baseband [email protected]_76.02_F
Build 2.51.617.1 8.0_g CL942117 release-keys
Bootloader unlocked and rooted with SU
TWRP 3.1.1
Recently installed Viper10 5.11.0 ROM. Trying to return to stock but cannot. I have tried running several HTC RUU exe files (including RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.41.617.3 RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21
PMEWL_2.51.617.32_NoWipe_TWRP3110).
Nothing works. The RUU files start InstallShield Wizard but when it gets end of the progress bar, the wizard stops and nothing else happens. I've Run As Admin and disabled AV/Firewall. Nothing.
I've tried to install zip versions of same RUU files, both using Fastboot and moving to internal/card storage of the phone. No ZIP file will return unit to stock.
Using the RUU should be the best option but the RUU file always fails when the Wizard's progress bar gets to the end. Why does the RUU fail every time?
Click to expand...
Click to collapse
What does it say next to CID, MID, and OS in bootloader mode?
You are S-Off, so instead of running an RUU, you can flash a no-wipe firmware package (an RUU will wipe your phone). With that information I can link you to a no-wipe firmware, with instructions to flash it.
Thanks, but I don't want to change CID to Verizon. It's a GSM phone, not CDMA. It's unlocked (617). But I do understand the confusion. The HTC Dev site downloads an RUU that is seemingly for Verizon even though it's listed under the Unlocked Phone section.
Thanks. Bootload mode shows CID as BS_US001, MID as 2PS650000 and OS as 2.51.617.32. I have tried to flash (using both TWRP and Fastboot) a no-wipe firmware (namely PMEWL_2.51.617.32_NoWipe_TWRP3110) but it hasn't returned me to stock. Nothing takes and the only thing I can do to revive the phone is reflash (using TWRP) the Viper10 rom. I can live with the Viper10 rom but I'd like to return to stock so I can get HTC OTA, etc. I figure the most likely way to accomplish this is to use the HTC Dev RUU but, as mentioned, it never gets past the InstallShield Wizard.
Interesting that the Bootloader shows a different OS version than checking through the phone's software. In any event, I am definitely running Viper10 and it uses an older Build as its base.
adamocca said:
Thanks. Bootload mode shows CID as BS_US001, MID as 2PS650000 and OS as 2.51.617.32. I have tried to flash (using both TWRP and Fastboot) a no-wipe firmware (namely PMEWL_2.51.617.32_NoWipe_TWRP3110) but it hasn't returned me to stock. Nothing takes and the only thing I can do to revive the phone is reflash (using TWRP) the Viper10 rom. I can live with the Viper10 rom but I'd like to return to stock so I can get HTC OTA, etc. I figure the most likely way to accomplish this is to use the HTC Dev RUU but, as mentioned, it never gets past the InstallShield Wizard.
Interesting that the Bootloader shows a different OS version than checking through the phone's software. In any event, I am definitely running Viper10 and it uses an older Build as its base.
Click to expand...
Click to collapse
Software in setting> about is your ROM base, OS in download mode is your firmware version.
Do you have HTC Sync installed on your PC? Try uninstalling it and running the RUU again. You could also try running it while your phone is booted to download mode.
Yup, I've installed fresh drivers via HTC Sync and the PC recognizes the phone no problem.
ADB and fastboot also see the phone. I've tried the RUU in download mode,
bootloader and even OEM rebootRUU. Nada. In all cases the RUU InstallShield Wizard starts and then stops when it reaches the end of the progress bar. It never even gets to the actual RUU install routine (which I've used in the past with my HTC M9, so I know how it works when it flashes correctly). I'm running out of ideas. I'm happy with Viper10, if I can't get back to stock.
Try this https://www.reddit.com/r/htc/comments/2vxite/ruu_exe_file_doesnt_load_closes/colxuoy/
I've had the same problem while running on win 10 ltsb 2016 and this seemed to fix the problem.
adamocca said:
Thanks. Bootload mode shows CID as BS_US001, MID as 2PS650000 and OS as 2.51.617.32. I have tried to flash (using both TWRP and Fastboot) a no-wipe firmware (namely PMEWL_2.51.617.32_NoWipe_TWRP3110) but it hasn't returned me to stock. Nothing takes and the only thing I can do to revive the phone is reflash (using TWRP) the Viper10 rom. I can live with the Viper10 rom but I'd like to return to stock so I can get HTC OTA, etc. I figure the most likely way to accomplish this is to use the HTC Dev RUU but, as mentioned, it never gets past the InstallShield Wizard.
Interesting that the Bootloader shows a different OS version than checking through the phone's software. In any event, I am definitely running Viper10 and it uses an older Build as its base.
Click to expand...
Click to collapse
If your OS says 2.51.617.32, then you are on the latest firmware now. Seems like the no-wipe firmware worked after all. The firmware won't return you to stock.
If you want to go back to stock and not just update your firmware, you could try flashing a 2.51.617.32 RUU.zip via your extSD instead of running the RUU.exe.
I can upload the RUU.zip if you need it.
Thanks again for the help. I have the following RUU downloaded from the HTC Dev site: RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I also found what I believe is the ZIP version of that RUU: 2PS6IMG_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I've tried both running the RUU.exe and flashing the ZIP from my externalSD. No luck with either. Viper10 stays stubbornly stuck as my ROM. If you have a better ZIP, I'd be happy to try that too.
Thanks. I saw this suggestion as well in my hunt for a solution.
I've reloaded every.... possible... redistributable... with no success.
At least my C++ Visual Studio redistributables are up to date.
I can't even get the the license acceptance screen on the RUU install wizard.
I crash out before then.
Thanks. I found the same suggestion in my hunt for a solution.
I've updated every single redistributable... with no success. At least my PC is up-to-date with C++ Visual Studio. :-/
adamocca said:
Thanks again for the help. I have the following RUU downloaded from the HTC Dev site: RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I also found what I believe is the ZIP version of that RUU: 2PS6IMG_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32
I've tried both running the RUU.exe and flashing the ZIP from my externalSD. No luck with either. Viper10 stays stubbornly stuck as my ROM. If you have a better ZIP, I'd be happy to try that too.
Click to expand...
Click to collapse
First of all, you should use the reply/quote button when responding to a comment. It makes it easier to tell who you are replying to, and who you are replying to will get a notification about it.
Okay, delete any RUU.zips you already have on your ext SD
Download this
Rename it by deleting everything in the name of the .zip except for 2PS6IMG (and .zip of course) and place it onto your ext SD card
Boot to download mode and your phone will recognize the .zip and prompt you to press volume up to confirm the flash. Do that
When the flash is complete your phone will ask you to press power to reboot. Do that
After the RUU has flashed, either delete the .zip or rename it again to something else (add _2.51.617.32 to the name so you know what it is). If you don't do that, every time you boot to download mode your phone will try to update again.
Good luck!
xunholyx said:
First of all, you should use the reply/quote button when responding to a comment. It makes it easier to tell who you are replying to, and who you are replying to will get a notification about it.
Okay, delete any RUU.zips you already have on your ext SD
Download this
Rename it by deleting everything in the name of the .zip except for 2PS6IMG (and .zip of course) and place it onto your ext SD card
Boot to download mode and your phone will recognize the .zip and prompt you to press volume up to confirm the flash. Do that
When the flash is complete your phone will ask you to press power to reboot. Do that
After the RUU has flashed, either delete the .zip or rename it again to something else (add _2.51.617.32 to the name so you know what it is). If you don't do that, every time you boot to download mode your phone will try to update again.
Good luck!
Click to expand...
Click to collapse
Tada! That worked. I was able to flash the ZIP you sent and restored to stock 2.51.617.32. I still have no idea why the RUU exe file won't work but as usual there is more than one way to skin a cat -- or in this case, flash an HTC 10. Also not sure why prior attempts to flash a ZIP from the external SD didn't work.
Thanks for all your help (and patience).
adamocca said:
Tada! That worked. I was able to flash the ZIP you sent and restored to stock 2.51.617.32. I still have no idea why the RUU exe file won't work but as usual there is more than one way to skin a cat -- or in this case, flash an HTC 10. Also not sure why prior attempts to flash a ZIP from the external SD didn't work.
Thanks for all your help (and patience).
Click to expand...
Click to collapse
You are welcome
I'm not sure what was going on with the .exe not working, but I knew this would.
I'm glad that I could help.
xunholyx said:
First of all, you should use the reply/quote button when responding to a comment. It makes it easier to tell who you are replying to, and who you are replying to will get a notification about it.
Okay, delete any RUU.zips you already have on your ext SD
Download this
Rename it by deleting everything in the name of the .zip except for 2PS6IMG (and .zip of course) and place it onto your ext SD card
Boot to download mode and your phone will recognize the .zip and prompt you to press volume up to confirm the flash. Do that
When the flash is complete your phone will ask you to press power to reboot. Do that
After the RUU has flashed, either delete the .zip or rename it again to something else (add _2.51.617.32 to the name so you know what it is). If you don't do that, every time you boot to download mode your phone will try to update again.
Good luck!
Click to expand...
Click to collapse
Hello! I am having the same issue; however, I am S-ON. Do you have the RUU of the file you referenced? Many thanks!
dburger66 said:
Hello! I am having the same issue; however, I am S-ON. Do you have the RUU of the file you referenced? Many thanks!
Click to expand...
Click to collapse
That is the RUU I linked.
You could get the RUU.exe that you can run from your PC from HTC's official US website here.
But if you want to flash from SD that's the one. It works with S-On as well.
xunholyx said:
That is the RUU I linked.
You could get the RUU.exe that you can run from your PC from HTC's official US website here.
But if you want to flash from SD that's the one. It works with S-On as well.
Click to expand...
Click to collapse
Thank you!
xunholyx said:
That is the RUU I linked.
You could get the RUU.exe that you can run from your PC from HTC's official US website here.
But if you want to flash from SD that's the one. It works with S-On as well.
Click to expand...
Click to collapse
Does this require an external sdcard?
Thanks
redesignni said:
Does this require an external sdcard?
Thanks
Click to expand...
Click to collapse
No. You can run the .exe on your PC, or flash the .zip in fastboot with
fastboot flash zip 2PS6IMG.zip after renaming it to 2PS6IMG.zip