It happened this morning, I started the GO4 app as usual, enter the aircraft and...Suddenly a window popped up saying "a mainland China phone number is required to complete the DJI GO varification process"
It wouldn't let me close that window unless I give a Mainland China number...
Is this normal since I don't live in mainland China?

Make sure you do not have the "use China map" selected in settings.

Hi, did you fly in mainland China before?
What's the ip address of the network? Please find the note from your mobile device. Here is the path : DJI/dji.go.v4/log/CACHE/verphone

Thanks Mindy,
How do I type the path in the iPad?
I live in Hong Kong, took it to Europe but never mainland China.  Never been locked down before.
I have a sim card(Mainland China roaming enable) in the iPad mini, maybe that is the reason why?
So I need to have a mainland Chinese phone number in order to fly in mainland China?

fans2a3ea1c6 Posted at 2017-5-10 20:05
Thanks Mindy,
How do I type the path in the iPad?
I live in Hong Kong, took it to Europe but never mainland China.  Never been locked down before.

That maybe the reason. Please try to test without that sim card.
And YES, you need to input a mainland Chinese phone number in order to fly in mainland China.

I have the same problem, updated the App yesterday wanted to start the drone and it asks for a mainland china phone number.(of course I don’t have a mainland china phone number)
I bought the drone in Germany. I have a Austria Sim in my iPhone. At the moment i travel through China and now a can’t fly my drone anymore?! What’s going on?
How can I activate the app again? Or do I now carry a 1500$ piece of plastic around which I can’t use anymore?

The same with me - very beginner btw. - Phantom 4 pro+ (with integrated Screen). Preparing for first flight... Update RC and drone ... but suddenly I'm asked for a China Mainland Number. Can't get away that dialog... I have of course neither (as Swiss) no China Phone number nor have I ever been in China ... Really frustrating ...

Hello,

I have the exact same problem after updating firmware. What to do ?

I tried remove data and cache from settings --> applications, then reinstall the app, and still the message pops-up !

I tried remove data and cache from settings --> applications, then reinstall the app, and still the message pops-up !

I'm sorry for the inconvenience caused, so you didn't travel to China, right? We released new DJI Go recently, please update your APP to the latest version. If the message still persists, please send me your location, IP address of smartphone, log file in DJI/dji.go.v4/log/CACHE/verphone, appreciate your cooperation.

DJI Mindy Posted at 2017-6-19 01:05
I'm sorry for the inconvenience caused, so you didn't travel to China, right? We released new DJI Go recently, please update your APP to the latest version. If the message still persists, please send me your location, IP address of smartphone, log file in DJI/dji.go.v4/log/CACHE/verphone, appreciate your cooperation.

Hi,

No I didn't travel to China. I donwloaded the latest version of DJI Go app 4.1.2. and the message still persists.

My location is Paris, France, IP of my smartphone 66.249.93.218. Log file below, as mentionned here also.

Best

