I rooted my Moto 360 using this method by @dproldan and then modified build.prop to disable the ambient screen while charging. I just got the OTA to 5.0.1, but it failed because /system has been modified...
How can I restore the watch to work with OTA's after I've modified it already?
UPDATE: All I needed to do was restore the build.prop to the original one and everything worked fine.
removal of any mods is what makes an OTA work.... since the only thing u seem to have modieid was the build... thats all it took for the checks to validate
if u would have done any other mods, they would have also had to be undone
Related
So I got my phone today and rooted it directly. When I was browsing through the apps, I saw it has an update but it didn't let me install it because the phone was rooted. So, I had to go back to stock rom with a kdz file wiping everything, which seems to be the latest rom right now. I'm thinking about if i should root or not right now. Will I have to wipe everything again when the phone gets another update? Are you all in this situation or do i not know something correctly?
Some how I was able to install latest ota with root and also nothing was wiped.
Im not 100% sure but I think you can unroot with SuperSU then ota should go through but I may be wrong.
If you want to use apps like g3 tweaksbox, titanium backup etc, you will need root! I think you can do so much more when your Phone is rooted, so i would root it immediately!
homer285 said:
Some how I was able to install latest ota with root and also nothing was wiped.
Im not 100% sure but I think you can unroot with SuperSU then ota should go through but I may be wrong.
Click to expand...
Click to collapse
I also took an OTA for my F460S while rooted and it worked. My phone also is fine (it didn't die, crash or kill itself). When I get my next OTA I'll upload a video to show that it does work for some odd reason (only for a few people that I have seen). The benefits of rooting outweigh the drawbacks. If you root your phone, than you should be comfortable flashing a KDZ to restore it.
OTA updates often modify existing pre-installed apps, otherwise known as bloatware, so they check to be sure those targets are present and unmodified. If you have rooted but not deleted or removed or frozen any such apps, your system will pass that OTA test.
Some OTA's also look for su being installed, and hiding su can fool that, depending...
Sometimes the OTA is just mean altogether, for your protection.
Sent from my VS985 4G using Tapatalk
I have successfully done the guide to rooting your m8 while keeping the ability to do ota updates. However the ota updates are not working. It just keeps rebooting trying again and failing again.
I have xposed and xprivacy installed. I have the stock recovery installed. Was I supposed to remove xposed? I tought I read that I didn't have to in several places.
I read the entire thread of the guide and have searched for a while. I couldn't find any other errors like mine in any way.
Thank you for your time.
I am not positive on the M8 yet, but on an N5 for example, you can't take an OTA with a custom recovery, or Xposed.
And you need to properly uninstall Xposed. Search on that, I haven't done it.
Also, if you've made other system changes.. Like uninstalling system apps, it won't work either.
I'm not an OTA type, I flash updates manually... And I definitely am not sure if this applies to the M8. ?
You have to have stock recovery, stock rom, and stock kernel to be able to OTA.
I think you must not have any system installed mods as well. (HK sound mod etc.)
s-off and root and xposed do not affect the OTA.
hey, someone could have warned that the OTA updates don't work anymore after rooting the phone -.-... first with somehow reverted recovery (don't know how it happened) it failed, and now with TWRP it doen't do anything and sits idle in recovery mode, with no alarm clock... -.-
also I'm used to have a all-in-one-thread with links to the latest firmwares etc, I can't find this here.
so, what's the latest firmware, are there differential patches I can install with TWRP or only the >1GB full images?
I'm on version 10B or so, something with 'b'. from june.
Only solution is to flash v10b "stock" and lose root (by that you'll be able to Ota update), or the newer version (using LG flash tool). Note that you'll lose all date on your phone.
Edit:
By flash I meant using LG flash tool. (for which version you'll like to install.)
Sent from my LG-H815 using Tapatalk
*Of course* OTA updates won't work with root...what else could you have been thinking??
You actually have been warned if you had read the root thread...
Gesendet von meinem LG-H815
In the past, not all rooting automatically meant that OTA updates were stopped. This was an optional step you could take. Early on, when a phone is first released, updates from the provider should be expected - this is something why I might hold off on rooting ASAP. As the life cycle of the phone starts to wear on, less updates (or no more updates) so less of a concern. There was/is an app I use to use call OTA Root Keeper that allowed one to not turn off the OTA updates - as some are valuable like the coming Stagefright patches we should expect - and get the OTA updates and then also keep root. Taking an OTA update could mean you loose root even with OTA Root Keeper if part of the update is closing an exploit. That was always a risk. But for me, having updated proper software often outweighed the risk with losing root and in fact, OTA Root Keeper always worked for me so I never lost root on my phones or tablets. But as we know, phone makers and providers hate root so they work to close every exploit and I suspect that would be why shutting off OTA updates is part of the current root tool/method you refer to. Most are cool with shutting off OTA updates.
For example, in this current root method it clearly says "Now that you're rooted, MAKE SURE YOU DISABLE OTA UPDATES, if you accidentally take an OTA, you might not be able to roll back or fix it." so it looks as if in this case OTA updates are NOT shut off and you have to manually take that step if you want to.
kyle1867 said:
*Of course* OTA updates won't work with root...what else could you have been thinking??
Click to expand...
Click to collapse
this is not true.. this is exploit specific
the bootload is unlocked, therefore we have full access anyway, it's totally impossible to deny root to a phone with open bootloader.
therefore it should be doable to unroot, revert recovery back to stock, to ota, and do it all again. but it's annoying.
I tried to flash the OTA update (it's in /cache/xxxota/something), after renaming it to .zip and .img, but it didn't work.
any other way to simply extract the files from the OTA?
I was have root and update software via lg bridge. Now i dont have root but i dont need it till we have twrp and custom rom/s.
http://forum.xda-developers.com/showthread.php?t=3175493
Try this one
Sent from outer space using telepathy
So the Marshmallow OTA for M9 is already here (not sure for how long but I just checked for updates accidentally and it started nagging me to update).
However I have a modified system partition (stock with supersu and xposed) and I'm not sure if that one TWRP backup I have was before or after flashing su (silly me) so I guess OTA is a no-go for me. So here are some noob questions:
does the USB update work well with a rooted phone? (I suppose it does as it wipes everything, root included)
I've heard Marshmallow updates the bootlader. Does it require locked bootloader and will that affect my custom recovery?
are there any problems with rooting after the update?
is there a working xposed binary for 6.0?
and the last but not least - is it worth updating at all in the first place? I mostly look for better performance.
Usb, couldnt tell you. I have not seen any issues but you will need either a totally stock device to accept ota's or s-off to update. The ota doesn't wipe data.
Bootloader.. I think it did.
Root is possible but be careful as only certain twrp and supersu versions work.
Xposed is compatible (certain version) but some mods are extremely dangerous.
The interesting bit.. The mm update itself. Well, the constant discharging after a full charge is solved. The recents list has a new clear button and it has annoyingly been moved. The powersave notification icon has been removed so now you have to guess. Performance is seemingly much much better. Although i havent benchmarked it it feels a lot smoother.
I'm glad i updated but its still not perfect.
Sent from my HTC One M9 using Tapatalk
Recently picked up a Z Play and rooted it (unlocked bootloader, flashed chinese TWRP, flashed Phhh Superuser (and app/Magisk) and I've got everything set up just the way I want it. How do I prevent an OTA from coming through and ruining things or is that something I need to go checking for manually?
Also, when the N update is available, what would be the most advisable way of updating? I have only owned Nexus phones prior to this, so I'm not sure if I should expect Moto to post update factory images for me to flash like google always did the day they released updates, or if there will be some faster/better way?
You can use some sort of root app which has a freezing option, like Titanium Backup.
You have to freeze the "Motorola Updateservices" which is in shown in the attached pictures. "Auftauen" means unfreeze, because i already deactivated the updates service.
For the Nougat question, i would wait until somebody can proof that root is still working flawless before updating.
Ubelsteiner said:
Recently picked up a Z Play and rooted it (unlocked bootloader, flashed chinese TWRP, flashed Phhh Superuser (and app/Magisk) and I've got everything set up just the way I want it. How do I prevent an OTA from coming through and ruining things or is that something I need to go checking for manually?
Also, when the N update is available, what would be the most advisable way of updating? I have only owned Nexus phones prior to this, so I'm not sure if I should expect Moto to post update factory images for me to flash like google always did the day they released updates, or if there will be some faster/better way?
Click to expand...
Click to collapse
Use a good filer like Solid classic, go privapp, find 3c OTA (try this 1st) or 3c checkin, change .apk to .apk.bak.
Reboot.
You do not have to fuss with permissions if you just rename.
G4liant said:
You can use some sort of root app which has a freezing option, like Titanium Backup.
You have to freeze the "Motorola Updateservices" which is in shown in the attached pictures. "Auftauen" means unfreeze, because i already deactivated the updates service.
For the Nougat question, i would wait until somebody can proof that root is still working flawless before updating.
Click to expand...
Click to collapse
Thanks! I don't know why I didn't think of just checking for an updater service app to freeze.
Thanks again