Develop Bugs

[Q] New One M8, old HTC user: Need help understanding a few things

Hello All,
So I recently bought a M8 and I just need some help in getting the steps nailed down correctly. Be warned long post with lots of questions...
Code:
fastboot getvar version-main
version-main: 3.32.111.3
fastboot oem readcid
(bootloader) cid: T-MOB101
That is basically my device, now due to it being 4.4.4 from factory I am unable to use Sunshine & Weaksauce. I could wait until the new year but why
bother .
First step:
Get my factory firmware image after reading this thread: http://forum.xda-developers.com/showthread.php?t=2701376 due to it being a T-Mobile and
Germany and 4.4.4 I am unable to run the command listed there to get the stock recovery, so how do I get the stock recovery for my device? @BerndM14
Has provided me with a link to download the latest firmware for my device but it has the TWRP recovery inside it, link is this one: http://www.handy-
faq.de/forum/htc_one_m8_custom_roms/304821-htc_one_m8_firmwaresammlung_ruus_otas_backups.html#post2832636. I should point out that I do have a OTA
waiting to download and install, should I download and install it? The version listed on the screen is 3.32.111.9 and is only 183.73MB. Would it have a
viable stock recovery? Can I downgrade to a older version for the stock recovery?
Second step:
Once the above is done and dusted my next step is getting root & S-OFF & custom recovery. This is relatively simple because all I need to do is visit
HTCDev, unlock and then S-OFF with Sunshine and then a custom recovery. Correct? Sounds and looks simple enough.
Third step:
Download ROM of choice and flash away. So I am going with InsertCoin due to user loyalty from the Desire days . However I see people in the thread
mentioning that they flashed the latest firmware to sort out a couple of issues, I take it they mean the ROM file and not HTC firmware?
Fourth and probably not needed step:
Changing the phone to WWE and SuperCID? Do I really need to do this? Benefit of changing to WWE is changing the HBOOT to a more universal one? The
reason why I am thinking of converting is because I would want to get rid of the red text on the boot screen as listed here: http://forum.xda-
developers.com/showpost.php?p=51744965&postcount=1 however for T-Mobile Dutch the HBOOT CIDS are T-MOB003, if I flash that would it cause a problem?
I would also be looking at running the commands to change the flags showing tampered and unlocked but that looks simple to do. Am I missing anything? For warranty purposes I would use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2710735 but download the recovery file for T-MOB Germany instead?
Thank you for reading the long post and I hope that I have made some sort of sense.

Yes it will have the firmware.zip with the recovery.img inside it. Even the small 47MB or so, OTA update for the WWE from 2.22.401.4 - 2.22.401.5 had the firmware.zip inside. So just download the OTA.zip copy to PC extract firmware.zip and grab the recovery.img.
Benefits to converting to WWE or even Developer edition also includes the fact that those devices will receive OTA updates before any carrier version, directly from HTC. It's a bonus if you're into the "latest & greatest" scene.
As for making a backup before flashing custom recovery, have you tried booting the custom recovery? Philz will probably be better if you want to use the booted custom recovery to make a backup of stock recovery. You could also try and boot either TWRP or Philz and see if you can root your device without flashing custom recovery, that way you can at least use the dd command to grab a copy of the recovery block. <My preferred method, though it's a terrible circle. Need to flash custom recovery to root, need root to make backup of stock recovery... So hopefully booting the custom recovery will work. That being said, easiest way still remains to grab it from the OTA.zip.
Perhaps you could even upload a copy of the OTA.zip and share it on here, I don't think the OP has a copy in the second post
ROM/Firmware. You need the latest firmware to run the latest ROM. For most it'll be firmware with 3.x. If you still run on 2.x(which you aren't) you'd have some problems with radio(bluetooth, gps, wifi, data etc)

Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)
Click to expand...
Click to collapse
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .

Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
Hm, yeah I also had some problems booting a recovery, but I just tested it out again. I can at least boot TWRP version 2.8.3.0 so it still works for me. I'm on 3.28.1540.5 (Developer edition). Haven't tried Philz though, net a bit too slow to bother with even a small download