2017-06-18 11:44:43:644 E:
**********init**********
2017-06-18 11:44:44:879 E: getIsNeedPhone success result={"status":0}
2017-06-18 11:44:45:349 E: getIsNeedPhone success result={"status":0}
2017-06-18 11:44:45:424 E: getIsNeedPhone success result={"status":1,"mobile":"18380409443"}
2017-06-18 11:44:45:902 E: success getPhoneHistory
2017-06-18 11:45:55:316 E: ConnectLose status=ConnectOK
2017-06-18 11:45:56:685 E: start getStateFromFlyc isForce=true
2017-06-18 11:46:11:704 E: failure getStateFromFlyc ccode=TIMEOUT
2017-06-18 11:46:11:737 E:  status=NotBind
2017-06-18 11:46:12:392 E: getIsNeedPhone success result={"status":0}
2017-06-18 11:46:12:406 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=Unknown
2017-06-18 11:46:12:438 E: start writeBindOkToFlyc
2017-06-18 11:46:12:458 E:  status=NotBind
2017-06-18 11:46:27:458 E: failure writeBindOkToFlyc ccode=TIMEOUT
2017-06-18 11:47:58:663 E: ConnectLose status=ConnectLose
2017-06-18 11:47:58:660 E: ConnectLose status=ConnectOK
2017-06-18 11:47:58:762 E: NetWorkStatus=CONNECT_OK
2017-06-18 11:47:58:800 E: NetWorkStatus=WIFI_CHANGED
2017-06-18 11:47:58:818 E: NetWorkStatus=WIFI_CHANGED
2017-06-18 11:48:00:112 E: start getStateFromFlyc isForce=true
2017-06-18 11:48:04:303 E: getIsNeedPhone success result={"status":1,"mobile":"18380409443"}
2017-06-18 11:48:04:323 E: getIsNeedPhone success result={"status":0}
2017-06-18 11:48:04:355 E: getIsNeedPhone success result={"status":0}
2017-06-18 11:48:14:732 E: ConnectLose status=ConnectLose
2017-06-18 11:48:15:126 E: failure getStateFromFlyc ccode=TIMEOUT
2017-06-18 11:48:15:141 E:  status=BindOk
2017-06-18 11:50:23:512 E: ConnectLose status=ConnectOK
2017-06-18 11:50:24:996 E: start getStateFromFlyc isForce=true
2017-06-18 11:50:40:018 E: failure getStateFromFlyc ccode=TIMEOUT
2017-06-18 11:50:40:033 E:  status=NotBind
2017-06-18 11:50:40:556 E: getIsNeedPhone success result={"status":0}
2017-06-18 11:50:40:598 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=Unknown
2017-06-18 11:50:40:659 E: start writeBindOkToFlyc
2017-06-18 11:50:40:677 E:  status=NotBind
2017-06-18 11:50:55:682 E: failure writeBindOkToFlyc ccode=TIMEOUT
2017-06-18 11:55:56:640 E: ConnectLose status=ConnectLose
2017-06-18 11:55:56:648 E: ConnectLose status=ConnectOK
2017-06-18 11:55:58:034 E: start getStateFromFlyc isForce=true
2017-06-18 11:56:13:048 E: failure getStateFromFlyc ccode=TIMEOUT
2017-06-18 11:56:13:066 E:  status=NotBind
2017-06-18 11:56:13:566 E: getIsNeedPhone success result={"status":0}
2017-06-18 11:56:13:582 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=Unknown
2017-06-18 11:56:13:613 E: start writeBindOkToFlyc
2017-06-18 11:56:13:632 E:  status=NotBind
2017-06-18 11:56:28:668 E: failure writeBindOkToFlyc ccode=TIMEOUT
2017-06-18 11:59:46:226 E: ConnectLose status=ConnectLose
2017-06-18 11:59:50:327 E: ConnectLose status=ConnectOK
2017-06-18 11:59:51:732 E: start getStateFromFlyc isForce=true
2017-06-18 12:00:06:745 E: failure getStateFromFlyc ccode=TIMEOUT
2017-06-18 12:00:06:755 E:  status=NotBind
2017-06-18 12:00:07:210 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:00:07:219 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=Unknown
2017-06-18 12:00:07:241 E: start writeBindOkToFlyc
2017-06-18 12:00:07:253 E:  status=NotBind
2017-06-18 12:00:22:254 E: failure writeBindOkToFlyc ccode=TIMEOUT
2017-06-18 12:00:54:521 E: ConnectLose status=ConnectLose
2017-06-18 12:00:57:877 E: ConnectLose status=ConnectOK
2017-06-18 12:00:59:347 E: start getStateFromFlyc isForce=true
2017-06-18 12:01:14:363 E: failure getStateFromFlyc ccode=TIMEOUT
2017-06-18 12:01:14:375 E:  status=NotBind
2017-06-18 12:01:14:806 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:01:14:817 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=Unknown
2017-06-18 12:01:14:841 E: start writeBindOkToFlyc
2017-06-18 12:01:14:855 E:  status=NotBind
2017-06-18 12:01:29:856 E: failure writeBindOkToFlyc ccode=TIMEOUT
2017-06-18 12:11:37:375 E: ConnectLose status=ConnectLose
2017-06-18 12:12:08:545 E: ConnectLose status=ConnectOK
2017-06-18 12:12:09:872 E: start getStateFromFlyc isForce=true
2017-06-18 12:12:10:123 E: success getStateFromFlyc  flyc flag=Unknown, local snPhoneStatus=NotBind
2017-06-18 12:12:10:134 E: start writeBindOkToFlyc
2017-06-18 12:12:10:145 E:  status=NotBind
2017-06-18 12:12:10:335 E: success writeBindOkToFlyc
2017-06-18 12:12:10:588 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:12:10:601 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=NotBind
2017-06-18 12:12:10:629 E: start writeBindOkToFlyc
2017-06-18 12:12:10:649 E:  status=NotBind
2017-06-18 12:12:10:790 E: success writeBindOkToFlyc
2017-06-18 12:13:11:227 E: ConnectLose status=ConnectLose
2017-06-18 12:13:20:328 E: ConnectLose status=ConnectOK
2017-06-18 12:13:21:694 E: start getStateFromFlyc isForce=true
2017-06-18 12:13:21:883 E: success getStateFromFlyc  flyc flag=NotBind, local snPhoneStatus=NotBind
2017-06-18 12:13:21:892 E: start writeBindOkToFlyc
2017-06-18 12:13:21:901 E:  status=NotBind
2017-06-18 12:13:22:127 E: success writeBindOkToFlyc
2017-06-18 12:13:22:338 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:13:22:354 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=NotBind
2017-06-18 12:13:22:387 E: start writeBindOkToFlyc
2017-06-18 12:13:22:402 E:  status=NotBind
2017-06-18 12:13:22:569 E: success writeBindOkToFlyc
2017-06-18 12:13:47:249 E: ConnectLose status=ConnectLose
2017-06-18 12:14:10:132 E: ConnectLose status=ConnectOK
2017-06-18 12:14:12:205 E: ConnectLose status=ConnectLose
2017-06-18 12:14:15:977 E: ConnectLose status=ConnectOK
2017-06-18 12:14:17:417 E: start getStateFromFlyc isForce=true
2017-06-18 12:14:17:542 E: success getStateFromFlyc  flyc flag=NotBind, local snPhoneStatus=NotBind
2017-06-18 12:14:17:551 E: start writeBindOkToFlyc
2017-06-18 12:14:17:561 E:  status=NotBind
2017-06-18 12:14:17:793 E: success writeBindOkToFlyc
2017-06-18 12:14:18:023 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:14:18:039 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=NotBind
2017-06-18 12:14:18:064 E: start writeBindOkToFlyc
2017-06-18 12:14:18:082 E:  status=NotBind
2017-06-18 12:14:18:203 E: success writeBindOkToFlyc
2017-06-18 12:14:18:574 E: start getStateFromFlyc isForce=true
2017-06-18 12:14:18:769 E: success getStateFromFlyc  flyc flag=NotBind, local snPhoneStatus=NotBind
2017-06-18 12:14:18:784 E: start writeBindOkToFlyc
2017-06-18 12:14:18:800 E:  status=NotBind
2017-06-18 12:14:19:003 E: success writeBindOkToFlyc
2017-06-18 12:14:19:264 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:14:19:280 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=NotBind
2017-06-18 12:14:19:310 E: start writeBindOkToFlyc
2017-06-18 12:14:19:329 E:  status=NotBind
2017-06-18 12:14:19:401 E: success writeBindOkToFlyc
2017-06-18 12:14:24:123 E: ConnectLose status=ConnectLose
2017-06-18 12:14:27:416 E: ConnectLose status=ConnectOK
2017-06-18 12:14:28:855 E: start getStateFromFlyc isForce=true
2017-06-18 12:14:29:044 E: success getStateFromFlyc  flyc flag=NotBind, local snPhoneStatus=NotBind
2017-06-18 12:14:29:061 E: start writeBindOkToFlyc
2017-06-18 12:14:29:079 E:  status=NotBind
2017-06-18 12:14:29:304 E: success writeBindOkToFlyc
2017-06-18 12:14:29:545 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:14:29:562 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=NotBind
2017-06-18 12:14:29:589 E: start writeBindOkToFlyc
2017-06-18 12:14:29:608 E:  status=NotBind
2017-06-18 12:14:29:903 E: success writeBindOkToFlyc
2017-06-18 12:14:58:906 E:
**********init**********
2017-06-18 12:15:01:477 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:15:01:691 E: getIsNeedPhone success result={"status":1,"mobile":"18380409443"}
2017-06-18 12:15:01:736 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:15:02:410 E: success getPhoneHistory
2017-06-18 12:15:11:724 E: ConnectLose status=ConnectOK
2017-06-18 12:15:11:736 E: ConnectLose status=ConnectLose
2017-06-18 12:15:15:836 E: ConnectLose status=ConnectLose
2017-06-18 12:15:15:844 E: ConnectLose status=ConnectOK
2017-06-18 12:15:17:687 E: start getStateFromFlyc isForce=true
2017-06-18 12:15:17:885 E: success getStateFromFlyc  flyc flag=NotBind, local snPhoneStatus=NotBind
2017-06-18 12:15:17:900 E: start writeBindOkToFlyc
2017-06-18 12:15:17:915 E:  status=NotBind
2017-06-18 12:15:18:145 E: success writeBindOkToFlyc
2017-06-18 12:15:18:386 E: getIsNeedPhone success result={"status":0}
2017-06-18 12:15:18:399 E: success onFlycPhoneStatusUnknown status=NotBind, curFlycState=NotBind
2017-06-18 12:15:18:556 E: start writeBindOkToFlyc
2017-06-18 12:15:18:577 E:  status=NotBind
2017-06-18 12:15:18:774 E: success writeBindOkToFlyc
2017-06-18 12:15:22:995 E: ConnectLose status=ConnectLose
2017-06-18 12:15:23:265 E: ConnectLose status=ConnectOK
2017-06-18 12:16:26:592 E: ConnectLose status=ConnectLose
2017-06-18 12:16:26:607 E: ConnectLose status=ConnectOK
2017-06-18 12:19:37:922 E: ConnectLose status=ConnectLose
2017-06-18 12:19:43:581 E: ConnectLose status=ConnectOK
2017-06-18 12:19:45:227 E: start getStateFromFlyc isForce=true
2017-06-18 12:19:45:330 E: success getStateFromFlyc  flyc flag=NotBind, local snPhoneStatus=NotBind
2017-06-18 12:19:45:339 E: start writeBindOkToFlyc
2017-06-18 12:19:45:350 E:  status=NotBind
2017-06-18 12:19:45:575 E: success writeBindOkToFlyc
2017-06-18 12:19:49:276 E: getIsNeedPhone success result={"status":-2}
2017-06-18 12:19:49:177 E: ConnectLose status=ConnectLose
2017-06-18 12:19:49:869 E: ConnectLose status=ConnectOK
2017-06-18 12:19:49:868 E: success onFlycPhoneStatusUnknown status=NeedBindLock, curFlycState=NotBind
2017-06-18 12:19:50:543 E:  status=BindOk
2017-06-18 12:19:57:928 E: ConnectLose status=ConnectLose
2017-06-18 12:19:57:978 E: ConnectLose status=ConnectOK
2017-06-18 12:19:59:469 E: start getStateFromFlyc isForce=true
2017-06-18 12:19:59:668 E: success getStateFromFlyc  flyc flag=NotBind, local snPhoneStatus=NeedBindLock
2017-06-18 12:19:59:678 E: start writeBindOkToFlyc
2017-06-18 12:19:59:688 E:  status=NeedBindLock
2017-06-18 12:19:59:698 E: model.time=1497781190 model.status=NeedBindLock isinactive=false upgrade=false firstByte=1 motor=false
2017-06-18 12:19:59:786 E: model.time=1497781190 model.status=NeedBindLock isinactive=false upgrade=false firstByte=1 motor=false
2017-06-18 12:19:59:950 E: success writeBindOkToFlyc
2017-06-18 12:20:04:269 E: success DJIAddPhoneFragment getPhoneHistory
2017-06-18 12:20:21:080 E: DOPhone result=false
2017-06-18 12:20:25:417 E: success DJIAddPhoneFragment getPhoneHistory
2017-06-18 12:20:27:296 E: DOPhone result=false
2017-06-18 12:20:29:351 E: success DJIAddPhoneFragment getPhoneHistory
2017-06-18 12:20:30:029 E: DOPhone result=false
2017-06-18 12:27:16:899 E:
**********init**********
2017-06-18 12:27:20:072 E: start getStateFromFlyc isForce=true
2017-06-18 12:27:20:314 E: success getStateFromFlyc  flyc flag=NeedBind, local snPhoneStatus=null
2017-06-18 12:27:20:814 E: getIsNeedPhone success result={"status":-2}
2017-06-18 12:27:20:824 E: success onFlycPhoneStatusUnknown status=NeedBindLock, curFlycState=NeedBind
2017-06-18 12:27:20:849 E: start writeBindOkToFlyc
2017-06-18 12:27:20:862 E:  status=NeedBindLock
2017-06-18 12:27:20:871 E: model.time=1497781640 model.status=NeedBindLock isinactive=false upgrade=false firstByte=1 motor=false
2017-06-18 12:27:20:880 E: model.time=1497781640 model.status=NeedBindLock isinactive=false upgrade=false firstByte=1 motor=false
2017-06-18 12:27:20:962 E: success writeBindOkToFlyc
2017-06-18 12:27:41:382 E: model.time=1497781640 model.status=NeedBindLock isinactive=false upgrade=false firstByte=1 motor=false
2017-06-18 12:27:45:315 E: success DJIAddPhoneFragment getPhoneHistory
2017-06-18 12:27:46:339 E: DOPhone result=false
2017-06-18 12:31:45:153 E: success DJIAddPhoneFragment getPhoneHistory
2017-06-18 12:31:45:675 E: DOPhone result=false
2017-06-18 12:32:36:119 E: ConnectLose status=ConnectOK
2017-06-18 12:32:36:117 E: ConnectLose status=ConnectLose
2017-06-18 12:32:37:552 E: start getStateFromFlyc isForce=true
2017-06-18 12:32:37:760 E: success getStateFromFlyc  flyc flag=NeedBind, local snPhoneStatus=NeedBindLock
2017-06-18 12:32:37:787 E: start writeBindOkToFlyc
2017-06-18 12:32:37:810 E:  status=NeedBindLock
2017-06-18 12:32:37:845 E: model.time=1497781640 model.status=NeedBindLock isinactive=false upgrade=false firstByte=1 motor=false
2017-06-18 12:32:37:875 E: model.time=1497781640 model.status=NeedBindLock isinactive=false upgrade=false firstByte=1 motor=false
2017-06-18 12:32:38:013 E: success writeBindOkToFlyc
2017-06-18 12:32:42:814 E: ConnectLose status=ConnectOK
2017-06-18 12:32:42:832 E: ConnectLose status=ConnectLose

