Database Users

[q] lg g2 320l korean version now in uk

I am requesting assistance with basic development of the Korean 320L Variant of this device. I chose it due to the removable battery and 64gb micro sd card capability over the standard version available here in the uk.
I have achieved Root which is excellent but would like a CWM/TWRP based recovery if this is possible. I have tried the Korean Telecom 320k version to no avail.
Any help or guidance would be appreciated, I have already looked at the existing threads for answers but I see none (I may be missing something!)

jody04c said:
I am requesting assistance with basic development of the Korean 320L Variant of this device. I chose it due to the removable battery and 64gb micro sd card capability over the standard version available here in the uk.
I have achieved Root which is excellent but would like a CWM/TWRP based recovery if this is possible. I have tried the Korean Telecom 320k version to no avail.
Any help or guidance would be appreciated, I have already looked at the existing threads for answers but I see none (I may be missing something!)
Click to expand...
Click to collapse
I think i know what it might be.Did you update to the last OTA before you try the recovery?If the answer is yes then this is your problem,and you will need to revert back to stock to do so (and stay there until a new recovery img for the new rom arrives).

woof123 said:
I think i know what it might be.Did you update to the last OTA before you try the recovery?
Click to expand...
Click to collapse
I'm currently running JDQ39B / Software version F320l11C

jody04c said:
I'm currently running JDQ39B / Software version F320l11C
Click to expand...
Click to collapse
Yes then this is the problem it wont work for the latest version.

woof123 said:
Yes then this is the problem it wont work for the latest version.
Click to expand...
Click to collapse
BolloXXX to that! Thanks for the update though. I guess I will have to wait for a workaround.. Times like this makes me miss the simplicity of a Nexus and an unlocked bootloader.

jody04c said:
BolloXXX to that! Thanks for the update though. I guess I will have to wait for a workaround.. Times like this makes me miss the simplicity of a Nexus and an unlocked bootloader.
Click to expand...
Click to collapse
Its very easy to go back to another rom if you want,i did that with mine like 3-4 times already :good: You just need the rom and FlashTool.1.0.54.
They do have the K variant roms for download here:Btw S and L models are pretty much the same,mine is the S one but if i open it it says F320S/L.Even flashed it with the K software with no problems at all.
The latest that works is 10M
http://forum.xda-developers.com/showthread.php?t=2432476

