[REF] Nexus 9 Stock OTA URLs - Nexus 9 General

This thread compiles all known OTA updates for the Nexus 9 WiFi-only and LTE variants.
Nexus 9 WiFi (flounder 0P82100) - volantis
Current firmware: Android 6.0, Build MRA58N
MRA58N from MRA58K - https://android.googleapis.com/pack...5f522d.signed-volantis-MRA58N-from-MRA58K.zip
------------------------------------------------------
MRA58K from LMY48T - https://android.googleapis.com/pack...83199e.signed-volantis-MRA58K-from-LMY48T.zip
------------------------------------------------------
LMY48T from LMY48M - https://android.googleapis.com/pack...26824b.signed-volantis-LMY48T-from-LMY48M.zip
------------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack...gned-volantis-LMY48M-from-LMY48I.a8f87fa0.zip
------------------------------------------------------
LMY48I from LMY47X - https://android.googleapis.com/pack...olantis-LMY48I-from-LMY47X-superblock-fix.zip
------------------------------------------------------
LMY47X from LRX22L - https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
------------------------------------------------------
LRX22L from LRX22C - http://android.clients.google.com/p...gned-volantis-LRX22L-from-LRX22C.61f6bdb8.zip
LRX22L from LRX22C - https://android.googleapis.com/pack...olantis-LRX22L-from-LRX22C-fix-superblock.zip (Superblock)
------------------------------------------------------
LRX22C from LRX21R - http://android.clients.google.com/p...ned-volantis-LRX22C-from-LRX21R.3c1c62441.zip
------------------------------------------------------
LRX21R from LRX21L - http://android.clients.google.com/p...is-LRX21R-from-LRX21L-factory-recovery-ok.zip
LRX21R from LRX21Q - http://android.clients.google.com/p...is-LRX21R-from-LRX21Q-factory-recovery-ok.zip
------------------------------------------------------
LRX21Q from LRX21L - http://android.clients.google.com/p...gned-volantis-LRX21Q-from-LRX21L.e0ce5d82.zip
Nexus 9 LTE (flounder_lte 0P82200) - volantisg
Current firmware: Android 6.0, Build MRA58N
MRA58N from MRA58K - https://android.googleapis.com/pack...4db5d.signed-volantisg-MRA58N-from-MRA58K.zip
------------------------------------------------------
MRA58K from LMY48T - https://android.googleapis.com/pack...8ab3d.signed-volantisg-MRA58K-from-LMY48T.zip
------------------------------------------------------
LMY48T from LMY48M - https://android.googleapis.com/pack...f9311.signed-volantisg-LMY48T-from-LMY48M.zip
------------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack...ned-volantisg-LMY48M-from-LMY48I.fd894caa.zip
------------------------------------------------------
LMY48I from LMY47X - http://android.googleapis.com/packa...lantisg-LMY48I-from-LMY47X-superblock-fix.zip
------------------------------------------------------
LMY47X from LRX22L - http://android.googleapis.com/packa...ned-volantisg-LMY47X-from-LRX22L.3c854210.zip
------------------------------------------------------
LRX22L from LRX22C - http://android.googleapis.com/packa...ned-volantisg-LRX22L-from-LRX22C.05a03333.zip
Special Thanks:
techiedj
EthanFirst
Dark_Eyes
JC_1
beredan
marcomsousa
Niggo372
dpjohnston
lajuoika
WineSnob
McChen147

OK guys, now that these pups are starting to ship, I need your help!
When you get your new Nexus 9 in the mail, please fire it up and DO NOT accept an OTA that comes out of the box. Please go and get the Android build #, the values of ro.build.date.utc and ro.product.name from build.prop, and the bootloader version (which you'll need to reboot into bootloader mode in order to do). Once you have that info, please post it here so we can get this thread started!
Then, after that, if there's an OTA available out of the box, please get the URL of the ZIP file from adb logcat. Once you do that, feel free to apply said OTA update and enjoy your tablet!
Thanks in advance for your help! If you need any help rebooting into bootloader mode, or grabbing OTA URLs from logcat, let me know.

The review N9 units already got their first ota from LRX16F -> LRX21L.
We need someone to connect wireshark/etherial/fiddler/<your preferred network sniffer> and grab the url for the initial ota when retail devices ship.
While they may not get that specific ota by the time it's generally out, there is very likely going to be an ota for something by then.

nexus 7 and note 3 with wifikill and dsploit so im ready

oldblue910 said:
OK guys, now that these pups are starting to ship, I need your help!
When you get your new Nexus 9 in the mail, please fire it up and DO NOT accept an OTA that comes out of the box. Please go and get the Android build #, the values of ro.build.date.utc and ro.product.name from build.prop, and the bootloader version (which you'll need to reboot into bootloader mode in order to do). Once you have that info, please post it here so we can get this thread started!
Then, after that, if there's an OTA available out of the box, please get the URL of the ZIP file from adb logcat. Once you do that, feel free to apply said OTA update and enjoy your tablet!
Thanks in advance for your help! If you need any help rebooting into bootloader mode, or grabbing OTA URLs from logcat, let me know.
Click to expand...
Click to collapse
Lollipop setup is a little different than past versions.
Step 1 - Choose language
Step 2 - Login to WiFi
Step 3 - "Downloading" updates! No choice in the matter. And it's before logging in to the device for the first time.

#3 has been explained as to why google now does this and i think its a good idea.
Ars technica interview...

cam30era said:
Lollipop setup is a little different than past versions.
Step 1 - Choose language
Step 2 - Login to WiFi
Step 3 - "Downloading" updates! No choice in the matter. And it's before logging in to the device for the first time.
Click to expand...
Click to collapse
Don't Set up Wi-Fi immediately

cam30era said:
Lollipop setup is a little different than past versions.
Step 1 - Choose language
Step 2 - Login to WiFi
Step 3 - "Downloading" updates! No choice in the matter. And it's before logging in to the device for the first time.
Click to expand...
Click to collapse
Just unplug your router from the Internet

Hindsight really is 20/20, isn't it? Of course, when I set mine up at 10:30 this morning I didn't know this would happen.... Better luck to the next guy.?

So once the forced OTA happened, what build number abd bootloader version are you on now?
Sent from my Galaxy Note 4 using Tapatalk

