Develop Bugs

Help with rooting Htc M8 marshmallow

Hi,
So I'm new to these forums and have been browsing all of the rooting guides for my HTC M8. I am running official Marshmallow and really want to root my phone (again) as far I know I have unlocked boot loader. I had to factory reset my phone last year and never got round to re rooting, but now with marshmallow I wish to do so again.
My issue is I can't seem to understand the steps the guides are outlining. I download the links and try and open them, but nothing happens. Is there a step by step fluid guide in rooting my phone? As all the guides I have found have basically blown over my head. I used a toolkit in the past which did everything for me automatically. If no such post exists would someone be able to explain the steps in a simplified manner? (If possible)
Many thanks in advance to any who help

Optcpsi said:
as far I know I have unlocked boot loader
Click to expand...
Click to collapse
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.

redpoint73 said:
This is easy to determine definitely. Boot into bootloader (if you don't know how, ask and I'll explain) and it will either say bootloader is: LOCKED, UNLOCKED or RELOCKED near the top of the screen.
Vomer's guide is dated at this point, but mostly still accurate for what you want to do (root MM); and its the best guide I know of: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
If your bootloader is UNLOCKED, you can skip the whole section on unlocking it, and pick back up the guide again where it says CUSTOM RECOVERY. If the bootloader is LOCKED or RELOCKED, you'll need to do the section for unlocking the bootloader.
AFAIK, the only part of Steps 0 and 1 that is out of date, is the TWRP version. For MM, you should use TWRP 3.0. And somewhat obviously, the fastboot command to flash TWRP will need to have the corresponding file name; rather than the old version number given in the guide's example.
You'll also want to use SuperSU 2.76 (if the SuperSU version is too old, it will fail to root MM and leave you stuck with no boot). But the guide is already rigged to link to the latest stable version (not a particular version number), so presently it already links to 2.76.
Don't continue to Step 2 of the guide. Its not longer accurate, and not needed for root.
Click to expand...
Click to collapse
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?

Schmix said:
Thanks for posting, couldn't find an up-to-date tutorial anywhere.
TWRP is asking to keep system read-only and I'm confused. If I allow modificaions, can I automatically never receive OTA updates again?
Will there even be another one for the M8/ will it get Nougat? Anyways, can I still root it with read-only?
Click to expand...
Click to collapse
You need to allow modifications for root. At least traditional root. Systemless root, I would think would work if you stay read only - but do the research especially if you don't know the difference between traditional root and systemless root.
You can't install OTA updates with a rooted device in any case, so that point is irrelevant.
If/when ever an OTA comes, you would need to return to stock never rooted ROM and stock recovery, in order to OTA update (there are guides on this forum). This would remove any modification by TWRP.
But that's mostly just FYI/academic. Its extremely unlikely we'll get an OTA update to Nougat. Your best bet for Nougat will be custom ROMs, anyway.

1. UNLOCK bootloader with HTC Dev site.
2. Flash latest twrp recovery
3. Flash Stable v2.65 SuperSU
4. Flash wp mod.
5. Update SuperSU on Play Store.
Latest SuperSU 2.76 zip kills Boomsound. Permissive zip can fix that.

Help with a boot problem. (soft brick?)

