Related
I recently purchased a Nexus 7 because I was getting tired of dealing with IOS devices and needed a break from them and also wanted to get a tablet that would allow me to play games and apps on a bigger screen. (I recently got a mobile broadband device so I can play on-the-go). When I got the nexus 7, being unfamiliar with android OS and devices, I thought it would update just like an iPod or iPad. Boy was I wrong. After realizing that the nexus 7 I had was running 4.0.3 and that the google play store wasn't on the device (and wouldn't work after manually putting on the nexus), I frantically rushed to get jellybean 4.3 in hopes that my problems would be solved.
So I began to search on how to update and after looking for a while I was directed to a couple of youtube videos as well as this site. Following the guides available on this site, accompanied with the youtube videos, I was able to begin flashing my device in order to get jellybean 4.3 but one instruction that was not outlined was how to update the bootloader. The bootloader I had was a "GROUPER" 3.32 bootloader and when attempting to flash 4.3 on to my nexus 7, it said that it failed because I needed 4.23 to do it. So now I have a nexus that only boots into that bootloader mode and that's it. I can't access recovery mode or start the nexus 7. It only shows the Google sign and booting failed in the top right corner.
So, my question is how do I upgrade the bootloader to 4.23? I need to know this because a couple threads that I read after panicking stated that all I had to do was flash the stock image to my nexus in order to fix the problem but I cannot do that without a 4.23 bootloader. Can I fix the problem or is there no hope for my device?
Are you REALLY sure about that its a N7? The 1st gen of N7 was released with JB 4.1 and the 2nd gen with JB 4.3 and all of them have Play preinstalled and have the latest version of android downloaded and installed via OTA updates.
Anyway, if you see 100% sure its a N7, here is a fine guide for returning to stock. http://forum.xda-developers.com/showthread.php?t=1907796
Erovia said:
Are you REALLY sure about that its a N7? The 1st gen of N7 was released with JB 4.1 and the 2nd gen with JB 4.3 and all of them have Play preinstalled and have the latest version of android downloaded and installed via OTA updates.
Anyway, if you see 100% sure its a N7, here is a fine guide for returning to stock. http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I just purchased a refurb Nexus 7 (1st gen), and it came exactly the same way as the other guy described. It's running 4.0.3, and this grouper bootloader 3.32. I was expecting a device that was running android 4.1 at the least.
@funkball: Could you link me where did you buy that tablet?
Something must be fishy about it, because there is no ICS rom to the grouper, not even custom roms.
OP has probably solved the problem by now but in case anyone needs it the solution to upgrading the bootloader is below:
http://forum.xda-developers.com/showthread.php?t=2150251
I bought a Nexus 7 (refurb) from Expansys-USA and it came with 3.2 bootloader so I had to update via the above link so I could flash the Lollipop factory image.
This post/thread is to summarize where to find full SBF files, leaks, etc for the Moto X (2013 or First Generation).
REMEMBER... Always flash the same ROM/SBF or Newer to your phone. NEVER attempt to downgrade your rom!!! for more info, see DOWNGRADING
Motorola posts their complete STOCK "Recovery Images" (aka SBF files) for the GSM and Verizon Developer Edition X at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
If you have the Retail and/or Moto Maker XT1053 (aka Unlocked ships with T-Mobile SIM, or Unlocked Ships with Net10 SIM), you can also use the GSM Developer Edition (XT1053) roms from Moto's site.
If you have the Retail and/or Moto Maker Verizon X (XT1060), you can also use the Verizon Developer Edition (XT1060) roms from Moto's site.
There might be a delay in Moto making an SBF available.
For other models of X, I know of 3 sites for "leaks" which contain the SBF files for nearly every model of X (2013). You may need to check EACH site to find the particular rom you are looking for. NOTE: None of the following sites are owned, operated, or sponsored by Motorola. They may be down or offline at any time, without warning.
http://sbf.droid-developers.org/ <- DEAD when checking on 8/22/15
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 <- seems to have the most 4.4.4 roms
http://motofirmware.com/files/category/9-ghost/ <- DEAD when checking on 8/22/15 once there, look under the GHOST folder. (as of 11/9/2014, its format and access has changed)
http://motofirmware.center/files/ <- Select Moto X 1St Generation from the list along the right side of the page
Are there any others?
@dagoban has linked a few other in Post #17 of this thread..
dagoban said:
..Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Click to expand...
Click to collapse
See Post #17 for more direct links.
As 5.1 SBF files become available, they are being collected and curated in this thread -> [OFFICIAL] Collection Full Firmwares (FXZ/SBF) Lollipop 5.1
FAQ:
1. How do I know which file to download?
- If you are NOT running a 3rd Party or Custom ROM... take a look on your phone, under App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until you find the SBF that matches. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
2. Where do all these SBF files come from?
As mentioned earlier, Moto does make the Dev Edition "recovery images" (in SBF format) available on their web site. For all others, the only way for us to get firmware files, is for a copy to be LEAKED to us.. The "Leaked" firmwares are files that are basically "stolen" by a Motorola or wireless carrier employee, who then posts the file on the internet for us... So we can't always count on this ever happening, nor can we have any expectations that a particular firmware will actually get leaked, or when it will be leaked.
There is some talk about using Motorla Device Manager (MDM) app to upgrade your phone, and how during the update process, the app downloads the full FXZ (another term for SBF) to your PC, so it could be copied/saved to another folder for use later. I have not done this with MDM.
EDIT: As of 12/12/14, Only the filefactory.com link is working. The others appear to be down. I don't know the owners of the sites, so I can't say if they will return or not.
EDIT2: As of 1/2/15, motofirmware.com seems to be back up, but sbf.droid-developers.org appears to be gone.
Great info! ??
SBF is my first choice, but when I needed the 4.4.4 retail firmware not found it in SBF, I had to turn to Google and found it.
FTP of Moto Firmware is empty, but the File Factory folder has many versions! Very cool.
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
x000x said:
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
Click to expand...
Click to collapse
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
edit: problem resolved. see my findings: http://forum.xda-developers.com/showpost.php?p=57122184&postcount=635
Thanks Kidjoe
x000x said:
well issue was I was rooted with twrp and silly me I tried to do the ota update. so now it won't get past the warning about unlocked bootloader. I read after the fact that you needed to revert back to stock before taking ota. mine is 30.71, but the other issue is I cannot find that firmware anywhere. my only option in regards to firmware is to use 4.4.2 that I found. I've posted the question here http://forum.xda-developers.com/showthread.php?t=2542219&page=123
Click to expand...
Click to collapse
BUT if you tried to take the OTA while TWRP was on your phone, just boot into fastboot mode on the phone, and do a mfastboot erase cache will get you out of the bootloop. Then you can flash stock recovery on there, take the ota.
Or you can just flash the 4.4.2 or 4.4.4 for your phone, when completed, flash TWRP on there, reboot hte phone to bootloader, enter Recovery/TWRP and root.
Yes, You can flash a higher/newer version without problems. You just can't flash older once 4.4.2 or higher has been flashed to your phone. (the only time its safe to flash older was when you had 4.4 on your phone, and you were Following the SlapMyMoto process to downgrade to 4.2.2. W/Camera Update as part of the process).
Thank you for this!
KidJoe said:
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
Click to expand...
Click to collapse
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
scryan said:
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
U can always flash newer images without a problem. It's flashing older images (downgrading) that's a problem.
scryan said:
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
The OTA updates are incremental, so you need to be on a certain level to take them. (to take 4.4.4 you need to be on 4.4.2, to take 4.4.2 you need to be on 4.4, etc)
Full SBF/FXZ files are complete roms. They are not incremental like the OTA Updates are. When flashing a FULL SBF/FXZ you can just flash it, so long as its the same version OR newer than what is on your phone, with no need to "step up." In other words, if you have 4.4 on your phone, you can flash directly to 4.4.4 using the full 4.4.4 SBF, without having to flash 4.4.2 on there first.
The risks to keep in mind would be, just like any update...
If you have a locked bootloader, the vulnerabilities exploited to root and disable write protection might be patched in the newer roms, that means you might not be able to root, or the processes may change for the newer rom. However, with an unlocked bootloader, there is no issue rooting and disabling write protection (lollipop is yet to be confirmed).
In either case, since you can't safely downgrade, if you find bugs, other issues (battery life, reception, etc), or there is something you don't like about the rom, you're stuck, since you can't safely downgrade.
THANK YOU SO MUCH every damn site I went to posted a link to a long dead server LIFE SAVER YOU ARE....
Method to go STOCK.
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
the_fiasco said:
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I suggest you use this : perfect compatible stock firmware for xt1052 asia retail first gen moto x. : http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip pl. check it with someone else just in case if I'm wrong. pm me if you have any problems
Hey, thanks for replying!
Yeah, I found this stock recovery a while ago and downloaded it and now back to stock 4.4.4. Thanks a lot!
Sent from my Moto X using XDA Free mobile app
@KidJoe since filefactory is really slow, I searched for some alternatives and found some good ones, maybe you could add it to your 1st post?
Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Some other alternatives:
XT1053 4.4.2; 4.4.3; 4.4.4 (downloading from mega server (fast!)), thx to OP (http://www.grupoandroid.com/topic/110743-aporte-firmware-t-mobile-retail-442/):
TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml.zip: https://mega.co.nz/#!7RJygbQI!Sbx-bGRV8NbRsqLKS-d33nM_SEgY81czr8rye2ROYb0
TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml.zip: https://mega.co.nz/#!HQ4l2JIT!LD1gf8m2GxBou3NDFD8lzuxSi2OCn37X7Vhbe-hjNqc
TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz: https://mega.co.nz/#!zIJhlSCS!o9B7xvRSJ9gTCdTYjXdmVActEmdWRBvhIVjs8JUHI8Q
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/M2H9LMFJbYiag
from mega (fast!):http://www.mega.co.nz/#!jZgjECZT!sG0-9Vqngms551gwv9PfejY1mw_5QCL8Pg48KTVx4m0
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/KLmLR43SbYiaX
XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/hDEHw2O-bYiae
For Brazilians user's
http://www.motoforum.com.br/topic/4...oto-g-2014-moto-e-moto-maxx-nexus-6-moto-360/
Does anyone know of a link that contains the Rogers 4.4.4 file? I need it to update to 5.1.
I have tried the filefactory link but after the countdown, the file is unavailable. I haven't seen any other links for it.
Thanks
I have the same problem. I've looked everywhere and cannot find the rogers 4.4.4 file.
If anyone has it download, could you please share with us.
Alternatively, would i be able to Flash XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml.zip since the build versions are the same?
I only need the 4.4.4 in order to install the Lolipop update.
Thanks
I just Received OTA update 5.0.2 for Nexus 7 3G Nakasig. After updating i couldnt find any settings related to Mobile Data. Its completely gone from the settings. I tried replacing SIMs. I cannot enable 3G anymore. I wanted to flash my android to Stock android but i cannot find Images for it anywhere. I think i got the OTA by mistake (maybe of WIFI nexus 7)
Any Ideas .
I think my device is converted into Nexus 7 Wifi. It is showing the model number ME370T which is Nexus 7 Wifi.
That is weird if you automatically got the WiFi only update for a 3G N7.
The older KitKat stock roms (including lollipop) for N7 3G (nakasig) are available from Google: https://developers.google.com/android/nexus/images#nakasig
Alternatively if you wanna stick with the WiFi lollipop that you have and you're into flashing minor mods, check out my last (5.0.2) post here on possibly restoring the 3G. haven't gotten feedback as to whether it actually works tho (I have WiFi only):
http://forum.xda-developers.com/showthread.php?t=2535586&page=22
but you should be comfortable with flashing stuff to try it tho, if not you could make things worse and might be better off flashing KitKat or waiting for the correct lollipop.
Personally i was waiting for Lollipop for months ... Since the first release . So i think i am going to keep it until lollipop for 3G version comes out. Then i flash it to bring back my Modem Features.
Looks like the proper Lollipop images for 3G have been released. Check the Google link above.
dtg7 said:
Looks like the proper Lollipop images for 3G have been released. Check the Google link above.
Click to expand...
Click to collapse
Nice find... Now i can restore to stock image . Lets see if it brings back Mobile Data Options.
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.
TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.
jehy_rus said:
TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.
Click to expand...
Click to collapse
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.
Mynouddin said:
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.
Click to expand...
Click to collapse
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.
jehy_rus said:
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.
Click to expand...
Click to collapse
Thread closed
I need your help.
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks
Nanakwameampong said:
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks
Click to expand...
Click to collapse
Download this app it will show you your correct software and model.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo