Ken,

Any chance you can help this guy out? Seems like he just needs a few documents to get this thing fixed. Let me know your thoughts and I'll send him your way.

Thank you very much!

Jerry

"I am located outside of US. In the country of Georgia. There are no official DJI re-sellers in here. So i had to order DJI over the internet. In the january of this year, i ordered DJI P3 Advanced, through the freight-forwarding company in Delaware. The one that ships from Delaware to the country of Georgia. Not vice versa. So p3a was delivered to DE first and after shipped to Georgia. After i received it, i had to pay 18% taxes, because by Georgian rules, anything imported that costs over 150$, government should take taxes from you. 18%.

Recently i got this problem, of ESC status error, (Esc status error?? more details about this) which means something is wrong with the motherboard, and i need to send it back for the repair. I can't do it through the freightforwarding company - since they work only one way. From US. not vice versa.

I acknowledge that i need to send it by regular post, and which won't be paid by DJI, and will cost me at least 90$ to send it all across to globe to US. I acknowledge that.
But the problem i have is that, after DJI will fix/replace the drone, and send it back to me(again through freight forwarding) - the government will tax me again 18%.
To make sure it doesn't happen, i need DJI to write the official letter stating my name, and the Serial number of the AC and the fact that they are waiting for me to send it to them to fix it. And only after i provide customs with this letter, they will give me some sort of a document, which will keep me away from paying taxes again. BUT with the customer support that DJI has, i really DOUBT they are able to do it. Because it takes them hours to reply, and they never know the solution. Promise to get back to me. But never do with one.

Another option is to ask DJI after fixing/replacing the AC, include the $0 invoice or anything under $150. But this will be also hard to explain to them, and control that they actually do it.

I am devastated. Don't know what to do. Should i sell the P3A here by parts?
Because, sending it to us, 90$ + 40$for bringing it back + 150$ for taxes. = 280$ for repairing it. Its terrible."

Bump...Ken, you think you can help this guy out?

Jerry

I just found out that some countries may impose taxes and I am sorry about that.
As far as repairing, you would have to pay to ship it to the Germany repair center and they ship back to you at no charge.
What is your email and I will have the German support center contact you and you can explain to them to include something on the packaging so you are not charged any more taxes.

DJI-Ken Posted at 2016-4-25 12:47
I just found out that some countries may impose taxes and I am sorry about that.
As far as repairing ...

Ken,

Thanks so very much! I don't know what time it is in Georgia right now or when this individual will be available again but I'll have him contact you on this thread. Thanks again, Ken. I knew you'd come through.

Jerry

Hey  JtrJr-UAV Pilot , Thank you!

Hey Ken.
This is me.
toradze2@gmail.com
Thanks

DJI-Ken Posted at 2016-4-25 12:47
I just found out that some countries may impose taxes and I am sorry about that.
As far as repairing ...

You're a good dude, Ken. If the whole crew down there was like you are that company would be unstoppable. I'll let you know when I hear back from this guy.

Thanks again,

Jerry

JtrJr-UAV Pilot Posted at 2016-4-26 02:20
You're a good dude, Ken. If the whole crew down there was like you are that company would be unsto ...

Ha, thanks buddy. I appreciate the kind words
I'll take care of your buddy.

t2adze Posted at 2016-4-26 02:18
Hey  JtrJr-UAV Pilot , Thank you!

Hey Ken.

Hello and sorry for your experience, I have emailed the Germany repair center and they will contact you.Are you on the latest update, just cruious if you can try to upgrade or downgrade. I know it probably will not work, but doesn't hurt to try before spending more mney to ship.

DJI-Ken Posted at 2016-4-25 23:30
Hello and sorry for your experience, I have emailed the Germany repair center and they will contact ...

I tried. It doesn't do anything. Doesn't start any updates.
I do everything correctly(Not the first time upgrading FW) -  the update simply doesnt start. Used different sd cards, still nothing.
Neither reinstalling 1.8. neither rolling back to 1.7.
TXT file says that the Firmware is SAME or older on the aircraft.
Update never starts.

I think this all is connected to 1.8 fw upgrade since the day one. Cause it went wrongish. Still nothing my fault. I followed all the instructions as i usually do.
This is my experience with it.
http://www.phantompilots.com/thr ... .74351

But after this i flew 3-4 times. Without an issue. NEVER ever crashed. Neither before, neither after the firmware upgrade.
One day i flew, i changed the battery. put in the new one, and since then ESC Error. No matter, new or old battery



P.S. Thank you guys for helping!