Hi.
I recently got a HTC one M8 second hand from my father.
I decided that i wanted my next phone to be rooted, so i started working on that before anything else.
I have followed a youtube guide located at /watch?v=wpFpmAQa-40 (new user, cant post links) to get my phone rooted.
Unlocking the bootloader went fine, and i managed to boot into the OS from then on and managed to make a back-up with TWRP while unrooted.
Getting into the OS with the bootloader unlocked, i downloaded SuperSU-v2.37 onto the phone.
However, once i tried to use TWRP to install this it went wrong.
After installing this, the phone would no longer boot, and get stuck on the initial white boot screen with the HTC logo.
i tried to restore the backup i made using TWRP, but to no anvil.
The bootloader shows *** Software status: Modified *** at the top.
I suspect that becaus this flag is set, the OS reuses to load.
Some more info: the phone in question is from Vodafone, and i used the AT&T/T-Mobile/international TWRP recovery from the site mentioned in the above youtube video at link (site here)/cwmtwrp-recoveries/ (again, new user, can't post links).
As such, it had a bunch of vodafone stuff (like a vodafone boot and shutdown animation), so i also suspect it has some form of carier lock, though i have not been able to find a guide which mentions a vodafone lock, only AT&T, Verison and Sprint.
I someone know how to get my phone working again (preferably rooted, but at this point i would also settle for unrooted, locked and s-on).
I don't really want to go messing with s-off since i aparently already borked this up.
EDIT:
OK, so i tried to do a restore again, seems that restoring does indeed work, but getting SuperSU does not.
I'l look for a more up to date version of superSU.
EDIT2:
It went even wierder now. I can no longer download files on the phone, nor can i transfer files from the computer.
EDIT 3:
Well, didn't fix it, but got aound it. got an sd card in the phone, downloaded SuperSU from the site, and installed it with TWRP from the sd card. access to the internal storage is still blocked/buggy.

First! - The flag ****MODIFIED**** shows when you have custom recovery
and second - in my opinion the best thing you can do is to lock the bootloader using "fastboot oem lock" when in bootloader and then instantly reflash the phone using RUU which should be the Vodaphone version and then use KingoRoot to gain root. Use the PC Root method!

wild_dog said:
I have followed a youtube guide located at /watch?v=wpFpmAQa-40 (new user, cant post links) to get my phone rooted.
Unlocking the bootloader went fine, and i managed to boot into the OS from then on and managed to make a back-up with TWRP while unrooted.
Getting into the OS with the bootloader unlocked, i downloaded SuperSU-v2.37 onto the phone.
However, once i tried to use TWRP to install this it went wrong.
After installing this, the phone would no longer boot, and get stuck on the initial white boot screen with the HTC logo.
Click to expand...
Click to collapse
That Youtube guide is outdated. Its says published Feb 2016, but I thinks that is misleading. I believe the video was made much longer ago. The phone being used has KitKat OS version from the M8 release back in May 2014. And as such, the root method is just as horribly outdated.
If your phone was on Marshmallow OS version, the general process in the video is okay, but you need should use TWRP 3.0.2 and a relatively current stable version SuperSU (which is currently 2.78, that's right 41 versions newer than what you used). TWRP version and SuperSU version is dependent on OS version, but what I"ve stated probably applies to most folks at this point (since Marshmallow was released some time ago, Dec 2015).
Using outdated SuperSU version is the most common reason for no boot after trying to root. And flashing the proper version SuperSU is the fix. So good work figuring it out.
---------- Post added at 11:05 AM ---------- Previous post was at 11:00 AM ----------
wild_dog said:
The bootloader shows *** Software status: Modified *** at the top.
I suspect that becaus this flag is set, the OS reuses to load.
Click to expand...
Click to collapse
This would be an incorrect assertion. Software: Modified has no bearing (in itself) on whether the phone boots into OS or not. As another mentioned, it just means a custom recovery is installed, and/or system modifications (root, etc.) have occurred.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
wild_dog said:
i tried to restore the backup i made using TWRP, but to no anvil.
EDIT:
OK, so i tried to do a restore again, seems that restoring does indeed work, but getting SuperSU does not.
Click to expand...
Click to collapse
Also, nice work (honestly) making a TWRP backup before trying root. Many folks skip this simple (yet critical) step, and then are in a panic on how to recovery after a failed root attempt.
---------- Post added at 11:10 AM ---------- Previous post was at 11:07 AM ----------
todorkaravalchev said:
in my opinion the best thing you can do is to lock the bootloader using "fastboot oem lock" when in bootloader and then instantly reflash the phone using RUU which should be the Vodaphone version and then use KingoRoot to gain root. Use the PC Root method!
Click to expand...
Click to collapse
While technically valid, this is overly complicated solution; considering the fix was to flash the proper version SuperSU (and bootloader already unlocked, and TWRP installed).
Also, while kingroot works for some folks, others have had issues with it. Rooting with the more common method (TWRP and SuperSU) virtually always works, as long as the proper version SuperSU is used.
Just some constructive comments. Your contribution is appreciated nonetheless.

Yes mate, I agree, but he only wants root and everithing else to work, so, as he said he isn't so good at this things and I offered the purest and easiest way for him to aquire what he wants. Thank you!

And i apriciate the help, todor.
Although i have gotten this working, i have run into some small things (don't you always... SIGH).
I have not gotten the block on coppying files to the internal memmory fixed yet, but for what i wanted to do (remove factory deafault bloatware) it apears i have to do s-off anyway, and i suspect doing so will fix it.
So that will be a nice project for next weekend.
I do have to point out though, that king root, which you referenced, in a listing i found, currently does not support the HTC one M8 with android 6.0, which i have.

wild_dog said:
I have not gotten the block on coppying files to the internal memmory fixed yet
Click to expand...
Click to collapse
This may be a matter of internal storage being corrupted. In TWRP, try going to WIPE, select "Format data" and see if that helps.
Obviously, you will lose your data, so backup before hand, accordingly.
wild_dog said:
but for what i wanted to do (remove factory deafault bloatware) it apears i have to do s-off anyway, and i suspect doing so will fix it.
Click to expand...
Click to collapse
Incorrect, you don't need s-off to delete bloat apps. The issue is that the system is write protected (from deleting bloat apps, etc.) on this device, even with root. You need the kernel mod to disable write protection, in order to delete bloatware.
The wp_mod zip attached to the following thread should work on most or all Android 6 Sense 7 ROMs. But backup your current ROM in TWRP before flashing, just in case it doesn't work properly:
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894

I'm not so sure about what I'm about to say, but if you have root and use this file manager called "Root Browser" you should be able to delete the bloat. The only thing that you have to do before you delete something is to mount the /system partition -rw (read, write) and there was such option tn the file manager that I told you about. And make sure you have busybox installed for this option to work.

Zenfone 2 issues in 2017

Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time

assuming you are already on MM version ww4.21.10.233... if no update to this version and download the following tool..
https://drive.google.com/open?id=0B72QQTXqZSRwTDNtU1N6OEdMdmM
reboot phone in fastboot mode. now extract the downloaded zip and double click unlock.bat phone will reboot 2 times. then you will get white screen and stuck there. when you see white screen. simply turn off mobile. reboot in fastboot mode with volume plus and power button. and run restore.bat from extracted zip.
now download twrp from official twrp website version 3.1.1.0. and flash it in fastboot mode. hope you know how to ( place twrp image in adb fastboot tool and open command windows in same folder reboot phone in fastboot mode and connect to pc. run the following command
fastboot flash recovery twrp-3.1.1-0-Z00A.img
then use volume button to find recovery mode and click power button to boot into twrp.
now download super su from following link use this version only as i have just tested it few minutes ago.
https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
place superuser zip on internal memory or sd card and click install in twrp and install super userzip. alternatively you can sideload supersu zip as well. then wipe cache and dalvik cache and reboot system. note phone may bootloop or restart 2,3 times. don't interrupt it. it will boot itself into system.
this is 100 percent safe way.
---------- Post added at 11:12 PM ---------- Previous post was at 11:05 PM ----------
x86fanboy said:
Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time
Click to expand...
Click to collapse
do you state that you have an old device which you are unable to revive with xFSTK. what error do you get? put device on charge for 5,6 hours with original charger and use the following guide. use correct gp flag value use 4 zeros not 5
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

wow, no need to do all this... just use one of the available tool, my prefered one is this one:
https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293
very easy to use, to unlock, it will temporaly downgrade your boot to 5.0, unlock bootloader, then reflash boot 6.0.
Once there, just flash TWRP recovery and Magisk, from the tools.
I also had a locked ZF2 in MM 6.0 and using this tool it took less than 5 minutes to have an unlocked rooted phone, and I haven't wiped or lost anything.

M8s on Marshmallow - systemless root - how?

Hi,
I recently had to return my phone back to stock because of a warranty issue. (battery dying between 25% and 40%)
So chances are high that I will get the phone back with Marshmallow instead of Lollipop.
is there a guide or can anyone give some pointers how to root this device? After a bit of reading I still have a few specific questions, so maybe someone here can help.
A) What TWRP version will I need for the M8s on Marsmallow?
B) Will Magisk systemless root work on this device?
C) If the rooting has succeeded and I remove some bloatware apps from /system/vendor and /privapp and such. Will this trip the Google safety net? Or is safety net not yet applied to our M8s devices?
Thanks!

I don't personally have the M8s version specifically. But as the device forum sections for all the M8 versions in general are becoming pretty quiet; I'll try to help you to the best of my knowledge.
A) The TWRP recovery posted in this (M8s) forum section should work fine on Marshmallow. Looks like it's only updated to 2.8.6
B) Should work, yes. I would suggest the current stable Magisk version, which is 14.0
Backup your stock (unrooted) ROM before trying to root (as you always should - this is best practice and just good common sense). Then if anything goes wrong, you can easily restore to stock.
C) Not sure. But I can tell you on my current device (OnePlus 3T) that removing system (bloat) apps does not trip safety net.

