Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 16 to 19 of 19
  1. #16
    I managed to do it too. However, just as mixawy0 - I was only able to revive the bricked device back to OpenWRT. @R1D2 I tried using the uboot, you provided. And even though it is different than the one on my device, I see no change when I use it. I fixed my image with your uboot, and it still works with OpenWRT. However, I still cannot get past the 4th line when connected through the serial interface. And even though it no longer asks for vmlinuz, when trying to autorecover through TFTP, it does not recover anything. The OpenWRT image remains on and working. Can you please provide a full image of your CPE 210 v1.0? I want to try studying it and maybe flashing it. I could try build myself an image of Pharos and your uboot, if I knew at what offset I need to write the Pharos image.

  2. #17

    partition table cpe210

    partition fs-uboot base 0x00000 size 0x20000
    partition partition-table base 0x20000 size 0x02000
    partition default-mac base 0x30000 size 0x00020
    partition product-info base 0x31100 size 0x00100
    partition signature base 0x32000 size 0x00400
    partition os-image base 0x40000 size 0x170000
    partition soft-version base 0x1b0000 size 0x00100
    partition support-list base 0x1b1000 size 0x00400
    partition file-system base 0x1c0000 size 0x600000
    partition user-config base 0x7c0000 size 0x10000
    partition default-config base 0x7d0000 size 0x10000
    partition log base 0x7e0000 size 0x10000
    partition radio base 0x7f0000 size 0x10000

  3. #18
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Quote Originally Posted by jimmytaker View Post
    Can you please provide a full image of your CPE 210 v1.0?
    Sure, no problem. Find attached archive of all 7 partitions. But take care to flash them on correct addresses. When I last checked the OpenWRT partition table, it was different compared to the original CPE partition table. This is the partition table of my CPE210 v1.0 for reference:

    dev:    size   erasesize  name
    mtd0: 00020000 00010000 "u-boot"
    mtd1: 00010000 00010000 "pation-table"
    mtd2: 00010000 00010000 "product-info"
    mtd3: 00180000 00010000 "kernel"
    mtd4: 00600000 00010000 "rootfs"
    mtd5: 00030000 00010000 "config"
    mtd6: 00010000 00010000 "ART"
    This are the md5 checksums of the 7 files in attached ZIP archive:

    MD5 (mtdblock0) = 03af561034b6faf8d93adda8eed591dd
    MD5 (mtdblock1) = f80ba6723eff0da04328c0603543d2c8
    MD5 (mtdblock2) = 5e4589d48005bbf5b17c4025e1123788
    MD5 (mtdblock3) = 8bd33eab4761a483b1cdd146a61eb515
    MD5 (mtdblock4) = 30ad122107b7200d098a15dd5bc1abc7
    MD5 (mtdblock5) = 465d28439117ec959d62c2eed5dba061
    MD5 (mtdblock6) = 5a763917b74cf02a537e69e7f2f730eb
    The password I used to enable ssh was: tp-link. But you will probably want to reset to factory defaults anyway after flashing.

    Good luck!

    PS: I couldn't manage to upload the rootfs partition (mtdblock4), the forum software always throws a "database error". So I have stripped the rootfs from the archive. You can extract the relevant parts from the firmware file. This are the offsets in firmware version 2-0-0-P1[20170301-rel45104]:

    fwup-ptn partition-table base 0x00800 size 0x00800
    fwup-ptn os-image base 0x01000 size 0xcbf8d
    fwup-ptn soft-version base 0xccf8d size 0x00015
    fwup-ptn support-list base 0xccfa2 size 0x0063c
    fwup-ptn file-system base 0xcd5de size 0x3e4001
    Attached Files

  4. #19
    Anyone with a dump of a CPE510? i screwed up ART partition


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2018 TP-LINK Technologies Co., Ltd. All rights reserved.