Database Users

[Q] Why no su access after it's rooted?

I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!

KJTseng said:
I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!
Click to expand...
Click to collapse
I can't see any reason why you'd become unrooted unless you either replace the system partition (via an update or rom change or fastboot flash or whatever) or delete the binary yourself. If you didn't do either of those it could be either a problem with supersu, a problem with the binary, or a problem with your kernel. Try putting the root binary (su) back on the phone and trying again, and if that fails try using SuperUser instead of Supersu. If neither work you may need to do a factory reset and try again.

did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.

cooljais said:
did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.
Click to expand...
Click to collapse
oh, yes!!!! I just upgraded a couple of days ago from JRO03D to JZO54K. THANK YOU!!
I tried re-rooting again (w/o flashing custom recovery) after I upgrade Nexus Root Toolkit to v1.5.4 t support 4.1.2, But get stuck at the message "waiting for your device to finish booting back up." Nexus 7 is at the TWRP mode and can't get out of it. So I reboot to bootloader mode and eventually the toolkit tells me to run SuperSU and Busybox. Still doesn't work since I still don't have super user access. What shall I do next? I know there are still few more steps after the TWRP.

[Q] Root stock 4.2.2 without lost apps & data?

I have been reading through previous threads but I cannot find anything that specifically answers the question I have.
I had stock Android 4.2.1 (which was rooted) and now that it has updated to version 4.2.2 I am unrooted (even though upon boot it still displays the unlocked padlock but I assume that is something different).
So my question is, is it possible to root my current stock 4.2.2 and keep all of my apps and data? or is the only solution to wipe it all and start again if I want root access?
As a side note and to anyone who is reading this if you are currently rooted install this https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en and hopefully that should be the end of having to worry about losing root but in hindsight it is obviously to late for myself.
Thank you very much to anyone who can help me!