Hi @redpoint73,
Thanks. That takes away some worries and gives me some confidence for giving it a third shot . Nandroid's don't work on the M8s unfortunately, I've tried this once since I botched something up during my first root attempt, put back the Nandroid and my Bluetooth was dead. (and probably more, but I didn't investigate it further back then.)
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Thanks so far and I'll report back my results in this topic. Now I first have to wait to see if they give me my warranty, since the bootloader said relocked and the firm I had to send it to is notorious for blaming factory faults on rooting of the phone. Fingers crossed!

Thijs_Rallye said:
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Click to expand...
Click to collapse
Should be the same, yes.
The reason for this, is that the system is write-protected, even with root. On the M8, there is a kernel mod which disables the write protection (allows you to modify system while booted to OS), but I don't know if there is such a mod for the M8s. But if you were able to do it in TWRP, the same should apply on Marshmallow.

So I finally got my phone back, or well, to be accurate, I got another phone (albeit another M8s) back under warranty. I guess they f'd it up during repairs or something. And as expected my phone was upgraded to Marshmallow.
Anyhow, the more I read about Magisk and systemless rooting the more lost I seem to get lost. Is there somewhere a step by step guide for obtaining root on this phone?
Let me recap from what I've understood so far (SOURCE 1, SOURCE 2 and SOURCE 3)
1) Backup my boot partition, I am still searching how to accomplish this without rooting the phone first. Booting to TWRP without installing resulted in mangling some data in the boot partition, so unfortunately that is not an option. (blanks the OS version)
2) Boot to TWRP and flash the Magisk zip file. There should be an option somewhere in TWRP to enable systemless rooting.
3) ?
So if anyone knows if I am on the right (or wrong) track please let me know .
Thijs
Edit: I can't seem to get the phone boot TWRP for some reason (from my harddrive htc_fastboot boot twrp.img). This used to be possible on my old M8s which I had send in for repairs. Do I really have to flash it because I have no way of backing up the old original recovery .

