Related
https://mega.nz/#!BKQS2a4K!G5YrKHWUy2HvL2TOqOlLzwn7Sulp7q8i7-h8uVi0uk8
UNIVERSAL V2 - IF TOP DONT WORK
https://mega.nz/#!bphxHJBB!jRhp0AeNa8orSwscFJHJdE7M14_GxQgbHpnbq-21vy8
Step 1 Download & Extract the bundle for your device
You will be getting either a zip or 7z file, personally I would use 7zip to extract these files, you should get a recovery.img and also a folder called TWRP. If you have these two things move on to step 2
Step 2 - Locations
Both SD Card and USB being formatted Fat32 - Some boxes except most s905 you can use the SD card for both TWRP folder and recovery.img, Regardless I use SD only for recovery.img, so drag and drop the recovery.img onto the Fat32 SD Card and Drag and drop the TWRP folder onto the Fat32 USB drive. Done
Step 3 - Formatting before installing.
Connect everything but the power - Connect a real USB mouse/Airmouse to the box due to the regular remote will not work, connect the USB drive and connect the SD Card, Everything but power. Some boxes have a reset button on the side and some the reset button is inside the AV jack, you will feel it, If in the AV jack simply use a toothpick or use a Q Tip with the cotton end removed and slide it in the AV jack and you will feel the button.
HOLD THIS BUTTON AND DO NOT LET GO - At the same time plug it in and keep holding, boxes with physical power button press this now. You will be presented with a blue screen, you will get a read only scren most likely, slide to proceed.
First thing first I always recommend backing up partitions incase something is to go wrong. There are tons of cloned boxes its hard to cover them all. I personally would go to backup. Locate where it says storage, and change from internal to usb otg for USB drive or external sd for your SD Card. Backup all your partitions.
When done, go back. Press the little house button on the screen or the back button until back at the TWRP menu, go to restore, Make sure usb otg or external sd is chosen, wherever you put the TWRP folder, If you are using a box not from me PM me the model and I will confirm what to restore, for example, M8, M8S BCM and AP models, MX3, M10, You can restore all, S912 boxes some are different so PM me to be safe. After I tell you what to restore do so. Let it do its thing. Once done, reboot and enjoy. If it fails by any means. Do not reboot, just go back and choose wipe, format data, type yes press enter. Once done just go back and restore data JUST BY ITSELF so untick everything but data, once finished restore all the other partitions. All done
Enjoy the build - When you first boot my firmware let it sit after it boots for a good minute or two. It will auto load my custom firmware patches and more.
If you are using M8, M8S, M10, MXq you need to follow below -
When you start the TV box. Let it sit a few minutes and first things first. In Android applications click on No Frills CPU - the accelerometer and when it opens click apply and than exit. It is super important with my custom rom to unlock the other 2 CPU Cores and the other 4 GPU Threads. If this does not make sense just go into my apps and look for no frills, same app as on the desktop you will just see the name instead.
NOT EVERY FIRMWARE HAS NO FRILLS - IF NOT DO NOT WORRY ABOUT IT.
i do not own the firmware
credits go to ghostware.
Congrats!
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
MyM8SFinallyWorks said:
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
Click to expand...
Click to collapse
i used a m8s+ rom and the 5.1.1 rom from acemax the only problem is with the m8s+ rom is ethernet dont work so by doing this i got ethernet to work.
Thanks for this link
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
lutty321 said:
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
Click to expand...
Click to collapse
you have to open it and look inside
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Tazosman said:
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Click to expand...
Click to collapse
if you have the recovery.img file on the root of the sd card, toothpick method should take you to TWRP where you can then flash the zip. did you give it some time (with the reset button pressed in)? it can take approx 10 seconds sometimes.
Failed signiture
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Hi
i just tryed this metod but my M8S does not respound anymore(no on light) it seems dat it is deed???Has any body iedea what can i do now?
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Devmau53 said:
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Click to expand...
Click to collapse
Either your download is corrupt, or you are not using TWRP to perform the update.
Has anyone been having random freezing and reboots?
wolfpack64 said:
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Click to expand...
Click to collapse
I also had that problem even though I flashed the square remote zip after the lollipop update. I might have flashed the M8N remote though to be honest and I don't have the box anymore to test more remote patches.
You can try the M8S remote zip from the link below and report back if it worked for you.
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s802/eny-acemax-ott/firmware-roms-tools-af/18312-s802-multi-remote-patcher-zips
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
highpoiss said:
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
Click to expand...
Click to collapse
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
MyM8SFinallyWorks said:
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
Click to expand...
Click to collapse
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
highpoiss said:
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
Click to expand...
Click to collapse
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
MyM8SFinallyWorks said:
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
Click to expand...
Click to collapse
Same problem installing acemax firmware over original 4.4 rom wil brick my device brick at first boot.
Help needed M8S ap6360 v1.3 20150921
Can someone make a TRWP backup from this rom ? specially the boot file
Also want to know where to download the M8s+ rom what daniel uses in this treat
Thanks
Hi d4nielr,
Wanted to thank you for the excellent work in compiling this ROM to support m8s app6330.
After trying out various ROMs and in the process bricking my device several times and un-bricking it using the burning tool, I finally came across your forum.
Thanks for the wonderful rom and the installation was a breeze and smooth sailing throughout.
Btw, for the installation I can only use the other most USB port. If I insert the sd card into the inner most usb port, it will take me to the bootloader.
So, for the TEAMWIN logo to appears, I need to put the sd card into the outer most usb port which is located at the back of my m8s unit.
cheers.......
Update.....
Unfortunately, after a cold boot, it doesn't work any longer. Back to kitkat using usb burning tool.
Hello. I have been given this box by a friend as it as misbehaving. I flashed it with the latest MX firmware(1.6) and now it wont boot. It gives me a blue light and the box is seen by my PC and USB Burning tool. I cannot get into recovery mode with the tooth pick method. I also tried Bennies magic files with now luck. I dont know what firmware was on the box originaly but it had Openelec installed. The Board is a HD18 V2.22. Any help would be appreciated. Thanks
kPATm said:
Hello. I have been given this box by a friend as it as misbehaving. I flashed it with the latest MX firmware(1.6) and now it wont boot. It gives me a blue light and the box is seen by my PC and USB Burning tool. I cannot get into recovery mode with the tooth pick method. I also tried Bennies magic files with now luck. I dont know what firmware was on the box originaly but it had Openelec installed. The Board is a HD18 V2.22. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
kPATm, did you have any luck or receive any help elsewhere? I'm in the same position as you
I have not mate. I keep coming back to it after a few months. I just looking into it again and thats how I found my old post. Sorry
maiz box
i got the box two and not boot up and no recovery it had Openelec and kodi 14.2 got no firmware for it
Hi guys,
Hope it's ok if I start this thread, I just wanted to give new users some feedback before/ after unlocking and flashing an India ROM on my sealed China ROM K20 Pro (8/256). It might be useful to some, or maybe even help others. Thanks a lot to Robbo.5000, Madsponge and Hursty UK (hope I got it right?) among others for their help and advice.
- [BUYING PROCESS] My trip with the K20 Pro started here: https://forum.xda-developers.com/k2...ice-to-buy-t3939616/post79918346#post79918346 (about 18 days to get it from China during high season, not too bad I guess). (FYI, the real Global version will come out in Europe in a few weeks but the 8/256 won't be available here.)
- [UNLOCKING PROCESS] I then started the "infamous" unlocking process which triggered the even more "infamous" unlocking wait time. Why did Xiaomi choose to do that? Pretty strange if you ask me. Why should you wait 5 days or more? Anyways, in my case it was almost 6 days. That part of the process went smoothly (I run a kinda old Windows 7 PC). I rebooted the phone and it was unlocked indeed. Then started the stressful process: flashing a +400 euros phone without knowing if it would actually work. Kinda reminded of the time when we "backuped" PS1 (PSX) games, haha.
- [FLASHING PROCESS] I used the official MiFlash tool, with the official India ROM (fastboot file, .TGZ extension). First problem : MiFlash couldn't install the drivers because a /log/ folder was missing, which I had to create manually (didn't see that mentioned on the forum, but might be my OS? Oh well). The rest was OK until I launched the flashing process and hit the "clean all" button (I carefully didn't choose the clean all and lock which would have bricked the phone).
>> Link to the official India ROM Fastboot .TGZ -> http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
>> Link to the official MiFlash tool I used -> https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
>> Use the official Xiaomi USB-C cable - do not try another USB cable
>> Important reminder: please change the default option in the flashing tool and DO NOT choose "clean all and lock". Change it to "clean all" only (you don't want to lock it as you might brick it - see posts below about this)
- [STRESSFUL REBOOT] The flashing process ran for about 10 minutes, said "error: Not catch checkpoint (\$fastboot -s .*lock)". Needless to say I was very stressed out at that point, especially with the not cool red message "error" on the right of the tool, in the column "result". I thought the phone was bricked...but no, it just rebooted normally with the India ROM on it. Honestly I don't know what happened, if it was normal or something but I didn't see anyone mentioning this.
Some feedback post flash: everything is fine, the phone seems even faster than on China ROM but it might be just an impression. I do not like the POCO launcher at all, when you're used for 4 years with the classic MIUI launcher it's honestly a pain, I like to see all installed apps on the home and next screens. I had an issue with my Mi Cloud backup (home screen): Mi Cloud said there was no backup even though I did one just before flashing. The rest of the sync process (except home screen - maybe because of POCO launcher?) was fine though: pics, notes, calls, messages, etc. Too bad we're missing NFC but it feels good to be back on "Global" (was coming from a Mi 8 Global phone). Oh yeah, missing the multiple shots option from the China ROM (where you can choose the "best" shot), but it will come to Global one day I guess.
- [MI CLOUD BACKUPS] I can confirm the Mi Cloud home screen backup issue described above is indeed because of the POCO launcher: my previous backups didn't have it (Mi 8 Global, K20 Pro China) and so Mi Cloud couldn't restore from those backups. I now have a POCO launcher backup (daily in Mi Cloud) and I can restore from those. So keep that in mind: if you come from non POCO you won't be able to restore home screen, but same thing if you move from POCO to a non POCO launcher. If you're not familiar with those backups, it's very practical (usually...) when you change phone because you just have to restore it and you'll have all your icons, apps and stuff like before.
[UPDATE] As you might know, a European Global version will be released in a few weeks, let's see if it has the POCO launcher or not.
Thanks again all for the help and let me know if you have more feedback.
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
You need to fully unpack the ROM. It requires unzipping twice. You now need to extract everything from the tar file. After extracting the tar file you should have a folder with all the ROM image files and some .bat files. Point the Mi Flash Tool to this folder.
The phone needs to be booted into fastboot mode. The PC should recognise the phone automatically if it has all the correct drivers installed.
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
i failed multiple times to flash the global india rom before(using winzip to extract). and I tried again extract the files using winrar and it succeed. i'ved been using it almost 2 weeks now. the issue that i am facing is i cant use earphone mic on discord and whatsapp call. the rest is fine. for the updates, i get it from system app updater in settings.
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
I forgot to mention it, yes you do have to extract it (using WinRAR or similar) until you get an actual folder like Robbo.5000 said. I then renamed the rom's parent folder as "raphaelin" because another user mentioned we could have issues if the folder's name was too long.
About the USB connection i didnt change anything, i left it by default.
hippo2s said:
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
Click to expand...
Click to collapse
I'm guessing your phone is already in fastboot mode (with the little Mi cartoon guy)?
I installed ADB minimal, the MiFlash drivers but also ADB Lite drivers (mentioned in the big Madsponge thread where you can find the links). That might help.
In MiFlash when i hit Refresh it saw the phone as some ID like 1d23456 or something.
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
piqiee said:
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
Click to expand...
Click to collapse
I dont think there is an update since 10.3.3.0 but i guess we'll find out with the next OTA update. I read somewhere an automatic update might lock the phone back (and brick it) so i disabled them for now, until we know more...
Of course Chinese OTA was fine on the China ROM.
hippo2s said:
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
Click to expand...
Click to collapse
In fastboot mode you cant change it on the phone if i remember, and its set automatically in file transfer mode i think.
Yes I installed those drivers too. I might try a different laptop and usb cable tonight.
Thank you so far for your help.
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
DontDamnMe said:
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
Click to expand...
Click to collapse
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
theincognito said:
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
Click to expand...
Click to collapse
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
DontDamnMe said:
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
Click to expand...
Click to collapse
Thanks mate. Just one more thing. Could you play "Test Patterns" - S1:E1 video, zoomed out for 2 mins, in Netflix app?
It will initially show "960x540" (right top corner of the screen in zoomed out mode), but after 2 mins, does it change to "1280x720" or still stays at "960x540"??
Again, thanks in advance!
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
I think its only "soft bricked". Another user had a similar issue and created a thread below. Experts here will be able to help you for sure. If its locked i believe you have to reinstall the China stock ROM.
About Netflix it stays on 960, so no HD i guess...
hippo2s said:
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
Click to expand...
Click to collapse
Just download the china latest stock rom or china latest dev rom (recovery rom will be enough), no need of mi flash.
Then go to this link and follow the instructions. Since you can access the recovery, you are fine mate.
PS: Use the latest official Mi Assistant app from the MIUI site, not the one given in the link above. But the steps are the same.
Thanks guys I will try. Really worried that phone doesn’t shut down it keeps going into recovery (doesn’t power off) and charging doesn’t seem to work in all these conditions.
Will work quickly
---------- Post added at 12:15 PM ---------- Previous post was at 12:04 PM ----------
err... thats not the Mi PC Suite is it? when i google miphone assistant thats what comes up...
Err...not detecting my phone so the PC Suite can't find the device
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 ! )
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Reserved for future shenanigans.
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
effgee said:
Hi everyone,
Updates:
2021-08-17 - Added patched Magisk boot for this device. (Conceptum Stock ROM)
I'm starting this thread to collect information and files regarding this particular version of X96 box and to explain to anyone interested what I have discovered so far..
The company who has repackaged the firmware for this box for the Greek market, CONCEPTUM, refuses to release the original firmware for this device.
So currently, I have dumped two types of firmware from a stock box in case it is needed. A standard TWRP backup, and a dd image.
At the moment, I actually am NOT having any luck restoring the firmware using the TWRP restore. Not sure why.
I was able to restore the original firmware using the dd image. So for anyone who screws up their stock firmware, you can use the dd image from the mega drive. Punchline: The stock image has terrible wifi speed as well. I have yet to try restoring the firmware via dd yet but when I do I will write if it works or not.
Here is a link to the folder where I will be updating what compatible files I can find.
4.38 GB folder on MEGA
13 files and 6 subfolders
mega.nz
This post is very incomplete and I will be adding to it shortly.
--------------------------------------
SPECIFICATIONS
4GB RAM/32GB Storage
Ethernet Speed: 1000mbps / 1gbs
Ethernet Chipset: Realtek RTL8211F
Wifi : 5ghz & 2.4 ghz support
Wifi / Bluetooth Chipset: Cdtech 4761743 (which is a Qualcomm QCA6174A design? See links below.)
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/248
https://discourse.coreelec.org/t/looking-for-users-with-no-working-wifi-or-bt/9649/249
https://blog.csdn.net/u012851408/article/details/86605778
Motherboard Markings: BM805H_141 V3.2 20352 4020
Motherboard Sticker: 4+32+CDW ZF210129
---------------------------
How to get into recovery
The button needed to access recovery is hidden. It is deep inside the stereo jack. (You can see it if you shine a flashlight into there.
My suggested tool to press this button easily is a qtip with the cotton from one end removed.
Insert the tool, and press it in until you feel the click.
Apply power to the device and as soon as you can see the logo come on, release the tool pressure.
It should enter recovery in 5 to 10 seconds.
---------------------------
CoreELEC
I was able to boot CoreELEC via sdcard, with bluetooth and wifi working with the following device tree:
sm1_s905x3_4g_1gbit.dtb
I forgot to check the speed of the wifi, but if I recall, both 2.4 & 5ghz was working with that dtb.
---------------------------
TWRP
The TWRP_AML_ViT_3.3.1_2020.zip (in the Mega folder) is a "hinged" version. Not sure if its the right term, but it can be run from the stock recovery, (Apply update from external). It does NOT install, it just runs it and lets you do stuff from there.
If anyone knows the source or an update for the Amlogic TWRP Hinged version, please post it here.
I used a previous "hinged version" TWRP_322.zip but this version did not backup properly all the partitions, ex it totally skipped the Vendor partition, which is why I have 2 of these Tvboxes as my first one the backup was bad and it was essentially bricked.
---------------------------
Amlogic USB Burning Tool
This seems to work fine, but something that is always missing from peoples instructions,
The Male to Male USB cable, on this device must be plugged into the USB 3 port.
The power cable must also be removed, and when plugging in the USB cable to the correct port, will provide power for the "fastboot" equivalent mode needed to flash from the Amlogic tool.
So the procedure to flash is (after installing the USB Flash tool)
Device is powered off.
Insert USB cable into your pc end.
Insert tool and press recovery mode button.
Plug in other end of USB cable into the tvbox.
It should power on, keep the recovery button pressed until you hear the device connect to Windows (USB being plugged in sound)
They you should be able to flash.
---------------------------
Compatible ROMS
Long story short, due to a initial TWRP backup that was missing certain important partitions, I bricked my first box.
While trying to get the box working again, I have found the following firmware to work mostly. I am not reccomending them, as I am not sure they are working optimally, but if needed these can boot the system and work in some capacity.
X96Max_Plus_Q2_20201209-1446.img
Original firmware for X96 Max Plus Q2 version
sbx_x96max_plus_q2_v12
Slimbox Version 12 for X96 Max Plus Q2
This version does not come with Google framework which I needed so I didn't work with it much.
---------------------------
Magisk
Patched boot image for this device.
9.67 MB file on MEGA
mega.nz
Download and extract this file and put it somewhere you can flash from.
Install Magisk Manager.
Boot from Hinged TWRP, goto Install, Install image, select the file and flash to Boot partition. BE CAREFUL AND DON'T FLASH TO BOOTLOADER
Magisk Should be working, try running a root app and magisk should pop up
Magisk is complicated. On all the Amlogic boxes as far as I know, Magisk will install but NOT function properly.
The geniuses at 4pda have figured out a procedure to make Magisk work properly, but it requires hex editing the boot partition and reflashing it.
I have done the procedure successfully when I was using the X96Max_Plus_Q2_20201209-1446.img firmware. It does work.
I will upload this to the mega folder when I have time.
When I manage to hex edit the stock boot image, I will also upload it. Its an involved process and takes some time.
Click to expand...
Click to collapse
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
reza0511 said:
i have a full twrp backup but unable to go to recovery to unbrick my device or will you change twrp backup to img file so that i can burn that with usb burning tool ? full detail of the problem in the previous post
Click to expand...
Click to collapse
Regular Air firmware's do not work.
P1-P3 don't work for sure, P4 I don't know but I think not.
I haven't found a photo yet of the P4 hardware.
Try USB Flashtool 4/64 image for X96Max_Plus_Q2 to get your recovery back if such a firmware exists, otherwise try the 4/32. X96 Max Plus Q2 firmware (X96Max_Plus_Q2_20201209-1446.img)
You should be able to get recovery back via flashing one of those images.
X96 Max Plus Q2 firmware is compatible, but if you use the 4/32 image you will only see the half of your storage.
Restoring your TWRP full backup again once you get the max firmware (for twrp) installed will not work unfortunately. Already went through this.
reza0511 said:
my device has the same mainboard as you mentioned above ,but mine is 4/64 , my device bricked after burning non related image and after i plug in the power , for first 5 minutes nothing happens and then in vfd it shows boot and then clock and on tv screen only boot logo appears after 5 min but non consistent if you change tv source and back again it shows no hdmi connection and nothing more happens.
i tried out all p3 version of x96 air images but useless because they have different main board i wanted to try your dd imade backup (twrp is impossible bacause of no recovery) and burn it with amlogic usb tool but extraction of image ended with error with more than 15 gigabytes .
i appreciate anyone who can help me to unbrick my device , i am hopeless because this device has no support mine is named,x96 air 4/64
Click to expand...
Click to collapse
You have a Conceptum box or just the same motherboard?
If you have a Conceptum, you are pretty much ****ed. They wont release the original firmware. You will have to buy a second box and get the image via dd.
I had to buy a second box and get the disk image via dd, and then restore the dd image using dd from within TWRP, overwriting the entire storage with the image. This was using the terminal built into TWRP.
In general, restoring from TWRP doesn't work well on these boxes, especially going from rom to rom as the partition layouts are different and TWRP doesn't handle it correct.
Conversion of the dd image to usb flashable is tricky and I haven't done it.
The person that MAY be able to do such a thing is Ricky ( https://forum.xda-developers.com/t/...w-milestone-donate-version-available.3786991/ ) but I dont know and I don't think there is any point as my dd image has partition layout for 32 gb version, you will lose half your storage unless he can also expand the partition.
Even if you manage to get TWRP back, there will probably be a partition layout difference from the firmware you use to get TWRP on the box, and the TWRP image backup you did. It probably will not work.
You need to get your original firmware, or a dd image of the same box.
You can also use the Slimbox for x96max_plus_q2. I did NOT like Slimbox 12 because it was missing google play and a lot of other things. But it will restore recovery.
solved !!
i save my box by below two steps
1- burning veitnami atv version of x96air img file (google for link )
2- restoring my full twrp via recovery
reza0511 said:
решено !!
Я сохраняю свою коробку, выполнив следующие два шага
1- сжигание veitnami atv версии файла img x96air (гугл для ссылки)
2- восстановление моего полного twrp через рекавери
Click to expand...
Click to collapse
is there a link?
Я уже решил свой вопрос. Спасибо за ваш сайт. Меня интересовало восстановление кирпича x96air_100. Я из Украины.
I have already solved my question. Thank you for your site. I was interested in the restoration of the brick x96air_100. I am from Ukraine.
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Soldiaz said:
How you did get MAGISK working? I own x96 AIR P3 and would like to use MAGISK
Click to expand...
Click to collapse
Hi.
To get Magisk working, its a bit of a difficult process.
Essentially, Amlogic released / built their kernels with a kernel boot option "skip_initramfs" which magisk needs "want_initramfs" for this to work.
The process is complicated as you must hex edit your boot.img after you have patched it with the Magisk Manager patching method called "Recovery Mode"
4pda where this was discovered - https://4pda.to/forum/index.php?showtopic=774072&st=25020#entry91068157
Video from 4PDA that shows the hex editing process - https://mega.nz/file/pJ1RTChR#b5rLNs-4GF2qlZXKzbL0P5lmAeLLYObJ_w3_Yf8h16U
You can also get the video from the above thread but if I recall you must register to download and unless you know russian its difficult to register there.
A guide I wrote that you can follow along with the video to understand the process - https://rentry.co/wgu9u
Every detail matters, I studied the video for many hours to understand the process, good luck.
My thread about this process here: https://forum.xda-developers.com/t/...ide-to-accompany-video.4320923/#post-85493037
Thanks!!!! Dam looking not that easy .
The Boot img from x96 Air you edited, is it Stock?
Sorry i dont check my mesages here very often.
I don't know which boot image you are talking about, it would be very helpful for you to link me which one specifically I need to answer the question for..
If you are talking about the image for my Air Extreme, it is stock and patched by magisk, and then hex edited for magisk. But I dont know its compatibility for any of the other Air versions.
effgee, just wanted to let you know there is a lot of information and multiple versions of the X96 Air TV Box Firmware available at...
Original Google link... (Vietnamese)
https://www.google.com/url? sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwiDtPO9yZj0AhUOXM0KHYnzCIUQFnoECA8QAQ&url=https %3A%2F%2Ftinhte.vn%2Fthread%2Ftong-hop-cac-ban-firmware-cua-android-tv-box-x96- air.3050996%2F&usg=AOvVaw1it1QO7hR_e5XsrdSZH-Rj
Google Translated (English) link...
https://tinhte-vn.translate.goog/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/? _x_tr_sl=vi&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=nui,sc
Direct link... (Vietnamese)
https://tinhte.vn/thread/tong-hop-cac-ban-firmware-cua-android-tv-box-x96-air.3050996/
"X96 Air" search via direct link... (Vietnamese)
https://tinhte.vn/search/333184298/?q=x96+air&o=relevance
Hope they help!
Mr350
Ps... If you have trouble with the Google translation links not working try a Google search for... x96 air tinhte.vn ... that might work then click Translate this page.