Mi Box S MDZ 22 AB sucessfully unbricked but remote buttons issues now - Android Stick & Console AMLogic based Computers

my MDZ 22 AB was running great on 8.1 and when it upgraded to 9.0 i didnt like the new version so i wanted to downgrade. i sourced several firmware files for 8.1. they were diff files sizes. looks like the first one was for like model or was corrupted and the box was bricked...only the red diode in rear and no access to recovery. after searching around i successfully unbricked it using the "other" file for 8.1 and all now seemed normal, i have access to recovery menu and it will boot up to the initial wizard mode where you are pressing the "OK" button then later have to press both the "home and app's keys" to pair the remote.
the problem is that the above operations fail: the "OK" button and the "home and app's keys" are not being received by the box. the "power" button also doesnt work. the batteries are fresh i charged them. during the time im pressing the OK key over and over a message pops up saying, "cannot connect to internet". FURTHER info: i can successfully boot into recovery mode using the remote by using both the back arrow and the OK key and applying power to unit. once inside recovery all remote keys work perfectly.
why would the OK key work okay in recovery but not during bootup?
do i have to "reset" my remote? is there a way?

---

Hi,
Unfortuantely I won't be able to help you on your request but I would be curious on having more details on the way you used to unbrick your box?
I am stuck on the topic for a week now and haven't been able to do anything...
Many thanks in advance,
Regards,

---

i used this link to fix mine but im still having remote issues they arent
https://forum.xda-developers.com/an...c/help-to-unbrick-mi-box-s-mdz-22-ab-t4020279
make sure you DL the link for your unit....MDZ 22 AB? 2 links are provided one is for the Mi Box 3 not the S (MDZ 22 AB)
this link show step by step instructions from the russian in the first post but here in english. however, in this pic where he shows which pins to short together to initiate the restore of the rom, his pics show the Mi Box 3 NOT the Mi Box S. link here however only thing wrong is the pin shorting pic. i can send you pic of the correct oins for the MDZ 22 AB for Mi Box S (only). not sure how to post on this forum?

---

nedro018 said:
i used this link to fix mine but im still having remote issues they arent
https://forum.xda-developers.com/an...c/help-to-unbrick-mi-box-s-mdz-22-ab-t4020279
make sure you DL the link for your unit....MDZ 22 AB? 2 links are provided one is for the Mi Box 3 not the S (MDZ 22 AB)
this link show step by step instructions from the russian in the first post but here in english. however, in this pic where he shows which pins to short together to initiate the restore of the rom, his pics show the Mi Box 3 NOT the Mi Box S. link here however only thing wrong is the pin shorting pic. i can send you pic of the correct oins for the MDZ 22 AB for Mi Box S (only). not sure how to post on this forum?
Click to expand...
Click to collapse
looking for advice from bigtalker or others here about this remote issue. when i boot up from freshly installed 8.1 or 9.0 installs, the operating system comes to the "wizard" after a fresh startup and you are asked to press the OK button and or later the 2 "pairing" buttons. my remote is simply not responding to the main Mi Box S unit. i cant get past this wizard.
i have changed my batteries many times no help. i have removed them for 10 moin plus no help.
question(s) (since i may not have a functioning remote i dont know):
1) is there supposed to be a light emitting from the front of the remote?
2) is there a way to "reset" the remote?
3) i cannot locate on Net purchase of a OEM remote for the Mi Box S MDZ 22 AB so is there a "universal" option?
thanks to all for any help. read this entire thread above before answering and special note: the "OK" button does NOT work during initial boot ups from the operating system however it DOES work when im navigating around inside of the Mi Box S recovery menu. how is that possible?
currently, my remote is not emitting any lights at all whatsoever when pressing any buttons. i think it is supposed to do so. so the remote is not working in operating system (OS) interaction but it DOES work inside recovery.
this remote is supposed to be both IR and BT compatible....maybe the BT part is broke (the part that interacts in the OS) but the IR signal (which works during recovery?) is why the remote works ok there?

