Systemless Root and Titanium Backup - Nexus 6 Q&A, Help & Troubleshooting

I read on another forum that Titanium Backup does not work if you're using systemless root. Can anyone verify if this is true ?
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?

aparanoidandroid said:
If TB does work, how would I go about upgrading stock Android 6.01 rooted with TWRP to 6.0.1 with systemless root ?
Click to expand...
Click to collapse
Make backup's with TWRP.

NLBeev said:
Make backup's with TWRP.
Click to expand...
Click to collapse
I know how to make backups with TB. That wasn't my question. My question is, how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)

aparanoidandroid said:
... how do I go from 6.0 rooted with SuperSU to 6.0.1 with systemless root (assuming TB works in 6.0.1)
Click to expand...
Click to collapse
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493

NLBeev said:
Read post 2153 of @Tylog in this thread
http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?

aparanoidandroid said:
So is SuperSU 2.61 the ZIP for Chainfire's systemless root ?
Click to expand...
Click to collapse
Yes since version 2.6x.

NLBeev said:
Yes since version 2.6x.
Click to expand...
Click to collapse
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method. Do root apps need to be specifically modified for this type of rooting so it can recognize it ?
Also just to be clear, I am on stock Android 6.0 ROM, rooted and with TWRP recovery.
so the order that I would need following according to the post that you gave me is:
Flash 6.0.1 ROM
flash Update-unSU
flash SuperUser 2.61 or 2.52
Is that correct ? Can I dirty flash 6.0.1 over 6.0 ?

aparanoidandroid said:
What about Titanium Backup ? Can anyone verify if it works or not with systemless root ? I read a post on Reddit where someone said that they were not able to use it with this root method.
Click to expand...
Click to collapse
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.

NLBeev said:
Root apps with hard coded su-stuff needs to be updated for use with systemless root.
What I read....There is a new version 2.62 that solves compatibility issues. But Android Pay will not work.
Click to expand...
Click to collapse
Oh really ? From what I read, Android Pay and OTA both do work using systemless root although many people think that Google will find a way to block Android Pay again. Its one of the reasons I wanted to use systemless root in the first place.

aparanoidandroid said:
Oh really ? From what I read, Android Pay and OTA both do work using systemless root..
Click to expand...
Click to collapse
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125

NLBeev said:
Not with version 2.62. Info in the SuperSU thread.
http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
OK. Thanks for the info.

Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.

hayzooos said:
Yes, TB works with systemless root.
I was running stock 6.0 w/ root (a few xposed mods) and here's what I did:
Wiped system, flashed Cataclysm, flashed SU 2.61, rebooted, profit.
I also manually updated the radio by using fastboot, for what it's worth. AdAway made me create a simlink with the systemless root, but TB seemed to work just fine.
EDIT: I wiped system before anything as I knew it would get rid of any root files and anything related to Xposed. Phone has been running great, but I haven't re-done Xposed as the only modules I really used were GravityBox and YouTubeAdAway. Catacylsm has almost all the features I used in GB so no need to do both. I might put Xposed on tonight for kicks, but I don't really need it for anything right now.
Click to expand...
Click to collapse
thanks but what happens when you wipe system ? What will I lose other than root ?

aparanoidandroid said:
thanks but what happens when you wipe system ? What will I lose other than root ?
Click to expand...
Click to collapse
Anything Xposed related will be gone, but other than that...nothing. All apps, settings, etc of mine were all retained. Wifi networks, bluetooth connections, all those stayed. Wallpaper, Nova Launcher setup/settings, stayed.
Most ROMs have built in their script to wipe the system partition before flashing anyway, so you're likely already doing it if you're flashing ROMs. I just wanted to start with a pretty clean slate and check to see if anything in data was causing issues, and nothing so far.

Titanium Backup 7.4.0.2 and System Root was working about 2 weeks ago FLAWLESSLY
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
Sorry,
I could not acquire root privileges.
This application will *not* work! Please
verify that your ROM is rooted, and try
again.
This attempt was made using the "/system/
bin/su"command."

CLETjB said:
My last Titanium Backup was on July 7, 2016 with Systemless root, with XPosed, Gavitybox for MM and Stock 6.0 ROM Build MPHS24.49-18-3. I have been using Titanium Backup since I got my MOTO X Pure (2015) in May of 2016, and everything is working great, except I just noticed that Titanium Backup v 7.4.0.2 states
"Error
Sorry,
I could not acquire root privileges.
This application will *not* work! Please
verify that your ROM is rooted, and try
again.
This attempt was made using the "/system/
bin/su"command."
Click to expand...
Click to collapse
Do you have Busybox installed? If not, that may be why. Had the same issue, installed Busybox to /su/xbin, and all is good now.

