I have a 32GB Pure edition Moto X. About phone shows:
Code:
Android
5.0
Baseband
MSM8974BP_4125.184.08.27.01R,
VICTARA_TMO_CUST
Kernel version
3.4.42-gd7d30ea
[email protected] #1
Thu Nov 20 06:00:45 CST 2014
System version
22.21.11.victara_tmo.tmo.en.US
Build number
LXE22.46-11
"System Updates" doesn't show any updates available.
So how do I get the latest Lollipop flashed? I've seen different versions around, and don't want to brick my phone.
Is the latest 5.1 or 5.1.1?
THanks
The latest is 5.0 which is why your phone does not show an update. 5.1 is being tested now for our phone. You can side load one of the tests from recovery if you want to try it(be careful if you try to revert, there have been some bricks). Or you can wait for the final release which will hopefully be soon.
Sent from my XT1095 using Tapatalk
Just got the 5.1 OTA, thanks!
Sent from my XT1095 using XDA Free mobile app
Related
Hi everyone I am very confused by all these android 5.1 build numbers. I am currently flashed to LMY47E and using T-Mobile network. But it seems features like WiFi Calling would only be available to T-Mobile build LMY47M.
According to @askdes in Twitter there will be an OTA update from E to M. But since my boot loader is unlocked am I still qualified for OTA? Or I will have to side load again when the factory image is available in Google's website ???
Thank you all for helping.
simoninoc said:
Hi everyone I am very confused by all these android 5.1 build numbers. I am currently flashed to LMY47E and using T-Mobile network. But it seems features like WiFi Calling would only be available to T-Mobile build LMY47M.
According to @askdes in Twitter there will be an OTA update from E to M. But since my boot loader is unlocked am I still qualified for OTA? Or I will have to side load again when the factory image is available in Google's website ???
Thank you all for helping.
Click to expand...
Click to collapse
You can install a OTA when the bootloader is unlocked mate, unless the rom you have is not 100% stock. So it shouldn`t be a problem.
Theres a stock, rooted M build in the development section that you can flash thru TWRP. Since your on T-Mobile i recommend you flash that build. I flashed it over the E build with no issues
Use the factory images to go back to 5.0.1 and either wait for the M ota or sideload
Here's a list of all the 5.1 builds
http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/
Nexus 6
5.0 -> 5.1 (LMY47D - Global): shamu LMY47D from LRX21O
5.0.1 -> 5.1 (LMY47D - Global): shamu LMY47D from LRX22C
5.0.1 -> 5.1 (LMY47I - Australia): shamu LMY47I from LRX22C
5.0.1 -> 5.1 (LMY47M - T-Mobile USA): shamu LMY47M from LRX22C
HipKat said:
Here's a list of all the 5.1 builds
http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/
Nexus 6
5.0 -> 5.1 (LMY47D - Global): shamu LMY47D from LRX21O
5.0.1 -> 5.1 (LMY47D - Global): shamu LMY47D from LRX22C
5.0.1 -> 5.1 (LMY47I - Australia): shamu LMY47I from LRX22C
5.0.1 -> 5.1 (LMY47M - T-Mobile USA): shamu LMY47M from LRX22C
Click to expand...
Click to collapse
Again, this information is speculation. There has been no official confirmation from Google that these builds are carrier or region specific. On the factory images page, no builds are labeled as such. Simply look at the hammerhead images for confirmation. I'm USA on Sprint, running the "I" build. While I don't argue that Verizon models shipped with "E" and T-Mobile is getting "M" as an OTA, these builds will still work on ANY nexus 6.
Am I completely missing something? Last I knew 5.1 was the latest OTA on XT1096, not 5.1.1.
5.1.1 would be a custom rom. 5.1 is the latest official.
Sent from my XT1095 using Tapatalk
AGISCI said:
5.1.1 would be a custom rom. 5.1 is the latest official.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Exactly, but when the word "stock" is stuck in front of "5.1.1" I'm left like
As far as I know, the fixes from android 5.1.1 were included in the 5.1 update moto provided..
So in a matter of speaking, the moto 5.1 ís android 5.1.1
N01tra said:
As far as I know, the fixes from android 5.1.1 were included in the 5.1 update moto provided..
So in a matter of speaking, the moto 5.1 ís android 5.1.1
Click to expand...
Click to collapse
And you think that because?
It seems to me that if that were the case they wouldn't have called it 5.1.
I think I read it in a thread here, or at another forum.. Don't recall.
I concur, it isn't logical to name it 5.1 instead of 5.1.1... But then again, the combo "Moto" and "making good decisions" isn't really happening at the moment
I have a factory shipped nexus 6 that i've been using since day one. I've never updated the firmware nor been promted to, mainly because I'm rooted and running custom roms. I'm currently running Pure 5.1.1
My question is... there is no straight upgrade from LYZ28J to MRA58K. Furthermore, I'm looking at sprints site and they dont list LYZ28J as their firmware, and in-fact its a t-mobile firmware. Is it displaying LYZ28J because of my rom? Do i have to upgrade from LYZ28J -> LYZ28K -> LYZ28M -> MRA58K ??
sprint link: http://support.sprint.com/support/a...ServiceAdvisory_542_GKB80765-dvc8540024prd#!/
memekmek said:
I have a factory shipped nexus 6 that i've been using since day one. I've never updated the firmware nor been promted to, mainly because I'm rooted and running custom roms. I'm currently running Pure 5.1.1
My question is... there is no straight upgrade from LYZ28J to MRA58K. Furthermore, I'm looking at sprints site and they dont list LYZ28J as their firmware, and in-fact its a t-mobile firmware. Is it displaying LYZ28J because of my rom? Do i have to upgrade from LYZ28J -> LYZ28K -> LYZ28M -> MRA58K ??
sprint link: http://support.sprint.com/support/a...ServiceAdvisory_542_GKB80765-dvc8540024prd#!/
Click to expand...
Click to collapse
Over in the other forum, you didn't mention that you were rooted and running a custom ROM. You will never get an OTA installed while in that state. OTAs require a stock target device.
Also, this seems to solve the mystery of how you came to be running a T-Mobile build on Sprint. That obviously was a property of the custom ROM you installed. Sprint did not ship it that way.
boomerbubba said:
Over in the other forum, you didn't mention that you were rooted and running a custom ROM. You will never get an OTA installed while in that state. OTAs require a stock target device.
Also, this seems to solve the mystery of how you came to be running a T-Mobile build on Sprint. That obviously was a property of the custom ROM you installed. Sprint did not ship it that way.
Click to expand...
Click to collapse
Thanks! so do i go through 3 firmware updates to get to the Android M update?
memekmek said:
Thanks! so do i go through 3 firmware updates to get to the Android M update?
Click to expand...
Click to collapse
No. You can't use any of the stock OTA updates on a modded phone.
Once you cross over into the world of custom ROMs, you will never get another automatic update from Google. The ROM developer you went with is responsible for incorporating updates from Google into an updated ROM. ( I see that the Pure Nexus ROM has been updated.)
And you are responsible for flashing that updated ROM manually.
boomerbubba said:
No. You can't use any of the stock OTA updates on a modded phone.
Once you cross over into the world of custom ROMs, you will never get another automatic update from Google. The ROM developer you went with is responsible for incorporating updates from Google into an updated ROM. ( I see that the Pure Nexus ROM has been updated.)
And you are responsible for flashing that updated ROM manually.
Click to expand...
Click to collapse
Everything suddenly makes perfect sense.
If you want back to stock, you just download and flash it yourself... and if your doing that no reason not to just go straight to the latest.
I found a BNIB Moto X to replace my older one with a cracked screen. Out of the box it was on Jelly Bean and after a couple OTA updates it's on 4.4.2 but it's not updating anymore. Checking for updates says the software is update even though on it's an older than current version. Is there any way to bring to a newer Android version without rooting it given this situation?
My recommendation is to leave it on 4.4.2. Lollipop sucks.
I agree, but at least getting the new dialer from 4.4.3 might be nice.
Sent from my XT1053 using Tapatalk 2
I am about to buy a New T-Mobile Samsung Galaxy Note 4 (SM-N910T), and just need to make sure that it would be possible to downgrade the Note 4 from whatever Android version is installed on it to Android 4.4.4 (KitKat).
I checked SamMobile and currently the known Android versions on the Note 4 (SM-N910T) are listed below along with their respective baseband numbers.
My question is this: can all of the basebands (Android versions) listed below for the SM-N910T be downgraded to Android 4.4.4 (Baseband: N910TUVU1ANK4 or N910TUVU1ANJ7 or N910TUVU1ANIH)?
SM-N910T - Baseband number/Android version List:
Date (Baseband) Android Version
2015-11-30 (N910TUVU2DOK2) 5.1.1
2015-11-30 (N910TUVU1COG2) 5.0.1
2015-08-10 (N910TUVU1COD6) 5.0.1
2014-11-24 (N910TUVU1ANK4) 4.4.4
2014-10-17 (N910TUVU1ANJ7) 4.4.4
2014-10-11 (N910TUVU1ANIH) 4.4.4
I definitely need to know this before I buy since I'll be making the purchase online, and won't be able to know which Android version/Baseband version is being shipped in the new package.
Would anyone please help with this question?
No sir. Once on dok2 5.1.1 your locked in. I made that mistake. As long as it's before the latest 5.1.1 your good