I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.
Hi, I've just bought a HTC One M8 from craigslist and I have a problem or two. The phone cannot connect to google servers, but the posts I found to fix that didn't help (delete hosts, install gmail). The main problem is I can't get it back to stock to get the new firmware (it's on 4.4.3), which I thought may cure my problems.
The phone is on Venom ROM, carrier is T-Mobile USA, tampered and unlocked flags showing, S-On
Here's what happens when I try to flash a recovery image:
adt and fastboot do exactly what they are supposed to do, but when I hit "Recovery" on the phone it says 'entering recovery', then just boots up as normal. I never get to TWRP. If I use CWM, it says 'entering recovery', then goes back to fastboot.
For some reason, the phone is taking a good 60 seconds to boot up each time.
I have tried to go to S-Off, but I got the Firewater message:
*** whelp, this sucks, firewater can not work on your device *** (etc.)
Can you tell me how to get communication to Google working again, or how to upgrade the firmware?
Thanks for your help, I am new to this, and running out of ideas
Alex
I would say use fastboot to install TWRP and try again. Or use fastboot to install the stock bootloader and then try to flash an RUU. Google around this forum for instructions.
like FreydNot said, I'd try downloading and fastbooting the latest TWRP onto the phone. power it down and let it chill for a minute and then try to get into the recovery.
Hi all,
This is my M8 - Stock, Rooted & S-OFF. It's an unlocked O2 one which I use on EE in the UK
M8_UL PVT SHIP S-OFF
CID-02___001
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenSDP-v48.2.2-00564-M8974_FO.1211
OS-4.20.206.1 <--- after the OTA, this now reads OS-4.20.206.2
eMMC-boot 2048MB
The Stagefright OTA for my M8 just downloaded, so I re-flashed recovery with one that I extracted from the last 5.0.1 OTA (it usually has the latest TWRP) & let it install the OTA. Everything went fine, it rebooted afterwards to recovery, then automatically rebooted again... & then it sticks at the boot screen after showing the O2 logo & chiming.
From the stuck boot screen, I can reboot it into the boot loader or recovery fine, but now when I boot it into recovery I get this:
Android system recovery <3e>
LRX22C release-keys
Volume up/down to move highlight;
enter button to select.
reboot system now
apply from sd card
wipe data/factory reset
wipe cache partition
reboot into bootloader
power down
view recovery logs
apply from phone storage
_____________________
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
Write host_mode success
handle_cota_install: No CW files. Skip cw installation.
What do you advise?
I haven't tried to factor reset it yet, but there is nothing on the phone that isn't backed up, so I can reset, re-flash or do anything required to get it back. As it's S-OFF, at a pinch I could change the SID & flash an entirely different ROM, although I have tended to stay Stock up until now...
If everything else fails, is it worth downloading the 5.0.1 RUU from http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 resetting my CID to HTC__001 & then letting it re-download & re-install the OTA before I re-root it & install TWRP again?
Nope... that didn't work! I just get
(bootloader) shift_signature size for header checking...
FAILED (remote: 32 header error)
regardless of whether I have a CID of HTC__001 or 11111111
& a factory reset doesn't seem to have made any difference either, as it is still stuck on the boot screen.
Any ideas of what to try next please?
Hey i Have the same Problem, but i doesnt have S-off (Still on S-ON) so i cant get RUU, or ?
Problemts solving hints ?!?!
I got the same problem, stuck on the boot screen.
S off, supercid, rooted, stock recovery and rom.
Hope we ll havé a solution quickly...
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://forum.xda-developers.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
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://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
JustinSB said:
OK, I managed to get my phone back...
Click to expand...
Click to collapse
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.
tim_h said:
It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.
Click to expand...
Click to collapse
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
JustinSB said:
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...
Click to expand...
Click to collapse
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
JustinSB said:
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://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
Click to expand...
Click to collapse
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
peter13337 said:
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
Click to expand...
Click to collapse
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
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
Peter13337 - There's a Stock Nandroid backup for your CID here, which would give you (hopefully) a way out: http://forum.xda-developers.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
ritdaw said:
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
Click to expand...
Click to collapse
:sly: You are a legend :thumbup:
Sent from my Nexus 6 using XDA Free mobile app
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
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.
Sent from my HTC One_M8 using Tapatalk
tony_5309 said:
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.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.
tim_h said:
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
Click to expand...
Click to collapse
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.
m112 said:
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.
Click to expand...
Click to collapse
Oh ok. Good.
Sent from my HTC One_M8 using Tapatalk
JustinSB said:
I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
Click to expand...
Click to collapse
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
Hi, recently I converted my international HTC One M9 to Developer Edition so that I could receive the Marshmallow OTA. This worked and I had everything setup, but whenever I booted the phone I was shown a red warning text. After surfing the internet for a while, I found a file to flash through ADB that should fix the problem. The file stated that it was for the Developer Edition, so compatibility should have been fine. Unfortunately, the first time I flashed it, it said error, please flush immediately and so I flashed it again. The second time it took much longer and then said it had been a success. However, when I went to reboot, it went straight to bootloader, and from there I can access download and recovery, but rebooting only takes me back to the bootloader. I have tried the hard reset key combo to wipe the cache and also 'fastboot erase cache' but it is still stuck.
My CID and MID is BS_US001 and 0PJA11000.
Software status: Official.
Unlocked and S-OFF.
Any help would be greatly appreciated as this is my daily driver and I need it online soon . I will probably try a factory reset and if that doesn't work maybe RUU it again
-----------------------------------------------------------------------------------------------
Just tried a factory reset and it went straight to bootloader so I have now started to RUU it again using 0PJAIMG in the SD Card. Fingers crossed :/
i did flash dev ed 2.11 and then OTA all way to Dev 3.35.617.12 MM, i will try on the afternoon to root with twrp 2.8.7.1beta and SUperSU 2.65.
just flash 3.35.617.12-Firmware-noredtext-aboot-only.zip if you are right now on this firmware , you will get the msg (90 pre-update FAIL) do not worry about this MSG as this is actually a success msg . all you have to do after that is to just use this command (fastboot reboot) . all done your m9 device will reboot into normal mode with no red text warning.