yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] DJ_BARO:
Stuck on boot "mi" screen after installing version 454 & performing reset

Hello everyone,

Thanks to [MENTION=6831974]Dave Deluria[/MENTION] for this useful translation of the vietnamese guide to Downgrade!

Unfortunately, after i installed the once_464.zip & performing a factory reset, it ended up in a stuck "MI" Boot Up Screen :confused:

Till then, i was able to follow you but now I'm really confused: Interesting enough, that the 1901 Version of MM boots up without any problem but I'm not able to restore my Bootloader (Permission denied).

Any ideas? I would really like to go back :/ My box is dr MDZ - 16AB Version (As written on the bottom of the box)

I could return to Nougat, but if there is a way to get MM working i would be very glad :)

One question beyond that: When i install Nougat again, can i restore my bootloader also with the latest 1560 Version? Our is ADB restricted to 1028?

Many thanks, hopefully, someone does now something about ;)
[Android Stick & Console AMLogic based Computers] oldblueeyes182:
Thanks for this write up. I keep getting this error:

dd: /sdcard/rom3.img: Not a directory

can someone help?
[Android Stick & Console AMLogic based Computers] Mr.LostPuppy:
Same in my case. It's may be HDMI compatibility issue in 6.0.1-454.

1) Try using another monitor

2) If you don't have any spare monitor, then you need 454 and later firmware (anything from 6.0.1-750 to 1901)

install firmware 454 then reboot, plug out hdmi immediateley

count about 6~10 sec then plug in hdmi again.

if you catch a right time, you can see booting animation. if you see mi logo or black screen, plug out hdmi and try again reboot.

if you see boot animation you can proceed pairing remote controller and may be stucks at language selection again.

Now connect mi box and laptop with usb cable

do bootloader restore process ( adb push backup-256mb.img to sdcard & dd img to mmcblk0 & reboot recovery)

install firmware any 6.0.1 (750~1901), reset data/cache , reboot...

now you can use MM.
[Android Stick & Console AMLogic based Computers] OscarBaia:
Hello guys. Need help

I received OTA Oreo update on Mi Box but turns out it bricked it.

Went to recovery and did factory reset (several times) and wipe cache but issue persist

Mi Box won't start to android.

Can anyone help?

Thanks in advance
[Android Stick & Console AMLogic based Computers] Djuganight:
Try to find the zip file and flash it.

Mine is installing the update At this moment

---------- Post added at 09:33 PM ---------- Previous post was at 08:59 PM ----------

Oreo installed fine here but my internet speeds are extremely low. Upload don't go over 4mb/s when usually was between 50-60mb/s. Why is this?
[Android Stick & Console AMLogic based Computers] bravovn:
Does this method work with downgrade from oreo? Thanks
[Android Stick & Console AMLogic based Computers] user30000z:
Is this thread relevant also for downgrading from Oreo?

Did someone try?
[Android Stick & Console AMLogic based Computers] Dave Deluria:
Just updating the thread. I have updated the box I originally reverted to MM to Oreo and it was successful.

This means this method has safely preserved DRM .

I suggest everyone who are now inquiring about Oreo downgrades to start a separate thread to keep the forum clean and searchable (even using google search).

Thanks.
[Android Stick & Console AMLogic based Computers] THEDARK_:
I would like to know

A person to try?
[Android Stick & Console AMLogic based Computers] Djuganight:
With this new Oreo my internet keeps disconnecting which makes streaming (Netflix and IPTV) an absolute pain.

Any ideas for a solution?
[Android Stick & Console AMLogic based Computers] phoenix08:
Please do let me know if you find a way to downgrade to MM.

Lessons learned, No more updates without confirming the stability.

Thanks in advance :)
[Android Stick & Console AMLogic based Computers] Djuganight:
Sadly I have the box connected to an old Philips TV therefore I have to stick with the Oreo version as it has the RGB 8bit option therefore preventing colour inversion.

The only issues I have noticed is:

- internet keeps disconnecting

- when connected the upload speeds are very low

- very often the remote original remote control does not work. Have to disconnect the box and connect again.

- some keys of the air mouse remote don't work or are switch (back and enter)

Hope that these issues can be looked into
[Android Stick & Console AMLogic based Computers] S-eye:
I am also interested in a guide how to go back to marhsmallow from Oreo.