---

My issue is same as you, at the time of dowgrading my mi box s is bricked, only red light glows and box doen't boot up.

---

sushnimo said:
My issue is same as you, at the time of dowgrading my mi box s is bricked, only red light glows and box doen't boot up.
Click to expand...
Click to collapse
check the links above you can unbrick yours i did.
but you are off topic here my post and problem is about the "remote control unit" not pairing upon the first bootup stage of the mi box OS... at this satge you cannot use a cell phone app to engage with the OS you need a remote. i cannot setup my mi box fresh installs because i cant get past the initial wizard of interacting with the remote.
my remote is not emitting any lights from the front when pressing buttons. does yours? is no lights normal? are these lights from IR (infrared) signals or BTooth signals?
repeat this topic is about my REMOTE issues i am not bricked any more thanks

---

need help in unbricking my mi-box
how to check is my remote emitting any lights from the front when pressing buttons.?

---

sushnimo said:
how to check is my remote emitting any lights from the front when pressing buttons.?
Click to expand...
Click to collapse
there's a small diode on the front face of remote. it supposed to blink "green" i believe when you are pressing buttons. i was told this by a friend who has same MI box unit and i had him test his remote....he said it was blinking green signal lights.
i have unbricked my mi Box S MDZ 22 AB. it boots up OK now. i can successfully go to Pie version or back to Oreo at will. my problem is that i cant get past the intial startup wizard because at bootup the remote wont talk to the Mi Box. im stuck at the wizard. in either Pie 8 or Oreo 8. i dont how the remote suddenly "died" or how to do a hard "reset" of it. ive left the batteries out for days. the batteries are fresh.
so ive order both a new Mi Box S with Oreo on it from china and also a new Mi Box S remote from china as well. they have not arrived in over 4 or 5 weeks prob due the the chinese new year delay. for now im stuck.
any other experts here know how to tear open the remote and "revive" it???

---

nedro018 said:
check the links above you can unbrick yours i did.
but you are off topic here my post and problem is about the "remote control unit" not pairing upon the first bootup stage of the mi box OS... at this satge you cannot use a cell phone app to engage with the OS you need a remote. i cannot setup my mi box fresh installs because i cant get past the initial wizard of interacting with the remote.
my remote is not emitting any lights from the front when pressing buttons. does yours? is no lights normal? are these lights from IR (infrared) signals or BTooth signals?
repeat this topic is about my REMOTE issues i am not bricked any more thanks
Click to expand...
Click to collapse
nedro018 said:
there's a small diode on the front face of remote. it supposed to blink "green" i believe when you are pressing buttons. i was told this by a friend who has same MI box unit and i had him test his remote....he said it was blinking green signal lights.
i have unbricked my mi Box S MDZ 22 AB. it boots up OK now. i can successfully go to Pie version or back to Oreo at will. my problem is that i cant get past the intial startup wizard because at bootup the remote wont talk to the Mi Box. im stuck at the wizard. in either Pie 8 or Oreo 8. i dont how the remote suddenly "died" or how to do a hard "reset" of it. ive left the batteries out for days. the batteries are fresh.
so ive order both a new Mi Box S with Oreo on it from china and also a new Mi Box S remote from china as well. they have not arrived in over 4 or 5 weeks prob due the the chinese new year delay. for now im stuck.
any other experts here know how to tear open the remote and "revive" it???
Click to expand...
Click to collapse
When I press remote key, green diode not blinking while pressing buttons. and i never seen any blinking diode when my mi box was working. So how ti unbrick it, can you share procedure with me on my mail. In my MI Box only red light is on in 3.5 mm jack, and and in TV it shows no HDMI Connected. please help..
My Mail ID Is- [email protected]

---

