I'm seeing an update for this phone and I don't know if I should. I know that since my bootloader is unlocked I can flash if need be but I'm not sure once I update this I will lose the ability for custom ROMs that require an earlier firmware.
It shouldn't be an issue. This update is pretty much just an upstream on the September security patch
Related
Hi!
I have a question:
If I'll just unlock the bootloader (no root or recovery), will I be able to install OTA updates?
If yes, can I root it and still install OTA's?
I'm ok with having to reroot, but can I install OTA's while I have a custom recovery and root?
Thank you!
EDIT:
Thanks to ollie_o I found a solution, see below for details
I was wondering the same - I've had one small OTA update when I first turned the phone on, but nothing since I unlocked the bootloader - has there been a December security update yet?
Can anyone confirm what the most recent OS version / security update is?
Mine's running the LMY48B build (Oct 7) with the November security update (2015-11-01)
Found out the solution!
benjymous said:
I was wondering the same - I've had one small OTA update when I first turned the phone on, but nothing since I unlocked the bootloader - has there been a December security update yet?
Can anyone confirm what the most recent OS version / security update is?
Mine's running the LMY48B build (Oct 7) with the November security update (2015-11-01)
Click to expand...
Click to collapse
Thanks to olli_o, I was able to find the answer:
You can't update with root, I don't know about unlocked bootloader, but you can install updates manually even if you are rooted. You just need to re-install the root after each update
Link to guide: http://forum.xda-developers.com/wileyfox-swift/general/rom-wileyfox-swift-t3267037
:good: Thank you olli_o :good:
Hey, just bought brand new 5x and I'm still on 6.0 with oct 1sr 2015 security patch. When I go to system updates it says I'm up to date. Am not getting OTA update automatically. Im on Telenor in Serbia. Should I wait or do I have to root and flash the latest update manually?
Btw, looove the handset and OS is lagfree, no issues, but still wonder why I'm not getting the latest update. No root, LB, brand new OTB device.
5ageman said:
Hey, just bought brand new 5x and I'm still on 6.0 with oct 1sr 2015 security patch. When I go to system updates it says I'm up to date. Am not getting OTA update automatically. Im on Telenor in Serbia. Should I wait or do I have to root and flash the latest update manually?
Btw, looove the handset and OS is lagfree, no issues, but still wonder why I'm not getting the latest update. No root, LB, brand new OTB device.
Click to expand...
Click to collapse
to update it manually u don't need to have root access.
But if u like to try some new 3rd party ROMs root it :good:
Geeks Empire said:
to update it manually u don't need to have root access.
But if u like to try some new 3rd party ROMs root it :good:
Click to expand...
Click to collapse
How do I update manually? Any recommended guides? I dont feel the need to flash a custom rom, I like what google is doing with android as is for now. Just want the lates and greatest, thats why I bought a nexus.
Also would like to know the reason why I am I not getting updates automatucally. I have the international H791 model. Firmware version MDA89E. Its two OTAs outdated.
Quick thought: Shut down, remove SIM, Start the device, Connect to Wifi, Check for updates.
Just unboxed a brand new 5X 10 minutes ago and have the exact same problem...
Tried to reboot and added a Google account, charged the battery to 100% but the thing still won't find a new system version...
marioemp2k7 said:
Quick thought: Shut down, remove SIM, Start the device, Connect to Wifi, Check for updates.
Click to expand...
Click to collapse
Tried that too. I activated the device without the SIM and used it that way yesterday, inserted it just today.
Than I guess you can't do anything else unless you unlock the bootloader. At this point you can fastboot \system \boot \radio \vendor from the latest factory image or you can sideload ota zip through stock recovey.
I am having the same issue, my new nexus 5x is on 6.0 MDB08L, securiry patch level: November 1, 2015.
When I check for updates it says that my device is up to date...
The OTA will show up eventually. Or update manually.
Same thing for me in Canada. I just ended up enrolling in the Android Beta to get N preview.
Issue solved!
I got a ton of OTAs overnight while device was charging. I think it was 5 OTAs one by one that had to be installed separately, now I am on the latest April security patch and loving my nexus even more. No noticable performance difference, smooth and snappy and now up to date. So I guess updates will come you just have to be patient so google can activate them for your device. In my case it was 2 days since activation.
Info
5ageman said:
How do I update manually? Any recommended guides? I dont feel the need to flash a custom rom, I like what google is doing with android as is for now. Just want the lates and greatest, thats why I bought a nexus.
Also would like to know the reason why I am I not getting updates automatucally. I have the international H791 model. Firmware version MDA89E. Its two OTAs outdated.
Click to expand...
Click to collapse
[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot
http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
How to download and install the Android Marshmallow OTA update on Nexus devices
http://www.digitaltrends.com/mobile/how-to-install-ota-updates-on-google-nexus-devices/
:good:
I have several Moto Z Plays here; two are retus and one is reteu. The reteu one is running 7.1.1 (official version, not a soak test, NPN26.118-22) because I downloaded the official update and sideloaded it yesterday. It has the July security patch. I was never a soak tester, either. The retuses are still on 7.0, May security patch (NPN25.137-24.4).
Here's the issue. When I sideload NPN26.118-22 (7.1.1. official) on a retus, I get an error saying "E3002: Package expects build thumbprint of 7.1.1/NPN26.118-22/21:user/release-keys or 7.0/NPN25.137-24.3/4:user/release-keys; this device has 7.0/NPN25137-24.4/5:user/release-keys," and it fails. (This also happened on reteu, but I happened to have the package it wanted to see, so I installed it first. See below.)
So, my next move is to replicate what worked on reteu, which was to flash the other package I have first, but I get another error saying "E3002: Package expects build thumbprint of 7.0/NPN25.137-24.3/4:user/release-keys or 7.0/NPNS25.137-24-1-9/10:user/release-keys; this device has 7.0/NPN25.137-24.4/5:user/release-keys."
I'm sort of at a loss from here of what to do, since the May security update for retus does seem to prevent compatibility with flashing any new package. The reason this wasn't an issue on the reteu one was, I'm assuming, because it was on the April security update, and I was able to install the second package, and then finally official 7.1.1 to get it current.
Anyone have any ideas? I can't be the only one running this freaking NPN25.137-24.4 (May) update on the retus Z Play that is preventing me from sideloading official 7.1.1. Thanks in advance!
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Zeljko1234 said:
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Click to expand...
Click to collapse
I appreciate your reply, but this isn't really relevant to my question at all. I acknowledge there are risks with flashing, but I did it successfully on one of my devices and it's really not the scariest thing I've ever done on ADB.
If you're content to wait, that's fine; what I want to know is the reason why I can't seem to do it on 2/3 of my devices. I'd appreciate responses that are relevant to my question.
I replied to your post on reddit, but I'll share it here too. Someone may even correct me here on XDA if I've got any info wrong.
The 7.1.1 that was released to most of us (retbr, retca, etc) require the build number NPN25.137-24.3 (May 2017 security patch) to be installed.
The May security patch on retus has the build number of NPN25.137-24.4 (I guess there was a change that warranted the .4 over .3). All retus phones will have this build number if they've installed the May patch.
This is why you were getting errors when trying to sideload 7.1.1 onto the retus phones (trying to install an update not meant for the device). retus will likely get a different install package for Android 7.1.1
How do you sideload using stock recovery? I tried adb devices and my device is not listed. I want to sideload Google stuff to stock ROM, any idea how to do that? Tried to install the APK files manually but I got force closed after that. Thank you.
how to downgrade from 8.0 to nougat?
ZeroVirus said:
how to downgrade from 8.0 to nougat?
Click to expand...
Click to collapse
Just a friendly reminder, never ever downgrade your bootloader and accept/install OTA's unless you are ready and prepared to unbrick your device. Many folks had brick their devices when they downgrade their bootloader and accept ota. If u are in a soak test firmware then best thing to do is wait until they release the 2nd or final soak firm. :good:
ZeroVirus said:
how to downgrade from 8.0 to nougat?
Click to expand...
Click to collapse
Just flash 7.1.1 firmware
LabLab...28 said:
Just a friendly reminder, never ever downgrade your bootloader and accept/install OTA's unless you are ready and prepared to unbrick your device. Many folks had brick their devices when they downgrade their bootloader and accept ota. If u are in a soak test firmware then best thing to do is wait until they release the 2nd or final soak firm. :good:
Click to expand...
Click to collapse
But what if i am just flash other thing accept bootloader?
ZeroVirus said:
But what if i am just flash other thing accept bootloader?
Click to expand...
Click to collapse
Downgrading your stock firmware generally will not downgrade your bootloader (you'll usually see a security downgrade error and/or pre-flash validation error if you try).
So if you do downgrade, you'll likely have an (newer) Oreo bootloader and (older) stock Nougat system. If you attempt to use a stock Nougat OTA update, the Nougat OTA may corrupt your newer Oreo bootloader and hard brick your device. OTA updates appear to only check if your system is the correct patch level, and do not appear to determine if your bootloader is of the same patch level. As you've downgraded, this mismatch of bootloader/stock system patch levels and stock OTA corruption is why downgrading is risky. The act of downgrading won't cause you issues, the use of stock OTA updates (regardless of whether they're from XDA or Motorola) may well cause you issues.
If you downgrade to the December 2017 7.1.1. firmware and it emerges that the next OTA update you receive is the Oreo OTA, you may be okay. However, if you downgrade and receive a Nougat OTA (e.g. you downgraded to the Nov 2017 firmware, or there is another Nougat OTA before the Oreo OTA), you may encounter serious trouble. We saw similar issues when the 7.1.1 soak test got leaked - users would downgrade from 7.1.1 to 7.0 and proceed to hard brick when they attempted to use OTA updates (because they had a newer bootloader). Luckily, we had a blankflash then, I do not know if the blankflash will still work for Oreo bootloaders.
As mentioned above, you can wait for the soak test OTA updates to be leaked or wait for the Oreo stock firmware to be captured, which should be safer to update with.
Hey all, I'm still on June 1st security patch (NCX26.2), T-Mobile variant and stock, with bootloader unlocked which seems to be preventing my phone from updating to the latest OTA. I'm getting served with NCX26.7, but the update keeps failing.
Could someone post step by step on how to update my phone to the most recent rootable OTA (perhaps sideload?), and then what would be the easiest way to root. I don't mind wiping the entire device as long as it gets me to the latest software patch.
*EDIT* Now looking at the settings, it seems like I've flashed my Kernel months ago, which is likely what's causing my phone not to update. If I follow the Flash-all guide, will that reset the kernel to stock? Screenshot attached.
Many thanks!
milan03 said:
Hey all, I'm still on June 1st security patch (NCX26.2), T-Mobile variant and stock, with bootloader unlocked which seems to be preventing my phone from updating to the latest OTA. I'm getting served with NCX26.7, but the update keeps failing.
Could someone post step by step on how to update my phone to the most recent rootable OTA (perhaps sideload?), and then what would be the easiest way to root. I don't mind wiping the entire device as long as it gets me to the latest software patch.
*EDIT* Now looking at the settings, it seems like I've flashed my Kernel months ago, which is likely what's causing my phone not to update. If I follow the Flash-all guide, will that reset the kernel to stock? Screenshot attached.
Many thanks!
Click to expand...
Click to collapse
yes