t2adze Posted at 2016-4-26 03:53
I tried. It doesn't do anything. Doesn't start any updates.
I do everything correctly(Not the first ...

it is not updating because you are already on 1.8.
You can try to downgrade by putting the 1.7 firmware on the aircraft from the P3 Advanced page http://www.dji.com/product/phantom-3-adv/info#downloads

Extract only the BIN file onto a freshly formatted SD card then put it in the aircraft (RC off) and let it run for up to 20 minutes until you see the camera lights go from red/green to solid GREEN.
If that is successful, then you have to downgrade the RC to 1.5.7. You can do that by connecting the RC to the app via USB cable, then from the GO app homepage, hold down the Academy section icon (graduation hat) for 5-10 seconds (aircraft powered OFF). Then it take you to the RC downgrade choice.
After you downgrade the RC, you will then be on matched firmware on both the RC and aircraft.

DJI-Ken Posted at 2016-4-26 00:04
it is not updating because you are already on 1.8.
You can try to downgrade by putting the 1.7 fir ...

I tried 1.7 also. It doesn't start. I've updated firmwares A LOT of times in the past, i know how it's done.
I put 1.7 on the SD card, put it in. And nothing happens. I left it for 10 minutes, still never started the upgrade.
There is no point downgrading the RC, if i can't rollback the AC firmware, right?

t2adze Posted at 2016-4-26 04:56
I tried 1.7 also. It doesn't start. I've updated firmwares A LOT of times in the past, i know how  ...

Correct, no need to downgrade if you cannot get the aircraft to downgrade to 1.7.
Can you post the hidden log file from trying 1.7 ?
I'm just curious why it will not downgrade.

Windows system :
http://windows.microsoft.com/en- ... den-files=windows-7
Mac system :
http://ianlunn.co.uk/articles/qu ... mac-os-x-mavericks/

DJI-Ken Posted at 2016-4-25 14:29
Ha, thanks buddy. I appreciate the kind words
I'll take care of your buddy.

Thanks again, Ken. Just to be clear, I don't have any "buddies"! You're alright though.

Jerry

DJI-Ken Posted at 2016-4-26 00:59
Correct, no need to downgrade if you cannot get the aircraft to downgrade to 1.7.
Can you post the ...

I'll be home in an hour and will do it.  (will try to downgrade to 1.7 again)
This hidden file will be on the SD card? Or i have to connect the aircraft?

Not sure what firmware I have..
But I downloaded DJI go app on April 12th. And it said firmware updated successfully.
Would it be wise to downgrade if possible?
Which firmware would be most stable right now?

Because I posted about my drone setting its own homepoint when I selected: Set current position as homepoint. It jumped the homepoint to a place a block away from where the drone was.
I have the Phantom Standard.
DJI says I can have option of sending my drone in for diagnosis but from my understanding, if i send it in and they test and find out there is "nothing wrong" then.. I would have to cover return shipping which is ridiculous. My case of what happened can be found from my posts.

It was a miracle that my drone landed safely in a parking lot and a lady happened to be walking by and she called the police. and the police was smart enough to send a message to DJI with the MAC number of my standard.
and was able to reteieve my drone. But if the home point was set to a major intersection, that could have caused harm or even death . that is very serious.
So what can I do...  I will test the drone again and try to recreate the same scenario.  and this time I will have more records with me , camera and everything for the test flight. hopefully it will not jump home points again.
my fail safe will be to switch to atti mode if it does start flying away again like last time, and HOPEFULLY atti mode will bring my drone back with no problems IF it jumps home points again.

t2adze Posted at 2016-4-26 05:17
I'll be home in an hour and will do it.  (will try to downgrade to 1.7 again)
This hidden file wi ...

Since you already tried to downgrade to 1.7, if you have not reformatted that SD card all the hidden data will be on it. If you did reformat, then try again and then put the SD card into the computer and post the hidden log file.

ryanlam115@gmai Posted at 2016-4-26 05:23
Not sure what firmware I have..
But I downloaded DJI go app on April 12th. And it said firmware upd ...

My only idea is that you reset the home point to the aircraft as you were flying by that location.
The home point is set to wherever you power the aircraft on and when it gets GPS signal.Since you are in Canada, you are free to send it in to be checked out, you woyuld pay the shipping to us and we pay to send it back to you.

DJI-Ken Posted at 2016-4-26 01:41
My only idea is that you reset the home point to the aircraft as you were flying by that location.
...

Will do in 40 minutes.
Quick question - better to format SD card from the AC?

t2adze Posted at 2016-4-26 05:46
Will do in 40 minutes.
Quick question - better to format SD card from the AC?

When putting firmware onto the SD card, better format it in the computer and also do an eject by right clicking.I'm am done for the day but will check in in a few hours.

DJI-Ken Posted at 2016-4-26 02:01
When putting firmware onto the SD card, better format it in the computer and also do an eject by ri ...

Here is the MISC hidden folder - https://www.dropbox.com/s/nxo2spkw40qjivb/MISC.rar?dl=0

and This is the text from the TXT file


========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.06.0040.bin
Upgrading ...
Result: Success.

========== 2016.01.04 16:19:51 =====================
Packet: P3S_FW_V01.06.0040.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin

========== 2014.01.01 00:00:14 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:10 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:09 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:10 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3S_FW_V01.08.0080.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2016.04.15 12:48:31 =====================
Packet: P3S_FW_V01.08.0080.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.07.0060.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2016.04.15 15:57:22 =====================
Packet: P3S_FW_V01.07.0060.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

toradze3 Posted at 2016-4-26 06:29
Here is the MISC hidden folder - https://www.dropbox.com/s/nxo2spkw40qjivb/MISC.rar?dl=0

and This ...

That is the normal log file, There's a MISC file on the SD card that can only be read if you enable the hidden log files.
It will look something like this, it shows each module.

                 

00265557]Version checking[2]...
[00265610][01 00][00] v2.47.4492 -> v2.47.4492
[00265666][01 01][00] v2.47.4492 -> v2.47.4492
[00265750][03 05][00] v34.1.0.5 -> v34.1.0.5
[00265830][03 06][05] v2.4.10.7 -> v2.4.10.7
[00265894][04 00][00] v1.29.0.51 -> v1.29.0.51
[00266010][05 00][00] v3.0.6.2 -> v3.0.6.2
[00278563][08 00][00] device not detected.
[00278629][09 00][00] v1.8.0.0 -> v1.8.0.0
[00278728][11 00][00] v3.8.15.4 -> v3.8.15.4
[00278928][12 00][00] v1.11.0.0 -> v1.11.0.0
[00279048][12 01][00] v1.11.0.0 -> v1.11.0.0
[00279148][12 02][00] v1.11.0.0 -> v1.11.0.0
[00279248][12 03][00] v1.11.0.0 -> v1.11.0.0
[00291813][15 00][00] device not detected.
[00291887][17 00][00] v1.1.0.4 -> v1.1.0.4
[00292008][17 01][00] v2.0.1.2 -> v2.0.1.2
[00292081][19 00][00] v1.0.8.96 -> v1.0.8.96
[00292136]Packet upgrade failed at version checking.

  

DJI-Ken Posted at 2016-4-26 05:40
That is the normal log file, There's a MISC file on the SD card that can only be read if you enable ...

Here is the MISC hidden folder - https://www.dropbox.com/s/nxo2spkw40qjivb/MISC.rar?dl=0

toradze3 Posted at 2016-4-26 03:02
Here is the MISC hidden folder - https://www.dropbox.com/s/nxo2spkw40qjivb/MISC.rar?dl=0

T2,

Can't you just cut and paste the contents of this file in your post? It's a small file. It's going to be a hassle for Ken to unzip the file from your Dropbox account. Also, others following this thread would like to see the info as well.

Jerry

JtrJr-UAV Pilot Posted at 2016-4-26 16:22
T2,

