Develop Bugs

Brand new One. Can't get any ROMs working.

I got the bootloader unlocked. I flashed TWRP. I installed SuperSu. Now after wiping and installing a new ROM, I can no longer get passed the HTC logo at all. I have tried multiple ROMs including Eragon ROM, Skydragon, and Viper. I really have no idea what to do at this point. Please help. If you need more info just ask. I am able to get into bootloader and TWRP but nothing I have tried has worked. This is the AT&T variant.
Edit: I've also just tried using a different recovery as well (Philz).. no luck.

the only time i had this happening with the M8 was when i forgot to do a full wipe before flashing, then got stuck with the logo. Are you absolutely sure you're performing a full wipe prior to flashing (daft Q i know).
Maybe it's something to do with TWRP? I'm using PhilZ Touch (simply because that it was recommended on the skydragon thread).
Can you restore the original ROM from a backup?

westy123 said:
the only time i had this happening with the M8 was when i forgot to do a full wipe before flashing, then got stuck with the logo. Are you absolutely sure you're performing a full wipe prior to flashing (daft Q i know).
Maybe it's something to do with TWRP? I'm using PhilZ Touch (simply because that it was recommended on the skydragon thread).
Can you restore the original ROM from a backup?
Click to expand...
Click to collapse
Yes I am doing a full wipe before install. This is incredibly stupid of me and you can all make fun of me for it but I didn't have a backup. I am coming off of an M7 and never had issues with it so I figured it was fine. Guess I was wrong. . I thought it came with a backup stock but there is not one.

What's your hboot no. on the bootloader.
All these ROMs require no lower than hboot 3.19.0000

ckpv5 said:
What's your hboot no. on the bootloader.
All these ROMs require no lower than hboot 3.19.0000
Click to expand...
Click to collapse
That could be it then. Says I'm on 3.16.0.0000. So I'll have to be S-Off and update my firmware then to get any ROMs working?

Seltioasa said:
That could be it then. Says I'm on 3.16.0.0000. So I'll have to be S-Off and update my firmware then to get any ROMs working?
Click to expand...
Click to collapse
I'm not familiar with AT&T variant. The last info that I know they have RUU for 4.4.4, not sure about lollipop.
If you have plan to S-Off your device, with hboot 3.16.0000 you have better chance to do it with SunShine.
Once you updated your firmware, the chance to S-Off is slimmer.
Either you browse thru AT&T forum for info or maybe @redpoint73 can assist you here.

Seltioasa said:
That could be it then. Says I'm on 3.16.0.0000. So I'll have to be S-Off and update my firmware then to get any ROMs working?
Click to expand...
Click to collapse
Depending on the ROM, most of them require a particular firmware (which contains hboot, radio, WiFI, media moduels and others), not just the hboot.
You can update to 4.4.4 firmware by RUU (relock bootloader since you are s-on). Backup any personal data first, as RUU will wipe the phone.
Once updated to 4.4.4 firmware, you can run any ROM that supports that firmware. If you want a ROM that requires 5.0 firmware, you currently need s-off to manually (by "unofficial" means) update the firmware; until AT&T releases official 5.0.
Yes, its confusing and you can blame HTC for the firmware complications.
RUUs are linked in my (AT&T specific) index thread: http://forum.xda-developers.com/showthread.php?t=2751432

[Q] Lost root access after flashing new firmware

Hi All,
I have a UK HTC One M8, rooted, S-off, and with ViperOne installed, an old version - 1.8.0
I have flashed a new firmware in order to update ViperOne, and I have lost root access. I used root checker app to verify.
I used this method to flash the firmware:http://forum.xda-developers.com/showthread.php?t=2696282
I obtained the firmware from here: http://android-revolution-hd.blogspot.co.uk/p/android-revolution-hd-mirror-site-var.html
I had changed the cid to supercid, as I am S-off, and i checked that the modelid was correct in "android-info.txt"
The flash went fine, no errors, phone turned on first time, but root access is lost.
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
I was wondering if somebody knowledgeable could reassure me that everything is fine, and perhaps point me to the most appropriate method for getting root access back. I am a little out of my depth here, I learned how to do most of this stuff a year ago when i first rooted, but I haven't been back to update since then, and have forgotten a lot of what I learned before.
Would appreciate any assistance you can offer
Cheers
Will

