Develop Bugs

[Q] 2013 Nexus 7 LTE Current Build?

What is the latest build? I see all these builds and posts from the 18th saying this version or that. None match mine and i want to be sure before rooting since OTA will be gone at that point. I cleared google service framework and it is NOT rooted and the bootloader is locked, i will do all that once its on the latest version. It shows build JLS36C is this the latest as of Sept 20th?

jasunto said:
What is the latest build? I see all these builds and posts from the 18th saying this version or that. None match mine and i want to be sure before rooting since OTA will be gone at that point. I cleared google service framework and it is NOT rooted and the bootloader is locked, i will do all that once its on the latest version. It shows build JLS36C is this the latest as of Sept 20th?
Click to expand...
Click to collapse
JLS36C is the latest for the LTE variant.

Yeah took a while of googling and I figured it out. BTW the AT&T deal $100 bill credit isn't possible. Need two year contract and can't do that unless you buy device from AT&T and they don't sell. I just tried. Added to my family share plan anyway.
Sent from my HTC One using Tapatalk 4

Moto X Force (XT1580) Android 7.0 NOUGAT is finally here! (25.11.12.en.EU) UPDATED

Moto X Force Official Android 7.0 Nougat Release Note - https://motorola-global-en-aus.custhelp.com/app/answers/prod_answer_detail/a_id/118889
​Model: Motorola MOTO X Force XT1580
System version: 25.11.12
Build number: NPK25.200-12
Android Version: Android 7.0 Nougat
Android Security Patch Level: 1st April 2017
I have received the update and installed it too! Everything seems buttery smooth and faster than before! Install it now! :good:
​
​
Note: I do not know how to extract OTA file from the update, so hope someone could be able to help in sharing the OTA zip file with us.

Seems you are using VPN to receive the update. Which VPN are you using? What is your / the VPN location?

Which screen protector You use? Looks good, any specs or link? I'm in Germany, still no update for eu version.

Seems like only the Motorola employees are getting the update. above photos are familiar to me. Seen somewhere in Facebook page of Moto.

FredericDelany said:
Seems you are using VPN to receive the update. Which VPN are you using? What is your / the VPN location?
Click to expand...
Click to collapse
Hi, I am not using VPN. Just using Adguard. I need to turn on the VPN to activate Adguard adblocking. Cheers!

zammi said:
Seems like only the Motorola employees are getting the update. above photos are familiar to me. Seen somewhere in Facebook page of Moto.
Click to expand...
Click to collapse
Hi, this phone is a retail version from the store. And the photos belongs to me and I shared to some Facebook pages.
You should be getting your update soon!

zammi said:
Seems like only the Motorola employees are getting the update. above photos are familiar to me. Seen somewhere in Facebook page of Moto.
Click to expand...
Click to collapse
Nope. Mine is UK retail. The update came yesterday.
Sent from my XT1580 using Tapatalk

bobyn said:
Nope. Mine is UK retail. The update came yesterday.
Click to expand...
Click to collapse
Mine also UK retail. No update yet.

What network are you on?

The most important question, were you guys able to keep root, or install root after updating to Nougat? Thanks!

Yeah, with unlocked bootloader it's easy, just flash a zip in TWRP

Thank you Lonixlon, have you personally updated your X Force while having TWRP? I had a problem with installing OTA security patch as phone booted directly to TWRP. Do you know any workaround for that?

can anyone help this guy to share OTA file?

My idea, maybe stupid and wrong - Update arrives depending on the CID of the phone.
The version of the system says "retapac", which stands for "Retail Asia Pacific" - a retail version of the phone for Asia and the Pacific.
But I do not understand what is written in "On the phone" before upgrading to NUGA. Take on incomprehensible things, mismatches, in the version of Android, the Baseband version, the system version and the build number. In the build number is very old version of the system mpks24.78-8-12, in the version of the system is the latest version of the system with the upgrade to 6.0.1, but here the old version 6.0 and the old modem.
I have a lot of questions without answers ...

