Database Users

Question about TWRP's SuperSU

For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg said:
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.[/b]
Click to expand...
Click to collapse
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.

tsuttie99 said:
For the longest time while installing a new ROM or working in TWRP, I have been asked if I want TWRP to go ahead and install SuperSU for me even if sometimes the device is already rooted. Every guide and advice ever, has always said to ignore this completely. This remains true with Heisenberg's guide.
Heisenberg mentions it is not compatible. My question is why is this true? I flashed a 6P specific version of TWRP.
Also, are there specific circumstances where one would want TWRP to install SuperSU? To me it just seems like a handy time saver especially if you forgot to download it or something.
Click to expand...
Click to collapse
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.

Heisenberg said:
Root with marshmallow is different to all previous Android versions, it requires a modified boot.img. The most recent versions of the beta branch of SuperSU patches the boot.img for you, and you get working root. The version that TWRP offers to install is outdated and doesn't perform thief modification of the boot.img, flashing it will result in a boot loop. For the above reasons there are no circumstances where you'd want TWRP to install it for you.
PS. You could have just asked this question in the guide thread.
Click to expand...
Click to collapse
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol

tsuttie99 said:
Thank you for the clear explanation. I suppose you are correct about that, my apologies. I think I was getting it confused for a different thread which was closed. In case you can't tell, I'm new here. Lol
Click to expand...
Click to collapse
Well, welcome to XDA then! Here's the thread in case you need it:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

boot loader unlock and root

please any body suggest me an easy way(any way) to unlock boot loader and root my device,my ultimate wish is to root my device to remove bloatware. I searched the entire forum for a way to root my device but there are lot of conflicting opinions some say unlocked boot loader is a must for root , some threads say root is required for unlocking the boot loader,i am confused ,please give some advice by witch i can ultimately root my device
my device- ZE550KL
OS - MARSHMALLOW 6.0.1
with locked boot loader and unrooted
2GB ram
I will be grateful to you and ill be glad

I don't know if you can get root if you are on MM without fully switching to CM13.

I think it's pretty "easy", it's depend from the person to person though
There's already thread to unlock BL (no relock atm), and getting root is simply flash supersu.zip
It's just my thoughts, I'm not saying you must do what I'm going to write down here, so I'm not responsible if anything happen
* You need, say TWRP, to get root, how to get TWRP? "flash" recovery right?
* flash custom img (recovery) only possible if BL unlocked, you got bootloop if still locked
* so what if we just boot to twrp? Leave that stock recovery? We don't need that unlocked BL right?
* then the problem come from supersu, default su installation on M+ come in "systemless" mode, which modifying the boot.img, as point 2 above, we can't have non-stock img flashed on locked BL
* so how about make supersu "system", it did work on L with locked BL anyway, it's not modifying any boot.img,
* you could got root w/o unlocking BL by booting twrp, and flash su in system mode
Personally I'm not able to test this, because I love breaking things :silly:
Sent from my ASUS_Z00RD using XDA Labs

testeraphy said:
There's already thread to unlock BL (no relock atm), and getting root is simply flash supersu.zip
Click to expand...
Click to collapse
Can you point me to this? I can't seem to find it
THanks

Brett8187 said:
Can you point me to this? I can't seem to find it
THanks
Click to expand...
Click to collapse
Really? I don't even need the search function to find this
http://forum.xda-developers.com/zen...de-unlock-bootloader-asus-unlock-app-t3405850
*ooh, I should studying using forum tags
Sent from my ASUS_Z00RD using XDA Labs

ZTE Axon 7 Tenfar's Root and Magisk

Hi all,
let me first start by thanking the good people of xda community for your kind help and contribution. It would not be possible for people like me with extremely limited rooting knowledge to even have the courage to attempt a root if it wasn't for the good people like you here.
I just got my Axon 7 and is trying to work up the courage to attempt a root following tenfar's instruction (I'm extremely scared of bricking my new phone) I also hope that I can continue to play Pokemon Go after I root it, but unfortunately with the latest update, it seems impossible until I discovered Magisk. My question may seem fairly simple but it is extremely confusing to me. In Magisk's instruction it says that in order to install Magisk, one must remove any kind of root and systemless Xposed. Since my phone is not rooted, I do not have to go through the step of removing root and xposed? However, it says that I have to download Magisk and flash it. My confusion rests on the concept on how I can flash Magisk if my phone is not rooted? I thought one can only flash a rom etc after the phone is rooted? So should I follow tenfar's root first and root my axon 7 then try to flash Magisk? or the other way around? Any advice /tips/precautions/high level guides regarding both rooting using the tenfar method and flashing Magisk is greatly appreciate! I may suck at rooting and etc, but what I can do is follow all instructions carefully. Thank you everyone, you are the best!

