yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
im sorry i dont have the time... you can use my tool or stock tool, just delete everything besides recovery and bootloader and image.cfg, then edit cfg with notepad++ and make sure it only has these 3 lines

[LIST_VERIFY]
file="bootloader.PARTITION"	main_type="PARTITION"	sub_type="bootloader"
file="recovery.PARTITION"	main_type="PARTITION"	sub_type="recovery"
[Android Stick & Console AMLogic based Computers] venioni:
I make all this but when i go to repacking the tool never finishing the repacking.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
try the stock tool, only unpack to level 1
[Android Stick & Console AMLogic based Computers] venioni:
Did you know where can i found the stock tool ?
[Android Stick & Console AMLogic based Computers] venioni:
[MENTION=5105831]Ricky Divjakovski[/MENTION] I make all this and i have this error when i trying to flash .
[Android Stick & Console AMLogic based Computers] claishem01:
how do we repack level 1 using customization tool?
[Android Stick & Console AMLogic based Computers] venioni:
I try that and dont working, something wrong with the stock rom.
[Android Stick & Console AMLogic based Computers] claishem01:
anyway how do we do the repacking using Customization Tool?
[Android Stick & Console AMLogic based Computers] venioni:
Look on the last tab of customization tool and down left has a button to repack.
[Android Stick & Console AMLogic based Computers] claishem01:
i see.. and as i have observed we cannot repack the bootloader and recovery only, and also without level 2.
[Android Stick & Console AMLogic based Computers] claishem01:
this is what happens when i try to repack.
[Android Stick & Console AMLogic based Computers] claishem01:
i am able to repack now but creates a file with ctp extension. now how do we convert this ctp to an img file or flashable firmware?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
As for anyone with a total brick, like i said, feel free to send the device to me to attempt bootloader unlock/root and if im successful, i will send it back..

Companies and people send me devices all the time, but im yet to recieve a mibox
[Android Stick & Console AMLogic based Computers] venioni:
[MENTION=2739843]jrs007[/MENTION]

I created this firmware(I am create a new one to replace) but just like Rick I do not have my Mi Box Bricked, I just have to understand the problem and help.

new imageMDZ-16-AB download

I download the new image and again i have the same error on my Mi tv box 3s MDZ 16-AB.

the error is this :
[Android Stick & Console AMLogic based Computers] claishem01:
sir [MENTION=6927702]venioni[/MENTION] , what windows os are you using?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Use burn tool 2.1.2
[Android Stick & Console AMLogic based Computers] venioni:
[MENTION=5105831]Ricky Divjakovski[/MENTION]

I will try that tool but i dont thinks to work, i think th problem is something other.

I try with 2.1.2 usb burning tool and i have the same problem, something wrong with the stock img is the problem i think.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Maybe try 2.0.8 then, that issue has nothing to do with the firmware
[Android Stick & Console AMLogic based Computers] venioni:
I'll try all this tools versions ,i try also on windows 7 pc but nothing happened ,all the time i see the same problem.

What can be the problem ?
[Android Stick & Console AMLogic based Computers] claishem01:
if only i already have my mi box there will be two of us [MENTION=6927702]venioni[/MENTION] who can run tests in these tools and firmwares. as of now it is only you who are doing the tests of this firmware flashing on a mibox 16-ab. hope you can already solve your problem and revive your unit. by then we can confirm that these tools and firmware are perfectly working in reviving mdz 16-ab.
[Android Stick & Console AMLogic based Computers] claishem01:
sir [MENTION=5105831]Ricky Divjakovski[/MENTION] is this bootloader console you are talking about is the one you said you are still developing now?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Yes, i have finished building it, will be included in my next release of Amlogic tools.

