Related
Hi all, I'm quite new to this forum and I hope I dont break any netiquette with my question.
Now I have a N1 I bought on ebay, used, rooted and perfectly functioning.
I don't remember how, but I was able to update it to FRG83D downloading the rom, renaming it, copying on my sdcard etc ...
Now ...
I can't update to FRG83D.
I understood that having a rooted N1 NO OTA UPDATE shall ever work for me, not the manual update is available.
I was able to skip the "no signature verification" error suing clockwork mod, but i can't install the patch anyway, the system alway replies "assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk" ... then a serie of letters and number follows.
I know nothing about this, I must confess, but my suspect is that the update fails because something doesn't match between the update and the ROM which is working on my N1 (which is by the way the original one build frg83d
baseband version
32.36.00.28U_4.06.00.12_7
kernel
2.6.32.9-27240-gbca5320 android-build apa26 #1
Any sugestion ?
I mean and idea about where I can download a FRG83D version suitable for my phone ?
If you just want stock with very little tweaks, may i suggest Geo's Rom. It's basically the latest stock rom w/ superuser, busybox, trackball alert etc. Runs amazing too =)
As for breaking any netiquette, you're suppose to post this in the questions forum not the general. Have fun with your phone.
worked!
Thanks Mokurex!
It worked.
It's unbelievable.
I spent three nights in search of an answer, and then you solved it in few seconds.
I'm new to Android, and I must confess that I'm quite disoriented.
There hare hundred of versions, produced by individuals, companies, etc ... The one I used, I mean the one you suggested me, seems to be the fruit of an individual's work in the US.
It's ok to me, sounds and works good.
But It's not the original one, I mean the one released by ... Google ? or ... what ?
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1, the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
I understand that we can rely of forums and on kind people like you, but having some clear cut guidelines would be very useful.
... and looking at the future ... I guess I'll have the same problems when I'll have to update to Gingerbread.
I's very frustrating to search the web for a suitable ROM for your phone ...
stefanopelloni said:
[snip]
But It's not the original one, I mean the one released by ... Google ? or ... what ?
Click to expand...
Click to collapse
No, it's not the original. That one is deodexed, so any future OTA updates will not work (as Google's stock ROMs and updates and not de-odexed). You will have to wait until someone repacks the update, then apply it.
stefanopelloni said:
[snip]
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1,
Click to expand...
Click to collapse
Did you read the wiki? There are lots of posts/threads/guides available.
stefanopelloni said:
[snip]
the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
Click to expand...
Click to collapse
What are you trying to say? Phones running a rooted, but otherwise stock ROM will certainly received the OTA updates. Now if you use a non-stock ROM, you may or may not receive the OTA update. But whether you receive it or not, you will not be able to apply it as is, until someone repacks it (unless you are using the stock ROM, rooted or not).
I believe you have to use the stock recovery as well if you wanted to update via OTA.
If you want to get Gingerbread by way of OTA, then revert to stock rom and recovery. Everything you need is in the sticked thread in the development section.
Mokurex said:
I believe you have to use the stock recovery as well if you wanted to update via OTA.
[snip]
Click to expand...
Click to collapse
No, you do not. You just need a newer version of Amon_RA (1.9+) or CWM.
Thank you for the correction.
Efrant, Mokurex,
perhaps it's my problem.
My original plan was to restore my phone is a status capable of receiving OTA updates. Considering that I'm not an IT expert it would be easier for me ho have such a phone.
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Mokurex helped me a lot (actually, solved my problem by now) suggesting that version of the ROM (I mean Geo's one) but it's the fruit of a work of an individual. I'm very grateful to him as well, but who knows about the future. Will Geo provide a similar version of Gingerbread as well ? Because without him I can't upgrade.
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Geo has been quick to update his rom to the newest version. To upgrade to gingerbread, i'd assume that it would be like flashing any other custom rom, but there might be a bit more steps involved.
If you want completely stock, no root whatsoever, go here.
stefanopelloni said:
[snip]
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Click to expand...
Click to collapse
I said it before, and I'll say it again: rooting has no bearing on the phone's ability to receive and install OTA updates -- what matters is which ROM you have. I rooted my phone when I bought it, and it had Eclair on it. I have received EVERY OTA update without any problem.
stefanopelloni said:
[snip]
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Click to expand...
Click to collapse
That is probably because you were not using a stock ROM...
stefanopelloni said:
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Click to expand...
Click to collapse
If you want a stock ROM, you can go here: http://developer.htc.com and download a Nexus One image to your sdcard, rename it to PASSIMG.zip and boot the phone into bootloader (by holding the trackball and powering up the phone). It should automatically detect the file and allow you to flash it.
Files from the site are official. If you get them from anywhere else, you can't really know what's been modified.
Dear Efrant,
if you were a girl, and in Italy, I would probably kiss you.
Now I have a bright-clear picture of the situation.
During the next holiday, I'll try and flash a stock version of the OS and then try the OTA update.
By now, the version mokurex suggested me work brilliantly and after so many nights wasted in a desperate search of an answer my myself i'm going to have a break.
... but thanks a lot. thanks indeed !!!
Sorry to disturb you again Eftant.
The fact is that today decided eventually to follow your step, but encountered another unexpected problem.
downolaed the original HTC rom - done
renamed it passimg.zip - done
turned on the N1 pressing trackball - done
expected detection of PASSIMG.zip - done
opening passimg.zip - done
checking passimg.zip - done
and then .. nothing
once the N1 load the passimg.zip file (i notice it from a loading bar on the upper right conder of the phone) it just allow me to
1)run bootloader agan
2) lock sim
3) restore something ...
... and that !
No possibility to "flash" rom as you wrote.
Did I miss anything ?
I see from the web that a lot of people bring back the N1 to the stock image using SDK from PC (MAC in my case) but the steps are not so clear considering the fact that I'm not that comfortable with the shell and the Android SDK is not intuitive (... to me).
Thanks in any case for your attention!
Try wiping your device then download the FRF91 image from the same site, rename it to PASSIMG.zip and save it to the root of your sdcard. Put your sdcard back into your device, and boot into the bootloader (by holding down the trackball as you push the power button). Once it flashes, wait for the OTA to FRG83G. Some users have said that the later images don't work using, particularly if you have updated to the 0.35 version of the bootloader.
I purchased my tablet from US and I live in india. Only one time i was able to update when i run it first time, after than never got any message for update of Android Version.
When i go to Settings>About Tablet and click on System Update and check for new version it's gives me message "Your device is up to date" and when i see the version details than these are
Model Number : A500
Android Version : 3.0.1
Kernel Version : 2.6.36-00017-gc98d63f
Build Number : Acer_A500_1.016.01_COM_GEN1
Update is not available for india yet or where i am wrong please help.
Not sure if your locale has anything to do with getting updates. That's typically an issue with 3G providers, but as long as your tablet is an A500 (wifi only version) it should find the OTA updates no problem, that it unless you are running a custom ROM. Either way, you can manually update your tablet. All the information you need is here: http://forum.xda-developers.com/showthread.php?t=1113878
If you currently have a custom ROM or rooted your stock ROM, you will lose root by updating to a newer stock ROM, and the only way to recover root is by reverting back to Android 3.0. There are several custom ROM's based on 3.2 which already have root, if you also choose to go that route. If you have no idea what I mean when I mention root, just don't worry about it and carry on with that link I posted
Thanks Bloodflame, Yes i read that it can not be rooted and thank you for the link to get it update manually but i don't understand why i am not able to get updates.
And whether it is good to update with 3.0.2 ? Please suggest.
BadProgrammer said:
Thanks Bloodflame, Yes i read that it can not be rooted and thank you for the link to get it update manually but i don't understand why i am not able to get updates.
And whether it is good to update with 3.0.2 ? Please suggest.
Click to expand...
Click to collapse
can't explain why you're unable to OTA update, but the security and performance improvements along with new features (ie, native mouse support) should make a manual 3.2 update worthwhile
Ok Thanks, I will update to 3.2 and let me see what magic it does.
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
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.
Hello, total newbie here. I've been searching around trying to find out how to manually update my android version to at least oreo 8.0 (due to a certain app). Or is it time to move on and grab a new phone?
As far as what I've done, I've gotten the bare basics of checking for updates on my settings and my current OS version (7.0). All it tells me is that I'm currently up to date. I've checked the manufacturer's website and it also told me that 7.0 is the official version of the phone (at least from my understanding unless I'm wrong which is very possible). I've tried looking around for manually upgrading the version and most recommend that I shouldn't because the device might not fully support the version and cause problems.
D3STINY22 said:
Hello, total newbie here. I've been searching around trying to find out how to manually update my android version to at least oreo 8.0 (due to a certain app). Or is it time to move on and grab a new phone?
As far as what I've done, I've gotten the bare basics of checking for updates on my settings and my current OS version (7.0). All it tells me is that I'm currently up to date. I've checked the manufacturer's website and it also told me that 7.0 is the official version of the phone (at least from my understanding unless I'm wrong which is very possible). I've tried looking around for manually upgrading the version and most recommend that I shouldn't because the device might not fully support the version and cause problems.
Click to expand...
Click to collapse
Do NOT move on to a new phone.
S6 Edge+ with a custom ROM is suitable for another two years
D3STINY22 said:
Hello, total newbie here. I've been searching around trying to find out how to manually update my android version to at least oreo 8.0 (due to a certain app). Or is it time to move on and grab a new phone?
As far as what I've done, I've gotten the bare basics of checking for updates on my settings and my current OS version (7.0). All it tells me is that I'm currently up to date. I've checked the manufacturer's website and it also told me that 7.0 is the official version of the phone (at least from my understanding unless I'm wrong which is very possible). I've tried looking around for manually upgrading the version and most recommend that I shouldn't because the device might not fully support the version and cause problems.
Click to expand...
Click to collapse
download the update rom then copy it to sd card and then power off the phone and insert sd card to phone . go to recovery mode using 3 keys and select update from sd card using vol- and vol= and accept it using power button . this is at you own risk . all you data may be lost by upgrading the phone using this tutorial