yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] tim_h:
Hi,

maybe install TWRP recovery, restore everything to the state before applying the OTA and then trying once more?

But the newer TWRP versions might not even work any more, at least I have this problem, see http://xdaforums.com/htc-one-m8/help/help-longer-enter-twrp-recovery-one-m8-t3186208.

HTC really seems to have done something nasty with this update. And it actually does not even fix all StageFright vulnerabilitis, the latest one stays open. :(

Cheers,

Tim
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
OK, I managed to get my phone back... I left the CID as HTC__001 but the trick was to rename the RUU to 0P6BIMG.zip & copy it to the root of the SD card using an adapter plugged into my PC. Then, I just rebooted it with Power & Vol Down, whereupon it automatically found it & started the update. I did note the prominent warning of "Do not power off your phone", so I left it to do its thing which took quite a while). Now, it's busy "optimizing apps", so I know that we are back up & running. OK, now, it's found the OTA & is busy downloading it again as well, so it appears that I now have a nice, stock, unrooted WWE install instead of my old O2 one. I must do a nandroid backup as soon as I replace the recovery with whatever version of TWRP works, but happy happy, I have my phone back again. I do hope the OTA doesn't kill it again when I run it, but as it is now 100% stock, I am full of hope.

Peter13337 - I don't know how to fix yours, seeing as you aren't S-OFF & the trick that I just pulled needed it, but I think that you might be able to flash an RUU that matches your own installation exactly. I would double check that though. However, if you know your CID & your modelid is 0P6B10000, then maybe your CID is in the list here http://xdaforums.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
[One (M8) Q&A, Help & Troubleshooting] tim_h:
Glad you got it running again. It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
I live right out in the sticks here in England, so my Internet connection is filthy - I'll have to leave it overnight to download all the apps that it needs to reinstall before I'll even try the OTA again. Then I'll see if the latest TWRP works, or it we have to go way back to get a version that plays nice. I also wonder where we stand on rooting this version too, but I guess that I just need to flash a current supersu from TWRP, when I finally get it working...

It looks like tomorrow will be just as much of a learning curve as today :D
[One (M8) Q&A, Help & Troubleshooting] tim_h:
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
[One (M8) Q&A, Help & Troubleshooting] peter13337:
Hmm

Found out, that i doesnt have stock OS. I Have CID VODAP102.

And Now ? Nandroid Backups which i Found for that need again S-OFF
[One (M8) Q&A, Help & Troubleshooting] m112:
crap

I've got exactly the same problem after running OTA I'm on s-on

I would be greatful for the solution

Edit: TWRP restore saved my phone

BTW it would be good to know how to apply this bloody update. I've stock rom so no sure why it bricked my phone
[One (M8) Q&A, Help & Troubleshooting] ritdaw:
I had the same issue on my O2 M8 and managed to resolve by using RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed.exe

I extracted rom.zip (by opening the exe to let it extract and then finding it within %temp%), renamed it to 0P6BIMG.zip and put it on my sdcard. I then booted up the phone with power and volume down and it applied the RUU. Once booted into Android I re-applied the stagefright update and all is working again.

Note: It will wipe the device.

o2 RUU can be found here:

https://www.androidfilehost.com/?fid=95916177934555499
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
Peter13337 - There's a Stock Nandroid backup for your CID here, which would give you (hopefully) a way out: http://xdaforums.com/showthread.php?t=2701376

It may also give you the chance to run the update, then factory reset it to Google will restore everything for you from its automatic backups. Good luck :)
[One (M8) Q&A, Help & Troubleshooting] MrChinn:
:sly: You are a legend :thumbup:
[One (M8) Q&A, Help & Troubleshooting] m112:
After restoring TWRP I tried running OTA again

it screwed the device up again

I've got a feeling there will be wave of similar posts soon

thanks HTC for faulty OTA
[One (M8) Q&A, Help & Troubleshooting] tony_5309:
Are you all trying to install this update while having TWRP as your recovery? Cause that's where your problem is.

I've put 3 HTC M8's back to full stock and accepted the updates with no problems.
[One (M8) Q&A, Help & Troubleshooting] m112:
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.