ilia3367 said:
My idea, maybe stupid and wrong - Update arrives depending on the CID of the phone.
The version of the system says "retapac", which stands for "Retail Asia Pacific" - a retail version of the phone for Asia and the Pacific.
But I do not understand what is written in "On the phone" before upgrading to NUGA. Take on incomprehensible things, mismatches, in the version of Android, the Baseband version, the system version and the build number. In the build number is very old version of the system mpks24.78-8-12, in the version of the system is the latest version of the system with the upgrade to 6.0.1, but here the old version 6.0 and the old modem.
I have a lot of questions without answers ...
Click to expand...
Click to collapse
Well, may I express my opinion here too. I have an XT1581 Kinzie from China, it came with Lollipop 5.1.1. Workling perfect.
I go and update it to MM 6.0 using a Mexican or LKatin America rom, I keep the modem for the baseband from the Lollipop 5.1.1 Chinese rom, everything works almost better than before, not a single issue.
Now,m I tried to update it to Nougat 7 following the Google+ guide, a nightmare, although an enjoyable one!
First, I have only one sim working, no wif. Try anoth system, now I have two sims OK but still no wifi.
At the end, after many trials, I went back to my old MM 6.0 LAt rom, backed using TWRP, and the system is back to normal with everything working OK.
Did you ask me if I'm going to change? Nope, I'm happy the way things are, unless an official Nougat 7 ir 7.1.1 rom comes by, not loosing other time.
I agreemthere is a lot of confusion between the various roms and regions.

This news about the update and the video is very similar to the fake... Just why from such an ordinary case as an update do such a stupid circus?

not yet arrived in Indian version XT1580

neither for reteu.retfr

I have moto x play, is that mean android nougat not so far from us...??

[New Firmware] 47.2.A.4.41 [G8441]

new Firmware 47.2.A.4.41 for Xperia™ XZ1 Compact (G8441)

I can't find any changelog. Where can I find it?

security update

profyler said:
security update
Click to expand...
Click to collapse
Could you provide a link to the source of your claim? Where we can see that it's *only* security update....

komer said:
Could you provide a link to the source of your claim? Where we can see that it's *only* security update....
Click to expand...
Click to collapse
How should he if there is none? It's a ~350mb update, that's usually just a security update with maybe some bugfixes.

So did it OTA anywhere?

landsome said:
So did it OTA anywhere?
Click to expand...
Click to collapse
Customized CH did, indeed.

Silly question : Would an update, like this one, need to update with previous versions first before upgrading to this one ? I'm asking this because here in the UK, I'm still with the Customized UK 47.1.A.16.20. And I've never had any Pie update available displayed on my phone.
Several versions have been dispatched to other zones in the world, including several for different UK providers but then hang in the middle of the roll out. Plus in the Support > Software section of my G8441, it says in the "Next Android version" sub section : "No new Android version planned yet".
It looks weird, isn't? Not to mention after Sony started to roll out their very first Pie firmware for the G8441, my Xperia Companion said a new Software version was available, with no description, no firmware version number, and when trying to download it, Xperia companion crashed and needed to restart. Few hours later, when opening it again, the 'New Software' notification disappeared. Since then my phone displays "No new Android version planned yet".
Is this related ?
Thanks in advance, and sorry for the half off-topic...

I too have the customized UK phone, and nothing here either

Does someone know which .sin files to exclude if I want to install the new firmware (I already have Pie) with newflasher but want to keep my existing settings, apps and data?
I know that persist*.sin should be excluded to avoid losing android assets keys and userdata*.sin also I guess by the name. Anything else?
I have an unlocked bootloader with DRM keys backed up and restored with Customized CH 47.2.A.2.33 installed. I also have flashed the secd patch so the phone offers OTA update, but I know it won't work with the bootloader unlocked.

Came OTA in Switzerland. Update worked like a charm and I don't see any changes except for December security patch.

beggar23 said:
Customized CH did, indeed.
Click to expand...
Click to collapse
I do not see it if I vpn to Switzerland.

landsome said:
I do not see it if I vpn to Switzerland.
Click to expand...
Click to collapse
Updates don't work like that. If you have the CH ROM, you'll get the OTA for that. If you have UK rom, you'll get the UK rom update regadless of the place you are in.
You can manually flash a different rom customization (uk, ch, nordic etc) and then het updates for that one. I don't know if there are some disadvantages doing that though, as some customizations might have specifoc stuff for some countries / carriers.

beggar23 said:
Customized CH did, indeed.
Click to expand...
Click to collapse
vofferz said:
Updates don't work like that. If you have the CH ROM, you'll get the OTA for that. If you have UK rom, you'll get the UK rom update regadless of the place you are in.
You can manually flash a different rom customization (uk, ch, nordic etc) and then het updates for that one. I don't know if there are some disadvantages doing that though, as some customizations might have specifoc stuff for some countries / carriers.
Click to expand...
Click to collapse
I do have CH. I flashed CH manually a long time ago, as I was not getting any updates (missed several months) on my DE. I have gotten many regular OTAs since and did a few resets. But I did not get any of the Pie versions. I thought maybe it is actual location...

