Good Evening! I opened this thread to ask if someone could give me an hopinion about a problem I had on mu Nexus 6 after going back to MM from Android N preview. So today I unenrolled my device and I received a Marshmallow OTA, which was said to be the last one available. But as soon as I updated my Nexus, I saw they sent me the OTA with July's Security patch. I tried to wait and see if september's update would show up but nothing in 2 days. Is it normal and have I just to wait or is it a problem? Have you had same experiences?
P.S. I wiped data and everything soon after updating back to MM.
Does it matter if it's the July patch? These security issues are not those that normally happen to users who don't download warez apps. Use Google Play, and you're safe.
But if you want the most recent version, the download the latest OTA from the Google OTA page, and sideload it.
istperson said:
Does it matter if it's the July patch? These security issues are not those that normally happen to users who don't download warez apps. Use Google Play, and you're safe.
But if you want the most recent version, the download the latest OTA from the Google OTA page, and sideload it.
Click to expand...
Click to collapse
Yes, you're actually right about it, security patches are more or less the same for normal users. Let's say, my first worry is about Android Nougat update, because my stock updater does not seem to work properly these last days after I went back to MM. So I thought it might be a matter of time.
Related
Hello everyone.
I`ve got rooted Nexus 6 with Franco kernel. From time to time it shows system security updates, which I install`s. But I notices on my android security patch level stops on January 2016 and still want to install February updates. Everytime N6 tries to install February updates. Does anybody know whats going on? Maybe it`s because I locked with security password on my twrp? After rebooting twrp show`s and I really dont know are updates installed well. I quess not. Can someone help?
And another question, does this android security updates will remove my root?
Shantarien said:
And another question, does this android security updates will remove my root?
Click to expand...
Click to collapse
Security updates will not work; unless the device is completely stock.
You should look at installing the OTA from this page - instructions are provided. If you want to retain the kernel,TWRP & and root you'll have to re-flash them when you're finished.
https://developers.google.com/android/nexus/ota
If you're unencrypted (I'm not - I prefer the security to an extra 10 minutes of battery life) do some reading first - I'm not sure how the OTA works with an unencrypted device. Maybe other members can advise both of us on this point.
Thx for answer`s.
Correct me if I wrong, but I`ve got stock rom, but with Franco kernel, and root, but it`s still stock, right? Does this could be a reason? All my data are encrypted, so maybe this could be a reason ( however after every update reboot I decrypt`s my data), I`ll switch off encrypting my N6 and try again update it.
----------EDIT------------
Guess, NLBeev was right. I can`t make an OTA update when my N6 is rooted, only manually method. I really afraid of this manually updates, because of losing something from my phone, or even brick it.
fear is something that xda can not help you with. itll happen through out life, in many situations. the only thing that you can do is deal with it and move on.
I manually update mine every update and have yet to have an issue.
I f you're encrypted (good!) then my earlier concern is irrelevant. Sideload the newest OTA at the link I gave you. I've done it now several times with two Nexus 5s and a Nexus 6. It's quick and simple and doesn't touch your data.
But I still always take a TWRP backup first and copy it to my laptop. Can't be too careful...
Once again thanks for help! I`ll try install them manually, as fast as I make backup by twrp.
Ach, I forgot, last question, which update should I download? I`ve got January system security updates, so should I download every single one by one? Or just last one (July 6.0.1 (MOB30O))?
Regards!
By "manually' do you mean extracting the separate components (system, radio, boot...)? I strongly recommend the OTA sideload method. Fast and simple, with no data loss.
You need only do it once. Download the MOB30O OTA and sideload it. Then if you want you can flash TWRP and root.
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.
Wife and I just upgraded to Pixel XL. Wife was behind on updates on her Shamu, so I initiated the ota update to 7.0. Update went fine, but when I checked the build number, it is NBD91L.
I didn't think that was possible. The only reference I could find online to this build is that it was an iteration of AOSP leading to NBD91P. No sim card was in the phone at the time of update.
Not really concerned by it, and I know I can just download the ota zip for 91P and sideload it, I just thought it was weird.
Has anyone else had this happen?
I received the same OTA version on my Nexus 6 Shamu.
I was on 7.0.0 NBD90Z, Oct 2016 (I flashed from googles factory images) then, a week or so back I got an OTA for November security update and it gave me NBD91L.
I thought was strange also since it isn't even listed on the google factory image page......Not sure why we both have that image....Anyone else know why this image exists but isn't listed and we weren't given the 91P update? I am on Verizon (is this a vzw specific update?)
I was even thinking of wiping and moving to 91P just to be safe, but wanted to see if anyone else had 91L before I did so....
Also, I am sure the Dec security patch is only days away (probably just wait for that then wipe and start fresh with the new image)
Drootz! said:
I received the same OTA version on my Nexus 6 Shamu.
I was on 7.0.0 NBD90Z, Oct 2016 (I flashed from googles factory images) then, a week or so back I got an OTA for November security update and it gave me NBD91L.
I thought was strange also since it isn't even listed on the google factory image page......Not sure why we both have that image....Anyone else know why this image exists but isn't listed and we weren't given the 91P update? I am on Verizon (is this a vzw specific update?)
I was even thinking of wiping and moving to 91P just to be safe, but wanted to see if anyone else had 91L before I did so....
Also, I am sure the Dec security patch is only days away (probably just wait for that then wipe and start fresh with the new image)
Click to expand...
Click to collapse
My Nexus 6 is still on this build. I didn't think much of it because I gave the phone to my mother in law. I figured she would update when she sees the prompt but she hasn't received one since this build. Pretty disappointing. I know I can side load it but I shouldn't have to after this length of time.
Sent from my Nexus 6P using Tapatalk
My AT&T SGS7 edge was updated to 4BRA1 last night. Besides the January 1 Android security patch, does anyone know if there's anything else different I should notice with this update?
Not noticing anything new, although I expect if I dug deeply a few preloaded apps may have been updated. With a 40MB update, can't expect much besides the security patch.
tamanaco said:
My AT&T SGS7 edge was updated to 4BRA1 last night. Besides the January 1 Android security patch, does anyone know if there's anything else different I should notice with this update?
Click to expand...
Click to collapse
Heres what the ATT Update site says: Android device security updates, including Meltdown and Spectre migration patches (on SPLs Jan. 1 or later)
If you ever want to check out the updates, you can always find it here: https://www.att.com/devicehowto/tut...tep_KM1135854?make=Samsung&model=SamsungG935A
Hope that helps...
Can i update from G935AUCS4API2 (6.0.1) directly to G935AUCS4BRA1 via ODIN and will it wipe my data and would you recommend to factory reset if yes then before update or after update?
Hello all, I currently have the stock 7.1.1 on my G5S+ Italian version.
Some days ago I received the notification for 8.1, so I accepted to download but it stopped at the beginning because the available space was less than 1.2 GB.
I made immediately the space available and tried again in system settings to get the update, but now I can't find it anymore!
In the system information my phone is always declared already up to date with its 7.1.1 (security patch level 1st June 2018).
Of course I already rebooted, but is there any other thing I can do?
Thank you
Why not you try to download and sideload it to your phone and check for the update again.. Please refer to this thread.
https://forum.xda-developers.com/mo...t/moto-g5s-plus-moto-stock-firmwares-t3843626
Aziziamran said:
Why not you try to download and sideload it to your phone and check for the update again.. Please refer to this thread.
https://forum.xda-developers.com/mo...t/moto-g5s-plus-moto-stock-firmwares-t3843626
Click to expand...
Click to collapse
Thank you but I would prefer to let the FOTA work in this case..
I'd recommend not updating... Wifi has become pathetic as it's dropping signals frequently. I see the launcher is consuming too much battery.
7.1.1 was way better. Wish I'd never updated