Can't you just cut and paste the contents of this file in your post? It's a small file. It's  ...

Sure.

[00022434]========== remo-con disconnect. boot(15) ============
[00022583]Firmware [C:\FC300SFw.bin] detected, card sn [0x60ce2769].
[00022621][01 00] Firmware upgrade start...
[00074093][01 00] Firmware upgrade finished successfully.
[00074128]Done.

[00012333]========== remo-con disconnect. boot(15) ============
[00012372]Packet [C:\P3S_FW_V01.06.0040.bin] detected, card sn [0x285538cf].
[00012411]Packet upgrade start...

[00012456]Packet checking...
[00012498]Packet vlink 01.06.0040 <-> 01.05.0030.
[00012573]Done.

[00012612]Version checking[1]...
[00012703][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012788][03 06][00] v2.4.0.4 -> v2.4.10.7 need upgrade.
[00012832][04 00][00] v1.41.0.0 -> v1.41.0.0
[00012939][11 00][00] v1.7.0.0 -> v1.7.15.1 need upgrade.
[00013037][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013137][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013212][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013312][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013354][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013448][17 00][00] v1.1.1.7 -> v1.1.1.7
[00013572][17 01][00] v1.0.2.7 -> v1.0.2.7
[00013642][19 00][00] v1.0.8.96 -> v1.0.8.96
[00013678][01 00][00] v1.22.4095 -> v1.22.4095
[00013718][01 01][00] v1.20.3419 -> v1.22.4095 need upgrade
[00013783][09 00][00] v1.7.0.3 -> v2.13.0.0 need upgrade.
[00013819]Done.

[00015859]Waiting for user confirm...
[00025907]Timeout, start upgrade automatically.

[00025983]Firmware upgrading[1]...
[00026119][01 01] Firmware upgrade start...
[00056412][01 01] Firmware upgrade finished successfully.
[00056474][11 00] Firmware upgrade start...
[00113885][11 00] Firmware upgrade finished successfully.
[00114123][03 06] Firmware upgrade start...
[00449449][03 06] Firmware upgrade finished successfully.
[00449515][09 00] Firmware upgrade start...
[00502988][09 00] Firmware upgrade finished successfully.
[00503035]Done.

[00503074]Version checking[2]...
[00503148][03 05][00] v34.2.0.9 -> v34.2.0.9
[00503228][03 06][05] v2.4.10.7 -> v2.4.10.7
[00503394][04 00][00] v1.41.0.0 -> v1.41.0.0
[00503508][11 00][05] v1.7.15.1 -> v1.7.15.1
[00503601][12 00][00] v1.10.0.0 -> v1.10.0.0
[00503681][12 01][00] v1.10.0.0 -> v1.10.0.0
[00503757][12 02][00] v1.10.0.0 -> v1.10.0.0
[00503852][12 03][00] v1.10.0.0 -> v1.10.0.0
[00503896][15 00][00] v1.1.2.0 -> v1.1.2.0
[00503976][17 00][00] v1.1.1.7 -> v1.1.1.7
[00504096][17 01][00] v1.0.2.7 -> v1.0.2.7
[00504157][19 00][00] v1.0.8.96 -> v1.0.8.96
[00504197][01 00][00] v1.22.4095 -> v1.22.4095
[00504242][01 01][05] v1.22.4095 -> v1.22.4095
[00504297][09 00][05] v2.13.0.0 -> v2.13.0.0
[00504339]Packet upgrade finish successfully.



[00011970]========== 2016.01.04 16:19:51. boot(15) ============
[00012008]Packet [C:\P3S_FW_V01.06.0040.bin] detected, card sn [0x285538cf].
[00012058]Packet upgrade start...

[00012102]Packet checking...
[00012144]Packet vlink 01.06.0040 <-> 01.05.0030.
[00012190]Record vlink 01.06.0040 <-> 01.05.0030 (flow = 0).
[00012231]Done.

[00012274]Version checking[1]...
[00012350][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012426][03 06][00] v2.4.10.7 -> v2.4.10.7
[00012472][04 00][00] v1.41.0.0 -> v1.41.0.0
[00012691][11 00][00] v1.7.15.1 -> v1.7.15.1
[00012802][12 00][00] v1.10.0.0 -> v1.10.0.0
[00012899][12 01][00] v1.10.0.0 -> v1.10.0.0
[00012983][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013077][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013120][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013218][17 00][00] v1.1.1.7 -> v1.1.1.7
[00013356][17 01][00] v1.0.2.7 -> v1.0.2.7
[00013411][19 00][00] v1.0.8.96 -> v1.0.8.96
[00013449][01 00][00] v1.22.4095 -> v1.22.4095
[00013493][01 01][00] v1.22.4095 -> v1.22.4095
[00013562][09 00][00] v2.13.0.0 -> v2.13.0.0
[00013603]Packet upgrade cancelled at version checking.



[00012638]========== remo-con disconnect. boot(15) ============
[00012675]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00012712]Packet upgrade start...

[00012755]Packet checking...
[00012793]Packet vlink 01.07.0060 <-> 01.06.0040.
[00012955]Record vlink 01.06.0040 <-> 01.05.0030 (flow = 0).
[00012995]Done.

[00013033]Version checking[1]...
[00013113][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013193][03 06][00] v2.4.10.7 -> v2.4.13.0 need upgrade.
[00013239][04 00][00] v1.41.0.0 -> v1.41.0.0
[00013378][11 00][00] v1.7.15.1 -> v1.7.15.1
[00013478][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013581][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013678][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013781][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013826][15 00][00] v1.1.2.0 -> v1.1.2.0
[00013921][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014057][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014107][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014148][01 00][00] v1.22.4095 -> v1.23.4920 need upgrade
[00014188][01 01][00] v1.22.4095 -> v1.23.4920 need upgrade
[00014246][09 00][00] v2.13.0.0 -> v2.13.0.0
[00014285]Done.

[00016325]Waiting for user confirm...
[00026366]Timeout, start upgrade automatically.

[00026448]Firmware upgrading[1]...
[00037959][01 00] Firmware upgrade start...
[00011737][01 00] Firmware upgrade finished successfully.
[00011782]Done.