Gravity Box works with XPosed Framework, which ONLY works with "BusyBox on Rails", which I do have installed. Not sure if I can tell it where to install BusyBox, but it seems to be working now.

Does anyone have a clue to get magisk and titanium backup to work with each other... TB does not seem to ask for Root, seems to simply bypass it...
-----Nevermind, just make sure you have unticked Magisk Hide- in Settings. WORKS!

Related

Root stock Lollipop 5.0.2 with Kingroot & Super-Sume .......no tripping Knox

SM-T700 UK version stock 5.0.2
1. Root using Kingroot 4.5
2. ONLY now !!! install and run Super-Sume
3. Update SuperSu binaries
That's all : you have root, SuperSu and Knox still "O" and Kingroot it's gone...
Would people please post the full build version of the firmware they have success or failure with, so others are aware of which ones work.
has this method been verified by other users?
Share your experience please!
It's brand new...
Verified by myself
Have you maintained root after reboot?
ashyx said:
Already tried it, v4.5 is posted in my kingroot thread, didn't work on lollipop for t805.
Neither did supersu me, binary always fails to update, once it did manage after several tries, but root is lost after reboot.
Supersu me is just the same script as posted in the kingroot thread. Root always lost after reboot.
Have you maintained root after reboot?
Click to expand...
Click to collapse
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
stefan.pilsu said:
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
Click to expand...
Click to collapse
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
louiscar said:
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
Click to expand...
Click to collapse
Super-Sume install SuperSu
Update binaries and done
I waiting also others to confirm
stefan.pilsu said:
I waiting also others to confirm
Click to expand...
Click to collapse
Ok Thanks for putting this up, if it's reliable it will save a lot time for many.
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
angelshie said:
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
Click to expand...
Click to collapse
Super_Sume make all this "work" with one click !
Ok guys, thanks for confirming, Sweet
Thanks for the tip. This worked perfectly. I installed Kingroot 4.5. When Kingroot runs scroll down and press "Try it" and it rooted. I then immediately installed Busybox from the Google Play store and ran the smart installer. After a successful install of Busybox, I then installed Super-Sume from the Play store. I ran Super-Sume and it installed Super SU and removed Kingroot. After that, I opened Super SU and allowed it to update the binary. Rebooted. I checked root with Root Checker app and checked Knox with an app called Knox Status on the Play store. Root is still active and Knox is still at "0". I powered off, then restarted again. Root has stayed.
I did this on a brand new US region SM-T700 pulled straight from the box and updated to Lolilipop from OTA.
System Version:
SM-T700
LRX22G.T700XXU1BOE3
*ROOT WORKING !! SMT-700 OTA 'lollipop'
Confirmed working on Lollipop NEE-T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits got to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
I've told you ...
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
It does not appear to work on T707a with 5.0.2.
Maybe ashyx could help.
What exactly didn't work for you ?
stefan.pilsu said:
I've told you ...
Click to expand...
Click to collapse
Do you think this is likely to work for KitKat ANL1? I already downgraded as part of Ashyx's tutorial to ANF7.
My only reservation to going to Lollipop is that I want to use the Xposed framework which I think is still in it's infancy for 5.x or still not compatible.
So before this my options are to keep the original Kitkat by Flashfire - ANL1 or go directly to Lollipop. For the latter I could just get the OTA and do this method now. But not sure if I go to ANL1 kingroot will work as easily
If not I'll continue in the normal way I guess.
Once you have root with Kingroot install Super Sume and run it.
Kingroot 4.5 from ashyxs tread works for me.
Super-Sume just install busybox, SuperSu and get rid of Kingroot.
Why not use Flashfire to install whatever you want: KK or L ?

SuperSU 2.66 beta on Shamu

