Hi everyone, it's been a while since I started thinking to root my Moto G 2 but I still want to run on stock kernel & ROM. We are still waiting for the update to Android 5.1 and I was wondering if I could get the OTA safely with a rooted device. If not, I would wait for the official update and after this I'm going to root it; otherwise I would root it now. Thanks in advance.
I think you should wait for the OTA update and root after the update.
You won't receive any OTA updates from Motorola if you have flashed custom recovery and rooted your device
Copy that, thank you guys.
Nahuwii said:
You won't receive any OTA updates from Motorola if you have flashed custom recovery and rooted your device
Click to expand...
Click to collapse
If I understood it right, @luke! wants to run stock rom after rooting. So there is absolutely no problem to boot into TWRP 2.8.5.0, make a nandroid backup and flash latest superSU from there. OTA just cares about custom recovery and changes in system. So when an OTA arrives just restore your nandroid backup or revert the changes you made like unfreezing systemapps, uninstalling things like adaway and there will be no problem to install OTA.
Even if you flash twrp instead of booting into it,you can easily flash back the custom recovery. As long you stay stock this is all an easy thing. And also after flashing a custom rom there are ways to get back to the original firmware. @luke!:If you need any help pm me.
Wolfcity said:
If I understood it right, @luke! wants to run stock rom after rooting. So there is absolutely no problem to boot into TWRP 2.8.5.0, make a nandroid backup and flash latest superSU from there. OTA just cares about custom recovery and changes in system. So when an OTA arrives just restore your nandroid backup or revert the changes you made like unfreezing systemapps, uninstalling things like adaway and there will be no problem to install OTA.
Even if you flash twrp instead of booting into it,you can easily flash back the custom recovery. As long you stay stock this is all an easy thing. And also after flashing a custom rom there are ways to get back to the original firmware. @luke!:If you need any help pm me.
Click to expand...
Click to collapse
Great! Thank you, very appreciated If I have some problems, I will pm you. Thanks in advance
Related
Hello XDA,
Im quite sure this has already been asked on the forum but i couldn't find an answer.
I need some advise about my recently rooted Nexus 6. I want to fully enjoy from a custom recovery but i dont want to lose the option of receiving OTA updates to my phone.
What do you guys do so your nexus keeps getting the lastest of Android?
Can i use WugFresh's root toolkit to sideload OTA updates even when i have a custom recovery?
What other ways can i use to update Android?
Thanks,
No but you could use the tool kit to reload recovery and stock then take your OTA then reroot and reload TWRP.
And you can side load but it is important you understand exactly what you're doing. the kit does nothing more than you can from the command line it just tries to save you from yourself. it can be a help or hindrance. If you don't understand what's going on it will be the latter
Sent from my Benzo'd Google N6 on VZ
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Agreed. OTA is overrated. If I was on T-Mobile or the factory image was not available. I would grab the radio and load what I wanted.
Now I am running the E radio and the i build on VZ
Sent from my Benzo'd Google N6 on VZ
Didgeridoohan said:
you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
torecdude said:
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
Click to expand...
Click to collapse
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Evolution_Freak said:
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Click to expand...
Click to collapse
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Updating via OTA on a Nexus is an undesirable method IMO. As mentioned previously, if you download and flash the factory images, you avoid the potential update failures in an OTA from modified stock parameters. As for recovery, you don't need to flash a custom recovery, you can simply boot a custom recovery from the PC using fastboot and having the recovery image of choice in your platform tools.
fastboot boot name_of_recovery_image_here.img
I don't flash from the device any more. Keeps me out of trouble. Being connected to the PC helps remind me to move a copy of my backup to the PC before flashing.
torecdude said:
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Click to expand...
Click to collapse
I put the link to that thread in mine as a quick way for people who are rooted/unlocked and running a custom recovery to find. Those are not the "official" way of updating. They work because someone here put the time in to make them work for unlocked/rooted users. No, you can't use an "official" OTA process if you've altered your device but that method uses TWRP to flash just like you were flashing a custom ROM.
I'm glad my thread has helped you! Since I'm not a developer yet, it is my sole purpose here to help users with anything I can. So a comment like that is very reassuring that I'm on the right path.
I have unlocked the bootloader on my encrypted N6 and installed TWRP.
I was invited by my phone to install the 5.1.1 update so I downloaded it, tapped on install and my phone duly rebooted. It booted into TWRP and then nothing happened. I am quite happy to flash the update myself although I'm not sure why it didn't work but I don't know where the update is.
Can I just flash the update like flashing any other ROM using TWRP and if so, where did my phone download the update to?
lotus49 said:
I have unlocked the bootloader on my encrypted N6 and installed TWRP.
I was invited by my phone to install the 5.1.1 update so I downloaded it, tapped on install and my phone duly rebooted. It booted into TWRP and then nothing happened. I am quite happy to flash the update myself although I'm not sure why it didn't work but I don't know where the update is.
Can I just flash the update like flashing any other ROM using TWRP and if so, where did my phone download the update to?
Click to expand...
Click to collapse
no, you can not flash an ota unless you are completely stock with a stock recovery and without any system file changes.
Thank you, that answers that question.
In the past I have always flashed non-stock ROMs and I knew I couldn't install OTA updates but now my phone is at least running a stock ROM. I haven't been in this position before.
lotus49 said:
Thank you, that answers that question.
In the past I have always flashed non-stock ROMs and I knew I couldn't install OTA updates but now my phone is at least running a stock ROM. I haven't been in this position before.
Click to expand...
Click to collapse
Its new since lollipop
Hi,
So i have a Moto G 2 XT-1068 with Android 5.0.2 and system version 22.21.28.titan_retaildsds.retaildsdsall.ex.03 reteu.
I rooted it and installed Xposed.
Since some days, my phone notify me that there is a new (official) update avalaible :
22.56.3.en.03
My first reflex was to post in the Xposed forum :
I have a Motorola Moto G 2nd edition (2014 XT-1068) with Android 5.0.2 and these xposed versions installed :
XposedInstaller_3.0_alpha4.apk
xposed-v75-sdk21-arm-1
This morning, my phone notify me that there is a newsoftware update available :
22.56.3.en.03
Can i update ?
Will Xposed still running or do i have anything to do before or after update ?
Click to expand...
Click to collapse
then :
Yes i'm rooted (i didn't know i could install exposed without root ?!) and i ask the question to rooted users : what is the recommended behavior to have when we are rooted and there is an official update like this one ? Should i ignore it ? Should i wait ? Should i update (with one of your solutions) ?
Click to expand...
Click to collapse
and this is the reply i had :
You'll have to ask how an OTA works for that in your device forum.
For Google Android (untouched by OEM) in Kitkat, OTA used to check each important file individually and if one was modified, OTA would fail. This did not check all existing files or added files such as root, so as long as you uninstalled Xposed properly (restoring the original app_process files etc) then an OTA would be fine.
Since Lollipop, OTA checks the /system partition as a single item so any modification in any file, or any additional file will make the OTA fail. In which case, the only way to update would be to flash a stock ROM.
You will need to find out in your device forum which of these applies to your device.
Click to expand...
Click to collapse
So this is it, i make a post in this Moto G 2014 forum
Doing the OTA will most likely delete the XposedBridge.jar so you will have to flash it again.
Else the Xposed app will still be available but the Framework won't be installed.
If it doesn't update because the /system partition has been modified, you'll have to flash the whole rom to update.
Ok, so i can try without risk ?
And what about my root ?
nonobio said:
Ok, so i can try without risk ?
And what about my root ?
Click to expand...
Click to collapse
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Hi
TheKill69 said:
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Click to expand...
Click to collapse
Ok.
Seriously said:
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Click to expand...
Click to collapse
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
nonobio said:
Hi
Ok.
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
Click to expand...
Click to collapse
You might have to flash the whole stock firmware back to get the stock recovery. Big waste of time.
Then rooting back means using CF Auto Root Commands again..
You have to update to it though if you want Android 6.0.
Since it won't be soon, you rather go for CM13 once it gets really stable.
Also by the way, Xposed is already supported on MM.
Thanks for these precisions.
So if i can resume : a custom rom is easier for enjoy Android updates than just Xposed.
Hi,
Can you confirm :
For someone searching advanced features like customize status bar, quick settings, shutdown menu, hardware buttons, etc : customs roms and "stock rom + exposed" are two solutions. BUT, for someone searching these same advanced features but also keep his device up to date : custom rom is really a better solution. Isn't?
I was happy when i discovered xposed as it seemed to be a easier process that flashing a custom rom, but i didn't know that i couldn't update easily..
So, what is the advantage to use xposed instead of custom rom?
Hi,
I am always thinking if i will update my stock rooted xposed rom, or if i will install a custom rom prerooted like Cyanogen mod (o have easier future updates).
i have some questions :
1- Is it possible to install xposed and modules on a custom rom like cyanogen mod ? I think yes but can you confirm ?
I know that CM come with inbuilt tweaks but i discover some great xposed module i would continue to use, even if i install CM.
2-If i keep my stock rooted xposed rom, and don't make this "little" Android 5 OTA update, will be i notified for "Android 6" ?
(i don't want to lose my time to reflash my rom, reroot mydevice, etc.., just for a little update, but i could do that for a more important update like Android 6...
3- We are agree that if i flash a custom rom like CM, it will resolve my "ota update" problem, cause there won't be "Motorola OTA" anymore, but there will be CM updates easy to make, isn't ? If yes, what could be the advantage to use stock rom rooted + xposed vs custom rom + xposed ?
Thanks
So the android 6.0 OTA update just got available for me.
I tried to install it but the update failed. I have a rooted xperia z3 c (D5803) running android 5.1.1 with locked bootloader and custom recovery installed.
So my question is, how do i install the update? i dont mind if i lose root and custom recovery, i just want to keep my apps and settings.
-Victor- said:
So the android 6.0 OTA update just got available for me.
I tried to install it but the update failed. I have a rooted xperia z3 c (D5803) running android 5.1.1 with locked bootloader and custom recovery installed.
So my question is, how do i install the update? i dont mind if i lose root and custom recovery, i just want to keep my apps and settings.
Click to expand...
Click to collapse
The only way you will get OTA to work via PC Companion is buy putting your phone back to stock (no root, no recovery). It might be possible to use flashtool to restore a stock build without wiping data, but if it goes into a bootloop, then you will have to wipe it to fix it, loosing everything.
You could use Titanium backup to save all your apps/settings onto the SD card, then force PC Companion to 'repair' your phone. But then you'll be stuck with trying to root your MM build so you can restore your TA backup (Don't be tempted by Kingroot).
Have you considered moving to an MM custom rom? Slim works with a locked bootloader and is very popular, or an MM stock prerooted build. Both of these have install instructions that recomend a wipe, but it may not be necessary.
Several users in the Slim thread have said they successfully flashed without wipe.
There are still lots of glitches and problems with the MM build, are you sure you want to go through the pain of being an early adopter? Another month or so and they'll all be fixed.
Make sure you do a TWRP backup before you start, preferably onto the SD card.
Didgesteve said:
The only way you will get OTA to work via PC Companion is buy putting your phone back to stock (no root, no recovery). It might be possible to use flashtool to restore a stock build without wiping data, but if it goes into a bootloop, then you will have to wipe it to fix it, loosing everything.
You could use Titanium backup to save all your apps/settings onto the SD card, then force PC Companion to 'repair' your phone. But then you'll be stuck with trying to root your MM build so you can restore your TA backup (Don't be tempted by Kingroot).
Have you considered moving to an MM custom rom? Slim works with a locked bootloader and is very popular, or an MM stock prerooted build. Both of these have install instructions that recomend a wipe, but it may not be necessary.
Several users in the Slim thread have said they successfully flashed without wipe.
There are still lots of glitches and problems with the MM build, are you sure you want to go through the pain of being an early adopter? Another month or so and they'll all be fixed.
Make sure you do a TWRP backup before you start, preferably onto the SD card.
Click to expand...
Click to collapse
Does the custom roms unlock the bootloader?
-Victor- said:
Does the custom roms unlock the bootloader?
Click to expand...
Click to collapse
No, neither does using a stock prerooted.
Generally, is it says 'stock' or 'LB' in the title of the thread, then you can use it without having to mess with the bootloader.
Hi guys. I got this device today and am very happy with it.
I'm used to rooting my devices, so I want to root this one too and was hoping you could help me a bit.
I have the Oreo update installed and I see there are some TWRP that work with oreo. What is the best one to use with stock rom? I only want to root so I can install adaway and lucky patcher. Also, if an update comes later this year, like android P or something, can I switch back to the stock recovery, install it and then switch to TWRP again?
So, basically, where can I download stock recovery for Oreo, what TWRP should I use?
Thank you very much
olat_dragneel said:
Hi guys. I got this device today and am very happy with it.
I'm used to rooting my devices, so I want to root this one too and was hoping you could help me a bit.
I have the Oreo update installed and I see there are some TWRP that work with oreo. What is the best one to use with stock rom? I only want to root so I can install adaway and lucky patcher. Also, if an update comes later this year, like android P or something, can I switch back to the stock recovery, install it and then switch to TWRP again?
So, basically, where can I download stock recovery for Oreo, what TWRP should I use?
Thank you very much [/QUOTE
Excellent Question. Highly unlikely to get a reply as you have not included geek terms.
Click to expand...
Click to collapse
I'll add #geek to the post
I am pretty sure you need TWRP. Here is a good guide: https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
I do not know how to update with root. I am afraid it involves reinstalling the original recovery and a factory reset.
Unlocking the bootloader is currently a bit of a hassle since the unlock webpage is down. You'll have to contact Huawei Customer Service to get the code.