[00011828]Packet [C:\P3S_FW_V01.07.0060.bin] resumed, card sn [0x285538cf].
[00011874]Packet vlink 01.07.0060 <-> 01.06.0040.
[00011917]Record vlink 01.06.0040 <-> 01.05.0030 (flow = 0).
[00011969]Version checking[2]...
[00012047][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012123][03 06][00] v2.4.10.7 -> v2.4.13.0 need upgrade.
[00012176][04 00][00] v1.41.0.0 -> v1.41.0.0
[00012283][11 00][00] v1.7.15.1 -> v1.7.15.1
[00012383][12 00][00] v1.10.0.0 -> v1.10.0.0
[00012457][12 01][00] v1.10.0.0 -> v1.10.0.0
[00012557][12 02][00] v1.10.0.0 -> v1.10.0.0
[00012657][12 03][00] v1.10.0.0 -> v1.10.0.0
[00017204][15 00][00] v1.1.2.0 -> v1.1.2.0
[00017271][17 00][00] v1.1.1.7 -> v1.1.1.7
[00017392][17 01][00] v1.0.2.7 -> v1.0.2.7
[00017456][19 00][00] v1.0.8.96 -> v1.0.8.96
[00017500][01 00][05] v1.23.4920 -> v1.23.4920
[00017545][01 01][00] v1.22.4095 -> v1.23.4920 need upgrade
[00017717][09 00][00] v2.13.0.0 -> v2.13.0.0
[00017771]Done.

[00017814]Firmware upgrading[2]...
[00017982][01 01] Firmware upgrade start...
[00048319][01 01] Firmware upgrade finished successfully.
[00048564][03 06] Firmware upgrade start...
[00319411][03 06] Firmware upgrade finished successfully.
[00319455]Done.

[00319506]Version checking[3]...
[00319602][03 05][00] v34.2.0.9 -> v34.2.0.9
[00319682][03 06][05] v2.4.13.0 -> v2.4.13.0
[00319740][04 00][00] v1.41.0.0 -> v1.41.0.0
[00319882][11 00][00] v1.7.15.1 -> v1.7.15.1
[00320002][12 00][00] v1.10.0.0 -> v1.10.0.0
[00320102][12 01][00] v1.10.0.0 -> v1.10.0.0
[00320210][12 02][00] v1.10.0.0 -> v1.10.0.0
[00320310][12 03][00] v1.10.0.0 -> v1.10.0.0
[00320357][15 00][00] v1.1.2.0 -> v1.1.2.0
[00320446][17 00][00] v1.1.1.7 -> v1.1.1.7
[00320582][17 01][00] v1.0.2.7 -> v1.0.2.7
[00320656][19 00][00] v1.0.8.96 -> v1.0.8.96
[00320703][01 00][05] v1.23.4920 -> v1.23.4920
[00320754][01 01][05] v1.23.4920 -> v1.23.4920
[00320815][09 00][00] v2.13.0.0 -> v2.13.0.0
[00320860]Packet upgrade finish successfully.



[00010186]========== remo-con disconnect. boot(15) ============
[00010230]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00010273]Packet upgrade start...

[00010328]Packet checking...
[00010372]Packet vlink 01.07.0060 <-> 01.06.0040.
[00010415]Record vlink 01.07.0060 <-> 01.06.0040 (flow = 0).
[00010458]Done.

[00010509]Version checking[1]...
[00010594][03 05][00] v34.2.0.9 -> v34.2.0.9
[00010674][03 06][00] v2.4.13.0 -> v2.4.13.0
[00010725][04 00][00] v1.41.0.0 -> v1.41.0.0
[00010835][11 00][00] v1.7.0.0 -> v1.7.15.1 need upgrade.
[00010928][12 00][00] v1.10.0.0 -> v1.10.0.0
[00011028][12 01][00] v1.10.0.0 -> v1.10.0.0
[00011111][12 02][00] v1.10.0.0 -> v1.10.0.0
[00011203][12 03][00] v1.10.0.0 -> v1.10.0.0
[00015753][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015844][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015965][17 01][00] v1.0.2.7 -> v1.0.2.7
[00016164][19 00][00] v1.0.8.96 -> v1.0.8.96
[00016206][01 00][00] v1.23.4920 -> v1.23.4920
[00016256][01 01][00] v1.23.4920 -> v1.23.4920
[00016323][09 00][00] v2.13.0.0 -> v2.13.0.0
[00016364]Done.

[00018408]Waiting for user confirm...
[00028453]Timeout, start upgrade automatically.

[00028550]Firmware upgrading[1]...
[00028604][11 00] Firmware upgrade start...
[00074873][11 00] Firmware upgrade finished successfully.
[00074920]Done.

[00074968]Version checking[2]...
[00075066][03 05][00] v34.2.0.9 -> v34.2.0.9
[00075138][03 06][00] v2.4.13.0 -> v2.4.13.0
[00075186][04 00][00] v1.41.0.0 -> v1.41.0.0
[00075299][11 00][05] v1.7.15.1 -> v1.7.15.1
[00075399][12 00][00] v1.10.0.0 -> v1.10.0.0
[00075499][12 01][00] v1.10.0.0 -> v1.10.0.0
[00075599][12 02][00] v1.10.0.0 -> v1.10.0.0
[00075699][12 03][00] v1.10.0.0 -> v1.10.0.0
[00075753][15 00][00] v1.1.2.0 -> v1.1.2.0
[00075827][17 00][00] v1.1.1.7 -> v1.1.1.7
[00075950][17 01][00] v1.0.2.7 -> v1.0.2.7
[00076007][19 00][00] v1.0.8.96 -> v1.0.8.96
[00076053][01 00][00] v1.23.4920 -> v1.23.4920
[00076106][01 01][00] v1.23.4920 -> v1.23.4920
[00076167][09 00][00] v2.13.0.0 -> v2.13.0.0
[00076212]Packet upgrade finish successfully.



[00010201]========== remo-con disconnect. boot(15) ============
[00010246]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x285538cf].
[00010291]Packet upgrade start...

[00010349]Packet checking...
[00010394]Packet vlink 01.08.0080 <-> 01.07.0060.
[00010443]Record vlink 01.07.0060 <-> 01.06.0040 (flow = 0).
[00010493]Done.

