I'm running CM 12.1 and I've been receiving updates on my phone that new updates are available over the last couple of days. I know these are nightly updates. My question is this, if i went through with the update directly on my phone will this wipe my current ROM and all apps on it or will it just do a delta updates?
I took a gamble and downloaded cyandelta and it worked. I updated to the newest nightly without losing all my apps and settings.
Related
If i install CM7 on my phone. Do i get updates from OTA? or do i have to manually flash ROM each time a new update comes from CM team?
How about nightlies? Will i get update from 19 til 20 from OTA?
you know, as you are asking this, you probably should not install CM7 in the first place until you really know what you are doing
But if i do? Can i update?
When its released, is it possible to update it over OTA then?
You can update but not by OTA read the CM7 topic
Right now with the nightly, you have to reflash it everytime. This is made easy if you have clockwork's rom manager. The app will help you keep the rom up to date with the latest version.
If you have the paid ROM Manger you can get OTA nightly build updates.
Hi. I'm currently running a nightly build of CM9 on my Touchpad that's about a month old (07/21, I think). I'd like to update to a newer nightly, but I'm worried about getting Flash. Will I be able to reinstall Flash from the Play Store after I wipe everything and flash a new nightly, or should I be looking at saving the Flash I have installed now? I know it won't work with CM10, I'm just wondering about a newer CM9.
Tired_ said:
Hi. I'm currently running a nightly build of CM9 on my Touchpad that's about a month old (07/21, I think). I'd like to update to a newer nightly, but I'm worried about getting Flash. Will I be able to reinstall Flash from the Play Store after I wipe everything and flash a new nightly, or should I be looking at saving the Flash I have installed now? I know it won't work with CM10, I'm just wondering about a newer CM9.
Click to expand...
Click to collapse
I started on nightly's in June and am now on the latest one and still have flash. Plus my daughter's which has just come back from HP after being repaired and therefore had a fresh install, was able to search and install flash after I put on the latest nightly then ran one of her backups in order to restore her settings and updated again .
Both machine's are/were also backed up to our Google accounts.
I hope this helps.
sstar said:
I started on nightly's in June and am now on the latest one and still have flash. Plus my daughter's which has just come back from HP after being repaired and therefore had a fresh install, was able to search and install flash after I put on the latest nightly then ran one of her backups in order to restore her settings and updated again .
Both machine's are/were also backed up to our Google accounts.
I hope this helps.
Click to expand...
Click to collapse
Did you do full system/data/cache/factory-reset wipes between nightlies (or even just once since Aug 15th), or did you just install them over top of the last one?
Tired_ said:
Did you do full system/data/cache/factory-reset wipes between nightlies (or even just once since Aug 15th), or did you just install them over top of the last one?
Click to expand...
Click to collapse
On mine I installed over and did cache/davlik wipes plus the occasional re-flash of gapps.
My daughter's was a fresh install on Wednesday when I got it back from HP plus I used a backup once to reestablish her settings before again flashing the latest nightly
Trust this helps.
Just had an update notification for flash , nervously hit the update button and all is still good !
I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.
1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.
Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?
Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.
I just bought a new R1 HD Prime version. It's on 6.1, and the wireless update is showing that no updates are available. So I've tried manually downloading the OTA updates and applying them from local storage using the wireless update app, but I get an error message when attempting to do so (Signature verification failed). How am I supposed to update this phone? It's completely stock.
The only thing I've noticed is that the build time of what's on my phone is slightly different than what the 6.4 OTA says it's supposed to be updated from:
My build - BLU_R0010UU_V6.1_GENERIC 17-06-2016 14:53
OTA build - BLU_R0010UU_V6.1_GENERIC_6.0_20160617-1456
Notice the build time is different by 3 minutes. Is that maybe the source of the problem I'm having? I'm honestly at a loss here and I really want to get this phone updated.
Found out what the problem was with the manual OTA...I committed that cardinal sin of not opening up the zip file and realized I needed to extract update.zip I'm still not sure why the wireless update wasn't getting the OTA from 6.1 to 6.4, but once I was able to manually update to 6.4 I got the subsequent OTAs.
So 2 month ago, I had registered for the developer Preview of Android 9 on the official website. Got the regular updates until September 1st. Yesterday, we got the official release of the android Pie and I tried to download it. After downloading the 1.4GB update and restarting my phone, it says that the update failed. But when I attempt to check for the latest update, it tells me that I have the latest release and the date the last security patch is on 1st September. Customer care wasn't of any help, so I was hoping you guys would know what's going on here
Cheers
try to clear data of google services framework, restart your phone and check again
Happened to me as well as my cousin who was on Oreo. It shows update failed but we are both on Android 9 with build number 3.22C (0WW_3_22C).
After checking out the new build, there is no change in latest beta and the Android 9 update, I think they have pushed the same ROM with some certifications. All the bugs that was on last beta still persists on this stable build.