Willr01 said:
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
Click to expand...
Click to collapse
Different device manufacturers do things in very different ways, so I wouldn't take that thread to mean anything, one way or another, regarding losing root when updating firmware. I also think in that thread, they may be talking about firmware = ROM (as opposed to something very different on HTC devices). In which case, yes, installing a stock ROM will in fact usually remove root on most Android devices.
In any case, see if you still have TWRP installed. That depends on whether the firmware package was modified or not to remove the stock recovery. If TWRP was replaced by stock recovery, simply install TWRP again using your method of choice (personally I prefer installing by fastboot). Then download the SuperSU zip to your phone from here and flash in TWRP.
In reality, I think you may not even have to download SuperSU. If you boot into TWRP and select reboot, I believe TWRP will automatically sense your ROM is not rooted, and ask you if you want it to do so. But I'm not 100% on that, and the SuperSU method is a sure thing.

Thanks a lot for your input. I don't have a recovery installed, so I have tried to flash twrp.
I tried flashing it twice, after reading it can be necessary to do that, and erasing the cache before attempting to boot to recovery. When I try and enter recovery, I get stuck on the startup htc screen with "Entering Recovery..." in pink.
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Thanks in advance

Willr01 said:
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Click to expand...
Click to collapse
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.

redpoint73 said:
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.
Click to expand...
Click to collapse
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?

Willr01 said:
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?
Click to expand...
Click to collapse
What exactly did you flash from the Android Revolution website (what you linked in the top post)?
That website has up-to-date firmware, but what you want is 4.xx version firmware, found under the "Firmware collection" link on that webpage.
Since your hboot number is 3.16, you either did not properly flash a firmware (flashed something else) or flashed a really old firmware (hboot 3.16 corresponds to firmware version 1.xx).

[Q] bootloop on every reboot

Every time i reboot phone i get stuck in bootloop , i have to wipe cache and dalvik cache to fix this . Fixed permissions in recovery, reflashed ROM , the problem still persists. Changed ROM . the problem is still there. I was using the same ROM before , didn't have this problem before , appeared out of nowhere.
Using Insertcoin ROM currently , ElementalX kernel.
Please help.

Anyone?

Did you attempt a factory reset while running a non-stock recovery?
If so, you need to put the stock recovery back on, let it complete the reset, then put your desired recovery back. This is true even if you are using a non-stock ROM.

jshamlet said:
Did you attempt a factory reset while running a non-stock recovery?
If so, you need to put the stock recovery back on, let it complete the reset, then put your desired recovery back. This is true even if you are using a non-stock ROM.
Click to expand...
Click to collapse
No i didn't attempt factory reset from within the ROM when using non-stock recovery.
But i will flash stock recovery back to check on this issue , Thanks.

It seems your boot files are crashed, try to flash boot.img
Sent from my HTC One using Tapatalk

Not nearly enough info:
1) What hboot, radio number?
2) What OS number (on bootloader screen) or main version (on getvar all)
3) What version InsertCoin you trying to flash? What other ROMs and version?
4) What version TWRP?

redpoint73 said:
Not nearly enough info:
1) What hboot, radio number?
2) What OS number (on bootloader screen) or main version (on getvar all)
3) What version InsertCoin you trying to flash? What other ROMs and version?
4) What version TWRP?
Click to expand...
Click to collapse
Insertion 7.1.8 (ON 5.0.2 LOLLIPOP)
Build number - 4.16.401.10 CL448934
M8_UL PVT SHIP S-ON
HBOOT - 3.19.0.0000
RADIO - 1.22.213311491.08G
OPENDSP - V46.2.2-00564-M8974-FO.0811
OS - 3.32.531.2
TWRP VERSION - 2.8.7.0
i guess there is a firmware mismatch.
This is originally a t-mobile version of M8 but it is sim-unlocked and i flash international version of any rom i flash. I also have no GPS Lock problem (might get fixed because of firmware? Tried everything FasterGPS, GPS status and Toolbox, no fix)
Being S-ON, i want to upgrade the firmware. How can i do that?
Can you explain to me in steps.
I've searched and have gotten really confused in these things like -
What RUU should i download (t-mobile or international?) and in what order should i do steps like relocking bootloader and stock recovery.
Need the solution in proper steps.
Thank you.