oldblue910 said:
So once the forced OTA happened, what build number abd bootloader version are you on now?
Sent from my Galaxy Note 4 using Tapatalk
Click to expand...
Click to collapse
Turns out my update came already downloaded
cry sorry
Will give the info you need after I unlock it

Code:
bootloader=3.43.0.0114
Ref. https://android.googlesource.com/device/htc/flounder/+/lollipop-release/board-info.txt

EthanFirst said:
Code:
bootloader=3.43.0.0114
Ref. https://android.googlesource.com/device/htc/flounder/+/lollipop-release/board-info.txt
Click to expand...
Click to collapse
Are we sure that's what's actually on the device though?
Sent from my Galaxy Tab S 8.4 using Tapatalk

I'll wait for @USBhost to do verify his bootloader version and build number from his device.
Sent from my Galaxy Tab S 8.4 using Tapatalk

oldblue910 said:
I'll wait for @USBhost to do verify his bootloader version and build number from his device.
Sent from my Galaxy Tab S 8.4 using Tapatalk
Click to expand...
Click to collapse
After update
Build LRX21L
Bootloader
HBOOT-3.43.0.0114
OS-n/a
emmc - boot 2048

USBhost said:
After update
Build LRX21L
Bootloader
HBOOT-3.43.0.0114
OS-n/a
emmc - boot 2048
Click to expand...
Click to collapse
Thank you, sir! If anyone can find a way to get the bootloader and build number of the original shipping firmware prior to the forced OTA, please post that info as well. Until then, I'm going to start the thread at LRX21L. :good:
Sent from my Galaxy Tab S 8.4 using Tapatalk

anyone get the stock recovery.img yet? was thinking about trying to port chainfires autoroot.. but with no recovery.img or boot.img
we get no luck lol

No way for me to get past WiFi without selecting a WiFi spot. Skip is grayed out.

datdirtyscrew said:
No way for me to get past WiFi without selecting a WiFi spot. Skip is grayed out.
Click to expand...
Click to collapse
Unplug the Internet from your wifi router, that way you can connect to wifi workout being in the Internet.
Sent from my Galaxy Note 4 using Tapatalk

#nexus9

Related

[REF] Nexus 6 Stock OTA URLs