Please write your experience with SuperSU 2.60 / 2.61 / 2.62-3...2.66 on Shamu.
2.56 didn't work on my unlocked, unencrypted 6.0.0 (MRA58R)
Systemless 2.62-3 with works as a charm with my 6.0.1.
I dirty flashed 6.0.1 system.img and boot.img, then I flashed SuperSU 2.62-3 (in TWRP). I stayed unencrypted.
Xposed, ES File Explorer, Double tap 2 wake, Greenify, BetterBatteryStats ... work perfectly.
Edit:
2.62-3 works for some with 6.0.1. and with Android Pay
2.52 has been working fine for me since mm has been out, running on MRA58R now. Have not tried 2.6 but 2.49 was also working perfectly. If you need android pay to work then 2.6 or there are other options like custom ROMs that have it successfully working
Sent from my Nexus 6 using Tapatalk
Running it here without issue. Also had it running on mra58r.
The only casualty I suppose was/is es file explorer. It could not gain root access for some reason.
I am rooted, unencrypted and have the latest Elite kernel.
Sent from my Nexus 6 using Tapatalk
Using 2.6.1 and brand new 6.0.1 fresh install and Android pay is working flawlessly!
Does anybody have a downloadlink for 2.61, can`t find it anywhere
Nevermind, found it.
gee2012 said:
Nevermind, found it.
Click to expand...
Click to collapse
Adding the link to the post would have been useful!
f2 said:
Adding the link to the post would have been useful!
Click to expand...
Click to collapse
Thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344. Link http://forum.xda-developers.com/attachment.php?attachmentid=3568267&d=1449521348.
belek1979 said:
Please write your experience with SuperSU 2.60/2.61 on Shamu.
2.56 didn't work on my unlocked, unencrypted 6.0.0 (MRA58R)
Maybe 2.60/2.61 will work with 6.0.1?
Click to expand...
Click to collapse
Although 2.61 is installed
TWRP says: no root
Root Explorer says: you are not rooted
Quick reboot says: no root
NLBeev said:
Although 2.61 is installed
TWRP says: no root
Root Explorer says: you are not rooted
Quick reboot says: no root
Click to expand...
Click to collapse
Root Checker Pro, BusyBox Pro said i was rooted and the Franco FKU app has root too. Maybe its a problem with apps not adapted/compatible with systemless root (2.61) yet.
gee2012 said:
... Maybe its a problem with apps not adapted/compatible with systemless root (2.61) yet.
Click to expand...
Click to collapse
I am using the lite Rom 6.0.1 of @Danvdh. Works, but with Franco's kernel (r35) installed, problems with the sim-card. (Not recognized).
Going back to 6.0...... Too many issues.
NLBeev said:
I am using the lite Rom 6.0.1 of @Danvdh. Works, but with Franco's kernel (r35) installed, problems with the sim-card. (Not recognized).
Going back to 6.0...... Too many issues.
Click to expand...
Click to collapse
Well i`am on stock 6.0.1/TWRP/2.61/Franco r35 and so far no issues, everything working well :fingers-crossed:
gee2012 said:
Well i`am on stock 6.0.1/TWRP/2.61/Franco r35 and so far no issues, everything working well :fingers-crossed:
Click to expand...
Click to collapse
Now back on 6.0. Will retry with a full wipe.
NLBeev said:
Now back on 6.0. Will retry with a full wipe.
Click to expand...
Click to collapse
Good luck, from what i understand systemless root works best on stock.
gee2012 said:
Good luck, from what i understand systemless root works best on stock.
Click to expand...
Click to collapse
Did a full wipe and flashed again the lite Rom 6.0.1 of Danvdh. This rom is stock based.
After reboot I restored the 6.0-data from a nandroid backup with TWRP. Root checker says 'no root'.
Now last try with full wipe and restore from Google.
At this moment my N6 is restoring the apps from Google take a long time, but root checker says there is root access.
So this update needs a complete wipe and factory reset.
NLBeev said:
Did a full wipe and flashed again the lite Rom 6.0.1 of Danvdh. This rom is stock based.
After reboot I restored the 6.0-data from a nandroid backup with TWRP. Root checker says 'no root'.
Now last try with full wipe and restore from Google.
At this moment my N6 is restoring the apps from Google take a long time, but root checker says there is root access.
So this update needs a complete wipe and factory reset.
Click to expand...
Click to collapse
Maybe thats it, i didn`t mention i actualy did a full wipe prior to rooting.
gee2012 said:
Maybe thats it, i didn`t mention i actualy did a full wipe prior to rooting.
Click to expand...
Click to collapse
I did some reading and trial with the lite rom of Danvdh. What seems important is that SuperSU 2.6x is flashed as the last file after flashing system stuff, like mods, kernel.
NLBeev said:
I did some reading and trial with the lite rom of Danvdh. What seems important is that SuperSU 2.6x is flashed as the last file after flashing system stuff, like mods, kernel.
Click to expand...
Click to collapse
Yup, that what i did too. Thought you knew that
gee2012 said:
Yup, that what i did too. Thought you knew that
Click to expand...
Click to collapse
It is logical, but I was too busy with trying to flash without wiping the data partition.
gee2012 said:
...about wiping data...
Click to expand...
Click to collapse
I managed to update from M6.0 to M6.0.1 with data kept.
Important is that the system partition does not contain su-stuff of previous versions.
In TWRP I wiped the M 6.0 system and caches, but not the data.
Flashed the lite 6.0.1 rom of Danvdh;
Flashed Franco's kernel r35;
Flashed SuperSU 2.61;
Reboot - TWRP button 'do not install SU'.
Needed to restore settings (dpi), layers and the black themed apps of the TBO team.
I dirty flashed from stock rooted 6.0.0 to 6.0.1 today and rooted using Systemless 2.62-3. Everything is working great so far.

Root in 6.0.1

Hey guys! So I read around about rooting Android 6.0.1 and I only see systemless root. I am rooted right now using systemless root and it works fine, but my question is, is there a way to root 6.0.1 with traditional system root? Or is systemless the only way? Just curious really. Will systemless most likely be the future of rooting and the way it's going to have to be done from now on to keep Android Pay working?
Sent from my Nexus 6
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
Thanks for the response! And I wonder if it will be what it is for now! It's the only way to keep Android Pay working while the device is rooted correct? Android Pay refuses to work with a traditionally rooted device?
Sent from my Nexus 6
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
I did. I still use SU2.52. But only until this weekend. I'm switching to systemless too.
Actually building a permissive kernel is really straightforward, needs one line of code added. The build is about five minuters then with abootimg you can just replace the existing with the newly buil kernel in the boot.img, and flash it.
I can give you details if you're interested.
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
Mine works perfectly.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Krzysiek_CK said:
Mine works perfectly.
Click to expand...
Click to collapse
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
H4X0R46 said:
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
I tested 2.61, is problem fixed in 2.62.3? because I must flash 6.0.1 and setup phone again!
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
simms22 said:
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
Click to expand...
Click to collapse
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
H4X0R46 said:
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
Click to expand...
Click to collapse
ive no use for pay, so never tried. i assume its broken..
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
carmatana said:
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
Click to expand...
Click to collapse
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
H4X0R46 said:
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
Click to expand...
Click to collapse
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
I would say yes, I'm 90% sure but could be wrong. I would flash the a new update with fastboot.
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
Any mod stops ota's. Root, kernels....You will have to flash full images to get updates. You can skip the userdata part and save your apps and data. But you will have to flash.
Not a big deal, it an extra couple of commands just like the kernel you want to flash.
Thanks!
kamkar said:
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
Click to expand...
Click to collapse
Clean 6.0.1 followed by systemless root installation as expained in the Root done right thread.

Flashable OTA?

When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
idbl_fanatic said:
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
Click to expand...
Click to collapse
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
WOW thank you, I didn't know that TWRP did this.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
Ok, I am a little confused, I am trying to apply the MRA58K from LMY48T OTA found here: http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 in the ZIP file, I am not finding system.img, or boot.img
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
idbl_fanatic said:
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
Click to expand...
Click to collapse
yup
simms22 said:
yup
Click to expand...
Click to collapse
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
idbl_fanatic said:
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
Click to expand...
Click to collapse
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
zelendel said:
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
Click to expand...
Click to collapse
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
idbl_fanatic said:
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
Click to expand...
Click to collapse
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
zelendel said:
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
Click to expand...
Click to collapse
That makes sense, maybe I'll go to MMB29K instead.
Systemless root or systemless exposed?
Sent from my Nexus 6 using XDA-Developers mobile app
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
putridfoetus said:
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
Click to expand...
Click to collapse
Thank you, I just reinstalled 6.0.1 MOB30M and it works!
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
cL0uD` said:
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
Click to expand...
Click to collapse
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
idbl_fanatic said:
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
Click to expand...
Click to collapse
Yes, used, Great job, Mr Chainfire

[SOLVED] Can I really switch from SuperSU ?

Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.
I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.

Categories

Resources