Xiaomi mi wifi 3 support

For Developers
974

After upgrade from 21.02 to 21.02.1 from your link I found 2 issues

  1. Look like Leds control package was removed so my led is always orange now.
  2. Printer server via p910nd is stopped because device not recognized usb port
 :~# lsusb
unable to initialize libusb: -99

~# dmesg | grep usb
return nothing

~# opkg list-installed | grep usb
kmod-usb-core - 5.4.154-1
kmod-usb-ehci - 5.4.154-1
kmod-usb-ohci - 5.4.154-1
kmod-usb-printer - 5.4.154-1
kmod-usb2 - 5.4.154-1
libusb-1.0-0 - 1.0.24-4
usbids - 0.350-1
usbutils - 013-2

Does anyone know how to fix issue 2?

1 Like
976

pardon my question is this the newest openwrt kernel update for mir3 router ?
am trying to build following an old post but am ggetting some error patch patch phase

978

quick question regarding mipsel_24kc which from below is the right choice ?

Linux MIPS: [32-bit MIPS] [32-bit MIPSLE] [64-bit MIPS] [64-bit MIPSLE]

PS: its for adguard package choice

========================
edited

its MIPSLE 32

979

Hi everyone:

I had my Xiaomi R3 with X-WRT running and I wanted to put it back to stock following the procedure specified on the Routers page info.

At some point of the procedure something went wrong and now the router is bricked or semibricked.

I´m trying to recover it with the TFTP procedure but I´m unable to choose the option 1 to load it when the router boots.

The log that I get is this one:

U-Boot 1.1.3 (Apr 15 2016 - 17:46:32)

Board: Ralink APSoC DRAM:  128 MB
Power on memory test. Memory size= 128 MB...OK!
relocate_code Pointer at: 87fb8000
enable ephy clock...done. rf reg 29 = 5
SSC disabled.
!!! nand page size = 2048, addr len=4
..============================================
Ralink UBoot Version: 4.2.S.1
--------------------------------------------
ASIC 7620_MP (Port5<->None)
DRAM_CONF_FROM: Auto-detection
DRAM_TYPE: DDR2
DRAM component: 1024 Mbits
DRAM bus: 16 bit
Total memory: 128 MBytes
Flash component: NAND Flash
Date:Apr 15 2016  Time:17:46:32
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

 ##### The CPU freq = 580 MHZ ####
 estimate memory size =128 Mbytes

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   9: Load Boot Loader code then write to Flash via TFTP.


3: System Boot system code via Flash.
Booting System 2
..ranand_erase_write: offs:40000, count:20000
.Done!
done
## Booting image at bc600000 ...
   Image Name:   MIPS OpenWrt Linux-4.14.89
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1596367 Bytes =  1.5 MB
   Load Address: 80000000
   Entry Point:  80000000
.........................   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
commandline uart_en=0 factory_mode=0 mem=128m
No initrd
## Transferring control to Linux (at address 80000000) ...
## Giving linux memsize in MB, 128

Starting kernel ...

