I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Quark^2 said:
I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Click to expand...
Click to collapse
It's just a simple security patch, not an version upgrade, it can be safely ignored. That said, if you really want it you need to be pure, unmodified stock... Restore your pre-root Nandroid or flash the current factory image with fastboot.
Related
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
Yes!
SWTR said:
Yes!
Click to expand...
Click to collapse
Indeed.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
The OTA will download but not install. You need stock recovery AND any system file that is updated by the OTA needs to be stock as well otherwise OTA install will fail.
Plenty of threads on XDA speak of this.
If you look at the OTA updater file you will see if uses MD5 (or similar) to check each system file it updates to make sure its as it was originally.
When you root it alters some system files.
Best thing is to install custom recovery and take a backup before rooted. Then root. When you get an OTA just restore backup and flash stock recovery. Then OTA will re-download. Let it install, then flash custom recovery and re-root.
Thanks, well I'll just stay unrooted and make the best out of it, the Moto G is just as amazing as Motorola developed it to be.
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
denzel09 said:
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
Click to expand...
Click to collapse
Do you mean you downloaded OTA and flashed manually via recovery. You can do that I agree, but what you can't do is let OTA install naturally the way Motorola intended.
No. I had Philz recovery. System stock partition. Downloaded ota normally, reboot like ota update ask, phone reboots in philz recovery and this last flash ota automatically without any problem. There is not need to reflash stock recovery or flash ota update manually with custom rec, only need a non root stock system partition. I dont know if stock cwm or other rec like twrp work in same way but i doubt, always used only philz recovery.
You do not need stock recovery, I don't know who made this stupid rumour up. I use twrp and it flashes fine.
Sent from my Google Nexus G -
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
technocrat7 said:
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
Click to expand...
Click to collapse
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
jeffsga88 said:
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
Click to expand...
Click to collapse
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
technocrat7 said:
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
Click to expand...
Click to collapse
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
jeffsga88 said:
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
Click to expand...
Click to collapse
Thanks!
That helps a ton.
What is dm-verity though?
technocrat7 said:
Thanks!
That helps a ton.
What is dm-verity though?
Click to expand...
Click to collapse
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
jeffsga88 said:
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
Click to expand...
Click to collapse
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
carnivalrejectq said:
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
Click to expand...
Click to collapse
Here's the link to chainfires thread which will always have the latest beta supersu versions:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
minalm said:
Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
Click to expand...
Click to collapse
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
you have given a very detailed explanation and i fell like a simple thank you would be enough. you helped me out now and i feel somewhat obliged to thank you this way.
cheers
Is the things still the same... namely unrooting will not return KNOX and can not use Samsung warranty?
hi
i have a rotted phone s8..i flashed a stock rom, but phone is still rooted. Some apps like us google pay,mcdonalds tell me that phone is rooted..What i can do?
Hi, I'm very very new about Huawei devices, and I have a question..
I'm on build 8.0.0.120 (C432), and I can update my device to 8.0.0.130 (C432)..
I've rooted my Honor V10 with Magisk and I've TWRP recovery...
If I install this OTA update, I will lose root, or because the system partition on this device is read-only, I can update without lose anythings????
Thanks at all
BoGnY said:
Hi, I'm very very new about Huawei devices, and I have a question..
I'm on build 8.0.0.120 (C432), and I can update my device to 8.0.0.130 (C432)..
I've rooted my Honor V10 with Magisk and I've TWRP recovery...
If I install this OTA update, I will lose root, or because the system partition on this device is read-only, I can update without lose anythings????
Thanks at all
Click to expand...
Click to collapse
Magisk has an add-on to survive OTAs, but I really don't know
BoGnY said:
Hi, I'm very very new about Huawei devices, and I have a question..
I'm on build 8.0.0.120 (C432), and I can update my device to 8.0.0.130 (C432)..
I've rooted my Honor V10 with Magisk and I've TWRP recovery...
If I install this OTA update, I will lose root, or because the system partition on this device is read-only, I can update without lose anythings????
Thanks at all
Click to expand...
Click to collapse
I would be surprised if you can install an OTA with TWRP recovery.
To successfully apply the OTA you probably have to do something like this
Deinstall Magisk
Flash stock recovery
Apply OTA
Flash TWRP
Install Magisk
st_voss said:
I would be surprised if you can install an OTA with TWRP recovery.
To successfully apply the OTA you probably have to do something like this
Deinstall Magisk
Flash stock recovery
Apply OTA
Flash TWRP
Install Magisk
Click to expand...
Click to collapse
Yes. This is the process
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.