[Android Stick & Console AMLogic based Computers] mghool2004:
Hi guys,

Soft bricked Xiaomi TV Box S 2nd Gen (MDZ-28-AA).

I created FTP server (via mixplorer) on the Xiaomi then uploaded videos via FileZilla FTP client from my PC.

I believe that the rootcause of the issue is when it failed to upload all of them due to limited device storage but for some reason when I retried the upload via the FTP client it was able to upload all of it!

Then my remote stopped working. I thought that when I restart the box, it will be fine again but then I lost control.

I will try to state all the information that may help and sorry for making it long.

- Remote controller can not perform any action at all.

- USB port on the device does not make wire/wireless mouse or keyboard work at all.

- "Back" + "OK" buttons does not start recovery mode.

- "Home" + "Xiaomi" button does not have any effect on the box to accept pairing (although I can pair the remote to my phone).

- USB debugging is enabled on the box (but silly me did not authorize my PC!).

- Device boot up to home screen but shows "" which I believe is duew to filled-up storage space.

- Device shows on "adb devices" as unauthorized.

- When I try to perform any adb action (via the cable or WiFi, the box shows "Allow USB debugging?" message but I am unable to press allow as I have no control.

- I have "Zank Remote" on both phone & box and was using my phone to as a remote before it fails but now when I start Zank on my phone, the box screen flashes instantaneously a white screen then it goes back to normal (I believe it tries to use the Zank service on the box but fails as it doesn't show "Running!" when Zank used to run on the box).

- I tried using Google "Home" app from my phone. It shows the box as "offline" but when I tap on it, I am able to cast my phone to the box! and I am able to control the box volume via phone! but when I try to use "Home" as a remote, the bo shows me 6-digits code on the TV screen, and when I enter it on the phone, it shows on the TV that my phone is paired successfully but then it shows another code.

I am stuck in this loop of typing codes, successful pair, then ask for the code again.

- I have "RTE Player" on the phone, which when I start on the phone and tap "Cast", it starts the "RTE" app on the box but I when I try to cast any video, it fails (my goal is not to cast a video but all these symptoms shows me that the connection between phone & box is up but the box suffers from memory issues).

- When I leave the box running, it shows the screensaver while it grabs the photos from internet.

- I disassembled the case (chassis) trying to short pins to enter recovery (as I saw in another site but it was for the older models) so, I couldn't do this too.

When I connect usb peripherals (mouse/keyboard), it doesn't even light up as an indicator to have power.

but I tried experimenting to short-circut random pins on the xiaomi box to see if it will restart in recovery (it is a dumb thing to do I know but did anyways), so when I connect the pin "TPM100" to the ground (the chassis), it makes a short then the box auto-restart and then my USB mouse red laser gets turned on so it gets power from the box but it still doesn't show the cursor on the screen.

Also, I tried the same while connecting the USB keyboard but it doesn't even light-up and key combinations have no effect (ctrl+alt+del) or (alt+prntscr+i).

I think that when I filled all the device storage, it fails to start the required services (which is stupid as the device should reserve system empty space for it's basic services) but I don't know!

- Finally, I tried both commands but no luck:

"fastboot reboot bootloader"

"fastboot flashing unlock"

It keeps < waiting for any device > forever.

To confirm the sequence:

0. HDMI cable is connected at all times.

1. Apply fastboot command.

2. Connect data cable (I don't have USB-A to USB-A cable currently) so I use USB-A in the box to USB-C in my laptop.

3. Connect power cable.

What I notice is that the usb connection sound on the computer comes late (after the 2nd screen of "Google TV" logo) not after the 1st screen of "mi" logo) which is believe is a reason of why fastboot command does not work as the computer does not recognize the USB connection this early. Could it be that the box is blocking the USB intentionally?

I read all your replies and I see you can go to recovery in the same box model but can it be related to a newer more restrictive firmware or something?

Am I completely stuck?

Do you suspect an issue in fastboot drivers? I installed it but I have no way to verify if it works or not.

(if fastboot & adb uses the same drivers, then it should be fine as "adb devices" shows my Unauthorized phone).

I also tried many other cables that I have which are USB-C to USB-C + (a converter from type-C to type-A)

The box is shown as "Unauthorized" on the "adb devices" which indicates that the cable is fine.

Please let me know if you have any input or ideas.

Thank you very much in advance!View attachment 6042720View attachment 6042721