See below
[Android Stick & Console AMLogic based Computers] venioni:
I think the problem with [0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed is that burning tool can not read the RAM DDR3 must modify the stock ROM for working the burning tool.
[Android Stick & Console AMLogic based Computers] claishem01:
when can we expect the release of this sir?

is this also the tool that could unlock bootloader and root mdz 16-ab?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Depends how long this customization tool takes
[Android Stick & Console AMLogic based Computers] jrs007:
Very informative this log. :good:

As I suspected the problem is with the DDR.USB file inside the firmare. Of all this was what I still did not understand how it works. I will analyze.

It is as if the firmware was 98% ready and that 2% is the DDR.USB :silly:

---------- Post added at 10:31 PM ---------- Previous post was at 10:27 PM ----------

Impressive. with it being uboot, we could burn an image directly to a partition. Right?

But I have this question: Do I need to install the uboot on the nib of the mibox or the amlogic S905x-h understand the commands directly?

Another thing: Do you know how I can handle the DDR.USB file? Is there any tool for this?
[Android Stick & Console AMLogic based Computers] claishem01:
sir [MENTION=2739843]jrs007[/MENTION] do you mean that we really cannot flash this firmware succesfully that is why [MENTION=6927702]venioni[/MENTION] never had success in flashing his mdz 16 ab?
[Android Stick & Console AMLogic based Computers] elliwigy:
can anyone link me to usb burning tool 2.1.8? also what is tge process to get it to show in the tool to begin with lol.. im on oreo AB variant and cant get it to show for the life of me
[Android Stick & Console AMLogic based Computers] jrs007:
Yes, momentarily not. until you correct this DDR.USB. it is the cause of not starting the firmware recording.

what happens is that it tells the program that the hardware is different from the AA model even the firmware (bootloader, boot, recovery and system) being correct
[Android Stick & Console AMLogic based Computers] claishem01:
so the bottomline now here sir [MENTION=2739843]jrs007[/MENTION] is to avoid messing up the software as much as possible, because there is not yet, until now, a working flashable image firmware for mdz 16-ab.. that's just sad.. still no known way to revive a bricked 16-ab.. :(
[Android Stick & Console AMLogic based Computers] claishem01:
where is this DRM thing located from the image files?

---------- Post added at 07:06 AM ---------- Previous post was at 06:59 AM ----------

im not sure about this, since i know little with regards to programming, but i guess its important to have a way to unlock the bootloader first of our 16-ab, and a compatible TWRP recovery img, then we will be able to pull the firmware/images from a working device and then we can share it to others and try if it will recover their device from soft bricks.
[Android Stick & Console AMLogic based Computers] hacker001:
[MENTION=2739843]jrs007[/MENTION]

on my mdz-19-aa

I think problem is wrong ddr.usb

where is correct ddr.usb can i have on official firmware zip or not?
[Android Stick & Console AMLogic based Computers] andybz:
I just attempted to use the amlogic burn tool and that image posted here on my MDZ-16-AB.

I think it's bricked even more than before now.

GXL:BL1:9ac50e:a1974b;FEAT:BDFD71BC;POC:2;RCY:0;USB:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 125458

BL2 Built : 13:27:37, Oct 25 2017. gxl g56b77aa - xiaobo.gu@droid12

_vcc5_power_init
rn5t567_power_init
Board ID = 1
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz
bist_test rank: 0 18 02 2f 2a 15 3f 18 01 2f 2e 1a 43 18 03 2e 2b 15 42 19 03 2f 2b 14 43 693 rank: 1 16 02 2b 2b 17 3f 17 02 2d 32 1d 47 14 04 24 2b 16 41 17 03 2b 2d 16 44 693 - PASS

Rank0: 1024MB(auto)-2T-13

Rank1: 1024MB(auto)-2T-13
AddrBus test pass!
-s
emmc switch 3 ok
Authentication key not yet programmed
emmc_rpmb_key_is_programmed: error 0x00000007
emmc switch 0 ok
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
aml log : R1024 check pass!
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01700000, size: 0x0000d600
aml log : R1024 check pass!
Load bl31 from eMMC, src: 0x00020200, des: 0x01700000, size: 0x0002c600
aml log : R1024 check pass!
Load bl32 from eMMC, src: 0x00050200, des: 0x01700000, size: 0x00034600
aml log : R1024 check pass!
Load bl33 from eMMC, src: 0x00088200, des: 0x01700000, size: 0x00051e00
aml log : R1024 check pass!
NOTICE: BL3-1: v1.0(release):7c45a4f
NOTICE: BL3-1: Built : 14:09:28, Oct 13 2017
[BL31]: GXL CPU setup!
NOTICE: BL31: GXL secure boot!
NOTICE: BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3255-1a77b01 2017-09-15 16:58:02 xiaobo.gu@droid12]
OPS=0x82
10 e4 16 a2 97 54 b8 a7 a7 34 a6 28 [1.500927 Inits done]
secure task start!
high task start!
low task start!
INFO: BL3-2: ATOS-V2.4-67-g26d2f32 #1 Tue Jan 23 10:10:32 UTC 2018 arm
INFO: BL3-2: Chip: GXL Rev: B (21:B - 80:2)
INFO: BL3-2: crypto engine DMA
INFO: BL3-2: secure time TEE
INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e

U-Boot 2015.01-g0a1e56b (Jun 21 2018 - 13:51:11), Build: jenkins-once_cts-2167

