I bricked my p3s with ftp range mod - let's fix it together

BaDvs3viL · Jun 17, 2016

andrew_by said:
just connect to rx0 and tx0 on a wifi module , speed 115200 .

You are getting further then me, I am just getting garbled crap no matter what baud rate I set. I can tell its the boot sequnce just from watching the garbled crap and watching the LED's

Andreweer · Jun 17, 2016

For Andrey

Sent from my iPhone using PhantomPilots mobile app

andrew_by · Jun 17, 2016

console port i think SOUT and SIN

ElMalo · Jun 17, 2016

andrew_by said:
UPD-we need find HG310.bin -( this is firmware for wifi module) - and boot.bin - this files unpacked from firmware , then put \tmp and update system

Hi, so I got into the serial console, can esc into u-boot or see the same error as you:

init started: BusyBox v1.22.1 (2015-11-16 16:28:58 CST)
starting pid 219, tty '': '/etc/init.d/rcS'
can't run '/etc/init.d/rcS': No such file or directory
can't open /dev/ttyS0: No such file or directory
process '/bin/login' (pid 220) exited. Scheduling for restart.
can't open /dev/ttyS0: No such file or directory

So, could you tell us which software you used to unpack the firmware file? It doesn't seem to be zip-format? And a few more details about how you uploaded the firmware file? Did you write the firmware/flash from u-boot (uploaded with Kermit?), and to which address? I really would not like to mess up this controller more than it is. A step-by-step list of exactly what you did would be very appreciated.

You've really brought us a lot further! Thanks.

beshanoe · Jun 18, 2016

ElMalo said:
. A step-by-step list of exactly what you did would be very appreciated.

I also vote for step-by-step guide!

tommekand · Jun 18, 2016

Hi to all of you

I also vote, as my 5 days old phantom 3 4k is bricked

no vision

sentinel · Jun 18, 2016

It is not clear to me if anyone actually recovered a bricked RC? Up to now I see that some people were able to interrupt the boot process and display what goes wrong during a boot. However, I did not see any recovery action or did I misunderstand something?

Andreweer · Jun 18, 2016

not yet. we need to extract some files from firmware.bin and flash it into the memory of rc.

Ojcze Nasz · Jun 18, 2016

Extracted flash from WORKING remote.

My own remote....

I had to add .txt in order to upload it here.
It's a .tar.gz

Andreweer · Jun 18, 2016

it is working rc or bricked too?
standard / 4k ?

Ojcze Nasz · Jun 18, 2016

My own, working.
It's a dump of /dev/mtd7 which is firmware.

Phantomic · Jun 18, 2016

The console port only has a monitor function then? It cant be used to write back a correct version of just the rcs script file? Just wondering about it, because flashing the wifi module also involves writing to the remote.

Also that u-boot tool.. where is that actually running? If on the remote, how do you get it there?

ElMalo · Jun 18, 2016

Ok, so I got it to boot!!! And it created a WLAN. I've got to do some more testing, but this is very promising.

There seems to be a backup root system. What I did was this:

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

ElMalo · Jun 18, 2016

Finally gained access to root shell. Next step would be to mount mtd3 (the original root filesystem) to somewhere. I chose /tmp/flash:

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. Mine had a lot of ^M in it, which means it was corrupted by ftp from Windows to Unix.

Ojcze Nasz · Jun 18, 2016

ElMalo said:
Finally gained access to root shell. Next step would be to mount mtd3 (the original root filesystem) to somewhere. I chose /tmp/flash:

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. Mine had a lot of ^M in it, which means it was corrupted by ftp from Windows to Unix.

This is exactly IT ! You did it. Congratulations !

ElMalo · Jun 18, 2016

Thanks, after repairing it I just did a reboot and it worked!! This is just amazing. But I'll have to say we all did it. I wouldn't have found this method without the information from you all guys!

Andreweer · Jun 18, 2016

YES! ITS WORKS!
Thank you

and what about phantom?

Ojcze Nasz · Jun 18, 2016

Andreweer said:
YES! ITS WORKS!
Thank you

and what about phantom?

Reflashing from SD card ? You can put firmware on SD and try to reflash. There are instructions somewhere.

Andreweer · Jun 18, 2016

[ 1.460000] VFS: Mounted root (jffs2 filesystem) readonly on device 31:5.

[ 1.470000] Freeing unused kernel memory: 220K (802c9000 - 80300000)

init started: BusyBox v1.22.1 (2015-11-16 16:28:58 CST)

starting pid 219, tty '': '/etc/init.d/rcS'

can't run '/etc/init.d/rcS': Permission denied

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 220) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 221) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 222) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 223) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

Phantom 3 4K

sentinel · Jun 18, 2016

Andreweer said:
[ 1.460000] VFS: Mounted root (jffs2 filesystem) readonly on device 31:5.

[ 1.470000] Freeing unused kernel memory: 220K (802c9000 - 80300000)

init started: BusyBox v1.22.1 (2015-11-16 16:28:58 CST)

starting pid 219, tty '': '/etc/init.d/rcS'

can't run '/etc/init.d/rcS': Permission denied

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 220) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 221) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 222) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

process '/bin/ash --login' (pid 223) exited. Scheduling for restart.

can't open /dev/ttyS0: No such file or directory

Phantom 3 4K

Congratulations! Great work - now the bird and you are all done!