geekman / xqrepack

patch XiaoQiang images to maintain SSH & UART access
136 stars 42 forks source link

Redmi AX5 full nand dump backup? #22

Open love4life048 opened 2 years ago

love4life048 commented 2 years ago

Hi, does anyone have the full nand dump of Redmi AX5 (Xiaomi AX1800) or at least mtd1 partion? Please help me! Thank you very much.

KaMyKaSii commented 2 years ago

I made a backup of mtd1 from my Redmi AX5 (Chinese) with nanddump tool, hope it is enough.

root@XiaoQiang:~# nanddump --file /tmp/mtd1.bin /dev/mtd1
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00100000...
root@XiaoQiang:~# stat /tmp/mtd1.bin
  File: /tmp/mtd1.bin
  Size: 1048576         Blocks: 2048       IO Block: 4096   regular file
Device: eh/14d  Inode: 271975      Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2022-03-17 19:57:35.000000000
Modify: 2022-03-17 19:57:35.000000000
Change: 2022-03-17 19:57:35.000000000

mtd1.bin.zip

love4life048 commented 2 years ago

Thank you very much, can you share me full mtd from mtd0 and mtd7 ( SLB and APPSLB partition). Thank you and thank you.

KaMyKaSii commented 2 years ago

mtd0-mtd7.zip

KaMyKaSii commented 2 years ago

@love4life048 did you manage to revive your AX5? How did you brick it?

love4life048 commented 2 years ago

I flash wrong firmware so my AX5 bricked :( I use your mtd backup to revive but the nand have a lots of bad sectors, I have to change the new nand. However I need full mtd backup (from mtd0, mtd1,…,to mtd18) to work with the flash memory prgrammer . Would you please help me one more time. Thank you very much! 7B5AE314-8E06-400D-A0E9-70AF0636C948

KaMyKaSii commented 2 years ago

The partition table of my Chinese Redmi AX5 (with the latest firmware 1.0.49 if relevant) is different from the one you sent and which is on the OpenWrt page. Maybe it's that of the global Redmi AX1800?

root@XiaoQiang:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00180000 00020000 "0:SBL1"
mtd1: 00100000 00020000 "0:MIBIB"
mtd2: 00380000 00020000 "0:QSEE"
mtd3: 00080000 00020000 "0:DEVCFG"
mtd4: 00080000 00020000 "0:RPM"
mtd5: 00080000 00020000 "0:CDT"
mtd6: 00080000 00020000 "0:APPSBLENV"
mtd7: 00180000 00020000 "0:APPSBL"
mtd8: 00080000 00020000 "0:ART"
mtd9: 00080000 00020000 "bdata"
mtd10: 00080000 00020000 "crash"
mtd11: 00080000 00020000 "crash_syslog"
mtd12: 00080000 00020000 "0:BOOTCONFIG"
mtd13: 00080000 00020000 "0:BOOTCONFIG1"
mtd14: 00380000 00020000 "0:QSEE_1"
mtd15: 00080000 00020000 "0:DEVCFG_1"
mtd16: 00080000 00020000 "0:RPM_1"
mtd17: 00080000 00020000 "0:CDT_1"
mtd18: 02400000 00020000 "rootfs"
mtd19: 02400000 00020000 "rootfs_1"
mtd20: 024a0000 00020000 "overlay"
mtd21: 00080000 00020000 "cfg_bak"
mtd22: 003a2000 0001f000 "kernel"
mtd23: 01303000 0001f000 "ubi_rootfs"
mtd24: 00953000 0001f000 "rootfs_data"
mtd25: 02093000 0001f000 "data"

This time I used the script on this page that uses dd to make the backup. I had to edit the script and remove the mtd24,25 backup because they both led to error and canceled the whole operation, I think maybe it's because the partitions are mounted. I compared the checksum from mtd0,1,7 with the previous backups I made with nanddump and they are all the same so I think there is no problem. I hope it helps you. https://drive.google.com/file/d/10-ABUfQ__hYIAnZMFSmY44kwoKl2fNAD/view?usp=sharing

love4life048 commented 2 years ago

Thank you very much, I'll try to save my AX5

lutfor-diu commented 5 days ago

The partition table of my Chinese Redmi AX5 (with the latest firmware 1.0.49 if relevant) is different from the one you sent and which is on the OpenWrt page. Maybe it's that of the global Redmi AX1800?

root@XiaoQiang:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00180000 00020000 "0:SBL1"
mtd1: 00100000 00020000 "0:MIBIB"
mtd2: 00380000 00020000 "0:QSEE"
mtd3: 00080000 00020000 "0:DEVCFG"
mtd4: 00080000 00020000 "0:RPM"
mtd5: 00080000 00020000 "0:CDT"
mtd6: 00080000 00020000 "0:APPSBLENV"
mtd7: 00180000 00020000 "0:APPSBL"
mtd8: 00080000 00020000 "0:ART"
mtd9: 00080000 00020000 "bdata"
mtd10: 00080000 00020000 "crash"
mtd11: 00080000 00020000 "crash_syslog"
mtd12: 00080000 00020000 "0:BOOTCONFIG"
mtd13: 00080000 00020000 "0:BOOTCONFIG1"
mtd14: 00380000 00020000 "0:QSEE_1"
mtd15: 00080000 00020000 "0:DEVCFG_1"
mtd16: 00080000 00020000 "0:RPM_1"
mtd17: 00080000 00020000 "0:CDT_1"
mtd18: 02400000 00020000 "rootfs"
mtd19: 02400000 00020000 "rootfs_1"
mtd20: 024a0000 00020000 "overlay"
mtd21: 00080000 00020000 "cfg_bak"
mtd22: 003a2000 0001f000 "kernel"
mtd23: 01303000 0001f000 "ubi_rootfs"
mtd24: 00953000 0001f000 "rootfs_data"
mtd25: 02093000 0001f000 "data"

This time I used the script on this page that uses dd to make the backup. I had to edit the script and remove the mtd24,25 backup because they both led to error and canceled the whole operation, I think maybe it's because the partitions are mounted. I compared the checksum from mtd0,1,7 with the previous backups I made with nanddump and they are all the same so I think there is no problem. I hope it helps you. https://drive.google.com/file/d/10-ABUfQ__hYIAnZMFSmY44kwoKl2fNAD/view?usp=sharing

Your file saved me brother. Just revive my ax5