Database Users

(Q&A) Any major changes in final release of lollipop (India)

Those who are using Indian soak test before and now using official release in India.... Do you notice any changes?
Sent from my XT1068/69 using XDA Premium 4 mobile app

Soak Testers didn't get the final OTA and will not get it. Reason is, the final OTA rolled out today is the same one soak testers got. They just got it a little early. You can see in the screenshots that everything under About Phone is same in soak test version and final version.

So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc

bla7e said:
So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc
Click to expand...
Click to collapse
Correct. It is like we got the final OTA a little early.

Sri2702 said:
Correct. It is like we got the final OTA a little early.
Click to expand...
Click to collapse
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.

bla7e said:
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.
Click to expand...
Click to collapse
What do you mean by "we do an ota as is"?

Sri2702 said:
What do you mean by "we do an ota as is"?
Click to expand...
Click to collapse
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to

bla7e said:
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to
Click to expand...
Click to collapse
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.

Sri2702 said:
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.
Click to expand...
Click to collapse
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...

bla7e said:
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...
Click to expand...
Click to collapse
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".

Sri2702 said:
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".
Click to expand...
Click to collapse
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep

bla7e said:
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep
Click to expand...
Click to collapse
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?

Wolfcity said:
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?
Click to expand...
Click to collapse
Aside from the ram I highly doubt there's any real difference since when I got mine in the first few days of fiddling around it had the hindi, korean and pinyin keyboards which i disabled so I don't think that would be the case....I mean why would most eu phones need these inputs from the get go. As far as laws go I can't really see much reasoning there either since it's a 130-50eu phone so they can't really have much to complain and unless it somehow magically bricks the device I doubt there would be many if any at all issues...Dunno doe. I'm not motorola so i have no idea what's going on through their heads but it's just kinda silly to me considering that everything's running fine on mine at least without any factory resets or anything....could be just me doe. On another note I think one of my little gripes about lollipop is that it doesn't hide the signal bar for my secondary sim when it's inactive and just shows it. Is this just for me or does everyone have that cuz I didn't pay attention to that on screenshots the last few days

Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.

cmahendra said:
Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426

Sri2702 said:
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426
Click to expand...
Click to collapse
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105

cmahendra said:
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105
Click to expand...
Click to collapse
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?

Sri2702 said:
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?
Click to expand...
Click to collapse
Yes, weird but there is reason. MD5 of old link and new capture matched perfect. Update in link by you and new both are same. Looks like Motorola fooled everyone and rolled same update again.
Anyways! Can anyone share TWRP backup of this version?

some apps bugs ..
Some apps like fifa 15 ut and some others are not supported for locked device and while installing from play store it showed error 505.

Stop making such threads...use the search option instead.

New Verizon Update NMF26U

Looks like there is a new update coming.
https://9to5google.com/2016/12/05/android-7-1-1-update-ota-nexus-pixel-december/
Interesting that it is coming to Verizon pixels but no factory images from Google yet. Curious to see if both models will always have the same updates or if sometimes Verizon models will have specific ones.

This is just the january patch due to be released on the 2nd of Jan

123cyborg said:
This is just the january patch due to be released on the 2nd of Jan
Click to expand...
Click to collapse
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?

b00ster23 said:
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
Click to expand...
Click to collapse
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay

123cyborg said:
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
Click to expand...
Click to collapse
I'm guessing because of the New Year's Holiday the push was delayed. I would suspected it would have come out today. So if it's not out yet, then I'm maybe next Monday. That's if they stick with their current deployment scheme.

Two versions just posted, NMF26U and NMF26V.

sliding_billy said:
Two versions just posted, NMF26U and NMF26V.
Click to expand...
Click to collapse
Haha that was fast :laugh:

I'm on NMF26O. Nothing shows when I click check for updates on my phone. It's Verizon phone with root running on TMobile. Should I go ahead and sideload NMF26V?

and "NMF26V" is international?

thats the question, how can i identfy which one is my OTA file from Europe, version NMF26O

Not sure which version to use. Google phone on Verizon.

Cares said:
Not sure which version to use. Google phone on Verizon.
Click to expand...
Click to collapse
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.

Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.

TonikJDK said:
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Click to expand...
Click to collapse
I got the OTA U on a Verizon phone activated on Project Fi. I'm thinking unless specifically you know to use V then the U update is the way to go if you want to sideload.

