I did range mod from
Phantom 3 Standard range mod , let's do it together... and now my drone's RC doesn't create Wi-Fi access point. This topic is for those unfortunates who've done the same and don't know how to fix it. So please share your situation and ideas.
I used mac, filezilla and vim to change files. I defenitely forgot to do "chmod +x" which is thought to be crucial.
Today I brought my drone to the official repair service here in Moscow and I'm waiting now for their diagnosis, it should take up to 5 days thay said. It seemed that they have no special instruments for reuploading healthy firmware to RC and drone using service connectors or smth, but who knows..
UPDATE:
With common effort, the way to recover has been discovered. Basically, all you need is to connect to TX, RX, GND pins of Wi-Fi module board with UART TTL adapter and open serial console(see pictures here
I bricked my p3s with ftp range mod - let's fix it together and here
I bricked my p3s with ftp range mod - let's fix it together). Then you should prevent u-boot from loading linux kernel by pressing ESC key and type to u-boot console the next commands(thanks ElMalo):
MI124
DRAM: 32 MB
Flash: 8 MB
In: serial
Out: serial
Err: serial
Press ESC to abort autoboot in 1 seconds
ar7240>
setenv bootargs board=DJI-WM305 console=ttyS0,115200 root=/dev/mtdblock5 init=/sbin/init mtdparts=ath-nor0:256k@0k(u-boot),64k@256k(u-boot-env),896k@320k(kernel1),3008k@1216k(rootfs1),896k@4224k(kernel2),3008k@5120k(rootfs2),64k@8128k(art),3904k@320k(firmware1),3904k@4224k(firmware2),8192k@0k(all)
And then
ar7240>
bootm 0x9f420000
This will allow you to boot backup copy of system. After that you'll be able to mount main root filesystem:
mkdir /tmp/flash
And then mount it:
mount -t jffs2 mtd3 /tmp/flash
Then you can go to /tmp/flash/etc/init.d and repair the rcS.