I upgraded to 4.2.2 and it seems I have lost my Root Access. I has SuperSU Pro with OTA Survival mode on installed as a system app before the upgrade but it seems it did not keep Root access. I used Root Checker and it's telling me I am not rooted. I am still seeing the unlock Icon at boot so I assume my boot loader is still unlocked.
Is there an easy way to get my Root access back?
Thanks.
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Thanks for your reply. I will try to follow the steps you outlined however, most of what you said is new to me. I initially rooted my device with the Nexus 7 Toolkit so it was a fairly simple procedure. I have never used the SDK or twrp are there any tutorials on how these work on 4.2.2? Also they will probably update Nexus 7 toolkit to support 4.2.2 eventually, so if I can't figure out the steps indicated I may have to wait.
Another noob question: After the update I can still open busybox and SupeSU, how come these apps still run if I am no longer rooted?
gastonwalpole said:
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
hey man yeh i didnt get how i still had supersu but i definitely wasnt rooted. its all a bit complicated aye, basically you need to download the andriod sdk bundle [now called adt bundle] for whatever you have eg. windows 7 32/64, and the jdk java development kit, look for guides on these, there two youtubers who have helpful channels: driodmodderx and wwjoshdew. also search threads here. you want your device to be recognized by the comp, sdk and jdk do this. twrp is a custom recovery that you can use to flash roms zips etc, you use your comp to send this custom recovery to your device. i would have stayed on 4.2.1 because i dont think you can use custom roms on 4.2.2 bootloader, still 4.2.2 is very smooth, i like it.
Sent from my Nexus 7 using XDA Premium HD app
gastonwalpole said:
Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb.
Click to expand...
Click to collapse
Boy did your post make me happy! I had the exact same problem. Managed to install 4.2.2 with modified OTA update (original was failing due to some discrepency in GoogleCalendar.apk) but even though I had SuperSU in survival mode, I lost my root. I've been trying all afternoon to connect via adb to my Nexus and just couldn't - it was always offline.. I tried 3 different computers and my SGNII phone (which worked) but N7 just wouldn't stop being offline...
I hope this is the solution! Thanx a BUNCH!
One question - my bootloader is unlocked telling by the icon on boot "google" screen - will I lose my apps and data after "re-rooting" that is, after flashing custom recovery and SuperSU?
THANX!!!!!!!!!!!!!
you won't lose anything by flashing recovery or su
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
burnitdown said:
you won't lose anything by flashing recovery or su
Click to expand...
Click to collapse
Great, managed to do it, everything fine. Thanx again!
SimonP2 said:
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
Click to expand...
Click to collapse
And if you can't wait, the workaround is there on http://www.wugfresh.com/nrt/ under IMPORTANT NOTICE.
Related
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...
yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.
NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
try:
http://forum.xda-developers.com/showthread.php?t=1796109
comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...
I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2
I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock
Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
What you are doing wrong is using a toolkit. Follow these instructions. http://forum.xda-developers.com/showthread.php?t=2018179
I use mskip's Nexus 4 Toolkit without any issues. So far I've used it to root, install clockworkmod recovery and flash the stock image after messing up a build prop edit. Saved me a lot of headaches as I haven't used adb or fastboot commands in over a year, don't even have the sdk installed any more. This is the first phone since I got my Incredible in 2010 that I actually wanted to put a custom recovery on and play with.
Here are some basic questions. Did you unlock your boot loader? Do you have usb debugging enabled? Does your device show up when when your plugged in and booted up into fastboot? Do you have the correct drivers installed? Which recovery are you trying to install and did you try the other one available? Did you use the toolkit to root and did it work?
Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.
KyraOfFire said:
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.
Click to expand...
Click to collapse
While I agree there are "really easy" ways to do things, I was trying to point him in the direction of learning.
Obviously since they don't know how to flash a recovery, they probably aren't familiar with much else.
Learning how to do things properly never hurt anyone.
Sent from my Nexus 4
Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp...
...Am i doing anything wrong?
Click to expand...
Click to collapse
El Daddy is correct.
Toolkits are silly on Nexus devices, for Nexus the simplest way is flashing via faboot. At the very least take the time to learn from the guide that El Daddy provided a link to. With that knowledge you'll be able to resolve issues like this and help others who get stuck.
Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...
All the toolkits are are scripts that run the fastboot and adb commands for you, they're nothing complicated and IMO from someone with experience I prefer using them now as I no longer have the sdk installed. Gave up on custom ROMs, my own and others, a long time ago.
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Toobie said:
Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...
Click to expand...
Click to collapse
Actually it's fastboot not adb that you use to flash recoveries, two different animals. and to the poster recommending ROM Manager, its kind of borked right now and I wouldn't use it to flash anything.
Edit: spoke too soon on ROM Manager looks like Koush updated it and it appears to be working properly. This was the first app I ever bought back in 2010 when I first rooted my Eris and couldn't get clockworkmod recovery to install, the moderators at the time recommended ROM Manager to me to get it installed as nothing else worked.
Yeah, but both didn't work.
I used now the adb commands on my one, still remembering them from my Nexus One, and see it works
For sure fastboot and adb will work. I used it very recently when my n4 updated. Just make sure to download the latest cwm. Had a boot loop the first time as I used an old one. Hehehe
Edit: actually not sure if it was the old fastboot files or cwm that caused the error. Anyway I updated my sdk so everything works well
Sent from my Nexus 4 using Tapatalk 2
Actually all the tools booted the phone fine in the fastboot mode, telling me flashing the recovery is fine.
But every time i wanted to reboot in the recovery i got this android roboter with the red alarm...
with the normal adb commands everything was really fine!
You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2
thephantom said:
You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sounds great, will try that.
Thank you.
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?
Newbie here.
Pls guide me..
Many tks!
Sent from my SM-N9005 using xda app-developers app
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Issues with rooting (4.4), stuck after flashing recovery
I just got my Nexus 10, and unlocked the boot loader, then flashed the custom recovery. All was fine, and I could boot into recovery, however recovery can not mount any filesystems. So I rebooted, now the Nexus does not boot, but hangs on the intro animation, normally meaning in my experience that the kernel is looped and is no longer finding (or else) booting the OS. I've tried booting 3 times.
So then, the steps I took,
enable USB debugging
were copy over the zip file for supersu
reboot to (fastboot mode), verify device
unlock boot loader "fastboot oem unlock"
flash the recovery "recovery-clockwork-touch-6.0.4.3-manta"
reboot into recovery
Failed to mount filesystems
for instance "E: Can't mount /cache/recovery/command or E:Can't mount /sdcard .... (you get the idea).
rebooting again a leaving it does nothing.
I also tried side loading a new image in my case "ThunderKat_manta-KRT16S-20131201" and after installing the "UniversalAdbDriverSetup", I was able to do so, I also was also able to side load the google apps "GoogleAppsPack-4.4-20131128", in both cases I get a success message after the install, however there after when I attempt to reboot I'm still stuck looking at the boot animation.
Now I'm really confused as if if the OS was destroyed when I unlocked the device, then side load of the zip contains a new kernel and OS image so it should be working, but it is not. In fact, recovery while still working throws the same can not mount exceptions after the flash as it did before (I rebooted) as I was previously getting and a factory reset, fails to mount /data, but does flash /cache and sd-ext without issues, so again I'm lost as to what to do.
Best guess I have is that partitions such as /data are just missing, I have no idea the state of teh device in such a case, but recovery and side loading using adb are working, how do I recover a working ANDROID OS from here?
Thanks,
ERIC
stuck in loading screen
Hi,
i just got my Nexus 10 yesterday. I tried to root it, but it is stuck in the loading screen. What can i do now? Can i like undo it to get it back to work?
I have the same issue egandt described.
Edit: I just got it back with this tutorial to android 4.2.2 and now i am updating it back up
nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
I unlocked nexus10,
Flashed cwm,
Installed su, but whn i turned it on, su not found, rootchecker shows no root access..
I also encounter bootloop initially,
Need to wide data / factory reset then its normally booted..
Sent from my SM-N9005 using xda app-developers app
Agreed the factory reset was required to fix the issues I encountered, then installing super-su worked.
I still cannot root the Nexus10..
Any one can help?
Thanks in advance!
XxLordxX said:
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Click to expand...
Click to collapse
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
xing369 said:
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
Click to expand...
Click to collapse
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
shimp208 said:
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
Click to expand...
Click to collapse
Thanks for your kind offering of hands!
Last night I tried again to re-flashed latest TWRP as well as latest SuperSU.
I ran 2x Root Checker,
1 said rooted,
1 said no root access, no BusyBox available.
I tried some apps like GMD Gesture, no working or no root access.
So,
Should I redo everything: enable USB Debugging then unlock bootloader then flash CWM then install SuperSU?
I initially gone thru above steps w/o enabling USB Debug..
Many thanks!
Sent from my SM-N9005 using xda app-developers app
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
xing369 said:
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
fritzhy said:
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
Click to expand...
Click to collapse
Very much appreciated for reviving my nexus!
However, after flashing latest TWRP, and installed SuperSU 1.80,
It seems my nexus still unrooted.
Any ideas?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
fritzhy said:
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If it's needed the app will say so when you open it.
fritzhy said:
If it's needed the app will say so when you open it.
Click to expand...
Click to collapse
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Not that I can think of, nope...
Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help
First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ
I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade
I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Easily got my root back using Wugfresh toolkit.
Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.
[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.
[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.
If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app