Develop Bugs

Possibly bricked One X - need assistance!

Hey, everyone!
So within the past week or two my stock standard HTC One X started playing up, which I'm pretty sure was a result of a recent system update (to 4.2.2, from memory). My 'twilight' app (similar to f.lux but for phones) started randomly turning on and off for no reason, the screen became very rapidly unresponsive unless a great deal of force was applied or the phone was repeatedly locked and unlocked, it began to heat up (even more so than normal), etc, etc. Yesterday the unthinkable happened: it got stuck in a bootloop.
So here's how I wound up where I am right now.
I came to terms with the fact that I was going to lose all of my data (at least Google has automatically backed up my images and videos every few days), and anyone important enough to me that I need their phone number I also have on facebook/google plus or see frequently enough in person that when the issue is resolved I can add their numbers again. So I performed a factory reset hoping that would fix the problem. It didn't. Today, at the behest of a friend of mine, I decided to flash a custom ROM on my phone in an effort to salvage what was increasingly likely looking to be a $600 paperweight. I've never done this before, so I followed the instructions in the following video exactly as shown, and downloaded the latest stable version of Cyanogen mod for the One X. The video can be found by googling, "HTC One X - How To Root (in-depth)". It's the first result.
Everything went... well, not smoothly. But I got there in the end. Eventually the phone rebooted, and the blue (or cyan, I suppose) Cyanogen mod logo came up with the circular loading symbol tracing around it. It stayed this way for some 30 minutes or so. I decided to reboot the phone. Same issue again. I performed a factory reset, cleared the cache, cleared the Dalvik cache, and rebooted again. Still wouldn't pass the booting process. I cleared everything a second time and even reinstalled the update.zip (which for some reason appeared as update.zip.zip in ClockworkMod Recovery v5.8.2.7... I'm wondering if that caused some issue). Still no progress. Eventually, out of frustration, I began playing around with random settings within Clockwork Mod Recovery and tried backtracking a few steps computer-side in terms of the installation process, and somewhere along the way I've really F'd things up.
And here's the current situation.
Now, whenever the phone restarts the white HTC splash comes up, followed very quickly by a black screen which flickers momentarily, and then immediately jumps to ClockworkMod Recovery (v5.8.2.7).
Whereas earlier today both fastboot and adb recognised my device, now only fastboot will. I can't get anything to appear in the adb device list anymore. I'd prefer it if people didn't immediately scream, "DRIVER ISSUE!" considering adb worked for half of the day so it seems relatively unlikely to me that that's the problem.
My computer itself won't recognise that my phone is plugged in (probably because there's no OS anymore by the seems of things). I've tried two USB cables to no avail (the first worked earlier on this afternoon, so that shouldn't be an issue).
Within the 'choose zip from sdcard' section of ClockworkMod Recovery I can choose from (other than all of the files that were already in there):
CWN-SuperSU-v0.87.zip
update.zip.zip (the double file extension really bugs me)
'mount USB storage' within ClockworkMod Recovery gives me an erroy reading, E: Unable to open ums lunfile (No such file or di...) (runs off the screen, although presumably it just says no such file or directory exists).
I can't think of anything else that's relevant or would help troubleshoot this issue. If you need anymore info please just let me know and I'll do my best to supply it (you may have to lead me through the data acquisition process, however). I'm really hoping the phone isn't completely bricked because I don't exactly have the money right now to buy a new phone - I'm a uni student who only works part time and I just bought a car a few weeks ago. Bye bye, savings.
Regards,
Scott.

man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?

Want a working phone for now, follow this :
Download this recovery and flash it :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.

Husky34 said:
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Click to expand...
Click to collapse
I flashed SOME .img file, but not one called 'boot.img'. Can't remember when, unfortunately. If you find the youtube video I mentioned I followed that exactly.
No recovery unfortunately. I saw no point given that the phone was almost unusable in any form prior to me getting Cyanogen installed (it was constantly and randomly rebooting). Probably a mistake in retrospect.
Version 10.2, by the way.
Mr Hofs said:
Want a working phone for now, follow this :
Download this recovery and flash it :
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Click to expand...
Click to collapse
Can you walk me through it step-by-step. Again, I'm a total noob to this and I DON'T want to stuff this up again. Is the fact that adb (or my PC in general) isn't recognising my phone going to make this difficult? I mean how am I meant to copy anything to the SD card if I can't access it through windows explorer or via adb push?!

You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps

