Related
Hi!
I am sorry if this has been asked here before. I'm fairly new to this kind of stuff.
So I'm a foreigner living in Japan. Due to the allure of local warranty, I decided to get the Axon 7 (A2017G JPV).
It has been months since the last Nougat update came to other A2017Gs but hasn't arrived on the A2017G JPV. So I thought, may be ZTE Japan was just taking a longer time, etc. So recently, I decided to contact customer support. And their answer was unclear at best. They were apparently still deciding if they would release a Nougat update for Axon 7.
So here's my question. Considering that my Axon 7 is also A2017G, is there a way for me to install the latest A2017G European ROM or any other A2017G Stock ROMs for that matter, without unlocking my bootloader and rooting? And get OTA updates from A2017G European? If so, can someone please kindly point me in the right direction, I'm getting a bit lost.
If that isn't possible, is there a way, to install the stock A2017G ROMs (aside from JPV) and then relock the bootloader afterwards?
Please help me. Thank you.
jjquinto said:
Hi!
I am sorry if this has been asked here before. I'm fairly new to this kind of stuff.
So I'm a foreigner living in Japan. Due to the allure of local warranty, I decided to get the Axon 7 (A2017G JPV).
It has been months since the last Nougat update came to other A2017Gs but hasn't arrived on the A2017G JPV. So I thought, may be ZTE Japan was just taking a longer time, etc. So recently, I decided to contact customer support. And their answer was unclear at best. They were apparently still deciding if they would release a Nougat update for Axon 7.
So here's my question. Considering that my Axon 7 is also A2017G, is there a way for me to install the latest A2017G European ROM or any other A2017G Stock ROMs for that matter, without unlocking my bootloader and rooting? And get OTA updates from A2017G European? If so, can someone please kindly point me in the right direction, I'm getting a bit lost.
If that isn't possible, is there a way, to install the stock A2017G ROMs (aside from JPV) and then relock the bootloader afterwards?
Please help me. Thank you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Absolutely no need to root.
Enjoy.
Hamburgle4 said:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Absolutely no need to root.
Enjoy.
Click to expand...
Click to collapse
Hi
Thank you for replying so quickly.
Please bear with me as I am still a bit confused.
The link you gave mo contains Factory Images for the A2017G, right? Therefore, I should just put the factory images (zip file), into the root directory of my SD Card, and update via settings (no need to unlock bootloader or root, right?)?
My A2017G (JPV) is now on A2017G JPV1.0.0B03.
Which factory image should I use?
Thank you very much.
*Deleted for apparent "madness"
Are you mad?!!! This won't work as the signature's don't match.
At best you end up with a failed update, at worst a brick...
ultramag69 said:
Are you mad?!!! This won't work as the signature's don't match.
At best you end up with a failed update, at worst a brick...
Click to expand...
Click to collapse
Now I'm scared. Haha
Do you have any advice on how I should proceed with this? Thank you very much.
Hamburgle4 said:
*Deleted for safety reasons.
Click to expand...
Click to collapse
Considering @ultramag69 said, do you think I should still proceed with this?
I don't think you have to the same radio firmware with all the G version out there.... If you dare to try it probably you will end up bricking your phone.... So don try. Unless you are sure can warranty claim it if it is briked
Unfortunately this region locking thing came in, sometimes it's different hardware for different regions but mostly it's to stop the grey import trade...
Due to this it is a requirement to unlock your bootloader if you want to flash other region/carrier roms, which again is a trial in itself...
If you do wish to try it, make sure you have a flashable version of your FULL stock rom, not an OTA - the difference is an OTA is a patch, usually of a few hundred Mb or so to update parts of your ROM, the full ROM is a stand-alone installation that will completely replace the current ROM.
Generally this will get you out of hot water but be aware this is also not 100% guarantee...
It will probably also delete all your data, back up first....
ultramag69 said:
Unfortunately this region locking thing came in, sometimes it's different hardware for different regions but mostly it's to stop the grey import trade...
Due to this it is a requirement to unlock your bootloader if you want to flash other region/carrier roms, which again is a trial in itself...
Click to expand...
Click to collapse
What I'm confused about is he's not asking to flash A2017A/U firmware (where region locking comes into play) on his device, only another country's A2017G fw so why would he need to unlock bootloader? It's still fw for the global model if I understand correctly.
Hamburgle4 said:
What I'm confused about is he's not asking to flash A2017A/U firmware (where region locking comes into play) on his device, only another country's A2017G fw so why would he need to unlock bootloader? It's still fw for the global model if I understand correctly.
Click to expand...
Click to collapse
I'm on your side - the modem file might be different, but since the hardware is the same, it should work. Maybe the modem file has improved signal stuff for Japan, but it's extremely improbable considering ZTE's craptastic devs...
Also, what could be the worst thing that could happen? Here are the possibilities:
- Works: enjoy
- Installation failed: Should fail before even changing files anyways
- Soft brick: get to recovery, download full update zip, install, wait for Nougat
- Hard brick: "I woke up this morning and it was off, doesn't boot anymore, I want a replacement"
And if the modem is too crappy you can always go back to Japan's firmware
I believe that the Japanese version is different from the other G versions, at least on the modem level. Japan uses some bands that are not used by any other country in the world, so unless ZTE Japan decided to release the G model knowing that it would have some connectivity issues on all Japanese carriers, the Japanese G model must have at least a different modem.
Bold = band is present in the global G model
KDDI: CDMA BC0 / BC6, LTE 1/11/18/41
NTT Docomo: UMTS 1/9/19, LTE 1/9/19/21/28
Softbank: UMTS 1/8/11, LTE 1/8/9/41
I kinda get what you're getting at after looking further into the models. Basing off the spec sheets, Amazon JP has the exact same A2017G TD-LTE with matching bands sold by ZTE. Whereas on the ZTE JP page, it instead matches the bands of something named Axon 7 TD-LTE JP (couldn't find model number, but sounds like OP's A2017G). This has over half the exact bands available on A2017G, additional UMTS bands 6 & 19 and one CA band.
I think someone in another thread previously mentioned about potential signal issues with the Axon 7 being sold in Spain after flashing DE fw. Looking at their spec sheet, it appears to have a few bands missing, may have additional bands, but it's hard to tell since only the frequencies are stated. Could just be anecdotal as you'd think with the greater range of frequencies, it shouldn't face those issues. Anyways this is a separate matter, and potentially an apples to oranges comparison.
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
jjquinto said:
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
Click to expand...
Click to collapse
Great to hear. Also vindicates my apparent "madness" lol.
Hamburgle4 said:
Great to hear. Also vindicates my apparent "madness" lol.
Click to expand...
Click to collapse
Yeah it was nonsense, they are both a2017Gs anyways
We're all a bit mad though, flashing stuff on a 400 dolar thingy...
ive got the A2017 Chinese, bought from aliexpress. Ive rooted and installed the twrp flashable B15 from @djkuz, but the nougat firmware is awful for my DoCoMo phone reception (in far regional Nagasaki). So i need a method to either flash the modem for A2017G (not sure which B# release), or wait for the next chinese firmware release and hope for the best. Any suggestions or experiences to improve my reception? Is it the modem?
Thanks for all the contributions to this thread, as it has got me in the right direction.
jjquinto said:
Thank you all for your advice and insights.
I figured, damn all worries, and just used the recovery mode to flash the update.zip.
Lo and behold, it was updated with seemingly no issue. Even tried if my mobile data would work properly. And it did.
Thanks everyone!
Click to expand...
Click to collapse
Hey I know this is an old thread but I thought I would poke in and add my feedback. I also live in Japan and have the A2017G. I bought it because it was the only phone on the market at the time that [supposedly] supported Google Daydream. Later I realized that only the US version actually worked with Daydream. Later on support was added to European ROMS (when upgraded to 7.1.1). But for some reason the Japanese ROM, despite being 7.1.1 would say 'Incompatible Phone', even when installed manually. I contacted ZTE's customer service, which was terrible; all they said was "we don't know when it will be supported". This was about a year ago, so this week I just got sick of waiting, found the German firmware (A2017G-N-B10), installed it and everything works fine. The radios have no issues, and I was able to download Daydream right from the marketplace.
Thanks for everyone who contributed to this thread!
Hi all,
I recently installed fRomFuture ROM, but being an idiot I didn’t take note of which brand it was...
The phone was purchased in the UK on the EE network, does anyone know which brand it will be?
I don’t have the box or the sticker on the back of the mobile.
At the moment in the About phone I have the following incorrect info
EMUI 3.1
Android version 5.1
Build Number NRD90M Test-keys
Model D189-L09
Any help or advice appreciated
Mike
The same things looking for solution.!
Mines C440 (current EE release is VTR-L09C440B171)
Edit:
Sorry, this is P10, not plus.
Hey guys,
So i have the canadian version of the mini, with the details as follows:
model number: ZTE B2017G
android version: 6.0.1
build number: ZTE B2017G+BELLV1.0.0B06
and I cant update it, ive downloaded the nougat update file from here: https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
and attempted to update it in system setting from sd card, but got the message: package mismatch installation aborted.
Update didnt work from recovery either. Any ideas on how to update it, or if its even possible? Thanks!!
talha746 said:
Hey guys,
So i have the canadian version of the mini, with the details as follows:
model number: ZTE B2017G
android version: 6.0.1
build number: ZTE B2017G+BELLV1.0.0B06
and I cant update it, ive downloaded the nougat update file from here: https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
and attempted to update it in system setting from sd card, but got the message: package mismatch installation aborted.
Update didnt work from recovery either. Any ideas on how to update it, or if its even possible? Thanks!!
Click to expand...
Click to collapse
Doesn't seem like it's updatable at this point in time.
Reached out to ZTE: No updates available. If there were to be it would be through bell/Virgin as it's specific build/firmware/model.
Reached out to Virgin, bell and PC mobile as well. If something interesting comes from it I will surely post.
parawizard said:
Doesn't seem like it's updatable at this point in time.
Reached out to ZTE: No updates available. If there were to be it would be through bell/Virgin as it's specific build/firmware/model.
Reached out to Virgin, bell and PC mobile as well. If something interesting comes from it I will surely post.
Click to expand...
Click to collapse
Cool, thanks man.
Btw, is the Bell/Virgin model rootable? So we can put custom rom on it? Would it be the same roms other models would use?
I know tdm is working on one atm (https://forum.xda-developers.com/axon-7-mini/development/recovery-twrp-7-1-unofficial-t3685339)
talha746 said:
Cool, thanks man.
Btw, is the Bell/Virgin model rootable? So we can put custom rom on it? Would it be the same roms other models would use?
I know tdm is working on one atm (https://forum.xda-developers.com/axon-7-mini/development/recovery-twrp-7-1-unofficial-t3685339)
Click to expand...
Click to collapse
I think it should be but I haven't tried yet as I am using this phone as my daily. Maybe if I grab another one.
I need help too with the canadian version. There is no option to activate the NFC...
lanautechdroid said:
I need help too with the canadian version. There is no option to activate the NFC...
Click to expand...
Click to collapse
I don't think this version has NFC. There is no mention of it anywhere.
https://www.ztedevices.ca/axon-cat/axon7mini.html
USA version does mention it.
https://www.zteusa.com/axon7mini/
I got the Axon 7 mini from PC Mobile as well. Looks like the Canadian mini is a variant P852A15H, without NFC.
Any idea how to get rid of the carrier name at the top right? SytemUI tuner doesn't seem to activate either.
The mini is really sleek and light! Haven't had the battery issues mentioned in reviews either. Wish we could update to N though.
For what it's worth, there may be some activity behind the scenes for a minor update to the Canadian Axon 7 Mini late this month.
If this individual is to be believed, it will be bug fixes and security patches ONLY. That is, it will NOT be an upgrade to Nougat; we'll still be stuck on Marshmallow. But at least we'd end up with a security patch newer than late-2016.
https://community.zteusa.com/discussion/comment/228993/#Comment_228993
I wonder if this method will work for Canadian version:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
fy0u1 said:
I wonder if this method will work for Canadian version:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
Click to expand...
Click to collapse
It's said somewhere in the ZTE section that someone tried it and bricked his phone.
zigonneux said:
if you read more posts, it's said somewhere that someone tried it and bricked his phone.
Click to expand...
Click to collapse
That was after I posted here
So, are there any news on rooting+custom ROM for this device?
Security patch today
Hi,
Just got ZTE B2017G_BELLV1.0.0B08 this morning ....
yergy said:
Hi,
Just got ZTE B2017G_BELLV1.0.0B08 this morning ....
Click to expand...
Click to collapse
Did it upgrade to Nougat? What version of Android is it on after the B08 update.
Bettaxis said:
Did it upgrade to Nougat? What version of Android is it on after the B08 update.
Click to expand...
Click to collapse
No nougat, still M, only security patch february 2018. Better than nothing
yergy said:
No nougat, still M, only security patch february 2018. Better than nothing
Click to expand...
Click to collapse
Confirmed. 105.67 MB download, the device stays on Marshmallow. It brings the device from the November 1, 2016 security patch to February 5, 2018.
This is the first OTA ever released for the Canadian variant. It would include fixes for some pretty high-profile vulnerabilities, such as Blueborne, Krack, and Spectre, so it's definitely welcome.
talha746 said:
I have the canadian version of the mini
Click to expand...
Click to collapse
Bettaxis said:
I got the Axon 7 mini from PC Mobile as well. Looks like the Canadian mini is a variant P852A15H, without NFC.
Click to expand...
Click to collapse
Can you please execute the following adb command and post your product name here?
Code:
adb devices -l
List of devices attached
... device product:P852A11 model:ZTE_B2017G device:tulip transport_id:1
The adb devices -l command lists the following properties: ro.product.name, ro.product.model and ro.product.device
Hint: I downloaded the latest ADB tool from https://developer.android.com/studio/releases/platform-tools.html#download
I just finished a live chat with a ZTE rep. I give him all informations he asked and he told me that he's submitting that info to R&D and they will get back to me within 5 - 6 business days with a package update.
My build number is ZTE B2017G_BELLV1.0.0B08
I don't keep my hope very high on this, but hey you never know ...
I'll post what comes out of this ...
yergy said:
I just finished a live chat with a ZTE rep. I give him all informations he asked and he told me that he's submitting that info to R&D and they will get back to me within 5 - 6 business days with a package update.
my build number is ZTE B2017G_BELLV1.0.0B08
I don't keep my hope very high on this, but hey you never know ...
.
Click to expand...
Click to collapse
good luck with that
The Canada-specific version of the Axon 7 Mini was not sold on the open market, but rather was sold as a bundle through one of Bell Canada's affiliates. (I am aware of it being sold through Virgin Mobile and PC Mobile.) As such, it is running a customized OS that was approved by Bell Canada. The Bell Canada-specific OS has always been visually distinct from the version of the OS that shipped on open-market versions of the Axon 7 Mini; in my opinion it appears quite a bit more similar to the vanilla Android experience, with the exception of the preinstalled Bell account management apps.
Unfortunately, because the phone was bundled through Bell Canada, that means that ZTE will also be obliged to get Bell Canada's approval of any OS updates that may be offered for the phone. We've already seen, with the patch that was released earlier this year, that the OS update path being approved by Bell Canada is following a very different track from what ZTE has been offering on the open market, and I don't expect to see that change any time soon.
And it really doen't matter if ZTE's engineering department is technically capable of offering Nougat or newer for this device. They'd still have to get it cleared by Bell Canada first before they could distribute it.
Hello guys. As I do not live in the USA, i do not have a AT&T SIM and my phone never got any updates. Initially, it was on baseband version G892AUCU1AQG4. Till recently, I was stuck in this version. I managed to update to G892AUCS2AQL1 using links from a Russian forum. But, the SS-G892AUCS2AQL1-to-S2ARA1-UP.zip is corrupted and so I cannot update beyond this. I would be highly thankful if anyone could help me find a working copy of this file.
Hi, so I got an AT&T Galaxy S10+ (SM-G975U) from the US and it was stuck at Android 10. I can't get any updates so I tried to flash a new firmware into my phone. The problem is, SamMobile doesn't provide AT&T firmwares for SM-G975U but other carriers like T-Mobile and Verizon is available. Can I use firmwares from other carriers for my AT&T phone?
Yes
I need help i own a S10 plus model SM-G975U AT&T variant, it runs android 10 with UI ver 2.5 I cant update the phone through its update options located in settings. I see new Android 12 Update have been released i want to update my phone can someone please tellme what CSC to use ? What PDA to use ? exactly which version of firmware should i install ? i know i am asking like a noob but please i really need some expert advise. P.S i dont know if my phone is unlocked or not ... how to check that either ? Moreover Expert Opinons be communicated to my email address which is: [email protected]
I would advise anyone looking to update not to update beyond Android 11. Android 12 has issues and not just on Samsung devices. You can download Android 11 for all US Variants here.
SM-G975U1_ACG_G975U1UES6GUG1_Android11_Full - FirmwareX
firmwarex.net