Any LTE/4G on f320l in UK?
woof123 said:
Its very easy to go back to another rom if you want,i did that with mine like 3-4 times already :good: You just need the rom and FlashTool.1.0.54.
They do have the K variant roms for download here:Btw S and L models are pretty much the same,mine is the S one but if i open it it says F320S/L.Even flashed it with the K software with no problems at all.
The latest that works is 10M
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
Hi jody04c and woof123
I too have an f320l model. Have you managed to get this to work on UK LTE/4G connections? I have an EE 4G Sim but can only get 3G. Various people are saying different things.
The pda site says limited band support, but the 5457#*320# menu has LTE Band 3 and LTE Band 7 listed. The latest Korean manual for 4.4.2 OTA update now also lists Band 7 support in the manual too.
However, I notice that In Korea LGUPlus don't use these LTE bands (according to wikipedia) and so I was wondering if I should just root and try loading the K or S ROM which might open these up?
I have seen the return to Stock page - for me to use that, will I need to Root first? Any advice on rooting the Korean variants (sorry if this is listed elsewhere, I'm not a familar user here and often find several threads with different details/steps).
Thanks in advance for any help here.

mikeefreedom said:
Hi jody04c and woof123
I too have an f320l model. Have you managed to get this to work on UK LTE/4G connections? I have an EE 4G Sim but can only get 3G. Various people are saying different things.
The pda site says limited band support, but the 5457#*320# menu has LTE Band 3 and LTE Band 7 listed. The latest Korean manual for 4.4.2 OTA update now also lists Band 7 support in the manual too.
However, I notice that In Korea LGUPlus don't use these LTE bands (according to wikipedia) and so I was wondering if I should just root and try loading the K or S ROM which might open these up?
I have seen the return to Stock page - for me to use that, will I need to Root first? Any advice on rooting the Korean variants (sorry if this is listed elsewhere, I'm not a familar user here and often find several threads with different details/steps).
Thanks in advance for any help here.
Click to expand...
Click to collapse
So has anyone had success getting the f320l working on uk 4g by using stock/custom s/k rom. As suggested here hardware with s and l seem to be same or similar, and the l model is used by lugplus who don't support EU lte bands so probably block through their software, whereas skt on the f320s support bands on EU. The latest f320l ota update also says it supports band 7, but it didn't work with uk Ee for me with default settings.

Identifying Yotaphone 2 model (YD206/YD201) using its hardware information

Hello
I ordered a Yotaphone 2 YD201 from china not long ago, and after recieving it I decided to check the phone's details to make sure I'd received the right version.
Unfortunately, I had received a YD206, which won't work well with 4G networks in the UK.
I contacted the seller, and he assured me that the phone I have received is in fact a YD201, stating the following:
"a few yotaphone YD201 was reflashed to YD206 before sending , pls check the phone after delivery . If your phone is YD206 system , don't worry ,it just softwareproblem , the hardware is original YD201 , we can give you reflash rom and tutorial to reflash it back to original YD201 . It will be YD201 system and work with B3/B7/B20 4G net"
My question is; is there a way I can find whether the phone was originally a YD201, or if the version I have been sent is actually just a YD206?
Attached are some screenshots containing my device's info.
Any help would be much appreciated
Thank you
- Luke

Imei = 356... -> yd201
imei = 359... -> yd206

The difference between 206 and 201 are the radio bands supported.
To flash radio only:
fastboot flash modem radio\NON-HLOS.bin
fastboot flash sbl1 radio\sbl1.mbn
fastboot flash rpm radio\rpm.mbn
fastboot flash tz radio\tz.mbn
The chinese model is compatible with 1800Mhz LTE band, that is used in some contries in Europe also,
On the phone dialer if you insert *#06# it will show the phone IMEI.
The I.M.E.I. stands for International Mobile Equipment Identity and is specific for each country,
IMEI numbers starting with 359 will be Chinese YD206, if this is your case, then you must flash the Chinese Radio even if you use other location ROM, the correct installed radio will give you better battery life and network speed.
Keep in mind that the Information on Android -> About the phone -> Model: YD201 or YD206 is not accurate because it gets its information from the ROM and not from the hardware.

Thanks for the help

Tippfehler said:
Imei = 356... -> yd201
imei = 359... -> yd206
Click to expand...
Click to collapse
Good! Looks like my phone was originally a YD201 after all, thank you!

Luke25361 said:
Good! Looks like my phone was originally a YD201 after all, thank you!
Click to expand...
Click to collapse
Hi. I'm sitting with the same dilemma... I received the same explanation from Geeks Planet Store, word for word.
I do not even understand why they would even consider re-fashing something with a higher value (YD201) with the software that would make it look like something of lower value (YD206).
Anyway in your screenshot it says Baseband version ..._CN1_M05. Does this mean it uses the CN radio firmware?
I also downloaded their suggested firmware from the link they sent. In that there are no files under the radio folder. Does that mean the radio firmware is supposed to stay unchanged in this case? If so and if baseband _CN1_ means it is currently running CN radio firmware, does this mean the hardware is really YD206?
One more question: how reliable is the imei number check?
To me the best approach seems to be the suggestion by cvzalez to really test the radio with different firmware and see what works.

JJNNTT said:
Hi. I'm sitting with the same dilemma... I received the same explanation from Geeks Planet Store, word for word.
I do not even understand why they would even consider re-fashing something with a higher value (YD201) with the software that would make it look like something of lower value (YD206).
Anyway in your screenshot it says Baseband version ..._CN1_M05. Does this mean it uses the CN radio firmware?
I also downloaded their suggested firmware from the link they sent. In that there are no files under the radio folder. Does that mean the radio firmware is supposed to stay unchanged in this case? If so and if baseband _CN1_ means it is currently running CN radio firmware, does this mean the hardware is really YD206?
One more question: how reliable is the imei number check?
To me the best approach seems to be the suggestion by cvzalez to really test the radio with different firmware and see what works.
Click to expand...
Click to collapse
I'm confused too as to why they would re-flash a YD201 to a YD206. It doesn't make any sense.
According to this guide, the 'S01_003_3034_CN1_M05' baseband that we have is the one used by YD201s that's supposed to work with all available frequency bands. The reason for the radio folder being empty is so that flashing the phone leaves this baseband as it is.
As for the imei number, after a bit of research I've found that changing this number is relatively easy (even without root), so it's possible that Geeks Planet have just changed the imei number to make our phones seem like YD201s. However, it wouldn't make sense for them to do this and to not also flash the firmware to YD201 as well.
Have you tried flashing the phone to the YD201 using the instructions they've given you? I'm wondering whether or not to try this myself.

Luke25361 said:
Have you tried flashing the phone to the YD201 using the instructions they've given you? I'm wondering whether or not to try this myself.
Click to expand...
Click to collapse
I have not received the phone yet. Even though I ordered it a very long time ago, it was only sent after the Chinese new year holiday.
I am seriously considering not accepting the delivery...
---------- Post added at 11:22 AM ---------- Previous post was at 11:16 AM ----------
Luke25361 said:
According to this guide, the 'S01_003_3034_CN1_M05' baseband that we have is the one used by YD201s that's supposed to work with all available frequency bands.
Click to expand...
Click to collapse
I might be wrong or blind, but when I look it says: "YD206 users have to change their modem components to CN version, in order to have all the available bands working. The modem version is written in "About Phone", under "baseband version". You must have the S01_003_3034_CN1_M05 version. "

JJNNTT said:
I have not received the phone yet. Even though I ordered it a very long time ago, it was only sent after the Chinese new year holiday.
I am seriously considering not accepting the delivery...
Click to expand...
Click to collapse
I've asked the supplier if they can give me any assurance that they would help me out should I follow their flashing instructions and the phone be damaged as a result.
If they can give me this assurance, then I'll give it a go and give you the results.
Reading the comments on the youtube video Geeks Planet have sent me, it seems like this problem isn't exclusive to just Geeks Planet and is rather an issue with the main supplier of these YD201s. The comments state that both coolicool and e-fox have sold people phones with the same issue and have been linked to this same video.

JJNNTT said:
I might be wrong or blind, but when I look it says: "YD206 users have to change their modem components to CN version, in order to have all the available bands working. The modem version is written in "About Phone", under "baseband version". You must have the S01_003_3034_CN1_M05 version. "
Click to expand...
Click to collapse
The wording of this section is a little difficult to interpret. It's not really clear if baseband 'S01_003_3034_CN1_M05' is the original baseband or the international baseband.

Luke25361 said:
The wording of this section is a little difficult to interpret. It's not really clear if baseband 'S01_003_3034_CN1_M05' is the original baseband or the international baseband.
Click to expand...
Click to collapse
If I look at:
S01_003_3034_RU1_M11_P2 : 4.4.3-S01-003-APC.0.3.56C ; 4.4.3-S01-003-HK1.0.3.56A ; 4.4.3-S01-003-EU1.0.3.56A; 4.4.3-S01-003-RU1.0.3.56A
S01_003_3034_RU1_M15_P2 : 4.4.3-S01-003-EU1.0.3.61A ; 4.4.3-S01-003-HK1.0.3.61A ; 4.4.3-S01-003-ME1.0.3.61A
S01_003_4240_RU1_M05 : 5.0.0-APC.1.65 ; 5.0.0-RU.1.1.112 ; 5.0.0-HK.1.1.66
S01_003_4240_RU1_M04 : 5.0.0-APC.1.44; 5.0.0-EU.1.1.39 ; 5.0.0.-ME.1.1.45
S01_003_3034_CN1_M05 : in every CN firmware, in the oldest there's the 3032 version.
Click to expand...
Click to collapse
It really looks like _RU1_ is for RU, APC, HK, EU, ME
and
_CN1_ is only for CN
(So YD206 needs _CN1_ ?)

Guys, you're lucky! You've a YD201, it doesn't matter if the firmware inside is from YD206, it can be easily changed looking at the guide you already linked.
The fact that they flashed a firmware for 206 to a 201 is because their phones are suited for Chinese market.
All you have to do is to flash the RU version (including its radio folder) and see that all LTE bands will be working as expected on a YD201!
Changing IMEI is possible, but not simple. And if your IMEI in "About phone" is the same on that written on the package of YotaPhone, you're good to go.
IMEI checking is the most reliable way to understand if it's a YD201 or YD206.

TheArt. said:
Changing IMEI is possible, but not simple. And if your IMEI in "About phone" is the same on that written on the package of YotaPhone, you're good to go.
IMEI checking is the most reliable way to understand if it's a YD201 or YD206.
Click to expand...
Click to collapse
Chinese can easily print a new IMEI on the box

TheArt. said:
Guys, you're lucky! You've a YD201, it doesn't matter if the firmware inside is from YD206, it can be easily changed looking at the guide you already linked.
The fact that they flashed a firmware for 206 to a 201 is because their phones are suited for Chinese market.
All you have to do is to flash the RU version (including its radio folder) and see that all LTE bands will be working as expected on a YD201!
Changing IMEI is possible, but not simple. And if your IMEI in "About phone" is the same on that written on the package of YotaPhone, you're good to go.
IMEI checking is the most reliable way to understand if it's a YD201 or YD206.
Click to expand...
Click to collapse
Thank you for the clarification
I've been sent this reflash rom by the supplier. Would you recommend I use this or use the one on the yota website?

Luke25361 said:
Thank you for the clarification
I've been sent this reflash rom by the supplier. Would you recommend I use this or use the one on the yota website?
Click to expand...
Click to collapse
The one on Yota ftp site are official. I don't know if the firmware the seller sent to you is modified or they just downloaded it via ftp, repacked and sent to you. The firmware version is invisible looking at the files, first you have to flash it and them you will see which version it is.
Personally I would flash only official firmwares.

TheArt. said:
The one on Yota ftp site are official. I don't know if the firmware the seller sent to you is modified or they just downloaded it via ftp, repacked and sent to you. The firmware version is invisible looking at the files, first you have to flash it and them you will see which version it is.
Personally I would flash only official firmwares.
Click to expand...
Click to collapse
Ok, I've decided to try and flash using one of the official firmwares.
If I were to flash to one of the RU firmwares, which one of them would I need to use?

Luke25361 said:
Ok, I've decided to try and flash using one of the official firmwares.
If I were to flash to one of the RU firmwares, which one of them would I need to use?
Click to expand...
Click to collapse
In this guide this information is already written down, anyway use the latest which is: 5.0.0-RU1.1.124.zip.
Let us know which version of firmware and baseband is the ROM the seller provided you!

Luke25361 said:
Ok, I've decided to try and flash using one of the official firmwares.
Click to expand...
Click to collapse
Did it work? Could you test the LTE capabilities with the RU base band?

TheArt. said:
In this guide this information is already written down, anyway use the latest which is: 5.0.0-RU1.1.124.zip.
Let us know which version of firmware and baseband is the ROM the seller provided you!
Click to expand...
Click to collapse
JJNNTT said:
Did it work? Could you test the LTE capabilities with the RU base band?
Click to expand...
Click to collapse
I've managed to flash the phone using the firmware the seller provided. I have also managed to install an OTA update.
I've attached a screenshot with the new device details.
Is this the correct version that I should be on now?

Luke25361 said:
I've managed to flash the phone using the firmware the seller provided. I have also managed to install an OTA update.
I've attached a screenshot with the new device details.
Click to expand...
Click to collapse
At least the baseband changed... which I guess is a good sign. For me now the big question is: Does LTE B20 work? (That is what I need where I live.)

New A2017G hardware?

My recently bought (Feb 2017) Axon 7 has a firmware that is unusual.
The phone name: ZTE A2017_7383
Model number: ZTE A2017G
Android Version: 6.01
Android Security patch level: December 1, 2016
Baseband version
M8996FAAAANAZM-1.68528.1.71127.1
Kernel version: 3.18.20
Build number: ZTE A2017GV2.0.0B08
Note that the build number is a V2.0.0B08
This phone is incompatible with the A2017GV1.0.0B05 and A2017GV1.0.0B10, so beware. I semi-bricked my phone (no network connectivity anymore) and I can't find a replacement A2017GV2.0 software.
I contacted ZTE, but no reply yet.
The reason I upgraded was due to inability to connect to 4G or LTE networks, even though my provider is on LTE band 3 and band 7.
Can anyone help me with this problem?

I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?

laicc said:
I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?
Click to expand...
Click to collapse
The A2017 is the chinese version...you can check this link to get the latest nougat update.....100% working
https://forum.xda-developers.com/axon-7/how-to/a2017-nougat-twrp-flashable-djkuz-t3571714

laicc said:
I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?
Click to expand...
Click to collapse
as far as I know A2017 variant doesn't have capacitive keys under the screen, so you would notice it right away. My sticker does spell "Model: A2017G" though. Have you made sure that the IMEI numbers written on the sticker match with your phone actual IMEI numbers too? (to be sure it's not a sticker issue)

laicc said:
I looked at the back of the phone, where the original stickers still haven't been removed. It says ZTE A2017, without the "G". Could this be a Chinese set and the supplier reflashed it with a modified B08 firmware?
Anyone has a phone with the sticker not yet removed and has a different model number? I need proof that this is not the international version.
Would a Chinese version work on a "G" version software?
Click to expand...
Click to collapse
USA (U) & International (G) = Hardware keys.
Chinese = No Hardware keys , and uses On-screen Navigation keys.
About the V2, that's something else.... Need further findings thought.

DrakenFX said:
USA (U) & International (G) = Hardware keys.
Chinese = No Hardware keys , and uses On-screen Navigation keys.
About the V2, that's something else.... Need further findings thought.
Click to expand...
Click to collapse
About the Chinese version, the 64GB model doesn't have hardware keys, that's right, but the 128GB version does. I have one.

Thanks everyone, just to close this issue, for the benefit of everyone, my discussions with the Ebay seller revealed that the handset is actually an A2017 Chinese set, and reflashed with their custom ROM to emulate an A2017G. Thats why it didn't work very well, and practically cannot be OTA'ed or updated.
This same message has been cross posted to [A2017G] B10 Update Released 1 2 3
Thread by rikin93
So sorry if I repeat myself here, but I just wanted everyone to know that the issue is closed.

I have the same issue, So how did you manage to solve it? did you flash the Chinese version? (A2017) if so how?
or did you ask the seller for the custom ROM to flash it back to that?
thank you

dude215p said:
I have the same issue, So how did you manage to solve it? did you flash the Chinese version? (A2017) if so how?
or did you ask the seller for the custom ROM to flash it back to that?
thank you
Click to expand...
Click to collapse
I had looked at the various options available here on this XDA site, like flashing back to the stock Chinese A2017 rom, or converting it to an A2017U, but in the end, I didn't think it was worth the trouble, and could even make the problem worse.
They did mention that their supplier has the custom rom, and he could probably get it for me. But that means I will be stuck with that rom forever with no possibility of an OTA.
I eventually convinced the Ebay seller to accept the return for a full refund.
Hope this helps.

laicc said:
I had looked at the various options available here on this XDA site, like flashing back to the stock Chinese A2017 rom, or converting it to an A2017U, but in the end, I didn't think it was worth the trouble, and could even make the problem worse.
They did mention that their supplier has the custom rom, and he could probably get it for me. But that means I will be stuck with that rom forever with no possibility of an OTA.
I eventually convinced the Ebay seller to accept the return for a full refund.
Hope this helps.
Click to expand...
Click to collapse
Hey, thank you for sharing,
I decided to do the opposite, and dived into getting my phone in working condition by flashing the chinese rom on it, although I never done anything like this before. I think I'll make a noob's guide to it, because while there are a lot of good tutorials out there, there are a lot of details kind of glossed over on how to do certain small steps, and you'll have to search for other guides on how that particular step is done.
For now let's just say that I'm happily running Nougat 7.1 with the Google Now launcher, and Google stock apps.

dude215p said:
Hey, thank you for sharing,
I decided to do the opposite, and dived into getting my phone in working condition by flashing the chinese rom on it, although I never done anything like this before. I think I'll make a noob's guide to it, because while there are a lot of good tutorials out there, there are a lot of details kind of glossed over on how to do certain small steps, and you'll have to search for other guides on how that particular step is done.
For now let's just say that I'm happily running Nougat 7.1 with the Google Now launcher, and Google stock apps.
Click to expand...
Click to collapse
That's great. I would really like to know how you did it. Reading the forum, even with the fairly detailed instructions that have been posted, can be intimidating for noob's like us. Is your 4G working good now? Thanks in advance.

A2017G Japan to A2017G European/other A2017G ROMs

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!

A2017G Japan - Lots of Questions...

Okay, so I used to love rooting my phones, but I mostly dealt with flagship phones in the US which made rooting and flashing a cakewalk. I understand some of the nitty gritty, so when I got my first phone in Japan, I was super excited about rooting it. But after reading this forum for hours, I have so many questions...my phone build is A2017G JPV1.1.0B03.
I read this but this mostly focused on using an update on this phone.
https://forum.xda-developers.com/axon-7/help/a2017g-japan-to-a2017g-european-a2017g-t3608411
1. If that thread is correct, that means I technically just have the European version of the phone with Japanese modems installed. Is that correct?
2. Also, does that mean (if I were not to root the phone) I would need to install a European Axon 7 Oreo update for it to actually work on the phone? Would the US version fail?
3. I can't seem to find the modem for my phone. I can upload some screenshots later but can someone clarify if I'm right that it's a "B03" or am I looking at the wrong information?
4. There is no Oreo release for Japan, so does that mean I can't flash an Oreo ROM because there won't be any modems for this?
That's all for now, but I'm sure I have a lot of follow-up questions to your answers. Your help is greatly appreciated.

Unlock bootloader, install twrp, instal "G" model bootstack, instal any custom rom, then flash "G" modem in twrp, reboot. No matter where you device are from, the model matters. If its "G", its a european version and its only what you need to know. If you want stock oreo and didnt recieve through OTA, download the update in ZTE website for your "G" version, put it in a sdcard then reboot your phone to recovey then select "install update from sd card" option.

Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.

RobboW said:
Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.
Click to expand...
Click to collapse
I'm so used to dealing with multiple modems for the same model of phone in the US (between the major carriers and stuff) that I was overthinking it.
Thanks a ton. That simplifies things so much...and also makes me wonder why updating never occurred for the Japanese release. It's not like there isn't language support for newer versions of Android, but maybe not for the MIUI? I need to be more careful choosing my next phone then, though probably it should be an AOSP phone like the Zenfone or Pixel.
Guess I have my work cut out for me this weekend. Time to run a giant backup and start rooting. Thanks again for all your help. I like this phone (though I often accidentally hover/touch the home button when typing, and I hope there's a sensitivity fix for that :laugh so I want it to last for a while before I get my next one.

It's still a good phone, I look at new phones and think, hmmm, nice, but what will I gain on a daily basis? Nothing more to be honest. The A7 has enough power for me still. The one thing I could really use would be a higher capacity battery. Was looking at Huawei phones but now, well.....
For updates, they had issues with OTA and reverted to only releasing for a whole ROM download for update from SD card.
I personally won't apply an OTA for mine even now at Oreo. Must be a whole ROM to flash with the updater. That's all I've done with it since purchase and it works great still. A lot of people seem to have all sorts of weird issues after applying OTA updates.

Sweet. As someone with some experience with this stuff, do you have any tips or tricks I should know moving forward? I'm going to try rooting it tonight.
-EDIT: Quick little question, my phone says the Android version is 7.1.1 but that would be Nougat, right? Or is it actually Marshmellow?

7.1.1 yeah, Nougat. That doesn't make sense from your first post.
Was it used when you got it or new? Have you checked the model from what's on the back of it, not what software says it is?
I keep mine stock, can't advise on rooting etc. I use it with personal and work SIMs and it has to pass requirements including encryption to run Microsoft InTune and our company portal and use it in work mode. Bootloader hasn't even been unlocked. The most I did was uninstall some built in user apps through ADB.

I also have a 2017G bought in Japan. I unlocked it and worked on it based on this forum, and I can say that it behaves as any other 2017G. I am not interested to use the stock ROM, but yes, I remember that it was on Nougat version when I received it.

I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.

darth_antz said:
I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.
Click to expand...
Click to collapse
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:

The Zenphone 6 is looking a viable buy now.
My Axon 7 is still good so not really looking but I did just get a new Axon 7 Mini for use as a media player. It still has AMOLED screen, stereo speakers, headphone jack, DAC for the jack etc. No hi res bluetooth though. Cost me AU$149 new in box from retail store. Bargain! How much is a dedicated music player which is crap at movies or just cant do them?
Chucked my 128Gb SD in. Sounds good playing through the car hifi, lower 3.5 jack output matches HU aux in impedance better than Axon 7 which can overload the input at high volume. Very balanced and clean sound.

TheZen said:
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:
Click to expand...
Click to collapse
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!

darth_antz said:
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!
Click to expand...
Click to collapse
I bought it at Rakuten Mobile. There was a super sale and it was like 80% off, lol.
I tried using the guide over the last couple of days and no matter what I've done, I can't seem to get to recovery after doing the flashing (step 9). I was able to flash a stock image back on, but then when I try again it's the same results. I'm at a loss as to why but...there's another guide using the Axon7Tool.
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
The downside is that I work two jobs tomorrow so I won't have time to try this new one out but I think I downloaded everything already. This is kinda frustrating though..
-EDIT: I used the unbricking guide to EDL flash the B10 Nougat and it is a different experience than what I had before...geez, seems the Japanese version was severely neglected. If I run into problems with the other guide I feel comfortable EDL flashing Oreo. Really appreciate the support guys, let me know what you think. Before I started this, my battery was lasting barely 8 hours with only LINE and Chrome being the main background apps...

Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on

GeoffUK said:
Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on
Click to expand...
Click to collapse
you can't. There are 3 modem variants by region (US, china, global) and many versions for each, but they are not interchangeable and flashing another has already wiped some IMEIs long ago (doesn't always happen though)