Problems with recovery of CPE510(EU)1.1
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Problems with recovery of CPE510(EU)1.1
Model : Hardware Version : Firmware Version : ISP : Hello, a friend asked for help with a CPE510 with a bad flash. Recovery as described on this forum and TP-Link support resources has failed, so I connected a serial console to see what is going on: TP-LINK SafeLoader (Build time: Jun 12 2015 - 09:49:53) CPU: 560MHz AHB: 225MHz DDR: 64MB Performing LED check.. PASS Press CTRL+B to enter SafeLoader: 1 Flash Manufacturer: Unknown(0xc8) Flash Device ID: Unknown(0x4017) Data flash init failed. open user-config failed. open user-config failed. enet0 port4 up TFTP server address is 192.168.0.100; our address is 192.168.0.254 Get filename 'recovery.bin'. ################################################################# ###################### Done. Bytes transferred = 4453887, 2938 Kbytes/sec Incorrect File. Writting error. ##Warning: File is unidentiable. Try downloading TFTP server address is 192.168.0.100; our address is 192.168.0.254 Get filename 'vmlinuz'. TFTP error: Starting again. ##ERROR: Can't download image. Input Password: ------------------ I cannot seem to log in to the bootloader with the password "admin". (Also "tpl", als used on some other devices, won't let me log in). Pressing CTRL-B on boot seems to bring up the mode TFTP directly, but with the same results. I've - so far - tried different versions of the Pharos firmware starting with 1.0.0P25 to 2.1.6P4 - each time I get this error: Incorrect File. Writting error. ##Warning: File is unidentiable. Try downloading Any hints on how I can access the SafeLoader (=password) in order to format the flash before retrying? Do I have to (as opposed to the recovery instructions) strip off a header of the binary firmware image in order to flash it? Thank you and best regards Epek [UPDATE]: I managed to compile an OpenWRT kernel+initramfs and renamed it to vmlinuz (I had to give partition sizes and names as a LINUX_CMDLINE). I was able to boot that firmware into CPE510's RAM. From there I could mtd erase kernel and rootfs and managed to place at least an original kernel image of the Pharos Firmware onto /dev/mtdblock3. Unfortunately I rebooted soon after, but did not copy the rootfs partition from the Pharos firmware to /dev/mtdblock4 before that... So I am now stuck in a loop. The full pharos firmware image recovery.img fails to load (see above). Vmlinuz will no longer be loaded via TFTP, because it is locally available. SafeLoader asks for a password, that is not "admin", so I am unable to reformat partition 3.... What's going on with SafeLoader? Is there any way to make SafeLoader overwrite at least the kernel partition somehow, so that it will load vmlinuz from TFTP again?