I restored the backup by booting to TWRP.
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
tim_h, I flashed TWRP 2.8.7.0 without any problems, rebooted it & used it to flash super-su 2.46 fine. It doesn't give me any problems at all & everything works & boots exactly as it should.
[One (M8) Q&A, Help & Troubleshooting] tony_5309:
Oh ok. Good.
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
OK, after flashing the RUU yesterday, as I mentioned above, I left it downloading all my apps overnight, along with the Stagefright OTA (on my reeeaaaly sloooooow Internet connection), rebooted it to load various HTC updates, then installed the OTA. WARNING! The OTA reboots it twice, & the second time it just sits there on the Boot Screen for well over a minute before it boots & goes into the whole "optimizing apps" routine. I was getting really worried that it had all gone wrong again, but thankfully I stepped away from the phone & let it be, & it came good just before I gave up hope. But compare this with what originally happened yesterday (on a rooted, slightly elderly stock ROM), when I also left it alone & it just sat there for an hour, doing nothing... I don't know the answer, but this OTA seems to be really very picky!

One it had installed & rebooted & I was 100% certain that I was in the clear on the OTA, I flashed in the latest TWRP, which worked fine & gave me no problems at all (Note, there have been reports of people having problems with recent versions of TWRP after this OTA, but I didn't replicate those problems). I used TWRP to install UPDATE-SuperSU-v2.46.zip so I am now back up & running rooted again. But because of this I now have a brand new, shiny WWE Stock ROM (as opposed to my elderly, & heavily patched O2 Stock) with the latest firmware, TWRP & SuperSU. I'm happy that it all works, but I have the greatest of sympathy for everyone out there who didn't have S-OFF, as without it I'd have had very serious problems.

Good luck everyone :)
[One (M8) Q&A, Help & Troubleshooting] tim_h:
Ok, thanks for the info. Strange that TWRP 2.8.7.0 works for you but does not for me (and at least 3 other people have reported it does not work any more).

