Unlock Tool Redmi 9

[Martin Glow]

Forthe Redmi Note ADB drivers, you have to go through this hoop. I am certain it is the same with all MI phones or maybe for all non-Google mfg phones, I am not sure. First of all if you connect the device with USB cable and USB Debugging off, you will see that Windows 8 loads a generic driver for you to copy on/off files to the phone and SD storage. This will appear when the USB cable is first plugged in and appears as a device icon under Control Panel, Device Manager, Portable Devices, HM Note(or the device you are working with).

Go to the phone and switch on USB Debugging in the Developer section of your phone. Notice that an additional item appears as an undefined device now in the device manager list, it will have the yellow exclamation mark and it may not have the same name of the phone listed as you saw under Portable Devices. Ignore this item for the moment. Now, without doing anything to the phone (it should be already in USB debug mode) go back to the Portable Devices in Device Manager and right-click the HM Note or whatever phone you are working with that is listed there without the exclamation mark (listed under Portable Devices). Right click on the icon under Portable Devices. On that icon select Properties, Details, and under the pull down, select Hardware IDs and copy down what you see.

Now do as the instructions say above, of course customizing the lines you add the the INF file with those relating to your own phone, not the Nexus 10. Here is what to customize; when you downloaded the SDK you should have a file structure expanded from the ZIP such as this:

Edit the redmi.inf and add the lines as instructed above only modified for your particular phone. For example, for the HM Note, I added the following 2 lines as instructed in the 2 locations as instructed.

Now go back up to the unknown device that appeared in Device Manager when you switched on device USB debugging and right click on this item (has yellow exclamation mark), right click on it and then select Update Driver Software, and then Browse My Computer, Let Me Pick, click on the Have Disk button and browse to find the Redmi.inf. Continue to agree to all the prompts warning you it might not be the right driver. As the final step, Windows should have identified the device as Android ADB Interface and once that is done, you should be able to go back, open your CMD window and run the command "adb devices" as instructed in this tutorial and now you should see that the phone is now discovered and communicating.

Try Installing the PC Suite that came with Redmi Note and it will install all the necessary drivers for the mobile to work properly with PC Suite ;) . And after that check the connection with ADB it works fine.

If it doesn't work out by trying out solutions mentioned by others, then on top of that Try installing and running MI PC-SUITE from official Mi website HERE. Then try debugging again and you will see your device name in the list of available devices/options to run the app.

Thanks @anon_openwrt. Using a Windows PC is no problem, but I believe the partition layout I have applied as part of the instructions from dimfish are incompatible with the Xiaomi recovery tool, can you confirm?

If so, the experience has taught me the benefits of keeping the partitions in stock form. If there is anything else I can do, please let me know. Otherwise, I'm awaiting delivery of a USB to serial interface.

Get device access:

From direct connected LAN port (PC address will be assigned by AX6000 using DHCP), access miwifi.com portal and follow these steps (one per page):

a. Remove second tick and click blue button

b. Click last hyperlink below blue button

c. Select DHCP arrow

d. Type WiFi password (8 chars min). I'll be used for login, so make it simple. Uncheck middle tick and click blue button

e. Go to the web UI at

f. Type WiFi password (as above) in box for access.

Gain telnet access:

a. Run following script as "script 1 stok", using the stok part of the URL of the signed-in web UI.

b. Once it has rebooted, log in again to the web UI and run following script as "script 2 stok", using the new stok part of the URL.

c. Once it has rebooted, log in again to the web UI and run following script as "script 3 stok", using the new stok part of the URL.

Thank you for this! I am new to OpenWrt and had my AX6000 delivered yesterday. I was planning on waiting a week or two until the install process seemed to have settled down (e.g. PR 11115 and 11004), but these instructions made it easy for me to install OpenWrt just now. For other people's benefit, the only couple of issues/clarifications needed that I hit on the way were:

Thanks, I was able to recover my device using the serial interface and tftp to reload initramfs, then continued the documented SSH install process. I installed the sysupgrade file from the snapshot folder rather than dimfish's copy, and it worked fine.

Thanks @chrismiller - this was very helpful - I would also have expected the LuCI web UI to be installed by default - any idea why it's not? Regardless, I followed the instructions in your link and my router is now operational with OpenWRT!