benji89 Posted at 2017-6-19 05:28
Hi,

No I didn't travel to China. I donwloaded the latest version of DJI Go app 4.1.2. and the message still persists.

Thank for your information, Natalia has escalated this issue to our engineer for further analysis, we will come back to you once we hear from them, appreciate your patience.

P4P Plus: This is what I did. I turned the AC off. Switched RC to airline mode since the China phone link prompt rendered practically all apps useless. Then restarted the RC. Went to System Settings>Personal-Backup & reset>Personal Data-Factory data reset>RESET DEVICE. Then restarted RC. Then turned off airline mode. Re-entered my account name and password. Went to maps and downloaded my country. Though I had to reprogram all RC setting all over again. Better than not being able to use the RC. Hope this helps.

P4P Plus: This is what I did. I turned the AC off. Switched RC to airline mode since the China phone link prompt rendered practically all apps useless. Then restarted the RC. Went to System Settings>Personal-Backup & reset>Personal Data-Factory data reset>RESET DEVICE. Then restarted RC. Then turned off airline mode. Re-entered my account name and password. Went to maps and downloaded my country. Though I had to reprogram all RC setting all over again. Better than not being able to use the RC. Hope this helps.

launch Go 4 app without connection to Mavic. Then select Mavic Pro in pick list and Enter Device. Go to General Settings and ensure that Enable Amap for China AND Caliibrate Map Coordinates for China are OFF. For some reason after the update one of them was turned ON. Then restart app and connect to Mavic Pro as usual and all should be good.