I also have another new problem. My camera stopped working. I could not get it running again so far (wiped app data, wiped cache, numerous restarts, ...). I will now try to restore an older version of my data partition and possibly system partition. It could of course be a coincidence, maybe my camera just broke at this very moment. But reading about the multiple problems people have with this latest OTA, it seems that HTC really screwed this one up! :(

---------- Post added at 06:52 PM ---------- Previous post was at 06:06 PM ----------

Ok, restoring data did not help. Restoring system did! Very very strange. HTC seems to have screwed up bigtime.

If the camera breaks again, I am off to CM12.1.
[One (M8) Q&A, Help & Troubleshooting] tim_h:
So, the camera died again. It might be related to changes I made to platform.xml (giving rw access a la pre-KitKat). Although it worked with the modifications for a while when I made them first. I will try again.

What annoys me more is that I cannot even install CM12.1. The CyanogenMod Recovery won't boot. When I install CM12.1 from TWRP 2.8.1.0 it doesn't work. Damnit!

[MENTION=5148480]JustinSB[/MENTION], can you check the version numbers you get displayed in FastBoot? I want to find out what firmware bit causes these recovery issues. Mine are:

M8_UL PVT SHIP S-OFF

HBOOT-3.19.0.0000

RADIO-1.25.214500021.06G

OenDSP-v48.2.2-00564-M8974_F0.1211

OS-4.19.161.3

eMMC-boot 2048 MB

Aug 4 2015, 21:56:12.0
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
[MENTION=3838420]tim_h[/MENTION] , here is my fastboot info:

M8_UL PVT SHIP S-OFF

CID-HTC__001

HBOOT-3.19.0.0000

RADIO-1.25.214500021.06G

OenDSP-v48.2.2-00564-M8974_F0.1211

OS-4.16.401.13 <-- this is different

eMMC-boot 2048 MB

Aug 4 2015, 19:21:49.0

Oddly enough, I recorded the details from the Stock O2 version & OTA that crashed my phone - the one that originally caused me to use the RUU to rebuild it all. After the OTA on that original ROM, that one gave me OS-4.20.206.2, but the whole phone stuck on the Boot Screen. My current ROM is a nice, simple, WWE version.
[One (M8) Q&A, Help & Troubleshooting] whiperhack:
I have the same firmware but HTC__032 info and the issue with twrp is there. So is something else. I run the ruu.exe then updated with ota and the recovery that works is 2.8.1.0

Sent from my HTC One_M8
[One (M8) Q&A, Help & Troubleshooting] tim_h:
In the firmware.zip inside the OTA zip there are the following files:

boot.img

hboot_signedbyaa.img

rcdata.img

recovery.img

tz.img

Obviously, recovery.img does not matter. The hboot version is reported the same for all of us, so shouldn't be the culprit either (except they are different in spite of the same version number). boot.img only matters when booting the ROM (not recovery), right? That leaves only rcdata.img and tz.img as the possible causes, doesn't it?

Wait a minute, [MENTION=3710150]whiperhack[/MENTION], you started from the same RUU as JustinSB, went the same way installing the StageFright OTA and you have the TWRP issue while Justin does not? That would be really strange!?
[One (M8) Q&A, Help & Troubleshooting] whiperhack:
Yes, I installed 4.16.401.10 from PC, then run the ota, then twrp issue.

I see in boot loader that even I'm rooted and custom recovery installed, software status is official and not modified. Long time ago I changed it to show like this via adb command with an tutorial from here. From what I know running RUU should put back the original status. Strange.

Sent from my HTC One_M8
[One (M8) Q&A, Help & Troubleshooting] peter13337:
Thanks [MENTION=5148480]JustinSB[/MENTION].

I Send it to HTC to fix it ( i know they probably won't do it cause i rooted it, but i try it).

If they dont fix it, i will try it with the nandroid Backup.

But i have a question to get it right:

First i have to download the "right" Backup, with my correct CID (VodaP102) and the right Version of my TWRP.

What if the versionsnumber of the Backup, e.g.

it not the same i have ?

Restore it with my Recovery and hopefully it works.
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
[MENTION=5907854]peter13337[/MENTION], I have always treated CID's as case sensitive out of force of habit, but now that I think about it, I can't honestly say, hand on heart, that VodaP102 is a different CID from VODAP102 - & a quick search around brought me no decent info on this question either.

Is there anyone out there who knows the answer to this question for definite?

Are you absolutely 100% certain that it is VodaP102 & not VODAP102?

Good luck with HTC & I hope that they sort it out for you & don't charge you to much.
[One (M8) Q&A, Help & Troubleshooting] peter13337:
Oh. Sorry for the Mistake. I mean the different Version of TWRP.

I have VODAP102, was to lasy to write it in Cappital letters ;)

Or what is the "3.29.161.9" For a Number ?
[One (M8) Q&A, Help & Troubleshooting] wernn:
Same Problem with Vodafone branded HTC ONE M8

I've the same problem with my HTC M8, Vodafone branded, s-off, TWRP 2.8.7.0-m8, super su, Titanium Backup, modified platform.xml to optimized use of 128GB microSD, some "garbage" Apps frozen /disabled, but completly STOCK 5.02 Vodafone.

Before applying the OTA I copied back the Original platform.xml from TWRP Recovery and flashed the stock Recovery extracted from Lollipop (5.02) OTA via adb (the all previous OTA updates went fine). On the first step it looked very well, but when it booted up, after the Vodafone screen it was stucking with the white screen (the screen, after this usually the phone is up and running. Left it there for very long time but nothing happened.

No way to get it up...

However, I was able to get it into Bootloader by Volume + / Power and Volume - / Power as soonas the screen got dark!

Re-flashed TWRP 2.8.7.0 and restored my Backup taken via TWRP.

In the meantime tried 2 times more, ending up in the same scenario. Before last try I have unfrozen the frozen Apps, but no success...

May be it's worth to try to completely unroot via super su and give another try????

Hopefully we will find, what's going worse with this OTA, soon....

On the first step, I'm very likely waiting, but the OTA update pops up again and again.

However, TWRP Recovery prevents an update accidently initiated....
[One (M8) Q&A, Help & Troubleshooting] quinxy:
MY AT&T phone stuck at boot...

Ugh. So I had been refusing the patch prompts for two days so that I could do a Nandroid backup but this morning for some reason the damn thing installed the update of its own accord and now it won't boot. I had no idea it could do it of its own accord. I am 99.999% sure it did in that I was driving at the time, not touching anything, and it suddenly rebooted and applied the patch. So now I have no recent backup and am reasonably screwed. Grr....

Anyone know of a way out that doesn't require reflashing?
[One (M8) Q&A, Help & Troubleshooting] tim_h:
This is really puzzling. Two people should have the same software, one hast the TWRP issue, one does not. Also, several others reported that TWRP newer than 2.8.1.0 stopped working. What can we do to find out the cause? Maybe some more organized comparison of all version info between [MENTION=5148480]JustinSB[/MENTION] and [MENTION=3710150]whiperhack[/MENTION]?

By the way, I confirm that my camera issue was related to the modified platform.xml. I recommend not touching it ...
[One (M8) Q&A, Help & Troubleshooting] whiperhack:
I believe that is something to do with the ram_disk. Something was changed in the new firmware and new boot.img.

Sent from my HTC One_M8
[One (M8) Q&A, Help & Troubleshooting] tim_h:
What I am not sure about: Is the boot.img relevant for starting the recovery? Or just for booting the android system?
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
I ran my RUU zip from the SD Card, & I now have the red text on saying it's for devs only, which I had removed months ago. This would appear to indicate that there is a difference between the RUU exe & the RUU zip. As I don't run Windoze, I can't use the exe, so I'm guessing that the only way to test it is for someone who has used the exe & currently still has issues to try the zip method & see if their problems vanish.
[One (M8) Q&A, Help & Troubleshooting] wernn:
Is your phone on Stock Recovery or still at TWRP???

In case you are on TWRP, I don't think the OTA was installed and you should be able to get into Bootloader and TWRP.

Have the USB Cable disconnected

Power / VOL+ and as soon the screen gets dark immediatly switch to POWER/VOL-

Hope it helps in your case too
[One (M8) Q&A, Help & Troubleshooting] BartVCD:
Try this....

http://xdaforums.com/showpost.php?p=62548312&postcount=4889
[One (M8) Q&A, Help & Troubleshooting] quinxy:
Sadly, I had stock recovery installed so that I could still do OTA updates as necessary. (As I mentioned here or in another thread I didn't initiate this OTA install, I think it was automatic or the pop-up dialog maybe flashed up just as I was going to click an app's interface and I never saw it.)
[One (M8) Q&A, Help & Troubleshooting] essteekay:
Having the same issue as OP< but I am having a difficulty time finding a RUU that will work for me. Could someone point me in the right direction?

M8_UL PVT SHIP S-ON

CID-ROGERS001

HBOOT-3.19.0.0000

RADIO-1.25.21331147A1.06G

OpenSDP-v48.2.2-00564-M8974_FO.1211

OS-4.20.631.3

eMMC-boot 2048MB
[One (M8) Q&A, Help & Troubleshooting] quinxy:
I gave up on trying to recover without RUU and just went ahead and did the RUU restore.

Just a few reminders for anyone else faced with the same:

1) Before doing the RUU restore, make a Nandroid backup from within TWRP or CWM to EXTERNAL sd card

2) Copy your internal sd card folder to the EXTERNAL sd card also, RUU will WIPE your internal sd card (contrary to what some people say elsewhere)

