So the title pretty much says it all. I don't need root very much. Just for fixing the bluetooth with my Nyko Playad. http://forum.xda-developers.com/showthread.php?t=2138911
Anyway I installed the OTA 4.2.2 update and then I discovered my root wasn't working anymore. I have relocked my bootloader since rooting the first time and I know that if I root again I will lose all my apps will be deleted.
Last time I rooted I use the Nexus 7 toolkit to backup my apps. But certain apps like Need for Speed most wanted didn't backup. So when I restored my backed up apps some of them never appeared again and I lost all my progress.
If I re-root how can I be sure that all my apps will be backed up completely with all their data backed up as well?
Buy the paid-version of SuperUser, and you wouldn't have this problem...
Just sayin.....
Look up carbon in the play store. It will allow you to backup user apps+ data to your PC (if you get the paid version i believe it can sync up to google drive or dropbox to name a few) if you are not rooted. That way you can keep your games positions and apps data, unlock and root, then restore via carbon.
You didn't need to re-lock the boot loader to gain root back. (But now you DO.)
For OTAs that replace the recovery partition, you really only need two steps to gain back root:
- flash a custom recovery (need unlocked boot loader for this) into the recovery partition
- restore the setuid/setgid permission bits on the "su" binary, e.g. with the custom recovery running:
Code:
adb shell mount /system
adb shell chmod 6755 /system/xbin/su /system/bin/su
Alternately (instead of the step above) you could just re-flash a SuperSU/Superuser root kit, or use a "rootkeeper" app.
Any way you slice it it's not much work.
BTW - there will certainly be more OTAs - it's a Nexus device after all.
Thank you everybody.
I will definitely be purchasing the paid version of SuperUser so that I can keep my root after OTA updates.
I'm currently using carbon to back everything up. Then I will unlock, root, and relock. I keep my bootloader locked for security.
Ota rootkeeper will work too, but yes, you will always lose root after an update. How easy you regain it is up to your configuration.
Related
I have been reading through previous threads but I cannot find anything that specifically answers the question I have.
I had stock Android 4.2.1 (which was rooted) and now that it has updated to version 4.2.2 I am unrooted (even though upon boot it still displays the unlocked padlock but I assume that is something different).
So my question is, is it possible to root my current stock 4.2.2 and keep all of my apps and data? or is the only solution to wipe it all and start again if I want root access?
As a side note and to anyone who is reading this if you are currently rooted install this https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en and hopefully that should be the end of having to worry about losing root but in hindsight it is obviously to late for myself.
Thank you very much to anyone who can help me!
You didn't read enough threads.
The bootloader has been replaced, but is still unlocked.
The OTA also overwrote your custom recovery with a new stock recovery, but that's only a temporary issue - read on.
Because the new bootloader is also unlocked, that means that you can re-install a custom recovery just the same way you did it originally (with fastboot or a toolkit which also uses fastboot), but without the unlocking step (which wipes everything).
After you have a custom recovery in place you are free to do whatever you want - you could just reinstall a minimal SuperSU/Superuser overflash. This leaves everything unmolested, and you have root back.
Note that the superuser software is still on your tab; it has been temporarily disabled because the 'su' binary got its' permissions reset by the OTA install. Without doing a new over flash you could simply perform (with the custom recovery booted)
adb shell mount /system
adb shell chmod 6755 /system/xbin/su /system/bin/su
adb shell ls -l /system/xbin/su /system/bin/su
(it's one or the other of those locations depending on whether you are using SuperSU or Superuser; in any event you should see "swxs-xr-x" if you have the correct setuid/setgid permissions set)
good luck
The unlocked padlock means you're bootloader is unlocked, which is fine.
Yes it is possible, I suggest reading the stickies which explain how to do this. Basically, you'll need to flash a custom recovery via fastboot, then download a SuperSU flashable zip file (or Superuser) to flash in the custom recovery, and that's all.
Beaten by bftb0.
Thank you both very much for your responses!
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 installed twrp and SU. Really the only reason I did it is because I use titanium backup to back up and restore apps and such. Otherwise I really don't need root.
I have two questions.
First Question: Can I re-lock the boot loader if I have TWRP and SuperSU installed? If not how can I use Android pay? Is there a work around? It's not allowing me to because it can't verify
Second Question: The OTA 6.0.1 won't stick. I'm pretty sure I've done one other over the air update (at least I thought I did, I may be remembering incorrectly) and it worked just fine. But for some reason 6.0.1 isn't taking. Any ideas?
If you don't need root what you can do is download the 6.0.1 imag direclty from google, put it in your adb/fastboo folder and use the flash-all command and it will erase root, twrp and it will be like you just got it from the factory. The only thing that would be still there is the unlocked bootloader. Once you've performed the flash-all command, you can simple lock the bootloader again. That's if you want to get rid of Root and Twrp.. If not, you can try a Rom like Chroma that has android pay working on it.. Here's the instructions. Hope this helps: http://forum.xda-developers.com/showpost.php?p=64269166&postcount=2338
Edit: Make sure you follow the systemless root instructions from that link to get android pay to work...
So I cannot lock the boot loader if I have root and twrp installed?
I really don't want to use a Rom. I'm happy with stock, just want to be able to use titanium backup.
And are ota updates not working if you have twrp installed?
OTA updates won't flash properly if you have TWRP installed, though I heard there is a way to extract the components of the update you want to apply so you can preserve root and custom recoveries while still updating. Sorry I don't know where the instructions are though.
No you can't lock the bootloader with TWRP installed, it can result in a brick.
I would not lock the bootloader unless you are 100% stock. You open yourself up to unrecoverable bricks. As for the update if you download the image from google you can just flash the individual partitions in fastboot. This way you can preserve your data. Heisenburg has a great guide here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 You will loose root but getting it back just involves reflashing the SuperSU-v2.62-3-20151211162651.zip from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125#post64161125
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
zishhaider said:
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
Click to expand...
Click to collapse
I don't understand your goal?
Systemless root IS full root. Your terminology is incorrect.
SuperSU doesn't really support system root on Android 7.
I also dont see the point of making SuperSU a system app. Even though its rather pointless if that is all you require for whatever strange reason then you can just move the Supersu app to the system partition.
There is a better way to stay rooted after a hard reset and it's called FRP.
First there is nothing strange in stay rooted after hard reset, trust me. My friend use this mobile. He needs root for lucky patcher. When first he came to me I rooted it via twrp and after couple of days he came back with custom binary block option and plus he doesn't remember newly created gmail id pass. For me it was hell of a job. So i decided to root it permanently. I am not an expert though but my point was to take full root instead of systemless root. Thanks for clearing that 7.0 isn't supported for full system root. I saw here a rom stock dexoded and pre rooted. Is it better option to install it rather than stock rom?
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
zishhaider said:
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Click to expand...
Click to collapse
Like I already stated Factory Reset Protection (FRP) is already built in to SuperSU.
Just do the following in a terminal then re-install SuperSU:
echo "FRP=true">>/data/. supersu
.
Just now my tank let me defer an update. I do not care about or need root.
I just want to know if this update kills anything like playingwithfire.
This just appeared today (3/21) at 7pm ct. Its defintely new.
Don´t know. But with root (TWRP Recovery) you can test every ota update and downgrade in minutes.
I have two gen2 sticks rooted now, it´s easy. TWRP is really usefull. And with the Magisk App I can restrict root by App (currently only ADB is allowed).
Love the rooted ADB Shell for blocking updates, hide or delete system apps, explore and edit /data/data, run scripts, dmesg, top, cat Log.d and so on.
I have zero need to root.