launch Go 4 app without connection to Mavic. Then select Mavic Pro in pick list and Enter Device. Go to General Settings and ensure that Enable Amap for China AND Caliibrate Map Coordinates for China are OFF. For some reason after the update one of them was turned ON. Then restart app and connect to Mavic Pro as usual and all should be good.

Spurelli61 Posted at 2017-6-24 13:24
launch Go 4 app without connection to Mavic. Then select Mavic Pro in pick list and Enter Device. Go to General Settings and ensure that Enable Amap for China AND Caliibrate Map Coordinates for China are OFF. For some reason after the update one of them was turned ON. Then restart app and connect to Mavic Pro as usual and all should be good.

I dont understand this. Why the developpers dont test the App before go live???

fans2767d1d8 Posted at 2017-6-22 02:44
P4P Plus: This is what I did. I turned the AC off. Switched RC to airline mode since the China phone link prompt rendered practically all apps useless. Then restarted the RC. Went to System Settings>Personal-Backup & reset>Personal Data-Factory data reset>RESET DEVICE. Then restarted RC. Then turned off airline mode. Re-entered my account name and password. Went to maps and downloaded my country. Though I had to reprogram all RC setting all over again. Better than not being able to use the RC. Hope this helps.

I did what you suggested....I updated to latest firmware version. when I restarted the RC is said I should enter a mainland china phone number. I live in Australia and don't have one. I then put the RC into aircraft mode, and reset the RC to factory default. I then restarted the RC and asks me to log in to DJI. When I enter my username and password it now says "Network Unavailable. Check your internet connection". My wireless internet is working fine.... I cannot get out of the login screen. My RC is useless.....