nedro018 said:
i used this link to fix mine but im still having remote issues they arent
https://forum.xda-developers.com/an...c/help-to-unbrick-mi-box-s-mdz-22-ab-t4020279
make sure you DL the link for your unit....MDZ 22 AB? 2 links are provided one is for the Mi Box 3 not the S (MDZ 22 AB)
this link show step by step instructions from the russian in the first post but here in english. however, in this pic where he shows which pins to short together to initiate the restore of the rom, his pics show the Mi Box 3 NOT the Mi Box S. link here however only thing wrong is the pin shorting pic. i can send you pic of the correct oins for the MDZ 22 AB for Mi Box S (only). not sure how to post on this forum?
Click to expand...
Click to collapse
Hi my friend,
Can you email me the pic of the correct pins to short for the MDZ 22 AB for Mi Box S?
my email : [email protected]
Many thanks!

---

nedro018 said:
my MDZ 22 AB was running great on 8.1 and when it upgraded to 9.0 i didnt like the new version so i wanted to downgrade. i sourced several firmware files for 8.1. they were diff files sizes. looks like the first one was for like model or was corrupted and the box was bricked...only the red diode in rear and no access to recovery. after searching around i successfully unbricked it using the "other" file for 8.1 and all now seemed normal, i have access to recovery menu and it will boot up to the initial wizard mode where you are pressing the "OK" button then later have to press both the "home and app's keys" to pair the remote.
the problem is that the above operations fail: the "OK" button and the "home and app's keys" are not being received by the box. the "power" button also doesnt work. the batteries are fresh i charged them. during the time im pressing the OK key over and over a message pops up saying, "cannot connect to internet". FURTHER info: i can successfully boot into recovery mode using the remote by using both the back arrow and the OK key and applying power to unit. once inside recovery all remote keys work perfectly.
why would the OK key work okay in recovery but not during bootup?
do i have to "reset" my remote? is there a way?
Click to expand...
Click to collapse
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
DONE

---

Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
Can you please give me full instructions for flashing firmware from pendrive
Click to expand...
Click to collapse

---

Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
Can you please give me full instructions for flashing firmware from oendrive
Click to expand...
Click to collapse

---

Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
DONE
Click to expand...
Click to collapse
Thank you! I was frustrated when my remote didnt work after unbricking my mi box s. Used your update method and voila - everything works perfect now, but I used this update Link instead, since your direct update link didn't fix my problem. You're the real MVP

---

Hasenkampf said:
I FOUND THE PROBLEM
You flashed an old/unstable image (r363) with the bridge
I FOUND A SOLUTION, YES THATS RIGHT
Flash the newer stable image (r699) with an update.zip file via an usb-stick in the recovery mode
Here is the Mi Box S Android 8.1 Oreo update direct link
Source of the stable image
Reboot after the flash
No wait and use the OK-Button multiple times until a noise comes to be able to use the remote keys
DONE
Click to expand...
Click to collapse
Hello,
I have the exact same issue. But since remote is not responsive after flash with bridge I cannot enter recovery mode using the OK+BACK button combination on the remote. Is there a stable image to be flashed over usb or an alternative way to enter recovery mode?

---

