Xiaomi Mi Box Update Issue: Android Won't Start, Eternal Reset & Remote Control Problem

Hello, I have a Xiaomi Mi Box that after hanging up during the update does not start eternal reset when going to upload Android I can't enter service mode because it can't even see the remote control (ok, backwards doesn't work). Please help if anyone had a similar problem.

Exactly what model is it.

Good morning this is Xiaomi Mi Box S (MDZ-22-AB)

Try to enter service mode

Well, unfortunately, it does not work because the box does not see the remote control

Added after 10 [minutes]:

I found better options https://miuipolska.pl/forum/topic/49642-flashowanie-atv-81-oreo-na-mi-box-s-mdz-22-ab/ but here I have a problem, the first one can't name the devices as in point 9 "WorldCup Device" but it seems to see the equipment only when uploading, an error pops up. And it looks like this

The problem may be the usb port or bad rom Image. Try a different usb first and change the cable.

I'm plugging in. The system cannot boot up after the update. The MI logo appears and turns off over and over again. Is it possible to somehow reset it back to the previous version without interfering with the device?

I just have it

Anyone solved?

I’ve tried key combinations on startup but nothing so far...

I had a bootloop too. Tomorrow I will try to explain how I managed to revert to the previous update. You need a USB-A - USB-A cable to connect the box to your computer. The rest can be downloaded online. See you tomorrow.

Man, we're waiting here like on pins and needles...

Read here https://4pda.to/forum/index.php?showtopic=928322&st=23080#Spoil-94116294-13
User Volkodav and instructions with opening the device. The USB burning program must be found on the network in this version (the latest one did not work for me). Password.bin download here: https://forum.xda-developers.com/attachments/password-bin-zip.5445437/
Updated I took from: https://forum.xda-developers.com/t/official-s...hread-mi-box-mdz-16-ab-and-mdz-22-ab.4241475/

This is just to see what it looks like. Tomorrow I will write how I did at home, because at first it didn't work. Patience

Alright...
Of course, I am not responsible for any damage, but what could be more broken than bricked equipment
My TV box started looping with the latest update (3933) and I had 3595 installed a while back with no problem.
Here in Polish how to flash mi box: https://miuipolska.pl/forum/topic/49642-flashowanie-atv-81-oreo-na-mi-box-s-mdz-22-ab/
But I used USB Burning Tool version 2.1.7.3 because the latest one didn't mount my img file.
We open the box, connect the USB cable to the computer. Power must be OFF.
Open the program with administrator privileges, mount the img file (File>Import image)
We also need to use the password.bin file, because without it you will probably get an error. Download the file from here: https://forum.xda-developers.com/attachments/password-bin-zip.5445437/, unpack and add it in the program (View>InPut Password and indicate our password.bin file.
Uncheck Erase bootloader and press Start
We short-circuit the places marked in the pictures and turn on the power. We are watching the program. When flashing starts, it can be reversed (weird word). We are waiting for the process to be successful. If it is ok, then we disconnect the box from the computer and connect the HDMI to the TV or monitor. I don't remember if I started the box from the remote control or just unplugged the power cable and plugged it back in.
The system should load, but you probably won't be able to pair the remote control according to the instructions that will appear on the screen (I couldn't)
So I turned off the box and entered the recovery mode, i.e. with the device turned off, press the "ok" and "back" buttons of the remote control at the same time (surprisingly it worked), while holding the power cable. We wait until it enters recovery mode and release the keys on the remote control.
We need the update.zip file, which we download from here: https://android.googleapis.com/packages/ota-a.../5cabec120b0378853b3d89a58c0171ac3e965046.zip. We change the name to update, so that the file update.zip is created. We put the file on a pendrive previously formatted to FAT32.
Other updates are here: https://forum.xda-developers.com/t/official-s...hread-mi-box-mdz-16-ab-and-mdz-22-ab.4241475/
This is version 3595, so the one I had before the unfortunate update. Others didn't work for me. On the Russian site there is an update in the manual (some earlier one, I think), but for recovery version 8 (at the top in recovery mode you can read it). For me, 9 was visible (I don't know why so), so maybe that's why this update from the Russians did not work.
We plug the pendrive with the file into the box and the remote control, we do 3 things:
1. Wipe cache partition
2. Wipe data/factory reset
3. Apply update from ext > update from udisk > update.zip
If successful, just reboot system now.

Good luck

@unida Thanks a lot, you saved my box I have a question. Did you do that wretched update after restoring? Because I don't know whether to risk another bootloop

I just wrote how I used the instructions of other wise people Something didn't work for me, so I made small adjustments by trial and error, and luckily it worked.
I didn't update. Even if there's another one, I won't do it either. As long as everything works, I don't move

Thanks for the large amount of information. Unfortunately, following all instructions step by step, I still get an error (after 4% loading)


[HUB4-4][Inf]--IOCTL_IDENTIFY_HOST_Handler ret=-116 error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: The I/O operation was aborted due to thread termination or application request.

...
[0x10303004]Romcode/Switch status/Identify/Error result

zerowek wrote:

Thanks for the large amount of information. Unfortunately, following all instructions step by step, I still get an error (after 4% loading)


[HUB4-4][Inf]--IOCTL_IDENTIFY_HOST_Handler ret=-116 error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: The I/O operation was aborted due to thread termination or application request.

...
[0x10303004]Romcode/Switch status/Identify/Error result

I crashed when I kept the compact elements on the board for too long. It went when I let go right after the flashing process started.

Hello. Can anyone tell me which pins to short because the photos from this post can no longer be viewed?

In my case (factory reset after a damaged system and non-working remote control) it was enough to connect the keyboard to USB. Using the arrows, I reinstalled the system and everything was back to normal.

How did you enter service mode using the keyboard? And I don't know how to update it, the remote control doesn't want to test.

>>20554639
How did you reinstall the system using a keyboard? The remote control doesn't work for me, only the USB keyboard. Wi-Fi also doesn't work to update. The USB port is occupied by the keyboard, so I have no way to update and enter service mode

I have a problem waking up my MiBox.
I have this message :

.

Cable short and certainly good because box X69Q I did with this cable without problem (of course different software and obra).
USB2 and USB3 no difference same error.

I think you need to play with the drivers and the port as the cable is ok

What do you have in mind?
How do you play?

>>19724058 >>19724058

Hello colleagues. I'm going to dig up the topic, can anyone provide information on which pins need to be shorted to flash the box?