i am having the same issue!  it was indeed turned on somehow (by default?) "Enable Amap for China", so disable, and reset both RC and AC and worked for sometime but came back to prompt the same issue again.

is there any conclusion on this issue? or still being debugged?  I just received this drone and cannot get it working because of this issue. help!

I managed to fix this issue. Steps:

1. Uninstall DJI App
2. Install a File Browser app on your phone (I used FX)
3. Delete all folder and files you can see with the word DJI in it
(Main Storage > DJI Folder), (Main Storage > dji.go.v4 Folder) and there may also be a DJI text file in Main Storage also.
4. Reinstall the app
5. Log into app and turn off BOTH China settings
6. Restart App
7. Turn on RC and AC and connect as normal

I'm 99% sure this issue is caused by the Flight Simulator! Don't use unless you are happy to follow this process every time.

I  am having the same issue, WTF is this crap. I just picked up the Phantom 4 Adv in Canada yesterday and I cant use the app because its asking for a number from China? Jesus... this is absolutely  UNACCEPTABLE.

There is no solution on here either, Cleared cache, deleted app and files and reinstalled...................

Hi

I have the same issue with the message:

"Link Phone Number
To complete you registration information and aircraft activation data in DJI GO 4, please link and verify your phone number"

and when I press "Link",

"Enter Mainland China telephone number... etc."