DRAM: 2 GiB
Relocation Offset is: 76edb000
register usb cfg[0][1] = 0000000077f65290
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpu: vpu_clk_gate_init_off
MMC: aml_priv->desc_buf = 0x0000000073edb640
aml_priv->desc_buf = 0x0000000073edd960
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
original ext_csd[171] USE_WP field value is 50
ext_csd[171] USER_WP filed value after switch is 58
[mmc_init] mmc init success

Then it just sits there at mmc init success forever.

I guess that image isn't good?
[Android Stick & Console AMLogic based Computers] bigtalker:
What is the current status of your mdz-16-ab? 1- Do you get lights when you apply power? 2- Is it stuck in a boot loop and won't advance beyond colored dots on screen?

The ONLY solution to recover from 2 is to apply recovery using well documented steps. You must use the update.zip file that is equal or higher than the installed build.

In the case of 1- there is absolutely no way to recover from a dead device. Time to bin it at that point.
[Android Stick & Console AMLogic based Computers] claishem01:
hi sir. i actually dont have mi box yet, but i am buying one (mdz 16-ab) on the following days. i am just getting as much information i can get about this device as reference when i already have it.

since it will come out of the box in marshmallow android, im planning to flash it right away with MM build 464 so i can adb backup the bootloader and drm for safekeeping. but i just want to have a confirmation first if it is really not possible , as stated by [MENTION=6831974]Dave Deluria[/MENTION] ,to flash an earlier build of mm if you are in a later build of MM already out of the box. and if so, can i just flash directly from MM to Nougat 1028 instead and not lose the DRM? and then there i will make adb backup and pull of my backup-256.img to safely keep my drm?

I hope someone can confirm to me if this the right way..

or if not, maybe you can give me advice on hiw to do it correctly.

thank you very much.
[Android Stick & Console AMLogic based Computers] elliwigy:
updating from mm to N will not lose drm.. only downgrading from N to mm you will lose it..

so make a backup like the guide says and store it somewhere safe..

also, if you like root i wouldnt upgrade past N.. theres no userdebug firmware for oreo to my knowledge and no way to downgrade from oreo to N to my knowledge..

what allows downgrade from N to mm is the userdebug firmwares (only on n and mm is userdebug available) as they allow root shell
[Android Stick & Console AMLogic based Computers] claishem01:
thank you very much sir. so there is a 100% assurance of not losing the DRM in flashing the Nougat build 1028 update.zip directly from the stock MM os out of the box?

i actually been studying and reading the instructions from this thread for days now to be sure that i wont make a mistake.

https://xdaforums.com/android-stick...ic/xiaomi-mi-box-mdz-16-ab-downgrade-t3737186

from Oreo, im also aware that there is yet no way of downgrading.

so it is true that downgrading to an earlier build from a later build (aside from MM r464 and N 1028 which has enabled user debug) is also not allowed?
[Android Stick & Console AMLogic based Computers] elliwigy:
only downgrading from N to MM do u lose DRM.. anytime switching between different MM builds or switching between N builds is fine..

again, backup is a must lol.. if u need to restore drm for w.e reason and u have the backup and did not update to oreo u should be able to restore drm following the guide..

theres only userdebug on mm and on n and they are needed to downgrade from n to mm as ull need root to do the steps
[Android Stick & Console AMLogic based Computers] elliwigy:
but yes, you can only downgrade from the userdebug N firmware... you can manually install other N builds however and if u want to downgrade u just install the userdebug N build then follow the guide

if that makes sense.. lol
[Android Stick & Console AMLogic based Computers] claishem01:
so you are confirming that it is fine to flash MM earlier build if you are already on MM later build? because i understood it as downgrading also.

and this statement of sir [MENTION=6831974]Dave Deluria[/MENTION] confuses me,

what could he meant by that that trying to downgrade from current MM to build 464 that others have been unable to do so?

thank you very much sir for your responses.
[Android Stick & Console AMLogic based Computers] jrs007:
Has anyone ever tested this img firmware?

https://www.atvxperience.com

On the site says that it is for various amlogic devices. I think it's worth trying and in this video a guy uses the recording tool "USB_Burning_Tool"

https://www.youtube.com/watch?v=LptnsPdn0Hc

---------- Post added at 12:23 AM ---------- Previous post was at 12:08 AM ----------

Look at this forum about this:

https://forum.atvxperience.com/viewforum.php?f=1

