Help HOW TO UNBRICK ZLT S10 via UART

[odilonser1]

Hello, everyone,
do you have any idea to unbrick ZLT S10 using UART method ?
I change index home page file on it and after the device can't boot correctly.

When i try to Open the Serial Com port with Putty, (rx, tx, gnd)
it detected but the u-boot loading is still looping.

Thank you

.

Logs...
Inc zloader 1.3.4 spi-nand:init ok. bbt ok. read uboot ok. start uboot... U-Boot 2011.09 (Mar 12 2022 - 21:11:22) for ZXIC U-Boot code: 0x23DF0000 -> 0x23E3FF24 BSS: -> 0x23F021CC CPU: ZX297520V3 Board: ZX297520V3 monitor len: 0x00200000 ramsize: 0x04000000 TLB table at: 0x23ff0000 Top of RAM usable for U-Boot at: 0x23ff0000 Reserving 2048k for U-Boot at: 0x23df0000 Reserving 16k for nand dma buffer at: 0x23dec000 Reserving 2080k for malloc() at: 0x23be4000 Reserving 24 Bytes for Board Info at: 0x23be3fe8 Reserving 120 Bytes for Global Data at: 0x23be3f70 New Stack Pointer is: 0x23be3f60 RAM Configuration: Bank #0: 0x20000800 64 MiB relocation Offset is: 0x00000000 dram_bank_mmu_setup: bank: 0 monitor flash len: 0x0004FF24 Now running in RAM - U-Boot at: 0x23DF0000 Using default environment Destroy Hash Table: 23e40404 table = (null) Create Hash Table: N=91 DELETE CANDIDATE: "bootargs" hdelete: DELETE key "bootargs" DELETE ERROR ############################## INSERT: free(data = 23be8008) INSERT: done In: serial Out: serial Err: serial [UBOOT]NOTICE->[sys_entry]<520>sys_entry ... [UBOOT]NOTICE->[uboot_init_func]<461>go into uboot init func [UBOOT]NOTICE->[uboot_init_func]<474>uboot init pull on pshold success [sys_entry_wdt]: watchdog no reset! [UBOOT]NOTICE->[uboot_init_func]<474>uboot init wdt_reboot success [UBOOT]NOTICE->[uboot_init_func]<474>uboot init dma success [UBOOT]NOTICE->[uboot_init_func]<474>uboot init i2c success [zx234290_get_boot_reason_prev][START_UP_STATUS = 0x1] ... [zx234290_get_boot_reason_prev][USER_RESERVED = 0xFF] ... [UBOOT]NOTICE->[uboot_init_func]<474>uboot init peri success. . . . . . [at][721]: receive client inform str = +ZLC: 0,0,0, fd = 10 [at][721]: at_rcvmsg_handle AT_TYPE_RESPONSE str=OK, at_fd = 10, at_cmd_paras: (null), prefix_len: 2, paras_len: 0 [at][721]: rcvmsg_rsp_at_client context->prefix = ZLC? [at][721]: rcvmsg_rsp_at_client send msg to app msg_id=0x150e,dst_id=0x100f,rsp_msg_id=0x0 [at][721]: rcv_msg_proc recv usMsgCmd = 0x150e, source is 0x100f [at][721]: at_write fd=10,len=8,ret=8,data=AT+CSQ [at][721]: receive client inform str = +CSQ: 151,99,5, fd = 10 [at][721]: at_rcvmsg_handle AT_TYPE_RESPONSE str=OK, at_fd = 10, at_cmd_paras: (null), prefix_len: 2, paras_len: 0 [at][721]: rcvmsg_rsp_at_client context->prefix = CSQ [at][721]: at_write fd=10,len=9,ret=9,data=AT+ZLC? [at][721]: receive client inform str = +ZLC: 0,0,0, fd = 10 [at][721]: at_rcvmsg_handle AT_TYPE_RESPONSE str=OK, at_fd = 10, at_cmd_paras: (null), prefix_len: 2, paras_len: 0 [at][721]: rcvmsg_rsp_at_client context->prefix = ZLC? [at][721]: rcvmsg_rsp_at_client send msg to app msg_id=0x150e,dst_id=0x100f,rsp_msg_id=0x0

 

[cullet]

Meron ka ng firmware?
If yes flash mo via tfpd64 tas ung command to flash via putty

 

[okjokj2]

Dear

odilonser1​

The Boot Information that you sent are not enough
Send me the MTD Partition Details
i may help you