SO WHAT IS THE DEFINITE ANSWER FROM DJI TO THAT SURREAL PROBLEM ???

DJI Mindy Posted at 2017-6-20 00:21
Thank for your information, Natalia has escalated this issue to our engineer for further analysis, we will come back to you once we hear from them, appreciate your patience.

Hi
Any news about the problem?

matthew.becker Posted at 2017-7-27 14:55
I managed to fix this issue. Steps:

1. Uninstall DJI App

Works fine!
Thanks...

matthew.becker Posted at 2017-7-27 14:55
I managed to fix this issue. Steps:

1. Uninstall DJI App

Thank you Matthew.Becker -- Using your instructions, I am back in the air.

It seems that this problem has something to do with after you run the simulator on the app.

I uninstalled the app, reinstall it, there was no such notification to put in my China number. After I ran the simulator, suddenly after I was done with it, the notification came out.

Uninstalled the app, reinstall it, and there was no problem with the notification.
DJI, i hope you could come up with an update to counter this issue.

EZMavic Posted at 2017-8-14 10:54
It seems that this problem has something to do with after you run the simulator on the app.

I uninstalled the app, reinstall it, there was no such notification to put in my China number. After I ran the simulator, suddenly after I was done with it, the notification came out.

Thanks for your feedback, I will report to our engineers for testing and analysis.
If other users encounter the same problem, we suggest:
1. Clear all cache in Settings.
2. Bring the aircraft to the place with strong GPS signal.
3. Connect your mobile device to local network and reboot the APP.
4. Reconnect aircraft to APP.

DJI Mindy Posted at 2017-8-14 22:32
Thanks for your feedback, I will report to our engineers for testing and analysis.
If other users encounter the same problem, we suggest:
1. Clear all cache in Settings.

Mavic received yesterday. Initially very impressed with build quality after coming from Yuneec and Parrot offerings but what is going on? This Chinese phone number issue has prevented me from flying it. I have literally wasted hours deleting and reinstalling the GO4 app, checking settings and all of the above. I have not been near the simulator and have a strong GPS signal so why it thinks I am in China is beyond me and quite frankly bizarre. This drone was bought for a trip inside the Arctic Circle and if I can't get it sorted soon regrettably I will need to return it. I sincerely hope it doesn't come to that. Please help!

g-wills Posted at 2017-8-17 12:49
Mavic received yesterday. Initially very impressed with build quality after coming from Yuneec and Parrot offerings but what is going on? This Chinese phone number issue has prevented me from flying it. I have literally wasted hours deleting and reinstalling the GO4 app, checking settings and all of the above. I have not been near the simulator and have a strong GPS signal so why it thinks I am in China is beyond me and quite frankly bizarre. This drone was bought for a trip inside the Arctic Circle and if I can't get it sorted soon regrettably I will need to return it. I sincerely hope it doesn't come to that. Please help!

Sorry for the trouble caused. Have you tried the steps I posted on 28#?
If the message still persists, please send me your DJI account, serial number of the aircraft, location when the windows pops up, IP address of smartphone, log file in DJI/dji.go.v4/log/CACHE/verphone, appreciate your cooperation.

DJI Mindy Posted at 2017-8-17 23:39
Sorry for the trouble caused. Have you tried the steps I posted on 28#?
If the message still persists, please send me your DJI account, serial number of the aircraft, location when the windows pops up, IP address of smartphone, log file in DJI/dji.go.v4/log/CACHE/verphone, appreciate your cooperation.

Hi Mindy, thanks for the reply.

I have followed all of the suggestions posted on 28# and am still being prompted for a mainland China tel no. This is with an excellent GPS signal.

