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 !
Related
Hi,i've downloaded the three dot mode from here:
http://forum.xda-developers.com/showpost.php?p=25063642&postcount=279
The problem is that it isn't working,phone just stucks at the logo(HTC ONE).Is that only made for 1.28?I have 1.26.Can someone please give me the 1.26?
Or else,can anybody tell me how to upgrade from 1.26 to 1.28?
PS:I have stock rom,only CWM and unlocked bootloader (from htcdev).
maybe this mod is only available for 1.28.
i think you have to wait for an OTA to 1.28, or flash a rom with this number?
Yeah,i've seen a lot of custom ROM's out there for One X but i want to stay as stock as possible and this is the only thing i hate at this phone,the three dots are realy annoying.
Yesterday i've downloaded the MILocker.The app is verry great but the three dots apear on the lockscreen and kinda spoils the whole aspect if you know what i mean.
Are there so many diferences between 1.26 and 1.28?
i found this, but idk if this helps you
http://forum.xda-developers.com/showthread.php?t=1551581
I saw that post but honestly i have no ideea what that means.This is my first Android phone and i'm kinda scared not to do anything stupid to it and brick it or something worse.And i've allready unlocked my bootloader and my CID is none...
The three dots mod is available for 1.26 but only for deodexed roms as far as I can see, if you upgrade to 1.28 you'll be able to use it on the stock odexed rom.
If you made a backup in recovery you can restore that to get out of the HTC splash screen, if you don't have a backup then run an applicable RUU to return your firmware to stock.
There are several custom roms available that don't look cosmetically different to the stock rom but will allow you to install the 3 dots mod. You could give those a go if you want, eg Android Revolution HD.
edit: removed
hopscotchjunkie said:
The very first post in the three-dot mod thread has attached links to the mod for 1.26 as well as 1.28 (you need the ones with filename beginning "126_").
Click to expand...
Click to collapse
They're only for deodexed roms, they won't work on the stock rom.
rogersnm said:
They're only for deodexed roms, they won't work on the stock rom.
Click to expand...
Click to collapse
Yeah I know, you quoted me in the seconds between me posting that and realising and removing it. Too quick off the draw.
I didn't had any problems restoring.I've made a nanodroid backup the second i've installed the CWM.Because it's my first time with an Android phone i've made a lot of backups,and daily i am making a backup in Titanium.
Well the post sayd for stock roms(1.26,1.28),but so far for me doesn't work.
Hoping an experienced guy from the forum does a three dot removal for stock roms 1.26.
jeyml said:
I didn't had any problems restoring.I've made a nanodroid backup the second i've installed the CWM.Because it's my first time with an Android phone i've made a lot of backups,and daily i am making a backup in Titanium.
Well the post sayd for stock roms(1.26,1.28),but so far for me doesn't work.
Hoping an experienced guy from the forum does a three dot removal for stock roms 1.26.
Click to expand...
Click to collapse
That odexed version is for 1.28 only. You should get an OTA which will allow you to update to 1.28 and then you'll be able to install the 3 dots mod.
Ok,sorry if i apear to be an idiot(witch i am),but what does OTA means?
It stands for "over the air", it's basically an update package you can download and install. If you go to settings and check for updates it may give you the option to update to 1.28, it depends on whether or not it's been made available for your carrier/region yet.
Oww i understand now.Yes i have a notification witch tells me i can update but i don't know if it's 1.28 and i didn't update because i'm afraid to lose my root.If i update i will have to flash the supersu again for the 1.28 i presume?
That should be the 1.28 OTA, you shouldn't lose root but if you do you can just re-root it again with the same instructions. After you install the update you should be able to install the 3 dots mod (check your version number first though).
Ok,just gave the phone to update.After i update i will make a new nanodroid backup and then i will check if i have the root,if not...well...i will have to do the whole process again.I will post soon.Thank you all for helping a noob like me.
EDIT:After download i gave it to update,phone restarted an then it gives me an error:
E:unnkwown volume for path [INTERNALSDCARD: Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.301.9-1.26.401.2_release_256505w0tk6eiq8g74y4vb.zip]
E:Can't mount (that thing that says upwards)
Installation aborted.
Positive side: I know it's 1.28 update
What do i have to do?
jeyml said:
Ok,just gave the phone to update.After i update i will make a new nanodroid backup and then i will check if i have the root,if not...well...i will have to do the whole process again.I will post soon.Thank you all for helping a noob like me.
EDIT:After download i gave it to update,phone restarted an then it gives me an error:
E:unnkwown volume for path [INTERNALSDCARD: Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.301.9-1.26.401.2_release_256505w0tk6eiq8g74y4vb.zip]
E:Can't mount (that thing that says upwards)
Installation aborted.
Positive side: I know it's 1.28 update
What do i have to do?
Click to expand...
Click to collapse
You need the stock recovery to run the OTA. Hook your phone up to your pc and boot it into fastboot mode like you did when you were rooting it. Download this file: http://www.androidrevolution.nl/ARHD/OneX/Recovery/endeavoru_recovery_signed.img and place it in the same directory as your fastboot exe then navigate to that dir in cmd prompt and enter the command:
Code:
fastboot flash recovery endeavoru_recovery_signed.img
After that try running the OTA again and it should succeed, then you can reflash CWM.
Ok,i understood.After that is this CWM good?
recovery-clockwork-touch-5.8.2.7-endeavoru.img
It's the same i've used the first time i've unlocked my bootloader.
You should flash the latest version of CWM:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.3.1-endeavoru.img
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
It has a few bug fixes and allows you to charge the device whilst it's off
Done with the endeavoru_recovery_signed.img.I am now trying to update,i will edit as i do the steps you told me.
Ok,the update has started,so far so good.
Update finished,now optimizing the applications step.After this i will flash the new CWM,hope it works.
Flashed the CWM,now waiting to power up and check up if i have the root.
I don't have root acces (((.Is this file good: CWM-SuperSU-v0.88.zip?
OK, So after searching and Searching for a way to go back to complete stock after taking the latest 1.31 update and rooting my HTC One, and not being able to use any current RUU without having to gain S-off. I finally did it. I am 100% stock on an updated software version of 1.31.651.2.
So here is what I did and please feel free to step in and let me know if there was an easier way.
Step 1.
I unlocked my boot-loader to gain root privileges
Step 2.
I flashed TWRP
Step 3.
Created Nand Backup if something fails
Step 4.
I flashed SuperSU
OK, so that got me rooted. but I wanted to go back to stock after playing around with certain roms my phone started acting goofy.
this is the part where it gets a lil tricky.
in order for me to get back to stock on my One to the most current version of 1.31.651.2.
this is what I had done.I installed an app from the market called Rom toolbox lite(FREE) put REVONE in /data/local/temp
gained S-off. installed a stock RUU 1.29.651.7. Now the only problem is that I was S-off and my boot loader shows tampered and unlocked.so I used revone to remove tampered with the -t command and also wanted to lock the boot loader with the -l command. in order to get s-on. booted into the boot loader and selected fastboot and entered fastboot command, fastboot oem writesecureflag 3 to regain s-on.
ok so I am still technically rooted so in order to remove all root instances I ran again the RUU 1.29.651.7. all good so far. I double checked by booting into the boot loader to make sure I am s-on and locked along with no tampered flag. YES!!!!. so now I booted up my phone . skipped all setup processes. and went straight to the check for updates in the phone menu. I updated to the next most recent after the 1.29.651.7 and installed 1.29.651.10. I download and installed the update. again checking to see if there were any changes in the boot loader. NOPE STILL ALL GOOD,YESSSS!!!!
so now it rebooted and again went straight to the HTC update menu and ran a check for updates and it then downloaded the most recent update 1.31.651.2. Installed and I checked the bootloader and I AM NOW 100% STOCK and on the latest software version.
At least a Thank You ??
Thanks for Sharing!
viper1723 said:
At least a Thank You ??
Click to expand...
Click to collapse
I was having the same issues when trying different Roms and screwed up my phone to the point where roms would boot but them restart over and over and over...no matter what rom i loaded and any kind of wiping i did.
so I also returned to stock locking the bootloader and flashing stock RUU as you mention. Just tried going from 1.29 to 1.31 with OTA last night and it wiped my phone and didn't upgrade. So i'm hoping it was just a hiccup and going to try again.
Hope it works this time.
Solartrooper said:
I was having the same issues when trying different Roms and screwed up my phone to the point where roms would boot but them restart over and over and over...no matter what rom i loaded and any kind of wiping i did.
so I also returned to stock locking the bootloader and flashing stock RUU as you mention. Just tried going from 1.29 to 1.31 with OTA last night and it wiped my phone and didn't upgrade. So i'm hoping it was just a hiccup and going to try again.
Hope it works this time.
Click to expand...
Click to collapse
Let me know how it went I'll give u a more detailed method of what I did exactly
That's were I'm at right now.
viper1723 said:
Let me know how it went I'll give u a more detailed method of what I did exactly
Click to expand...
Click to collapse
Okay guys so everything you described is exactly where I'm at. I've tried a million ROMs, process, adb.exe (no devices), etc...... Anyway here's my scenario.... Exactly yours: got my phone, rooted it, had S-On. the phone ran it's updated to 1.31.651.2 so there are no RUUs for this. Any extra details to get me there?
Where should I start? Please let me know if you can help.
Thanks!:cyclops:
Hi all,
so I got my M8 like three weeks ago and made the ultimate mistake of not backing up MY factory ROM before flashing stuff. I went ahead and, following a guide from 'teh internets', turned my phone into a Google Play Edition after a successful S-Off with SunShine. About a week later, I started missing some Sense features and tried to revert back to stock which proved difficult at first due to partition size issues. Finally, I was successfully following a mixture of several guides in this very forum, flashing different combinations and versions of stock ROMs, firmwares and recoveries. I'm on Sense again. Last thing I can't get rid of is a message in HTC Tell that's talking about a testing device and how I could not turn off HTC Tell for that reason.
Long story short, I do now have a phone that reads:
Code:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-HTC__102
HBOOT-3.19.0.0000
RADIO-XXX
OpenDSP-XXX
OS-3.28.401.7
eMMC-boot 2048MB
Oct 10 2014,00:20:35.0
Unfortunately, I do not exactly remember which Recovery I flashed last. I'm pretty sure it was one from the Stock Backup & OTA Collection thread. If I go into recovery, I get a red triangle and nothing happens.
Now for my question, I want some features of Lollipop really bad and I know HTC is going to come out with their Lollipop-Sense in about two weeks. I would gladly wait and go for it instead of starting over and turn my phone into a GPE again. Question is, will I get the Sense OTA or is there anything that will keep me from it?
Thanks a lot for reading and any information I got (and hopefully will get in the future) from the folks on this awesome forum!
If you are on the appropriate stock ROM for your CID, and corresponding stock recovery, you will get the OTA.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
jndvid said:
Unfortunately, I do not exactly remember which Recovery I flashed last. I'm pretty sure it was one from the Stock Backup & OTA Collection thread. If I go into recovery, I get a red triangle and nothing happens.
Click to expand...
Click to collapse
Red triangle is stock recovery. However, its not clear whether its the right stock recovery. You need to be on the stock ROM for your CID, and the recovery needs to be the one that matches that software number. Just find the stock ROM (and corresponding recovery) for your CID on the following thread.
http://forum.xda-developers.com/showthread.php?t=2701376
There is no harm in restoring the correct stock ROM and recovery over whatever you have now (whether the current state is correct for your CID or not). But being on the correct stock ROM and recovery will put you in the right place for OTA.
Thanks for the explanation.
So it is safe to assume that if I flash TWRP now and restore the 3.28.401.6 nandroid and recovery from this thread, I should A) get the OTA from .6 to .9 and later on B) the Sense-Lollipop OTA?
Sorry for the redundancy of my question but without a speedy internet connection, downloading ROMs is a time-consuming project, so I want to get it right the first time now.
jndvid said:
So it is safe to assume that if I flash TWRP now and restore the 3.28.401.6 nandroid and recovery from this thread, I should A) get the OTA from .6 to .9 and later on B) the Sense-Lollipop OTA?
Click to expand...
Click to collapse
If you restore to .6, it won't install the .6 OTA since its already on that version. But yes, it should install any "more up-to-date" OTAs (and then any future OTAs as they are released) in sequence once you return to stock and check for updates.
Thanks again. I will report back after flashing.
Well, it worked - I think. However, a little more research showed that the red text in HTC Tell is present because I unlocked my phone, particularly the bootloader, via HTCDev. I will consider to revert that change in the future.
I restored (via TWRP) the stock 3.28.401.6 and flashed the corresponding stock recovery. Unfortunately, no update is to be found yet (according to the OTA collection, there should be an update from .6 to .9 which I hoped to get automagically or on manual query in phone settings).
For the time being, I can download the OTA myself from the awesome collection and then update manually through stock recovery, I suppose.
jndvid said:
Well, it worked - I think. However, a little more research showed that the red text in HTC Tell is present because I unlocked my phone, particularly the bootloader, via HTCDev. I will consider to revert that change in the future.
Click to expand...
Click to collapse
The device will come up as a "test device" since its s-off.
jndvid said:
I restored (via TWRP) the stock 3.28.401.6 and flashed the corresponding stock recovery. Unfortunately, no update is to be found yet (according to the OTA collection, there should be an update from .6 to .9 which I hoped to get automagically or on manual query in phone settings).
Click to expand...
Click to collapse
I'm not that familiar with the WWE updates, as its not my version. So I don't know of the .7 and .9 updates deployed to all folks in all regions that have the WWE version, etc. You might check with folks that know more about the WWE updates.
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
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.