LEDE Project

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity High
  • Priority Very Low
  • Reported Version lede-17.01
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 1
  • Private
Attached to Project: LEDE Project
Opened by Jose Ignacio Guzman - 12.07.2017

FS#902 - Unable to restore stock ROM in TP-Link CPE210 HW 1.1 after flashing LEDE

Hello

Has anybody tried to restore stock ROM in CPE210 hardware version 1.1. after flashing LEDE? I have reviewed TP-LinkĀ“s forum and it seems it is not possible. People has tried the Pharos OS TFTP recovery (http://forum.tp-link.com/showthread.php?81684-How-to-use-firmware-recovery-function-of-Pharos-CPE1) as well as from the OpenWRT/LEDE web GUI, and both fail.

Everybody labels flashing to OpenWRT or LEDE as “one-way” action because they suspect that OpenWRT/LEDE “changes something” in the flash, so it breaks a restore to stock ROM . Bellow I list them:

1) OpenWRT/LEDE misses partitions of the stockROM partitions. Bellow is the partition table with stock ROM:

U-Boot partition
partition fs-uboot base 0×00000 size 0×20000 partition partition-table base 0×20000 size 0×02000

Firmware partitions
fwup-ptn partition-table base 0×00800 size 0×00800 fwup-ptn os-image base 0×01000 size 0xcbf29
fwup-ptn soft-version base 0xccf29 size 0×00015 fwup-ptn support-list base 0xccf3e size 0x0063c
fwup-ptn file-system base 0xcd57a size 0x3e4001

2) OpenWRT/LEDE changes something in the environment of the SafeLoader, which breaks the standard recovery mode.

3) Log from an attempt to transfer recovery.bin (the recovery.bin file is firmware pharos-up-ver1-3-3-P9[20160705-rel52453].bin). Safeloader request a “vmlinuz” file from the TFTP ad, of course, it does not exists.

Connection received from 192.168.0.254 on port 4011 [16/03 07:27:19.543]
Read request for file <recovery.bin>. Mode octet [16/03 07:27:19.543]
OACK: <timeout=5,blksize=512,> [16/03 07:27:19.823]
Using local port 49447 [16/03 07:27:19.823]
<recovery.bin>: sent 9643 blks, 4936747 bytes in 2 s. 0 blk resent [16/03 07:27:21.708]
Connection received from 192.168.0.254 on port 3164 [16/03 07:27:24.831]
Read request for file <vmlinuz>. Mode octet [16/03 07:27:24.831]
File <vmlinuz> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [16/03 07:27:24.831]

I think it is important to check and solve it, because this behavior avoids warranty.

Javier commented on 27.07.2017 21:53

I can confirm this bug... and is even worse, you cannot upload even lede fimware...+

Trying to upload lede firmware as recovery.... log:

Connection received from 192.168.0.254 on port 4009 [27/07 23:41:57.485]
Read request for file <recovery.bin>. Mode octet [27/07 23:41:57.485]
OACK: <timeout=5,> [27/07 23:41:57.486]
Using local port 64947 [27/07 23:41:57.486]
<recovery.bin>: sent 6965 blks, 3565777 bytes in 6 s. 0 blk resent [27/07 23:42:03.914]
Connection received from 192.168.0.254 on port 3146 [27/07 23:42:06.986]
Read request for file <vmlinuz>. Mode octet [27/07 23:42:06.987]
File <vmlinuz> : error 2 in system call CreateFile El sistema no puede encontrar el archivo especificado. [27/07 23:42:06.987]

Javier commented on 27.07.2017 23:10

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing