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.
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 -
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.
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?
Whenever i click on software update it says connecting then gives me a message Registration Failed.
How am i supposed to get phone updates after root?
vangry2020 said:
Whenever i click on software update it says connecting then gives me a message Registration Failed.
How am i supposed to get phone updates after root?
Click to expand...
Click to collapse
Stock updates require an unmodified system, and they also require stock recovery, meaning, no root, no exposed or any other kind of system modification. Even if you did find a way to apply the update while being rooted, it would probably soft brick the device, then you would have to repair the device, IF it can be repaired.
If you want to apply a stock update, return your device to full unmodified stock system, then the update should work. If you have custom recovery, you need to flash the stock recovery back onto your device before you apply the update because the stock update requires stock recovery in order for it actually flash the update.
After applying the update, root the device again and install custom recovery(if you had custom recovery).
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Stock updates require an unmodified system, and they also require stock recovery, meaning, no root, no exposed or any other kind of system modification. Even if you did find a way to apply the update while being rooted, it would probably soft brick the device, then you would have to repair the device, IF it can be repaired.
If you want to apply a stock update, return your device to full unmodified stock system, then the update should work. If you have custom recovery, you need to flash the stock recovery back onto your device before you apply the update because the stock update requires stock recovery in order for it actually flash the update.
After applying the update, root the device again and install custom recovery(if you had custom recovery).
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
Is there a way to recover my files and settings exactly as they were after the update since the phone is erased when i unlock the bootloader?
update verification failed while trying OTA updates. Pls give me a solution for it
If device is a Samsung one, look inside here:
How to solve "Verification Fail" in Samsung devices | The TechRim
While rooting and changing stock rom of android there may arise different problems ..... while rooting or changing Rom is "Verification Fail".
thetechrim.com
anirban197 said:
update verification failed while trying OTA updates. Pls give me a solution for it
Click to expand...
Click to collapse
The cause of this problem depends on whether your device was rooted or had a custom recovery installed before you tried applying the OTA update.
If you were rooted or had custom recovery installed, first, you have to remove root and/or any other system modifications that you made and you have to restore stock recovery instead of having custom recovery installed. Stock OTA updates require an unmodified system partition and they also require stock recovery because the OTA update process checks the system partition to verify whether it is stock or not and the OTA process has to boot into stock recovery in order to install the OTA update before it can boot into the new system.
If you were not rooted or had custom recovery installed then the update may have failed due to one of your partitions being corrupted.
Either way, the solution is to manually download the update to your PC and then use Odin to flash the update. After the update, you can root the device again and/or install TWRP again. But be warned, if the update comes with a locked bootloader that can not be unlocked then you will not be able to install TWRP and you may not be able to root the device if certain aspects of the software have been patched to prevent rooting exploits.