[00010543]Version checking[1]...
[00010628][03 05][00] v34.2.0.9 -> v34.2.0.9
[00010724][03 06][00] v2.4.13.0 -> v2.4.14.5 need upgrade.
[00010774][04 00][00] v1.41.0.0 -> v1.44.0.0 need upgrade.
[00010924][11 00][00] v1.7.15.1 -> v1.7.15.1
[00011023][12 00][00] v1.10.0.0 -> v1.10.0.0
[00011124][12 01][00] v1.10.0.0 -> v1.10.0.0
[00011230][12 02][00] v1.10.0.0 -> v1.10.0.0
[00011330][12 03][00] v1.10.0.0 -> v1.10.0.0
[00015987][15 00][00] v1.1.2.0 -> v1.1.2.0
[00016085][17 00][00] v1.1.1.7 -> v1.1.1.7
[00016231][17 01][00] v1.0.2.7 -> v1.0.2.7
[00016296][19 00][00] v1.0.8.96 -> v1.0.8.96
[00016345][01 00][00] v1.23.4920 -> v1.23.4920
[00016396][01 01][00] v1.23.4920 -> v1.23.4920
[00016457][09 00][00] v2.13.0.0 -> v3.0.0.10 need upgrade.
[00016502]Done.

[00018554]Waiting for user confirm...
[00028600]Timeout, start upgrade automatically.

[00028688]Firmware upgrading[1]...
[00028920][03 06] Firmware upgrade start...
[00680665][03 06] Firmware upgrade finish failed (step = 4, err = 0xaa, idx = 0, los = 30, ng = 0).
[00710746][09 00] Firmware upgrade start...
[00762690][09 00] Firmware upgrade finished successfully.
[00762762][04 00] Firmware upgrade start...
[00821770][04 00] Firmware upgrade finished successfully.
[00821825]Done.

[00821871]Version checking[2]...
[00834417][03 05][00] device not detected.
[00846967][03 06][06] device not detected.
[00847024][04 00][05] v1.44.0.0 -> v1.44.0.0
[00859575][11 00][00] device not detected.
[00872119][12 00][00] device not detected.
[00884667][12 01][00] device not detected.
[00897214][12 02][00] device not detected.
[00909767][12 03][00] device not detected.
[00909823][15 00][00] v1.1.2.0 -> v1.1.2.0
[00922369][17 00][00] device not detected.
[00934916][17 01][00] device not detected.
[00935007][19 00][00] v1.0.8.96 -> v1.0.8.96
[00935054][01 00][00] v1.23.4920 -> v1.23.4920
[00935105][01 01][00] v1.23.4920 -> v1.23.4920
[00935168][09 00][05] v3.0.0.10 -> v3.0.0.10
[00935214]Packet upgrade failed at version checking.



[00012201]========== remo-con disconnect. boot(15) ============
[00012254]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x285538cf].
[00012299]Packet upgrade start...

[00012355]Packet checking...
[00012406]Packet vlink 01.08.0080 <-> 01.07.0060.
[00012452]Record vlink 01.07.0060 <-> 01.06.0040 (flow = 0).
[00012497]Done.

[00012550]Version checking[1]...
[00012773][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012853][03 06][00] v0.0.0.0 -> v2.4.14.5 need upgrade.
[00012916][04 00][00] v1.44.0.0 -> v1.44.0.0
[00025467][11 00][00] device not detected.
[00038028][12 00][00] device not detected.
[00050576][12 01][00] device not detected.
[00063127][12 02][00] device not detected.
[00014324]========== remo-con disconnect. boot(15) ============
[00014383]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x285538cf].
[00014431]Packet upgrade start...

[00014495]Packet checking...
[00014543]Packet vlink 01.08.0080 <-> 01.07.0060.
[00014588]Record vlink 01.07.0060 <-> 01.06.0040 (flow = 0).
[00014637]Done.

[00014692]Version checking[1]...
[00014764][03 05][00] v34.2.0.9 -> v34.2.0.9
[00014845][03 06][00] v0.0.0.0 -> v2.4.14.5 need upgrade.
[00014914][04 00][00] v1.44.0.0 -> v1.44.0.0
[00027463][11 00][00] device not detected.
[00040014][12 00][00] device not detected.
[00052564][12 01][00] device not detected.
[00065120][12 02][00] device not detected.
[00077674][12 03][00] device not detected.
[00077732][15 00][00] v1.1.2.0 -> v1.1.2.0
[00090279][17 00][00] device not detected.
[00102835][17 01][00] device not detected.
[00102899][19 00][00] v1.0.8.96 -> v1.0.8.96
[00102947][01 00][00] v1.23.4920 -> v1.23.4920
[00102999][01 01][00] v1.23.4920 -> v1.23.4920
[00103079][09 00][00] v3.0.0.10 -> v3.0.0.10
[00103134]Done.

[00105181]Waiting for user confirm...
[00115236]Timeout, start upgrade automatically.

[00115343]Firmware upgrading[1]...
[00115576][03 06] Firmware upgrade start...
[00446215][03 06] Firmware upgrade finished successfully.
[00446264]Done.

[00446308]Version checking[2]...
[00446402][03 05][00] v34.2.0.9 -> v34.2.0.9
[00446503][03 06][05] v2.4.14.5 -> v2.4.14.5
[00446559][04 00][00] v1.44.0.0 -> v1.44.0.0
[00446684][11 00][00] v1.7.15.1 -> v1.7.15.1
[00446790][12 00][00] v1.10.0.0 -> v1.10.0.0
[00446896][12 01][00] v1.10.0.0 -> v1.10.0.0
[00446995][12 02][00] v1.10.0.0 -> v1.10.0.0
[00447235][12 03][00] v1.10.0.0 -> v1.10.0.0
[00447297][15 00][00] v1.1.2.0 -> v1.1.2.0
[00447391][17 00][00] v1.1.1.7 -> v1.1.1.7
[00447531][17 01][00] v1.0.2.7 -> v1.0.2.7
[00447602][19 00][00] v1.0.8.96 -> v1.0.8.96
[00447658][01 00][00] v1.23.4920 -> v1.23.4920
[00447706][01 01][00] v1.23.4920 -> v1.23.4920
[00447781][09 00][00] v3.0.0.10 -> v3.0.0.10
[00447828]Packet upgrade finish successfully.