I finally managed to restore my Mi Box S from r363 which I have flashed with USB Burning Tool and had lost remote control connectivity and wifi connectivity (bad MAC address 02:00:00:00:00:00) back to fully working r3933 (last version) so I would like to share it with you.
In my case tha OK+BACK button combination did not work to enter the recovery menu. So this is what I did.
You will need Amlogic CustomizationTool v2.0.10 for this. You will also need r2216 and r3933 recovery images.
First download and unzip r2216. We will need boot.img file found in this file.
Install Amlogic CustomizationTool. Run it and press Load button. Check all the first 4 Level Low options, click ok and a window will open to select burn image. Select the r363 buggy image and click Open. The firmware will unpack and there will be an "Unpack Success" dialog box where you click ok. Go to "Advance" tab and press the "Kernel" button on the right. A dialog will appear with the currect boot.partition. Select it and press Replace. Browse to the boot.img file from r2216 recovery. Verify your selection in next dialog box and cloce the dialog with the partitions. Press the Pack button and save the new generated image.
Format a USB stick with FAT32 and place r3933 recovery image renamed to update.zip in the stick.
Flash the image generated above with USB Burning Tool that works for you using the same method that you flashed r393. I used Amlogic USB Burning Tool v2.2.4.
Boot the box after the flash with a USB hub connected with a usb keyboard only. I guess this kernel does not match with the r363 system so the recovery menu for 8.1.0/r363 pops up. Now plug the USB stick in the hub. My box didn't boot with USB stick connected that is why I advice to plug the stick after the recovery menu appears.
Select "Wipe data/factory reset" with the keyboard and verify. Then select "Apply update from EXT", then "Update from udisk" then select the update.zip from the stick. It will verify the package (this might take 10 minutes) and it will update the recovery.img and reboot.
The recovery menu will appear again but now it is the newer version from r3933. Redo the above (wipe data, update from the same update.zip). This time the whole update is flashed and there is also a graphic with the progress. Let it finish.
After the update reboot the box and you should be back!
P.S.: I did not erase the bootloader via the option in the USB burning tool so my DRM license for Netflix survived. Please make sure not to check this option. If you started with the option checked abort immediately and you will save the bootloader since it is the very last part flashed. Restart the procedure from scratch with the option unchecked.

---

babylonx said:
I finally managed to restore my Mi Box S from r393 which I have flashed with USB Burning Tool and had lost remote control connectivity and wifi connectivity (bad MAC address 02:00:00:00:00:00) back to fully working r3933 (last version) so I would like to share it with you.
In my case tha OK+BACK button combination did not work to enter the recovery menu. So this is what I did.
You will need Amlogic CustomizationTool v2.0.10 for this. You will also need r2216 and r3933 recovery images.
First download and unzip r2216. We will need boot.img file found in this file.
Install Amlogic CustomizationTool. Run it and press Load button. Check all the first 4 Level Low options, click ok and a window will open to select burn image. Select the r393 buggy image and click Open. The firmware will unpack and there will be an "Unpack Success" dialog box where you click ok. Go to "Advance" tab and press the "Kernel" button on the right. A dialog will appear with the currect boot.partition. Select it and press Replace. Browse to the boot.img file from r2216 recovery. Verify your selection in next dialog box and cloce the dialog with the partitions. Press the Pack button and save the new generated image.
Format a USB stick with FAT32 and place r3933 recovery image renamed to update.zip in the stick.
Flash the image generated above with USB Burning Tool that works for you using the same method that you flashed r393. I used Amlogic USB Burning Tool v2.2.4.
Boot the box after the flash with a USB hub connected with a usb keyboard only. I guess this kernel does not match with the r393 system so the recovery menu for 8.1.0/r363 pops up. Now plug the USB stick in the hub. My box didn't boot with USB stick connected that is why I advice to plug the stick after the recovery menu appears.
Select "Wipe data/factory reset" with the keyboard and verify. Then select "Apply update from EXT", then "Update from udisk" then select the update.zip from the stick. It will verify the package (this might take 10 minutes) and it will update the recovery.img and reboot.
The recovery menu will appear again but now it is the newer version from r3933. Redo the above (wipe data, update from the same update.zip). This time the whole update is flashed and there is also a graphic with the progress. Let it finish.
After the update reboot the box and you should be back!
P.S.: I did not erase the bootloader via the option in the USB burning tool so my DRM license for Netflix survived. Please make sure not to check this option. If you started with the option checked abort immediately and you will save the bootloader since it is the very last part flashed. Restart the procedure from scratch with the option unchecked.
Click to expand...
Click to collapse
hi i'm follow your steps but i have no luck. i'm a little confused with 2 things. when you say r393 did you mean r363 right? and in the part when you replace boot.partition and ask if you want continue you select yes and close the dialog and then pack the new image?
my mac address still it's 02:00:00:00:00:00 and bluetooth completely dead

---