Our processor is the S905x
[Android Stick & Console AMLogic based Computers] venioni:
[MENTION=2739843]jrs007[/MENTION] I try this firmware and dont working on my bricked mi box 3 .
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Yes but xiaomi use a heavily modified bootloader to disable flashing via usb
[Android Stick & Console AMLogic based Computers] ZeRoZeRoRaZ:
They have time to modify bootloader, but they don't have time to fix bugs...
[Android Stick & Console AMLogic based Computers] iakovl:
any idea on how to force MDZ-19-AA into recovery, was following the guide to flash global rom on it and when i was planning to install ONCE rom from external USB it rebooted and now wont go into recovery
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Its sickening right?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Good news , someone is sending me a MiBox, not sure what model but if all goes well we will have a proper unbrick method

Not 100% sure if connection over UART is needed or not but ive ordered a UART debugger just incase
[Android Stick & Console AMLogic based Computers] ohst0901:
Hi, thanks for your sharing... I had tried to flash my mdz-19-aa with img (MDZ-19-AA_Test2 - Download).

After finish with the flashing tool, it stuck at the 'mi' screen.

And now I want try to redo again the step, but can't, my laptop can't detect my mdz-19-aa...

How can I do to save it?
[Android Stick & Console AMLogic based Computers] g2mantap:
goodluck bro....looking forward to test ur rom on my mi box 3c
[Android Stick & Console AMLogic based Computers] hacker001:
You are my only hope to revive my mdz-19-aa

May the force be with you :)

[MENTION=5105831]Ricky Divjakovski[/MENTION]
[Android Stick & Console AMLogic based Computers] rusgold:
How are your successes with MDZ-16AB?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Hey, the device was a complete dead brick, to the point the eMMC was completely wiped, im not willing to invest in an eMMC flasher and learn about manual eMMC flashing just to unbrick the device

Ill just have to wait until someone sends me a MiBox that is some what functional or atlease gets to a point i can sinterupt the boot process and communicate with uboot
[Android Stick & Console AMLogic based Computers] rusgold:
Is it possible to flash custom rom with another uboot after cleaning the eMMC?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Im still not 100% aware of what can be done with this device sorry
[Android Stick & Console AMLogic based Computers] rorovillarroel:
Hola a todos estoy con un Xiaomi Mi box 3 modelo MDZ-16AB, alguien ha encontrado alguna solución. Los sigo desde Chile.

Saludos.
[Android Stick & Console AMLogic based Computers] bigtalker:
Perform full factory reset

Find and flash latest Oreo bugfix build 2179
[Android Stick & Console AMLogic based Computers] rorovillarroel:
Hola amigo, la caja que tengo está brickeada, por lo tanto, no es posible instalar la actualización de forma normal. Trate entrar al recovery con los botones del control remoto y tampoco funcionó. Creo que la única opción es flashear abriendo el mibox y puentear, mediante el cable USB.

Enviado desde mi CLT-L09 mediante Tapatalk
[Android Stick & Console AMLogic based Computers] darthcircuit:
The link on Mega is down. Do you have a working image for the mdz-16-ab still? Thanks :)
[Android Stick & Console AMLogic based Computers] jrs007:
unfortunately the bootloader blocks the recording, it can be the dtb files. Does not work. sorry
[Android Stick & Console AMLogic based Computers] darthcircuit:
That’s ok! Thank you for your help
[Android Stick & Console AMLogic based Computers] venioni:
Can you make a patch rom from mi box 3 China to flashing on my mi box 3 international ?

Στάλθηκε από το ONEPLUS A5000 μου χρησιμοποιώντας Tapatalk
[Android Stick & Console AMLogic based Computers] bigtalker:
What are you trying to accomplish?

What build are you currently running on your mdz-16-ab?
[Android Stick & Console AMLogic based Computers] venioni:
Yes , my current mi box is the mdz 16-ab international and is totally bricked , i want to know with some how if we can flash the bootloader and recovery img ?

Στάλθηκε από το ONEPLUS A5000 μου χρησιμοποιώντας Tapatalk
[Android Stick & Console AMLogic based Computers] bigtalker:
Any light on front when you apply power? If you have blue light, try following link. If no light, its truly dead

try this first aid...

https://www.reddit.com/r/AndroidTV/comments/9fo34b/xiaomi_mdz16ab_solution_to_downgrade_from_flaky/
[Android Stick & Console AMLogic based Computers] venioni:
Can someone with dev skills can help me to flash bootloader and recovery.img on my mi box 3 international version? I have connected my mi box 3 board with usb uart 2102 on txd and rxd but i don't know how to send - flash the bootloader.img and which programme or what command i can use to flash.