I'm in the UK boat, I've been a Sony user since the Xperia arc and I've certainly had some long waits for software updates but I can't remember seeing so many versions released without the UK sim free getting any of them. Can't see my next phone being Sony now.

frankie99969 said:
I'm in the UK boat, I've been a Sony user since the Xperia arc and I've certainly had some long waits for software updates but I can't remember seeing so many versions released without the UK sim free getting any of them. Can't see my next phone being Sony now.
Click to expand...
Click to collapse
From what I am deducting all around the web (Sony forums, XDA, 4pda) just keep Oreo and don't bother seeing the number 9 instead of the 8 in the about section of your phone.
I had the OTA update notification for a few weeks, neved installed and eventually it disappeared because Sony has shut down the updates as of Pie bugs reported in their forums.
I am still on latest Oreo and I am going to keep it until I see a totally polished Pie, and it will take months!
Apart from slowmo 960fps in FullHD I truly do not see any reason to update, because the cons are more than pros.
Sure, security patches will be up to date, but does anyone feel the difference having a few month outdated patches? The security is in the hands of the user.
Sent from my XZ1 Compact using XDA Labs

about updating without loosing any data (as same as it was)
I just remove all. . Ta files and IF you want to keep like it was dont Flash userdata or appslog..

Just updated.. Use to go with MY Malaysia version

vofferz said:
Does someone know which .sin files to exclude if I want to install the new firmware (I already have Pie) with newflasher but want to keep my existing settings, apps and data?
I know that persist*.sin should be excluded to avoid losing android assets keys and userdata*.sin also I guess by the name. Anything else?
Click to expand...
Click to collapse
I'd also love to know.
I have an unlocked bootloader with DRM keys backed up and restored with Customized CH 47.2.A.2.33 installed. I also have flashed the secd patch so the phone offers OTA update, but I know it won't work with the bootloader unlocked.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, are you still able to encrypt internal and external?

frankie99969 said:
I'm in the UK boat, I've been a Sony user since the Xperia arc and I've certainly had some long waits for software updates but I can't remember seeing so many versions released without the UK sim free getting any of them. Can't see my next phone being Sony now.
Click to expand...
Click to collapse
They are in the early days for Android 9 Pie. And Sony is one of the first companies to release pie updates. It's buggy, which is the usual after updating to a new major android version. The previous version 47.2.A.2.33 was not even completely rolled out before this current version started rolling out. I'm sure the usual rollout schedule will continue as the software matures.

June 19's ROM update, Verizon-specific

All my Pixels have been Google-branded. Over the years, there have been carrier-specific builds during some updates. I have seen it for Verizon and T-Mobile. I have used both the generic version and carrier-specific builds and they work fine in the Google-branded Pixels.
I am still curious, though, what is Google's intent for these carrier-specific builds? Should the Google-branded Pixel always run the generic build, or if I am using a Verizon SIM, I should use the Verizon-specific build?
My phone is rooted, so I never OTA.

The carrier specific builds usually have either different bootloader or radio images than the Google stock build. My guess as to why Google does this is that the carrier submitted their changes somewhat late in the cycle and Google doesn't want to risk rolling them out to everyone until they are sure it works as intended, since they usually go back to a single stock build the next month that includes the carrier specific items. As to which build to use my experience has been that a Google branded phone with a Verizon sim will try to take a Stock OTA if the difference is the bootloader and the Verizon OTA if it is the radio. I have downloaded and looked at both versions and the bootloader is the difference so I would use the Google stock image.

DougMG said:
I have downloaded and looked at both versions and the bootloader is the difference so I would use the Google stock image.
Click to expand...
Click to collapse
To confirm my understanding -- you compared the June firmware between the Google and VZ version, and the only difference is the bootloader? Thanks.

snovvman said:
To confirm my understanding -- you compared the June firmware between the Google and VZ version, and the only difference is the bootloader? Thanks.
Click to expand...
Click to collapse
Correct.

june 19?

I honestly don't think it matters. I didn't even notice that there was a Verizon version and was in a rush getting ready to leave work. I accidentally downloaded and flashed the Verizon version to my Google branded 3XL on AT&T and it's doing fine. I've had no issues.

General New report of actual Verizon OTA SD1A.210817.037.A1 on Pixel 6/Pro