The DJI GO app is 4.1.5 and I am trying to register and activate a Mavic.

There is no cache to clear if you mean the one on the app.

The AC serial number is 08QCE6S0120T7C
Location is Ware, Hertfordshire, UK
IP address is 217.44.101.84

What is the best way to provide the log file. Do I need DJI assistant.

Excuse my ignorance. This is my first DJI product.

g-wills Posted at 2017-8-18 10:16
Hi Mindy, thanks for the reply.

I have followed all of the suggestions posted on 28# and am still being prompted for a mainland China tel no. This is with an excellent GPS signal.

Have you tried to reinstall the APP? If it is the same, please upload the log file to the Dropbox, then provide us a link to download it, thank you in advance.

DJI Diana Posted at 2017-8-19 02:45
Have you tried to reinstall the APP? If it is the same, please upload the log file to the Dropbox, then provide us a link to download it, thank you in advance.

Hello Diana. I have deleted and reinstalled the app several times, clearing any cached data and making sure that anything to do with Chinese mapping is unticked.  Please read my previous posts. As can be seen from the log file the information is basically about the firmware update which was successful. The problem I am having is not being able to activate and register the Mavic Pro because I cannot get past the Chinese phone number issue. It is brand new and has never been flown. There are many posts online of people having the same problem even after they have replaced their Mavic so I feel that this must be an issue outside of the hardware. I am finding this hugely frustrating and am almost at the point of returning it to my supplier for a refund unless you can help.

[00384916]========== Download: remo-con disconnect. boot(1B3D) =======
[00385090]Master [10 02].
[00385179][29 00] Firmware download start...
[00409592][29 00] Firmware download finish successfully.
[00409681]Done (37697448B 0x93a027ca07ed75d2d40c0ba381b2ca46).

[00416263]========== Upgrade: remo-con disconnect. boot(1B3D)============
[00416351]Current version: loader[02.04.0385] firmware[02.04.0385].
[00416440]Firmware [A:\FC220_SEFw.bin 0x93a027ca07ed75d2d40c0ba381b2ca46] detected, card sn [0x00000000].
[00416532][29 00] Firmware upgrade start...
[00416620][01 00] Firmware upgrade tracecode 0x00010000
[00416723][01 00] Firmware upgrade tracecode 0x00020000
[00418281][01 00] Firmware upgrade tracecode 0x00030000
[00418369][01 00] Firmware upgrade tracecode 0x00040000
[00429047][01 00] Firmware upgrade tracecode 0x00050000
[00429136][01 00] Firmware upgrade tracecode 0x00060000
[00429223][01 00] Firmware upgrade tracecode 0x00070000
[00468875][01 00] Camera firmware programed successfully.
[00012241]========== Download: remo-con disconnect. boot(E020) =======
[00012329]Master [10 02].
[00012417][29 01] Firmware download start...
[00019965][29 01] Firmware download finish successfully.
[00020052]Done (59628B 0x39e7117be84db031fd2fe4927031338a).

[00022742]========== Upgrade: remo-con disconnect. boot(E020)============
[00022832]Current version: loader[02.04.0385] firmware[02.07.0498].
[00022921]Firmware [A:\CAMLDRFw.bin 0x39e7117be84db031fd2fe4927031338a] detected, card sn [0x00000000].
[00023011][29 01] Firmware upgrade start...
[00023100][01 01] Firmware upgrade tracecode 0x00010000
[00023191][01 01] Firmware upgrade tracecode 0x00020000
[00023281][01 01] Firmware upgrade tracecode 0x00030000
[00023416][01 01] Firmware upgrade tracecode 0x00040000
[00023519][01 01] Firmware upgrade tracecode 0x00050000
[00023659][01 01] Firmware upgrade tracecode 0x00060000
[00023783][01 01] Firmware upgrade tracecode 0x00070000
[00023873][01 01] Camera loader update successfully.
[00054094][29 01] Firmware upgrade finished successfully.
[00054314]Done.

[00725992]========== Download: 2017.08.17 19:23:44. boot(2710) =======
[00726081]Master [10 02].
[00726173][29 00] Firmware download start...
[00760824][29 00] Firmware download finish successfully.
[00760914]Done (37697448B 0x65f967a5178c677cba9524380bda70a6).

