i want to root my device but then I am also planning to unroot it in the future to try updates ota. and then eventually will root again. my question is it is safe to root and unroot a device multiple times? sorry for the noob question.
Not unless you mess up the process no...
Sent From My Toro+ via Tapatalk
No, it's not safe? Or No, it is safe?
Sent from my Nexus 7 using Tapatalk 2
thank you so much
AMoosa said:
No, it's not safe? Or No, it is safe?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It is safe unless you do something wrong.
As long as you keep the stock recovery and are only rooting the stock Rom. You will still get the ota updates while rooted.
However it is possible that applying the update will remove root, but then you can just root it again anyway
Sent from my HTC One X using xda app-developers app
Why not just apply a rooted version of the update and save time and problems. Sometimes updates half further rooting capabilities
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Don't need stock recovery
bagofcrap24 said:
It is safe unless you do something wrong.
As long as you keep the stock recovery and are only rooting the stock Rom. You will still get the ota updates while rooted.
However it is possible that applying the update will remove root, but then you can just root it again anyway
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. You don't need stock recovery. Clockworkmod can apply updates as long as signature verification is disabled. It will patch completely normally but on your next boot will overwrite clockworkmod with stock recovery. You can avoid this by telling it to prevent itself from being modified when it asks when you hit reboot.
Rooting does not prevent updates in any way shape or form. The only things that prevent OTAs are modified fastboot (modified bootloader partition), modified gsm/cdma radio drivers (radio partition, does not apply to nexus 7), modified kernels or boot files (modified boot partition), icon packs, deodexing or other system apk mods (modified system partition), or some very specific changes to the data partition. All of those only include modifying existing files, not adding new files.
Google has a list of checks in their update and what's checked depends on the update so all of those things CAN prevent updating but not all of them will break any one update. If you root it just adds a small binary file onto the filesystem so you're fine. If you use that root to replace the calculator app with the one from gingerbread or something though it will change that file and may prevent updating.
Related
How can I safely update 4.5.91 to latest ota? My bootloader is locked, my phone is rooted with something called fastboot.
The ota update notification is getting annoying. Please help.
Sent from my MB860 using XDA
Just an FYI, "fastboot" is a protocol used to flash system files:
http://www.androidcentral.com/android-z-what-fastboot
Either way, if you want to stop the notifications you can use a root file manager (such as Root Explorer) to freeze the "Updater.apk" (or Upgrader.apk?) in the /system/app folder by adding a ".bak" to the end and rebooting.
You can maybe try "rootkeeper" and do the OTA but I don't know the extent of your modifications so I really can't recommend that.
Or you can take the leap and unlock the bootloader and flash custom ROMs.
nekrosoft13 said:
How can I safely update 4.5.91 to latest ota? My bootloader is locked, my phone is rooted with something called fastboot.
The ota update notification is getting annoying. Please help.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Or he can use the Automatic Update (PC Only) from here if he wants to stay stock:
http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
That will flash the 141 sbf onto your phone so you will lose root
Then you can re-root using the preinstall method using Fastboot again.
or just root / unlock and load a custom rom They are FAR superior that any stock atrix firmware! period!
Sent from my MB860 using Tapatalk
ok, i was able to unroot and run OTA using these directions http://forum.xda-developers.com/showpost.php?p=22723943&postcount=15
how can i root now? is there any method other then preinstall method?
1: will unlocking the boot loader prevent me from OTA? And let's say I do get an OTA in the future with a unlocked bootloader, will the boot loader "relock" itself ?
2: If I root, can I use OTA, and will it keep root.
Thanks !
Sent from my Nexus 4 using xda app-developers app
1. the state of the bootloader does not affect OTAs
2. don't know
I'd like to know this as well. I've rooted and am getting a nag to apply the update but it doesn't seem wise until I have the answer to your 2nd question
Sent from my Nexus 4 using Tapatalk 2
i believe neither matter. But often the phone will just get unrooted after the ota.
As long as the rom is still stock it should be fine.
*Someone confirm?
As long as you keep stock recovery you can update and keep root. Also its wise to keep a nandroid of stock ROM, that way when an OTA is released you can nandroid back and get ota. This works well if you like to run a custom ROM but be able to check out ota should you feel the need.
Also many people updated to 4.2.1 while using CWM but the rest of their system is stock including root. I nandroid back to stock, with root and cwm. I was prompted to download the ota. Then I applied it via cwm. It will ask you if you wanna keep root and cwm while going through the flash process. Pretty seamless actually
Muffin approved this message.....
worked perfectly with CWM Recovery 4.2 to 4.2.1
sincere thanks for your guidance
Anyone tried and confirmed working the old adb backup method that doesn't require root?
http://forum.xda-developers.com/showthread.php?t=1420351
Was hoping to use this method to backup before unlocking. I got into the usual problem of not wanting to unlock right away (in case issues etc.) then once I was comfortable with the unit too lazy to want to set up all up again from scratch....
Use helium. Backup each app individually. There are some apps that will Bork restore.
Sent from my Nexus 7 using XDA Premium HD app
bummer screw that for a joke then LOL
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
wintermute000 said:
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
Click to expand...
Click to collapse
Unlocking doesn't prevent you from getting the OTAs.
If you want root to be compatible with OTAs, see this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
yeah I know that, I know I can reflash stock recovery and unroot etc. just too lazy to be bothered setting up all my apps losing saves etc. at this point short of mucking around with carbon. TBH if the multitouch issue is fixed or at least toned down there's not a lot of incentive to root for me aside from adblock.
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
wintermute000 said:
yeah I know that, I know I can reflash stock recovery and unroot etc.
Click to expand...
Click to collapse
My point is you don't need to unroot nor flash stock recovery (though it is safest to flash stock recovery)
The JSS15J OTA update will flash fine with root and twrp with just the small fix I referenced.
wintermute000 said:
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
Click to expand...
Click to collapse
JSS15J already included firmware updates, it updated aboot, sbl, tz, and rpm. Bootloader went from 3.05 to 3.14 and it flashed ok with root and twrp (though again, personally I suggest using stock recovery)
Also you don't need to install twrp persistently to root. I just boot into twrp one-time by using fastboot boot twrp.img to install the root files and leave stock recovery on the tablet.
With the one simple fix referenced above, you can have stock recovery, root, and be totally compatible with future OTAs, no need to revert anything. Of course after the OTA is successful, just re-run the SuperSU zip and the fix to set yourself up with root and await the next OTA.
On this nexus, you need to unlock even to do the official factory restore google published. The official images don't come with signatures.
To answer the question re adb bu, yes it works just fine.
Sent from my Nexus 7 using Tapatalk 4
As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
341464 said:
As a long time Android power user, I rooted my Nexus as soon as I got the phone. However, I completely forgot about the best thing Nexus devices have to offer, OTA updates.
I completely ditched OTA before since I was on custom ROMs most of the time on other devices.
So here are the questions.
1) How will modifying the system partition affect OTAs? Will they still show up and I won't be able to install them?
2) How can I get OTA back and working? Does a simple "fastboot flash system/boot system.img/boot.img" with the stock system and boot partition fix the issue? If not, what do I do? And will it involve data wiping?
3) If I don't do those, I can still do a manual update for the system partition using fastboot, correct?
Note: I rooted the device using the Nexus Toolkit method over at the dev sub.
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Heisenberg said:
1. They'll still show up, but any attempt to install them will fail.
2. See my guide.
3. Yes.
Click to expand...
Click to collapse
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
341464 said:
So wait, what's the status now on the latest SuperSU package? I've heard that its system-less installation now?
Sent from my Nexus 6P using XDA Forums
Click to expand...
Click to collapse
There are two versions, the traditional version, and the systemless version.
Heisenberg said:
There are two versions, the traditional version, and the systemless version.
Click to expand...
Click to collapse
Speaking of OTA and systemless. I have opted for the systemless root method. If I want to install an OTA, all I have to do is flash the stock boot image, install update, then re root correct? Assuming there are no changes to system?
Sent from my Nexus 6P using Tapatalk
I just got a notification about new security patches. It seems to me that if all its doing are small security tweaks I can update safely with this OTA update and still retain root and everything else. Can someone chime in?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
I just got a notification about new security patches. It seems to me that if all its doing are small security tweaks I can update safely with this OTA update and still retain root and everything else. Can someone chime in?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The update will not work while you are rooted.
dratsablive said:
The update will not work while you are rooted.
Click to expand...
Click to collapse
What's preventing it? And to get around it is it just a simple unroot or will I basically need a relocked bootloader and everything else?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
What's preventing it? And to get around it is it just a simple unroot or will I basically need a relocked bootloader and everything else?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It depends on what method you used to root. If you have a systemless root, then you need to flash stock
boot.img
recovery.img
If you have a non-systemless root you will need to flash
boot.img
system.img
recovery.img
dratsablive said:
It depends on what method you used to root. If you have a systemless root, then you need to flash stock
boot.img
recovery.img
If you have a non-systemless root you will need to flash
boot.img
system.img
recovery.img
Click to expand...
Click to collapse
I do in fact have systemless. But why is this all necessary just for a small update that doesn't even change major files of M?
Sent from my Nexus 6P using Tapatalk
Because the updates checks for any changes to the system. And you need stock recovery because the OTA does not work with TWRP.
Just download the update and flash it using fastboot if you are on stock. You will have to flash the entire google image instead of the small incremental update but its easier than unrooting or flashing system and stock recovery which you will have to do in fastboot also.
murphyjasonc said:
Just download the update and flash it using fastboot if you are on stock. You will have to flash the entire google image instead of the small incremental update but its easier than unrooting or flashing system and stock recovery which you will have to do in fastboot also.
Click to expand...
Click to collapse
I am in fact stock software wise. But flashing the entire Google image will reset data and everything else won't it?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
I am in fact stock software wise. But flashing the entire Google image will reset data and everything else won't it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It will not wipe the data on your internal SD card. It will only over write your system partition. You will have to set your phone up and download your apps or restore them from titanium backup but all your personal data such as pictures will not be deleted.
murphyjasonc said:
It will not wipe the data on your internal SD card. It will only over write your system partition. You will have to set your phone up and download your apps or restore them from titanium backup but all your personal data such as pictures will not be deleted.
Click to expand...
Click to collapse
I am on a custom rom and want to flash stock rom without losing root and other data. Is it possible to do so with fastboot? Can't find a flashable stock rom.
rajarshi10 said:
I am on a custom rom and want to flash stock rom without losing root and other data. Is it possible to do so with fastboot? Can't find a flashable stock rom.
Click to expand...
Click to collapse
Probably not going to happen. Are you referring to the new security update or...?
Sent from my Nexus 6P using Tapatalk
See this thread:
http://forum.xda-developers.com/nexus-6p/general/january-security-update-incremental-zip-t3286533