Thanks for your feedback. I've updated my post with it. You don't need to use ssh for configuration in steps 2 to 5, just scp for firmware upload. All those steps can be done within the telnet session.

Hi to everyone! I need some help. I do everything to put OpenWRT on my RB06, but in the last part (sysupgrade) my device didnt rebooted. I waitened 4 hours and i did a hard reboot. Now, my device gets the ip 169.254.31.105 and keeps the ethernet adapator on and off on cycles (on for about 7 seconds and off for about 3 seconds). Can anyone have an idea to fix it? Thanks and sorry about my poor English.

To recover it, you'll need to use a serial connection to boot it from u-boot. You need a serial adapter for it. No need to open the case, as serial pins can be accessed through the case ( Add OpenWrt support for Xiaomi "Redmi AX6000" - #33 by EUA )

thanks for the info @soxrok2212. I already got a Bananapi BPI-R3 running smoothly with snapshot, but I need addition 3 AX routers to cover additional space. saw this AX6000 had similar hardware as BPI-R3 but cheaper, wonder if it will perform same using open source wireless driver.

Hello guys

My brand new xiaomi ax3600 cn version got bricked i think due to current cut during automatic update!!! Now it has an orange amber light and when trying to press reset and power on after 8 or 10 seconds its start blinking for 2 or 3 second , i tried the repair tool and tiny pxe but nothing happened i think the uboot is messed up , so can ibunbrick it using a 1.8v uart adpater ? If yes can anyone provides help on how ? For info ibhave a ch340a programmer is this router have thos eight legs chips ? Tthank you so much

I read all the comments before opening this thread , there is no explanation on how the unbrick this router via uart serial, im a noob and i would appreciate a video or tuttorial on how to do it , thank you so much

No need to use UART and crack the case open. As with many (most?) routers, it's the bootloader responding to the button press and running a TFTP client recovery process. This is almost unbrickable unless you've erased the bootloader.

Xiaomi has an automatic/guided TFTP server Windows tool for this which I've used multiple times on my AX3600 ( _download.html). Chinese-only, but I've never had a problem clicking through. Look on YouTube for Mi recovery videos in English if necessary, or read the Wiki. You just feed it a firmware file (e.g. -img.com/xiaoqiang/rom/r3600/miwifi_r3600_firmware_5da25_1.0.17.bin, from the Wiki), and choose your Ethernet interface from the list.

Timing is important. It might take a few goes. You can leave your PC in the TFTP-ready state throughout. You'll know it has worked OK once you see a pop-up TFTP transfer window on the PC for a few seconds. The LEDs on the AX3600 will then do something for a while, then something else (can't remember), after which you can power cycle and let a factory-fresh copy of the original firmware boot. Probably about 1 minute in total. Interrupting any of this process won't make things worse, but you might have to restart. The 1.017 firmware linked is a suitable starting point for opening SSH as described in the Wiki.

Hello

Thank you so much for your time , i already followed all of this and tried it moore than 50 times on windows 11 and 10 and two differents pc's and using tftp tiny pxe and xiaomi repair tool someone in the thread said that the device must blink 5times twice and mine blink only one so if i can do the serial uart thing i will im good at hardware but software im a little noob on routers and tftp . Thank you so much again

I don't know "Tiny PXE Server", but I'm not seeing a file request in the log. Maybe it doesn't show it? In any case, I doubt it's offering the correct filename to the router. From the OpenWRT Wiki, the AX3600 will request .bin, where filename is a hex encoding of the IP that you assigned it using DHCP.

I you are unsure how to diagnose and debug any of this, I suggest dropping back the Xiaomi tool again as it takes care of everything for you. Try it more times. Try varying your button press & release timing. Try waiting longer. I've done this recovery at least five times on three different units and generally took a few tries to get a successful trigger.

Hello

I tried the xiaomi repair tool over 50 times with differents combinisation and tried all the router ports 2 differents pc's with win7 and win10 , the assignedbip is 192.168.31.100 i renamed the file to test.bin and put it in the tiny pxe folder , can you plz assist me via teamviewer if you can i'll be so gratefull

I can't help via teamviewer. I'll just again say that 'test.bin' is incorrect. In the OpenWRT Wiki the example has the router on 192.168.11.100, where it apparently requested C0A80B64.img. It's nice to use a TFTP server which shows the requests - so that you don't have to compute/guess.

3a8082e126