[00010793]========== remo-con disconnect. boot(15) ============
[00010845]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00010892]Packet upgrade start...

[00010955]Packet checking...
[00011007]Packet vlink 01.07.0060 <-> 01.06.0040.
[00011056]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 1).
[00011102]Done.

[00011149]Version checking[1]...
[00011226][03 05][00] v34.2.0.9 -> v34.2.0.9
[00011306][03 06][00] v2.4.14.5 -> v2.4.13.0
[00011360][04 00][00] v1.44.0.0 -> v1.41.0.0
[00011467][11 00][00] v1.7.15.1 -> v1.7.15.1
[00011556][12 00][00] v1.10.0.0 -> v1.10.0.0
[00011637][12 01][00] v1.10.0.0 -> v1.10.0.0
[00011717][12 02][00] v1.10.0.0 -> v1.10.0.0
[00011796][12 03][00] v1.10.0.0 -> v1.10.0.0
[00016348][15 00][00] v1.1.2.0 -> v1.1.2.0
[00016438][17 00][00] v1.1.1.7 -> v1.1.1.7
[00016567][17 01][00] v1.0.2.7 -> v1.0.2.7
[00016637][19 00][00] v1.0.8.96 -> v1.0.8.96
[00016684][01 00][00] v1.23.4920 -> v1.23.4920
[00016737][01 01][00] v1.23.4920 -> v1.23.4920
[00016795][09 00][00] v3.0.0.10 -> v2.13.0.0
[00016848]Packet upgrade cancelled at version checking.



[00010249]========== remo-con disconnect. boot(15) ============
[00010296]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00010349]Packet upgrade start...

[00010399]Packet checking...
[00010453]Packet vlink 01.07.0060 <-> 01.06.0040.
[00010499]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 1).
[00010554]Done.

[00010599]Version checking[1]...
[00010681][03 05][00] v34.2.0.9 -> v34.2.0.9
[00010761][03 06][00] v2.4.14.5 -> v2.4.13.0
[00010954][04 00][00] v1.44.0.0 -> v1.41.0.0
[00011061][11 00][00] v1.7.15.1 -> v1.7.15.1
[00011155][12 00][00] v1.10.0.0 -> v1.10.0.0
[00011265][12 01][00] v1.10.0.0 -> v1.10.0.0
[00011361][12 02][00] v1.10.0.0 -> v1.10.0.0
[00011450][12 03][00] v1.10.0.0 -> v1.10.0.0
[00016006][15 00][00] v1.1.2.0 -> v1.1.2.0
[00016090][17 00][00] v1.1.1.7 -> v1.1.1.7
[00016231][17 01][00] v1.0.2.7 -> v1.0.2.7
[00016290][19 00][00] v1.0.8.96 -> v1.0.8.96
[00016347][01 00][00] v1.23.4920 -> v1.23.4920
[00016400][01 01][00] v1.23.4920 -> v1.23.4920
[00016471][09 00][00] v3.0.0.10 -> v2.13.0.0
[00016518]Packet upgrade cancelled at version checking.



[00010827]========== remo-con disconnect. boot(15) ============
[00010875]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00010922]Packet upgrade start...

[00010973]Packet checking...
[00011030]Packet vlink 01.07.0060 <-> 01.06.0040.
[00011078]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 1).
[00011128]Done.

[00011176]Version checking[1]...
[00011264][03 05][00] v34.2.0.9 -> v34.2.0.9
[00011344][03 06][00] v2.4.14.5 -> v2.4.13.0
[00011398][04 00][00] v1.44.0.0 -> v1.41.0.0
[00011524][11 00][00] v1.7.15.1 -> v1.7.15.1
[00011613][12 00][00] v1.10.0.0 -> v1.10.0.0
[00011715][12 01][00] v1.10.0.0 -> v1.10.0.0
[00011792][12 02][00] v1.10.0.0 -> v1.10.0.0
[00011894][12 03][00] v1.10.0.0 -> v1.10.0.0
[00016446][15 00][00] v1.1.2.0 -> v1.1.2.0
[00016528][17 00][00] v1.1.1.7 -> v1.1.1.7
[00016658][17 01][00] v1.0.2.7 -> v1.0.2.7
[00016734][19 00][00] v1.0.8.96 -> v1.0.8.96
[00016781][01 00][00] v1.23.4920 -> v1.23.4920
[00016834][01 01][00] v1.23.4920 -> v1.23.4920
[00016893][09 00][00] v3.0.0.10 -> v2.13.0.0
[00016941]Packet upgrade cancelled at version checking.



[00012332]========== remo-con disconnect. boot(15) ============
[00012380]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00012425]Packet upgrade start...

[00012585]Packet checking...
[00012637]Packet vlink 01.07.0060 <-> 01.06.0040.
[00012685]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 1).
[00012734]Done.

[00012782]Version checking[1]...
[00012868][03 05][00] v34.2.0.9 -> v34.2.0.9
[00012947][03 06][00] v2.4.14.5 -> v2.4.13.0
[00013001][04 00][00] v1.44.0.0 -> v1.41.0.0
[00013147][11 00][00] v1.7.15.1 -> v1.7.15.1
[00013238][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013331][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013416][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013516][12 03][00] v1.10.0.0 -> v1.10.0.0
[00018069][15 00][00] v1.1.2.0 -> v1.1.2.0
[00018158][17 00][00] v1.1.1.7 -> v1.1.1.7
[00018281][17 01][00] v1.0.2.7 -> v1.0.2.7
[00018357][19 00][00] v1.0.8.96 -> v1.0.8.96
[00018410][01 00][00] v1.23.4920 -> v1.23.4920
[00018461][01 01][00] v1.23.4920 -> v1.23.4920
[00018516][09 00][00] v3.0.0.10 -> v2.13.0.0
[00018572]Packet upgrade cancelled at version checking.



[00012666]========== remo-con disconnect. boot(15) ============
[00012713]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x285538cf].
[00012764]Packet upgrade start...