Mr Hofs said:
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Click to expand...
Click to collapse
This seems to work at first - instead of jumping into ClockworkMod Recovery, after flashing the image file you gave me, it jumps into a new recovery mode. But after rebooting and going into recovery mode again it's back to ClockworkMod Recovery (I made sure to clear the cache).

You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !

Mr Hofs said:
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Click to expand...
Click to collapse
Oh. Well it looks different the first time I boot into recovery versus the second time (PhilZ Touch 5 with a distinct purple background the first time, but the second time it goes back to a black background with blue text).
Not really sure how to proceed from here. Battery is dropping fast (9%) despite being plugged in, so I'm worried if I don't fix this ASAP it'll be forever FUBAR.

The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
If you use Fastboot flash recovery command the old one is gone.....can't come back like that !

Mr Hofs said:
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
Click to expand...
Click to collapse
Mr Hofs, you sir are a gentlemen and a scholar! I have managed to get back to the initial bootscreen for Cyanogen mod. AND SUCCESS! IT JUST PASSED THAT SCREEN AS I WAS TYPING!
I am indebted to you, you glorious man! Thank you so very much I'll keep you guys posted (for better or worse)!

Hope it will be fine. I will keep an eye out here

Mr Hofs said:
Hope it will be fine. I will keep an eye out here
Click to expand...
Click to collapse
So I tried updating the camera (?) as a suggested update after getting back into my phone, and it's already stuffed up again. It rebooted and said that root access has possibly been lost. What's happening now?

Doesn't appear to be a big issue for now, actually. Reset, not caused any problems since then! Managed to get google apps working, and downloaded a bunch of the apps I need All's well!
Thanks one again!

Alright ! Hope i don't see you here again

Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?

darule_2011 said:
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
Click to expand...
Click to collapse
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA

Mr Hofs said:
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Click to expand...
Click to collapse
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
Radio-0-19as.32.09.11_2

As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....

Mr Hofs said:
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Click to expand...
Click to collapse
uh oh, that doesn't sound good for me...I don't have the XL version, just the one X. Will that matter? Did I flash this baby using files for the XL when I should have used something else?

No you don't read well. You have the HTC one XL (EVITA) and this forum is for the ENDEAVORU HTC one X international version.
We here have the quad core and you there have the dual core phone !

OMG,i am so lost!

tried to get OTA 5.0.1 today. woudn't take. I have (had)rooted,s-off,bootloader unlocked. Now i somehow wiped everything off.No OS, no recovery. No idea how to begin again. Screen is on white with HTC logo and Powered by android showing. won't power down. Any ideas?

Try holding volume up with power button down for ten seconds.
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
Are you sure you wiped everything, or are you just assuming this based on the screen you are seeing?

update
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks

stlsports said:
ok, i held power up/power for 20 seconds, then power down/power and got into twrp recovery. there is NOTHING else on the phone. No OS at all. what's the best way to proceed? PC wont pickup device,so adb cmd prompt isn't working. thanks
Click to expand...
Click to collapse
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.

i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Theoriginalgiga said:
What I would do is pop out my MicsoSD card, back everything up on it then download my original OS I WAS running before I blew it up onto the SD card and attempt to flash it. From there I'd hit up this thread http://forum.xda-developers.com/showthread.php?t=2714456 to see if I could glean how to return back to stock. I'm sure someone will yell at me if you shouldn't do it, not that am I saying you should do that, I'm just saying what I'd do.
Click to expand...
Click to collapse

stlsports said:
i was able to get lollipop dream on my sd card and flash it. WHEW! but, i really want stock rooted lollipop. i actually enjoy sense 6.0 a little bit. gonna keep at it..
thanks.
Click to expand...
Click to collapse
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.

Theoriginalgiga said:
Well now that you're up and running, you can go through the process of flashing the old stock rom (not the lollipop rom), unroot and restore the stock BL, then take the OTA update and I believe you should be able to reroot if you wanted to.
Click to expand...
Click to collapse
couldn't he just flash the most current RUU?