The Mi Box is very buggy right now. Biggest problem for me, that there is no audio.
[Android Stick & Console AMLogic based Computers] jseymour:
Try rebooting repeatedly to see if it'll come back. It has for some people.
[Android Stick & Console AMLogic based Computers] S-eye:
Unfortunately that doesn't work either.:(
[Android Stick & Console AMLogic based Computers] hsnlpy:
There is alot of problems on Oreo.Please help how to downgrade Marshmallow.
[Android Stick & Console AMLogic based Computers] ANTHONY 93:
You could indicate the process to dowgrade from oreo to 6.0
[Android Stick & Console AMLogic based Computers] omer919:
Have anyone succesfully downgraded from oreo to marshmello using this method?

OP have you tried ^ ?
[Android Stick & Console AMLogic based Computers] :
This doesn't work for me.
[Android Stick & Console AMLogic based Computers] claishem01:
Question: after succesfully doing this process, will there be no more automatic updates that is going to happen?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Not sure how this works, pretty sure you need root to do this..

And as we know mibox are not rooted

The only way possible(that i know of) to dump the bootloader, kernel, etc from the device is via uart or uboot

Also what do you mean the bootloader was never released?

I have multiple packages with bootloader included, the keys however are not and im still working on a way to dump them

Me and another dev are working on a bootloader unlock
[Android Stick & Console AMLogic based Computers] bravovn:
Wow. Really excited to here that. Good luck to your working. Hope one day our mibox could be rooted. Thanks so much for all of you.
[Android Stick & Console AMLogic based Computers] diogo.sena:
Please take a look here, https://discourse.coreelec.org/t/xiaomi-mi-box-ce-and-drm/834/8
[Android Stick & Console AMLogic based Computers] claishem01:
may i know what is the stock MM build of 16 ab out of the box? is it already the r454?
[Android Stick & Console AMLogic based Computers] claishem01:
sir [MENTION=6831974]Dave Deluria[/MENTION] , so if i got the box on a later build than the 0464 i will not be able to flash the 0464? so what is the option sir to backup my bootloader then? Thanks.
[Android Stick & Console AMLogic based Computers] bigtalker:
If you have 1 Mibox and 1 tv there is no possible way to pinpoint where the fault lies. If you have another branded Netflix approved streaming device you can use that device to divine the DRM status of your screen. Connect the other device and run Netflix diagnostic videos titled "Test Patterns".

If the results you get for resolution after running test patterns S2 E8 exceed 720 X 480 resolution, that is confirmation your screen supports sufficicient DRM for Netflix, and your MiBox is the issue. OTOH, if your other box never goes beyond 720X480, it is prima facie proof that Netflix is not seeing proper DRM on your screen.

In my vast experience, there are an overwhelming number of tvs in circulation with faulty or missing DRM.

The chances of having a MiBox with faulty DRM/HDMI is less than 1%, based on my evaluation of over 350 MiBox units.
[Android Stick & Console AMLogic based Computers] aperture:
Very excited with the unlocked bootloader. :)

There's a user debug build for marshmallow and nougat. its build 454 and build 1028 respectively.

You can do SU under ADB shell using these builds.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Sorry but you should kill that excitement right away, the bootloader is unlocked, however the firmware is encrypted very heavily, to clone the partitions is almost impossible without UART, luckily i have a UART on the way and just got a mibox from someone on here!

So i can begin to findout whats going on with the mibox
[Android Stick & Console AMLogic based Computers] claishem01:
hi.

is it possible to downgrade from oreo if you already have the 256mb backup?

because downgrading from nougat requires flashing of the modified bootloader from davietpda before you can flash the MM.

i am just thinking if the case is you are on Oreo and already have the backup, is it possible to just flash the N1028 then dd flash the rom3.img, flash MM, then restore bl backup?
[Android Stick & Console AMLogic based Computers] bigtalker:
You are missing one critical element. There is absolutely no userdebug build available for Oreo.

Without pseudo root system access provided by userdebug build, you are not allowed to flash any lower build onto an Oreo system.
[Android Stick & Console AMLogic based Computers] claishem01:
ok. thanks. so it always has to be a userdebug firmware to be able to flash an update.zip on a stock recovery.
[Android Stick & Console AMLogic based Computers] claishem01:
can someone give me a link where i can download this specific mm firmware build? this was the firmware my box came with when i got it. just wondering if i could get this exact firmware again..
[Android Stick & Console AMLogic based Computers] bigtalker:
Absolutely impossible.