No problem. I am busy downloading the OTA.zip and once complete I will try the toolkit method and see what happens . Again, thank you for the reply.

I need some help... My phone seems to be stuck in fastboot mode and is not picked up in Device Manager of Windows. I can touch the fastboot screen and it vibrates but it does not nothing. I have held down the power button for 20 seconds with no result. I had just unlocked the bootloader and then tried pushing the Philz recovery image to the device with the command line:
Code:
C:\android\sdk\android\platform-tools>fastboot boot philz_touch_6.57.8-m8.img
downloading 'boot.img'...
OKAY [ 1.541s]
booting...
OKAY [ 0.002s]
finished. total time: 1.547s
*edit*
Holding volume up + power for 10 seconds helped *whew*...

Anakha56 said:
Thank you for the reply .
To be honest I have not tried booting a custom recovery because I saw this in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2701376
So I am not sure what to try to be honest. This toolkit: http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278 mentions getting root without S-OFF but with a unlocked bootloader. So I am thinking that if I follow those steps, maybe when I get to the reboot phase I can execute a nandroid instead which might get me the files I want?
I won't bother with WWE then. I will rely on the dev's to give me the latest & greatest .
Click to expand...
Click to collapse
You don't need S-Off to root, just the unlocked bootloader, custom recovery, and superuser.

@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?

Anakha56 said:
@xunholyx Thanks for the post . I am trying to get an image of my stock recovery file first, so I am trying to avoid flashing the custom recovery right now . BTW Does anyone know if TWRP makes a backup of the stock recovery before overwriting it like Philz does?
Click to expand...
Click to collapse
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832635
oops sorry.. i see you already been their
your hboot 3.19 will prevent booting to recovery ... and no TWRP doesn't backup stock recovery
you just need to find the OTA.zip for your version it must be out their somewhere

@clsA I have the file
3.32.111.3 - TWRP
Click to expand...
Click to collapse
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
boot.emmc.win
boot.emmc.win.md5
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
Click to expand...
Click to collapse
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?

Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
it should work, recovery does not have to be exact just close
and the file you have doesn't include TWRP .. it was created with twrp ... big difference

Anakha56 said:
@clsA I have the file
From that site but its recovery is TWRP. I am trying to grab the stock recovery currently on the device before going forward. When I unzip that file it has 6 items:
I have downloaded the OTA that is ready for my phone but I had hit a snag. The file was corrupt, on redownload I have the small OTA but the recovery version number has incremented past mine, I don't know if it will be still useable with the ROM file from the link?
Click to expand...
Click to collapse
You can use any 3.32 based stock recovery for your phone. There are plenty of backups for that on this thread. No need to backup your own.

Thank you guys! That helps me a lot! Off I go to flash a custom recovery .

[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).

HTC One m8 Deleted OS & Deleted Backup on internal storage

Hi
hope any can help with the issue i am facing, simply i deleted my os & the back up file while trying to flash a rom
all i can access now is twrp recovery screen, i tried flashing a couple of custom rom with no luck
my device is HTC one M8, it was rooted but i don't think it is anymore since it says that i don't have su installed
excuse my lack of android knowledge, as i am new to this whole thing
thanks for reading and any help is appreciated

I never fail to be frustrated at the nearly countless reports here of "I deleted everything on my phone and now its stuck".
If you lack knowledge of Androids mods, the proper way to proceed is to familiarize yourself and understand what you are doing before doing it. The absolute wrong thing to do, is to delete things without knowing what the result will be, and not knowing how to revert from that condition. Plus, the default wipe (user data, cache and Dalvik) on TWRP clearly states that "most of the time, this is the only wipe you need". It says this for good reason, and the additional wipe options are labelled "Advanced" also for good reason. So there were a couple warning signs against doing what you did, that you chose to ignore.
You didn't specify what ROMs you tried (makes it hard to help) and whether you put those on the phone before you wiped the OS; or if you know how to put ROMs on the phone in the current condition (using adb push, or removable SD).
Also, missing some key info:
1) hboot number
2) OS number on hboot screen (or main version as determined by adb getvar all)
3) CID (carrier version) of your phone
4) S-on or s-off
5) What version TWRP

