Related
I am in China and a VPN user. I turn on VPN from time to time for updates and other web browsing etc.
I received an OTA update yesterday and updated it. But today I received the exact same update. I have learned that many people using Nexus 6 had their phones stuck at reboot after two same updates. Is Nexus 6P the same case?
Many people suggest me to unlock OEM and BL so that I don't have to worry about "stuck at reboot" issues because of OTA. Is it necessary to unlock BL?
If I only leave the OEM unlocked, is it still possible to flash it when it bricks?
Sorry for poor English and thanks in advance!
I don't know about unlock OEM. I think it's common to unlock boot loader (this will ERASE your phone) and flash custom recovery. If you are not sure about this, read this very nice guide.
On a different note, I bought the 6p to use with Fi in the States and am currently in China. But when I bought a Liantong (unicom?) SIM, I can't make calls although internet and sms are fine. And the phone can't recognize the number.
PS. It's interesting to see 'sorry for the poor English.' I'm Chinese too! And happy to see you here
Not one but two Chinese friendlies? Nice
Just back up all your data first and unlock the bootloader. After that you might want to flash the latest factory image via fastboot to stop worrying about this month's OTA. And before every OTA you can take nandroid backups in a custom recovery just in case.
Or better - just use a ROM other than stock
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Sorry for the stupid question. I have checked in the system settings for a new update but it says I'm on the latest patch. I've also heard that there may not even be a security patch available for the retail US XT1625 and it should still be on MPJ24.139-48, is that true?
I've checked the Motorola website and it seems there is an update that I don't have. I don't really know what I'm doing and I don't want to void my warranty by flashing a newer stock image, if that even does void it.
If there's anything I can do, I would appreciate the help. Thank you.
NDS02 said:
Sorry for the stupid question. I have checked in the system settings for a new update but it says I'm on the latest patch. I've also heard that there may not even be a security patch available for the retail US XT1625 and it should still be on MPJ24.139-48, is that true?
I've checked the Motorola website and it seems there is an update that I don't have. I don't really know what I'm doing and I don't want to void my warranty by flashing a newer stock image, if that even does void it.
If there's anything I can do, I would appreciate the help. Thank you.
Click to expand...
Click to collapse
No, MPJ24.139-64 is the latest stock firmware. Not sure why you aren't getting it, unless you are on a custom recovery. That would prevent you from getting the update. I too have the XT1625 and I had to return my device to stock recovery before I received the update. There is a thread somewhere in the forum (might be in G4+) that tells you how.
However, if you are on full stock with no modifications then I have no idea why you aren't getting it.
I am indeed on full stock, I just bought this phone factory unlocked last week from a retail store and I really don't know why I haven't received an update for it. Is there any way that I can force it to update without unlocking the bootloader and just flashing the new stock image? I want to receive the Android 7.0 update when that comes out, but I would also like to update to the most recent build.
Can I sideload the OTA without voiding my warranty and also still get the Android N update when it becomes available? If so how?
If you have any answers I would greatly appreciate them.
NDS02 said:
I am indeed on full stock, I just bought this phone factory unlocked last week from a retail store and I really don't know why I haven't received an update for it. Is there any way that I can force it to update without unlocking the bootloader and just flashing the new stock image? I want to receive the Android 7.0 update when that comes out, but I would also like to update to the most recent build.
Can I sideload the OTA without voiding my warranty and also still get the Android N update when it becomes available? If so how?
If you have any answers I would greatly appreciate them.
Click to expand...
Click to collapse
If you are 100% certain the bootloader is still locked then the only thing I can suggest is to contact Motorola Customer Service and find out why it isn't updating. Or return to the store where you purchased it. But my phone downloaded the update even before I returned to stock recovery. I then saved it to my SDCard, returned to stock, and put the update back in the proper folder. When I rebooted it updated the normal way. Was it unopened when you bought it? Maybe the store did something to affect the update. Also, I am on the USA version and assume you are as well.
It is a USA version.
I already called Motorola customer service and they said that the Moto G4 receives updates in batches and that whether or not I receive the security update is based entirely on my carrier. I have Straight Talk AT&T. I've also tried it with a Sprint SIM card and it didn't update either.
When I brought it back to the store I purchased it from (Best Buy), they said that since it's an unlocked phone it will receive updates directly from Motorola, and it doesn't matter what carrier it's on.
NDS02 said:
It is a USA version.
I already called Motorola customer service and they said that the Moto G4 receives updates in batches and that whether or not I receive the security update is based entirely on my carrier. I have Straight Talk AT&T. I've also tried it with a Sprint SIM card and it didn't update either.
When I brought it back to the store I purchased it from (Best Buy), they said that since it's an unlocked phone it will receive updates directly from Motorola, and it doesn't matter what carrier it's on.
Click to expand...
Click to collapse
Best Buy is correct. As far as Motorola Customer Service, the answer one gets from to any question depends on who you ask. I have never had to call them, but other users here on XDA have had a wide variety of results. Sometimes calling back and trying a different rep yields better results. Maybe clarifying your phone model/type and the fact you have an unlocked phone would help.
Other than that my friend, I am out of suggestions.
I'm also still on -48. Purchased from Costco.
Sent from my Moto G (4) using Tapatalk
NDS02 said:
Sorry for the stupid question. I have checked in the system settings for a new update but it says I'm on the latest patch. I've also heard that there may not even be a security patch available for the retail US XT1625 and it should still be on MPJ24.139-48, is that true?
I've checked the Motorola website and it seems there is an update that I don't have. I don't really know what I'm doing and I don't want to void my warranty by flashing a newer stock image, if that even does void it.
If there's anything I can do, I would appreciate the help. Thank you.
Click to expand...
Click to collapse
From all the threads and surfing on different sites I have come to a conclusion that the MPJ24.139-63/64 updates is only for amazon variant , because on the official Motorola site the said update is only for amazon variant . And the latest for non-amazon is the MPJ24.139-48/49
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Mansuur said:
From all the threads and surfing on different sites I have come to a conclusion that the MPJ24.139-63/64 updates is only for amazon variant , because on the official Motorola site the said update is only for amazon variant . And the latest for non-amazon is the MPJ24.139-48/49
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
Not sure why you came to that conclusion, but you are dead wrong. I do not have the Amazon variant and I received the update to MPJ24.139-64 via the normal update channel from Motorola. Also, here is a link to the Non-Amazon variant of the stock ROM (-64 version):
http://www.filefactory.com/file/3sqq...LT_CFC.xml.zip
Furthermore, I have a copy of the -64 update blur file (non-Amazon variant) saved to my PC.
Any questions?
Can you share the blur file update?
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
pastorbob62 said:
Not sure why you came to that conclusion, but you are dead wrong. I do not have the Amazon variant and I received the update to MPJ24.139-64 via the normal update channel from Motorola. Also, here is a link to the Non-Amazon variant of the stock ROM (-64 version):
http://www.filefactory.com/file/3sqq...LT_CFC.xml.zip
Furthermore, I have a copy of the -64 update blur file (non-Amazon variant) saved to my PC.
Any questions?
Click to expand...
Click to collapse
Can you share the blur file update?
pastorbob62 said:
Not sure why you came to that conclusion, but you are dead wrong. I do not have the Amazon variant and I received the update to MPJ24.139-64 via the normal update channel from Motorola. Also, here is a link to the Non-Amazon variant of the stock ROM (-64 version):
http://www.filefactory.com/file/3sqq...LT_CFC.xml.zip
Furthermore, I have a copy of the -64 update blur file (non-Amazon variant) saved to my PC.
Any questions?
Click to expand...
Click to collapse
Okay , but a lot of Moto G4 users are still on MPJ24.139-48 and not getting the update , especially the ones who are on MPJ24.139-49 . I have not read a single comment from a MPJ24.139-49 user that he/she got the july patch to MPJ24.139-63/64 .
There is a person on the official Lenovo Motorola forums where he wrote that he bought two devices from the same retailer and one of the devices got the update immediately to MPJ24.139-64 but the other one is still stuck on MPJ24.139-49 . Can you help me with that .
I have tried to install the blur files available on the forums but it gives the error because the update is for 139-48 users not 139-49 ones . I have also tried to install the Full Stock MPJ24.139-64 but still gives the " wrong footer " error .
Thanks !
Mansuur said:
Okay , but a lot of Moto G4 users are still on MPJ24.139-48 and not getting the update , especially the ones who are on MPJ24.139-49 . I have not read a single comment from a MPJ24.139-49 user that he/she got the july patch to MPJ24.139-63/64 .
There is a person on the official Lenovo Motorola forums where he wrote that he bought two devices from the same retailer and one of the devices got the update immediately to MPJ24.139-64 but the other one is still stuck on MPJ24.139-49 . Can you help me with that .
I have tried to install the blur files available on the forums but it gives the error because the update is for 139-48 users not 139-49 ones . I have also tried to install the Full Stock MPJ24.139-64 but still gives the " wrong footer " error .
Thanks !
Click to expand...
Click to collapse
I have no idea. All I know is that my XT1625 16 Gbyte USA version updated without any issues from -48 to -64 (back in October). The -49 version is a completely different animal (maybe the G4+) and I have no experience with it. You might check your Software Channel under Settings/About Phone and see which one you are on (I am on the retus Software Channel), but other than that I have no clue, unless the version hardware is different.
Again, you are talking apples and oranges when referring to the -49 version.
pastorbob62 said:
I have no idea. All I know is that my XT1625 16 Gbyte USA version updated without any issues from -48 to -64 (back in October). The -49 version is a completely different animal (maybe the G4+) and I have no experience with it. You might check your Software Channel under Settings/About Phone and see which one you are on (I am on the retus Software Channel), but other than that I have no clue, unless the version hardware is different.
Again, you are talking apples and oranges when referring to the -49 version.
Click to expand...
Click to collapse
Hahahaha .....
Mine is also ( G4 )ATHENE XT1625 RETUS version , not ( G4+ ).
Available firmware versions for XT1625 are :
MPJ24.139-48
MPJ24.139-49 , and
MPJ24.139-64 . You can check on https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
For some reason a some users got update from -48 to -64 and some got -48 to -49 and got stuck with it . I do not know what is going on . Just hoping to get the NOUGAT UPDATE . I am also very confused about the number system .
I would love to keep this thread going. I am in the same boat. I have a Moto G4 (Non-Plus) XT1625 Retus version. I am still on MPJ24.139-48. If you review Motorola's website...it says the latest version available is MPJ24.139-64. However, I have never received this OTA update. As a matter of fact I have tried to install this firmware from their website before and while it installs I get error crashes.
As far as I can tell from my research, in the US... some users got 64 but a lot of people are still on 48. Any thoughts? I would love to get this solved. Oh! and before you ask NO i don,t own the amazon variant!
30mmrain said:
I would love to keep this thread going. I am in the same boat. I have a Moto G4 (Non-Plus) XT1625 Retus version. I am still on MPJ24.139-48. If you review Motorola's website...it says the latest version available is MPJ24.139-64. However, I have never received this OTA update. As a matter of fact I have tried to install this firmware from their website before and while it installs I get error crashes.
As far as I can tell from my research, in the US... some users got 64 but a lot of people are still on 48. Any thoughts? I would love to get this solved. Oh! and before you ask NO i don,t own the amazon variant!
Click to expand...
Click to collapse
If you are on 139-48 try this OTA update .
https://forum.xda-developers.com/moto-g4/help/amazon-xt1625-ota-t3474128
Mansuur said:
If you are on 139-48 try this OTA update .
https://forum.xda-developers.com/moto-g4/help/amazon-xt1625-ota-t3474128
Click to expand...
Click to collapse
Good news this image worked! I am not on mpj25.139-64 :good: thanks.
Now on to the next problem... Relocking the bootloader. Ever since I unlocked it the first time... I have not been able to lock it. It errors out and asks for an official signed image. Which confuses me... Since ever one I've installed (minus the custom Roms ) have been. If anyone here has suggested fix let me know... Otherwise. I'll create another thread so I don't hijack this one.
Thanks again
30mmrain said:
Good news this image worked! I am not on mpj25.139-64 :good: thanks.
Now on to the next problem... Relocking the bootloader. Ever since I unlocked it the first time... I have not been able to lock it. It errors out and asks for an official signed image. Which confuses me... Since ever one I've installed (minus the custom Roms ) have been. If anyone here has suggested fix let me know... Otherwise. I'll create another thread so I don't hijack this one.
Thanks again
Click to expand...
Click to collapse
For that you have to install full stock/factory image which will re-lock your bootloader . But , that will erase all of your data . You can find tutorials on forum , no need to create another thread .
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
Mansuur said:
For that you have to install full stock/factory image which will re-lock your bootloader . But , that will erase all of your data . You can find tutorials on forum , no need to create another thread .
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
Click to expand...
Click to collapse
When I was on mpj24.139-48... I tried flashing the full image downloaded from Motorola's site. Still ran into the same issue. I don't mind that it will wipe my data.
On that link you sent over. Which file to download? I see the xt1625 folder and I see the Amazon firmware in it... But I am unsure what the other firmware is. I also see the Athens mpj25.139-64 folder on the main page below. Which is the safe file?
Thanks
30mmrain said:
When I was on mpj24.139-48... I tried flashing the full image downloaded from Motorola's site. Still ran into the same issue. I don't mind that it will wipe my data.
On that link you sent over. Which file to download? I see the xt1625 folder and I see the Amazon firmware in it... But I am unsure what the other firmware is. I also see the Athens mpj25.139-64 folder on the main page below. Which is the safe file?
Thanks
Click to expand...
Click to collapse
Try the the one with this name " XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip " .
Have you tried flashing through fastboot mode ?
Mansuur said:
Try the the one with this name " XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip " .
Have you tried flashing through fastboot mode ?
Click to expand...
Click to collapse
Yeah minus... The custom Roms that is where I have always been flashing. On the custom side of things I was using TWRP.
Alright... I will try flashing the file is suggest and I'll post back here shortly
Hello everyone
I'm new member
I have moto x style never unlocked or modified and without facing any issues with my device since the first date of purchase but who knows!!!!
for this reason I would like to ask you guys if there any software can repair device OS if something goes wrong one day (as SW issue not HW one)
Thank you for any help you can provide.
We all wish there was... there is a Software Repair Assistant for Verizon Motorola devices (Droids) but otherwise no such software exists that I am aware of. You can always just flash your factory image via fastboot if it is available, but as of today the latest versions are not available and we are one version behind.
acejavelin said:
We all wish there was... there is a Software Repair Assistant for Verizon Motorola devices (Droids) but otherwise no such software exists that I am aware of. You can always just flash your factory image via fastboot if it is available, but as of today the latest versions are not available and we are one version behind.
Click to expand...
Click to collapse
So only way by using fastboot with correct image .and does it works with locked bootloader ? Any risks ?
Thakisgr said:
So only way by using fastboot with correct image .and does it works with locked bootloader ? Any risks ?
Click to expand...
Click to collapse
Yes... Only way. And it works with a locked bootloader as long as you are not downgrading, same or higher version only.
The problem is when these "software" problem occurs, it's typically at an OTA update, and we don't usually get new firmware images for 3-4 months after they are released
But this isn't unusual for manufacturers, few except the big "brands" have any way to recover and it's spotty at best.
acejavelin said:
Yes... Only way. And it works with a locked bootloader as long as you are not downgrading, same or higher version only.
The problem is when these "software" problem occurs, it's typically at an OTA update, and we don't usually get new firmware images for 3-4 months after they are released
But this isn't unusual for manufacturers, few except the big "brands" have any way to recover and it's spotty at best.
Click to expand...
Click to collapse
I really appreciate your time answering all my questions!!!:good:
VERIZON UNLOCKED BOOTLOADER ONLY.
Yes you can unlock these things as long as they have never hit the network on Verizon )... EVER... (with a different CARRIER sim) I watched guy at Best Buy do it with a PIXEL and Pixel I guess the true issue is, you never know how or when they would be started especially on a refurb --- etc... Good Luck on that one...
First thread ever but the support scarce for VZW users (Specifically)and ROMs are scarce in generally. WE ARE SCARED TO DEATH to get the bootloader relocked... I've been flashing since the originally G1 and usually just keep my mouth shut stay humble and learn from every thread. I can't really find a lot of info on the VZW version and really the fear of locking the bootloader after trying so hard to get an nde64x ver on 7.1.0 to unlock was quite the endeavor in itself. I just wanted to pass along some info. Ask questions. If your an expert I'm sure this is pointless, but I just answered all of this for a friend that just switched to the Evil Red.
1. YOU CAN Flash the google updates (Not the ota but full system img using the flash all.bat)
DOWNLOAD THE FACTORY IMAGE NOT THE OTA (Google --- Factory IMG, Marlin)
- Download which ever from 7.1.0 to 8.1.0 unzip (I use 7zip but your windows programs can do the same
- Install your Fastboot/Adb and drop the EXTRACTED in your platform tools folder ... NOT the whole folder... but the items within the folder, into Platform tools (Should be 6 items including the flash all.bat) IT WILL NOT RELOCK YOUR BOOTLOADER BUT WILL WIPE YOUR DEVICE UNLESS YOU GO IN TO MOVE THE -W SCRIPT
2. 7.1.2 roms aren't working well with the A B Slot issues recovery... I was losing my mind trying to get things to flash and finally come to the conclusion... TWRP-3.1.1-0-fastboot-marling.img and .zip are the only recovery I can install to get roms to flash... If I Fastboot or flash the -1 img (twrp 3.1.1-1) or the 3.2.1-0-marlin.img I have to flash back to stock to get roms flasheable again.
- Working TWRP Nougat twrp-3.1.1-0
Flash Away At that point... If you get stuck like me and install 3.1.1-1 or the Other 3.2.1-0 I had to return to stock because of the A-B partition issues and get back to 3.1.1.0 to flash roms and Kernels.
3. Oreo 8.1.0 works with the flash-all bat (Google FACTORY image). The Oreo version will NOT relock your bootloader!!!
- TWRP works on 3.2.1-0.
- Magisk 14.5 and 14.6 work on Oreo...
- Super Su SR5 works with SU Hide 1.09
- Sound mods are eluding me on Oreo but Weta 9 Pixel is working with MANUAL MOVES--- Use at your own risk...
Right now I am on a VZW device running Carbon (LOS Based) with a Modded Google Cam (GCMOD cam )Viper4Andriod working, Franco Kernel --- ((A Lot harder than I thought on LOS to get some of the normal things working))
Ask questions if you want I'll answer what I can. Or I'll ask question of someone else to try to get an answer... Happy flashing...
So if I have a VZW pixl XL on 8.0.0 that HAS been used on vzw then Im out of luck is what Im gathering?
LeoTheRomRasta said:
So if I have a VZW pixl XL on 8.0.0 that HAS been used on vzw then Im out of luck is what Im gathering?
Click to expand...
Click to collapse
Most likely, if you didn't unlock the bootloader with depixel8, back on 7.1
Sunshine team has no plans to work on unlocking newer versions, although, jcase said if someone could get temp root, he would provide an unlock...
So we're screwed. ?
Mikkey81 said:
VERIZON UNLOCKED BOOTLOADER ONLY.
Yes you can unlock these things as long as they have never hit the network on Verizon )... EVER... (with a different CARRIER sim) I watched guy at Best Buy do it with a PIXEL and Pixel I guess the true issue is, you never know how or when they would be started especially on a refurb --- etc... Good Luck on
1. YOU CAN Flash the google updates (Not the ota but full system img using the flash all.bat)
DOWNLOAD THE FACTORY IMAGE NOT THE OTA (Google --- Factory IMG, Marlin)
- Download which ever from 7.1.0 to 8.1.0 unzip (I use 7zip but your windows programs can do the same
2. 7.1.2 roms aren't working well with the A B Slot issues recovery... I was losing my mind trying to get things to flash and finally come to the conclusion...
3. Oreo 8.1.0 works with the flash-all bat (Google FACTORY image). The Oreo version will NOT relock your bootloader!!!
Click to expand...
Click to collapse
So can you not flash.all.bat 7.1 image and unlock bootloader if it's vzw pixel XL?
Bryanx86 said:
So can you not flash.all.bat 7.1 image and unlock bootloader if it's vzw pixel XL?
Click to expand...
Click to collapse
No you can't, because you can't flash until after you are unlocked.
I returned mine to Google and sweet talked my way into the one I have now. Still Verizon, but it was rolled back to 7.1.0.... Well and blue (my original was black). I'm not sure I could've kept the phone without actually being able to flash roms/kernels/themes. No matter who you are or what you do, the developers around android building are just remarkable at finding and fixing those little stutters and issues that drive us all nuts as well as adding those little goodies that make them fun and unique.
This was actually an argument I was having with the gentleman at Best Buy telling me the phones are all the same with the Pixel 2 a month or so ago. After a bit of discussion he also said I could immediately unlock these devices even on Verizon. I called him out and he proved it, but HAD to use an AT&T sim as the start up. Once VZW is booted past the 7.1.0 version, that it is unlockable... its over... unless someone else can find another unlocking method to downgrade without OEM unlock or a bootloader unlock method I don't know what to say. Personally I would've rolled back to the 6p or gone to the 2 and had the guy at Best Buy help me out with a sim.
This thread is so noob... Makes me cringe.
stebomurkn420 said:
This thread is so noob... Makes me cringe.
Click to expand...
Click to collapse
Come on man... Gotta help the cause... Everyone wants options and themes... Thats why we dont have IPhones.
Verizon users dont stand a chance at catching up or learning assuming they ever had a Pixel xl on NDE63P If they want to unlock, they need to start backing up to the 6P.... which is actually still a comparable device to newer phones at a couple years old.... and then they cant even go to the store to set it up... LOL. Sooooooo many posts from Verizon Users asking about whether they can update stock or via Google images and noone answers, well, mostly because their in the wrong thread.
And yes I realize I answered the last question asked, in the original post. I still have a little patience in my old age...
NO you can not flash down to 7.1.0 because you cant run the Google img through Fastboot, without being unlocked and there is NOWAY currently to unlock, past the original build version... I believe the last unlockable was NDE63X (dont quote me on that) Sorry guys. You CAN HOWEVER flashall.bat if you are ALREADY unlocked and you will stay bootloader unlocked.
stebomurkn420 said:
This thread is so noob... Makes me cringe.
Click to expand...
Click to collapse
Come on man... Gotta help the cause... Everyone wants options and themes... Thats why we dont have IPhones.
Verizon users dont stand a chance at catching up or learning assuming they ever had a Pixel xl on NDE63P If they want to unlock, they need to start backing up to the 6P.... which is actually still a comparable device to newer phones at a couple years old.... and then they cant even go to the store to set it up... LOL. Sooooooo many posts from Verizon Users asking about whether they can update stock or via Google images and noone answers, well, mostly because their in the wrong thread.
And yes I realize I answered the last question asked,...well most in the original post. I still have a little patience in my old age...
NO you can not flash down to 7.1.0 because you cant run the Google img through Fastboot, without being unlocked and there is NOWAY currently to unlock, past the original build version... I believe the last unlockable was NDE63X (dont quote me on that) Sorry guys. You CAN HOWEVER flashall.bat if you are ALREADY unlocked and you will stay bootloader unlocked.
Hi All
can i flash the following firmware on my ZTE Axon Mini - It was purchased from Gearbest
https://www.ztemobile.de/support/downloads/?product_id=2344
current version is 6.0
many thanks
if yours Mini is G version and you live in europe - then yes.
Tommixoft said:
if yours Mini is G version and you live in europe - then yes.
Click to expand...
Click to collapse
done with the gearbest B2017G, update to 7,1,1 , but I can't go in bootloader mode to root
Diomorgan said:
done with the gearbest B2017G, update to 7,1,1 , but I can't go in bootloader mode to root
Click to expand...
Click to collapse
Next time read before doing With 7.1 there is no longer bootloader mode. Downgrade to 6. Also you dont need to unlock it, there is no better ROMs for this rom. Official one is best. I tried them, so you can save time and use official one.
ALso root not working well with it. I had root but somehow i couldn't delete system apps.
Tommixoft said:
if yours Mini is G version and you live in europe - then yes.
Click to expand...
Click to collapse
Sorry if I'm hijacking this thread, if so, I can start another.
I recently purchased this phone (B2017G) from Gearbest as well.
It is still on 6.0.1 Marshmallow.
I have been searching for the right update file, starting with the US version, since that is where I live, but no go. The bootloader says
"E footer is wrong
"E:signature verification failed
"E: open file /cache/fota/error_code error erno = 2
'Installation aborted'
Am I right in thinking I need to find the update with the right signature? I have tried US, Austrian and Russian official ZTE updates with no success so far.. Am I on the right track?
US ZTE Support was as helpful as they could be, but were not familiar with the GearBest global variant. They sent me to the global support site, which won't let me use it, since I'm from the US, lol
Any suggestions? I'm going to try the German update from earlier in this thread after I get home tonight, by the way...
I also purchased mine from Gearbest (B2017G). I believe the phone is for the European market as it comes with a EU plug in the sealed box, but not sure for which country. I tried the firmware for the Spanish model http://www.ztedevice.com/support/detail?id=D4454D33442F45E192A95718509F4586. The update failed.
I just flashed the Nougat 7.1.1 an hour ago from here:
https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13.
It already looks promising - the phone is very cool after update. Previously the phone is always warm, even in standby. I hope the battery life is a big improvement.
If you intend to flash this zip file, make sure your phone is a European model B2017G. As posted before I got this phone from Gearbest as many others.
Hi,
Updated to 7.1.1 by OTA 3 weeks ago when i bought the phone from Amazon.
It seems that we'll get Oréo later...amazing ! thks ZTE !
It is not official that Axon 7 Mini (B2017G) will get Android 8 aka Oreo. ZTE should do the update to Oreo as this is one popular phone still.
reticuli said:
It is not official that Axon 7 Mini (B2017G) will get Android 8 aka Oreo. ZTE should do the update to Oreo as this is one popular phone still.
Click to expand...
Click to collapse
In a chat with ZTE USA assistance last week, the tech mentioned that Oreo will be rolling out for the Axon 7 Mini in the US.
afigienas said:
Next time read before doing With 7.1 there is no longer bootloader mode. Downgrade to 6. Also you dont need to unlock it, there is no better ROMs for this rom. Official one is best. I tried them, so you can save time and use official one.
ALso root not working well with it. I had root but somehow i couldn't delete system apps.
Click to expand...
Click to collapse
Once you downgraded and rooted can you upgrade back and keep the root?
Root is needed for this phone because it doesn't allow to move ANY app to SD.I sort of recovered the backup of my apps and data with Helium without root, but I need more internal space: with root you can even enable adoptable storage.
If only we can get access bootloader and flash modified boot.bin with magisk...
At the moment I can only use it as backup phone, my everyday phone LG G5 has 7gigs of whatsapp stuff that can only be internal, but most part of the 130+ apps I got are shared in the SD card.
I don't even need TWRP actually, just root to move apps to SD (or a firmware that allows it, since it's a firmware option...ZTE decision)
Flashing nougat 7.1.1 is the best thing I've done - it basically fixed the battery drain. I had to charge 3 times a day before the update. Last night the battery was only down 3%. This morning I recharged it to 93% before I left for work. At 5pm after a days normal use, it still had 55% left. It's just amazing. I think the update flashed out all the nastiest including the suspicious apps that come with the phone. I have no idea what they are - 99003, 99033, 99035 and more. I suspect they are malware although I cant be sure. They consume battery and keep the phone awake. The phone was warm even in standby.
priority1 said:
Flashing nougat 7.1.1 is the best thing I've done - it basically fixed the battery drain. I had to charge 3 times a day before the update. Last night the battery was only down 3%. This morning I recharged it to 93% before I left for work. At 5pm after a days normal use, it still had 55% left. It's just amazing. I think the update flashed out all the nastiest including the suspicious apps that come with the phone. I have no idea what they are - 99003, 99033, 99035 and more. I suspect they are malware although I cant be sure. They consume battery and keep the phone awake. The phone was warm even in standby.
Click to expand...
Click to collapse
you mean the stock one or a custom 7.1.1 ?
Diomorgan said:
you mean the stock one or a custom 7.1.1 ?
Click to expand...
Click to collapse
Stock one
Got the 7.1.1 update...
... in a round-about way. Went here http://www.ztedevice.com/support/detail?id=6CCC18CC9451416C8A01BED5174B5762#software and it downgraded my phone to a December 2016 security update.
Flashed the Russian 6.0.1, (had to use the bootloader method for both), then was able to run the Spanish update from ZTE, directly from the System updates menu after extracting the 'update.zip' file from the package and placing it in the root of the SD.
Now running 7.1.1 and happy. I can still access AT&T's US network perfectly, so I didn't destroy the usefulness of my new phone as a phone.
I may eventually put a second T-Mobile sim in it if I think I can live without the SD card's storage...
Edit: I am running a GearBest-purchased phone with 'global' firmware, meaning no official updates available. It is possible that I could have tried to use the Spanish 7.1.1 directly, but I didn't try that before taking the route I did. Just happy *something* worked!
Still no root? Even a firmware where I can patch boot.img with magisk and repack and flash?
I did it with Ulefone S8Pro, but because someone here posted the firmware and it was editable and flashable without getting errors! No TWRP, but who cares, I have adoptable storage and Is essential with those "low" internal memory phones....
A ZTE moderator on the official US site has disconfirmed my report of Oreo on Axon 7 Mini:
"sshasan Z-Community Moderator New YorkPosts: 3,409Z › admin
April 2, 2018 5:40PM
No announcements have been made at this time. If a representative has stated this, they have misspoken."
Click to expand...
Click to collapse
Please disregard my earlier reporting. Although my report was accurate as far as what I had heard, the rep I chatted with was likely mistaken.