Build 699 was only available pre-installed on retail boxes of MDZ-16-AB

It was never available OTA therefore was not available for capturing into a file.

IIRC, when you purchased a box with this build installed it was immediately required to perform update to build 750 of MM (or the latest current build of MM, which, at this moment is build 1901)
[Android Stick & Console AMLogic based Computers] timmydy:
You can download all the firmware builds here. Change ***** to mediafire

*******.com/folder/9k82rbe2nc0vw/MDZ-16-AB

build 454 is indeed a user debug build and I was able to gain root via adb and perform a backup of my DRM.
[Android Stick & Console AMLogic based Computers] claishem01:
i actually have this download link already and have downloaded most of the firmwares from there, but unfortunately the mm 699 build is not included in the list. thanks anyway sir [MENTION=9366437]timmydy[/MENTION]

. i accessed and created my drm backup in nougat 1028. just went back to mm, build 1901.

---------- Post added at 03:20 AM ---------- Previous post was at 03:06 AM ----------

thanks.

just what's with this 699 that it wasnt made available?

but since, as what youve said, it will be required to do the update anyway, then theres no reason going back to it.

---------- Post added at 04:08 AM ---------- Previous post was at 03:20 AM ----------

and may i also ask, which firmware are you using? which is the stablest firmware for you? currently im in MM 1901.

One thing that ive been noticing is i cant find the setting/option to change the function of power button. mine can only make the box sleep/wake when short pressed, and option to reboot when long pressed. i think i saw a video in youtube that it can be set to shutdown the device too.
[Android Stick & Console AMLogic based Computers] claishem01:
%everybody is saying that it is impossible to flash a N or MM update.zip from Oreo.

Meaning if you are in Oreo then try to flash a N or MM update.zip in recovery it wont flash succesfully?

So how come flashing an MM update zip from Nougat to works just fine?
[Android Stick & Console AMLogic based Computers] aperture:
The reason why you can flash MM rom from Nougat is that Nougat beta 1028 is a debug build.

Remember that we were able to DD or copy the rom3s.img (modded temporary bootloader) via ADB shell with root access to /dev/block/mmcblk0

included in the rom3s.img is also the recovery image for MM.

so after you reboot to recovery you'll see that recovery is now for MM and you can now flash the MM user debug build 454.

If we have a user debug build for OREO then we can also copy the rom3s.img (modded temporary bootloader) to /dev/block/mmcblk0 via ADB shell with root access.

reboot to recovery and flash MM 454 build via recovery.
[Android Stick & Console AMLogic based Computers] claishem01:
since oreo has no user debug, what happens if we flash an MM or a Nougat update.zip directly from Oreo recovery?
[Android Stick & Console AMLogic based Computers] aperture:
There's going to be an error..

i just flash MM rom under Oreo recovery just for you so you can see.

here's the error i got.
[Android Stick & Console AMLogic based Computers] claishem01:
thank you. this is the answer to my question. i remember somebody have already posted that error here. so its the error you get when you flash lower android versions without the unlocked or modified bootloader. so i wont be attempting to try the oreo then..
[Android Stick & Console AMLogic based Computers] claishem01:
is there a way to unroot without reflashing the firmware? or is there a bat script also to remove the root?
[Android Stick & Console AMLogic based Computers] bigtalker:
Root does not exist in the traditional sense so your question is not germane.

Full system access can only be accomplished by proper adb command seqences, provided unit is flashed with userdebug firmware build.

You are in over your head. Be careful or you will have a disaster.

What exactly are you trying to accomplish?
[Android Stick & Console AMLogic based Computers] claishem01:
sorry. i should have quoted one of the comments here with regards with tethered supersu. i was referring to it.

so there is that script.bat that you will run to get supersu, only you have to run specific commands with every boot for the device to boot normally. i was just wonderin if there is also a script.bat for reverting, or for removing the supersu, and for the device to boot again normally without the adb commands.

---------- Post added at 03:55 AM ---------- Previous post was at 03:43 AM ----------