while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.

ashypanda said:
while in TWRP, plug your phone into a computer and under mount you mount the phone as USB, and you copy over a ROM zip, and you flash it as you would normally. that should have fixed it.
Click to expand...
Click to collapse
While your advice is generally true, the specific ROM (or TWRP version) may part of the issue. OP will need to be careful to flash a ROM that supports his current firmware (hboot, radio, etc.) otherwise he may have some serious problems.
The fact that he said he tried a few ROMs that didn't work, leads me to believe he either has old firmware, or old TWRP.
OP should provide the info I requested in my last post, so we can more specifically help.

thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance

ahmed.abdelradi said:
thank you for your assitance
1) hboot number:3.16..0.000
2) OS number on hboot screen: nothing apears next to OS on Hboot screen
3) CID (carrier version) of your phone-HTC__j15
4)s-off
5) What version TWRP: 2.7.0.2
hope this info helps
please advise me which rom to use as i am totally lost here
sorry if i caused any disturbance
Click to expand...
Click to collapse
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.

redpoint73 said:
To bring your phone up to date, you can flash the 4.16.1540 firmware posted here. Then update to TWRP 2.8.7 (flash in fastboot), then flash most any current ROM for the M8.
Another option you can flash an old Android 4.4.2 ROM based on software version 1.xx (1.12, 1.54, etc.) to match your old firmware. But in this case, don't update to the latest TWRP before doing so, as it won't work with hboot 3.16.
Click to expand...
Click to collapse
Personally, I would rather go with a "combined" firmware, such as the ones provided here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Mike's firmwares are incremental afaik (pulled from the OTAs), so jumping from from a 1.xx firmware all the way to an [incremental] 4.16 version, is going to cause problems.

i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...

srijan0008 said:
i did the same..
htc one m8
UNLOCKED
S-OFF
cid-11111111
hboot- 3.18.0.0000
radio-1.08.20.0612_4
opendsp- v38.2.2-00542-M8974.0311
os-1.54.651.8
eMMC-boot 2048mb
jul 7 2014, 20:03:18.23767
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom (i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
kindly help me to how should i get back to 4.2.2 or how can i still get viper rom flashed ...!
thank you.. been trying to get my phone back to 4.2.2 for the past week and havent tried doing viper yet..
plzzzz help...
Click to expand...
Click to collapse
Dude, your firmware is super old and you won't be able to run the latest ViperROM with it.
Be aware what I'm telling you to do will wipe your phone, (you'll need to do a full wipe to flash the ViperROM anyway)
Go here to download the official RUU from HTC's US website
Scroll down to the "Manual System Update Instructions" and read them. The RUU download is at the end of the instructions
After the RUU has run, reflash TWRP, then flash the ROM

srijan0008 said:
i did the same..
Click to expand...
Click to collapse
A word of advice, I know you are new here, but posting "I did the same" or similar ("same problem" etc.) is never true. Especially since you are responding to a thread from 2 years ago, different M8 versions, different ROM, different TWRP version.
There are simply far too many differences to say you "did the same" and that statement is therefore meaningless. Better to just describe the exact issue (which you did) and not bother with such vague statements.
srijan0008 said:
os-1.54.651.8
this is displayed when i turn on my device and i can enter recovery( teamwin recovery project 3.1.1-0 )
i was running on 4.2.2 version and wanted to upgrade to viper rom
Click to expand...
Click to collapse
As xunholyx explained you need to update the firmware, not just the ROM. Firmware includes a whole bunch of other partitions (hboot, radio, WiFi, and more) that ROM doesn't touch. Old firmware (your is very old) is not compatible with a more recent version ROM.
Old firmware is also not compatible with the current TWRP 3.1.1-0, so the ROM won't flash properly, either.
So as already suggested, flash RUU to update all the firmware. Then flash TWRP 3.1.1-0 back to the phone, and flash Viper.
srijan0008 said:
i ended up flashing a rom for some other device and deleting every stuff on my internal and sdcard by wiping it in recovery.
Click to expand...
Click to collapse
Another good rule of thumb, do NOT wipe things in TWRP "Advanced" wipe options, unless you know exactly what it is, and what the result will be. Wiping internal storage and/or SD will in most cases not help matter, but just make them worse (wipe backups, ROM zips, etc.).