You didn't read enough threads.
The bootloader has been replaced, but is still unlocked.
The OTA also overwrote your custom recovery with a new stock recovery, but that's only a temporary issue - read on.
Because the new bootloader is also unlocked, that means that you can re-install a custom recovery just the same way you did it originally (with fastboot or a toolkit which also uses fastboot), but without the unlocking step (which wipes everything).
After you have a custom recovery in place you are free to do whatever you want - you could just reinstall a minimal SuperSU/Superuser overflash. This leaves everything unmolested, and you have root back.
Note that the superuser software is still on your tab; it has been temporarily disabled because the 'su' binary got its' permissions reset by the OTA install. Without doing a new over flash you could simply perform (with the custom recovery booted)
adb shell mount /system
adb shell chmod 6755 /system/xbin/su /system/bin/su
adb shell ls -l /system/xbin/su /system/bin/su
(it's one or the other of those locations depending on whether you are using SuperSU or Superuser; in any event you should see "swxs-xr-x" if you have the correct setuid/setgid permissions set)
good luck

The unlocked padlock means you're bootloader is unlocked, which is fine.
Yes it is possible, I suggest reading the stickies which explain how to do this. Basically, you'll need to flash a custom recovery via fastboot, then download a SuperSU flashable zip file (or Superuser) to flash in the custom recovery, and that's all.
Beaten by bftb0.

Thank you both very much for your responses!

Question about systemless root and TWRP

So I'm following the guide on rooting, unlocking, etc and confused about systemless root and traditional. I was going to do systemless to keep android pay alive and it seems that is the future. However, I'm at the point of installing TWRP. But the guide mentioned "TWRP isn't able t persist without modifying system, so you'll lose it after booting into Android, you'll need to flash/boot it to access it again". What does this exactly mean? I read it as that after I reboot my phone after doing something in TWRP, than TWRP becomes non existent. And I'd have to flash it every time I wanted to get into TWRP. Is this correct? Seems not very smart because if something happens on my phone, I'd like to be able to boot right into my TWRP recovery to restore a stable version.

I don't know why it says that but I allow TWRP to make system modifications and I have systemless root with AP working.
You definitely don't want to let TWRP install it's version of SuperSU though. When it gives you the option select "Do not install".

I would like to share my experience on flashing systemless root with TWRP on my Nexus 9:
1. Reboot to bootloader and perform fastboot boot TWRP.img (TWRP.img is the filename of TWRP IMG file). Yes, TWRP is temporary and won't keep after reboot)
2. If TWRP prompts you to decrypt /data partition, simply skip that
3. Don't allow /system modifications
4. Use adb sideload to install systemless SuperSU
5. Directly reboot to system after installation. The device may reboot multiple times, just let it finish.
SuperSU should now appear in the app tray. This method works well for me.

Much info on systemless root here
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105

Rooting Stock XT1575 Marshmallow 6.0

This device seems to be a little trickier to root compared to my old Galaxy S3.
I just received a brand new Moto X Pure, XT1575 (North American variant I'm assuming since I bought it from the US).
It's currently running Marshmallow 6.0, and has been OTA updated to the Feburary 2016 security update.
I want to keep the stock ROM, but I want it to be rooted. XPosed would be nice as well, but not necessary. I do not want any custom ROMs, just the stock ROM rooted.

To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Fantastic advice!
Sent from my XT1575 using XDA-Developers mobile app

You'll have to use a very specific - older systemless root though. I think supersu-2.64, but I'll let someone else confirm that. The other superusers will not work.

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Sorry I been away from the rooting methods for too long (since my note 2) I already unlocked the bootloader on my phone but to install twrp can I still follow this tutorial? TIA
https://youtu.be/iPspDlbRf88
Sent from my XT1575 using XDA-Developers mobile app

jason2678 said:
To root you have to unlock your bootloader, install TWRP, and use TWRP to flash supersu.
For the most part just follow the Heisenberg guide and you'll be fine.
Since you're on marshmallow make sure to install supersu systemless or your system won't boot. Don't use the old supersu linked to the Heisenberg thread. Stay away from the ivcarlos method linked there too; newer versions of supersu handle all that boot image patching automatically. You just have to be a little careful about what version of supersu you use. Supersu version 2.62 works fine. I can vouch for supersu 2.67 too, but you have to force it to install systemless. Enter this in TWRPs built-in terminal or an adb shell before flashing or it will try to install using the traditional method and you'll freeze on the big M when you reboot:
Code:
echo "SYSTEMLESS=true" > /data/.supersu
Just use TWRP to make a backup before you mess with rooting so you have something to fall back on in case things go wrong.
Click to expand...
Click to collapse
Thanks!!! that little line of code for TWRPs built-in terminal did the work

rmaspons said:
Thanks!!! that little line of code for TWRPs built-in terminal did the work
Click to expand...
Click to collapse
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu

martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.

martyxng said:
Can someone clarify? I also just got the same exact phone and installed the Feb OTA updates, then unlocked the bootloader.
I just need to enter the following in the terminal and THEN flash Supersu? Is the code below what "forces it" to install systemless? Can I use the newest version of supersu if I pop this line in first?
echo "SYSTEMLESS=true" > /data/.supersu
Click to expand...
Click to collapse
It didn't work for me via adb command.... Had to use TWRPs built-in terminal. Just wrote wrote the line, as it is, go back to the main menu and flash Supersu (I used the latest one: 2.67) just as you normally do. Then reboot. No more stock in the M logo

jason2678 said:
That command creates a text file /data/.supersu with one line in it "SYSTEMLESS=true". Supersu checks for that file when you flash it, and if it is found with sytemless set true installs systemless.
2.67 is the newest zip I tried it with, but I see no reason why it wouldn't work with newer versions.
Just be sure to backup /boot /system and /data first. If anything goes wrong restoring those will get you back up and running.
Click to expand...
Click to collapse
Thanks! This did work for me. I am now rooted.

I am using twrp 3.0.0.0 I used 2.62 however when I tried to click the option in the terminal keyboard for the = (equal sign) I keep getting a blue screen. 3.0 keyboard works ok. I entered the, echo "SYSTEMLESS=true" > /data/.supersu and pressed the go button. It showed up on the main terminal screen. Im a bit confused at this point....do I flash supersu from my pc using flashboot on the bootloader page? or download the supersu.zip to my phone and use twrp to flash it? When twrp asked to flash supersu I did that and wound up stuck on the big M again. I think I restored my phone about 6 times so far. lol

Flash in recovery. Use 2.62-3.

So using 2.62.3 will void having to type SYSTEMLESS=true" > /data/.supersu. or do u still have to type that in terminal? Plus using the twrp-3.0.2-0-clark. Should I use and older version?

No just flash.

Flashed Supersu 2.76 on top of xt-1575 18-4 image without any problems usung TWRP 3.0.2.
I did add .supersu text file to /data just as an insurance.

Nuts. Didn't see the part about doing a backup first (hitting head, as this isn't my first rodeo). Too anxious I guess. Now I'm stuck at the M android screen. (didn't do the "SYSTEMLESS=true" > /data/.supersu" command). Any way to fix or am I just screwed?
I can get to TWRP, so theoretically, I could flash a stock version of Android back onto it. Anyone know where I can pick one up?

Did the same ****. Was so excited getting the phone and didn't read the systemless =true crap for M. Didn't do a back up but got a system file from Motorola. You can pick one up here to start over. http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

Anxiety might lead to unexpected results
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance

eat-man said:
Can anyone make and post a video step-by-step on how to do this? Last night I was about to root my new Moto X Pure X1575 (No updates installed, need to freeze the process to avoid making the root process more difficult) and if I rushed I could've made a HUGE mistake. Mine is running Android 6.0 (Marshmallow), was about to use previous and experimental methods but after reading this post I'd rather wait and make sure everything works.
Btw, I got my phone directly from Motorola, added a bit more memory through Moto Maker (32GB), will this make any difference in terms of getting the root access?
Thanks in advance
Click to expand...
Click to collapse
Not really sure what you need a video for, the process is simple and the same for all Gen3/4 Moto devices... the chanced of "breaking" something are near zero. You need fastboot working, that is on you.
1) Unlock the bootloader
2) Download the latest TWRP and SuperSU. Place TWRP img in your fastboot directory and SuperSU zip on your device so you know where it is, internal storage or SD card is not relevant.
3) Start the bootloader, either with `adb reboot bootloader` or power off and hold VOL DN and then press and hold POWER until the menu comes up
4) Start TWRP with `fastboot boot twrp-3.0.2-0-clark.img` and backup
5) Go to TWRP's Advanced menu and select Terminal
6) Enter `echo SYSTEMLESS=true>>/data/.supersu` press enter , exit, and Home button
7) Install (Flash) SuperSU ZIP file, clear caches if you wish but it isn't necessary.
8) Reboot
That is all there is too it