This thread compiles all known OTA updates for the Nexus 6.
Nexus 6 (shamu XT1100 and XT1103) - shamu
Current firmware:
International
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Project Fi
Oceania
Verizon
AT&T
Sprint
T-Mobile
U.S. Cellular
6.0 / MRA58N
6.0 / MRA58X
6.0 / MRA58N
6.0 / MRA58R
5.1.1 / LMY48Y
6.0 / MRA58N
6.0 / MRA58X
6.0 / MRA58N
MRA58X from LVY48I - https://android.googleapis.com/pack...ed-shamu-MRA58X-from-LVY48I-new-timestamp.zip (Project Fi Only)
MRA58X from LYZ28N - https://android.googleapis.com/pack...ed-shamu-MRA58X-from-LYZ28N-new-timestamp.zip (T-Mobile Only)
MRA58X from MRA58K - Need link! (T-Mobile and Project Fi Only)
---------------------------------------------------------
LVY48I from LVY48H - Need link! (Project Fi Only)
LMY48X from LMY48T - Need link!
LMY48Y from LMY48W - https://android.googleapis.com/pack...7375b2b4a.signed-shamu-LMY48Y-from-LMY48W.zip (AT&T Only)
LYZ28N from LYZ28M - https://android.googleapis.com/pack...a563f25ab.signed-shamu-LYZ28N-from-LYZ28M.zip (T-Mobile Only)
MRA58N from MRA58K - https://android.googleapis.com/pack...f2896f8dc.signed-shamu-MRA58N-from-MRA58K.zip
MRA58R from LMY48T - https://android.googleapis.com/pack...582096a63.signed-shamu-MRA58R-from-LMY48T.zip (Verizon Only)
---------------------------------------------------------
MRA58K from LVY48H - https://android.googleapis.com/pack...14758cf40.signed-shamu-MRA58K-from-LVY48H.zip
MRA58K from LMY48T - https://android.googleapis.com/pack...926bddfb4.signed-shamu-MRA58K-from-LMY48T.zip
MRA58K from LYZ28M - https://android.googleapis.com/pack...e97e91fcf.signed-shamu-MRA58K-from-LYZ28M.zip
---------------------------------------------------------
LVY48H from LVY48F - https://android.googleapis.com/pack...c124e6877.signed-shamu-LVY48H-from-LVY48F.zip
LYZ28M from LYZ28K - https://android.googleapis.com/pack...4f033c6b8.signed-shamu-LYZ28M-from-LYZ28K.zip
LMY48T from LMY48M - https://android.googleapis.com/pack...397fd39fa.signed-shamu-LMY48T-from-LMY48M.zip
---------------------------------------------------------
LMY48W from LMY48M - https://android.googleapis.com/pack...4b4d34a04.signed-shamu-LMY48W-from-LMY48M.zip (AT&T Only)
LVY48F from LVY48E - https://android.googleapis.com/pack....signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
LYZ28K from LYZ28J - https://android.googleapis.com/pack....signed-shamu-LYZ28K-from-LYZ28J.2888e222.zip
LMY48M from LMY48I - https://android.googleapis.com/pack....signed-shamu-LMY48M-from-LMY48I.4458964f.zip
---------------------------------------------------------
LVY48E from LVY48C - https://android.googleapis.com/pack...amu-ota-LVY48E-from-LVY48C-superblock-fix.zip
LYZ28J from LYZ28E - https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
LMY48I from LMY47Z - https://android.googleapis.com/pack...amu-ota-LMY48I-from-LMY47Z-superblock-fix.zip
---------------------------------------------------------
LVY48C from LVY47H - https://android.googleapis.com/pack....signed-shamu-LVY48C-from-LVY47H.d7374f75.zip (Project Fi only)
LYZ28E from LMY47M - https://android.googleapis.com/pack...Z28E-from-LMY47M-fullradio-fix-superblock.zip (T-Mobile USA only)
LYZ28E from LMY47Z - https://android.googleapis.com/pack...Z28E-from-LMY47Z-fullradio-superblock-fix.zip
---------------------------------------------------------
LMY47Z from LMY47D - https://android.googleapis.com/pack...Y47Z-from-LMY47D-fullradio-fix-superblock.zip
LMY47Z from LMY47E - https://android.googleapis.com/pack...Y47Z-from-LMY47E-fullradio-fix-superblock.zip (Verizon Wireless)
LMY47Z from LMY47I - https://android.googleapis.com/pack...Y47Z-from-LMY47I-fullradio-fix-superblock.zip (Oceania)
---------------------------------------------------------
LMY47M from LRX22C - http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip (T-Mobile USA only)
---------------------------------------------------------
LMY47I from LRX22C - http://android.clients.google.com/p...ed-shamu-ota-LMY47I-from-LRX22C-fullradio.zip (Oceania only)
---------------------------------------------------------
LMY47E from LRX22C - https://android.googleapis.com/pack....signed-shamu-LMY47E-from-LRX22C.3c0d3398.zip (Verizon Wireless only)
---------------------------------------------------------
LMY47D from LRX21O - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX21O-fullradio.zip
LMY47D from LRX22C - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
---------------------------------------------------------
LRX22C from LNX07M - http://android.clients.google.com/p....signed-shamu-LRX22C-from-LNX07M.3d678edb.zip
LRX22C from LRX21M* - http://android.clients.google.com/p....signed-shamu-LRX22C-from-LRX21M.73cc5bf6.zip
LRX22C from LRX21O - http://android.clients.google.com/p....signed-shamu-LRX22C-from-LRX21O.c1fda898.zip
---------------------------------------------------------
LRX21O from LNX07M - http://android.clients.google.com/p....signed-shamu-LRX21O-from-LNX07M.1baf39e7.zip
* LRX21M was not a ROM that appeared on devices sold to the general public, but it did appear on some prerelease devices sent out for review.
Special Thanks:
lawrencegs
EthanFirst
iil
NastyNeil
VivaErBetis
xdatastic
Xoo00o0o0o
imex99
JetBlk
DA6030
Schoat333
Onlyunless
BiggieStuff
Scottatron
jj14
anonchalantsigh
alryder
bloodiedwraith
fallen101
theTyGuy
BrianUsher
jrparker99
depassp
renny083
Did anyone manage to pick up a Nexus 6 from Sprint yesterday? If so, did it force you to do an OTA out of the box? What's the build, baseband, and bootloader version you're on now? I pre-ordered one from AT&T but it won't be here until later in the week.
Sent from my iPhone 6 Plus using Tapatalk
oldblue910 said:
Did anyone manage to pick up a Nexus 6 from Sprint yesterday? If so, did it force you to do an OTA out of the box? What's the build, baseband, and bootloader version you're on now? I pre-ordered one from AT&T but it won't be here until later in the week.
Sent from my iPhone 6 Plus using Tapatalk
Click to expand...
Click to collapse
Unfortunately no Sprint Stores were carrying the N6 in stock demo or otherwise. Just online orders.
Dr Faustus said:
Unfortunately no Sprint Stores were carrying the N6 in stock demo or otherwise. Just online orders.
Click to expand...
Click to collapse
Ah. Wasn't aware of that. Thanks for the info!
Sent from my iPhone 6 Plus using Tapatalk
Has anyone got their Nexus 6 yet? If so, did it make you do an OTA update out of the box? After that update, what is the firmware, bootloader, and baseband version for the updated firmware?
oldblue910 said:
Has anyone got their Nexus 6 yet? If so, did it make you do an OTA update out of the box? After that update, what is the firmware, bootloader, and baseband version for the updated firmware?
Click to expand...
Click to collapse
I'll be able to tell you tomorrow at around 11AM EST
XxKINGxX2580 said:
I'll be able to tell you tomorrow at around 11AM EST
Click to expand...
Click to collapse
AT&T should be shipping mine either today or tomorrow as well. Can't wait.
oldblue910 said:
AT&T should be shipping mine either today or tomorrow as well. Can't wait.
Click to expand...
Click to collapse
I can't wait for shipping. I get impatient. I'll just go to my local T-Mobile store 5 minutes before they open.
oldblue910 said:
Has anyone got their Nexus 6 yet? If so, did it make you do an OTA update out of the box? After that update, what is the firmware, bootloader, and baseband version for the updated firmware?
Click to expand...
Click to collapse
Yes, I got mine from Motorola yesterday. There was an OTA when I got it; it did not force me, but I upgraded anyway. Here's what my phone says now:
From bootloader:
BL: moto-apq8084-71.05 (sha-0d4c769, 2014-10-21 12:04:24)
Baseband: D4.0-9625-02.55.03a
From about phone:
Baseband Version: MDM9625_104335.118.02.55.03R
Kernel version: 3.10.40-g72dfced [email protected] #1 Wed Oct 29 15:06:28 UTC 2014
Build number: LRX210
If there more info you need, I'll need instructions for fetching it.
Thank you for that!
Now that I know the out-of-the-box OTA isn't forced, here's what I need someone to do:
BEFORE BOOTING YOUR NEXUS 6 UP FOR THE FIRST TIME:
1. Boot into bootloader mode. This is done by either holding power and volume down, or power and volume up, at the same time. I'm not sure which. Please get the bootloader version from the screen.
2. Reboot your system normally.
3. Go through the setup process
4. Go to Settings | About Phone and give us the Android version, build number and baseband version.
5. Install a file manager from the Play Store, and then go into that app and open /system/build.prop. Please post the values of ro.build.date.utc and ro.build.fingerprint.
6. Enable developer options on your phone by going back to Settings | About Phone and repeatedly tapping on the build number until it says "you're a developer."
7. Go into Settings | Developer Options and enable USB debugging.
8. Check for a system update. Once it downloads, DO NOT INSTALL IT YET.
9. Go to Settings | Developer Options and choose "Take Bug Report".
9. After a few minutes, you'll get a text file emailed to your gmail account.
10. Open that text file and search it for ".zip" (without the quotes).
11. Please post the entire URL here. It'll start with "http://android.clients.google.com/packages/ota/."
At that point, install the update, enjoy your phone, and accept my eternal gratitude!
oldblue910 said:
4. Go to Settings | About Phone and give us the Android version, build number and baseband version.
Click to expand...
Click to collapse
Unfortunately, I can't do most of that anymore, but I did have the foresight to write down the build number from before I updated: LNX07M
Hope that's helpful, even if just for verification.
signals said:
Unfortunately, I can't do most of that anymore, but I did have the foresight to write down the build number from before I updated: LNX07M
Hope that's helpful, even if just for verification.
Click to expand...
Click to collapse
Thanks for that. Can anyone full in the rest of the needed information when they get their Nexus 6?
Sent from my Galaxy Note 4 using Tapatalk
If anyone is willing to wait for a custom recovery to come out and dump the initial rom, here are the steps to do so: [REQ]Dump of the preinstalled rom
oldblue910 said:
Now that I know the out-of-the-box OTA isn't forced, here's what I need someone to do:
BEFORE BOOTING YOUR NEXUS 6 UP FOR THE FIRST TIME:
1. Boot into bootloader mode. This is done by either holding power and volume down, or power and volume up, at the same time. I'm not sure which. Please get the bootloader version from the screen.
2. Reboot your system normally.
3. Go through the setup process
4. Go to Settings | About Phone and give us the Android version, build number and baseband version.
5. Install a file manager from the Play Store, and then go into that app and open /system/build.prop. Please post the values of ro.build.date.utc and ro.build.fingerprint.
6. Enable developer options on your phone by going back to Settings | About Phone and repeatedly tapping on the build number until it says "you're a developer."
7. Go into Settings | Developer Options and enable USB debugging.
8. Check for a system update. Once it downloads, DO NOT INSTALL IT YET.
9. Go to Settings | Developer Options and choose "Take Bug Report".
9. After a few minutes, you'll get a text file emailed to your gmail account.
10. Open that text file and search it for ".zip" (without the quotes).
11. Please post the entire URL here. It'll start with "http://android.clients.google.com/packages/ota/."
At that point, install the update, enjoy your phone, and accept my eternal gratitude!
Click to expand...
Click to collapse
Just wanted to quote myself here and remind everyone that when you get your Nexus 6, I need someone to perform these steps before applying that first update that will be available. If anyone could do this for me, I'd greatly appreciate it.
oldblue910 said:
Just wanted to quote myself here and remind everyone that when you get your Nexus 6, I need someone to perform these steps before applying that first update that will be available. If anyone could do this for me, I'd greatly appreciate it.
Click to expand...
Click to collapse
If my local T-Mobile's (there's twenty of them) were selling it, I'd help. But nope, they're saying order online
TheJesus said:
If my local T-Mobile's (there's twenty of them) were selling it, I'd help. But nope, they're saying order online
Click to expand...
Click to collapse
Mine just shipped from AT&T today, so I'll have it Friday. I'm just hoping someone who gets theirs before me will do get all the info so I don't have to wait 'til Friday. If not, no big deal.
oldblue910 said:
Mine just shipped from AT&T today, so I'll have it Friday. I'm just hoping someone who gets theirs before me will do get all the info so I don't have to wait 'til Friday. If not, no big deal.
Click to expand...
Click to collapse
I would do this for you, but.......
I'm like a week or more away from receiving mine. Its kinda cool that you live in Durham though, I live in Fayetteville.
Just got mine an hour ago.
XxKINGxX2580 said:
Just got mine an hour ago.
Click to expand...
Click to collapse
Any chance you can get the info from the pre-installed ROM that I asked for above, or did you already update it?
amberkalvin said:
I would do this for you, but.......
I'm like a week or more away from receiving mine. Its kinda cool that you live in Durham though, I live in Fayetteville.
Click to expand...
Click to collapse
Nice! Next time you're up this way or next time I'm down that way, perhaps beers are in order.