[    0.000000] Linux version 4.14.89 (ador@ubuntu) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7365-95daf4c441)) #0 Tue Dec 18 17:25:50 2018
[    0.000000] Board has DDR2
[    0.000000] Analog PMU set to hw control
[    0.000000] Digital PMU set to hw control
[    0.000000] SoC Type: MediaTek MT7620A ver:2 eco:6
[    0.000000] Linux version 4.14.89 (ador@ubuntu) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7365-95daf4c441)) #0 Tue Dec 18 17:25:50 2018
[    0.000000] Board has DDR2
[    0.000000] Analog PMU set to hw control
[    0.000000] Digital PMU set to hw control
[    0.000000] SoC Type: MediaTek MT7620A ver:2 eco:6
[    0.000000] Linux version 4.14.89 (ador@ubuntu) (gcc version 7.3.0 (OpenWrt G

As you can see as soon as it boots it goes directly to option 3. I try to restart to choose option 1 pressing it as soon as I plug it, but it is like it is not receiving the keyboard input.

Can anyone help me with this ot tell me if should I try an escape key to stop the boot?

I´m using putty for the serial connection between the router and the PC with the CP2103 USB adpater.

Thanks in advance.

1 Like
980

Hi everyone,

Does someone have the schematic for this PCB?
I have been looking online but without any luck.

Thank you in advance.

981

If you have destroyed flash:

1 Like
982

same situation with yours. sad....

983

Hey, I just got hold of this router and I wondered which file I should flash coming from stock, also does this router have the breed bootloader? (All done without opening the router)

984

Nvm, followed the guide for X WRT and it worked.
Did I miss something important or was it this easy?

985

hi again =D,
how to return from x-wrt/Openwrt to stock the method shown in the (openwrt site )website doesnt initiates te recovery mode

986

Hello, the router is stuck at starting kernel after accessing the router via serial consol , i try to access the cli by typing 4 any one had similar issues ? is it possible to recover from this ?

U-Boot 1.1.3 (Apr 15 2016 - 17:46:32)

Board: Ralink APSoC DRAM:  128 MB
Power on memory test. Memory size= 128 MB...OK!
relocate_code Pointer at: 87fb8000
enable ephy clock...done. rf reg 29 = 5
SSC disabled.
!!! nand page size = 2048, addr len=4
..============================================ 
Ralink UBoot Version: 4.2.S.1
-------------------------------------------- 
ASIC 7620_MP (Port5<->None)
DRAM_CONF_FROM: Auto-detection 
DRAM_TYPE: DDR2 
DRAM component: 1024 Mbits
DRAM bus: 16 bit
Total memory: 128 MBytes
Flash component: NAND Flash
Date:Apr 15 2016  Time:17:46:32
============================================ 
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768 

 ##### The CPU freq = 580 MHZ #### 
 estimate memory size =128 Mbytes

Please choose the operation: 
   1: Load system code to SDRAM via TFTP. 
   2: Load system code then write to Flash via TFTP. 
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   9: Load Boot Loader code then write to Flash via TFTP. 

   
3: System Boot system code via Flash.
Booting System 2
..ranand_erase_write: offs:40000, count:20000
.Done!
done
## Booting image at bc600000 ...
   Image Name:   MIPS OpenWrt Linux-4.14.195
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1875247 Bytes =  1.8 MB
   Load Address: 80001000
   Entry Point:  80001000
.............................   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
commandline uart_en=0 factory_mode=0 mem=128m
No initrd
## Transferring control to Linux (at address 80001000) ...
## Giving linux memsize in MB, 128

Starting kernel ..
987

This behavior means that the nvram parameter boot_wait contains a off value or param bootdelay is 0.

So that this situation does not arise, in my OpenWrt firmwares I make sure that these values corrected when the system starts: https://github.com/openwrt-xiaomi/openwrt/commit/626b8ef4223123612dc2970f9db91c579a0bec50#diff-b79bbb74af325be4c6fb2cf11b641332e142dafdb011b768ba8f34c089f0a984

Try MIWIFIRepairTool.x86.zip

1 Like
988

thank you for your feedback i messed with the parameters below in desperate need to make the router go into recovery mode and flash the stock firmware i think that did something because after rebooting i was stuck on orange led and until today i managed to connect via serial

fw_setenv flag_try_sys1_failed 0 fw_setenv flag_boot_success 0 fw_setenv flag_try_sys2_failed 0

989

Hi all! I've tried to read the thread, but too much information to get all. I have an old Mi3 with Padavan firmware installed. I want to install OpenWRT. I've seen some posts about Padavan in the thread but I have not been able to get to a final response.
Is possible to move from Padavan to OpenWrt? I need to install first Stock? Someone can guide me a little about the steps in the process?
This is my mtd if it helps:

dev:    size   erasesize  name
mtd0: 00040000 00020000 "Bootloader"
mtd1: 00080000 00020000 "BootEnv"
mtd2: 00040000 00020000 "Factory"
mtd3: 00040000 00020000 "crash"
mtd4: 00040000 00020000 "crash_syslog"
mtd5: 00020000 00020000 "reserved0"
mtd6: 00400000 00020000 "kernel0"
mtd7: 00140000 00020000 "Kernel"
mtd8: 00ec0000 00020000 "RootFS"
mtd9: 00080000 00020000 "Config"
mtd10: 00080000 00020000 "Storage"
mtd11: 06900000 00020000 "RWFS"
mtd12: 01000000 00020000 "Firmware_Stub"

I've one virtual machine with "prometheus" that is what I used to install the Padavan firmware some years ago. It has a restore backup option, maybe it helps.

990

If it helps to someone, I finally reverted to stock. I used the revert option in Prometheus and after that, installed the miwifi.bin file from the USB flash.
Now, gonna try the openwrt version from this thread :grin:

991

Can I ask why this version was abandoned and not merged into OpenWrt? I installed it and all seemed to be working...

992

If I remember correctly, something along the lines of the NAND driver isn't merged upstream at the time?

1 Like
993

Can someone give me a hand here?

I have the SSH Dropbear access with the development stock firmware. I can SSH into it but when i try to flash any image the MTD Write works just fine and then when i do the reboot it reboots to the stock image.

I dont know why is like if it was read only ? and the MTD did nothing? am i missing something here?

Im trying to flash X-WRT so Kernel1 and rootfs0. Some step im missing or any idea?

994

Last week, I flashed x-wrt on a mir3 and it worked fine with the steps on the wiki page. Are you sure you give the correct naming coventions in "<CURRENT_VERSION>"? You should get output "writting" with many consequence dots "............".
Kr.
PS: Another issue, I have experienced and can be connected is that your USB drive is not formatted correctly in FAT32. I struggled for hours to flash my Google Tv with multiple USB drives formatted in FAT32 on Linux.. ones I formatted them on Win it worked.Since then I use win for fat32

995

Yep im not even typing it, i tab the name for autocomplete. And yes i do get the writting secuence and it goes well that is the strangest thing.

I copied the file to the /tmp folder just to be sure is not the USB drive but even then it doesn't work.