To flash something (a ROM or an app, like Magisk) you need to have a custom recovery installed (such as TWRP, you boot into the custom recovery to flash the .zip file that contains whatever you want to flash) which generally means having an unlocked boot-loader, neither of those has anything to do with root (other than that they make rooting the phone considerably easier) they don't require it and they don't do it by themselves.

@Nameless One is right, you need a custom recovery (TWRP) to be able to flash Magisk. There is a thread about this in the forums.
However I would advise you to wait until next week when a new update is expected and perhaps some changes to the bootloader unlock policy and hopefully stock ROMs, which will make it much easier to solve any problems.
If you insist on going through with this now, you should take backup images of various partitions so that you can restore your phone to stock to receive the OTA.

How does it work if you have uninstall any kind of root? I would think root would be a requirement.

KyJelly69 said:
How does it work if you have uninstall any kind of root? I would think root would be a requirement.
Click to expand...
Click to collapse
It right on the top of their post
"This mod requires boot image modification, so unlocked bootloaders are required!"
What it does is implement it's own system-less root management module that will not be detected like other root methods. But will conflict with other root methods hence you have to be unrooted
Unlocked bootloader let's you flash custom recovery. That in turn let's you flash anything else including root modifications. In essence tenfar's boot image is modified to allow root. This will do something similar but you have to have the BL unlocked since patching boot image will change the signature.

iirc magisk alters the bootimage, so you need a unlocked Bootloader go get it to work.
And no, root is not a preq, you can use magisk to /aquire/ root though.
What u need:
- unlocked bootloader
- custom recovery
- a somewhat clean and not already modified system

Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!

projectseahorse said:
Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!
Click to expand...
Click to collapse
If you have copies of the stock images you will probably be able to fix your phone if something goes wrong and you want to go back to stock.
Not having these copies is like jumping out of a plane without a parachute and hoping you'll hit a haystack, without the pitchfork in it...
There are never any guarantees, every phone is different and as you are playing with important partitions there is a chance, generally through users fault, to brick your device...

Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!

projectseahorse said:
Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!
Click to expand...
Click to collapse
Well, the stock images have not been released for the B27 update, which would make it much easier to recover if something goes wrong. However, unofficial images are available (look around the forums). So at this point it is your call, just be careful.

Anyway to root without unlocking BL?

I just got the Axon 7 and am loving it. Is there anyway to root the latest B29 software without unlocking the boot loader. I saw an older thread but the software was B27 and it seems out of date and people were complaining about the links being dead. Anyways thanks in advance!
-Leroy

neo4uo said:
I just got the Axon 7 and am loving it. Is there anyway to root the latest B29 software without unlocking the boot loader. I saw an older thread but the software was B27 and it seems out of date and people were complaining about the links being dead. Anyways thanks in advance!
-Leroy
Click to expand...
Click to collapse
That would be the way.

neo4uo said:
I just got the Axon 7 and am loving it. Is there anyway to root the latest B29 software without unlocking the boot loader. I saw an older thread but the software was B27 and it seems out of date and people were complaining about the links being dead. Anyways thanks in advance!
-Leroy
Click to expand...
Click to collapse
So use the older b27 and root it that way? That shouldn't brick it should it? From the tool I understand it copy's your boot files so I guess that I could restore if need be?

You need to be on b27 to use that method. Just unlock bl if you want root.

neo4uo said:
I just got the Axon 7 and am loving it. Is there anyway to root the latest B29 software without unlocking the boot loader. I saw an older thread but the software was B27 and it seems out of date and people were complaining about the links being dead. Anyways thanks in advance!
-Leroy
Click to expand...
Click to collapse
Maybe a little too late for you, since I saw another of your threads saying you ended up restoring to B20
I was able to use TWRP and installed DrakenFX's BootStack and System images of B27 to downgrade from B29 to B27.
While I was trying to follow the "Root without unlocking bootloader" thread, I ran into some other issues though and my phone wouldn't boot so I tried a bunch of stuff and ended up re-flashing again to B27 and then restoring to B20.
But the good news was, after restoring to B20, I was able to follow the steps provided in http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157 to root without unlocking. The last step not mentioned, is to install the superuser manager app mentioned in the first post of that thread, phh's superuser. I previously tried using Chainfire's SuperSu but it was missing some binaries and didn't seem to work.