New Nexus 4 user: OTA/updates questions

Hello Nexus 4 users,
I recently switched over to the Nexus 4, which belonged to my wife previously, and want to update all the latest OTAs before I start flashing.
The nexus 4 was successfully rooted with Wug's Nexus Root Toolkit awhile back, perhaps a year ago.
I want to know how to determine which OTA I currently have on the phone. Then ,if I am not on the newest update, how do you go about? Is LMY47V or LMY48I the newest? How do you find out what update the phone is on?
Also, please tell me your tips and the simplest way to install the update. I'm not very good with scripts and commands but an excellent flasher :laugh:
Thank you in advance
Settings -> About Phone -> Build Number
Android versions: https: // developers . google . com /android/nexus/images?hl=en (but these are not OTA versions, to get those search for OTA download <build number> -- usually android police or another site will have a link to the OTA image).
Not sure about LMY47V or LMY48I. =( Educated guess that the last one in the list fixes stagefright so that's why it's still 5.1.1.
----
p.s. These sites need whitelisting of URLs... (for new accounts -- it's kind of stupid to restrict it if it's not a SPAM bot).
Just to add, OTA updates will fail since you've rooted your phone! You must be completely stock for OTAs to work.
So will all the updates be integrated in to the ROM I flash? Thus unnecessary to update OTA?
First, 48I is the newest and does patch stagefright. OTAs will not work on a rooted phone or one with any system files changed. If your bootloader is unlocked the easiest way to upgrade is to flash the system and boot images from 48i with fastboot. If you don't know how to do that start here,http://forum.xda-developers.com/showthread.php?p=34552123

6.0 Rolling Out For Canadian [Wind] XT1527!

Just got the notification now. Anybody interested? If so, a quick link, or a step by step on what's needed to pull this in for distro to all!?!? I have not dl'd yet, as I'm sure that's the first section to start with! :fingers-crossed:
I insteresa this update but unfortunately I have no knowledge to make a master eso.Espero help us forgiveness for my English so bad
I would like to try but my computer its broken
DSchwarz47 said:
I would like to try but my computer its broken
Click to expand...
Click to collapse
You would like to try what? What I was stating was my Moto E has an update available to 6.0 MM. I have not downloaded it as of yet, cause I am aware there's something you need to do first in order to capture the download for redistribution. From what I understand you cannot use an already downloaded and installed OEM~OTA update for redistribution...
A little guidance from the seniors would be EXTREMELY appreciated, as this is my first thread ever... I'm looking at you squid2 lolz
i am waiting for the 7th when Telus said they would roll it out.
Not sure how they make the uploaded Firmware archives either..
No matter how many time i asked i either got ignored or hammered with some weird advice (English issue?)
And i meant the one that we all use uploaded to Mega etc.
Who is making them and with what?
Apparently no one knows and what concerns me even more is a little thing called security.
I asked so uhhh why are we not using hashes to verify the firmware ?
It's complete insanity to check hashes on some dumb app and not your OS ..that just blows me away LOL
I'm interested in putting this on my Sprint phone (XT1526). CM13 won't detect my Canadian SIM.
24.51.39.en.CA
That's the fsent. Will upload in a few hrs.
Does anyone know if I'll be able /aloud to post a AFH link here on this thread I started?
Marshmallow v6.0 24.65.39 Telus XT1527 downloading now..
someone already ripped it into a standard package.
So OP you are in luck someone did the work for you :good:
I am downloading this one but there is one for Rogers too..
XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
http://www.filefactory.com/file/10v...0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
Source + Rogers version etc:
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
lenigma1too said:
24.51.39.en.CA
That's the fsent. Will upload in a few hrs.
Does anyone know if I'll be able /aloud to post a AFH link here on this thread I started?
Click to expand...
Click to collapse
You were right
BUILD REQUEST INFO:
SW Version: surnia_retca-user 6.0 MPI24.65-39 25 release-keysM8916_2020629.41.03.21.51R
MBM Version: 80.20
Modem Version: M8916_2020629.41.03.21.51R
FSG Version: FSG-8916-02.61
Build Fingerprint: motorola/surnia_retca/surnia_umts:6.0/MPI24.65-39/25:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.51.39.surnia_retca.retca.en.CA
Model number: Moto E
Android Version: 6.0
Baseband Version: M8916_2020629.41.03.21.51R
Build Number: MPI24.65-39
Build Date: Thu Jan 28 14:25:13 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_telus_v1.1.nvm
Blur Version: Blur_Version.24.51.39.surnia_retca.retca.en.CA
Version when read from CPV: surnia_retca-user 6.0 MPI24.65-39 25 release-keys
I tried installing the Rogers firmware but stuck on boot animation. Help?
EDIT: I think I fixed it. Installed squid kernel r16.
xpmule said:
You were right
BUILD REQUEST INFO:
SW Version: surnia_retca-user 6.0 MPI24.65-39 25 release-keysM8916_2020629.41.03.21.51R
MBM Version: 80.20
Modem Version: M8916_2020629.41.03.21.51R
FSG Version: FSG-8916-02.61
Build Fingerprint: motorola/surnia_retca/surnia_umts:6.0/MPI24.65-39/25:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.51.39.surnia_retca.retca.en.CA
Model number: Moto E
Android Version: 6.0
Baseband Version: M8916_2020629.41.03.21.51R
Build Number: MPI24.65-39
Build Date: Thu Jan 28 14:25:13 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_telus_v1.1.nvm
Blur Version: Blur_Version.24.51.39.surnia_retca.retca.en.CA
Version when read from CPV: surnia_retca-user 6.0 MPI24.65-39 25 release-keys
Click to expand...
Click to collapse
Could you please lend a fellow Ontarian brother a hand, and tell me where the OTA file actually is? I've had the damn thing for a week now, and I can't seem to find it anywhere to capture it! I would love to actually install this OTA...
I do appreciate your help in finding somebody who had done the work already. However the OTA that I have waiting on this phone is a slightly different one. the numbers are different 24.51.39.... my educated guess is going to be it is slightly smaller because it contains no Rogers or Telus bloatware. Wind Mobile does not have a single app installed on this phone right outta the box, So I would like to capture it before I send it off to be installed.
I have read many of your posts across multiple threads, and you are obviously quite knowledgeable -> especially in the coding Department!
Are you sure it's going to install?
Once you Root it or various other custom changes the updates will not install.
It checks if you were tampering with the phone and will deny the update.. even if you can download it.
Thanks for the kind words but i am not sure off hand unless i search around.
One thing you try doing is search online etc with the words Blur, Update, Zip, Location
Or if you have a file manager with root you can search for it.
The benefit of the full packages available is they just install on any phone with no checks.
It's also not an update but the full installer.
So i think it's possible you may download an update with patches.
So it will see what you had before and patch those files.
Which could make saving & using the update again later problematic
..especially if you root !
If you upload it publicly we can check and see if it's a full install or a patch by looking at updater-script probably.
If i were you i would keep tabs on the Firmware repositories to see if the Wind package gets uploaded.
Then you will have a full install you can use coming from most others and with the security checks removed.
If you have something that can search your system files installed you can try searching for something that
will probably have Blur in the file name and be a flashable zip file.
If you have TWRP installed i think you can just load that and look around with the Built-In File Manager.
I am eating lunch so i might look on the web soon and check back here.. good luck.
Sorry i have not done it before so maybe someone who has can speak up or you can find one of their topics here.
The OTA update file is in the device main memory in data/data/com.motorola.ccc.ota/app_download
Thanks hedimahf i will save that for future reference.
Also lenigma1too i am pretty sure if you rooted your phone then you can not install that update.
Those type of updates are risky for us that customize our phones.. be careful.. make plans to fix it ahead of time
Unless my phone was stock (not rooted) with the default recovery and an original factory locked bootloader
i myself would not even attempt to install the update.
Google it and see the many people talking about BootLoop problems
I bet there is also little difference between Wind, Rogers or Telus aside from a couple small APK's and the Modem data stuff.
If all three have the same radio band support then i wouldn't worry too much about which one to use.
Although you may end up struggling to get your phone calls and text's etc working again if you switch like that.
The Telus one i tried just had 1 extra APK the "My Telus" app and a shortcut to it on the phone.. i uninstalled it with ease.
Other than that i did not see ANY other app's installed that were not standard on the USA/EU retail versions etc
EDIT:
Oh and the BootLogo was like on Lollipop but slightly more blue.
And the Boot animation was new too.. Marshmallow Telus has "Stitches World" video.
The default wallpapers and the collection of them were like on Lollipop too.
EDIT:
My point was the Telus firmware only had "branding" with that one app.
Otherwise the word Telus does not show up anywhere really.
Also i tend to compare packages so i am keeping my eye out so i can see what is different.
If you want i can PM you if i run across Wind version.
Can this be insstalled on a stock 5.1 xt1528? if so how? thanks
abispac said:
Can this be insstalled on a stock 5.1 xt1528? if so how? thanks
Click to expand...
Click to collapse
I don't think you understood what this topic was about.
He was asking how to capture an OTA update.
Didi you read what was said?
The needed flashing method?
xpmule said:
Marshmallow v6.0 24.65.39 Telus XT1527 downloading now..
someone already ripped it into a standard package.
So OP you are in luck someone did the work for you :good:
I am downloading this one but there is one for Rogers too..
XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
/file/10vpb6d09x43/XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
Source + Rogers version etc:
/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
Can those compiled zip files in filefactory website be installed using TWRP recovery or are they created to be installed using desktop ADB software only?
Click to expand...
Click to collapse
hedimahf said:
xpmule said:
Marshmallow v6.0 24.65.39 Telus XT1527 downloading now..
someone already ripped it into a standard package.
So OP you are in luck someone did the work for you :good:
I am downloading this one but there is one for Rogers too..
XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
/file/10vpb6d09x43/XT1527_SURNIA_RETCA-TELUS_6.0_MPI24.65-39_cid14_subsidy-TELUS_CFC.xml.zip
Source + Rogers version etc:
/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
Can those compiled zip files in filefactory website be installed using TWRP recovery or are they created to be installed using desktop ADB software only?
Click to expand...
Click to collapse
They are intended to used with RSDLite or ADB.
They are found on the big Firmware topic(s) here. (first post over there for links)
You should check out the discussion going on for help with that on those topics for best information.
Putting Firmware from on model onto another may break your ability to make phone calls
and then you would have to try and fix it somehow and it starts to get complicated.
Which is why those other topics are so valuable.. good luck.
I repeat the 2 zip's mentioned are NOT flashable-zip's. (they are just a normal zip file for storage)
Click to expand...
Click to collapse
A new OTA rolled out for many users.
I found it in root /cache
I am working on restoring my phone to stock and applying it.
I don't see anyone making a non-sign firmware package so..
EDIT:
I got it installed now.. it says Patch Level DEC 1st 2016 (instead of February)
System version version 24.71.4
I guess i have to re-apply a ton of changes now

Help identify ASUS grouper tablet & full OTA

This tablet has these markings, but, no proper model number:
Product name -grouper
Variant -grouper
HW Version =ERS
Bootloader 4.2.3
Baseband n\a
serial 015d4..........................2613
ACEPLUS 2012-11-18D
CSZY 18
Is it model ME370T ?
It was locked, but unable to do proper factory reset.
fastboot OEM unlocked sucessfully.
But unable flash with fastboot ADB, because have not found the proper ROM
Can anyone point me to the proper full OTA download please ?
It is ot included in the Google's list.
Paul
As far as I am aware there are only 2 models for the Nexus 7 (2012) a Wi-Fi and 3G version. Yours says grouper so that's the Wi-Fi version.
ME370T is as well the model name but rarely used.
https://forum.xda-developers.com/wiki/ASUS_Nexus_7/ME370T
https://developers.google.com/android/images#nakasi - for the official images from google. It's official code name is nakasi.
https://forum.xda-developers.com/nexus-7 - support forum on xda (NOTE DON'T PICK THE 3G DEVELOPMENT FORUMS FOR ROMS)
You might try the Nexus Root Toolkit for unlocking the bootloader and follow step by step assistance to flash rom, etc...
RDDraco said:
As far as I am aware there are only 2 models for the Nexus 7 (2012) a Wi-Fi and 3G version. Yours says grouper so that's the Wi-Fi version.
ME370T is as well the model name but rarely used.
https://forum.xda-developers.com/wiki/ASUS_Nexus_7/ME370T
https://developers.google.com/android/images#nakasi - for the official images from google. It's official code name is nakasi.
https://forum.xda-developers.com/nexus-7 - support forum on xda (NOTE DON'T PICK THE 3G DEVELOPMENT FORUMS FOR ROMS)
You might try the Nexus Root Toolkit for unlocking the bootloader and follow step by step assistance to flash rom, etc...
Click to expand...
Click to collapse
Thanks for reply
I did use the Nexus Root Toolkit, but couldnt find the 4.2.3 version. They suggested that I had Nakasi-Grouper 4.2.2 JDQ39B
Rooting was successful, but, on one attempt, the camera was present in settings > apps, but could not make welcome screen short cut, so was unusable. On another attempt, the camera disappeared from the list of apps. Otherwise, the tablet is working fine.
any suggestions please
pawlud said:
Thanks for reply
I did use the Nexus Root Toolkit, but couldnt find the 4.2.3 version. They suggested that I had Nakasi-Grouper 4.2.2 JDQ39B
Rooting was successful, but, on one attempt, the camera was present in settings > apps, but could not make welcome screen short cut, so was unusable. On another attempt, the camera disappeared from the list of apps. Otherwise, the tablet is working fine.
any suggestions please
Click to expand...
Click to collapse
Wasn't certain myself so did some searching and apperently the only way to access the Camera is using it as function for skype/instagram/snapchat etc... You need to install an app for the play store if you want to access it otherwise.

Help finding recent update file to manual update ZTE Axon 7 Mini (ZTE_B2017G)

I have recently bought a gold-coloured ZTE Axon 7 Mini through Amazon. It is a brand new and factory unlocked device. It is currently running Android 6.0.1 with 1st November 2016 security patch. The OTA update doesn't work, gives a network unavailable error all the time. I am planning to manual update it. But I don't know where to find the right update file and what version is the compatible one for the device I own. Please, any help is appreciated regarding this. Direct to me official link where I can download the right file for the device. If any of you can give me the exact file name and link, it would be really helpful. Thanks in advance. Please do find the device details below and feel free to ask if you need any other specific details about the device. Also is there a difference between gold model and grey model? They have separate SKU numbers: SKU: A7S121 (Gray) / A7S122 (Gold). And when I go to the grey product page (https://www.zteusa.com/axon-7mini/), I find a nougat update zip download link under support tab, but on the gold product page (https://www.zteusa.com/zte-axon-7-mini-gold#) I don't find any update zip file under the support tab. Does that mean only grey model has update zip and that file is not meant for gold model?!?
My device details:
1) Model: ZTE Axon 7 Mini
2) Model Number: ZTE B2017G
3) Android Version: 6.0.1
4) Android Security Patch Level: November 1, 2016
5) Baseband Version: TA.2.1c1-00101-8976_GEN_PACK
6) Kernel Version: 3.10.84
7) Build Number: ZTE B2017G_USAV1.0.0B16
8) Build Time: Tue Nov 8 17:05:24 CST 2016
9) MiFavor UI Version: 4.0
Well, I didn't have the patience to wait until I get a reply from one of you guys. So this is what I did.
I went to this link: https://www.zteusa.com/axon-7mini/
Downloaded the update file from the support section: Axon 7 Mini SD Card Package Update (B12 - Android N)
Unzipped and had a look at build prop file to check if this is the software zip that is compatible with my device. Even though I couldn't completely confirm it, I didn't find any information that said, it isn't. So far so good.
Renamed the file as update.zip and dropped the file into the root directory of the memory card.
In settings, navigated to update section, found the update zip file install option, clicked install and followed instructions. Device rebooted, updated and rebooted, all within five minutes.
Shut down the device, reboot recovery and reset the device and booted again.
On registering the device and completing the login process, proceeded to About section in settings and confirmed that the update was successful and complete. It indeed is!
System Details (After Update):
1) Model: ZTE Axon 7 Mini
2) Model Number: ZTE B2017G
3) Android Version: 7.1.1
4) Android Security Patch Level: June 1, 2017
5) Baseband Version: TA.2.1.c1-00101-8976_GEN_PACK
6) Kernel Version: 3.10.84
7) Build Number: ZTE B2017G_USAV1.2.0B12
8) Build Time: Mon Jun 5 22:56:10 CST 2017
9) MiFavor UI Version: 4.2
So if someone has a similar device and want to update, you can go ahead and follow this method. It works.
Please note that this update will erase data. So make a backup before updating.
Rider: Can anyone explain if there is any difference between gold and grey models? The SKU is different. Also, I have found the price of grey significantly higher than the gold version across various stores of various countries. There could be something!
prmbasheer said:
Well, I didn't have the patience to wait until I get a reply from one of you guys. So this is what I did.
I went to this link: https://www.zteusa.com/axon-7mini/
Downloaded the update file from the support section: Axon 7 Mini SD Card Package Update (B12 - Android N)
Unzipped and had a look at build prop file to check if this is the software zip that is compatible with my device. Even though I couldn't completely confirm it, I didn't find any information that said, it isn't. So far so good.
Renamed the file as update.zip and dropped the file into the root directory of the memory card.
In settings, navigated to update section, found the update zip file install option, clicked install and followed instructions. Device rebooted, updated and rebooted, all within five minutes.
Shut down the device, reboot recovery and reset the device and booted again.
On registering the device and completing the login process, proceeded to About section in settings and confirmed that the update was successful and complete. It indeed is!
System Details (After Update):
1) Model: ZTE Axon 7 Mini
2) Model Number: ZTE B2017G
3) Android Version: 7.1.1
4) Android Security Patch Level: June 1, 2017
5) Baseband Version: TA.2.1.c1-00101-8976_GEN_PACK
6) Kernel Version: 3.10.84
7) Build Number: ZTE B2017G_USAV1.2.0B12
8) Build Time: Mon Jun 5 22:56:10 CST 2017
9) MiFavor UI Version: 4.2
So if someone has a similar device and want to update, you can go ahead and follow this method. It works.
Please note that this update will erase data. So make a backup before updating.
Rider: Can anyone explain if there is any difference between gold and grey models? The SKU is different. Also, I have found the price of grey significantly higher than the gold version across various stores of various countries. There could be something!
Click to expand...
Click to collapse
That update is fine for your phone, but you are missing the security patch from September 1, 2017 which would bring the build up to B14. It was an OTA update but I don't know if it's available anywhere since the OTA updates haven't been working.
My understanding is that there is no difference between the gold and the grey except for the color. I think the difference in the price reflects the fact that the grey has more demand and/or less supply.
qzjxk said:
That update is fine for your phone, but ......
Thank you, for the reply.
Yes, you are absolutely right. The update I have installed is not the latest. But the latest available update from their site (https://www.zteusa.com/axon-7mini/) for this device is only the one with 1 June 2017 security patch. I was aware of this when I downloaded and updated. I couldn't find the latest update file anywhere on the internet. This page (https://community.zteusa.com/discussion/51249/software-update-axon-7-mini-b2017g-now-on-b14) has information about the B14 update but I see no mention of downloadable file in the forum. Probably that is only an OTA update and they have not made the file available to the public. But the problem with OTA update is that the ZTE servers seem to be completely broken and no OTA updates can be carried out currently. So, for the time being, I am stuck with B12 version. I will keep searching for a way to get B14. If any of you guys know a way, please do share with me. However, I am happy that at least I was able to get my device run Android 7.1.1 with 1 June 2017 security patch.
Info on Android 7.1.1 Update: I haven't noticed any cosmetic changes in the device after the update except some changes in the settings structure. I am not aware of any performance improvements too since I updated only yesterday and yet to install applications and use it regularly. But I am not so much worried about performance since this is my secondary device and will be only light using it. However, I would love to see a good battery performance so that my charging cycle for the secondary device is not as active as my primary device.
Rider: Is anyone aware of a 1) successful root, 2) TWRP, 3) Good & stable custom ROMs for this device running Android 7.1.1?
Click to expand...
Click to collapse
After little more searching, I came across this thread:
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
This thread has the B14 version of Android 7.1.1 but it is in three files (Boot stack, System and boot, Recovery), not as a single file. Plus it requires TWRP for installation. I am yet to deep dive and figure out how to do this. Maybe I will try it out tonight. Any suggestions welcome.
prmbasheer said:
After little more searching, I came across this thread:
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
This thread has the B14 version of Android 7.1.1 but it is in three files (Boot stack, System and boot, Recovery), not as a single file. Plus it requires TWRP for installation. I am yet to deep dive and figure out how to do this. Maybe I will try it out tonight. Any suggestions welcome.
Click to expand...
Click to collapse
I suggest reading that entire thread before attempting installation, as I see other people have had problems. There are other threads in the Axon 7 mini section for TWRP and custom ROMs. With those I also suggest reading the entire thread before flashing.
qzjxk said:
I suggest reading that entire thread before attempting ...
Yes, absolutely. I am not in a rush to do it. The update to Android 7.1.1 was good enough for me. I can live without the 1 September/November 2017 security patch. Probably the ZTE servers might wake up once ZTE sets right the issues it has with USA authorities currently. So fir the time being I am going to pass this incremental update and wait and see if it happens through OTA.
That apart, I am afraid I am noticing sound quality deterioration after updating from Android 6.0.1 to Android 7.1.1. The speakers sound less loud now. More than the speakers, I notice significant degrade in quality and volume of sound through 3.5mm jack. The set of songs I listened to before upgrade sounded louder, better and more punchier. Is it for real or is it just me?
Click to expand...
Click to collapse
Hello, I am trying to find recent update file for Axon 7 mini EU version. I am using B09 build from here: https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933 now, because OTA updates are disabled. Does anyone have update.zip B12 or higher version? Thanks in advance for help.
prmbasheer said:
qzjxk said:
I suggest reading that entire thread before attempting ...
Yes, absolutely. I am not in a rush to do it. The update to Android 7.1.1 was good enough for me. I can live without the 1 September/November 2017 security patch. Probably the ZTE servers might wake up once ZTE sets right the issues it has with USA authorities currently. So fir the time being I am going to pass this incremental update and wait and see if it happens through OTA.
That apart, I am afraid I am noticing sound quality deterioration after updating from Android 6.0.1 to Android 7.1.1. The speakers sound less loud now. More than the speakers, I notice significant degrade in quality and volume of sound through 3.5mm jack. The set of songs I listened to before upgrade sounded louder, better and more punchier. Is it for real or is it just me?
Click to expand...
Click to collapse
Hey, I have the official file that updates the Axon 7 Mini to the latest security patch. You have to rename the file to update.zip and then install via Recovery. For some reason it won't detect the update via Settings > Update.
At first I thought I had the wrong file but it turns out that in order to patch via Recovery you have to first enable Developer Settings, then enable USB debugging and Enable OEM Unlock. Once you've completed these steps make sure you have the update.zip on an SD card.
The option Enable OEM Unlock does NOT unlock the bootloader. It just allows for the update to apply.
Boot into recovery by turning off the phone then turning on with POWER and VOLUME UP. Then apply update via SD CARD. It does take at least 10 minutes so DO NOT think it got stuck and reboot the phone during the update. It does NOT wipe the device so all settings and files remain.
The original filename is B2017G-US-v1.2.0-b14-ota-from-b12.zip
Here is a link to the file: https://1drv.ms/u/s!AseCxOaqPUb6hVW5SADVg7nEM6vT
Good luck!
Click to expand...
Click to collapse
unlocked01 said:
prmbasheer said:
Hey, I have the official file that updates the Axon 7 Mini to the latest security patch. You have to rename the file to update.zip and then install via Recovery. For some reason it won't detect the update via Settings > Update.
Here is a link to the file: https://1drv.ms/u/s!AseCxOaqPUb6hVW5SADVg7nEM6vT
Good luck!
Click to expand...
Click to collapse
Thanks so much for this. May I know where you sourced this file from? Just wanted to make sure this is 100% compatible with my device.
Click to expand...
Click to collapse
prmbasheer said:
unlocked01 said:
Thanks so much for this. May I know where you sourced this file from? Just wanted to make sure this is 100% compatible with my device.
Click to expand...
Click to collapse
I can't seem to locate the site I got it from. Ask I know is I knew ZTE servers were shut down and I did hours of research to find the files before buying this phone for my aunt. As long as you have the US version of the Axon 7 Mini it will work with my instructions. Non official files or incompatible files will just fail instead of updating.
Click to expand...
Click to collapse
unlocked01 said:
prmbasheer said:
I can't seem to locate the site I got it from. Ask I know is I knew ZTE servers were shut down and I did hours of research to find the files before buying this phone for my aunt. As long as you have the US version of the Axon 7 Mini it will work with my instructions. Non official files or incompatible files will just fail instead of updating.
Click to expand...
Click to collapse
I took your advice, followed your instructions and updated the device with the update zip provided by you. Updated without any errors. It is the right package as you said. Took 15 minutes. Thanks so much.
Click to expand...
Click to collapse
I have the same model that you have, all the same except for the fact that it's not the usa model, but it's from europe, and i am stuck with android 6.0.1, should i try to update anyway?, And after the latest update you have done by the link that this guy gave you after you said the sound been bad, it got better or still bad? Thanks for the help.
Bhmg00 said:
I have the same model that you have, all the same except for the fact that it's not the usa model, but it's from europe, and i am stuck with android 6.0.1, should i try to update anyway?, And after the latest update you have done by the link that this guy gave you after you said the sound been bad, it got better or still bad? Thanks for the help.
Click to expand...
Click to collapse
Using the US version of the software could be dangerous. The US phones have different product numbers (this is not the model number) so the update may refuse to install even. Since ZTE's download sites are down and finding the software anywhere else is very frustrating your best bet would be to flash TWRP and use the stock EU files from here https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538. The stock recovery link does not work but who needs stock recovery anyway? Plus you can backup the stock recovery with EDL tool before you flash TWRP.
So even if I had the exact same model, would I not be able to use the files provided in this thread as there might be some other differences for EU models? How can I distinguish between EU and US models if they have the exact same model :/
PumpAction said:
So even if I had the exact same model, would I not be able to use the files provided in this thread as there might be some other differences for EU models? How can I distinguish between EU and US models if they have the exact same model :/
Click to expand...
Click to collapse
Mine is a USA factory unlocked model and the SKU is A7S122. Model is ZTE B2017G and build number during purchase is ZTE B2017G_USAV1.0.0B16. You could use a combination of this information to distinguish models of different regions. The zip files you find in this thread are for USA models. Even if you try to update, the update won't go through. It will show error.
Bhmg00 said:
I have the same model that you have, all the same except for the fact that it's not the usa model, but it's from europe, and i am stuck with android 6.0.1, should i try to update anyway?, And after the latest update you have done by the link that this guy gave you after you said the sound been bad, it got better or still bad? Thanks for the help.
Click to expand...
Click to collapse
After all the updates, I did a factory reset and started fresh. It works flawlessly. The battery is bad, used to be bad in the previous build too. The sound from the stereo speakers and the headphone jack are all good. No drop in quality as I first thought.
Just an update in case you haven't checked in a while: The OTA servers ought to be back up and running now, so automatic updates will probably start going through again.

Categories

Resources