[00012816]Packet checking...
[00012866]Packet vlink 01.08.0080 <-> 01.07.0060.
[00012914]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 0).
[00012965]Done.

[00013013]Version checking[1]...
[00013094][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013193][03 06][00] v2.4.14.5 -> v2.4.14.5
[00013250][04 00][00] v1.44.0.0 -> v1.44.0.0
[00013373][11 00][00] v1.7.15.1 -> v1.7.15.1
[00013469][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013570][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013668][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013768][12 03][00] v1.10.0.0 -> v1.10.0.0
[00018319][15 00][00] v1.1.2.0 -> v1.1.2.0
[00018422][17 00][00] v1.1.1.7 -> v1.1.1.7
[00018567][17 01][00] v1.0.2.7 -> v1.0.2.7
[00018637][19 00][00] v1.0.8.96 -> v1.0.8.96
[00018686][01 00][00] v1.23.4920 -> v1.23.4920
[00018737][01 01][00] v1.23.4920 -> v1.23.4920
[00018818][09 00][00] v3.0.0.10 -> v3.0.0.10
[00018984]Packet upgrade cancelled at version checking.



[00015442]========== 2016.04.15 12:48:33. boot(15) ============
[00015495]Packet [C:\P3S_FW_V01.08.0080.bin] detected, card sn [0x285538cf].
[00015557]Packet upgrade start...

[00015615]Packet checking...
[00015669]Packet vlink 01.08.0080 <-> 01.07.0060.
[00015719]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 0).
[00015773]Done.

[00015826]Version checking[1]...
[00015925][03 05][00] v34.2.0.9 -> v34.2.0.9
[00016023][03 06][00] v2.4.14.5 -> v2.4.14.5
[00016086][04 00][00] v1.44.0.0 -> v1.44.0.0
[00016225][11 00][00] v1.7.15.1 -> v1.7.15.1
[00016332][12 00][00] v1.10.0.0 -> v1.10.0.0
[00016431][12 01][00] v1.10.0.0 -> v1.10.0.0
[00016538][12 02][00] v1.10.0.0 -> v1.10.0.0
[00016627][12 03][00] v1.10.0.0 -> v1.10.0.0
[00016683][15 00][00] v1.1.2.0 -> v1.1.2.0
[00016787][17 00][00] v1.1.1.7 -> v1.1.1.7
[00016927][17 01][00] v1.0.2.7 -> v1.0.2.7
[00017003][19 00][00] v1.0.8.96 -> v1.0.8.96
[00017055][01 00][00] v1.23.4920 -> v1.23.4920
[00017122][01 01][00] v1.23.4920 -> v1.23.4920
[00017203][09 00][00] v3.0.0.10 -> v3.0.0.10
[00017255]Packet upgrade cancelled at version checking.



[00012697]========== remo-con disconnect. boot(15) ============
[00012748]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00012804]Packet upgrade start...

[00012862]Packet checking...
[00012915]Packet vlink 01.07.0060 <-> 01.06.0040.
[00012971]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 1).
[00013027]Done.

[00013081]Version checking[1]...
[00013181][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013281][03 06][00] v2.4.14.5 -> v2.4.13.0
[00013342][04 00][00] v1.44.0.0 -> v1.41.0.0
[00013480][11 00][00] v1.7.15.1 -> v1.7.15.1
[00013585][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013689][12 01][00] v1.10.0.0 -> v1.10.0.0
[00013789][12 02][00] v1.10.0.0 -> v1.10.0.0
[00013921][12 03][00] v1.10.0.0 -> v1.10.0.0
[00013976][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014065][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014345][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014416][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014470][01 00][00] v1.23.4920 -> v1.23.4920
[00014529][01 01][00] v1.23.4920 -> v1.23.4920
[00014594][09 00][00] v3.0.0.10 -> v2.13.0.0
[00014650]Packet upgrade cancelled at version checking.



[00012874]========== 2016.04.15 15:57:23. boot(15) ============
[00012928]Packet [C:\P3S_FW_V01.07.0060.bin] detected, card sn [0x285538cf].
[00012982]Packet upgrade start...

[00013050]Packet checking...
[00013103]Packet vlink 01.07.0060 <-> 01.06.0040.
[00013157]Record vlink 01.08.0080 <-> 01.07.0060 (flow = 1).
[00013215]Done.

[00013271]Version checking[1]...
[00013376][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013476][03 06][00] v2.4.14.5 -> v2.4.13.0
[00013540][04 00][00] v1.44.0.0 -> v1.41.0.0
[00013673][11 00][00] v1.7.15.1 -> v1.7.15.1
[00013785][12 00][00] v1.10.0.0 -> v1.10.0.0
[00013910][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014020][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014144][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014199][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014300][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014440][17 01][00] v1.0.2.7 -> v1.0.2.7
[00014517][19 00][00] v1.0.8.96 -> v1.0.8.96
[00014570][01 00][00] v1.23.4920 -> v1.23.4920
[00014622][01 01][00] v1.23.4920 -> v1.23.4920
[00014711][09 00][00] v3.0.0.10 -> v2.13.0.0
[00014764]Packet upgrade cancelled at version checking.

DJI-Ken Posted at 2016-4-25 17:41
My only idea is that you reset the home point to the aircraft as you were flying by that location.
...

So, when the home point jumped on the map, from where I was flying, to a block away... was because the phantom lost all GPS signal.. and regained GPS signal and it thought the home point -reset to a block away?  - and it started to head "home" because it was over 1000 m out of the max distance (200 m) in the parameters I set.
...... that's crazy!  
If I was a beinnger pilot , or if the drone found the GPS location to be a major road intersection or highway.. then that would have cost lives. Do you not agree?
Was this user error. that the drone lost GPS signal and then set the home to a place it was not even flying......


When I hit "Set current position as homepoint" during flight, in the app.

I plan on testing it out again- because I miraculously got my drone back.
But if I lost my drone from that morning? - then DJI would do nothing.... because I would have nothing to send in for any diagnosis ... that really really sucks...   
thanks for your response DJI- Ken.

t2adze Posted at 2016-4-26 23:08
Sure.

[00022434]========== remo-con disconnect. boot(15) ============