rahulsethi said:
i guess there is a firmware mismatch.
Click to expand...
Click to collapse
Firmware mismatch is your problem, as indicated by your radio number and OS number (on bootloader screen) which both correspond to Kitkat (Android 4.4.4).
rahulsethi said:
I also have no GPS Lock problem (might get fixed because of firmware?)
Click to expand...
Click to collapse
Most likely, yes.
rahulsethi said:
This is originally a t-mobile version of M8 but it is sim-unlocked and i flash international version of any rom i flash.
Being S-ON, i want to upgrade the firmware. How can i do that?
What RUU should i download (t-mobile or international?) and in what order should i do steps like relocking bootloader and stock recovery.
Click to expand...
Click to collapse
You need to use the T-Mobile US RUU (available here).
You can only run an RUU that matches your phone's carrier ID (CID) and model ID (MID), which in your case correspond to T-Mobile US. CID and MID can only be changed with s-off (have nothing to do with the ROM your flash).
What you want to do is:
1) Backup any personal data you want to keep (RUU will wipe the phone, including internal storage).
2) Relock the bootloader with command: fastboot oem lock
3) Connect phone to PC and run the RUU (its very self explanatory, just follow the prompts). Your firmware is not updated, and you are on the stock T-MOB Lollipop ROM, and stock recovery.
4) To get back to InsertCoin, unlock the bootloader again using the HTCDev.com website.
5) Flash current version TWRP in fastboot.
6) Flash InsertCoin.

Stuck in boot loop after flashing superSU (Marshmallow)

Hi all, I am playing around with an HTC m8 to decide if I should use it as replacement of my Nexus 4 (so far, too big and heavy ).
But well, I unlocked the phone and installed TWRP. All worked fine, but then I flashed supersu and I'm stucked in a boot loop. I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM as I don't know what´s the phone model. It says M8_UL in fastboot...
I´m looking at this but not sure if this phone is gpe.
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Any ideas?
Thanks!

1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.[2].56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.[2].56 zip
5. You should boot if you were booting before flashing TWRP.
EDIT: corrected SuperSU version.

spideyngo said:
1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.1.56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.1.56 zip
5. You should boot if you were booting before flashing TWRP.
Click to expand...
Click to collapse
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,

frozst said:
I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM
Click to expand...
Click to collapse
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Click to expand...
Click to collapse
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.

frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,
Click to expand...
Click to collapse
EDIT: SuperSU version 2.56. Sorry about that.
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop. You may need to flash a rooted stock ROM to repair booting. S-off not needed, but makes your life easier.

Thanks! the problem was the old SU version, solved now and testing different ROMs. Any recomendations?

spideyngo said:
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop.
Click to expand...
Click to collapse
Hadn't heard that. I wonder if its a known issue experienced by others? If so, I'll fall back to my previous recommendation to use 2.65, which was the former "latest" STABLE version; and no complaints that I am aware of.

Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?

kbytes said:
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
Click to expand...
Click to collapse
This forum is for the M8, any advice you get may not be correct. Post in the M9 forum.
But what I can say, is if you say "several version" SuperSU is not specific enough (when you post to the correct device forum). Be specific as to what version numbers you tried. Nobody can help, if you don't give the proper info to see what you did wrong. In particular, you need to provide info on what Android version your phone is currently on, what TWRP version, what SuperSU version(s) you tried.
But again, post to the M9 forum, not here.

Stuck on HTC Screen.
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?

weismanak said:
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
Click to expand...
Click to collapse
You probably used an old version TWRP and/or old version SuperSU.
TWRP 3.0.2 and SuperSU 2.76 is recommended.
Hold power+vol up for a minute or so, to force a reboot. Once the screen goes dark to reboot, let go of the buttons, and only hold vol down. Don't let go of vol down, until you are in bootloader. If the phone just gets stuck on the logo screen again, you just got the timing wrong; either didn't start pressing vol down soon enough, or let go too early. Just repeat the process, until you get to bootloader.
From there, restore TWRP backup (which you should always make before attempting to root) and try again, with the proper versions TWRP and SuperSU.
If no TWRP backup, flash proper version TWRP in fastboot, then get proper version SuperSU to the phone (adb push, or put the file on SD card).