i just wanted to rename the otacerts.zip from the system/etc/security folder to disable update (although there is another way to disable it using pm commands).

Anyway i was able to do it already.

im using 454.

adb root

adb shell

mount -o rw,remount /system

mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.bak

done.
[Android Stick & Console AMLogic based Computers] bigtalker:
There is a much simpler, permanent way.

Block this url at your router

https://android.googleapis.com/packages/ota-api/xiaomi_once_once

This works no matter what build you are using.

Also allows you to flash a current build without sacrificing your device security and operational integrity.

You will still be able to use the normal update process to flash your desired build, with certain limitations.
[Android Stick & Console AMLogic based Computers] claishem01:
maybe i just prefer the not simpler way.

i like doing the more complicated methods and learn from them.
[Android Stick & Console AMLogic based Computers] sylar10001:
can somebody confirm if this will work if you're using Android 8.0? have somebody tried?
[Android Stick & Console AMLogic based Computers] diabolyk34:
Hi,

I'm also interested to downgrade from android 8.0.0 cause not working well, some apps are not updated for this os and wifi unstable.

is it working with android8 or not ?

thanks
[Android Stick & Console AMLogic based Computers] tamamma:
No answer for downgrading from android 8?
[Android Stick & Console AMLogic based Computers] bigtalker:
The ability to downgrade from Nougat to MM was based on the existence of special userdebug builds, These builds had a provision to access the actual system files and manipulate them.

No such userdebug builds are available in Oreo.

My best suggestion is to find and flash Oreo build 2179, which is the least objectionable option to date.
[Android Stick & Console AMLogic based Computers] claishem01:
sorry. there was an error happened. ill make update when it's fixed.
[Android Stick & Console AMLogic based Computers] elliwigy:
where can we download this oreo userdebug?
[Android Stick & Console AMLogic based Computers] bigtalker:
What is Oreo userdebug build number?
[Android Stick & Console AMLogic based Computers] ds22:
I hope it's soon.

I'm just dying to downgrade back to Marshmallow and actually be able to use my Mi Box again.
[Android Stick & Console AMLogic based Computers] 666Spell:
Guys, most problems go away after a RECOVERY MENU factory reset.

Quoting from another post: Unplug the Mibox, and after plugging it back in while it's booting press the center DPAD key (ENTER or OK key) and at the same time the BACK key. Select factory reset option from recovery menu.

Not all problems go away, but the box becomes usable again.
[Android Stick & Console AMLogic based Computers] bigtalker:
Agree that factory reset should be employed after any flashing.

The timing on that process can prove problematic, especially in case of fat fingers that contact adjacent buttons.

If possible, do full factory reset from settings menu. Same effect, simpler process.
[Android Stick & Console AMLogic based Computers] ds22:
Have done all that, multiple times even, and it simply doesn't help a whole lot.
[Android Stick & Console AMLogic based Computers] whisnu88:
Hey can I use this method to downgrade from Oreo 8.1 to MM on my mi box?
[Android Stick & Console AMLogic based Computers] bigtalker:
Sorry, no way.

One critical element, a userdebug rom, was previously available on MM and Nougat.

NO userdebug version has been released for Oreo so this downgrade process cannot work.

The userdebug rom allowed for manipulating system files which are normally locked and hidden.

This applies to both MiBox versions that run official AndroidTV.
[Android Stick & Console AMLogic based Computers] bigtalker:
Sorry for duplicate post.
[Android Stick & Console AMLogic based Computers] Chryses:
Hi, I don't know if can be related, but actually my box DMZ-16-AB, won't start, only the red light on back, and after very loooong time, the white led appear, but no hdmi signal. If I connect to pc with USB-A/A cable the device is recognized as WorldCup device but I can't see any devices via adb command, only Amlogic_USB_Burning_Tool see the device, but I only found the firmware for the AA version.

Anyone can help me in order to recover this box?

Many thanks.

J
[Android Stick & Console AMLogic based Computers] bigtalker:
There is NO rom .img file that will work with USB burning tool and this device.

DO NOT under any circumstances, attempt to burn another .img file. You will turn your wounded box into a brick.....

Only available solution is to flash a current update.zip file written to a FAT32 freshly formatted USB thumb drive. I believe the most recent stable version is Oreo 8.0 build 2562.