Looks like there is many different tries here. format the SD card and install 1.8 from the Advanced page.
Then post the hidden file. Only attempt the update once.
I've also contacted the German repair center and if you can include the hidden log file in the RMA email as well.

ryanlam115@gmai Posted at 2016-4-27 03:24
So, when the home point jumped on the map, from where I was flying, to a block away... was because  ...

The home point can ONLY change if you changed it. If you lose GPS for a few, your original home point is the same place as you took off from.
You can easily see this by playing back the flight in the flight records tab.
What is your email and I will also look. Sync your flight records and star the flight in question as a favorite and I will look at the flight log.

DJI-Ken Posted at 2016-4-26 15:48
The home point can ONLY change if you changed it. If you lose GPS for a few, your original home po ...

Thanks for your response,
https://youtu.be/XlM0eYIGYsE
Note 3:00 - 3:45 onwards.
The home point set a block away. I did not ask to set home point so far away. I selected set current position as homepoint. Clearly the drone was not even close to the new home point.

Would atti mode have allowed it to fly back to me?
I plan on testing this in a few days. I hope atti mode will work, or else it might get lost for real this time.

Sorry for my late response. Had no time with my work.
I got contacted by DJI Germany, and they said they would repair it. So i sent it to them, 60$ for shipping to Germany.
So it will take up to 10 b.days to deliver there. another 14 to fix/replace. and probably another 10 to get back to me.
So somewhere in month and a half illprobably be up and flying again

Thank you for you support and help everyone!

DJI-Ken Posted at 2016-4-26 23:48
The home point can ONLY change if you changed it. If you lose GPS for a few, your original home po ...

Guys i have an issue.
I sent the aircraft to the address told me by DJI Germany
which is also menntioned here.

HERE

It got delivered there couple of days ago, and nobody is getting in touch with me. The RMA on the page says my name, but doesnt update the status that they received the aircraft.
Guy who was in touch with me via emails stopped replying to my emails.
Support.eu@dji.com also doesnt reply to the ticket it created.
Im calling the number, and even though i am calling in working hours, it says that the office is closed call us in working hours.

Srsly, what is going on?

t2adze Posted at 2016-5-5 09:26
Guys i have an issue.
I sent the aircraft to the address told me by DJI Germany
which is also mennt ...

T2,

Four days ago you posted that it could take up to a month and a half to get it back. My suggestion would be to let it rest for a few weeks and see what happens. Ken is a good guy, I'm sure he'll keep it in the back of his head. If you don't hear something in a few weeks, let him know. DJI is a "BIG" company with a lot of repairs. It's going to take a while. At least you're in a better place than you were before. Just my opinion, of course.

Jerry

t2adze Posted at 2016-5-6 00:26
Guys i have an issue.
I sent the aircraft to the address told me by DJI Germany
which is also mennt ...

stop hassling ppl...its sent, they have it...it will be sent back when fixed....there are many other ppl with real issues not just screwed up firmware they themselves have caused.

JtrJr-UAV Pilot Posted at 2016-5-5 18:50
T2,

Four days ago you posted that it could take up to a month and a half to get it back. My sugge ...

Jerry Hey!

Yes i know that's how long it will take. But at least to know that it is delivered, and that they received it. Some kind of confirmation from them.
Nobody answers even the phone number, when it's the working hours.
I know Ken is a great guy and so are you, and i am very thankful to you both for all the help that you provided!
Just it's very strange behaviour from the company like this not answering the phone and the emails for 4- days already.

Hope alll will be well!

Thunderbirdsare Posted at 2016-5-5 20:55
stop hassling ppl...its sent, they have it...it will be sent back when fixed....there are many oth ...

First of all, i did everything correct when updating the firmware. Not the first time updating it. Better go through the history first.
Second of all, the company should at least answer the phone calls or emails - at least once in 4 days. I sent my AC. I want to know if they got it. Confirmation from them and not only DHL.
Third - Please mind your own real issues.

Thanks.

Thunderbirdsare Posted at 2016-5-5 11:55
stop hassling ppl...its sent, they have it...it will be sent back when fixed....there are many oth ...

Thunder,

Come on, ease up Man. This thread was created to help T2 with his issues, not others. If anyone else needs help they can create their own thread.

Jerry

t2adze Posted at 2016-5-5 12:29
First of all, i did everything correct when updating the firmware. Not the first time updating it.  ...

T2,

Stay out of the fray. Stay focused on your bird. Give it some time. If you start pestering people, you'll get no where. I'll be watching too. I just want you to get a working bird back. Chill, let things go for a bit.

Jerry

JtrJr-UAV Pilot Posted at 2016-5-5 21:38
T2,

Stay out of the fray. Stay focused on your bird. Give it some time. If you start pestering pe ...

Sure my friend, no problem.Probably i didn't express myself correctly in the first post I just got confused with them not picking up the phone or answering the emails/tickets. That's all I have acknowledged the fact that i will have to wait for a while, until i'm up and flying again.
Thanks again for your support! God bless you!
Regards

JtrJr-UAV Pilot Posted at 2016-5-6 01:35
Thunder,

Come on, ease up Man. This thread was created to help T2 with his issues, not others. If ...

Why start 47 threads all dealing with the same issues .   DJI needs to get this 1 corrected fast

t2adze Posted at 2016-5-5 12:47
Sure my friend, no problem.Probably i didn't express myself correctly in the first post  I just  ...

T2,

No problem. I'll be around waiting for this to get resolved as well. Jut don't get too worked up, it'll work out. I know Ken will keep an eye out as well. I don't talk to him very much but when I reach out, he's always there.

(Ken, BTW I love my P3's and my P2. I felt like I had to stop updating things and my birds are flying great! Thanks for all of the support you've given me.)

Jerry

Show Me Drone Posted at 2016-5-5 12:48
Why start 47 threads all dealing with the same issues .   DJI needs to get this 1 corrected fast

Show,

Jeez, you guys just won't give it a break, will you? I've sought help here and got it, if you're going to tag on someone else's thread, you're going to get nowhere. Start a thread explaining your specific problem and I'll (and others will) try to help. T2 is in the middle of nowhere, he really needs some help. Where are you? What do you need help with? Please don't respond to me in this thread, start your own and tag me. I'll help if I can.

Jerry