man u are awesome it took me a while and just stumbled on to this and u couldnt have made it less confusing

[GUIDE] Change KingoRoot to SuperSU

Follow this ROM Installation Guide.
Root it with KingoRoot.
Flash patched aboot.img by typing "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7" command in Android Terminal Emulator App, I don't like to use PC.
Then download ChainFire SuperSU from GooglePlay.
On first application start it will ask to install su Binary, say Yes.
Wait about 5 minutes or until it fails…
If so, don't worry, be happy.
Reboot…
Try again.
It must ask for Root Authorization!
Continue Rebooting and tying again and again, until you see su binary installed successfully!
Now you can dance, you Switched to SuperSU
After that you can remove all KingoRoot sh**t and install SuperSU like System app in application options…
I'm still experimenting with this rom, so I'm keeping KingRoot and SuperSU apps, for reroot my device if I will reflash KDZ.
Since now we have Working TWRP…
Simply flash it via recovery.
There are two ways available : System(by system partition) and Systemless (by Repacking and flashing Modified Kernel Image)…
Google it to know more ?
(1) Download this: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
(2) Place it in /sdcard/
(3) Reboot to TWRP.
(4) Select "Install" and go to the folder where you had placed the SuperSu zip and select the zip.
(5) Swipe to confirm flash.
(6) Reboot to system.
(7) Remove kingoroot's supersu.

D_Vovan_238 said:
Follow this ROM Installation Guide.
Root it with KingoRoot.
Flash patched aboot.img by typing "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7" command in Android Terminal Emulator App, I don't like to use PC.
Then download ChainFire SuperSU from GooglePlay.
On first application start it will ask to install su Binary, say Yes.
Wait about 5 minutes or until it fails…
If so, don't worry, be happy.
Reboot…
Try again.
It must ask for Root Authorization!
Continue Rebooting and tying again and again, until you see su binary installed successfully!
Now you can dance, you Switched to SuperSU
After that you can remove all KingoRoot sh**t and install SuperSU like System app in application options…
I'm still experimenting with this rom, so I'm keeping KingRoot and SuperSU apps, for reroot my device if I will reflash KDZ.
Since now we have Working TWRP…
Simply flash it via recovery.
There are two ways available : System(by system partition) and Systemless (by Repacking and flashing Modified Kernel Image)…
Google it to know more
Click to expand...
Click to collapse
I rebooted like +10 times and still nothing. Also it doesn't ask for root authorization after reboot

Krystiannnnnn said:
I rebooted like +10 times and still nothing. Also it doesn't ask for root authorization after reboot
Click to expand...
Click to collapse
Follow this:
(1) Download this: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
(2) Place it in /sdcard/
(3) Reboot to TWRP.
(4) Select "Install" and go to the folder where you had placed the SuperSu zip and select the zip.
(5) Swipe to confirm flash.
(6) Reboot to system.
(7) Remove kingoroot's supersu.