You may need to try several different brands/sizes of thumb drive but, ultimately, it will flash correctly. Current world's record is 9 different thumb drives. Don't be easily discouraged....

Good luck
[Android Stick & Console AMLogic based Computers] Chryses:
Thanks

Do you know how can I flash the update.zip if the player won't boot? I mean, I attach the power cord and only the back red light is active, no white led on front, so I can't start the normal recovery. Only if I leave the HDMI attached, after some hours, the white led appear but no signal at all.

Where do you see people that tried different thumb drives? Many there's a kind of list?

Thanks again, Jo
[Android Stick & Console AMLogic based Computers] bigtalker:
Remove power plug from projector

Hold round button on top right of projector

connect power plug and wait for increased fan sound

Release pressure on round button
[Android Stick & Console AMLogic based Computers] Chryses:
Wait, are you talking about the MDZ-16-AB? There's no fan on it and is not a projector.
[Tilt, TyTN II, MDA Vario III General] Jaeger:
I am running a tilt that is giving me the message "voice command has quit due to low memory" a few seconds after pressing the VC button. I have an 8gb Sandisk micro card in it with about 2 gb of music and the remainder is movies. Voice command will generally work fine with the card removed.

When viewing the memory page and starting Voice Command with the card in the slot, available memory goes from about 68mb free to about 66mb free, nothing close to wiping out the memory

Originally when this started I could clear out the IE history and it would be fine - no such luck anymore.

I have gone through the Kaiser Tweaks turning card management stuff on and off and have found no combintion that helps.

Is this an irreperable problem with large cards and voice command, or is there some registry hack that can help me? Not much on this subject on the forums, I hope I am not the only one experiencing this...

Thanks
[Tilt, TyTN II, MDA Vario III General] NotATreoFan:
Which version of Voice Command / ROM are you running?

Voice Command 1.5 does not work properly with WM6.1 ROMs.
[Tilt, TyTN II, MDA Vario III General] Jaeger:
I'm using version 1.6

I just bought it about 2 weeks ago.

It worked fine for the first week, adding nothing of significance to the storage card or installing additional software. What set it off was downloading a large file over WiFi directly to the storage card. I immediately deleted it and checked the disk over in windows, but it still kept happening. clearing out the memory worked for a day or two, now nothing will stop the error aside from removing the memory card.
[Tilt, TyTN II, MDA Vario III General] Jaeger:
Also...

The ROM is the 6.0 ROM shipped with the Tilt.
[Tilt, TyTN II, MDA Vario III General] NotATreoFan:
Here's a few things to try:

1) Uninstall / Reinstall Voice Command (kind of obvious, probably already tried)

2) Backup your data on the SD card, and then format it

3) Perform a hard reset on your Tilt and start over.**

**Note: This step will erase EVERYTHING on your device. You can use a program called PIMBackup to save your contacts, call logs, appointments, text messages, and much more. You can then restore them once the hard reset is done.

If you make it to step 3 and do not know how to do a hard reset, check out the Wiki link in my signature.
[Tilt, TyTN II, MDA Vario III General] BigBen:
MSVC 1.6 Low memory problem

I am having this same problem of the low memory error ever since I installed a cooked WM 6.1 ROM with MSVC 1.6 baked into it. Since then, I have flashed several WM 6 ROMs on my HERMES and the same problem always comes up.

I never had this problem with the MSVC 1.6 since I first bought it over a year ago. Now no matter what ROM I flash, when I install my purchased MSVC 1.6, this low memory error plagues me.

This is not just a Kaiser problem, guys. Thought I would let you know. There have been a number of posts in the Hermes forum about this. It's driving me nuts. No solution found yet, and I have searched and searched here and on the internet.

If I find a solution, I will come back and let you all know.

Ben
[Tilt, TyTN II, MDA Vario III General] Jaeger:
Well...

I did the card reformat and replaced all the data, and it worked...for a while. Now it is back to doing the same thing. I am going to retry the format, try it for a few days and progressively add files to it. If number of files is not the problem, I'll reset all the way back. I have been using the tilt a lot for listening to streaming audio, maybe that has something to do with it (temp files in places I can't find, or heat buildup?)

Good to know my device is not just a lemon at least - Ben, does your problem happen all the time or only with the storage card installed?

Thanks for the help!