NEWB HTC One M9 Boot Loop

Ok I apologise in advance for anything I get the wrong way around. I have a HTC One M9 (Vodafone UK) that had the latest Marshmallow update installed.
I attempted to try to root it using the instructions on DroidViews website and they advised to use the latest TWRP and the BETA-SuperSU-v2.48.zip
Followed the instruction to the letter. Unlocked the bootloader using the HTC page and this was fine. I can also boot into TWRP recovery but the standard system loader just cycles.
I read on another XDA page that the SuperSU should be 2.67 as HTC M9 has issues with anything lower, so I tried that. But again It comes up with a HTC logo (this time the red "for development purposes only" text) but then just restarts after a few seconds and loops infinitely.
I used the following;
TWRP 2.8.7.0-hima
and
BETA-SuperSU-v2.67-20160121175247
Ive tried clearing the cache as mentioned in other threads and this doesn't help. I also DID NOT install SuperSU from TWRP as advised on other pages.
Now im a little stuck, dont really know what to do next as it just cycles. I would be grateful for any help given.
Thanks
Jamie

You didnt make a nandroid backup?? IF not.. Try pushing a custom rom on your SD card and flash it
Skickat från min HTC One M9 via Tapatalk

Roobwz said:
You didnt make a nandroid backup?? IF not.. Try pushing a custom rom on your SD card and flash it
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
Roobwz said:
You didnt make a nandroid backup?? IF not.. Try pushing a custom rom on your SD card and flash it
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
No, the instructions didn't tell me how to and I googled but there is so much info I didn't really know where to turn.
Im currently downloading Android Revolution HD. Shall I try and put that onto SD and install?
The phone has TWRP but is NOT rooted as far as im aware. Is this going to be an issue? As it didn't get that far.
I'll just walk through what I did.
1) Followed instruction to unlock bootloader - DONE
2) Followed instruction to install TWRP - DONE
3) Started Phone and re-setup (as it had been wiped)
4) Restarted into TWRP Recovery and installed SuperSU
5) Cleared Cache NOT accepting TWRP's offer of Root and restarted
6) Boot Loop
Thanks
Jamie

jamster1432 said:
No, the instructions didn't tell me how to and I googled but there is so much info I didn't really know where to turn.
Im currently downloading Android Revolution HD. Shall I try and put that onto SD and install?
The phone has TWRP but is NOT rooted as far as im aware. Is this going to be an issue? As it didn't get that far.
I'll just walk through what I did.
1) Followed instruction to unlock bootloader - DONE
2) Followed instruction to install TWRP - DONE
3) Started Phone and re-setup (as it had been wiped)
4) Restarted into TWRP Recovery and installed SuperSU
5) Cleared Cache NOT accepting TWRP's offer of Root and restarted
6) Boot Loop
Thanks
Jamie
Click to expand...
Click to collapse
Well arhd should work if you pick the right version. Are u lollipop or marshmallow?
Well, try not rooting the ROM and you shouldnt bootloop anymore.
Skickat från min HTC One M9 via Tapatalk

Roobwz said:
Well arhd should work if you pick the right version. Are u lollipop or marshmallow?
Well, try not rooting the ROM and you shouldnt bootloop anymore.
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
Done ARHD and that worked, im marshmallow.
Even SuperSU has installed properly now so looks like problem solved!
Thanks for your help!