deepsouth06 said:
couldn't he just flash the most current RUU?
Click to expand...
Click to collapse
Maybe, I'm not sure. I was able to because I was coming from just the stock rom rooted with xposed on it I know that at the least BL needs to be stock and match the version of stock ROM you nandroided back on. If you're using RUU I don't think unrooting is important. Whether or not you have to lock the BL I'm not aware of myself but it's an easy process. Below is what I did.
Being on a rooted stock ROM running xposed I downloaded drivers, BL that matched my ROM, ADB/fastboot current RUU I was on and latest RUU.
I was on 4.4.4, I verified the version of my ROM and got the matching BL. I've heard rumors that mismatching BL/ROM will cause an error.
FIRST I booted into my custom recovery and did a back up. Better safe than sorry right?
booted into fastboot and installed the recovery using fastboot flash recovery {recoveryname}.img
locked BL using "fastboot oem lock" rebooted my phone into the OS then fired up the latest[/B ]RUU and let it run and it ran just fine.
I then unlocked my BL again and installed the latest version of TWRP, reinstalled root and my apps. phone runs really well. I need to start going through and freezing apps but hey we skip those things at 2am don't we?
Mind you I have S-off on my phone and I didn't mess with S-off at all.
I would surmise that if you're experiencing getting the latest RUU to install that you might want to make sure your BL and rom number match and if that doesn't work try flashing the RUU that you're currently running and then the latest RUU.
I consulted this list to verify my version I was running, I happened to be running at the time 3.32.531.2 so I hunted for that BL.
https://support.t-mobile.com/docs/DOC-10366

HTC One M8 - Stuck at Boot Screen after Stagefright OTA [FIXED with RUU]

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

Wiped System file in TWRP, flashing new ROMs does nothing

Alright guys, I'm new to posting here but I used tutorials from here to root my LG G-Flex 2 and now my HTC One M9. I rooted it about 4 months ago, used it normally for a portion of that, for a time the charger port was broken so I had to get that fixed and got it back still normal, rooted and with TWRP as a custom recovery and such but otherwise working perfectly fine.
I had the android update notification up in my face all the time and I couldn't get rid of it myself and couldn't be bothered wasting too much time fixing it so I just decided I'd unroot the phone and go back to normal android since I hardly took advantage of the fact that it was rooted anyway.. I downloaded the system update and told it to install, I figured this would just get rid of the root for me and all would be good, but it didn't work. It would start the update then just boot itself into TWRP as normal. TWRP was getting in the way of it going into normal recovery mode to do the update.
This is where I ****ed up big time, and I know this was entirely my fault and I feel retarded for thinking it would do anything other than what it did. I went into the Wipe option in TWRP (V2.8.5.0 btw) and wiped the entire system folder. I don't know what I was thinking, something in my head made me think it would just factory reset the system and get rid of the root, which was just dumb as hell because it wouldn't have changed the custom recovery or anything anyway, and it didn't..
I've tried everything I can think of, the phone boots into all the different modes normally, Bootloader works fine, Download mode works fine, recovery works fine.
I used Squabbi's HTC One M9 Toolkit V 1.6.1.0 to update my TWRP to 3.0.0 but it won't go any higher than that without just looping until I flash it back to 3.0.0. I have tried ADB sideloading, it won't work, adb won't even read the Viper zip file I have in the same folder and stuff correctly. I've tried using an SD card to put the Viper zip onto the phones internal storage and install using TWRP, it all installs correctly and encounters zero problems but when I reboot the phone it just boots to the bootloader, the same thing happens when I tried Android Revolution ROM.
adb push command doesn't do anything, adb sideload doesn't do anything, nothing does anything.
I should also mention my HTC One M9 should be the international model, I live in Australia, its second hand and works with 2 different carriers that I have tried it with, I'm with Optus and didn't have to get it unlocked to use my SIM with it right away.
For transparancy I'll list out what is shown on each screen in case it helps in some way..
In download mode:
hTC download mode
*** UNLOCKED ***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.710.5
Sep 30 2015, 14:12:12(573756)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
^ Those all function properly except for reboot, that reboots to bootloader.
In bootloader:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***
and all the menu items as normal, again all function properly except for the general reboot.
The phone has been completely system wiped with TWRP now, flashing new ROMs still doesn't work.
I'd like it if people could give me suggestions and I can let you know if I've tried them already since I have tried a fairly large array of things to fix this problem, some of them I can't remember right now tbh..
Thanks all
UPDATE: Using lamahgra's suggestion I have successfully fixed the problem, phone is functioning perfectly normally now

