My M9S-Pro finally arrived. It's a modest AmLogic S905 chip with a Mali-450, notably only because it has Ethernet, three USB ports, 3 GB of RAM and a 32 GB ROM.
My kids use the Nexus Player as a gaming device, but I am constantly running out of space even with Marshmallow's USB space reallocation (which does not work perfectly by any means). I bought this hoping to replace the Nexus Player which only has 8GB (+ whatever Marshmallow offers, and whatever some apps will allow transfer to external storage).
Right off the bat, it boots quickly and is stable. It included Kodi, some generic TV streamer with pay TV streams in foreign languages, a file manager, Antutu, various video players, and Netflix. The USB port puts out enough current to power an external 2.5" HDD.
Antutu score is 31,300 if that matters to you.
I found a version of TWRP that worked great and I rooted this by flashing the same beta-SuperSU as I used on my Nexus Player.
It uses an IR remote with shortcuts to different apps and a mouse function. It's slow but usable. I use it with an airmouse with a better experience.
I am running HAL Launcher which is just about the best experience you can hope for with a Chinese box. I also added the keylist for the Bluetooth controllers from the OUYA that I had years ago, and my kids use it for a gaming box.
It's a good value for me, but if you use Android TV boxes for streaming only you don't need the space and should probably get a cheaper box - maybe one running 6.0+ so it supports the latest version of Kodi.
Now that I have TWRP and root, I am looking for an AOSP experience.
Are these available for AmLogic systems? I've seen RemixOS for certain AmLogic boxes, but they're all a bit different and haven't tried experimenting with that yet.
How did you get this device rooted and how did you boot it into TWRP?
If rooted the Docooler, could I run a Long Term Release of Ubuntu or Mint on it. I've used Linux with our Brother MFC-J835DW and its simple to print from any Application. Android not good at all. 2nd is with Ubuntu I can set up multiple guest users in various Languages "English" " "Spanish" etc. so a guest can log on , browse, print, done.
On Android it seems to remember Users, not sure how to delete,
Very hard to print "share",
Doesn't appear to allow set up to multiple users so can only run as 1 language.
I really like that these boxes have separate monitors, keyboards, and appear not to require a fan as we are at the beach with a lot of salt air. All my connections require DiElectric Grease from Autozone so as not to corrode. Even better would be a sealed heat sink case.
Ken PlayaLindaHotel.com
root m9s-pro docooler amlogic s905 how
how root and install twrp in that model please tell me
Send me the links of software that must to download
hello, i have the m9s pro 32gb and i have slow speed in WiFi connection. Does anyone have the same problem and how can i solved? thanks in advance
Hello everyone, where can I get the original stock firmware? tnx
shdware said:
My M9S-Pro finally arrived. It's a modest AmLogic S905 chip with a Mali-450, notably only because it has Ethernet, three USB ports, 3 GB of RAM and a 32 GB ROM.
My kids use the Nexus Player as a gaming device, but I am constantly running out of space even with Marshmallow's USB space reallocation (which does not work perfectly by any means). I bought this hoping to replace the Nexus Player which only has 8GB (+ whatever Marshmallow offers, and whatever some apps will allow transfer to external storage).
Right off the bat, it boots quickly and is stable. It included Kodi, some generic TV streamer with pay TV streams in foreign languages, a file manager, Antutu, various video players, and Netflix. The USB port puts out enough current to power an external 2.5" HDD.
Antutu score is 31,300 if that matters to you.
I found a version of TWRP that worked great and I rooted this by flashing the same beta-SuperSU as I used on my Nexus Player.
It uses an IR remote with shortcuts to different apps and a mouse function. It's slow but usable. I use it with an airmouse with a better experience.
I am running HAL Launcher which is just about the best experience you can hope for with a Chinese box. I also added the keylist for the Bluetooth controllers from the OUYA that I had years ago, and my kids use it for a gaming box.
It's a good value for me, but if you use Android TV boxes for streaming only you don't need the space and should probably get a cheaper box - maybe one running 6.0+ so it supports the latest version of Kodi.
Click to expand...
Click to collapse
dow did you root the device?
@alexxdj,
You'll need to do two things.
First, download TWRP for AmLogic devices. The link is below for a whole bunch of them.
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/16228-twrp-for-amlogic-devices
I don't remember which one I used, but I believe it was for a Minix S905 device. As long as it's S905, they are similar enough that you should be okay. Make sure it is scaled properly when you use it.
Then you'll need to download ChainFire's SuperSU.
https://download.chainfire.eu/743/supersu
Copy both files to a SD card. TWRP will be bootable, but you will need to press/hold the button that's hidden in the audio out jack. I simply used a pin. So, unplug the unit, insert the SD card, insert the pin, then plug it back in and wait for it to boot to TWRP.
If all looks well, great. You will need a mouse for this part.
Flash SuperSU as normal. Reboot.
After I booted, I actually had to run the supersu APK to make it work properly. I used Root Explorer (since it opens files in zip files with ease) to do this.
I hope this helps.
thanks for your information but where is this hidden button? I cant find it!!!
It's in one of the audio jacks in the back of the unit. Open it up if you need to see it: it comes apart easy and goes back together easy.
Otherwise get a long pin or needle and poke in the jacks until you feel it click.
shdware said:
It's in one of the audio jacks in the back of the unit. Open it up if you need to see it: it comes apart easy and goes back together easy.
Otherwise get a long pin or needle and poke in the jacks until you feel it click.
Click to expand...
Click to collapse
i found it is the spdif jack thanks. do you remember if needs to rename the recovery? Because i downloaded the recovery for minix s905 but i cant boot it to twrp
Try naming it 'recovery.img'
The recovery should not be zipped. Extract the IMG file if it is.
yes i know that. maybe i tried wrong recovery. after 2 times failed to boot to recovery. when i release the button? when i show the android and starts to erase?
alexxdj said:
i found it is the spdif jack thanks. do you remember if needs to rename the recovery? Because i downloaded the recovery for minix s905 but i cant boot it to twrp
Click to expand...
Click to collapse
I press and hold it until the TWRP logo appears.
I think you have the wrong recovery. Try the MINIX MX one. AmLogic makes a lot of devices, and the S805, S812, S905, and S912 all require different recoveries.
You need to make sure it's for the S905. Google is your friend here.
After I successfully rooted, I ultimately decided to flash TWRP itself on my box.
i tried 50 recovery for s905 form yesterday but nothing. Cant boot to twrp!!
alexxdj said:
i tried 50 recovery for s905 form yesterday but nothing. Cant boot to twrp!!
Click to expand...
Click to collapse
Apologies, I didn't realize the URL to Freaktab was truncated. I've corrected it now.
TWRP for AmLogic Devices
Try a few of these. There are only 31, and over half of them can be discounted because they are not for the S905.
If I remember right, I used this one:
/TWRP_MiniMX.img
shdware said:
Apologies, I didn't realize the URL to Freaktab was truncated. I've corrected it now.
TWRP for AmLogic Devices
Try a few of these. There are only 31, and over half of them can be discounted because they are not for the S905.
If I remember right, I used this one:
/TWRP_MiniMX.img
Click to expand...
Click to collapse
You remember right!!!! this recovery was. thanks for your help friend.
@Gi3drius, @k_graham, @stilonas -
I've provided a tutorial. Read the comments and let me know if they help.
is there any update for this tx box?? and why do you want to install TWRP? I use it only fr install roms but I can´t find any for this model
Related
Okay, so I picked up an 8 Gig MK802III from Amazon.com. Got a good deal on it. Could have gotten it cheaper if I had wanted to wait for a slow boat from China.
It is a pretty solid unit with the exception of the wifi speed issues. I am pretty sure it is hardware related. Some people have no problems and some do have speed issues. More on that later.
It is a versatile unit. Out of the box it is stable with 720P. The latest factory firmware is JB and it is rooted. That came on my unit. It is dated 11/29/2012 so I am sure there is a lot of stock out there floating around with the older firmware on it. The latest update also includes a remote control server and it also has the .apk for the client software to install on your phone or tablet.
Within a day of me getting it though, I found my tinkering taking over. I found a site that had some custom ROMs. www.freaktab.com
The ROMs that work on this unit are actually written for a UG802. Same unit different seller. They are identical units. The ROM is made by Finless and 2dark4u. They are very responsive in supporting their work.
When flashing the ROM you have several options with which to choose when it comes to a kernel. You can choose between 720P or 1080P, and processor speeds of 1272Hz or 1608Hz with the GPU at 466. Then there is the option of 1080P 1608Hz and GPU at 500. That is a total of 5 custom kernels. Although the MK802III is an Arm 9 capable of peaks of 1608Hz, IF YOU RUN A ROM AT 1608Hz KERNEL YOU MUST RUN A HEAT SINK OR YOU WILL BURN IT UP.
I chose 1080P at 1272Hz because I didn't want to mess with a heat sink at this time.
Back to WIFI. I may end up getting an RMA if an easy fix is not found soon and try another MK802. I like it that much. The mfg is working on a fix supposedly for the units that are having trouble. Again it is not everyone having a problem. I can connect fine. DL is extremely slow at around 500k and upload at 2Mbps. Not sure why upload will reach the limit set by my ISP while the download sucks. I have ruled out under-powered power supply, encryption bottlenecks (I tried my AP wide open), and case interference. As a temporary measure I picked up a USB LAN adapter at Best Buy for $19. It is marketed as and adapter for a Wii but it works fine. But i really need the wifi so i can make this unit portable.
With the wired LAN I am getting DL of anywhere from 25Mbps to 29Mbps down and 2Mbps up. That is what my cable connection is capable of. So no complaints there.
It streams fine over my LAN from NAS. Youtube and Netflix stream great as well. I don't have HBO Go so I haven't tested that. It has taken everything I have thrown at it so far video wise. And in full blown 1080P!!!
With the 1080P interface it was kind of unreadable on my 50" TV when sitting on the couch. So I set the font size to HUGE in settings and also adjusted the DPI to 240 using ROM Toolbox for making the icons larger. It is not recommended setting it higher than 240. It can cause some problems with the Play store and other apps. ROM Toolbox worked great for this. Prior to trying that, LCD Density monitor from the Play Store locked it up on reboot. This Forced me to flash recovery. When it comes to recovery, everything I am seeing is saying it is almost impossible to brick. To force a full flash it is a matter of shorting two pins on a chip for a few seconds and loading up recovery software and image on your laptop. CWM and TWRP have not been set up reliably yet that I have seen.
As mentioned earlier, it comes with remote software. I initially had problems with it on my RAZR but it worked great on my Kindle Fire. I have now found out that the initial problems on my phone were tied to the JB rotation problem that many are having on custom ROMs. It works fine on stock JB. The problem I was having was the app would close if the screen rotated. This would happen when setting it down or moving your arm the wrong way. Like I said it works great now on stock JB.
When I first set it up I had a wireless mouse hooked up to the USB. That worked flawlessly. I have had to remove it since it only has one USB port and I now have LAN connected to it. But I have one of these on the way which should solve that problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's about it for now but I am sure I am missing a lot. I know I focused a lot on things that weren't perfect but that is how I tend to be. I love this unit and it plays video and browses the web great. And on a 50" screen!!! The apps and few games that I have tried do great.
The unit cannot be expected to be perfect as these TV sticks are very new and emerging. Expect to be somewhat of a beta tester.
EDIT: Stock out of the box AnTuTu was 8080. On the 1080P 1272Hz Rom it rose to 8878. I've seen even higher with the 720P ROM. Can't find the post but i am trying to say it was near 10,000
hi
i have got mk802 ii. it is just single core unit. everything works fine but play avchd files from my camera. could you try it to play some avchd files on your dual core unit?
i can send you a sample video if you are interested.
thanks in advance.
jufo
jufo said:
hi
i have got mk802 ii. it is just single core unit. everything works fine but play avchd files from my camera. could you try it to play some avchd files on your dual core unit?
i can send you a sample video if you are interested.
thanks in advance.
jufo
Click to expand...
Click to collapse
Send me a PM with what you are using to play them. I will send you my email address. You can send there provided they are not too large for email.
Thank you for this. I just picked up the MK802 III today and your write up helped a lot. Now to go find some good roms.
SirVilhelm said:
Thank you for this. I just picked up the MK802 III today and your write up helped a lot. Now to go find some good roms.
Click to expand...
Click to collapse
Here is the best one I have found so far.
http://www.freaktab.com/showthread....-1080-and-overclock-AND-best-performance-ever!
I know it says it is for the UG802, but hardware is identical to MK802III and most people on the site with an MK802 III are running this rom.. I made the mods listed in my first post here as to resolution ROM, text size in settings, and DPI changes using ROM Toolbox for easy viewing from my couch.
I also modded the boot animation to reflect it being an MK802 III. That thread is here if you wish to use. http://www.freaktab.com/showthread....-us-MK802-III-Owners-on-Finless-v1-7-Download
When picking your kernel, do not go above the 1272 HZ unless you install a heat sink. I know the MK803 III is advertised as 1.6 GHZ, but that is peak speed. It will over heat at that if sustained. In the fastest CPU speed (1.6GHZ) there is also overclocking of the GPU option. Same thing. Don't use that without heat sink.
It is stable and works great.
Where can I find the ROM Toolbox for changing DPI?
The Play store. The free version should work for it.
The adjustment is under the build.prop editor. Lcd density
Sent from my Kindle Fire running CM10
Thank you
One other question, is the micro usb port only for power or can I push data through it? I don't have a USB-A to USB-A cable.
SirVilhelm said:
Thank you
One other question, is the micro usb port only for power or can I push data through it? I don't have a USB-A to USB-A cable.
Click to expand...
Click to collapse
It's power only i have the same issue need USB-A to USB-A cable to flash new ROMs
wapvirus said:
It's power only i have the same issue need USB-A to USB-A cable to flash new ROMs
Click to expand...
Click to collapse
You don't need an A to A to flash.
I just flashed a UG802 rom on my MK802III last night, worked great. Device seems smoother, especially after locking CPU to minimum of 1000Mhz / Max 1272Mhz
1. plug MK802III into PC using A side of cable
2. plug micro-b side of cable into mk802III into power port of device
3 plug hdmi of mk802iii into TV
4 after device boots, goto settings -> USB, click connect to computer. ( at this time, computer should start finding the device as a removeable drive, and assign it 2 drive letters, I believe)
5. After computer finds device and loads driver, use RKFlashTool to flash ROM.
(if you get 'change to flash mode failed', or No Rock Android device found, or whatever it says, make sure you have no "unknown" or failed drivers in device manager)
Windows 7 Home Premium 64-Bit was used.
I had some probs getting the correct driver, but a bunch of googling found me the correct RK30usb driver.
If anybody needs the files I used, I can post them tonight, when I get home.
Which ROM did you use? I was thinking about UG802 2dark4u/Finless custom ROM version 1.7 since I heard it works fine with our device.
If you can post a link or actual files for the driver that would be awesome! Thank you.
Hi 85gallon, I've read that the UG802 1.7 rom breaks wifi as the drivers are different. Can you confirm? Did you have to do anything to get wifi back?
SirVilhelm said:
Which ROM did you use? I was thinking about UG802 2dark4u/Finless custom ROM version 1.7 since I heard it works fine with our device.
If you can post a link or actual files for the driver that would be awesome! Thank you.
Click to expand...
Click to collapse
Assuming you were replying to me, yes, I used Finless 1.7, and it works much better than stock.. Still get a lag with my wireless pointer/keyboard (this one: http://www.amazon.com/gp/product/B006W494ZA/ref=oh_details_o01_s00_i01 ) but only when doing intensive things (downloading large apps, watching a large mkv, etc)
I think it has to do with the wifi being on the same bus as the usb. I may try a USB network adaptor to see if it calms down.
Also, WiFi under Finless 1.7 works fine (as good if not better than stock)
After I "locked" the CPU to 1200 min / 1272 max with CPU control lite, it is a LOT smoother.
I will try to remember to post links to all the files I used when I get home tonight.
Everything else I have tried works great:
Bard's Tale (low res, due to storage space)
XBMC (still trying to get NFS working with my Windows Home Server)
MX Player
"Contemporary Adult Film collection, through browser/flash"
Thank you for the info. I will try it this weekend. Not sure why finless said wifi would break but its good to hear it doesn't
SirVilhelm said:
Thank you for the info. I will try it this weekend. Not sure why finless said wifi would break but its good to hear it doesn't
Click to expand...
Click to collapse
OK, in the process of uploading the files I used to drop-box right now. As the 3 files are a total of 600Meg, it is going to take at least 80 minutes with my sh*tty TWC/RR upload speed.
In the folder will be 3 files.
Rikomagic MK802III.rar -> Newest stock firmware (Dec 12-ish, I believe) Only if you need it for recovery or to revert to.
RKM MK802 III Recovery.zip -> this is where, after extracting, I ended up getting the right driver, see below.
ug802_2dark_finless_rom17.zip -> Finless ROM -> uploaded with his permission, per this post:
I expect this to be overwhelmed by downloads and CUT OFF by Google!....
So users that got it PLEASE post mirrors for others!
Original topic over on freaktab dot com, giving permission to mirror.
Click to expand...
Click to collapse
Hopefully, obviously, extract all of these to there own individual folders on your HDD.
All copyright/credit/etc., belongs to the original creators. All files freely available elsewhere, I just co-located them for ease of use.
1. plug USB into PC using A side of cable
2. plug hdmi of mk802iii into TV
3. plug micro-b side of cable into mk802III into power port of device
4 after device boots, goto settings -> USB, click connect to computer. ( at this time, computer should start finding the device as a removable drive, and assign it 2 drive letters, I believe) This is where you may need the drivers from file 2 above. Go to device manager, and if you have unknown or Rikomagic device with yellow exclamation, do a driver update, and point to the folder inside the Recovery.zip called Rockusbdriver. Windows should then find the driver, and rename the device to RK30usb (or something close to that)
5. After computer finds device and loads driver, use Rom Flash Tool (Finless) to flash ROM.
Caveat* I was unable to get Finless' tool to set the flash mode (it found the device, but would not reset it), so using the RKbatchTool inside the recovery zip, I was able to reset the device into bootloader mode. (the tool comes up in chinese at first, press bottom left button, select second option, for English) The flash tool inside the ROM found the device and I was able to flash. I did select the 720p config and the 2Gig parameter files for my device.
I hope the above helps somebody, I haven't typed that much in I don't know how long. Hopefully not a TL;DR
I will post when files finish uploading.
Files have finished uploading...see original book post for link......
Thank you for the writeup! For the life of me I cannot get the driver to install. I've tried multiple computers but everytime windows comes up saying it cannot find a driver for the device. Maybe I need to update the firmware first?
I am on
MK802III_ANDROID_4.1.1-SDK-v1.00.1015
Kernel Version:
3.0.8+
[email protected]#110
SMP PREEMPT Thu Nov 29 09:45:17 CST 2012
---------- Post added at 11:36 AM ---------- Previous post was at 11:15 AM ----------
That didn't work. Not sure why I can't get drivers installed but this is frustrating!
Ok, had a hell of a time getting the drivers to work! Basically what I had to do was install SuperSU, Busybox (probably not needed) and a console program. Using the console program I typed:
su (which prompted me to accept)
reboot bootloader
This rebooted the device into bootloader mode. At this point I had no visuals on the TV but my computer saw two unknown devices. I was able to install the driver to one of the unknown devices successfully. At this point the rom flashing tool recognized the device and I was able to flash the rom.
Two questions about the finless rom 1.7
What are the two boot img options for? I flash the default 720 image even though I am using a 1080p kernel, does that matter?
I believe our devices have more ram than the UG802, are we loosing space by running this rom?
SirVilhelm said:
Thank you for the info. I will try it this weekend. Not sure why finless said wifi would break but its good to hear it doesn't
Click to expand...
Click to collapse
If it is the thread I am thinking about, and I can't find it for the life of me, finless was saying the ROM for the UG808 would break wifi because it used a different chipset.
SirVilhelm said:
su (which prompted me to accept)
reboot bootloader
Click to expand...
Click to collapse
Yes, su then reboot bootloader is much easier to get into flash mode.
For those on the stock 11/29/2012 ROM it is already rooted so you can use a terminal program. Just download a terminal program from the Play store.
While the MK802 III is hooked to your PC, open the terminal program you downloaded from the play store and type "su" without the quotes, at the next command prompt type "reboot bootloader" (without quotes) and it will reboot into flash mode, (TV will be black-nothing on screen) Windows will then find unrecognized device. The drivers are included with the finless v1.7 rom in the drivers folder. Both x86 and x64 drivers are there. Just navigate to the appropriate folder then sub-folder of which OS is on your computer.
SirVilhelm said:
Two questions about the finless rom 1.7
What are the two boot img options for? I flash the default 720 image even though I am using a 1080p kernel, does that matter?
I believe our devices have more ram than the UG802, are we loosing space by running this rom?
Click to expand...
Click to collapse
Per the readme file:
If you select a 720 boot.img and a 1080 kernel, your boot screen will not be right. It wont hurt you and the ROM will work but for a good looking boot, you need to select a boot.img that goes with the kernel resolution you select.
There are 2 boot.img's boot720.img and boot1080.img. Of course select the right resolution boot for the kernel you choose!
By DEFAULT, the flash tool is set for 720 boot.
Kernels:
2dark4u has provided 5 extra kernels. So there are 6 in the kit. This is what they are:
720 resolution kernels that should work on any ug802:
-kernel.img = Stock latest JellyBean kernel at 720. This is default choice in the flash tool!
-kernel_720_CPU1272_GPU466_RAM1120.img = Overclocked [email protected], [email protected], [email protected] - N0 heatsink required!
-kernel_720_CPU1608_GPU466_RAM1120.img = Overclocked [email protected], [email protected], [email protected] - WARNING!!! heatsink required!!!!!
1080 resolution kernels that should work on any ug802:
kernel_1080_CPU1272_GPU466_RAM1120.img = Overclocked [email protected], [email protected], [email protected] - N0 heatsink required!
kernel_1080_CPU1608_GPU466_RAM1120.img = Overclocked [email protected], [email protected], [email protected] - WARNING!!! heatsink required!!!!!
Hope that helps your decision making......
Hello,
I've purchased this one: http://www.dx.com/p/x96-tv-box-andr...-2gb-ram-16gb-rom-us-plug-449347#.WPuxONryuUk
Just wondering what ROMs and recoveries work. I've searched a bunch and found some dead links and conflicting information so I'm hesitant to flash it especially where I do not have a stock image to go back to if it renders it bricked.
If anyone can help out, it would be much appreciated.
Thank you,
Scott
Note: Keeping a repository here as I find more information about this box: https://drive.google.com/open?id=0Bzj6JjnAJZjjczVIbFlHS3VUWlU
Working on it
Custom TWRP and stripped down/modded firmware is on the way.
I hope we can get a pure Android Rom working on it
Again: Working on it
Fully unbranded and hopefully with unlocked custom bootanimation (Original Google would be my prefered option over Mbox).
Give me a bit of time and you will find flashable ZIP soon
All done
Another question about the box: is-it possible to have Android TV instead of a modded android marshmallow? Because the interface would be a lot easier to use.
Android TV is a complete different story and you can't really compare the two like this.
Android TV uses the Leanback launcher if I am not mistaken.
Already tried to include it into a testrom but so far no real luck as it uses a lot more binaries that are not included in the standard system.
Will have to create some symlinks, add binaries and do a lot of testing - not to mention finding all the included apps for android TV and figuring out how to make them work.
If the interface is your only trouble check some nice launchers first, like Apex for example.
Once I have something cooked up that actually works as expected you will find it in this section somewhere
Also interesting to test that , as mine is not even root ^^
Rom
Any news about the firmware for this device?
Nope, still no updates coming from the chinamen, seems they already abandoned firmware updates and moved on to different devices.
See this thread (beta 6 I used for.mine)
https://forum.xda-developers.com/an...gic/rom-x96-2-16gb-root-supersu-twrp-t3596525
I join the thread because because of a storm my X96 looks brick. I've been looking everywhere but I do not find the guide for unbrick. I wanted to save it not to throw it but I do not know where to download the firmware how to do unbrick. I know I'm in the wrong thread but I did not want to open it a lot like this and make it confusing. Thank you all
As long as you get into the TWRP recovery on the SD card all should be fine - assuming the box is a X96.
If that fails only the burn tool or burn card maker can help with a genuine firmware to get going again.
Hi guys sorry to bump an old thread. I'm still trying to find the TWRP zip for these so I can do a complete back up and then paste on other boxes.
Have an X96 Amlogic S905X Quad Core 2G/16G Android 6.0 Wifi HD 4K TV Box.
I flashed the FULLY UNBRANDED Kodi 17, everything looked fine but the box's red light just stays on after the reboot.
Does not go into TWRP at all or nothing on screen.
It now a paperweight?
Downloaded the Stock firmware (Android 6.0.1 X96 Amlogic S905x 20161122) and am trying to start box with a bootable SD-card.
BurnCardMaker asks for an IMG file with all the relevant (aml_autoscript, factory_update_param.aml, firmware.zip, recovery.img, u-boot.bin, etc) files in but i cannot find this IMG file.
Without these BurnCardMaker does not work at all or nothing happens on TV box at least.
Must also say, i use a 64gig SD card but it worked for the initial flash.
Am i wasting my time with this box now?
Thanks for help.
I managed to create a fully unbranded firmware for the X96 that also allows to use custom bootanimations.
Since the hardware of a lot of S905X boxes is literally identical this should work on other boxes as well !?
Mine has 2/16GB but it should be possible to remove some things for 1/8GB models.
I tried a lot of firmwares from other boxes on mine with various success rates (did not modifiy anything in the firmwares).
AFAIK all it takes is a custom recovery for the box in question and that problem should be quite easy to fix anyway.
Has anyone done firmwares that work on multiple boxes?
Would anyone be willing to de-brand their box?
Could not let it rest, so I started playing with TWRP 3.1 in the meantime.
Although I manage to get all partition included, so a few more than with TWRP 3.0, it seems to be impossible to mount the external SD for any good use.
Backups and restores work from internal or USB only
TWRP 3.0 does not backup the logo, bootloader and /tee or the original recovery for that matter.
IMHO that means without the means to flash a genuine firmware in case something goes wrong I am stuck now.
Not 100% certain how important a backup of the other stuff would be these days but I would prefer to offer the option of a full nand backup instead of just system, data, cache and boot.
Still, the mods to the firmware are basically completed and it should work on most if not all S905X boxes with the same hardware.
Working on including more WiFI drivers though.
Very interesting I got a T95X that I wanted to use a "netflix machine" and the android version is atrocious.
The only thing about is that it uses a wifi chipset (9082xs) that it seems there is no sources yet.
Are you progressing?
Progress is relative here...
Several S905 boxes are conform to the same standard in terms of partition layout and hidden partitions, while other manufacturers brew their own.
One thing that would need fixing is a routine to check what WiFi chipset is used and activate the corresponding drivers, or one would need to flash this after the actual firmware.
The other thing, as said, is the partitions.
Could make sense to actually collect and list the data of the various boxes out there to join what can be joined.
This way we should be able to do with just 3 or 4 firmwares to suit all.
Downunder35m said:
Progress is relative here...
Several S905 boxes are conform to the same standard in terms of partition layout and hidden partitions, while other manufacturers brew their own.
One thing that would need fixing is a routine to check what WiFi chipset is used and activate the corresponding drivers, or one would need to flash this after the actual firmware.
The other thing, as said, is the partitions.
Could make sense to actually collect and list the data of the various boxes out there to join what can be joined.
This way we should be able to do with just 3 or 4 firmwares to suit all.
Click to expand...
Click to collapse
OK, so let me know if I can help you.
You can take the WiFi folder from your firmware and replace the one in a suitable firmware to get it working on your box.
If rooted and the bootloader is unlocked you might even be able to just install the Open GAPPS TV package.
Just because it always fails on my box might not mean it fails on all boxes.
I am starting to think a "universal" firmware is only possible by creating a system partition that is happy with whatever kernel and startup routines are present on a device.
But even then there are still problems depending on how the security and additional security features are implemented in the kernel.
Not to mention managing partitions that are not available on all devices.
s905x
sorry for the presumptiousness but i dont know where else to turn. my m9c pro 4k 1/8gb box which has the marshmallow OS has stopped working. i had formatted my sdcard as internal memory forgot took the card out and gave it away now when it boots it continuosly shows the mbox boot screen runs my iptv in the back ground i can change channels up/down but cant see any thing because the mbox boot screen is still there.can you help me to recover using an sd card, please. i had a stroke so my memory is bad. thanks. also need link to the files. this box has a reset button underneath but it apparently only works when it has a bootable sdcard in it.
Downunder35m said:
I managed to create a fully unbranded firmware for the X96 that also allows to use custom bootanimations.
Since the hardware of a lot of S905X boxes is literally identical this should work on other boxes as well !?
Mine has 2/16GB but it should be possible to remove some things for 1/8GB models.
I tried a lot of firmwares from other boxes on mine with various success rates (did not modifiy anything in the firmwares).
AFAIK all it takes is a custom recovery for the box in question and that problem should be quite easy to fix anyway.
Has anyone done firmwares that work on multiple boxes?
Would anyone be willing to de-brand their box?
Click to expand...
Click to collapse
will your fully unbranded firmware work with T3X Mini............if yes will you like to share please
I recently purchased an MX10 Android TV Box running Android 7.1.2
It is supposed to be rooted and SuperSU came installed but when you run it, it reports that the SuperSU binary is not installed and SuperSU cannot install it. I've done a full factory reset but the image comes back broken like that.
I downloaded updated firmware for this box and the SuperSU zip file but I cannot get this box into recovery mode. Everything I've found says to stick a toothpick in the AV hole and power up the box. When I do that, the MX10 logo shows but then it pops up with "erasing" and then reboots. All that does is a full factory reset.
If I run Root Checker, it says I don't have root.
Anyone have any experience with this issue and this box? If I can't get into recovery mode then I can't fix SuperSU and/or update the firmware to one where I'm rooted.
The box otherwise seems to work ok with the exception that I cannot set a live wallpaper. I'm just not rooted.
Thanks for any help!
-TimG
TimothyGaray said:
I recently purchased an MX10 Android TV Box running Android 7.1.2
It is supposed to be rooted and SuperSU came installed but when you run it, it reports that the SuperSU binary is not installed and SuperSU cannot install it. I've done a full factory reset but the image comes back broken like that.
I downloaded updated firmware for this box and the SuperSU zip file but I cannot get this box into recovery mode. Everything I've found says to stick a toothpick in the AV hole and power up the box. When I do that, the MX10 logo shows but then it pops up with "erasing" and then reboots. All that does is a full factory reset.
If I run Root Checker, it says I don't have root.
Anyone have any experience with this issue and this box? If I can't get into recovery mode then I can't fix SuperSU and/or update the firmware to one where I'm rooted.
The box otherwise seems to work ok with the exception that I cannot set a live wallpaper. I'm just not rooted.
Thanks for any help!
-TimG
Click to expand...
Click to collapse
Yeah i just got mine yesterday and im having the same issue. I get a Root user account error with Root Checker Pro. Ive tried clearing data in the SU app but nothing. There is an update for SU in the Play Store but i read on Freaktab where someone said not to update SU app or it will give you a bootloop. I havent updated it yet cuz i wanted to do some more investigating but i really dont see the harm in just updating the app itself. I know updating the su binary will result in a bootloop because i updated the binary on my T95Z and got the bootloop. Ive been googling all day trying to find a TWRP.img file for the MX10 but have found nothing yet. Ive also been looking for a root method for this box as well but not sure what i should use. It would be nice if these each box had it own sub forum like the phones have.. would make life so much easier. lol
If you figure anything out i would appreciate if you would pass that info on.. will do likewise.
htxp://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/freaktabs-tools-utility-collection/656634-twrp-recovery-for-rockchip-devices
I'm in the same boat. Recieved my mx10 a week ago. Tried the tooth pick in the av port. Shows on screen 'erasing' and eventually factory defaults. No root
Android 7.01 said:
htxp://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/freaktabs-tools-utility-collection/656634-twrp-recovery-for-rockchip-devices
I'm in the same boat. Recieved my mx10 a week ago. Tried the tooth pick in the av port. Shows on screen 'erasing' and eventually factory defaults. No root
Click to expand...
Click to collapse
Have you updated the SU app? Not the su binary but the app from play store itself?
Hi, actually I was looking to root the MX10 but for a simple reason:
all I want to to is to get a shutdown or power off button, but this seems missing on the MX10 .. !!! First time I see a box without the shutdown option.
I looked up for apps providing power off button but they all require root access and so don’t work on the out-of-the-box MX10.
Anyone has same need and a solution?
Hi, I received my MX10, a few days ago and have the same problem (SuperSU issue).
I purchased it from GeekBuying, and posted on their blog, for the latest firmware update I could find: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
Really want to root it, so I can edit the keyboard/remote control files to map keys on the H18+ remote I bought at the same time as the MX10.
I haven't tried flashing different firmware (or booting into recovery). If/when I receive a reply to my post on the GeekBuying blog, I'll post here - but no idea if they'll reply.
supergiulio said:
Hi, actually I was looking to root the MX10 but for a simple reason:
all I want to to is to get a shutdown or power off button, but this seems missing on the MX10 .. !!! First time I see a box without the shutdown option.
I looked up for apps providing power off button but they all require root access and so don’t work on the out-of-the-box MX10.
Anyone has same need and a solution?
Click to expand...
Click to collapse
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
Seems really odd that it would come with Super SU installed, and not be rooted. Then again, it also advertises (on GeekBuying.com - in case anyone purchased elsewhere) that it comes with Kodi pre-installed, and mine didn't.
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
TimothyGaray said:
...I downloaded updated firmware for this box and the SuperSU zip file...-TimG
Click to expand...
Click to collapse
Whereabouts did you get the firmware? Was it this one MX10_RK3328_KODI18.0_20171208.img ? Listed on this GeekBuying blog entry: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
RADiuMOz said:
Seems really odd that it would come with Super SU installed, and not be rooted. Then again, it also advertises (on GeekBuying.com - in case anyone purchased elsewhere) that it comes with Kodi pre-installed, and mine didn't.
---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------
Whereabouts did you get the firmware? Was it this one MX10_RK3328_KODI18.0_20171208.img ? Listed on this GeekBuying blog entry: http://blog.geekbuying.com/2017/12/...r4-32gb-emmc-tv-box-firmware-update-20171214/
Click to expand...
Click to collapse
Yeah i agree.. odd it ships with su installed but no root. Theres some fw's on this page.... ive downloaded just in case i ever need it... dont see why i would since there is no root though. lol
http://freaktab.com/forum/tv-player...3328-4-32gb-tv-box-2-4ghz-wifi-fast-lan/page2
Hi mate,
Try my guide in the Media TV Box Amlogic forum. The recovery image is for TWRP. But you could try Philz or others. Worked on S912 and S905 so far fine.
https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
No root? I suggest you follow backup instructions, take 3 backups - all paritions, boot only, recovery only.
Then you can extract the boot image from your backup and use that with Magisk to root your system. After Magisk modifies your boot image, reboot, and flash the modified package via TWRP bootable (see topic)
If you have anything you wish to contribute, please feel free to post anything you have learnt that you feel will help others.
Cheers mate!
Thanks for the tip
Thanks Freak69! It was so easy ... but still it would be good to root the MX10
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart.
Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im
not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
flipmode_11 said:
Hi mate,
Try my guide in the Media TV Box Amlogic forum. The recovery image is for TWRP. But you could try Philz or others. Worked on S912 and S905 so far fine.
https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
No root? I suggest you follow backup instructions, take 3 backups - all paritions, boot only, recovery only.
Then you can extract the boot image from your backup and use that with Magisk to root your system. After Magisk modifies your boot image, reboot, and flash the modified package via TWRP bootable (see topic)
If you have anything you wish to contribute, please feel free to post anything you have learnt that you feel will help others.
Cheers mate!
Click to expand...
Click to collapse
Hey @flipmode_11 - which TWRP image should we use, please? In your post, you state to, "Download the X96 Media Player TWRP Recovery image...or a different device". As the X96 is S905X (from a quick Google - don't shoot me if I'm wrong!) and the MX10 is RK3328, the TWRP image for the X96 wouldn't work, would it? I took a look at the list of devices and can't find a matching device.
Cheers,
Richard.
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Somethng that REALLY annoys me about the MX10, is that I can't get it to write to my external USB drive (NTFS). It worked just fine - out of the box - on my old MXIII-G, but the MX10 just won't write to it (Total Commander and an FTP server app I usually use in order to access it from my LAN). Is this because of some weird driver, or because of root (permissions... I checked under apps and it has access to storage - but of course it does, because it can read the drive)?
I'm probably not too fussed about rooting this thing, if I can just get external drives working with it.
I did read about Android not supporting NTFS, for write - but my old MXIII-G did, so I'm assuming this should, too. The only other thing I can think of, is that the MXIII-G had something in the firmware for writing to NTFS.
I can't see why there would be external USB drive support, but you can't write to it - I mean, it's a TV box, surely there are some other people out there who copy movies, etc. to an external drive on the box, to watch?
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
RADiuMOz said:
Hey @flipmode_11 - which TWRP image should we use, please? In your post, you state to, "Download the X96 Media Player TWRP Recovery image...or a different device". As the X96 is S905X (from a quick Google - don't shoot me if I'm wrong!) and the MX10 is RK3328, the TWRP image for the X96 wouldn't work, would it? I took a look at the list of devices and can't find a matching device.
Cheers,
Richard.
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Somethng that REALLY annoys me about the MX10, is that I can't get it to write to my external USB drive (NTFS). It worked just fine on my old MXIII-G, but the MX10 just won't write to it (Total Commander and an FTP server app I usually use in order to access it from my LAN). Is this because of some weird driver, or because of root (permissions... I checked under apps and it has access to storage - but of course it does, because it can read the drive)?
I'm probably not too fussed about rooting this thing, if I can just get external drives working with it.
I did read about Android not supporting NTFS, for write - but my old MXIII-G did, so I'm assuming this should, too. The only other thing I can think of, is that the MXIII-G had something in the firmware for writing to NTFS.
I can't see why there would be external USB drive support, but you can't write to it - I mean, it's a TV box, surely there are some other people out there who copy movies, etc. to an external drive on the box, to watch?
Click to expand...
Click to collapse
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
Ok so ive been on Samsung for the last 5-6 years and never had to backup things like boot.img, recovery.img cuz we have have odin, so there was never any need to...... so i just did a google search on how to do this but it only brings up ways to do it with root. Can you explain how to do this or link to a tut?
Also could i get a more in depth of using Magisk? I have it on my HTC M7 but i rarely ever play around with it... actually im root with SU on it. So i have to run Magisk on my MX10.. search for boot.img.. patch it.. flash some zip in twrp.. and how do i get twrp on the box.. through adb? I should know this as long as ive been rooting but root on U.S. snapdragon samsung phones is totally different since the bootloader cant be unlocked. Thanks for your info so far bro
Post redundant.
flipmode_11 said:
Did you see my questions?
Where did you source your device from? Ebay? Online? Retail?
What software and steps above did you try?
Did you try the Paragon app with Total Commander?
Did you try downloading the recovery.img linked in the Media TV Box category? https://forum.xda-developers.com/showthread.php?p=75644464
Using Magisk is even more important these days as developers attempt to detect SU/Root, plus Magisk does not make modifications to your /System partition which makes life MUCH easier upgrading / troubleshooting / debugging and allows you to mask Root/SuperUser to then use all apps (Spotify, Play, Netflix, Stan, et al.)
Click to expand...
Click to collapse
I got my box from Amazon. Ive not tried anything with it yet. I dont use Total Commander.. that was another guy saying something about it and wanting to be able to write to external sd... i could care less for that. I want root for adaway and a few other things. Im using Blockada right now to block ads but i cant use it and Expressvpn at the same time.. so my choices are either block ads or run vpn to be anonymous.. cant do both because you cant run two vpns at the same time in android and blockada's vpn is not the same kind of vpn.
Ok i just read your thread.. i will give it a try sometime this weekend maybe.
Ya know the weird thing is is that DevCheck says i have root and busybox installed. Su app is there but say su binaries arent installed. I dont get why this box is shipped like this. lol
You are funny! I was talking to @RADiuMOz - I had quoted him.
No wonder your reply made no sense. Then my reply made no sense.
Please see my topic on AMLogic devices "AMLogic S905 S912 FAQ ✰ Fix Root, Switch SU, Backup/Restore etc ✩ Media Player TV Box" here: https://forum.xda-developers.com/an...mlogic-s905x-s912x-faq-backup-switch-t3752897
I would suggest you follow the steps to Backup first as it does not make any changes to your system.
Then follow steps to Root (download 3 files) and proceed with the FAQ I have written on how to root and which of the 3 methods suit you (probably the one similar to Part 1 of the backup, plus flashing the ZIP.
I had similar corrupt Root issue where SU and SUD were present, but didn't appear to have permissions. Some apps reported Root OK, and others No Root.
Anyway, let me know how you go. I have documented how to un-root / clean-up and then to re-root your system (i.e. Corrupt Root). Reply there.
Cheers!
p.s. May I suggest you check out AdGuard instead of AdAway? It lets you subscribe to block lists, plus you can set-up DUAL VPN's with it (read their KB/FAQ's). AdGuard's menu's allows you to accomodate both being able to VPN and run adblocking at the same time - ROOT Free. So you can probably ignore everything I have even said! LOL (AdGuard > Left Menu > Settings > Proxy Settings)
VyprVPN is far better and I suggest you try them when they have a promo. You can enable an option to block malicious servers, etc. But no way of managing this and adding adverts. Anyway, I switched and tried various VPN providers and found VyprVPN far better, plus offer a higher level of OpenVPN encryption which is not blocked or detected by 3rd parties called "Chameleon".
freak69ize said:
I got my box from Amazon. I want root for AdAway and a few other things. Im using Blockada right now to block ads but i cant use it and ExpressVPN at the same time.. so my choices are either block ads or run vpn to be anonymous.. cant do both because you cant run two vpns at the same time in android and blockada's vpn is not the same kind of vpn.
Ok i just read your thread.. i will give it a try sometime this weekend maybe.
Ya know the weird thing is is that DevCheck says i have root and busybox installed. Su app is there but say su binaries arent installed. I dont get why this box is shipped like this. lol
Click to expand...
Click to collapse
EXPERIMENT: Has anyone tried an OTG adapter in the USB-C slot for a Galaxy S8? Then connect a small USB drive with a recovery.img only, formatted in FAT32? You could even try placing the recovery.img on your Micro SD inside your phone...? Perhaps while holding down menu + up or menu + down, switch on your phone, and it might read the recovery.img on the external memory and boot into that?
*Anyway*, try the same thing in your MX10 and report back add success. Use a compatible S905 TWRP recovery.img (see my type here with download attached and tested with S905x Devices.
Hmm... So many ideas... so many things I have not tried!
freak69ize said:
Hey bud if you hold the power button down on the remote for about 5 seconds and it will bring the reboot menu up.. it has shut down and restart. Do the same to boot up
Ok.. everyone else that was wondering about root.. looks like this is our answer.. no root.. no TWRP...... for now at least. This box is still fairly new so im not giving up. It took 4-5 months for them to get root for Snapdragon S8 so who knows.. it may come for the MX10 one day too
View attachment 4436137
Click to expand...
Click to collapse
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
First up - sorry mate - I actually thought I'd replied to your post, but clearly either didn't submit it, or just dreamed the whole thing.
I have to wait for free time at the weekends (I have kids), but I'll go back to your topic and give that a go.
As for NTFS, etc. I ended up buying a Synology DS218J NAS box as I want my daughter to be able to back up her MacBook to it, as well as probably back up some of my stuff to it as well - and of course then use for the MX10. I bought it from GeekBuying, and they're not that particularly helpful. Not intentionally unhelpful, though.
My MXIII-G was great for just working straight out of the box, with the external NTFS drive (exact same drive).
So now, as for rooting, my only reason will be so I can remap some of the keys on my remote - but don't absolutely have to do that. But I'll do backups anyway, so that I'm ready for if/when any firmware updates come out.
I'll certainly know to have a MUCH better look round, before buying my next Android TV box, though - that's for sure. I did a quick search, but didn't find anything on a user level - but also didn't search XDA: just did a regular Google search.
Thanks for your detailed reply, as I know it takes time and thought on your part - it's much appreciated. As soon as I've got something to report, I'll post in the same thread, so other people can perhaps benefit from my findings.
Cheers,
Richard.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
flipmode_11 said:
G'day mate,
Yeah look just give it a try and see how you go. Booting to this recovery.img will not make any modifications. It is simply loading an interface and relevant dependencies for it to run. I read something about how RockChip devices are limited or something. I forget now, but that made me steer clear of them, despite having more regular updates and new hardware. :/ hmmm
No, you won't find a matching device. It is shocking that these mass-manufacturered generic devices aren't also listed. I recommend you give the recovery.img in my topic a stab.
Where did you source you MX10 from? Have you asked them? Although, every single Chinese seller I have come across has zero working knowledge or which models are better, plus have 101 mistakes in their specs (just got a $50 and $100 refund on Ebay for X96 and a 10.1" tablet! Wrong specs!).
NTFS? So it can READ but not WRITE? Hmm I would wipe everything in FAT32 for Android. Everything is much happier. You could try exFAT which is a superior file system. Have you tried this? Got any other ExFAT + FAT32 devices? Hmm actually I think I've been down that path with exFAT (Paragon tools to solve). Double check exFAT compatibility before proceeding with backup/wipe/re-format. Actually I know the Nexus 6 was able to read NTFS storage as helped a mate with one. But depends on the manufacturer! But the Nexus6 couldn't write to HPFS - never tested exFAT. I think there is an app - USB Media Exporter...? USB Media Explorer..? - I forget!?!
As you mentioned Total Commander, you could try it with the Paragon tool plug-in: https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro -or- https://play.google.com/store/apps/details?id=com.paragon.mounter (not tried this, but images looks interesting - free!). I use Solid Explorer + Smart File Manager - never been a fan of TC... There are other methods out there, but they require Root, which will not help you! e.g. ChainFire's StickMount.
No, I think you should proceed. However, as per my topic, take a full backup of 3+ partitions prior to making changes. I had to revert to a backup on 20th as had 2x SED processes going nuts. Titanium backup'd all important stuff. Then rebooted to Micro SD TWRP and did 3 Partitions (leaving int. storage intact). So Rooting is essential. It really is. Plus using Magisk is even more important, as it does not make modifications to /System which makes life much easier upgrading/troubleshooting/debugging et al.
NOTE: I would infact backup all the data on that ext. drive, delete partitions and create 2 FAT32/EXFAT/NTFS for redundancy. I have had too many past issues with partitions getting corrupt on external drives.
1. Backup Boot partition, 2. Extract the backup and find the boot.img, 3. Install Magisk Manager, click Install and select option 2 and browse for the boot.img, 4. Flash updated /MagiskManager/boot.img via TWRP and you are rooted w/ Systemless SU and BusyBox. There is seriously nothing better than having Root and being Play "Certified". You won't look back! Plus you can always re-flash the stock Boot.img and do OTA manufacturer updates, then open Magisk Manager and repeat.
Mac is like that. You can only read NTFS drives, but read / write to stupid HFS/HPFS drives with Mac, unless you install something like Paragon to read NTFS. The same for Windows, can read HFS+ but read/write NTFS.
Every Android device, regardless of OS, is totally different. Different Kernel's, different builds, ...
Good luck and let me know how you go?
Cheers mate!
Click to expand...
Click to collapse
Apologies! I thought I'd replied, here, but clearly didn't submit it, or just dreamed I had. I've replied to your PM, but also for anyone/everyone else's benefit (and in brief), I bought my MX10 from GeekBuying. I just bought a NAS box, so I'm going to use that instead of trying to get NTFS working, although the people at GeekBuying said, "Our factory tests show that the MX10 can read and write ntfs hard drives. So please try again." I'd be interested to hear whether anyone else is able to write to NTFS.
I'm going to go back to your topic, and give that a go - and will then post back here, to let everyone know (hopefully might benefit someone).
Cheers,
Richard.
i have mx10 and it suddenly stuck in start logo when i open,i dont have any idea please help.
i try to factory reset using toothpick and hit the factory reset no command coming out to delete all files and quick return to booth the system.
whwn i try to reboot again stuck in start logo i'll wait for 30 min but still just rounding the startup logo.Please help me...
I bought a MECOOL KM9 android box from the flea market. The Android on it was something custom from some IPTV service provider. On the bottom it says KM9 so I downloaded firmware from here. Using Aml_Burn_Tool the flashing got stuck at 30%, left it for about two hours didn't budge. After this the computer does not recognize the device (no plug-in sound, tested on two computers) and there is no output on HDMI.
So, I got to method two, which is the SD card burned with Burn Card Maker (multiple versions). Tested several firmware, several SD cards, no luck.
Opened up the device to get the serial output, you can find the output attached. Taking a closer look at the board I saw that is marked as: KM1 X2 DDR3 v1.4. The pcb doesn't look like the KM1's pcb and the SoC is different too. My board has Amlogic S905X2, the KM1 has Amlogic S905X3. Also, the pcb doesn't look like the KM9 board either.
The output log is the same regardless having an SD card or pressing de recovery button. It stops with "sdio read data fail". I don't think the EMMC is broken, earlier in the log it says "Load FIP HDR from eMMC" and there is no error. Also, if I have a bootable SD, shouldn't the EMMC be skipped?
As a last resort I tried shorting pins on the NAND chip, the computer still wouldn't detect it however if i short pins the serial output changes, again file attached.
Any ideas? Can I bring it back to life? At least does anyone have this board and firmware for it?
Thank you,
Alex
fyrewurx said:
I bought a MECOOL KM9 android box from the flea market. The Android on it was something custom from some IPTV service provider.
Click to expand...
Click to collapse
In which country? Do you have the provider information? That information might help identify or locate the original build of the firmware.
fyrewurx said:
Opened up the device to get the serial output, you can find the output attached. Taking a closer look at the board I saw that is marked as: KM1 X2 DDR3 v1.4.
Click to expand...
Click to collapse
It's too late now, but it would have been best to connect the uart and dump the original firmware before flashing anything. I understand that the label on the cover is wrong and that it does not match the board, but if you had a backup you could start over. Now, the drm keys (if any) are probably gone and the wrong dtb seems to have been flashed. Maybe it still can be fixed since the bootloader does still boot somewhat, but that may not be the original bootloader but rather the one that was flashed before the flashing failed.
fyrewurx said:
Also, if I have a bootable SD, shouldn't the EMMC be skipped?
Click to expand...
Click to collapse
There are different types of SD booting. For the lowest level booting, the emmc is skipped only if no bootable bootloader is found on the emmc.
It also will be skipped if the emmc clk resistor is removed. 4R1 may be the emmc clk resistor. Check if it is zero ohms. If it is not zero ohms, check the other side of the board.
Once the device is always booting from the SD card, try various videostrong (not skyworth!) firmware for S905X2 devices, like the KM3 and others (such as the KM9 Pro, which uses the X2). I don't see any information for this KM1 X2 device. It may be a custom variant for OTT providers.
Thank you very much for taking the time to answer.
All I can remember is that it was something Polish. You are right, having the original firmware would have been great. I usually check how much info there is on the internet (mainly xda) about the device I want to flash. If there is a lot, I don't bother with backup. Miiiistake. I didn't knew about the clk resistor and I assume others either because people don't mention on the internet. They recommend shorting the pins which is not a great idea in my mind. I did it with a random 330 ohm resistor to be on the safer side. I will definitely try to get the box to boot from SD and then try firmware from KM1 to KM whatever they got up to with the X2.
From your experience are these devices picky about the SD card? It would be easier if I test only with one card.
The DRM keys you mentioned, would stop the device from booting or the box just wont play Netflix and other streaming services? Even without Netflix I would like to get the box going.
I will have to lookup what a DTB file is, I have no idea. The board looks to be custom as there is one other picture I found about the device here.
Just for my knowledge, the bootloader for these devices is also in the main EMMC? I am used to x86 where you have an external memory to keep first stages of bootloader.
I attached closeups on the EMMC and the back, maybe we need them further on.
Thanks again for the reply,
Alex
fyrewurx said:
The board looks to be custom as there is one other picture I found about the device here.
Click to expand...
Click to collapse
Based on those photos, there is a chance that your board is (or is compatible with the firmware from) the KM9 PRO or the KM9 PRO DELUXE.
If this is the case, the state that your device is in now is probably a result of trying to flash an android 9 firmware image to a device that had an existing installation of android 10. If so, there is a decent chance that you can fix it.
You may be able to get a uart shell prompt by experimenting with shorting the emmc clk at various times, so that the attempt to load the invalid dtb (from the flashed firmware) fails. If you can get a uart shell prompt, you can start burn mode (uart shell command "update"), and then use command line tools to flash the km9 pro or km9 pro deluxe firmware.
Otherwise, remove the emmc clk resistor (once it is located), and raw copy the bootloader (from km9 pro or km9 pro deluxed) to the sd card. It isn't necessary to put the resistor back when you are done, a jumper wire can be used since it is zero ohms.
Functioner said:
Based on those photos, there is a chance that your board is (or is compatible with the firmware from) the KM9 PRO or the KM9 PRO DELUXE.
Click to expand...
Click to collapse
The KM9 devices use DDR4 memory, my board has DDR3. Can the firmware still be compatible?
I don't know. Maybe if the dtb has support for both types of ram. You'd have to check the dtb.
If you flash the dtb while watching the uart output, you'll know if it will work. But first you'd need to be able to start fastboot or have access to the uart shell, in order to flash it.
Support for both types of ram is not uncommon. For example, the sdmc dv8555 (S905x2) has multiple hardware versions, some with ddr3 and some with lpdd4, and both boards use the same firmware.
The original dtb and bootloader on your device are probably gone. They probably were overwritten before the flashing failed at 30%. You don't have much to lose by trying the other firmware, except perhaps a lot of your time.
I will try for sure. As you sad, there's nothing to loose. I probably shouldn't even bother (it was less then 10 dollars), but I hate contributing to e-waste, specially when the hardware is fine, the issue is software. And it's kinda my fault .