@pntballer505 reports getting the .037.A1 OTA on Verizon at post #138.
Old Verizon OTAs:
Several reports of the actual Verizon .036.A1 OTA, starting with @stevek216 at post #126.
Click to expand...
Click to collapse
https://support.google.com/pixelpho...t-software-to-get-all-the-features?hl=en&s=09
Checking for the software update
[Please check your device to see if you already have the latest software installed. Verify your Build number matches the official build by checking Settings -> About phone -> Build number. See section below]
After you complete the phone setup, the software update automatically downloads silently in the background. After the download completes, it will prompt you to reboot the phone. In case the software update is not seen, follow the instructions below:
Go to Settings -> System -> System update -> Check for update
Install the software update
Depending on your network connection speed and amount of apps involved, this will take about 25-50 minutes
Reboot the device after taking the update
Updating your apps
Many of the key apps have new features and improvements for Pixel 6. Please check to make sure that your apps are up to date by going to Play Store -> Your Account Icon -> Manage apps & device -> Update all.
Timing
Due to deployment timelines and staged rollouts, some updates may not be available until 10/28.
Software update Build number
After the software update, your device software version (Settings -> About phone -> Build number) will be be one of the following:
SD1A.210817.036
SD1A.210817.036.A8 (Verizon customers)
Click to expand...
Click to collapse

Not available for me just yet. Will try again on the 28th as the article mentioned.

Already updated to SD1A.210817.036 with SP dated 05/11 (UK) edited for typo

My unlocked Pixel 6 Pro purchased from Google Store USA has SD1A.210817.019.C2 and no updates.

No update yet. Here's to hoping for sometime today or tomorrow.

Mine is updating now, 64.35 MB, I'll update with before and after build numbers when it finishes.
EDIT: Almost an hour later and it's still optimizing apps, around 50%. Took about an hour and a half and a reboot, finally updated.
Unlocked model from Google Store USA.
Before:
Build Number: SD1A.210817.019.C2
Android security update: Oct 5
Baseband: g5123b-91479-210916-B-7738070
After:
Build Number: SD1A.210817.036
Android security update: Nov 5
Baseband: g5123b-92009-211008-B-7805583

Taking a long time. Really sweet phone.

nxt said:
My unlocked Pixel 6 Pro purchased from Google Store USA has SD1A.210817.019.C2 and no updates.
Click to expand...
Click to collapse
Same, nothing to update to.

GohanBurner said:
Same, nothing to update to.
Click to expand...
Click to collapse
It will come if they build it. I setup and popped the sim in. Be patient. It takes an hour to download. Damn. It's still updating. Best phone I ever had. I don't understand these complainers

I have an unlocked Pro used on Verizon but didn't get an update. Currently on SD1A.210817.019.C2

Golf c said:
Taking a long time. Really sweet phone.
Click to expand...
Click to collapse
Yeah took forever for me too, optimising apps. Build Number: SD1A.210817.036

Cares said:
I have an unlocked Pro used on Verizon but didn't get an update. Currently on SD1A.210817.019.C2
Click to expand...
Click to collapse
They are rolling out slowly. You'll get it in time.

Cares said:
I have an unlocked Pro used on Verizon but didn't get an update. Currently on SD1A.210817.019.C2
Click to expand...
Click to collapse
Did you receive the update in the meantime? I still haven't

nxt said:
Mine is updating now, 64.35 MB, I'll update with before and after build numbers when it finishes.
EDIT: Almost an hour later and it's still optimizing apps, around 50%. Took about an hour and a half and a reboot, finally updated.
Unlocked model from Google Store USA.
Before:
Build Number: SD1A.210817.019.C2
Android security update: Oct 5
Baseband: g5123b-91479-210916-B-7738070
After:
Build Number: SD1A.210817.036
Android security update: Nov 5
Baseband: g5123b-92009-211008-B-7805583
Click to expand...
Click to collapse

My P6 Pro still can't find the update
Supposedly the update should fix my fingerprint reading issues, so I'm sorta stoked to see that one comin' rather sooner than late.
Any way to force it? Stil no factory images/OTA, so I'm out of options.

No update here yet either (Google Store Unlocked on the Verizon network).

Indashio said:
Fingerprint and description from AIDA64 ?
Click to expand...
Click to collapse
I saw your previous post but I don't know where to find those. Give me exact specific instructions on where to find those, if I have to download an app, no thank you.

Morgrain said:
My P6 Pro still can't find the update
Supposedly the update should fix my fingerprint reading issues, so I'm sorta stoked to see that one comin' rather sooner than late.
Any way to force it? Stil no factory images/OTA, so I'm out of options.
Click to expand...
Click to collapse
Does it really fix fingerprint issues? do we have the changelog?

No changelog yet that I am aware of, only reports of people claiming that after the update you have to re-learn the fingerprint scanner and then it supposedly works better.

thx, could be just feeling