I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..
Related
this may have been asked, but i'm new to the nexus 7. i rooted it right away, and put TWRP on. probably shouldn't have but i like doing nandroids. i was excited for the OTA and want to just install it since my tab got it, but it won't obviously since i've got a custom recovery (duh i should've thought of that..) and i don't want to go flashing roms yet (i like keeping everything stock right away, it's so smooth)
so my question is, is there a way to go back and flash the stock recovery somehow so i can OTA, then put TWRP back on? i can't find the stock file to fastboot flash or anything
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
kangy said:
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
Click to expand...
Click to collapse
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Alright try this.
Go to SuperSU settings and and click on Reinstall under Cleanup, it will give you a prompt and tell you it will self close and to re-install from the market. (Mine never fully uninstalled which I assume is due to it being flashed to ROM, I checked under the App manager and it only had a downgrade option so) Anywho. If it did uninstall go ahead and redownload it from the market, if it didn't check the market anyway, the Dev published and update for it to help with 4.2 multi users.
Once you get it reinstalled and/or updated from the market go back to the settings and Toggle off Enable Superuser, close the app, re-open and then re-enable superuser. You probably will want to give it a reboot at this point. (Ive restarted my device a hundred times since going to 4.2 from trying to work through the bugs. Once you restart test a root app. I used Adaway for the test. Important, if the app fails or gives an error about not having root, try again. After I went through all of those motions SuperSU was pretty slow for a while with giving root access, usually the second request from the app wakes it up. Since then though it is back to being snappy with zero lag.
Yes, the reason you can't flash TWRP through ROM Toolbox is that requires root. Once you get your SuperSU working try flashing the latest TWRP again, it should only take a few seconds to flash. Let me know how it goes, I'm subscribed to the thread. I may not be the smartest guy on XDA but you are in the same exact boat I was last night!
jayochs said:
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Click to expand...
Click to collapse
First, determine if you have root or not. Open TiBackup, if it opens correctly and you can see all your apps listed, you have root. Otherwise it will say "Failed to obtain root," and quit.
If you have root, then great. If not, you can flash the SuperSU zip in TWRP/CWM: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
I haven't tried flashing superSU, I've always flashed Superuser zip [google "superuser zip"], and then installed superSU from Play store.
Once you have root..
Go to Settings > Security and check allow installation from non-market apps, and uncheck the security feature that checks all apps for being malicious.
Then try it. If you still cannot restore apps, you might have to install them with adb.
I just updated someone's N7 to 4.2, and as usual I backed up everything in TiBackup.
Then I backed up the TitaniumBackup directory [because I had to do a full factory reset].
I then extracted all the .apk.gz files with gunzip. [in linux OR adb: $ gunzip *.apk.gz -- for windows, I suppose you would have to use 7-Zip].
Then I tried to install with pm:
Code:
for i in *.apk; do pm install $i; done
But every one was giving me an error, INSTALL_FAILED_INVALID_URI, I couldn't figure it out. Found a thread said to chmod 755 /data/local, but that did not fix it.
So what I had to do, was on my linux PC:
Code:
for i in *.apk;
do adb install "$i"
done
So I finally was able to batch install my apk files.
after that I restored all apps data.
Nandroid back ups not possible after 4.2 update
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Yordan5 said:
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Click to expand...
Click to collapse
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
mvmacd said:
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
Click to expand...
Click to collapse
NRTK 1.5.5 would not flash the 4.2 custom rom I fed it either. Just kept stalling out with errors that it could not find the zip file.
So I booted into TWRP and flashed it with no problem at all.
I also did backup in TWRP and checked everything but saw no mention that is was a Nandroid backup. How can I be sure?
i'm trying to nandroid back to a 4.1.2 nandroid i have, problem is, twrp has different directories for nandroids in 4.2 than 4.1.2...so it can't find the old nandroids and i can't find the 4.2 dir where twrp stores them now. ugh. such a damn headache for an update that it turns out i didn't want lol
Read my post below, I was having the same problem but got back on 4.1.2. You have to use the twrp explorer and relocate the twrp files since 4.2 moved them.
http://forum.xda-developers.com/showthread.php?t=1992552
Nandroid Downgrade from 4.2 to 4.1.2
Sent from my Nexus 7 using Tapatalk 2
Nexus 4 running CM10 nighty and faux123 kernel
fauxclock app has problem remembering settings when using superuser so previously I installed superSU then removed superuser using root explorer, all good and no problems.
recently I updated CM10 to latest nightly, and as superuser is bundled app it was installed too. so now I have 2 apps for permitting root access but here my problems begin.
Neither app would grant superuser status to apps that requested it
superuser would force close when opened
superSU would start, then try to install the superuser binary, which it could not do as it did not have root privlige
I uninstalled superSU and rebooted, now my launcher pages had all changed back to default (no widgets and stock wallpaper) but worse I had no notification bar and the softkeys where not available. Very hard to navigate the phone
Anyways after an hour I gave up trying to fix the mess I had gotten into and restored my backup from recovery.
So my question is, where did I go wrong? What is the correct procedure for updating the ROM - other than a clean install
Prehaps I should have reinstalled superuser and removed superSU prior to the update?
Any pointers would be appreciated.
Thanks
Rumple
EDIT:
Found some good info on this in the CM10 thread, maybe I should have started there instead of searching all the superSU threads on XDA
problem is now fixed
I'm a bit confused. I'm on my Nexus 7 right now which is running a custom ROM. I can boot into bootloader as well as Clockwork Recovery. However when I just tried to run a backup using titanium, it told me my device is not rooted. Superuser is installed. How can this be? How do I gain root access so I can backup my apps before putting on a new ROM?
abdeviation said:
I'm a bit confused. I'm on my Nexus 7 right now which is running a custom ROM. I can boot into bootloader as well as Clockwork Recovery. However when I just tried to run a backup using titanium, it told me my device is not rooted. Superuser is installed. How can this be? How do I gain root access so I can backup my apps before putting on a new ROM?
Click to expand...
Click to collapse
Download to your Nexus 7, Chainfires SU updater package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Reboot into CWM/TWRP (whichever recovery you're running) and flash it...
(You should find it in the /download folder)
Reboot as normal... you should be rooted.
Rgrds,
Ged.
GedBlake said:
Download to your Nexus 7, Chainfires SU updater package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Reboot into CWM/TWRP (whichever recovery you're running) and flash it...
(You should find it in the /download folder)
Reboot as normal... you should be rooted.
Rgrds,
Ged.
Click to expand...
Click to collapse
So I followed what you said but I was still getting the no root error when launching titanium. Then I went into settings and uninstalled the SuperSU app and viola! Everything is working now
You probably had root disabled under development settings, as is the default. By installing and uninstalling SuperSU, you may have overridden that security setting. It is important to check whether an app is actually handling such requests; otherwise any app could get root without your knowledge.
Sent from my Nexus 7 using Tapatalk HD
I tried a couple of root apps, they didn't work. F***. Adaway and Music2SD. Both tell me that my rooted S4 isn't rooted. I have prerooted MF9, flashed via TWRP. It included SuperSU, with 1.1.3 binary (I think). Okay, after no search results I decided to do something on my own.
First, I opened SuperSU and told it to install itself as a system app. Then, I installed ChainsDD Superuser. That's when I found out my binary was out of date. I chose to update it via Superuser. For some reason or another, it said it didn't update. I went to app manager, cleared data and uninstalled updates for SuperSU. I updated it in the play store and opened it. Then, it told me my binary was out of date - woo! Wait.. normal method didn't work - "Installation Failed!" Okay, try TWRP/CWM method. It rebooted into recovery, flashed some stuff before I could read it, and restarted. Booted right back up. I opened Superuser and it said I was on v0. Went to ChainsDD's site and downloaded the 3.1.3 ARM to flash in recovery. I did that, still nothing. Now SuperSU and Superuser are permanently installed apps (I now have no root to delete them). Whatever. I ran CF-Auto-Root in Odin. After that, both SuperSU and Superuser were removed. I have nothing now.
My question is, what's the best way to get the latest binary on MF9? If i restore from Nandroid, how should I update? If I start from scratch, what binary will I get from CF-Auto-Root?
UPDATE: I'm back to rooted, with SuperSU. I got the update binary notice and chose the normal method. It updated just fine, but I still can't use Adaway or Music2SD. Superuser by ChainsDD still shows v0.. all of my normal apps have root access just fine.
FIX!: My ignorance is to blame here - XPrivacy blocks root access by default on Adaway and Music2SD... I didn't realize it did that!
I tried everything for note 3 to get the SuperSU binaries update to date and I tried all version from the su website or play store. All I get is Installation failed. I am clean stock rooted.
Questions and Help issues belong in Q&A and Help section, thanks!
Thread moved
FNSM
What version of supersu do you have? 2.01?
yup I have the latest SU installed, the problem is that whenever the su app is updated the binaries fail to install, but if I do a factory reset and install the most current version then there are updated... Does the SU app require internet to update/download the binaries?
I was having a similar issue with SuperSU and any all other super user apps. They install, and attempt to update binaries. At this point it never completes the update or the phone crashes and reboots. Haven't quite figured out what the snag is myself.
My issue comes and goes. right now it also asks to update binaries but always fails
I had this issue when I first rooted on stock 4.4.2. So I'm guessing you're on stock? Here download this http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip and instead of installing it. I zip it and go to the common folder. Extract supersu apk and install it. Then run it from the app drawer. Tell me if that works!
That is the not the solution, I have formatted my phone multiple times. I have never been able to update binaries. There has to be a solution to this problem..
jrdnsingh89 said:
That is the not the solution, I have formatted my phone multiple times. I have never been able to update binaries. There has to be a solution to this problem..
Click to expand...
Click to collapse
Why would you format your phone?
I having this weird error when I uninstall an/any app, the android.acore app/service force closes. I tried to wipe clean many times. I just received it again. So whenever I reformat the phone, I can't update the binaries for some reason