Still stuck in boot loop... but different place.
Whew!! OK, so I got past that hurdle (Thank you so much). I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. The phone is now stuck at the bootloader. If I select "Recovery" it simply comes back to the "Fastboot-usb". I've attached a screen shot (maybe) to demonstrate what I'm seeing on the phone.
*** Software status: Modified ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
Open DSP-v56.2.2-00593-M8974_FO.0126
OS-6.20.502.5
eMMC-boot 2048MB
Apr 14 2016,19:39:46.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
Thanks for all your help, I'm a noOb to this process. Recent convert from iOS.

weismanak said:
I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. .
Click to expand...
Click to collapse
Meaning you used the TWRP version and SuperSU version included with the toolkit? If so, that toolkit hasn't been updated in a long time, and likely is not using the versions TWRP and SuperSU that I specified previously.
Additionally, I don't personally recommend using such toolkits. Doing so robs you of a valuable learning experience, and therefore guarantees that you stay a n00b. Also, the toolkits constitute an additional point of failure (even when they are updated) that is not necessary. I've often seen processes fail using the toolkits, when the exact same steps complete just fine if done "manually".
Since it appears you've successfully unlocked the bootloader (can be verified if it says UNLOCKED near the top of the bootloader screen), than I would advise:
1) Manually flash TWRP 3.0.2 with fastboot using the instructions here: https://twrp.me/devices/htconem8gsm.html
2) Download SuperSU 2.76 from here, and put it on SD card (alternately, adb push to phone - but that may be a bit complicated for you).
3) Boot into TWRP, under Install, navigate to the SuperSU 2.76 zip, and flash it.

redpoint73 said:
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.
Click to expand...
Click to collapse
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2

ajay vadaparthi said:
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
Click to expand...
Click to collapse
have you flashed the latest supersu.zip ?
does the flashing process ended with success ?
you may try to enable root in developer options and see
also you are in the wrong forum
Sent from my HTC M8 using XDA Labs

Can I re-flash SuperSU over an existing one?
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.

tigarstyle said:
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.
Click to expand...
Click to collapse
your first post in the wrong forum this forum for m8 )
if you can flash a rom then flash it,will save the hassle of flashing RUU
and you used an outdated version of supersu ( i don't know if this will fix it but try to flash the latest version on top the older )
you can rename the RUU to 0PJAIMG.zip and put it in the sd card root ( formatted as fat32 or exfat , 3.xx can flash RUU from exfat cards ) then reboot to download mode and follow the instruction
if you have any question ask in the m9 forum as you may get a wrong answer here :silly:

Thanks a lot. I didn't realise this forum was for M8 only, my mistake. I've now posted in the correct forum.
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked. I guess I'm lucky that I have a connection with the PC as I can see the internal storage of my device still and I still have access to TWRP.
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program? Just thought it might be worth sharing for anyone who is on M8 and stuck on the HTC One splashscreen like I am.

tigarstyle said:
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked.
Click to expand...
Click to collapse
If the phone was hard bricked, you wouldn't be able to flash anything. The screen wouldn't come on at all. A hard brick means you need to open the phone to repair it (new motherboard or JTAG, at a minimum). You don't have a hard brick.
Do you mean to ask if flashing the proper SuperSU would brick the phone (if its safe to flash)? If that is the question, you best direct it to folks knowledgeable to the M9. On the M8, its fine to flash the newer SuperSU (and the proper fix after flashing obsolete SuperSU). But that doesn't meant the M9 is the same. And following advice meant for another device can possibly damage the device.
tigarstyle said:
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program?
Click to expand...
Click to collapse
Nowhere in any instructions for flashing RUU.zip will you see anything about extracting files from the RUU.zip.
Therefore, don't do it.
The file is encrypted and signed. Even if you were able to extract anything, you wouldn't be able to flash it with s-on (s-on can't flash unsigned RUU zips).

Excellent, thank you. I was wondering why the zip file wouldn't extract on the PC. I saw videos explaining that in other to get to Stock ROM, you'd do it via the RUU.zip. So when I downloaded the RUU.zip Stock ROM file, I thought I had to extract the zip in order to get to the application, then flash the device.
Thanks for taking the time out to explain in detail...much appreciated.

HTC One M8 Blocked on reboot after root

