Database Users

Oppo Find 5 China users info!!

Well well for starters a device (find 5) purchased anywhere can become any version just by flashing a firmware.ie a European oppo find five can become a chinese find 5 by flashing the chinese firmware and it will get its OTA from China.(Got to love this idea).First the chinese system supports english and has way better battery usage than the international software.(Don't asked i tried both).It's draw-backs are no gapps and chinese bloatware are on it.U can take them off with titanium but there is not root.This thread is for future updates,rom,posting perhaps and all that comes out off oppo's mouth first.
-Root:Just flash this in recovery(to get into recovery power down device then hold vol- + pwr for 10s and choose option 4 to install file from sdcard)
-To get 3rd party and gapps widget service working:Download the newest gapps from goo.im and flash in cwm or twrp recovery(from here).The file above gives u gapps but doesnt enable widgets service.
Update 11/04/2013 Official chinese firmware download here.Put on ur sd card,go to settings OTA and local upgrade then choose it and hit wipe and let it do its thing!!
Project firefly here
More coming soon and till then hit thanks and enjoy the power of the find 5:good:
unboxing

Actually you are wrong, there are a bunch of differences between the Chinese and the International version..
Here's a short list (note that this was copied directly from the thread on oppoforums.com):
1: Packaging: International Find 5 comes with an entirely English packaging.
2: Certifications: International Find 5 will have, among others, CE and FCC certification, making it theoretically legal to own and use in
for instance the EU. This will be visible on the backside of Find 5.
3: Firmware: International Find 5 comes with International (EN) Firmware pre-installed. EN firmware can be installed onto other
versions of the Find 5. We're working on adding more languages to the firmware, which currently supports English, Chinese and
Russian.
4: Networking: Chinese Find 5 does not support the 1700 MHz band on 3G (used by T-mobile in the US).
5: Support: OPPO employees will not provide English language support for Chinese devices. You can however receive support from
the Ofan community here at OPPO Forums, or communicate in Chinese with our Chinese customer support agents.
6: Price: Since the Chinese Find 5 is likely resold by a seller making a profit, there is a high chance that the price will be higher than
the upcoming International version.
Several of these aren't that important or can be fixed by flashing a different rom but #4, #5 and #6 are very important.
I suggest buying ONLY from oppo stores, that would be the OPPO shop on amazon and http://www.oppostyle.com (under maintenance when I'm writing this). That way you have the support you should have for a fair price.

Jell0zz said:
Actually you are wrong, there are a bunch of differences between the Chinese and the International version..
Here's a short list (note that this was copied directly from the thread on oppoforums.com):
1: Packaging: International Find 5 comes with an entirely English packaging.
2: Certifications: International Find 5 will have, among others, CE and FCC certification, making it theoretically legal to own and use in
for instance the EU. This will be visible on the backside of Find 5.
3: Firmware: International Find 5 comes with International (EN) Firmware pre-installed. EN firmware can be installed onto other
versions of the Find 5. We're working on adding ....
Click to expand...
Click to collapse
I know and I never said they were the same just said u can choose your side by choosing your firmware which I love BTW.And for the 3g support for the US bands I think that's neat.I'm here to inspiring a community for custom roms with ports of advantages from both sides.That's all!Thanks for the info.We'll need it along the line.:good:

hackarchive said:
I know and I never said they were the same just said u can choose your side by choosing your firmware which I love BTW.And for the 3g support for the US bands I think that's neat.I'm here to inspiring a community for custom roms with ports of advantages from both sides.That's all!Thanks for the info.We'll need it along the line.:good:
Click to expand...
Click to collapse
I have been very much looking forward to CM10.1

hiapk0percy said:
I have been very much looking forward to CM10.1
Click to expand...
Click to collapse
There is this thread in the dev forums for that and the guy developing it is doing a great job so far!!Lets hope he pulls everything together as the source is out!!

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!

Frankenstein device

Hello everyone
I had Note 4 with Exynos chipset (N910C) with no brand (European version).
After some issues with LTE connections and SIM card recognition I have bought used N910F motherboard and installed in my device.
First boot shows that motherboard is from Italy device with Wind operator applications installed.
Next I flashed device but forgot to record IMEI, modem version and bootloader version.
I have restored device using Samsung Kies and during restore process Kies reported device as:
PDA: QG3
CSC: QG1
PHONE: QA1
After restore system setting shows:
Model: N910F
Modem: N910FXXS1DQA1
Version number: MMB29M.N910FXXU1DQG3
1) Now I have a problem: should I use TRLTE roms or TRLTEXX?
When I put "Note 4" in TWRP website search it suggest "Samsung Galaxy Note 4 Qualcomm (trlte)" - so it is TRLTE device?
On the other hand most of N910F images are tagged as TRLTEXX.
2) Can I mix TRLTE TWRP with TRLTEXX ROM image (and vice versa) or they should always match?
3) I have tested few roms and faced problems with not working camera. I know that latest official Android version for Note 4 was Android 6.1
and most roms (RR, Lineage) are based on Android 7.1 If this is the reason of problems? Because official Samsung kernel with working camera
supports Android up to version 6.1 and customs kernel used in 7.1 have some camera issues?
4) What is the relation between kernel version and Android versions? Its like Android 6.1 requires kernel 3.x.x and Android 7.1 requires for example versions never than 4.x.x etc?
I will be thankful for answers to my questions. I know that they may be naive for experienced users but I try to good understand the process,
rather than blind flash roms until device will work.

Your device is basically n910f now. You should use twrp and roms for n910f

Your camera is nonfunctional because Exynos based units use Samsung's ISOCELL modules, and Snapdragon devices use Sony's image sensors. Your network connectivity should be gone as well for that reason.

neondragon1909 said:
Your device is basically n910f now. You should use twrp and roms for n910f
Click to expand...
Click to collapse
Ok, but still, if it is TRLTE or TRLTEXX because both tags comes with N910F roms.

oddbehreif said:
Your camera is nonfunctional because Exynos based units use Samsung's ISOCELL modules, and Snapdragon devices use Sony's image sensors. Your network connectivity should be gone as well for that reason.
Click to expand...
Click to collapse
By network connectivity You mean that antena design is also different and will cause signal loss?
I forgot to mention that I have also switched front and back camera to used ones from N910F.
From original N910C only body, USB port and scrren left.

elKoniu said:
By network connectivity You mean that antena design is also different and will cause signal loss?
I forgot to mention that I have also switched front and back camera to used ones from N910F.
From original N910C only body, USB port and scrren left.
Click to expand...
Click to collapse
Precisely. If you replaced those too, you should have no issues
Questions 1 and 2: Both use Snapdragon chips. Trltexx is the unlocked international N910F, while the other one is usually sold by carriers (T-mobile, AT&T and the likes). You should be able to mix 'em with no issues.
3: To get devices working on non-OEM firmwares without direct support from official drivers, developers write bundles of code called SHIMs. The camera is one such device, and because in most cases the driver is based on the manufacturer's own proprietary code, it's usually with blood and tears that our dear devs are able to get everything working even as it is. That's why you may face almost-working equipment with AOSP ROMs. You can read more about SHIMs here.
4: "If it ain't broken, don't fix it" applies here. There's no direct correlation between Android versions and which kernel versions they use, and manufacturers are sometimes slow to move to a higher version number because of how little meaningful improvements it brings. Recently, Google has mandated that all devices shipping with a SoC manufactured in 2017 or later must come with kernel version 4.4
Hope this clears things up. Anyone is welcome to correct if anything I've said is in the slightest incorrect. :angel:
Cheers,
-odd