CryloRends said:
Alright guys, I'm new to posting here but I used tutorials from here to root my LG G-Flex 2 and now my HTC One M9. I rooted it about 4 months ago, used it normally for a portion of that, for a time the charger port was broken so I had to get that fixed and got it back still normal, rooted and with TWRP as a custom recovery and such but otherwise working perfectly fine.
I had the android update notification up in my face all the time and I couldn't get rid of it myself and couldn't be bothered wasting too much time fixing it so I just decided I'd unroot the phone and go back to normal android since I hardly took advantage of the fact that it was rooted anyway.. I downloaded the system update and told it to install, I figured this would just get rid of the root for me and all would be good, but it didn't work. It would start the update then just boot itself into TWRP as normal. TWRP was getting in the way of it going into normal recovery mode to do the update.
This is where I ****ed up big time, and I know this was entirely my fault and I feel retarded for thinking it would do anything other than what it did. I went into the Wipe option in TWRP (V2.8.5.0 btw) and wiped the entire system folder. I don't know what I was thinking, something in my head made me think it would just factory reset the system and get rid of the root, which was just dumb as hell because it wouldn't have changed the custom recovery or anything anyway, and it didn't..
I've tried everything I can think of, the phone boots into all the different modes normally, Bootloader works fine, Download mode works fine, recovery works fine.
I used Squabbi's HTC One M9 Toolkit V 1.6.1.0 to update my TWRP to 3.0.0 but it won't go any higher than that without just looping until I flash it back to 3.0.0. I have tried ADB sideloading, it won't work, adb won't even read the Viper zip file I have in the same folder and stuff correctly. I've tried using an SD card to put the Viper zip onto the phones internal storage and install using TWRP, it all installs correctly and encounters zero problems but when I reboot the phone it just boots to the bootloader, the same thing happens when I tried Android Revolution ROM.
adb push command doesn't do anything, adb sideload doesn't do anything, nothing does anything.
I should also mention my HTC One M9 should be the international model, I live in Australia, its second hand and works with 2 different carriers that I have tried it with, I'm with Optus and didn't have to get it unlocked to use my SIM with it right away.
For transparancy I'll list out what is shown on each screen in case it helps in some way..
In download mode:
hTC download mode
*** UNLOCKED ***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.710.5
Sep 30 2015, 14:12:12(573756)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
^ Those all function properly except for reboot, that reboots to bootloader.
In bootloader:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***
and all the menu items as normal, again all function properly except for the general reboot.
The phone has been completely system wiped with TWRP now, flashing new ROMs still doesn't work.
I'd like it if people could give me suggestions and I can let you know if I've tried them already since I have tried a fairly large array of things to fix this problem, some of them I can't remember right now tbh..
Thanks all
Click to expand...
Click to collapse
hi,
try to download a full twrp backup of a stockrom from
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
put it on your sd card an recover it via TWRP... so all partions should work....

lamahgra said:
hi,
try to download a full twrp backup of a stockrom from
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
put it on your sd card an recover it via TWRP... so all partions should work....
Click to expand...
Click to collapse
This might be the way to go, I've already lost all my data on the phone so I don't care if its a stock restart. I just need to know how to identify which backup I would need for my particular phone?

CryloRends said:
This might be the way to go, I've already lost all my data on the phone so I don't care if its a stock restart. I just need to know how to identify which backup I would need for my particular phone?
Click to expand...
Click to collapse
Nevermind, figured it out. This seems promising, I'll reply with results once I've tried it. File is downloading at the moment.

CryloRends said:
Nevermind, figured it out. This seems promising, I'll reply with results once I've tried it. File is downloading at the moment.
Click to expand...
Click to collapse
success?

lamahgra said:
success?
Click to expand...
Click to collapse
Sorry, its taking some time to sort it out because the only SD card I had access too was my dads and it wouldn't let me format it when I plugged it into my laptop with an adapter, now it doesn't work in my dads phone or my laptop so I'm buying a new one as soon as I can, will let you know once I've tried that..

lamahgra said:
success?
Click to expand...
Click to collapse
Success. Can't tell you how much I appreciate your suggestion, after the first hitch of the bloody SD Card failing on me I got a new one and it all worked smoothly, 0 problems at all Thanks so much!

Stuck in bootloop, unable to get to recovery or get computer to recognize....

Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!