mozerxdaven said:
Maybe a little too late for you, since I saw another of your threads saying you ended up restoring to B20
I was able to use TWRP and installed DrakenFX's BootStack and System images of B27 to downgrade from B29 to B27.
While I was trying to follow the "Root without unlocking bootloader" thread, I ran into some other issues though and my phone wouldn't boot so I tried a bunch of stuff and ended up re-flashing again to B27 and then restoring to B20.
But the good news was, after restoring to B20, I was able to follow the steps provided in http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157 to root without unlocking. The last step not mentioned, is to install the superuser manager app mentioned in the first post of that thread, phh's superuser. I previously tried using Chainfire's SuperSu but it was missing some binaries and didn't seem to work.
Click to expand...
Click to collapse
Well crapola I ended up unlocking it
There's like alot of tools floating around with two different drivers so heck I ended up just combining a bunch of different methods lol. Needless to say I ended up unlocking the bootloader flashing TWRP and rooting. Thanks for coming in I might have to start over one day and that thread will help.

Want to understand how to root T-Mobile version

Like the title say, I'm getting ready to buy the T-Mobile version. I have read the conversion thread, but see others who say don't do that. I have a oneplus 3t but not a/b so I am confused lol

jamescable said:
Like the title say, I'm getting ready to buy the T-Mobile version. I have read the conversion thread, but see others who say don't do that. I have a oneplus 3t but not a/b so I am confused lol
Click to expand...
Click to collapse
I converted my 6t to the international version and have not had any issues in doing so. Don't quite understand why other users would advise not to do so. A plus to converting to the international rom allows you to easily unlock the bootloader and root the device of that's what you are looking to do.

elrey420 said:
I converted my 6t to the international version and have not had any issues in doing so. Don't quite understand why other users would advise not to do so. A plus to converting to the international rom allows you to easily unlock the bootloader and root the device of that's what you are looking to do.
Click to expand...
Click to collapse
Well, I have never used a a/b device before.....so I am very worried about the whole no permanent twrp

Don't worry about it you don't have to do anything with a or b slots just follow the instructions and you'll be fine

The a/b slots are nothing to worry about, as long as you follow the directions in the thread you'll be fine. There's an msm tool than can recover from any software failure if things go south. And for twrp, someone can correct me if I'm wrong but we have permanent twrp, at least I do

So, using the conversion tool is all I have to do to unlock bootloader and install ROMs like normal?

jamescable said:
So, using the conversion tool is all I have to do to unlock bootloader and install ROMs like normal?
Click to expand...
Click to collapse
Basically, yeah. Use this to do so. And for unlocking the bootloader extract the attached .rar file and run the .exe as administrator (you need ADB installed on your PC, OEM Unlocking enabled and USB Debugging Enabled for it to work) or use the command
Code:
adb reboot bootloader
then
Code:
fastboot oem unlock
For installing TWRP use this TWRP Installer (It also flashes Magisk), for installing custom ROMs use this guide.

_Masked_ said:
Basically, yeah. Use this to do so. And for unlocking the bootloader extract the attached .rar file and run the .exe as administrator (you need ADB installed on your PC, OEM Unlocking enabled and USB Debugging Enabled for it to work) or use the command
Code:
adb reboot bootloader
then
Code:
fastboot oem unlock
For installing TWRP use this TWRP Installer (It also flashes Magisk), for installing custom ROMs use this guide.
Click to expand...
Click to collapse
OK, and what about firmware? For the 3t, I have to have the updated firmware, is it the same for the 6t? And also, as I see, we have to use a computer for adb sideload everyyime we install a ROM?

jamescable said:
OK, and what about firmware? For the 3t, I have to have the updated firmware, is it the same for the 6t? And also, as I see, we have to use a computer for adb sideload everyyime we install a ROM?
Click to expand...
Click to collapse
No, the adb sideload was to bypass decryption issues, thanks (I forgot to update the guide). You don't need updated firmware.