So I received a new Mavic, got it from the box and remote was always in "connecting" mode. I tried to plug in my iPhone but it didn't see the remote either.
That was the first time it happened and that's how I fixed it:
1. Connected RC to my Mac and Launched DJI Assistant 2 app.
2. Downgraded firmware to 03.0400 and it succeeded.
3. Upgraded to 03.0500 and it failed.
4. Repeated steps 2&3 around 5-7 times, and then it finally succeeded. I'm not sure what changed during the process.
5. Upgraded to 03.0550 and was good to go.
Then, few days later 03.0600 came out. I upgraded with DJI Go app on my iPhone and it succeeded. I used my drone for a week after that.
Then, I started my trip to Ecuador and just when I arrived here I noticed that my RC is again in this weird "connecting" mode. It doesn't connect to the drone, doesn't connect to my iPhone, doesn't enter the pairing mode through C1 and C2 and shutter buttons. On the other side the remote DOES charge my iPhone (when it's working normally, it doesn't charge it). Drone is still working over wi-fi connection, though.
So I fire up DJI Assistant on my Mac again, it takes 5 hours to download 03.600 firmware over crappy wi-fi. I'm able to just "Refreshe" it and it succeeds from the first try. So I'm good to go... but only for 2 days.
So, 2 days later I get my remote out of the bag, and holy glory, here we go again, this bloody glitch is back. Remote is AGAIN in "connecting" mode. I come back home hoping to revive it through DJI Assistant app on my Mac, but this time it doesn't work. No matter what firmware I choose (I tried, 03.0400, 03.0550, 03.0600), it always fails the update/downgrade, always at 20%. Sometimes the app warns me that there are "inconsistencies in remote modules", and offers me to fix the issue by updating the firmware. If I agree it successfully goes up to 100%, and firmware seems to be updated, but it doesn't fix the glitch. I tried changing USB cables and usb ports on my mac, but nothing helps.
I also did find DJI Assistant logs on my mac, and I can see that successful update logs from before are different from the logs I'm getting now.
Does anyone has any idea what else can I try?
That was the first time it happened and that's how I fixed it:
1. Connected RC to my Mac and Launched DJI Assistant 2 app.
2. Downgraded firmware to 03.0400 and it succeeded.
3. Upgraded to 03.0500 and it failed.
4. Repeated steps 2&3 around 5-7 times, and then it finally succeeded. I'm not sure what changed during the process.
5. Upgraded to 03.0550 and was good to go.
Then, few days later 03.0600 came out. I upgraded with DJI Go app on my iPhone and it succeeded. I used my drone for a week after that.
Then, I started my trip to Ecuador and just when I arrived here I noticed that my RC is again in this weird "connecting" mode. It doesn't connect to the drone, doesn't connect to my iPhone, doesn't enter the pairing mode through C1 and C2 and shutter buttons. On the other side the remote DOES charge my iPhone (when it's working normally, it doesn't charge it). Drone is still working over wi-fi connection, though.
So I fire up DJI Assistant on my Mac again, it takes 5 hours to download 03.600 firmware over crappy wi-fi. I'm able to just "Refreshe" it and it succeeds from the first try. So I'm good to go... but only for 2 days.
So, 2 days later I get my remote out of the bag, and holy glory, here we go again, this bloody glitch is back. Remote is AGAIN in "connecting" mode. I come back home hoping to revive it through DJI Assistant app on my Mac, but this time it doesn't work. No matter what firmware I choose (I tried, 03.0400, 03.0550, 03.0600), it always fails the update/downgrade, always at 20%. Sometimes the app warns me that there are "inconsistencies in remote modules", and offers me to fix the issue by updating the firmware. If I agree it successfully goes up to 100%, and firmware seems to be updated, but it doesn't fix the glitch. I tried changing USB cables and usb ports on my mac, but nothing helps.
I also did find DJI Assistant logs on my mac, and I can see that successful update logs from before are different from the logs I'm getting now.
Does anyone has any idea what else can I try?
