Related
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well
gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
shelooga said:
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well
Click to expand...
Click to collapse
sheloga is correct. You'd have to revert back to full stock or wait for someone to make a flashable zip.
Can't you just flash the stock recovery and take the OTA? Or do you have to fully unroot and reflash the factory image?
I would like to pay close attention time to this thread because that is one is the main questions that I have. I hear so many different solutions towards this. I usually wait for a flashable zip but I would want to see someone either wrote a write up or make a video. Subscribed.
My understanding (from looking at the lollipop OTA updater-script) is it checks EVERY file for changes, including other partitions. You must be 100% stock with nothing extra in system (SuperSU apk or busybox etc).
gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.
BLUF: wait until OTA is made available in a recovery flash method. 90% of the time the OTA updates are patching security holes and other less important features.
Having been with a handful of different android devices in the past several years, I've always gone the route of flashing from recovery vs. OTA.
The LG G3 for example had an OTA just recently that broke rooting. It was fixed by a Dev, but that's the only update found in OTA.
Sent from my Nexus 6 using XDA Free mobile app
Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
simms22 said:
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.
Click to expand...
Click to collapse
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
no thoughts.
i just flash aosp hours after it appears there. or just wait for @rascarlo to add it to his rom, then i flash
HyperM3 said:
Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
After Android 5.0, you can't sideload the OTA file if you have made any changes to the system partition. You need to be completely stock to take OTA. You can just download the new factory images and extract the various img files from it and just flash those manually in ADB, thereby overwriting your modified system partition with the new factory system image (you can skip overwriting the userdata if you want to preserve your data). No need to revert back to stock (old image) and then take OTA - unnecessary step.
HyperM3 said:
Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?
gwojo22 said:
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?
Click to expand...
Click to collapse
From google
https://developers.google.com/android/nexus/images
hlxanthus said:
From google
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately
waqar.qu said:
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately
Click to expand...
Click to collapse
You need to install ADB and fastboot. After that, you can use the 'fastboot' command directly from Terminal. I've found that the easiest way to update Lollipop on my Nexus 6 is to:
Download image from Google
Decompress the archive, AND the second archive which was contained within the first one. Note: The recovery, boot, and system images are in the second archive.
Open Terminal, change directory to the extracted folder, and run these commands (they skip overwriting the userdata partition):
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader (VERY IMPORTANT TO DO THIS STEP)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
You need to restore root at this point; you can use these instructions if you're unfamiliar with the procedure.
I've got a question.
My moto g is rooted and has got a custom recovery installed.
Today I got the notification for the ota Lollipop update.
I wondered what would happen if I installed with the ota update?
Is there a way to disable checking for updates as I'm not interested in Lollipop an don't want to be bothered by the constant notifications?
schpongo said:
I've got a question.
My moto g is rooted and has got a custom recovery installed.
Today I got the notification for the ota Lollipop update.
I wondered what would happen if I installed with the ota update?
Is there a way to disable checking for updates as I'm not interested in Lollipop an don't want to be bothered by the constant notifications?
Click to expand...
Click to collapse
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Lucian Armasu said:
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Click to expand...
Click to collapse
Ok.
But i'm not really interested in the update anyway.
I would just prefer to stay on kitkat at the moment because I'm not convinced that lollipop is an "upgrade".
How do I turn of the constant notifications? I have already "froze" the update service with titanium backup but that didn't seem to help.
Lucian Armasu said:
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Click to expand...
Click to collapse
Because OTA.zip has to be used with stock recovery , unrooted and /system files unaltered - not for use via TWRP
If you ever want to reflash your phone to stock plenty of guides how to... or if xt1068 just use my signature links
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 MOTO G2 (XT1068). I have rooted it and even flashed many ROMs on it. Now if official 5.1 update comes from Motorola and if I revert back to pure stock(one without any customisations) then will I be able to get that update or I have to wait for someone to release it on XDA . I don't know about this things that's why I am asking.
Thanks in advanced. :thumbup:
You can grab the update image and fla**** with fastboot this wipes everything.
Unroot remove all customizations an see if you get the ota, you won't lose any data.
or wait for someone to upload an update zip for recovery
Thanks:thumbup:
Anyone have a stock rooted rom for the boost mobile version of this device?
Was rooted and then an official update was released and got installed, now google services and play store is crashing.
ravious said:
Anyone have a stock rooted rom for the boost mobile version of this device?
Was rooted and then an official update was released and got installed, now google services and play store is crashing.
Click to expand...
Click to collapse
I'm not sure how an update installed when you were rooted, that normally doesn't happen. I was going to make a flashable rom today or tomorrow, but if your modem was updated, I'm not sure you'll get service with the older firmware. You may need to change the modem back to the previous version. What firmware version and security patch does it say in settings after the update? You might be better off just flashing the stock firmware with fastboot or RSDlite.
Edit: did you try wiping data of the apps that are giving you trouble?
Sent from my Moto E (4) Plus using XDA Labs
I keep getting a notification for a boost mobile e4 plus update but don't want to take it because of this. Anyway to prevent it from popping up or is a good update available for those who are already rooted?
shezzy83 said:
I keep getting a notification for a boost mobile e4 plus update but don't want to take it because of this. Anyway to prevent it from popping up or is a good update available for those who are already rooted?
Click to expand...
Click to collapse
Taking an update when rooted should definitely fail. Is there any chance you could upload a copy of the OTA update zip, that would be great, because I haven't gotten it yet, and so could make a rom from the updated firmware. You need to flash full stock firmware before attempting to install an OTA update. The update zip should be in the cache folder, either /cache or /data /cache.
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
Taking an update when rooted should definitely fail. Is there any chance you could upload a copy of the OTA update zip, that would be great, because I haven't gotten it yet, and so could make a rom from the updated firmware. You need to flash full stock firmware before attempting to install an OTA update. The update zip should be in the cache folder, either /cache or /data /cache.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Hmm.. I don't see it in those folders.. It came up as a Motorola update ( Motorola software ) and not a typical Android ota update but it said it increased stability etc. Guessing not the same thing?
shezzy83 said:
Hmm.. I don't see it in those folders.. It came up as a Motorola update ( Motorola software ) and not a typical Android ota update but it said it increased stability etc. Guessing not the same thing?
Click to expand...
Click to collapse
Never mind that. I forgot I deleted the ota apk. I got the update now. I'll make a flashable of the original firmware and the newer one after I update. The best way to keep the update notification from popping up is to delete the Motorola ota apk in /system/priv-app by the way.
Edit: Here's where to find the update zip: /data/data/com.motorola.ccc.ota/app_download
GetOffMyLawn&!+¢#{$ said:
Never mind that. I forgot I deleted the ota apk. I got the update now. I'll make a flashable of the original firmware and the newer one after I update. The best way to keep the update notification from popping up is to delete the Motorola ota apk in /system/priv-app by the way.
Edit: Here's where to find the update zip: /data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
So you're making a flash-able to give us the update that we can't get now because we have twrp?
shezzy83 said:
So you're making a flash-able to give us the update that we can't get now because we have twrp?
Click to expand...
Click to collapse
I can't make a flashable for everything that is updated, I could, but it's safer to just do it the right way. It would take way longer than it's worth to make a full TWRP flashable firmware. Your better off just taking the OTA or waiting until the newer firmware is out to flash with fastboot. The old and new radio and OEM partitions, and some other things don't play well together.
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
I can't make a flashable for everything that is updated, I could, but it's safer to just do it the right way. It would take way longer than it's worth to make a full TWRP flashable firmware. Your better off just taking the OTA or waiting until the newer firmware is out to flash with fastboot. The old and new radio and OEM partitions, and some other things don't play well together.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Can you even take the OTA update with our recovery being replaced by TWRP? Shouldn't it fail?
shezzy83 said:
Can you even take the OTA update with our recovery being replaced by TWRP? Shouldn't it fail?
Click to expand...
Click to collapse
Yes it will. Who said you can't restore the stock recovery? You need to restore full stock with fastboot or RSDlite to take the update.
Sent from my Moto E (4) Plus using XDA Labs
I'm uploading a stock rom now. I'll upload flashable of the modem and eom partitions also. Then I'll update and make a stock rom from the newer firmware. I should have links for all of it before the day is over. Watch for a new thread.
Edit: the rom I'm uploading now is untouched for Boost. I'll do Sprint and the retail model next, then I'll make some that are rooted/debloated. I'll need testers for Sprint and retail versions.
Edit-2:
Here's Boost untouched stock. I haven't tested it yet, I'm waiting for my backup to finish to test it now.
Edit-3;
Didn't flash, I think maybe the mount points aren't right. it failed to mount /system. I'll fix it and reupload it.
Sent from my Moto E (4) Plus using XDA Labs
I got a rom working. I tried making it sparse.dat format but it wouldn't provision data services so I tried set metadata and it works fine. Only problem is the zip is 1.9GB. I'll do what I can to decrease the size so everyone doesn't have to use that much data to download it. I'll post a link as soon as I get it shrunk down and uploaded.
Sent from my Moto E (4) Plus using XDA Labs
Here's Boost Mobile stock:
https://www.androidfilehost.com/?fid=745849072291697789
It's not rooted or modified in any way. You'll have to flash a no dmverity zip or just Magisk or it won't boot unless you format data. There's some newer zips here:
https://build.nethunter.com/android-tools/
Or, you can flash the f2fs patched kernel recently posted. I'll make debloated and patched kernel versions when I have time.
Sent from my Moto E (4) Plus using XDA Labs
If anyone is feeling brave, I modified the last Boost Mobile ota update zip and made a partition updater and updated stock rom. What I did was removed all the system, oem and modem patches asserts/checks, added the updated oem.img and modem.img, and the flashable rom for the system update obviously. The updated ROM may not work without updating the partitions with either the zip I made, or by restoring the original firmware with fastboot and taking the official ota update. I know the rom posted above will not work with the updated modem/oem, so I would assume the same will with the new rom and old modem/oem.
Here is the TEST BOOST MOBILE partition updater:
https://www.androidfilehost.com/?fid=889964283620776382
Here is the updated Boost Mobile ROM:
https://www.androidfilehost.com/?fid=817906626617956720
Flash this at your own risk. If this doesn't work, you might have to flash the original firmware with fastboot, so please don't attempt flashing it unless you can restore your phone if something goes wrong. I take no responsibility for anything that might. I have also made Sprint and retail model ROMs and will make a stock ROM thread some time soon when I have time. Let me know how it goes if anyone tries.
Edit: make sure to flash a no-dmverity zip or format data after flashing the ROM or it won't boot. I also successfully restored a TWRP /data backup from the origional rom version to the new version after I updated so you don't have to worry about losing all your data by flashing stock firmware with fastboot to update officially.
Edit-2: I guess nobody was feeling brave. I really wanted to know if the damn thing worked or not so I flashed it. I was already updated but it flashed just fine and didn't brick my phone, so it should work just fine for you all to update the easy way. You'll see a "failed to mount firmware" message at the end, just ignore it.
Sent from my Moto E (4) Plus using XDA Labs
Y'all might be seeing me soon, if/whwn I can get a device
GetOffMyLawn&!+¢#{$ said:
If anyone is feeling brave, I modified the last Boost Mobile ota update zip and made a partition updater and updated stock rom. What I did was removed all the system, oem and modem patches asserts/checks, added the updated oem.img and modem.img, and the flashable rom for the system update obviously. The updated ROM may not work without updating the partitions with either the zip I made, or by restoring the original firmware with fastboot and taking the official ota update. I know the rom posted above will not work with the updated modem/oem, so I would assume the same will with the new rom and old modem/oem.
Here is the TEST BOOST MOBILE partition updater:
https://www.androidfilehost.com/?fid=889964283620776382
Here is the updated Boost Mobile ROM:
https://www.androidfilehost.com/?fid=817906626617956720
Flash this at your own risk. If this doesn't work, you might have to flash the original firmware with fastboot, so please don't attempt flashing it unless you can restore your phone if something goes wrong. I take no responsibility for anything that might. I have also made Sprint and retail model ROMs and will make a stock ROM thread some time soon when I have time. Let me know how it goes if anyone tries.
Edit: make sure to flash a no-dmverity zip or format data after flashing the ROM or it won't boot. I also successfully restored a TWRP /data backup from the origional rom version to the new version after I updated so you don't have to worry about losing all your data by flashing stock firmware with fastboot to update officially.
Edit-2: I guess nobody was feeling brave. I really wanted to know if the damn thing worked or not so I flashed it. I was already updated but it flashed just fine and didn't brick my phone, so it should work just fine for you all to update the easy way. You'll see a "failed to mount firmware" message at the end, just ignore it.
Click to expand...
Click to collapse
Does the updated boost version have that f2fs kernel included?
xhan145 said:
Does the updated boost version have that f2fs kernel included?
Click to expand...
Click to collapse
No, it is completely untouched. I was planning on building my own kernel.
Sent from my Moto E (4) Plus using XDA Labs
According to Motorola or Lenovo, this device is not eligible for unlocking the bootloader.
lwang9 said:
According to Motorola or Lenovo, this device is not eligible for unlocking the bootloader.
Click to expand...
Click to collapse
I just got this phone and unlocked bootloader no problem did on Motorola website
skullkid383 said:
I just got this phone and unlocked bootloader no problem did on Motorola website
Click to expand...
Click to collapse
Would it work with Walmart's prepaid xt1774?