Sorry, I was kind of exhausted yesterday and I didn't remeber the exact version number, yes I mean r363 obviously. It is the only burn image I found anyway.
And yes you cloce the dialog after you confirm replace of kernel boot.img and then Pack. You are asked for a name to save to.
Do you know what version you were before bricking with r363? I was at r3933 (last one from October 2021). If you were at different version maybe you should try to restore to that version instead of r3933. Here you can find other versions:
Official Stock Firmware Thread - Mi Box (MDZ-16-AB and MDZ-22-AB)
Disclaimer Flash these at your own risk, I am not responsible for any problems that may occur. It is NOT possible to easily downgrade firmware using recovery once upgraded. Downgrading requires a special cable and opening of the box. I am not...
forum.xda-developers.com

---

babylonx said:
I finally managed to restore my Mi Box S from r363 which I have flashed with USB Burning Tool and had lost remote control connectivity and wifi connectivity (bad MAC address 02:00:00:00:00:00) back to fully working r3933 (last version) so I would like to share it with you.
In my case tha OK+BACK button combination did not work to enter the recovery menu. So this is what I did.
You will need Amlogic CustomizationTool v2.0.10 for this. You will also need r2216 and r3933 recovery images.
First download and unzip r2216. We will need boot.img file found in this file.
Install Amlogic CustomizationTool. Run it and press Load button. Check all the first 4 Level Low options, click ok and a window will open to select burn image. Select the r363 buggy image and click Open. The firmware will unpack and there will be an "Unpack Success" dialog box where you click ok. Go to "Advance" tab and press the "Kernel" button on the right. A dialog will appear with the currect boot.partition. Select it and press Replace. Browse to the boot.img file from r2216 recovery. Verify your selection in next dialog box and cloce the dialog with the partitions. Press the Pack button and save the new generated image.
Format a USB stick with FAT32 and place r3933 recovery image renamed to update.zip in the stick.
Flash-elje meg a fent generált képet az Ön számára megfelelő USB-író eszközzel, ugyanazzal a módszerrel, mint az r393 flashelésekor. Amlogic USB Burning Tool v2.2.4-et használtam.
A vaku után indítsa el a dobozt egy USB-elosztóval, amely csak USB-billentyűzethez van csatlakoztatva. Azt hiszem, ez a kernel nem egyezik az r363 rendszerrel, így a 8.1.0/r363 helyreállítási menüje megjelenik. Most csatlakoztassa az USB-meghajtót a hubhoz. A dobozom nem indult el, ha USB-stick van csatlakoztatva, ezért azt tanácsolom, hogy a helyreállítási menü megjelenése után csatlakoztassa a pendrive-ot.
Válassza az „Adatok törlése/gyári beállítások visszaállítása” lehetőséget a billentyűzeten, és ellenőrizze. Ezután válassza az "Apply update from EXT", majd az "Update from udisk" lehetőséget, majd válassza ki az update.zip fájlt a stickről. Ellenőrzi a csomagot (ez 10 percig is eltarthat), frissíti a recovery.img fájlt, és újraindítja a rendszert.
A helyreállítási menü ismét megjelenik, de most az r3933 újabb verziója. Ismételje meg a fentieket (adatok törlése, frissítés ugyanarról az update.zip-ről). Ezúttal a teljes frissítés fel van villantva, és van egy grafika is a folyamatról. Hadd fejezze be.
A frissítés után indítsa újra a dobozt, és vissza kell jönnie!
Ui: Nem töröltem a rendszerbetöltőt az USB-író eszköz opciójával, így a Netflix DRM-licencem megmaradt. Kérjük, ne jelölje be ezt a lehetőséget. Ha a bejelölt opcióval kezdted, azonnal szakítsd meg, és elmented a rendszerbetöltőt, mivel ez a legutolsó felvillantott rész. Indítsa újra az eljárást a nulláról úgy, hogy az opció nincs bejelölve.
Click to expand...
Click to collapse
Szia !
)Köszönöm szépen a leírást ! ) Nekem sem volt távirányító , mac cím és wifi ! de a leírásod alapján minden rendbe jött ! ))
)Köszönöm szépen !!!!!

---