Google updated the image site, V is for Europe/O2 and U is for everyone else.

mrjiggywiggy said:
Google updated the image site, V is for Europe/O2 and U is for everyone else.
Click to expand...
Click to collapse
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!

TonikJDK said:
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
Click to expand...
Click to collapse
Well since you have their ear, perhaps you can tweet them to update the OTA images with descriptions. Only the full images have that. Not that it's hard to deduce but since some people sideload the ota rather than wait it might be nice.

fritzgerald said:
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
Click to expand...
Click to collapse
I used 2.79 SR2 and didn't have any problems.

EE simlocked uk versions got nmf26u, i'd think if you have nmf26o then you have the current version for your carrier, which carrier is 'o'

is there a way right now to get the bootloader unlocked on a verizon pixel xl...... 7.1.1?

looks like a new VZW OTA is out

Well it's that time again VZW put out a new OTA anyone taken this yet what does it fix and is it worth it and I think all of us will be wondering is will it lock your bootloader Its unlocked

Me too, I got an OTA notification today, update size is 823.5 MB, don't know what build it is.
I have VZ Pixel, unlocked, stock rooted NMF260 with VZ service. Is it safe to install updates ? Please advice.
Thanks in advance.

azn6929 said:
Me too, I got an OTA notification today, update size is 823.5 MB, don't know what build it is.
I have VZ Pixel, unlocked, stock rooted NMF260 with VZ service. Is it safe to install updates ? Please advice.
Thanks in advance.
Click to expand...
Click to collapse
I think your safe I doubt Verizon would lock your bootloader. That would wipe your device again

@Shiftydogit, @azn6929 got hold of a screenshot? If yes, pls share.

As you can see OTA notification

My guess is it's probably another patch or possibly a kernel update who knows or bug fix one of the three

Here it is

azn6929 said:
Here it is
Click to expand...
Click to collapse
Might as well just do it lmao

So one of you said you are on nmf260. That is December. So i doubt this is a "new" update, you are just behind. Google only releases on the first Monday of the month. VZ uses the same exact releases. There is no special VZ version.
Update away.

TonikJDK said:
So one of you said you are on nmf260. That is December. So i doubt this is a "new" update, you are just behind. Google only releases on the first Monday of the month. VZ uses the same exact releases. There is no special VZ version.
Update away.
Click to expand...
Click to collapse
Brand new update came out yesterday last update was December as you can see

Shiftydogit said:
Brand new update came out yesterday last update was December as you can see
Click to expand...
Click to collapse
Holy cow, they are two months behind. I had no idea, that is nuts. It is the exact same as the Google December update, FWIW.

TonikJDK said:
Holy cow, they are two months behind. I had no idea, that is nuts. It is the exact same as the Google December update, FWIW.
Click to expand...
Click to collapse
Leave it to VZW to be behind on updates as they try to patch everything I think it's safe to update I'll probably do it tonight

Shiftydogit said:
Leave it to VZW to be behind on updates as they try to patch everything I think it's safe to update I'll probably do it tonight
Click to expand...
Click to collapse
That's the crazy part. It is the exact same as what Google released in December. The Pixel's are different...they are only using Googles updates. No changes, no bloat, no nothing.

TonikJDK said:
That's the crazy part. It is the exact same as what Google released in December. The Pixel's are different...they are only using Googles updates. No changes, no bloat, no nothing.
Click to expand...
Click to collapse
Then us VZW users may want to start checking Google for updates instead of waiting for VZW OTAs

Shiftydogit said:
Then us VZW users may want to start checking Google for updates instead of waiting for VZW OTAs
Click to expand...
Click to collapse
They are at the link below, posted the first Monday of each month. Dunno how you get them on an unlocked phone, I know it is doable...just dunno how.
https://developers.google.com/android/ota
EDIT: LOL, I'm an idiot. The instructions are right at the top of the page I linked to.

TonikJDK said:
They are at the link below, posted the first Monday of each month. Dunno how you get them on an unlocked phone, I know it is doable...just dunno how.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
You'd just download them then sideload the OTA via recovery or you can flash it via fastboot/ADB but if you have TWRP installed fastboot will replace it with stock recovery

OK so with update my phone lost TWRP and root other than that bootloader is still unlocked and everything seems fine

Also build number changed after update OK then

If you are getting a new Verizon OTA, it is late. My Verizon Pixel updated to NOF26V (Feb security patch), weeks ago. NOF26V is the most current image for Verizon Pixels.