butneveragain said:
Hi all,
My m8 is rooted, with CWM. I was having issues with it, so I decided to wipe it and flash the marshmallow GPE update to see if that would help (since my OTA alert was there). However, it's now stuck in a bootloop, and I can't get into recovery, or get a computer to recognize it.
If I hold the power and volume buttons down, it will restart, I can get the white screen with HTC logo and red writing stating the build is for development purposes only, but after that it goes right to the loading screen again, instead of going into recovery like it normally would (and like it's done a thousand times for me in the past). I'm not the techiest person, but I thought I'd done enough research on this to do it properly.. apparently not I've tried everything I (and google) can think of, but everything seems to rely on getting to recovery to flash a new rom/wipe the cache/etc or hooking it up to a computer, neither of which I can do. Do I have any other options? This is a "new" phone (bought it refurbished from tmobile to replace my old m8 which I also had issues with... obviously a bad choice), and the thought of buying a new phone again just really kills me. Any help would be SO greatly appreciated. Thanks!
Click to expand...
Click to collapse
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!

xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!

butneveragain said:
You are a lifesaver! Didn't even think about trying to switch from volume up to down, but that did it.
Ok, so now I have TWRP, but my OS was definitely NOT 6 (it was 4.something). I assume that was one of my issues? Honestly, at this point, I just want to go back to stock lollipop, like I had before.. I bounced around a few stock marshmallow roms before my bootloop (realized I hated GPE, that HTC transfer didn't support my device on those versions, CWM wouldn't restore any of my backups--which now makes sense, etc), so I think I just want to quit messing with it at this point and count my blessings. I've had issues finding stock roms though, obviously. Could you point me in the right direction? I just want stock tmobile lollipop, with sense. I didn't think it'd be so difficult, but I'm clearly not very up-to-date on this stuff. Thanks SO much again!
Click to expand...
Click to collapse
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!

xunholyx said:
Okay. 4.xx firmware will actually work with 6.xx ROMs, but I'll instruct you on getting back to stock lollipop.
Backup anything important to you, such as photos and stuff, because this is going to wipe your phone. Don't worry about the apps. Google takes care of that for you. You might lose a little data from the apps, but if you want to be completely stock, this will do it. (you will probably get a prompt to update to Marshmallow via OTA eventually afterwards, but it will be the official stock version of it)
Also, this is assuming that you are T-Mo US, not a European T-Mo version.
Download this RUU onto your PC.
When the download if finished, hook up your phone and get into fastboot. You'll have to re-lock your bootloader first. The command is fastboot oem lock, then fastboot reboot
After you have re-locked your bootloader, double click on the RUU download and follow the prompts.
If there are problems with the RUU flash, try again while booted to bootloader. Sometimes that is needed for some reason.
That's it. You are now on stock T-MoUS 4.20.531.4
Good luck!
Click to expand...
Click to collapse
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?

butneveragain said:
Thanks so much. I still have everything backed up from before (well, my CWM nandroid is useless now, but I'll live). I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them. I'm S-ON--is that a problem?
Click to expand...
Click to collapse
No it's not a problem, and something that I have already assumed.
If you were S-Off, you wouldn't need to re-lock your bootloader before running the RUU.exe
Those "some people who were saying" are incorrect.

butneveragain said:
I read about the RUUs originally when I was trying to get the stock rom, but some people were saying you had to be S-OFF for them.
Click to expand...
Click to collapse
Yeah, people need to stop saying that. Its completely false. RUU is an official HTC recovery tool, and its intended to work on stock (s-on) devices.
You only need s-off to flash RUU as unintended by HTC, such as:
- flash an older version RUU than what is on the phone ("downgrade")
- Change CID/MID to flash another version's RUU
- Flash RUU with unlocked bootloader
- Flash a hacked/unsigned RUU

xunholyx said:
One big problem with what you are doing is you are using CWM. That recovery hasn't been maintained in about two years now. It's obsolete. You need to flash the latest TWRP instead. Also, you should make sure your firmware is up to date. You can find that in your bootloader listed under "OS"
Let's get you out of your bootloop first.
Hold down power + vol up until your phone reboots. AS SOON AS THE SCREEN GOES BLACK switch from holding vol up to vol down. This will take you to your bootloader. Check your OS version. It should be 6.xx.xxx.x
Now that you are in bootloader, flash TWRP with fastboot.
When that is done fastboot reboot-bootloader and go to your phone. Navigate to hboot on the bootloader menu, and you will have the option to boot to recovery. Flash the ROM again, and all should be working for you.
Go to this link to get TWRP. The downloads for the M8, and instructions on how to flash it in fastboot are all there for you.
Good luck!
Click to expand...
Click to collapse
My phone is stuck on boot screen... How can I turn off the device if my vol+ button does not work?