Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Any ideas?
On Marshmallow you could try to use the beta 2.66. This version has a nice to accomplish systemless root, were root is written to boot.img and /data instead of system partition.
As I'm on Maximus HD which comes prerooted with v2.65 I can tell that this version works flawlessly on Marshmallow devices.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Freaksterz said:
Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Click to expand...
Click to collapse
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
So let's say I'm in marshmallow with trwp 3.0.0
Which version of supersu should I flash and which MOD should I choose ?
ofir_a said:
Which version of supersu should I flash and which MOD should I choose ?
Click to expand...
Click to collapse
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!
redpoint73 said:
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!
Click to expand...
Click to collapse
Thanks a lot
redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
Thanks for the insights. I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu. No matter what I do I am stuck in the htc logo bootloop. I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it. How do I go about it? I've been trying to find a solution for the last 4 hours, it's 3 in the morning. Help.
post.ratz said:
I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu.
Click to expand...
Click to collapse
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
post.ratz said:
No matter what I do I am stuck in the htc logo bootloop
Click to expand...
Click to collapse
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
post.ratz said:
I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it.
Click to expand...
Click to collapse
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.
redpoint73 said:
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.
Click to expand...
Click to collapse
Hey, thanks for the reply. It probably was too late at night and my mind had stopped functioning, a little common sense was all that was needed. The bootloop had only occurred because of me flashing the lower version of SuperSu. The good rule of thumb, forgive my lack of knowledge, I had no idea that a rooting of a device may change with the upgraded version of the OS. Woke up, took my external memory card out, transferred the SuperSu 2.65 on it and later flashed it though recovery.
Rest assured, I'll never go for a phone that does not have expandable storage option.
Thanks
Related
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Norcalz71 said:
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Click to expand...
Click to collapse
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then let TWRP install SU. I actually just did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
I'm pretty sure it works the same for lollipop now too. Originally you needed to flash a special kernel, but I think now you can root it the same way as Kit Kat, ie. via recovery. Someone can correct me if I'm wrong but I don't think I am.
_MetalHead_ said:
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then TWRP install SU. I did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
Click to expand...
Click to collapse
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Norcalz71 said:
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Click to expand...
Click to collapse
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
_MetalHead_ said:
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
Click to expand...
Click to collapse
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Norcalz71 said:
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Click to expand...
Click to collapse
No prob bud. One of the big benefits of Nexus devices is that they are super simple to root. Heck, they are super simple to do pretty much anything on. That's the only reason why I decided to start from scratch yesterday, because it's like nothing to do. The longest part was re-downloading all my apps, but still the whole process took about 30 min start to finish. If you're not downloading a ton of apps, it'll take you 5 minutes.
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Alte.78 said:
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
If you want you can PM me or join Freenode IRC and PM droidlambda. I've already started making CyanogenMod for the device, although I haven't come that far yet (even though the TWRP recovery you installed was ported by me). I could give you some advice (of my experiences with this phone and porting) and my basic config (which builds recovery successfully) if you want.
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Alte.78 said:
Getting Root
For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu.
Click to expand...
Click to collapse
If we install TWRP, can't we just flash SuperSU zip from recovery to avoid the KingRoot removal hassle?
Alte.78 said:
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable.
Click to expand...
Click to collapse
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?
Thanks.
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Great!
nick_white said:
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Click to expand...
Click to collapse
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Karboush said:
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Click to expand...
Click to collapse
Thats absolutely cool! I want to have custom recovery anyway, but your discovery will surely help a lot of people. :good:
nick_white said:
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?.
Click to expand...
Click to collapse
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Could you point me as to where did you find the firmware for the phone. I'm tempted to try rooting it. Is xposed necessary for the root to take full effect or no ? Cause it sounds a bit tricky and risky.
CostasV23 said:
Could you point me as to where did you find the firmware for the phone.
Click to expand...
Click to collapse
Try this link: http://www.sammobile.com/firmwares/database/GT-I9195I/
soo
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Click to expand...
Click to collapse
So my phone has the AOD1 firmware can i root it like AOD2? Im in greece
Alte.78 said:
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Click to expand...
Click to collapse
Can you tell me if these will work for sure I have the aob1 firmware
Ok, so I have mine updated to I9195IXXU1AOG1. How do I get SuperSU on it without changing Knox to 0x1?
Which version of Xposed is everyone using? On the S4 Mini Plus?
xposed?
Is xposed necessary for the rooting process? or can i just skip it to avoid all the fuzz?
Alte.78 said:
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Click to expand...
Click to collapse
I upgraded my firmware to:
PDA: I9195IXXU1APA1
CSC: I9195IPHN1APA1
which is also (one of) the latest version, and has the Stagefright vulnerabilities fixed.
Then rooted with latest KingRoot (4.80) + Super Sume Pro.
Then installed Xposed 2.6.1 (stable) and installed "classical" (write to /system). It worked, no bootloops. Maybe you tried a different Xposed version?
Hi! anyone have a baseband I9195LUBUCNJ2?
Synomenon said:
Which version of Xposed is everyone using? On the S4 Mini Plus?
Click to expand...
Click to collapse
Im using the app_process 58 and
xposedBridge.jar 54 which i think is the latest stable edition as of 13/07/2016
Xposed installer version 2.61 with auto flash in recovery method no problems 5 months that i have it
Full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i)
For more than a year, after I upgraded my firmware to:
PDA: I9195IXXU1APF1
CSC: I9195IYUX1APG1
which was the latest version from https://www.sammobile.com/firmwares/database/GT-I9195I/
I am using a debloat version of Galaxy S4 mini Plus (serranoveltexx). Inspired by @btnetro I made a script and tested a full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i). All this time my device has worked very well and even now I am very pleased with him. For those who want to keep stock OS like me, I decided to share with you this flashable zip.
First flash via Odin, a custom recovery on your device( installation instructions here: https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207 ), restart your device and copy attached files in the root of your ext. SD card. Reboot your device in recovery mode and flash “Full_debloat_i9195i.zip”. For those who want to keep weather widget flash this file “weather2014_A3.zip” too (first debloat). Wipe /cache and reboot your device.
OK, i've a weird issue.
I tried all the available recoveries (Philz touch 6.59.0, twrp 2.8.4.0 & 2.8.7.1 etc, and all flashed with odin method) but none of them recognize my external SD.
I tried other sd cards as well, known to be good as they're used in other phones, but end up with th same.
Funny part is that inside os (stock KK 4.4.4) i can see all the files in SD card...
Any suggestion?
Root/Bootloader unlocking failed? "No SU binary"
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back) and tried to root and unlock the bootloader but failed so I just stored it away .
I followed these videos. Can't paste links...new xda account:
youtube:
HTC One M8 : How to Unlock Bootloader & Root - Easiest Method
HTC One M8 : How to Root & Install TWRP Recovery - Easiest Method
I believe the first video, unlocking the bootloader, was successful(says "Software status: Modified""**Unlocked**" in bootloader mode).
In the second I believe TWRP was installed successfully (It opens up via Recovery) but the SuperSU app was not successful . I don't remember exactly what happened (it was months ago) but when I hit the SuperSU app I think it failed to update as seen in the second video at 2;29. As of today, when I try to open SuperSU, I'm presented with a message that says: "There is no SU binary installed, and superSU cannot install it. This is a problem! If you just upgraded to Android 5.0, you need to manually re-root" hit ok and SuperSU closes.
I found various fixes and such but I'm not sure which is the safest.
Sorry I'm new to android and I just don't want to ruin my device.
SOLVED
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Delete this thread I guess.
If you used the toolkit as shown in the Youtube video, that was your main problem.
The toolkit uses obsolete (and by obsolete, I mean over a year) versions of both:
SuperSU (current version is 2.46)
TWRP (current version is 2.8.7)
Using outdated versions of either/both of these with a stock Lollipop M8 will cause some major issues. Before doing any mods, its best to read and research to make sure you are using the most up-to-date procedures and files. Youtube should not be your only modding resource. Also, keep in mind that the "easiest" way, is not necessarily the "best" way.
huura said:
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Click to expand...
Click to collapse
Making a TWRP backup before flashing anything would have minimized any risk.
---------- Post added at 01:20 PM ---------- Previous post was at 01:20 PM ----------
huura said:
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back)
Click to expand...
Click to collapse
M8x is the Taiwanese, higher CPU clocked variant.
That makes sense. Thanks for all the info. woo slightly higher clock speed variant!
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
huura said:
T woo slightly higher clock speed variant!
Click to expand...
Click to collapse
On a side note. Only thing to be aware of, the M8x can't have other versions' radios flashed to it, even with s-off; as confirmed by a few users here (including one very knowledgeable one).
By extension, this probably also means that you can't "convert" to another version by running that version's RUU.
Probably not a major issue, as all other common mods (TWRP, root, flashing custom ROMs) should work fine on the M8x. Just something to keep in mind.
huura said:
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Click to expand...
Click to collapse
My advice would be to learn how to use fastboot to install TWRP, and skip the pointless middle man apps. Doing it by fastboot is easy, and much more reliable.
huura said:
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
Click to expand...
Click to collapse
No benefits that I know of. 2.46 roots the phone (on Lollipop) just fine, no need to have any "benefits" beyond that.
Marshmallow is a different story.
Ah ok. I'll keep note of that quirk, thanks.
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
huura said:
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
Click to expand...
Click to collapse
Its a good trick to know (as well as other fastboot commands) as it allows you to flash recovery without a working OS (not an unheard of situation, if you mess with flashing ROMs and other things enough times).
The process is pretty simple, as you most likely already have fastboot setup on your computer if you unlocked the bootloader. So flashing a recovery is simply a matter of:
1) Download the desired recovery .img to your fastboot folder (where fastboot.exe is located)
2) Connect your phone to the computer, and boot into bootloader-fastboot mode
3) Open a command prompt on the computer
4) Issue the proper fastboot command
5) Drink beer
huura said:
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
Click to expand...
Click to collapse
I haven't messed with Xposed for a while, but I think you just need to:
1) Make a nandroid of your current working setup
2) Install the Xposed apk
3) Open the Xposed app and install the desired frameworks
Figured it out, was straight forward
Was rooted in past on Lollipop. Tried to upgrade to Marshmallow using the 3.38.502.12 file in this thread:
http://forum.xda-developers.com/att...ficial-att-3-38-502-12-rom-7-01-2016-t3409354
Somehow got completely bricked, but I found the full RUU exe file for AT&T using Google which rebuilt everything, with full (ugh) bloat. Anyway I'm now back up & running with Marshmallow 6.0 and latest TWRP 3.0.2-0 is successfully flashed. The weird thing is that it does NOT give me the option to root & install SuperSu. I did make sure the "mount system read only" option was unchecked. I also tried installing SuperSU from the app store, but it reports required binary is missing. Is there any way to force TWRP to do it's root thing? It apparently thinks the phone is already done when it's not.
Hope all this mumbo jumbo makes sense. Thanks!
~Vol
Vol4Ever said:
Was rooted in past on Lollipop. Tried to upgrade to Marshmallow using the 3.38.502.12 file in this thread:
http://forum.xda-developers.com/att...ficial-att-3-38-502-12-rom-7-01-2016-t3409354
Somehow got completely bricked, but I found the full RUU exe file for AT&T using Google which rebuilt everything, with full (ugh) bloat. Anyway I'm now back up & running with Marshmallow 6.0 and latest TWRP 3.0.2-0 is successfully flashed. The weird thing is that it does NOT give me the option to root & install SuperSu. I did make sure the "mount system read only" option was unchecked. I also tried installing SuperSU from the app store, but it reports required binary is missing. Is there any way to force TWRP to do it's root thing? It apparently thinks the phone is already done when it's not.
Hope all this mumbo jumbo makes sense. Thanks!
~Vol
Click to expand...
Click to collapse
You're doing better then me. From what I've read it looks like you need the supersu.zip, but I think you know that. If you haven't try to install the supersu.zip maybe you'll be able to do it without bootloop (I need to make my post). A new version came out 9.15.2016.
Just flash SuperSu 2.64 or 2.65 using TWRP and that's it. Look for the link using google. Ohter versions cause bootloop.
I tried to root my one m9 using twrp-3.0.2-0-hima and the zip file of SuperSU v2.79.
After flashing SuperSU and pressing reboot in the recovery, the phone started to bootloop.
I tried a dalvik clear and a data wipe.
I can still get into the recovery bootloader and download mode.
The phone is the Taiwanese variant and was fully updated if that helps.
Sorry if this seems simple, but I really don't want to mess it up more. Any help is appreciated!
iateapietod said:
I tried to root my one m9 using twrp-3.0.2-0-hima and the zip file of SuperSU v2.79.
After flashing SuperSU and pressing reboot in the recovery, the phone started to bootloop.
I tried a dalvik clear and a data wipe.
I can still get into the recovery bootloader and download mode.
The phone is the Taiwanese variant and was fully updated if that helps.
Sorry if this seems simple, but I really don't want to mess it up more. Any help is appreciated!
Click to expand...
Click to collapse
Try flashing SuperSu 2.79 SR1 - the M9 should accept that without issue.
computerslayer said:
Try flashing SuperSu 2.79 SR1 - the M9 should accept that without issue.
Click to expand...
Click to collapse
The only versions I can find are 2.79 SR2 and the "stable"
Neither are working. Could flashing the latest stock on the htc website or installing a different rom help?
The HTC site says that installing it may damage the device if you modified the device software or Bootloader is that just an obligatory warning or is it serious?
If you are rooting android 6.0 you need twrp 2.9.0.1 and supersu 2.65. You can find them here: https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
If you are rooting 6.0.1 you need twrp 3.x and supersu 2.7
Beamed in by telepathy.
According to download mode the OS is 3.36.709.3
I can't tell if that's 6.0 or 6.0.1 even with google.
If it is 6.0, can I just put the twrp file in the adb platform tools folder and flash like before or do I have to do anything different?
shivadow said:
If you are rooting android 6.0 you need twrp 2.9.0.1 and supersu 2.65. You can find them here: https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
If you are rooting 6.0.1 you need twrp 3.x and supersu 2.7
Beamed in by telepathy.
Click to expand...
Click to collapse
That is not correct. As already written in a different thread some days ago: captain throwback deleted twrp 2.9 on purpose. So please stop recommending that version.
The currently recommended versions of twrp are 2.8.7.1 for firmware 1.x and 2.x of the M9 and 3.0.3-0 for firmware 3.x and above. Both can be found in the TWRP thread in the original android development section.
And supersu 2.79 sr1 is just working fine with the stock rom of the m9. There you go: http://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
Edit @iateapietod: You need to reflash the stock boot image of your firmware. This can for example be done by restoring it via one of the backups in my thread. Follow the instructions in the twrp section II with the following exceptions: don't wipe anything via TWRP and only restore "boot" and not "system" or "recovery". After that your rom should be booting, again.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That is not correct. As already written in a different thread some days ago: captain throwback deleted twrp 2.9 on purpose. So please stop recommending that version.
The currently recommended versions of twrp are 2.8.7.1 for firmware 1.x and 2.x of the M9 and 3.0.3-0 for firmware 3.x and above. Both can be found in the TWRP thread in the original android development section.
And supersu 2.79 sr1 is just working fine with the stock rom of the m9. There you go: http://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
Edit @iateapietod: You need to reflash the stock boot image of your firmware. This can for example be done by restoring it via one of the backups in my thread. Follow the instructions in the twrp section II with the following exceptions: don't wipe anything via TWRP and only restore "boot" and not "system" or "recovery". After that your rom should be booting, again.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Okay, I completed that and redid TWRP and superSU, now though the SuperSU app is giving the error that its binaries are not installed and it cannot install them.
What do I need to do about that?
Just follow flippy, he knows everything..
Twrp 2.9.0.1 works fine for me since day 1 so i think the issues might not actually be this version of twrp.
Supersu 2.65 works peachy too, no need to use any other.
BUT, everyone seems to think otherwise but I ain't no sheep and my phone works great rooted and s-off. It has done since the day I done it so I have no reason NOT to recommend the files I'm CURRENTLY using and have been for nearly 12 months.
So, smarty pants. Su binaries won't install and I don't know how to solve it. I have no place in this thread now.
Beamed in by telepathy.
iateapietod said:
Okay, I completed that and redid TWRP and superSU, now though the SuperSU app is giving the error that its binaries are not installed and it cannot install them.
What do I need to do about that?
Click to expand...
Click to collapse
Please reflash the boot.img and then flash SuperSU 2.65. It was the latest compatible version before 2.79 sr1 got released. You can update it via the play store, afterwards. It looks like some M9s have issues with 2.79 sr1. You're the second person that reports problems.
shivadow said:
Just follow flippy, he knows everything..
Twrp 2.9.0.1 works fine for me since day 1 so i think the issues might not actually be this version of twrp.
Supersu 2.65 works peachy too, no need to use any other.
BUT, everyone seems to think otherwise but I ain't no sheep and my phone works great rooted and s-off. It has done since the day I done it so I have no reason NOT to recommend the files I'm CURRENTLY using and have been for nearly 12 months.
So, smarty pants. Su binaries won't install and I don't know how to solve it. I have no place in this thread now.
Beamed in by telepathy.
Click to expand...
Click to collapse
I don't know everything. And I apologize for my harsh words but the thing is that I simply don't understand why someone should recommend a version of a custom recovery that got deleted by the dev who created it so that no one is able to download it anymore. It might be working for you but if that version could be used without issues then you would still be able to download it from captain throwback's thread. (I'm not even sure whether you're allowed to re-upload the old TWRP version without captain throwback's permission.) I'm only repeating the recommendations that got posted in captain throwback's thread and I don't think that anyone else than the dev of the custom recovery himself knows better which version is recommended for this phone and which not.
The boot.img is what you said to backup in the one m9 guide correct? Just wanted to be safe.
iateapietod said:
The boot.img is what you said to backup in the one m9 guide correct? Just wanted to be safe.
Click to expand...
Click to collapse
Just restore the backup you restored when your phone wasn't booting after you had flashed SuperSU for the first time. Don't forget the exceptions that I posted at that time.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Just restore the backup you restored when your phone wasn't booting after you had flashed SuperSU for the first time. Don't forget the exceptions that I posted at that time.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks, will-do!
Flippy498 said:
That is not correct. As already written in a different thread some days ago: captain throwback deleted twrp 2.9 on purpose. So please stop recommending that version.
The currently recommended versions of twrp are 2.8.7.1 for firmware 1.x and 2.x of the M9 and 3.0.3-0 for firmware 3.x and above. Both can be found in the TWRP thread in the original android development section.
And supersu 2.79 sr1 is just working fine with the stock rom of the m9. There you go: http://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
Edit @iateapietod: You need to reflash the stock boot image of your firmware. This can for example be done by restoring it via one of the backups in my thread. Follow the instructions in the twrp section II with the following exceptions: don't wipe anything via TWRP and only restore "boot" and not "system" or "recovery". After that your rom should be booting, again.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I was being sarcastic..
When i rooted my m9 i followed the common guides which all recommended twrp 2.8.7.1 and that failed to boot for me so I went up to 2.9.0.1 and that worked. The next thing I know is it got deleted by the dev for no known reason and another version was immediately put in its place.
Rather than being ocd and updating immediately i decided to wait. Which was a good idea because at the time i was seeing quite a lot of problems relating to rooting with said higher version of twrp. I have stuck with it since.
A flea in your ear about "copyright infringement". Once you release something into the wild, especially under the gnu license, you lose all rights of control but you retain the rights to "design and ownership". I can keep, use and distribute 2.9.0.1 under the gnu license, as it is written in linux/unix, but I may not use it in my own projects or claim it as mine.
Beamed in by telepathy.
To settle this issue definitively it might be worth asking Captain Throwback why 2.9.0.1 was taken down, or searching the thread for discussions about potential issues. But as previously mentioned, the official thread's FAQ (#2) recommends using the 2.8.7.x version for pre-Marshmallow firmware and the latest 3.x.x.x version for post-Marshmallow firmware.
As one who has done so more than a few times, I can testify that it's both embarrassing and potentially damaging to recommend faulty software or advice. I have been grateful for the correction more experienced members have offered, though it's humbling every time. For the sake of helping other users, especially new ones, it's good to be sure that we're offering the best of both.
(For what it's worth: From what I can tell of the conversation in the original thread between 2.8.x.x and 3.x.x.x, the 2.9.x.x series was built primarily to test decryption of the M9. When 3.0.0.1 came out, it supported AOSP decryption, along with the updates that came with 3.0.0.0 (like flashing <4GB zip files). I imagine that the 2.9.x.x series was discontinued due to the success of the 3.x.x.x release. And of course, 3.0.3-0 now supports decryption stock Sense.)