I wanted to root my HTC One M8 to uninstall unnecessary applications. I describe the procedure that I survived:
1- I unlock the HTC One M8 bootloader
2- I installed the CWM Recovery: recovery-clockwork-6.0.4.8-m8.img
3- I proceeded to the root with UPDATE-SuperSU-v2.46.zip
And at restart it's where everything gets complicated. It remains stuck on the logo of the boot and can not restart anything. I left for more than an hour to see but nothing moved.
I managed to enter bootloader by associating the volume + and Power key to restart, and when the phone turns off before restarting I do volume- and power.
And the I'm stuck I know more manipulation to make my HTC one M8 work again.
Is the phone ****ing kind unrecoverable?
How to recover my phone?
Help me please

The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).

redpoint73 said:
The files (custom recovery and SuperSU) you used are horribly outdated. Unless your current firmware is something like Kitkat, the stuck on boot situation is expected.
Additionally, CWM never officially supported this phone, and that in itself may cause some problems (in addition to being outdated as well).
Correct versions depends on your current firmware number. Most folks (but not all) are on Marshmallow at this point. But you can tell us more by posting what it says for OS number on the bootloader screen. Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
But likely, you should use a TWRP version 2.8.7 or later. And SuperSU 2.79 or later. Or Magisk to root (latest is 13.3, which should work).
Click to expand...
Click to collapse
Yes indeed I had chosen the wrong files (custom recovery and SuperSU). The phone was on Marshmallow. I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow. But before I have installed last version of TWRP. After installing my rom stock, I installed stock recovery and I relock the bootloader.
thank you for your help