jamster1432 said:
Done ARHD and that worked, im marshmallow.
Even SuperSU has installed properly now so looks like problem solved!
Thanks for your help!
Click to expand...
Click to collapse
no problem. glad it worked out for you!
Skickat från min iPad med Tapatalk

Same problem
I have the same problem with a couple of differences. I am on o2 so have an o2 handset and although it does boot-loop, after about 10 minutes it actually boots. I followed the same guides as the original poster but my SuperSu is v2.65. Ideally I want to undo everything I have done but I too did not take a Nandroid backup and I cannot find a stock ROM anywhere. Same as the OP though, the phone reports that it is NOT rooted yet. Any help appreciated. Thanks

obrien1982 said:
I have the same problem with a couple of differences. I am on o2 so have an o2 handset and although it does boot-loop, after about 10 minutes it actually boots. I followed the same guides as the original poster but my SuperSu is v2.65. Ideally I want to undo everything I have done but I too did not take a Nandroid backup and I cannot find a stock ROM anywhere. Same as the OP though, the phone reports that it is NOT rooted yet. Any help appreciated. Thanks
Click to expand...
Click to collapse
Lollipop or MM? Try looking in Flippys thread for a stock nandroid backup. This is your best shot.
Custom M9
http://forum.xda-developers.com/showthread.php?t=3132698

Roobwz said:
Lollipop or MM? Try looking in Flippys thread for a stock nandroid backup. This is your best shot.
Custom M9
http://forum.xda-developers.com/showthread.php?t=3132698
Click to expand...
Click to collapse
MM - I looked through the thread and there is stock backups and TWRP backups that correspond to my devices CID (O2___001) The latest build version is 2.10.11.6 and my phone is currently 3.35.401.12. Does this matter? Will I just be able to update normally to the latest build?

obrien1982 said:
MM - I looked through the thread and there is stock backups and TWRP backups that correspond to my devices CID (O2___001) The latest build version is 2.10.11.6 and my phone is currently 3.35.401.12. Does this matter? Will I just be able to update normally to the latest build?
Click to expand...
Click to collapse
if youre s-off, then yes. But it wont work with s-on. try posting in the thread with your cid etc.. and hope that someone has a backup.
you can s-off with subshine for 25$ btw
Skickat från min iPad med Tapatalk

Roobwz said:
if youre s-off, then yes. But it wont work with s-on. try posting in the thread with your cid etc.. and hope that someone has a backup.
you can s-off with subshine for 25$ btw
Skickat från min iPad med Tapatalk
Click to expand...
Click to collapse
Does S-OFF mean that my bootloader is unlocked? If so then I am S-OFF
---------- Post added at 01:27 PM ---------- Previous post was at 01:13 PM ----------
Roobwz said:
if youre s-off, then yes. But it wont work with s-on. try posting in the thread with your cid etc.. and hope that someone has a backup.
you can s-off with subshine for 25$ btw
Skickat från min iPad med Tapatalk
Click to expand...
Click to collapse
No I just found that I am s-on
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
So if I pay sunshine to become s-off I can flash the version of stock in flippys thread and then update again or if I am s-on I need the correct version from the start?

obrien1982 said:
Does S-OFF mean that my bootloader is unlocked? If so then I am S-OFF
---------- Post added at 01:27 PM ---------- Previous post was at 01:13 PM ----------
No I just found that I am s-on
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
So if I pay sunshine to become s-off I can flash the version of stock in flippys thread and then update again or if I am s-on I need the correct version from the start?
Click to expand...
Click to collapse
When youre s-off, just change the cid to supercid and something more, and then youre able to flash the stock ruu because your phone is now a developer edition.
Skickat från min iPad med Tapatalk

Roobwz said:
You didnt make a nandroid backup?? IF not.. Try pushing a custom rom on your SD card and flash it
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
what file can I download to put in sdcard?

rosel11078 said:
what file can I download to put in sdcard?
Click to expand...
Click to collapse
Just follow a tutorial in the general forums