Okay, since it is kinda dead in here let me bump this for anyone in the same situation. I've managed to install Magisk successfully. The steps involved
1) unlock bootloader
2) flash twrp (htc_fastboot flash recovery twrp.img) I've used the latest version from Captain Throwback which I've found in the OP of the Void_Zero Lineage OS thread.
3) boot the phone and copy magisk systemless root zip and the apk file to your internal storage Grab the uninstaller as well in the topic.
4) reboot to recovery (adb reboot bootloader)
5) flash the zip from within recovery
6) reboot the phone and install the Magisk app.
7) done
Use this guide on your own risk. It worked flawlessly for me but no guarantees .

Need help rooting device

Hi,
As the title says, I need help rooting a Xiaomi Mi A2 Lite device, that is updated to Android 9.
I tried rooting it, but the issues are:
1. It needs unlocking the device first, so I tried going to - //en(DOT)miui.com/unlock/.
There it wants me to connect my device to my Mi account in Setting > Developer Options > Mi Unlock Status. Thing is that this device is using one of the ROM versions, which doesn't have Mi Unlock Status.
2. This led me to try and update the ROM. Issue here is that doing so through the fastboot is not possible because the device needs to be unlocked, so I tried this - //en(DOT)miui.com/a-232.html
3. From there on, everything is fine until step 3. In android 9, they have decided to move the System Update to another table, which is fine but there are no longer 3 dots or an option to select a package. I tried looking for that without success.
4. Downgrading to Android 8 is not possible anymore, and I haven't really checked if I can do it with a locked phone.
Can someone help me find what I am missing here? There must be a way I can root the device.
Thank you!

developer options , unlock oem, boot to bootloader and type fastboot oem unlock, its that simple. All you nee to do after this is follow a tutorial for rooting with magisk.

My friend you were following the wrong guide. This is an Android One device you don't need the unlock procedure that the other MIUI device have to do.
As mentioned above the unlocking is straight forward, however the steps following can be a bit more confusing.
Basically there are different methods on how to actually gain root access, the most popular and recommended one would be using a framework/app called Magisk.
Download the magisk manager from the app store and more importantly check exactly your build number in your phone settings as you will need a patched boot.img file for exactly that build (here you can either download the patched boot from one of the thread here but its more safe to actually patch the original boot.img yourself).
However most of the stuff is written in this thread, it's only missing the updated boot files for Android Pie.
I recommend you to patch the boot from the official Rom files (for example for Pie 10.0.2.0 here and patch it via magisk manager yourself)

Thank you all. I managed to root it.
1. Not entirely sure how the unlock went but it was successful. I tried the fastboot oem unlock. I think that did it.
2. Got TWRP on the fastboot and installed Magisk
3. Root access was granted, data got wiped twice though, but the second part was my fault.