[00768003]========== Upgrade: 2017.08.17 19:24:26. boot(2710)============
[00768090]Current version: loader[02.07.0498] firmware[02.07.0498].
[00768180]Firmware [A:\FC220_SEFw.bin 0x65f967a5178c677cba9524380bda70a6] detected, card sn [0x8d2b1c66].
[00768270][29 00] Firmware upgrade start...
[00768360][01 00] Firmware upgrade tracecode 0x00010000
[00769134][01 00] Firmware upgrade tracecode 0x00020000
[00770740][01 00] Firmware upgrade tracecode 0x00030000
[00770833][01 00] Firmware upgrade tracecode 0x00040000
[00781679][01 00] Firmware upgrade tracecode 0x00050000
[00781773][01 00] Firmware upgrade tracecode 0x00060000
[00781880][01 00] Firmware upgrade tracecode 0x00070000
[00825621][01 00] Camera firmware programed successfully.
[00012335]========== Download: remo-con disconnect. boot(2710) =======
[00012423]Master [10 02].
[00012512][29 01] Firmware download start...
[00019993][29 01] Firmware download finish successfully.
[00020085]Done (59628B 0xfdd6cfde5a38f876c7f1458b1ead5fe5).

[00022875]========== Upgrade: 2017.08.17 19:25:52. boot(2710)============
[00022965]Current version: loader[02.07.0498] firmware[02.07.0499].
[00023053]Firmware [A:\CAMLDRFw.bin 0xfdd6cfde5a38f876c7f1458b1ead5fe5] detected, card sn [0x8d2b1c66].
[00023142][29 01] Firmware upgrade start...
[00023232][01 01] Firmware upgrade tracecode 0x00010000
[00023321][01 01] Firmware upgrade tracecode 0x00020000
[00023411][01 01] Firmware upgrade tracecode 0x00030000
[00023544][01 01] Firmware upgrade tracecode 0x00040000
[00023647][01 01] Firmware upgrade tracecode 0x00050000
[00023911][01 01] Firmware upgrade tracecode 0x00060000
[00024034][01 01] Firmware upgrade tracecode 0x00070000
[00024123][01 01] Camera loader update successfully.
[00054213][29 01] Firmware upgrade finished successfully.
[00054428]Done.

g-wills Posted at 2017-8-20 07:21
Hello Diana. I have deleted and reinstalled the app several times, clearing any cached data and making sure that anything to do with Chinese mapping is unticked.  Please read my previous posts. As can be seen from the log file the information is basically about the firmware update which was successful. The problem I am having is not being able to activate and register the Mavic Pro because I cannot get past the Chinese phone number issue. It is brand new and has never been flown. There are many posts online of people having the same problem even after they have replaced their Mavic so I feel that this must be an issue outside of the hardware. I am finding this hugely frustrating and am almost at the point of returning it to my supplier for a refund unless you can help.

[00384916]========== Download: remo-con disconnect. boot(1B3D) =======

Further to my previous post I forgot to mention that it is possible to start the motors and probably fly without the app just with the RC. Does this mean that it has already been activated by someone else? As I said earlier it is as I understand brand new and came with all the stickers attached and batteries at a storage level of charge. The serial number is listed in a previous post 31#.

g-wills Posted at 2017-8-20 07:58
Further to my previous post I forgot to mention that it is possible to start the motors and probably fly without the app just with the RC. Does this mean that it has already been activated by someone else? As I said earlier it is as I understand brand new and came with all the stickers attached and batteries at a storage level of charge. The serial number is listed in a previous post 31#.

May I know where did you purchase this drone? Could you please provide the receipt?

DJI Diana Posted at 2017-8-20 22:25
May I know where did you purchase this drone? Could you please provide the receipt?

Certainly, do you have an email address that I can send it to?

g-wills Posted at 2017-8-21 02:50
Certainly, do you have an email address that I can send it to?

Sorry, are you able to upload it to the Dropbox, then PM me the link, or you can just tell the name of the retailer first, I can try to check it.

DJI Diana Posted at 2017-8-21 03:09
Sorry, are you able to upload it to the Dropbox, then PM me the link, or you can just tell the name of the retailer first, I can try to check it.

Not able to PM you with the Dropbox link showing my receipt as it's blocked but the retailer was Pro-Camera based in Cheltenham UK.

g-wills Posted at 2017-8-21 05:25
Not able to PM you with the Dropbox link showing my receipt as it's blocked but the retailer was Pro-Camera based in Cheltenham UK.

I actually got it to work without the Chinese number pop up late last night. Replicated everything this morning, same mobile, same network, strong GPS signal........and guess what Chinese number request back again !!!

This evening I received my first Mavic and haven't been able to fly one single minute! Still waiting for THE SOLUTION. I live in the Netherlands and not in Mainland China! On the DJI site still nothing mentioned about the problem and if they are working on an solution.This is very BAD!