Bricked Redmi Ax6000 Openwrt

Installing and Using OpenWrt
1

Hi everyone,

I recently managed to brick my redmi ax6000 while upgrading from ImmortalWRT to Openwrt using sysupgrade (Openwrt Uboot Mod Layout, First used: Immortalwrt). When finished, after Rebooting no leds show up but my pc can detect ethernet connected. I tried to use tftp server and provided file in 192.168.1.254 but it says no dhcpd detected. And since there are no leds working Its blind and I cant understand if its in recovery mode or not. Thanks.

screenshots attached:

image
image633×610 33.9 KB

image
image1920×1080 335 KB

Do I need to follow the UART method for this?

Thanks

2

no dude, based on your other thread, that's not what happened...

1 Like
3

The given device link do you mean I need to use UART to fix this issue? Sorry I may not be able get your message properly. my English is bad forgive me.

4

Tried the suggestion in the other thread?

5

Or you could just keep reading ...

2 Likes
6

yes I did. Its blind and if reset did fix the issue the leds would light up its dark

7

Sorry, I still couldnt catch you. :frowning:

8

He suggests you correctly follow the instructions located on the Wiki URL above.

For example, you need to address your server and client according to the Wiki instructions. Your screenshot shows you did this incorrectly.

2 Likes
9

Thank you for responding @lleachii

this time I used tftpd application and it says that the file is transferred sucessfully

image

image
image495×574 74.1 KB

But still not working

i transferred this file:

openwrt-77352dce071c-mediatek-filogic-xiaomi_redmi-router-ax6000-ubootmod-squashfs-sysupgrade.itb

10

Provide details.

1 Like
11

no it seems I was being stupid, the files was sent to the pc folder and telling it was transferred successfully. I still cant figure out what is wrong can you help?

12

this is what tinypxe shows:

image
image634×626 56.3 KB

image
image491×573 73.8 KB

image
image1282×858 60.1 KB

Am I still missing something? Is the board fried by any short circuit or something?

13

Yes:

screen559

Issuing a x.x.x.255 IP is invalid for a 255.255.255.0 subnet. Configure "IP Pool start" to use valid IPs.

1 Like
15

It's quicker to try it, than post a question, and wait for a reply..

1 Like
16

As I am in bed now I gave up testing I will reply with results again after 8 hours or so Thanks

17

image
image1920×1080 360 KB

Its still the same no matter what I try.

But when I switch the ipv4 address manually to 192.168.1.254 wireshark logs keep spamming with something relating to 192.168.1.253, I dont know what that means but I am attaching a screenshot

image
image1920×1080 368 KB

image
image1920×1080 325 KB

And by any chance is the board fried by any electric fault?

Thanks.

18

Should I go for the UART solution? how much helpful would that be? Since I am using openwrt uboot and not stock uboot. I think i expect to get some output from there?

19

probably a lot, unless you bricked your router.

do you have a firewall on your windows box, and have you disabled it ?

1 Like
20

yeah it asked for firewall access during the first phase. I allowed it but after that I disabled the firewall anyway. And I recovered my old Xiaomi R4A gigabit the same way. And few days back this AX6000 router was bricked from stock due to a wrong cmd input and I fixed it using TFTP. Now if it doesnt work it probably had hardbricked itself.

21

and So, if my router is bricked UART wont be able to fix it? I need to desolder NAND and reprogram it?