babylonx said:
Végre sikerült visszaállítani a Mi Box S-emet az r363-ról, USB Burning Tool-al flasheltem, és elvesztettem a távirányítót és a wifi kapcsolat (rossz MAC-cím 02:00:00:00:00:00) teljesen működőképes r3933 -ra (utolsó verzió), ezért szeretném megosztani veletek.
Az én esetemben az OK+VISSZA gomb kombinációja nem működött a helyreállítási menübe való belépéshez. hát ezt tettem.
Ha szükséges lesz az Amlogic CustomizationTool v2.0.10 -re. Szüksége lesz az r2216 és r3933 helyreállítási lemezképekre is.
Először töltse le és csomagolja ki az r2216-ot. Szükségünk lesz ebben a fájlban található boot.img fájlra.
Telepítse az Amlogic CustomizationTool eszközt. Futtassa és nyomja meg a Betöltés gombot. Jelölje be az összes első 4 Level Low opciót, kattintson az OK gombra, és válassza ki az ablakot, ahol kiválaszthatja a képírást. Ki az r363 bugos képet, és kattintson a Megnyitás gombra. A firmware kicsomagol, és megjelenik egy "Sikeres kicsomagolás" párbeszédpanel, ahol kattintson az OK gombra. Lépjen az "Advance" fülre, és nyomja meg a "Kernel" gombot a jobb oldalon. Megjelenik egy párbeszédpanel a megfelelő boot.partícióval. Ki, és nyomja meg a Csere gombot. Keresse meg a boot.img fájlt az r2216 helyreállításból. én a választást a következő párbeszédpanelen, és zárja be a párbeszédpanelt a partíciókkal. Nyomja meg a Pack gombot, és mentse el az új generált képet.
Formázz meg egy USB-meghajtót FAT32-vel, és helyezd el az update.zip-re átnevezett r3933 helyreállítási képfájlt a pendrive-on.
Flash-elje meg a fent generált képet az Ön számára megfelelő USB-író eszközzel, ugyanazzal a módszerrel, mint az r393 flashelésekor. Amlogic USB Burning Tool v2.2.4-et használtam.
A vaku után indítsa el a dobozt egy USB-elosztóval, amely csak USB-billentyűzethez van csatlakoztatva. Azt hiszem, ez a kernel nem egyezik meg az r363 rendszerrel, így megjelenik a 8.1.0/r363 helyreállítási menüje. Most csatlakoztassa az USB-meghajtót a hubhoz. A nem indul el, ha USB-stick van dobozba, ezért azt tanácsolom, hogy a helyreállítási menü megjelenése után csatlakoztassa a pendrive-ot.
Az „Adatok törlése/gyári beállítások visszaállítása” lehetőség a billentyűzeten, és egyszerűen. választás az "Apply update from EXT", az "Update from udisk" lehetőségek, majd választás ki az update.zip fájlt a stickről. Ellenőrzi a csomagot (ez 10 percig is eltarthat), frissíti a recovery.img fájlt, és újraindítja a rendszert.
A helyreállítási menü ismét megjelenik, de most az r3933 újabb verziója. Ismételje meg a fentieket (adatok törlése, frissítés ugyanarról az update.zip-ről). Ezúttal a teljes frissítés fel van villantva, és van egy grafika is a folyamatról. Hadd fejezze be.
A frissítés után indítsa újra a dobozt, és vissza kell jönnie!
Ui: Nem töröltem a rendszerbetöltőt az USB-író eszköz opciójával, így a Netflix DRM-licencem megmaradt. Kérem, ne jelölje be ezt a lehetőséget. Ha a bejelölt opcióval kezdte, azonnal szakítsd meg, és elmented a rendszerbetöltőt, mivel ez a legutolsó felvillantott rész. Indítsa újra az eljárást a nulláról úgy, hogy az opció nincs bejelölve.
Click to expand...
Click to collapse
Szia !
)Köszönöm szépen a le írást ! így sikerült visszaállítani a xiaomi mi box s-t )
)Szuper munka ! )