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?
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'm on the XT1540 and I got my OTA notification and went back to stock recovery (still rooted and unlocked bootloader) but it fails halfway through flashing everytime. I reflashed TWRP and captured the OTA into a zip but get an error about updating binary or something when flashing it. Is there something I need to delete from the OTA zip to allow it to flash in twrp?
Sent from my MotoG3 using xda premium
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
HelpMeruth said:
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
Click to expand...
Click to collapse
This...do a full factory image restore, then adb sideload the ota file. It's signed. TWRP can't install it.
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
nikon120 said:
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
Click to expand...
Click to collapse
This...I can't understand, for the life of me, why everyone is wiping userdata with fastboot....that wipes your android data, and internal storage in one shot. Cache erasing is another totally unnecessary step. All that's necessary, at the most, is a factory reset with TWRP to wipe the android data and both caches....but even that shouldn't technically be necessary for an update like this. It's not like this is the marshmallow update!!
arunhebbare said:
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Click to expand...
Click to collapse
@arunhebbare I've got the APAC version of the G3 as well, which ROMs are you flashing? I could only find images of the India version, did you use those?
I rooted my Nexus 6P when I purchased however a few months ago, something happened which kind of messed up my root. I can't remember now exactly what it was (maybe I updated OTA) however when I run Root checker, I get the message "Sorry! Root access is not properly installed on this device". Also Titanium Backup complains about my device not being properly rooted.
The strange thing is, my banking apps complain that my device is rooted and don't give me the full functionality
Also, my phone always downloads monthly updates, but I haven't been able to install since around June. It has now downloaded Android 7.1.1 and after trying to install this morning, it just booted into TWRP.
I'm after 2 things..
to have a properly rooted phone again
to have Android 7.1.1 installed
What's the best way for me to achieve this? What's actually happened to my phone? I would like to achieve the above 2 things with zero data loss if possible
5aq1b said:
I rooted my Nexus 6P when I purchased however a few months ago, something happened which kind of messed up my root. I can't remember now exactly what it was (maybe I updated OTA) however when I run Root checker, I get the message "Sorry! Root access is not properly installed on this device". Also Titanium Backup complains about my device not being properly rooted.
The strange thing is, my banking apps complain that my device is rooted and don't give me the full functionality
Also, my phone always downloads monthly updates, but I haven't been able to install since around June. It has now downloaded Android 7.1.1 and after trying to install this morning, it just booted into TWRP.
I'm after 2 things..
to have a properly rooted phone again
to have Android 7.1.1 installed
What's the best way for me to achieve this? What's actually happened to my phone? I would like to achieve the above 2 things with zero data loss if possible
Click to expand...
Click to collapse
If you are talking about stock OTA updates, that doesn't work on rooted devices.
To do stock OTA updates you need to remove root, you need stock recovery instead of custom recovery and you need to have an unmodified system partition.
Flash your stock firmware then update then root again after all updates are installed.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you are talking about stock OTA updates, that doesn't work on rooted devices.
To do stock OTA updates you need to remove root, you need stock recovery instead of custom recovery and you need to have an unmodified system partition.
Flash your stock firmware then update then root again after all updates are installed.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ok thanks for the reply...
So if I don't want to do the stock update, then how do i fix my root first of all?
After I fix my root - Can i perform an update to 7.1.1 via a non-stock method? ie. download the update somehow and flash via ADB or install via TWRP?
5aq1b said:
Ok thanks for the reply...
So if I don't want to do the stock update, then how do i fix my root first of all?
After I fix my root - Can i perform an update to 7.1.1 via a non-stock method? ie. download the update somehow and flash via ADB or install via TWRP?
Click to expand...
Click to collapse
As I said, flash your original stock firmware, then apply any stock updates that you want and THEN root. The 7.1.1 OTA is a stock update.
YOU CAN'T APPLY STOCK UPDATES WHILE YOU ARE ROOTED AND YOU CAN'T DO STOCK UPDATES IN CUSTOM RECOVERY.
Or you can flash stock firmware to fix the device, then install root and custom recovery again and then if you want to flash a CUSTOM 7.1.1 you flash it in recovery but you can't apply the stock 7.1.1.
Sent from my SCH-I535 using Tapatalk
Thanks... And in both cases, i shouldn't lose my data because my bootloader is unlocked already from when i originally rooted... Is that correct?
Sent from my Nexus 6P using Tapatalk
Droidriven said:
As I said, flash your original stock firmware, then apply any stock updates that you want and THEN root. The 7.1.1 OTA is a stock update.
YOU CAN'T APPLY STOCK UPDATES WHILE YOU ARE ROOTED AND YOU CAN'T DO STOCK UPDATES IN CUSTOM RECOVERY.
Or you can flash stock firmware to fix the device, then install root and custom recovery again and then if you want to flash a CUSTOM 7.1.1 you flash it in recovery but you can't apply the stock 7.1.1.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks... And in both cases, i shouldn't lose my data because my bootloader is unlocked already from when i originally rooted... Is that correct?
Sent from my Nexus 6P using Tapatalk
5aq1b said:
Thanks... And in both cases, i shouldn't lose my data because my bootloader is unlocked already from when i originally rooted... Is that correct?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'm not sure about that. Flashing something that upgrades or downgrades bootloader usually wipes data.
Sent from my SCH-I535 using Tapatalk
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?
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.