3) After re-install with RUU you can copy the internal sd card data back to the internal sd and then re-install user apps and user app data and phone log and SMS/MMS messages and voice mails and more with TItanium Backup or Nandroid Manager or other software

Unpleasant, but gets your device back to almost like it was.
[One (M8) Q&A, Help & Troubleshooting] wernn:
Thanks for this hint, but unfortunately it couldn't fix the problem in my case.

My HTC is running fine in the current state (TWRP save restored), but the update pops up again and again.

Still searching for a solution to get the update applied....

May be it's better to wait for the next Android Release?

Another option could be to go back to Kitcat (4.4.4, CWR Backup availabble) and to start over with the Lollipo OTA ... ?
[One (M8) Q&A, Help & Troubleshooting] tim_h:
Ok, I looked into this a little further and found this presentation: http://de.slideshare.net/chrissimmonds/android-bootslides20

According to slides 5 and 12, it is indeed as I thought that boot.img is only relevant for booting normal android. To start the recovery, only the bootloader and the recovery.img are needed. [MENTION=5148480]JustinSB[/MENTION], [MENTION=3710150]whiperhack[/MENTION] and I all have the same bootloader version (HBOOT 3.19.0.0000), but [MENTION=5148480]JustinSB[/MENTION] can boot TWRP recovery 2.8.7.0 whereas [MENTION=3710150]whiperhack[/MENTION] and I cannot. I do not see what else should matter for booting the recovery. (Also, all other reported firmware version numbers matched.) [MENTION=1162986]Captain_Throwback[/MENTION], as you are the expert on this stuff, could you maybe comment if this thinking is correct?

