Related
Hi everyone,
I have just purchased a Vodafone-branded Magic/Sapphire. Android prompts me to install an 4.2 MB large update called "Android Update 1.5" with this message:
Please install this update from Google. It contains a security fix.
Now, what really confuses me is that Android 1.5 is already installed - at least according to the settings menu, where this information is shown:
Model number: HTC Magic
Firmware version: 1.5
Kernel version: 2.6.27-00392-g8312baf [email protected] #72
Build number: CRB17
Accordingly, I have three questions:
The phone says that the update as already been downloaded (most likely in the background), but not yet installed. Is it possible, using a terminal program/shell-prompt, to browse the phone's filesystem and check the filename of the update before you install it on an un-rooted phone? If so, where do I look for the update package?
Why does the phone want to install an Android 1.5-update? According to the phone Android 1.5 is already installed?
Can someone please tell me what the 4.2 MB update does? I have been googling for Android OTA Update "4.2 MB", but it seems that nothing is known about this update anywhere (there are, however, other updates within the 4 MB-range but none of them are precisely 4.2 MB in size).
I'd very much appreciate any help to sort this out (moderators, I hope I havn't created this thread in the wrong subforum; if I have, I apologize).
1. Run ddms/logcat to see the URL of the update.
2. 1.5 is the OS version.
3. It's most probably a security patch (of 1.5).
Its CRC1 and already "leaked"
Amon_RA said:
1. Run ddms/logcat to see the URL of the update.
Click to expand...
Click to collapse
Thank you. I'll do it as soon as the phone is fully charged again (as the manual says the battery will perform at its best after completing a few full charge/recharge cycles, I don't want to disturb it - pseudo-science, I know ).
Is the ddms/logcat stored locally on the Magic/Sapphire by default, or is it just part of the SDK-package?
maxisma said:
Its CRC1 and already "leaked"
Click to expand...
Click to collapse
Woah, one step at a time mister . I'm a total Android-newbie (although trying to catch up browsing various forums).
What is "CRC1"?
Will installing this patch prevent me to root the phone at some later stage?
Is there a proper changelog available somewhere?
Focusyn said:
Woah, one step at a time mister . I'm a total Android-newbie (although trying to catch up browsing various forums).
What is "CRC1"?
Will installing this patch prevent me to root the phone at some later stage?
Is there a proper changelog available somewhere?
Click to expand...
Click to collapse
It's security updates. I'd recommend getting the update from here (xda) rather than attempting to install it from the carrier.
Looks like that some of the Nexus S got the wrong software that makes them at the moment not capable to get the 2.3.1 update neither manual nor as OTA. If you find under phone information "userdebug" you won't be able to update yet. It looks like Google just found out about this problem a couple of days ago. I got my phone today and this is not a good start with the Nexus S experience:-( I will wait a few days and otherwise this phone goes back to BestBuy.
Below is comment from Nick Kralevich who works for the Android security team:
"userdebug" versions of Android are intended for engineering use only. It contains additional debugging compared to "user" builds. The hardware is exactly the same. You'll never get an update for a userdebug version of Android, which is naturally bad.
You can find out if you have a userdebug build by going to "Settings > About Phone > Build number" and looking for a userdebug string.
We're still investigating how this happened, but we believe it to be extremely rare.
If you are running a userdebug build, can you please contact me directly at [email protected]? Please make sure the subject contains "Android userdebug problem" so I can find your e-mail more easily.
I would appreciate it if you could include the following information:
* Where did you buy the phone? Store location?
* IMEI (Available by going to Settings > About Phone > Status > IMEI)
* Your google account name used on the phone.
This will help me assemble a list of people affected by this bug.
Thanks!
Nick Kralevich
Android Security Team
mgymnop said:
Looks like that some of the Nexus S got the wrong software that makes them at the moment not capable to get the 2.3.1 update neither manual nor as OTA. If you find under phone information "userdebug" you won't be able to update yet. It looks like Google just found out about this problem a couple of days ago. I got my phone today and this is not a good start with the Nexus S experience:-( I will wait a few days and otherwise this phone goes back to BestBuy.
Below is comment from Nick Kralevich who works for the Android security team:
"userdebug" versions of Android are intended for engineering use only. It contains additional debugging compared to "user" builds. The hardware is exactly the same. You'll never get an update for a userdebug version of Android, which is naturally bad.
You can find out if you have a userdebug build by going to "Settings > About Phone > Build number" and looking for a userdebug string.
We're still investigating how this happened, but we believe it to be extremely rare.
If you are running a userdebug build, can you please contact me directly at [email protected]? Please make sure the subject contains "Android userdebug problem" so I can find your e-mail more easily.
I would appreciate it if you could include the following information:
* Where did you buy the phone? Store location?
* IMEI (Available by going to Settings > About Phone > Status > IMEI)
* Your google account name used on the phone.
This will help me assemble a list of people affected by this bug.
Thanks!
Nick Kralevich
Android Security Team
[email protected]
Click to expand...
Click to collapse
I dont have this problem but great find
Hi all
Count me in on this one. Good find, I was wondering why no OTA notification came up on my device...
Purchased mine at Best Buy @ Millenia Mall Orlando, FL
If you are having a phone having userdebug based firmware please contact [email protected], he has personally contacted me and gave me a solution. Google has taken customer service to a whole NEW level my friends.
I state again, anyone not being able to Update to 2.3.1 due to firmware version having "soju-userdebug 2.3 GRH55 79397 test-keys", "pre-released os" contact [email protected]
thanks mythamp.
does re-locking the bootloader after flashing allow me to get stock OTA updates? I read in another thread that when I flash CWM I loose the ability to update by OTA... thanks for any clarification!
I believe that firmware is completely stock and it even overrides the clockworkmod recovery with stock recovery. I have faith that this will receive OTA updates but I cannot test it and confirm until google sends out one!
I just exchanged my SNS against one with the normal software. It is so much faster now and I don't have problems installing applications from the market anymore. If you have a phone with the userdebug software running try to exchange it. I had no problems at BestBuy today.
Hi all,
For the most up to date information about this "userdebug" problem, please contact Google at [email protected].
Edited 2011-03-30 to use [email protected] instead of my personal e-mail address
Userdebug problem
What exactly was the solution for those of you with the problem?
I have emailed the people suggested but have had no response for two weeks so am just wondering whether there is another way to get a solution so i can get OTA updates or whether i should jump ship and get CM7.
Thanks
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
When I go to Settings > About phone, I can see my build number, which is vns-l23c45b130, but at the very bottom, I also see "Custom version: CUSTC45D002". Does anyone know what this means and if it has any affect on what roms I can safely flash?
DrPugsley said:
When I go to Settings > About phone, I can see my build number, which is vns-l23c45b130, but at the very bottom, I also see "Custom version: CUSTC45D002". Does anyone know what this means and if it has any affect on what roms I can safely flash?
Click to expand...
Click to collapse
It means that the firmware was custom made for your carier ( they modified it)
Would that have any impact on which roms I can flash?
DrPugsley said:
Would that have any impact on which roms I can flash?
Click to expand...
Click to collapse
No
Good to know, thanks!
RazOne said:
It means that the firmware was custom made for your carier ( they modified it)
Click to expand...
Click to collapse
How can we remove such custom patches (carrier custom patches) without rooting?
(I got an update while I was traveling in Singapore. But now I don't need that. EMUI 10 update also contains update for carrier custom patch... I need to remove it before upgrading to EMUI 10)
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.