I updated. New build is NOF26V. Everything seems to be fine. But root is gone. lol

Help me, I'm special

Does anyone have a reasonable explanation as to why one isnt getting certain updates?
The only available update I have is the December 2017 one, but afaik that one is riddled with bugs, and I don't rly feel like risking it. The January never popped up, yet alone february and march one. I've tried all those possible "tricks" with Google Services, from data clean up, signing up for the beta program, factory reset; nothing worked.
I've been told by the support to wait for the batches to arrive; 3 times now.. On the Mi Forums I've been told to sacrifice goats to Chthulu.
My disappointment is immeasurable, and my day is ruined.

Download and flash the fastboot ROM by Mi Flash Tool.

Zoldannah said:
On the Mi Forums I've been told to sacrifice goats to Chthulu.
My disappointment is immeasurable, and my day is ruined.
Click to expand...
Click to collapse
LOL! Well, did you do it?
You can try the miflashtool method.

LouisMuruu said:
LOL! Well, did you do it?
You can try the miflashtool method.
Click to expand...
Click to collapse
An entire stock. Did not work ??*
I've never done flashing before, I'm nutorious for ****ing things up. Why can't I just get the OTA the way it's mean to be received ffs

Zoldannah said:
An entire stock. Did not work ??*
I've never done flashing before, I'm nutorious for ****ing things up. Why can't I just get the OTA the way it's mean to be received ffs
Click to expand...
Click to collapse
You are probably on nougat. You need to update to the december Version (oreo preparation) and then you can update to march from there.

The OTA updates are incremental updates from a specific firmware version so you have to go through the sequence of all the updates. You can't just jump over several in one go.

t-bon3 said:
The OTA updates are incremental updates from a specific firmware version so you have to go through the sequence of all the updates. You can't just jump over several in one go.
Click to expand...
Click to collapse
I've seen ppl saying they've got both dec + jan simultaneously.. But I guess this explains it; Thanks babes!

Well, can I ask why are you so special ??

shubham8 said:
Well, can I ask why are you so special ??
Click to expand...
Click to collapse
Special in a sense of being mentally challenged; self degradation. Don't worry, I'm not being condescending ?

B392 Update now out for FRDL04 users

B392 Update is now out for us FRDL04 users. Based on the description it's just security patches and nothing major. Update file size is 170MB.

xsacter said:
B392 Update is now out for us FRDL04 users. Based on the description it's just security patches and nothing major. Update file size is 170MB.
Click to expand...
Click to collapse
just got mines.. it was quick tho the next security patch.. normally we would have to wait may lol

Does anyone need the raw img files to manually flash from adb commands?
I extracted them and plan to flash my frd-L04 later to keep root and twrp.
Sent from my FRD-L04 using Tapatalk

Rickymills said:
just got mines.. it was quick tho the next security patch.. normally we would have to wait may lol
Click to expand...
Click to collapse
True lol. I think there's maybe one more security patch and then we should be receiving the Oreo update, since I saw Honor recently tweet about Oreo preparation for the Honor 7x.

Yup I finally got it. Looks like it is rolling out to everyone today.

xsacter said:
True lol. I think there's maybe one more security patch and then we should be receiving the Oreo update, since I saw Honor recently tweet about Oreo preparation for the Honor 7x.
Click to expand...
Click to collapse
Lol. I know one of the devs for Honor USA and there is NO Oreo release for the 7x for main distribution yet. They just started the beta a month ago. Go check honor USA beta group on Facebook if you need confirmation.

agraceful said:
Lol. I know one of the devs for Honor USA and there is NO Oreo release for the 7x for main distribution yet. They just started the beta a month ago. Go check honor USA beta group on Facebook if you need confirmation.
Click to expand...
Click to collapse
Says here EMUI 8.0

yep got mmine..

Just updated.
How's the battery life on this one?

tiguy99 said:
Just updated.
How's the battery life on this one?
Click to expand...
Click to collapse
Honestly I see no difference

Hi guys,
I just got this update too on my FRD L04. Since it's been a while I factory reset after an update, I did so to clean up my phone of all the other junk I've been stacking. Well this was a huge mistake because now the my bluetooth earphone won't connect to my phone. Before factory resetting, and on B392 it worked perfectly fine, I don't know why and how the factory reset messed with the Bluetooth connectivity. Anyone have a solution for this? Thanks.