If the above reasoning is correct, could it mean that the HBOOTs are different in spite of the same version number? Could we somehow check this (read it out and calculate an md5 or something?). I would really like to understand what causes this issue.
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
I rebooted into HBOOT & selected IMAGE CRC, which gave me the following results:

rpm: 0xD0AD2083

sbl1: 0xE3DB0B9A

sbl2: 0x0

sbl3: 0x0

tz: 0x6F642CFB

radio: 0xB37DC069

hboot: 0xC9D8C00

boot: 0xEE1DEE04

recovery: 0xA94628C2

system: 0xC7BD014A

Perhaps this will allow you to check if your images are the same or different [MENTION=3710150]whiperhack[/MENTION] & [MENTION=3838420]tim_h[/MENTION]
[One (M8) Q&A, Help & Troubleshooting] AkrumError:
I tried that, when I reboot with Vol Down, it does detect the 0P6BIMG.zip file, but then I get an error [Device halted due to Large Image update fail! Press <POWER> to reboot.]

any ideas?

P.S: I'm currenlty Bootloader unlocked, S-On, and HTC__J15 (which is in the list)

I have more than 10 GB unused storage on both SD Card and USB Storage.
[One (M8) Q&A, Help & Troubleshooting] tim_h:
Aah, great, I didn't know this was so easy. :)

Here is my output:

rpm: 0xD0AD2083

sbl1: 0xE3DB0B9A

sbl2: 0x0

sbl3: 0x0

tz: 0x6F642CFB

radio: 0xB37DC069

hboot: 0x27C3015B

boot: 0xD4EAF4F9

recovery: 0xAD478A4E

system: 0xEE63B7CE

So, rpm, sbl1, sbl2, sbl3, tz and radio are identical.

hboot is indeed different. Is that expected because we have different CIDs (i.e., does the branding influence the hboot)? It would be very interesting to now see the HBOOT CRC of [MENTION=3710150]whiperhack[/MENTION]. If it matches yours, we are back to square one, because then the TWRP issue is obviously not be related to the HBOOT. If his HBOOT CRC matches mine, then we know pretty sure that the HBOOT is responsible for the TWRP issue (and also that branding does not influence the HBOOT). If [MENTION=3710150]whiperhack[/MENTION]s HBOOT CRC is different than both of ours, we are not really further.

That boot, recovery and system are different between us is logical. boot is very likely CID-dependent (Vodafone logo, ...). recovery is TWRP 2.8.1.0 for me and 2.8.7.0 for you. System is obviously CID-dependent, also modified in my case.
[One (M8) Q&A, Help & Troubleshooting] whiperhack:
Here is mine:

rpm: 0xD0AD2083

sbl1: 0xE3DB0B9A

sbl2: 0x0

sbl3: 0x0

tz: 0x6F642CFB

radio: 0xB37DC069

hboot: 0xC9D8C00

boot: 0xEE1DEE04

recovery: 0xAD478A4E

system: 0xBD0B0D64

Different from all ..... :D
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
[MENTION=3838420]tim_h[/MENTION], as you are S-OFF, why not just follow exactly what I did & change your CID to HTC__001, factory reset it, then copy the zip file of the nice WWE release to the SD Card & flash it that way. Theoretically then, it 'ought' to fix all of your problems. If you have access to Titanium Backup or the like, you could restore everything as soon as it has installed the OTA, rather than letting Google rebuild it all from its backup. That way, you don't have any issues with the O2 image & life 'should' be easier from here onwards as you have a very easy to find RUU...
[One (M8) Q&A, Help & Troubleshooting] JustinSB:
I don't know if you're S-OFF too, [MENTION=3710150]whiperhack[/MENTION], but it appears that O2 & whatever 'brand' yours is may have 'modified' things a little too much, which is why the very stock WWE image gave no problems at all, but the O2 version & your version blew chunks. I know it's a pain in the neck, but I'm pretty sure that if you are S-OFF, then changing your CID, factory resetting it, & moving over to the completely standard stock WWE image from the zip file 'should' eradicate all of your oddities.
[One (M8) Q&A, Help & Troubleshooting] whiperhack:
I'm factory unlocked 032 Europe S-OFF. I don't think that changing the CID is the solution, instead is like hiding the issue. If in the future I will really need newest TWRP I'll do it. I'm good with stock moded for now.