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.
To root even tmp root you need Kingroot, from:
http://forum.xda-developers.com/devdb/project/dl/?id=12450
Download SuperSU.zip:
http://download.chainfire.eu/supersu
Install and run kingroot, may take several attempts to tmp root device, once tmp root has been achieved download and flash TWRP.apk from thread below
http://androidforums.com/index.php?threads/918537/
Install twrp recovery and flash twrp recovery,BUT DON'T REBOOT.....FIRST UNINSTALL KINGROOT:
Uninstall all kingroot, kinguser, Chinese char apks
Reboot to twrp with twrp.apk
Make full backup
Flash SuperSU.Zip
1. Get full read/write to system per @jcase tutorial
Can be found here:
https://plus.google.com/+JustinCaseAndroid/posts/KzgyHLgVhwo
If you get a black screen with your led light blinking red, and green hold power button until it powers off, if it keeps rebooting hold volume up while you do this. To get out of booting into black screen with green and red flashing led you have to boot into twrp, and wipe cache, once you wipe cache you can reboot system and should have everything setup, rooted with updated su binaries
Once rooted if you would like to have full read write while keeping your twrp recovery there has been a solution made by Masterchief87 he created two zips one that flashes twrp to boot partition and your boot to recovery, with boot on your recovery partition booting into recovery boots up normal, but with read and write to system, while keeping twrp on boot if you boot normo you boot straight into your twrp recovery
http://androidforums.com/index.php?threads/919330/
Is were you can check md5 and see Masterchief87 original post
Flash for read write to system to boot into android you must choose reboot recovery, or hold volume up + power or you will boot into twrp again.
The second zip allows you to boot into android with only read as it has twrp on your recovery partition and only boot on your boot partition.
Flash for twrp on recovery, this will allow you to flash ROMs, zips, but will only mount system ad read only if you boot into android
To boot into twrp with this one flashed you must use reboot recovery or power + volume up
As always be careful when flashing any zip from recovery, and ones that write new boot.img I myself and or anyone else are not responsible if you brick your device
OK if you permrooted with kingroot, and are having issues getting SuperSU to read binary here is what you have to do
(this means you didn't uninstall kingroot, kinguser,Chinese char apks before a reboot)
Method 1 backup restore
1. Get su binary on sdcard
2. Make a backup of your system and boot
3. Run Restore from twrp(this restores your backup you just made)
4. Don't reboot yet
5. Mount system in twrp
6. Copy su binary from sdcard to /system/xbin/su
7. chmod 755 with twrp file browser
8. Copy install-recovery.sh to /system/etc/install-recovery.sh
9. Chmod 755 install-recovery. sh
10. Copy daemonsu /system/xbin/daemonsu
11. Chmod daemonsu 755
12. Cleanup delete old ku.sud from /system/xbin
Delete /system/use/iku
Delete kingroot.txt in system folder
Reboot
Enjoy SuperSU
Special thanks to jcase for getting the ball rolling
Special thanks to @hroark13 for his twrp.apk and twrp.recovery
Head over to hroark13 thread for more info
http://androidforums.com/index.php?threads/918537/
Special thanks to @Masterchief87 for his boot on recovery and twrp on boot zip
Thanks @tech_yeet for showing us kingroot
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
OBSOLETE
Method 2 terminal/adb copy
2. Get su binary on sdcard
3. use either adb or terminal emulator and grant su
4. Keep the adb or terminal emulator as su and uninstall kingroot, make sure you unchecked all three of the root options in kingroot, keep updated, backup, and the other one I already forgot lol.
5. In adb or terminal emulator use
cat /sdcard/su > /system/xbin/su
chmod 755 /system/xbin/su
cat /sdcard/su > /system/xbin/daemonsu
chmod 755 /system/xbin/daemonsu
cat /sdcard/su > /system/xbin/ku.sud
chmod 755 /system/xbin/ku.sud
cat /sdcard/su > /system/usr/iku/isu
chmod 755 /system/usr/iku/isu
Method 3 twrp copy
If you would like to keep twrp the whole time, and copy files over using twrp this is also possible.
1. boot into twrp recovery
2. mount system: check under mount system to mount
3. copy over files make a backup of su by placing in another folder or using adb and cp
cp sdcard/su /sdcard/ku.sud
copy su to /system/xbin/su
copy ku.sud to /system/xbin/ku.sud
copy su to /system/usr/iku/isu
copy deamonsu(which is also another su so you can make another copy of su as deamonsu)
copy deamonsu to /system/xbin/deamonsu
This should allow SuperSU to see su binary, the problem we are having is that install-recovery.sh instead of running daemonsu as a service with /system/xbin/daemonsu --auto-daemon &
is its just linking to another su in system/xbin and system/usr/iku,
so were just going to replace those extra su with SuperSU binary instead, when we permrooted with kingroot it added a /dev/null for its recovery-install.sh to survive ota update and Its beyond my knowledge to change that, but I can tell you how to change kingroot su to SuperSU, and thus we have SuperSU instead of kingroot.
After binary is pushed in all spots install SuperSU and enjoy!
After this please reinstall twrp recovery so you don't brick your device.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Okay before I try this I wanted to know, do I have to uninstall twrp and install stock recovery? Is there anyway to do this within the os? Also I have already uninstalled kingroot and have kept my root.
You can from twrp just mount system, then use advanced file manager, and copy all files over to their correct places, copy su, and make a nother su named isu, and ku.sud and replace all those files like I showed using twrp it will work.
The following i copied form masterchief in the other zmax post it is IMO a good safe way of having the ability to run the phone in "recovery boot mode" and still having a twarp in the boot partion that will allow a user to reinstall a backup to the "recovery boot" at least that is how I understand it . As I haven't done any of this yet I'm just going on what I have siffed out of the sea of posts.
"Masterchief"
Here is what I've been doing.
I used kingroot to get temp root.
I then used terminal emulator to make backup copies of the stock recovery and boot.img.
I then downloaded and installed twrp, and then rebooted to recovery and flashed the UPDATE-SuperSU-v2.46.zip for permanent root.
After doing this I made two flashable zips.
The first one
(ZMAX_TWRP_&_BOOT_SWITCHER.zip) flashes the boot.img to the recovery partition in order to allow the system to be mounted rw while booted in android, and flashes twrp to the boot partition just in case the s### hits the fan.
The second zip
(ZMAX_TWRP_&_BOOT_RESTORE.zip) flashes twrp back to the recovery partition and puts the boot.img back on the boot partition for whenever I need to restore a backup to fix a soft brick or if I need to flash a zip.
These two flashable zips allow me to have full root capabilities without ever having to uninstall twrp.
Twrp cannot write to the system partition when it is on the boot partition, BUT IT CAN flash
ZMAX_TWRP_&_BOOT_RESTORE.zip. Once you flash twrp back on the recovery partition and reboot recovery, you can restore a backup or flash zips. Once that is done you can flash
ZMAX_TWRP_&_BOOT_SWITCHER.zip again and have full root capabilities. Because of this I can modify the system however I see fit without fear of bricking my phone. It is not the most sophisticated way of doing things BUT IT WORKS.
How can I flash xposed installer with twrp to make it work?
Sent from my (ROOTED) Z970 ZTE Zmax
rkey1000 said:
How can I flash xposed installer with twrp to make it work?
Sent from my (ROOTED) Z970 ZTE Zmax
Click to expand...
Click to collapse
Make a backup first!!
Then open xposed inside framework chose install settings and choose install settings again, and check install from twrp, either auto flash or sdcard flash, then it should reboot to install xposed framework
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Shlickwilly said:
The following i copied form masterchief in the other zmax post it is IMO a good safe way of having the ability to run the phone in "recovery boot mode" and still having a twarp in the boot partion that will allow a user to reinstall a backup to the "recovery boot" at least that is how I understand it . As I haven't done any of this yet I'm just going on what I have siffed out of the sea of posts.
"Masterchief"
Here is what I've been doing.
I used kingroot to get temp root.
I then used terminal emulator to make backup copies of the stock recovery and boot.img.
I then downloaded and installed twrp, and then rebooted to recovery and flashed the UPDATE-SuperSU-v2.46.zip for permanent root.
After doing this I made two flashable zips.
The first one
(ZMAX_TWRP_&_BOOT_SWITCHER.zip) flashes the boot.img to the recovery partition in order to allow the system to be mounted rw while booted in android, and flashes twrp to the boot partition just in case the s### hits the fan.
The second zip
(ZMAX_TWRP_&_BOOT_RESTORE.zip) flashes twrp back to the recovery partition and puts the boot.img back on the boot partition for whenever I need to restore a backup to fix a soft brick or if I need to flash a zip.
These two flashable zips allow me to have full root capabilities without ever having to uninstall twrp.
Twrp cannot write to the system partition when it is on the boot partition, BUT IT CAN flash
ZMAX_TWRP_&_BOOT_RESTORE.zip. Once you flash twrp back on the recovery partition and reboot recovery, you can restore a backup or flash zips. Once that is done you can flash
ZMAX_TWRP_&_BOOT_SWITCHER.zip again and have full root capabilities. Because of this I can modify the system however I see fit without fear of bricking my phone. It is not the most sophisticated way of doing things BUT IT WORKS.
Click to expand...
Click to collapse
Where can I get my hands on those zips?
I updated post it has the twrp zips that Masterchief87 made to allow booting into read/write
Thanks hroak13 for the twrp recovery
Worked, uninstalled kingroot and kinguser. Can't find Chinese character apps.
Looked in app manager and app drawer.
Safe to reboot to twrp?
"a clock is ticking, but it's hidden far away, safe and sound, safe and sound....."
Did you choose uninstall su or unroot, in kinguser APK, there is 3 options, like backup ota survival, and one more the top three choices under kinguser settings need to be done I believe, but I might be wrong, Chinese characters APK will be the last APK in your app drawer doesn't need to be uninstalled, but its just a task manager that will watch your activities I would just delete it, if you can't find it !maybe you didn't install it it normally installs itself right after root, maybe the English very doesn't install it
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Deleted
Changed to thread Hadn't read that till now
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
DroidisLINUX said:
Changed to thread Hadn't read that till now
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Click to expand...
Click to collapse
Thank you sir
Kingroot sure fire root
DroidisLINUX said:
To root even tmp root you need Kingroot, from:
http://forum.xda-developers.com/devdb/project/dl/?id=12450
Download SuperSU.zip:
http://download.chainfire.eu/supersu
Install and run kingroot, may take several attempts to tmp root device, once tmp root has been achieved download and flash TWRP.apk from thread below
http://androidforums.com/index.php?threads/918537/
Install twrp recovery and flash twrp recovery,BUT DON'T REBOOT.....FIRST UNINSTALL KINGROOT:
Uninstall all kingroot, kinguser, Chinese char apks
Reboot to twrp with twrp.apk
Make full backup
Flash SuperSU.Zip
1. Get full read/write to system per @jcase tutorial
Can be found here:
https://plus.google.com/+JustinCaseAndroid/posts/KzgyHLgVhwo
If you get a black screen with your led light blinking red, and green hold power button until it powers off, if it keeps rebooting hold volume up while you do this. To get out of booting into black screen with green and red flashing led you have to boot into twrp, and wipe cache, once you wipe cache you can reboot system and should have everything setup, rooted with updated su binaries
Once rooted if you would like to have full read write while keeping your twrp recovery there has been a solution made by Masterchief87 he created two zips one that flashes twrp to boot partition and your boot to recovery, with boot on your recovery partition booting into recovery boots up normal, but with read and write to system, while keeping twrp on boot if you boot normo you boot straight into your twrp recovery
http://androidforums.com/index.php?threads/919330/
Is were you can check md5 and see Masterchief87 original post
Flash for read write to system to boot into android you must choose reboot recovery, or hold volume up + power or you will boot into twrp again.
The second zip allows you to boot into android with only read as it has twrp on your recovery partition and only boot on your boot partition.
Flash for twrp on recovery, this will allow you to flash ROMs, zips, but will only mount system ad read only if you boot into android
To boot into twrp with this one flashed you must use reboot recovery or power + volume up
I HAVE T-mobile AND MASTERCHIEF87 Flashable boot switcher could have bricked my device, I was lucky and know what I am doing, I urge caution when using these files some devices, and or carrier phones it might not work with. If you brick your phone I am not responsible
OK if you permrooted with kingroot, and are having issues getting SuperSU to read binary here is what you have to do
(this means you didn't uninstall kingroot, kinguser,Chinese char apks before a reboot)
Method 1 backup restore
1. Get su binary on sdcard
2. Make a backup of your system and boot
3. Run Restore from twrp(this restores your backup you just made)
4. Don't reboot yet
5. Mount system in twrp
6. Copy su binary from sdcard to /system/xbin/su
7. chmod 755 with twrp file browser
8. Copy install-recovery.sh to /system/etc/install-recovery.sh
9. Chmod 755 install-recovery. sh
10. Copy daemonsu /system/xbin/daemonsu
11. Chmod daemonsu 755
12. Cleanup delete old ku.sud from /system/xbin
Delete /system/use/iku
Delete kingroot.txt in system folder
Reboot
Enjoy SuperSU
Special thanks to jcase for getting the ball rolling
Special thanks to @hroark13 for his twrp.apk and twrp.recovery
Head over to hroark13 thread for more info
http://androidforums.com/index.php?threads/918537/
Special thanks to @Masterchief87 for his boot on recovery and twrp on boot zip
Thanks @tech_yeet for showing us kingroot
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Click to expand...
Click to collapse
Use MASTERCHIEF87 boot swither zip to get system r/w and kingroot will work first time every time. Then boot into recovery flash the boot restore and flash a system backup only need system. ...Then move the su files into the proper places in system.. It would seem that the problem with kingroot is getting system to be r/w, I tried this five different times today and all five times were on a clean system backup..every one of them worked without kingroot failing or rebooting.
I'm a little confused on what to do here., Im not exactly a noob, but Im still a little confused and would appreciate some help.
I got temp rooted using Kingroot
While temp rooted I installed ZMAX TWRP the lasted VERSION 2.8.6.0 from
( FROM ANDROID FORUM CANT POST LINKS, BUT I THINK IT WAS UPDATED YESTERDAY )
From there I deleted all the Chinese apps
booted into recovery with the TWRP app
Made a backup like I always do,
Installed S.U with no problems.
So I'm wondering if my device is ready to install custom roms yet, I still have TWRP 2.8.60 because I am able to boot into it from just holding the Up Volume button and Power button. Im able to boot into it anytime I want and I still have root. because in a normal android case it looks like it would be ready to go, but then I see these two links below and I get confused ( JUSTIN CASE TUTORIAL FROM GOOGPLE PLUS , AGAIN CANT POST LINKS ) and ( THE LINK RIGHT AFTER THE JUSTIN CASE LINK IN THIS THREAD THAT GOES TO ANDROID FORUM )
CarlJung said:
I'm a little confused on what to do here., Im not exactly a noob, but Im still a little confused and would appreciate some help.
I got temp rooted using Kingroot
While temp rooted I installed ZMAX TWRP the lasted VERSION 2.8.6.0 from
( FROM ANDROID FORUM CANT POST LINKS, BUT I THINK IT WAS UPDATED YESTERDAY )
From there I deleted all the Chinese apps
booted into recovery with the TWRP app
Made a backup like I always do,
Installed S.U with no problems.
So I'm wondering if my device is ready to install custom roms yet, I still have TWRP 2.8.60 because I am able to boot into it from just holding the Up Volume button and Power button. Im able to boot into it anytime I want and I still have root. because in a normal android case it looks like it would be ready to go, but then I see these two links below and I get confused ( JUSTIN CASE TUTORIAL FROM GOOGPLE PLUS , AGAIN CANT POST LINKS ) and ( THE LINK RIGHT AFTER THE JUSTIN CASE LINK IN THIS THREAD THAT GOES TO ANDROID FORUM )
Click to expand...
Click to collapse
Yes your ready for custom roms
Sent from my Z970 using XDA Free mobile app
DroidisLINUX said:
Changed to thread Hadn't read that till now
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Click to expand...
Click to collapse
I'm a little confused man how did my zips almost brick your phone? If you follow all the instructions there shouldn't be any risk at all. I been using them since before I posted em.
Not sure how to proceed
Got temp root with Kingroot
Installed TWRP APK
Successfully installed recovery
Removed all Kingroot related APK's
Now when I hit "Reboot Recovery" in the TWRP APK it does nothing....
What should I do now??
Haggis Warrior said:
Got temp root with Kingroot
Installed TWRP APK
Successfully installed recovery
Removed all Kingroot related APK's
Now when I hit "Reboot Recovery" in the TWRP APK it does nothing....
What should I do now??
Click to expand...
Click to collapse
Download the SuperSU zip from HERE then power off your zmax and boot into twrp recovery by holding power+volume up for approximately 4 seconds and then flash the SuperSU zip and reboot system.