Στάλθηκε από το ONEPLUS A5000 μου χρησιμοποιώντας Tapatalk
[Android Stick & Console AMLogic based Computers] karige:
Deleted
[Android Stick & Console AMLogic based Computers] ilkz:
Hi dears )

I buy a MDZ-16AB and try to resolder emmc from 8GB to new 32GB-chip. But i forgot to save old emmc dump. Therefore at now i have totally bricked device, lol.

Now i have a this info in COM-port:

GXL:BL1:9ac50e:a1974b;FEAT:BDFD71BC;POC:2;RCY:0;USB:0;EMMC:0;READ:0;0.0;CHK:0;

So it mean that i havent any bootloader, just clear flash memory.

USB Burning Tool is not help me - i have same DDR problem (when flashing) as many peoples here.

At now i trying to access emmc directly, thru card-reader or other method, but still no have a progress...

So does anybody flash AB device? Any news?

I believe that we can change the world together ))

Thanks!

UPD:

For COM-port i use pins from this post: https://xdaforums.com/android-stick...omi-mi-box-3-mdz-16-ab-boot-log-uart-t3702010

For terminal i use the PuTTY, speed 115200.
[Android Stick & Console AMLogic based Computers] mikescorei:
just did a stupid thing, after Oreo update on my MiBox S MDZ 22 AB everything went down, wifi connection drops in every 10 seconds, so I used a version of android from a MDZ-16 on a stick and tried to flash on a tutorial found on the web. It started to flash for a few seconds and total brick!

Now when I plug it, have no signal on hdmi, no led on front, nothing. :((

Can I restore the life in the box or no? Is it totally lost?

---------- Post added at 06:09 PM ---------- Previous post was at 06:08 PM ----------

Are there any test points for MDZ 22 AB?
[Android Stick & Console AMLogic based Computers] edwiniwde:
xiaomi mi box

Gracias por la ayuda, espero logre recuperar mi box tv
[Android Stick & Console AMLogic based Computers] averrone:
Some solution?

Someone? I have a bricked Mi Box 4k on Oreo
[Android Stick & Console AMLogic based Computers] bigtalker:
Define "bricked"?

Do you have any lights after you apply power?

If yes, you just need to manually reflash firmware. Look at this link...

https://www.reddit.com/r/AndroidTV/comments/9fo34b/xiaomi_mdz16ab_solution_to_downgrade_from_flaky/
[Android Stick & Console AMLogic based Computers] averrone:
Only power led is on. No image, just a black screen

---------- Post added at 12:44 PM ---------- Previous post was at 12:35 PM ----------

Only power led is on. No image, just a black screen
[Android Stick & Console AMLogic based Computers] simona70:
flash stop a 2% with error:

[15:52:43 476][HUB3-4][Err]--[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error

hints?
[Android Stick & Console AMLogic based Computers] averrone:
Same error here. I've tested Reddit tutorial and doesn't works
[Android Stick & Console AMLogic based Computers] bigtalker:
The link I posted was specific to MDZ16AB
[Android Stick & Console AMLogic based Computers] simona70:
My is MDZ16AA. hardware is the same. but you say this is the problem?
[Android Stick & Console AMLogic based Computers] bigtalker:
Have a look at this thread from the beginning, mdz16aa specific recovery solutions outlined
[Android Stick & Console AMLogic based Computers] harrybuckman:
Turn out this is for the mi box s not the mi box mdz-16-aa

---------- Post added at 11:02 AM ---------- Previous post was at 10:46 AM ----------

[/COLOR]
[Android Stick & Console AMLogic based Computers] venioni:
This is for the MI box S
[Android Stick & Console AMLogic based Computers] 7maya7:
I bought Mi Box and since I turned on the TV I only see this screen. It never worked for me.

Can anyone help?

I already tried resetting with the remote control (push back + confirm) and nothing. I can not enter recovery mode. I already tried it with remote control, with USB and nothing. I am trying to recover with the USB_Burning_Tool program on PC. It recognizes the device but does not pass ROM. Shows error message = [0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed.

The power supply is ok, the HDMI cable is ok, remote control I tested on the smartphone and it is ok. It looks like it's in a loop but it does not come out of that screen up there and when I try to reset it by remote control, it rarely blinks in black. I think the bootloader is corrupted. I think I'll be able to sort through rom stock but I just see error messaging.
[Android Stick & Console AMLogic based Computers] bigtalker:
What is the exact model number as in MDZ-XX-YY?
[Android Stick & Console AMLogic based Computers] ilkz:
MDZ-16-AB