Roobwz said:
Just follow a tutorial in the general forums
Click to expand...
Click to collapse
Broth My phone situation is that I don't know it has S-OFF or Bootloader Unlock, so my phone is in bootloop, I enter with Vol up+Power button in menu that it says Select Boot Mode: with 3 option to start in Recovery, Fastboot and Normal Boot so my question is if I can use something to restore a live of my phone without developer option activate and S-off?

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 YouTube 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:
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 YouTube 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
Ah Youtube - source of much entertainment...but not always the best place for the latest software advice. It looks like you flashed an incompatible SuperSU zip file. The M9 is very finicky - I'm sure others can explain why. You can either flash SuperSU 2.65 or SuperSU 2.79 SR1.
I think you can just flash one of those files over your current install of SuperSU, but perhaps someone else can chime in to confirm? The stickied HTC M9 readme thread's 4th post has links to the SuperSU install files you'll want.

Life saver!
Thanks for the advice.
To sum up: I have TWRP 3.0.2.0
The original Super SU I used (which bricked the phone) was v2.46
I then placed v2.76 on top didn't work (was stuck in the boot loop)
I then placed UPDATE-SuperSU-v2.65-20151226141550 on top of that...and it works!
So for S-ON, unlocked bootloader on M9, with a 161 firmware, best options to root are TWRP 3.0.2.0 and UPDATE-SuperSU-v2.65-20151226141550.
The phone is now starting up (installing apps) and if I find anything else, I'll be sure to let you good folks know.

tigarstyle said:
Thanks for the advice.
To sum up: I have TWRP 3.0.2.0
The original Super SU I used (which bricked the phone) was v2.46
I then placed v2.76 on top didn't work (was stuck in the boot loop)
I then placed UPDATE-SuperSU-v2.65-20151226141550 on top of that...and it works!
So for S-ON, unlocked bootloader on M9, with a 161 firmware, best options to root are TWRP 3.0.2.0 and UPDATE-SuperSU-v2.65-20151226141550.
The phone is now starting up (installing apps) and if I find anything else, I'll be sure to let you good folks know.
Click to expand...
Click to collapse
Congratulations! It's always nice to hear when a phone is restored to working order.
I notice that you tried v2.76 before trying v2.65. Keep in mind that the only reliably flashable versions of SuperSU are v2.65 and v2.79 SR1. Now that you have SuperSU installed (and booting!), you can update the binary from within the app without having to flash it again (recommended).
Also, you mentioned TWRP 3.0.2.0. There is a slightly newer version (3.0.3-0) that the developer recommends. You don't have to use it (obviously, given that you're not!), but it has the benefit of supporting HTC's stock encryption.
Come on back anytime if you have difficulties in the future. Unlike Youtube videos, the XDA forums are up-to-date with the latest software and methods - and populated by some of the most knowledgeable users & developers around. Who knows, maybe you'll end up helping someone else in the future!

computerslayer said:
Congratulations! It's always nice to hear when a phone is restored to working order.
I notice that you tried v2.76 before trying v2.65. Keep in mind that the only reliably flashable versions of SuperSU are v2.65 and v2.79 SR1. Now that you have SuperSU installed (and booting!), you can update the binary from within the app without having to flash it again (recommended).
Also, you mentioned TWRP 3.0.2.0. There is a slightly newer version (3.0.3-0) that the developer recommends. You don't have to use it (obviously, given that you're not!), but it has the benefit of supporting HTC's stock encryption.
Come on back anytime if you have difficulties in the future. Unlike Youtube videos, the XDA forums are up-to-date with the latest software and methods - and populated by some of the most knowledgeable users & developers around. Who knows, maybe you'll end up helping someone else in the future!
Click to expand...
Click to collapse
I'd say "if it ain't broke, don't fix it". As you stated earlier, "finicky". The next step is s-off and leave it at that until you learn a lot more about how easy it is to completely knacker this phone!.
Beamed in by telepathy.

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.