Koukougnon said:
I opted for a simple solution: to install a stock rom Android Jelly Bean 4.4.2 and wait for the update Marshmallow.
After installing my rom stock, I installed stock recovery and I relock the bootloader.
Click to expand...
Click to collapse
I don't think this will work. Your firmware indicated by OS number (in bootloader, not in OS Settings) will still read as updated (MM) and you won't be prompted to update.
Additionally, just as FYI, it is not necessary to relock the bootloader for an OTA update, only for RUU or flashing stock signed firmware.
Stuck on HTC logo screen due to old version TWRP and SuperSU, can often be fixed simply by using the proper updated files. But in the current condition, you will need to unlock the bootloader again. In light of that, it might make sense to restore by RUU (if you version has one - you haven't provided the info requested) or otherwise restore to MM (so ROM matches your firmware) before trying to root again.

Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
I am sending you the information you requested:
OS number on the bootloader
*** Software statut: Modified ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8674_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:48.0
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.29.214500021.12G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.401.4
INFOversion-misc: PVT SHIP S-ON
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 76df2b54
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.024s
I still have the TWRP installed and unlock bootloader
Can you help me?

Koukougnon said:
Excuse me for my absence. I need your help.
As I said earlier, I opted to go back to a Stock ROM.
Actually as you said, I can not install the update to Marshmallow. It downloads the update but it crashes at installation.
Click to expand...
Click to collapse
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
Koukougnon said:
I still have the TWRP installed and unlock bootloader
Click to expand...
Click to collapse
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.

redpoint73 said:
No surprise there. It's best you follow the advice given, instead of making up your own solutions, unless you really know what you are doing. This device has a lot of nuances, and what seems like common sense or a simple solution, often doesn't apply.
OTAs will not install on this device with TWRP, but rather require stock recovery. But it probably doesn't matter, as I stated before, since you are trying to load an update (ROM + firmware), when the firmware is already updated (even if the ROM is not updated), it will likely not install. Basically you have mismatched components, and this will prevent the update from installing. ROM is older, but firmware is updated (version main in getvar indicates firmware is Marshmallow 6.12.401.4).
What version TWRP? You mentioned before the "latest" but did not give a version number. I've had a lot of cases where folks thing they have the "latest" but when prompted for specific version number, it turns out to be an old version.
Just want to be sure before we proceed. After all, the other files you used are going on 3 years old.
Click to expand...
Click to collapse
I had installed a stock recovery and relocked the bootloader after installing the rom stock. I received an update for Marshmallow but that crashed at the installation.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
So I reinstalled the rom stock Jelly Bean 4.4.2. That's why I have the TWRP installed and the bootloader unlocked.

Koukougnon said:
.
After I wanted to install a Rom Custom Nougat for HTC M8, so I unlocked the bootloader, installed TWRP (version twrp-3.1.1-0-m8) then root with SuperSU (the SR1-SuperSU-v2 version. 82-SR1-20170608224931). I installed the rom that no more.
Click to expand...
Click to collapse
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.

redpoint73 said:
I'm not sure what that means (what the problem was after flashing the custom ROM). You may have some words missing/wrong in the last sentence.
Flashing the custom ROM should work (seems that it was the real goal here). Did you also flash gapps (Google Apps) which is normally required for AOSP type ROMs? This (or trying a different gapps) is a frequent cause for an AOSP ROM not booting after flashing.
If you still want to return to stock, restore the stock TWRP backup from the collection, using the instructions and files on the following thread. Only need to do through Step 9, and reboot: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, keep in mind best practice is to make a TWRP backup of your stock ROM, before trying to root of flash a custom ROM. If you did that, returning to stock would have been as easy as restoring the backup you made.
Click to expand...
Click to collapse
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
And I did not backup either the Rom Stock or the Custom Rom.
That's why I installed the Rom Stock 4.4.2 again
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed

Koukougnon said:
The problem I had with the Custom Rom was that I could not see my Sim contacts. It was a Rom Mokee 7.1.2 for HTC M8.
Click to expand...
Click to collapse
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
Koukougnon said:
Can I install a RUU for HTC M8?
I found this zip file : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.

redpoint73 said:
The description of events that got you to the current condition, gets more and more convoluted every time you post.
Not critical in this case (returning to stock is fairly simple, and doesn't rely that much on the history). But for other issues, conveying the information this way could be a real problem for those trying to help you.
You can. It would require relocking the bootloader. Then if you want TWRP, root or custom ROM, you will need to unlock the bootloader again after RUU. RUU will also wipe all data on the phone.
Must flash with SD card method, or using htc_fastboot
Not gaining much versus what I previously recommended, especially if you want to still have TWRP for root, custom ROM, etc.
Click to expand...
Click to collapse
I understand I was wrong at first to solve my problem. I got into that. I did not think well before applying the solutions. Thank you for your help.
So, if I understood correctly to flash the RUU,
- relocked the bootloader
- to be S-ON
- flash by SD Card or Fastboot
Should I install a recovery stock before relocking the bootloafer?

My comments/responses below in red font:
Koukougnon said:
So, if I understood correctly to flash the RUU,
- relocked the bootloader yes, using fastboot command: fastboot oem lock
- to be S-ON It's not a requirement to be s-on, but it's your current condition. With s-off, the requirement to lock the bootloader is bypassed (and RUU still works).
- flash by SD Card or Fastboot Either SD card method, or htc_fastboot specifically. Trying to use the "generic" fastboot will fail since the RUU file is too large. IF you need further info, see here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Should I install a recovery stock before relocking the bootloafer? NO. It's not needed when doing RUU.
Click to expand...
Click to collapse

I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens. But I intend to install the TWRP.
Thank you for your help.

Koukougnon said:
I managed to flash the RUU with your advice. Everything works well.
The only problem is the recovery. When I go into the recovery it shows me a red triangle and nothing happens.
Click to expand...
Click to collapse
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
Koukougnon said:
Thank you for your help.
Click to expand...
Click to collapse
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.

redpoint73 said:
That isn't a "problem", it is working as it should. It's the stock recovery. Press vol up and tap the power button to show the recovery menu options (although not much you can do in stock recovery).
You're welcome. Please click the "Thanks" button for any post you found helpful.
Some advice and "best practices" as it seems that you've missed a lot of important info when trying to mod the phone:
1) Always research the most up to date info on rooting a device, before you start anything. Files are updated often, and using old methods can (and will) lead to a lot of problems. I know a lot of the info for this device is outdated, or not entirely organized. So feel free to ask questions if you are confused.
2) Always make a TWRP backup of your stock ROM, before doing any mods (root, custom ROM, etc.).
3) Always know how to return to stock, before doing the mods.
4) At least for this device, after installing TWRP, you don't need to root, if you are then going to immediately flash a custom ROM. In other words, you don't need root to flash a ROM. Most ROMs are pre-rooted But the few that are not, you need to flash root (SuperSU or Magisk) after you flash the ROM.
Click to expand...
Click to collapse
I understood well. Thank you.