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
Related
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..
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Just reflash the superSU.zip from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in CWM and you should be rooted again. You will not loose any data so no need to backup. Download OTA Rootkeeper from Play to regain root after installing future OTA`s.
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
AAhrens said:
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
Click to expand...
Click to collapse
Try cmd and type: adb reboot recovery. If you see the androidian (stock recovery) you have to reflash the TWRP img file in fastboot mode.
Will this reset my phone? Or does only rooting do that?
You will not loose any data.
Sent from my Nexus 4 using xda premium
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Let me guess, you used a toolkit to root?
a) You did the full OTA, so you lost your custom recovery.
b) flash images through fastboot and skip the recovery.
c) Only after you flash a custom recovery. If your recovery is sitting in the same folder as fastboot and named "recovery.img, simply cd into the fastboot folder in a command prompt and type
fastboot flash recovery recovery.img
d) Not unless you lock or relock your bootloader.
OP, you need to do some more research and uninstall the toolkit from your computer. You know just enough to cause yourself problems, but not enough to know why they happen or how to fix them.
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Rizy7 said:
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Click to expand...
Click to collapse
Thanks all, was able to get it fixed by re-rooting!
I have a Razr M -- if there is a better place to ask this, please don't hesitate to let me know. I am new to this, but trying to learn.
I had the phone rooted and the bootloader unlocked, 4.1.2. I haven't accepted the OTA, but as you'll see below it's a pain because I've lost root and can't freeze the updater. The phone is still unlocked, and TWRP is still installed, but no root.
I had a problem with Safestrap where it would not create new ROM slots. I fixed it with a data format and factory reset. I was able to reroot with Motochopper, and then used Titanium to restore my apps. I must have restored something that the system didn't like, because I got stuck in a bootloop.
I then factory reset again, to start over. Only now Motochopper doesn't root.
I get a success message from Motochopper, Superuser does appear on the phone, but I also get the lines:
sh: /system/xbin/busybox: not found
cp: /system/xbin/su: No such file or directory
Superuser itself says that the binary needs to be updated, but none of the install options (install, recovery install) work. I tried Voodoo OTA Rootkeeper, since I had a protected SU installed, and it didn't work either.
Since I had Safestrap installed, I thought I might be able to get CMOD to a custom ROM slot even if the stock had lost root. I went ahead and created a custom ROM slot and tried to flash the Razr M CMOD 10.1 and gapps to it. I got a success message, but when I boot I just get a blackscreen; I've waited it out for 20 minutes or so, and nothing loads.
I have the Razr 1.20 utility, but frankly I am afraid to use it to try to go back to stock 4.1.2. I don't know what the OTAs have done, and frankly everything I have loaded to the M has bombed, and if I mess with my (now screwed up) stock install, I don't know that I'll be able to recover. But using the 1.20 utility and flashing 4.1.2 is my last idea.
Any help or thoughts? Why the hell did Motochopper stop working? What does this line about busybox mean? Can it be fixed short of trying to go back to stock 4.1.2?
Any help would be deeply appreciated. Because I lost root (and Titanium) I can't freeze the updater any more, which means it's now a matter of postponing every 12 hours. Not my favorite thing. And because my bootloader is unlocked I really hesitate to accept the OTA.
Since you have TWRP installed, get rid of Safestrap, you don't need it. If you're unlocked you can use Utility1.20 with no issues. If, somehow you did install the OTA, and you still have TWRP, then you just need to flash a SU zip in recovery to retain root. However, I think your best bet right now to get everything back to normal is to use the utility.
Sent from my Droid RAZR M using xda app-developers app
Many thanks. A few questions.
First, I may have misspoken, apologies -- the terminology is new to me. Safestrap has a version of TWRP, and that is what I mean when I say that I have TWRP installed. I don't have it separately installed. Does that change your advice?
Second, can I flash a zip of SU from Safestrap? Would I navigate to the Titanium Backup .zip and use the install function of Safestrap?
I deeply appreciate the advice. I may indeed have to go back to stock with the 1.20 utility, as you note.
Safestrap isn't a version of TWRP. It's based off of TWRP, but it's designed to work with a locked bootloader. Honestly, I would just use the utility and flash back to stock, re-root, and then install TWRP.
If you don't want to do this, your next step needs to be flashing TWRP, deleting and uninstalling SS, and flashing SU. You shouldn't be able to flash SU in SS. If you want to take the OTA, then you need to install an aftermarket recovery, first, so you can flash SU.
Sent from my Droid RAZR M using xda app-developers app
Hello, just flashed omni and its really great, I found out that my device is not Rooted, (it was but after the format probably canceled(?))
Anyway, is it normal? And there is anyway to root without a PC and will it mess the system?
Thanks!
Sent from my Nexus 5 using Tapatalk
Flash the update supersu zip in linked in its thread.
I think its a bug in omnirom. Happened to me as well when i updated omnirom. You will just have to root it again.
Sent from my GT-I9300 using XDA Free mobile app
Same here. That's why I keep the supersu zip file on my tablet
You can always enable Backup (or Survival mode) in Super SU, so you never lose root, even after a ful system wipe. That way, you'll always see the message below once you reboot from recovery after wipe:
Code:
Root access may be lost. Fix root? (Y/N)
You can also simply put flashable SuperSU package (the one you flash via recovery) into "Flash After Update" folder.
Then it will auto flash each time you update rom. You can also put there other zips like custom kernel.
It is a very useful OmniRom function
When you open SuperSu for the first time (once you have installed it), it asks you to install a script to survive over the flashes. There's nothing else needed. You'll be rooted always, even if you flash any update. At least that works for me..:silly:
Greetings!
Dumb question- If I've used CF-Auto-Root to initially root my N10, what's the best way to update to SuperSU 2.35? I haven't installed a custom recovery, so can I use stock recovery to simply flash the 2.35 zip file?
dberthia said:
Dumb question- If I've used CF-Auto-Root to initially root my N10, what's the best way to update to SuperSU 2.35? I haven't installed a custom recovery, so can I use stock recovery to simply flash the 2.35 zip file?
Click to expand...
Click to collapse
I've asked this very question in Chainfires main SuperSU XDA thread. Hopefully we can get some clarity.
I updated my SuperSU today. It requested to update the su binary.
Standard method didn't work, custom recovery option (I forgot I haven't yet installed TWRP) got me an unbootable tablet. The only thing that worked was fastboot mode.
I tried pretty much everything and ultimately I was left with two options:
Re-flash lollipop / factory reset
Install latest TWRP
I tried the latter first and luckily ended up with normally working tablet. I had to re-launch the su binary update procedure, but that really wasn't a problem given that I just made the tablet work again
velis74 said:
I updated my SuperSU today. It requested to update the su binary.
Standard method didn't work, custom recovery option (I forgot I haven't yet installed TWRP) got me an unbootable tablet. The only thing that worked was fastboot mode.
I tried pretty much everything and ultimately I was left with two options:
Re-flash lollipop / factory reset
Install latest TWRP
I tried the latter first and luckily ended up with normally working tablet. I had to re-launch the su binary update procedure, but that really wasn't a problem given that I just made the tablet work again
Click to expand...
Click to collapse
Interesting but I wonder what state your boot.img is in. I downloaded and examined the SuperSU v2.35 update flash file. I did not see anything to indicate that it backs out whatever non-stock boot.img changes were introduced. There was a "clean-up" comment which was intriguing.
As my tablet works well I'll wait for a while to see if I get any definitive response to my post. If not I'll likely use fastboot to re-install the stock boot.img and TWRP (which is already installed on my N10) to flash SuperSU v2.35 file.
Glad to read your tablet is in good shape.
I updated Binary via twrp and get fcs for all Google apps. Tried to clear Cache of everything, also wiped it: nothing changes. Going to reflash lollipop