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......
Related
Here's the victim, I believe it's a Wopad V7+ ..
7" /Capacitive 5 point Touch Screen/ Android 2.3 / HDMI /
vimicro VC882 ARM Cortex-A8 1GHz
It seems to be AKA: HAIPAD M8 /Zixoon V78c / McPad V7+ /
MOMO 1000 (BUT Resistive touchscreen)
I bought it at dealextreme. sku104916
You can see it at wopadusa.com store
I rooted it , confirmed via rootcheck, modified the build.prop to make it appear as a nexus s. All went good for many days...
I realised a few days ago that my tablet was unable to PERMANENTLY install an apps... or install a new one... Or change internal parameters or flash it(wallpaper won't be different after flashing)
In fact the weirder part is that the change appear as being applied but when it reboot, it returns to the same state (uninstalled apps still appear as installed) . The tablet indicate it's low on disk space , I uninstalled most application I could but it won't go away since the apps still appear as installed after a reboot.
I tried to flash it. The apps to flash it via Win7 confirmed the flash was successful... but I didn't notice any change. I flashed it with Zixoon and wopadusa and it didn't change anything. I tried different apps to flash it including those: chinadigitalcomm.com/flashtool-packtool-for-m8-incl-latest-1028-firmware-v3-0-update-23-11-2011-t11091
I'm not sure when the problem appeared... I believe it's after I followed the following procedure: ClockworkMod Recovery 5.0.2.6 unofficial port v1.0 alpha by mikeNG chinadigitalcomm.com/post23360. .
Because when i tried to enter in recovery mode the screen became ''fuzzy'' unreadable... but I confirm i was able to select the menu at that moment. Maybe i did something wrong. And I dont' know how to undo the change.
I believe it may be related to read/write/chown permission via adb... I dont' know.
I may have to correct via adb shell chmod ?SOMETHING? /system / at different place of the filesystem but I don't know what and where to look for...
I'm not very teck savvy. But I have good will. Please help me.
I don't want to send the tablet back to china. I use it to study. I really like android.
BONUS: By any chance, can someone tell me where to buy the power adapter for that tablet ? It doesn't recharge via USB and my actual charger have a shortcut and this adapter have a very RARE tiny pin connector, slightly larger than some nokia. it's 5v 2amps.
English isn't my first language but I believe I amde myself understandable. I'll clarify anything i'm able to.
Thanks.
I can't post outside links in my message as per forum rules. After approximately eight posts, I'll be able to post outside links. Thanks for understanding!
I recently acquired an Asus EeePC (900 model) for practically nothing, and was frustrated by how slow WinXP ran on it (even after a fresh install). Being that it only has a 16GB SSD hard drive and I don't fully plan on dumping money into upgrading it, I figured it was ripe for some Android goodness. So, I've tried 3 different versions available at android-x86.org (2.2 R2, 3.2 RC2, 4.0 RC1). Each has their own pros and cons, but I've decided to stick with Froyo, as it seems to be the thoroughly most stable of the bunch.
Overall, I'm pretty happy with the whole thing. Boot-up times are lightning quick, and most things seem to work fast enough, but there is the issue of APK compatibility. I understand that the architecture between x86 and ARM processors lends to a lot of apps simply not working. I was hoping to use Google Voice and Groove IP to be able to make phone calls using my home's WiFi network. I have no problem establishing a strong connection (both through WiFi and Ethernet), and Google Voice installs and syncs to my account with no problem, but I can not get Groove IP to install. My grasp of it is that until Groove's makers build the program to work on x86 architecture, I'm out of luck.
That's all well and good, but are there any other options I can look into? Search terms I come up with are vague at best and generally lead to dead ends. It isn't a deal-breaker for me either way, it just seems like a decent use for this little netbook.
Could you tell me how did you boot android from usb\/ cause i think that u did it using usb not sd card. Cause i have eeepc 1202nl and i cant boot android 4.0 rc1. Did you change sth in cd image files?
I pretty much just followed the install instructions HERE.
I used UNetbootin to make a bootable USB stick. Since I posted this thread, I have since switched to the 4.0.1 version for the EeePC. As long as you have a decent WiFi connections, it runs amazingly. The nice thing about going the UNetbootin method, is that you can boot from the USB and run it like a "LiveCD" version without altering anything on your hard drive, or go through the business of formatting and doing a clean install.
Basically, just download the version of Android x86 you need from the website, download UNetbootin, and when they are done, put the USB drive in the computer you downloaded the ISO and program to.
On UNetbootin, here's how you do it.
1. Click on the bubble about 3/4 of the way down where it says "Disk Image"
2. If it doesn't say so already, select "ISO" from the drop-down menu.
3. Select the Android ISO you want.
4. On the very bottom, make VERY SURE it says "USB Drive" for Type and that you select the correct Drive Letter for your USB drive.
5. Press OK, let it do its thing. When it is finished, Click the button to Exit, then properly unmount and remove your USB drive.
With your netbook turned off, plug in the USB stick. When the BIOS screen comes up, press the ESC key on the keyboard to bring up the boot menu. From there, choose a "Live" installation to test it out and run it from the USB stick, or choose to install it on a partition of the hard drive.
One last bit of advice, if you do elect to do a full installation, it isn't a bad idea to partition your hard drive. The maximum amount of memory Android-x86 will recognize is 2GB (1GB as "onboard memory" and 1GB as a dummy SD card). If you did a 3GB partition on your hard drive, it will be plenty of space for the full install of Android-x86 with the maximum amount of memory, and you'll still have the bulk of the hard drive left for a Windows, Linux, etc installation.
So today I have enough time to try run android on my asus and i cant do it. As i know u are the only one person with android x86 on asus I have one ask:
1. unebootin is booting and i can choose option to run/install android
2. than i got "detecting android-x86....", "found at /dev/sdb1"
3. than change resolution and "A N D R O I D [email protected]:/ # _"
4. after that i got sth like this (sry cause i did it in paint, but i cant make screenshot/good photo):
{
"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"
}
(it's black screen with 5-6 white dots in right up corner) - it is staying until i dont turn off netbook
I think its cause that my asus has Nvidia ION graphic and i cant run android on it
But i thought that maybe u have similar problem and can help me...
Or some1 other has any idea?
Try a different VoIP client?
I tried Froyo again and it is working! But i dont know why other dont work (
IAmAN00bie said:
Try a different VoIP client?
Click to expand...
Click to collapse
What its mean? Maybe any tutorial - if exist?
I'm noob in linux (i know sth about android but only about phone versions).
EDIT: is there any possibility to root it? I dont want recovery, but SU and RootExplorer is what i want
Glad you got it working. The installs seem to be a little weird. I had to wipe and install 3 times before I got a fully functional ICS install on my roommate's EeePC.
As for root, you should have it. My ICS install came bundled with Superuser. The only issue I'm having is adding apps to the accepted list.
Card83 said:
Glad you got it working. The installs seem to be a little weird. I had to wipe and install 3 times before I got a fully functional ICS install on my roommate's EeePC.
Click to expand...
Click to collapse
After installing i got the same - Froyo is running perfectly, other not boot (even after 10 installs). I still have the same problem with black screen and dots. I ask on android-x86 site about this, maybe they know sth.
Card83 said:
As for root, you should have it. My ICS install came bundled with Superuser. The only issue I'm having is adding apps to the accepted list.
Click to expand...
Click to collapse
On Froyo i dont see any superuser.apk. Maybe its only on ICS (and GB or Honeycomb).
Hi its me again. I want to ask about one thing: have/had u problems with wifi connecting? Cause i cant connect to my router - i get remember but i cant connect.
Sent using r800i with DoomKernel v11 (1.21ghz)
ch3mn3y said:
Hi its me again. I want to ask about one thing: have/had u problems with wifi connecting? Cause i cant connect to my router - i get remember but i cant connect.
Click to expand...
Click to collapse
As far as getting an internet connection...
On Froyo, I am able to establish a connection with both WiFi and a wired ethernet connection.
On ICS, I can get a good WiFi connection, but no wired ethernet connection.
However, I put ICS on my roommate's EeePC with the standard HDD instead of the SSD that mine has and he was unable to connect to the WiFi. I'm not 100% sure why that was the case. I think his is a 700-series EeePC while mine is a 900-series.
Hi
I'm new to running android on my netbook but not new to android, and I was wondering whether there's an easy way to change the resolution?
Idk what the default resolution it uses but my HP Mini runs on the standard 1024x600.. this was the only fault I could find with running android x86
I changed the ppi using root explorer but no matter what change I make, on rebooting, the launcher FC's and I pretty much can't do anything else, so I have to reinstall the whole thing
Does anyone know how to change the res? Right now, it's probably something like 800 x 480 or something
Is there no official x86 port of Android? I thought I read about it somewhere... but can't find anything, so I'm probably mistaken. On the other hand though Intel has already released Android devices which run on their x86 processors. Are they not bound by the GPL (of Linux) to release the sourcecode? I am quite confused...
Unrelashade said:
Is there no official x86 port of Android? I thought I read about it somewhere... but can't find anything, so I'm probably mistaken. On the other hand though Intel has already released Android devices which run on their x86 processors. Are they not bound by the GPL (of Linux) to release the sourcecode? I am quite confused...
Click to expand...
Click to collapse
Currently, there is not an official x86 port.
Will there ever be? Probably.
When? I have no idea.
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
This is a guide to install Debian Linux on your Nexus Player
NOTE: This guide is for advanced users
This is NOT VNC nor chroot nor Android X server nor anything else like that, but running Linux natively.
D I S C L A I M E R
----------------------------------------------------------------------------
Use this at your OWN RISK. Experimental software may harm you, your device and others around you. I cannot be held responsible for any damage done. You have been warned!
Installing Linux will most likely VOID YOUR WARRANTY! (If warranty still applies to a five year old device...)
P R O L O G U E
----------------------------------------------------------------------------
I have adapted the Nexus Player's kernel to meet GNU/Linux, namely Debian 10, requirements so far that it has become quite stable by now.
Since the processor is Intel x86 compliant you can run a regular distribution, receive updates, load software, etc. etc. This makes the Dell Venue virtually a desktop PC.
You can install Debian onto a USB stick and dual boot along with Android OR you may install Debian to the device's internal storage (and speed up things significantly).
H A R D W A R E S U P P O R T
----------------------------------------------------------------------------
What is NOT working:
* Suspend/standby
* Full 3D support
* Cameras
* Microphones (needs proper asound.conf)
* Likely something else
* Dell Venue 7840 users please see notes attached about sound. Be careful not to damage your speakers with high volumes.
R E Q U I R E M E N T S
----------------------------------------------------------------------------
* Dell Venue 7840 or Dell Venue 7040 (obviously) w/ unlocked bootloader
* USB OTG cable and mirco USB cable
* A USB Hub
* An empty USB stick (I suggest at least 16 GB of storage and 40 MB/s read and 20 MB/s write speed. 8 GB is the minimum requirement though.)
* Input devices (i.e. mouse, keyboard)
* Linux PC (or virtual machine)
* Basic Linux/ROM tinkering knowledge, some time and patience...
A lot of stuff has not been tested entirely, I am a little short of spare time lately, so please be patient, I am willing to help as good as I can.
Ready?! Let's go!
S T E P 1: Install the Linux boot image
----------------------------------------------------------------------------
a) Unlock your tablet's bootloader (there are guides online in case you don't know how to do that)
b) Reboot to bootloader, attach the tablet to your PC and flash the device specific Linux boot image to the boot partition.
fastboot flash boot dell_venue_7x40_linux_boot.img
Hint: This will be the only change to your tablet.
Note: You may revert the changes by flashing the stock boot image.
S T E P 2: Prepare SD card (done on the Linux PC)
----------------------------------------------------------------------------
a) Format the partition on the USB stick with the ext4 file system.
b) Manually mount the partition to e.g. /mnt
c) Download the attached root file system creator, untar it and change to that directory. (sorry had to be a tar inside a zip, XDA forum requirements)
d) Create the rootfs (need to be root):
./bbep_rootfs_creator /mnt your_username your_password
Note: The process sometimes fail, you might have to try more than once.
Note: This will take a long time. To speed things up, you may create the rootfs inside a disk image on your local hard drive and afterwards write the image to the SD card.
e) Download the system image (link: https://mega.nz/file/tK4UiDaB#yfmTgf8qg8e-WKFPfISbKabNeA2vd5cSfTiKCs5Oh2I)
f) Rename the downloaded system image file to system.img and paste it into /mnt
g) Insert the SD card into your tablet.
h) That's it, if you now boot your tablet, it will actually boot into Linux. Please see the debug output messages for hints in case you run into troubles.
Note: The kernel has become quite old. In case the file system gets corruptes, the kernel cannot recover the file system because the current EXT4 version is not entirely supported by the kernel. In that case, please remove the SD card and use another PC with a recent kernel to recover the file system by typing e2fsck -fy
P O S T I N S T A L L A T I O N A N D I S S U E S
----------------------------------------------------------------------------
a) sbin tools
I compiled some tools useful for running Linux on the tablet. Have a look at /usr/local/sbin. Those should be quite self-explainatory.
"toggle_blue_light" is a nifty little feature allowing you to turn on and off the blue pixel (makes the screen a little more easy on the eyes, also eliminates blue light hazard)
b) Keyboard and Dell Venue 7040
Dell has not released the kernel driver for the keyboard, so currently you won't be able to pair the keyboard using Linux. If you happen to own 2 units, you may boot Android on one of the machines and Linux on the other. Trigger the pairing in Android but then connect with the Linux machine. Swap keyboards afterwards. It's a mess...
c) Touchscreen orientation on Dell Venue 7840
Touchscreen orientation on the Dell Venue 7840 might be incorrect. In this case you need to trigger the script /usr/local/sbin/ts_rotate
d) Sound on Dell Venue 7840
Sound on the Dell Venue 7840 needs to be set up manually (you can automate the process with a start up script). You need to call /usr/local/sbin/bb_on_tfa9890.sh as root.
To change the volume use /usr/local/sbin/bb_set_volume.
Be careful with the volume, do not overdrive the speakers. I permanently damaged my 7840's speakers!
e) Compositing
On the tablet, Mate's window manager "Marco" is NOT hw accelerated. Compositing is slow. When watching Videos or browsing the internet, you may want to disable compositing (use mate-tweak) to increase performance.
If you need hw accelerated compositing you may use kwin-x11 but this takes up 1GB of disk space and stability is subpar...
You may reduce the resolution to full HD (still very good picture) by uncommenting the appropriate line in /usr/share/X11/xorg.conf.d/10-hwc.conf
f) Chromium
Chromium can be accelerated with X11/EGL, but buffer management does not work properly. When resizing the window you may need to restart Chromium, because the buffer allocation may fail.
Chromium does have support for WebGL. It's quite buggy.
g) Firefox
Firefox is not hw accelerated but still gives you decent performance when browsing or watching movies (tested Youtube FullHD and Netflix, works fine).
However when using WebGL, Chromium is much faster (in case it does not crash).
h) VLC media player
Video playback hw acceleration is not supported. To achieve decent performance anyways do as follows:
I) Choose Tools --> Preferences --> Video
II) As "Output" choose "X11 video output (XCB)" and for "Fullscreen Video Device" select "hwcomposer" for best performance.
i) Splashscreen
You can create your own splash screen. Just grap the appropriate raw flash file for your device (see below) and append a valid 24 bit image to the file (using your favorite hex editor). Flash afterwards:
fastboot flash splashscreen your_image.img
Q & A
----------------------------------------------------------------------------
Q: Does graphics acceleration work?
A: Well, OpenGL ES does work, however a lot of programs do depend on desktop OpenGL which is NOT supported. Graphics acceleration is achieved through libhybris which makes it possible to use Android graphics drivers in GNU/Linux. It might be very buggy. YMMV
Q: What is graphics performance like?
A: Depends. When a program supports OpenGL ES, you get decent performance (e.g. Kwin-X11 window manager, Chromium). Performance is sufficient to watch FullHD movies in Firefox or with VLC or browse the internet. Chromium supports accelerated WebGL.
Q: What is system performance like?
A: Depends. Bottle neck of system performance is the speed of the storage used. Using the internal storage gives huge speed improvements vs. an external USB storage (max ~ 30 MB/s). With internal storage simple tasks like file management, office applications etc. work fine.
S O U R C E C O D E
----------------------------------------------------------------------------
* Halium - https://github.com/halium
* Libhybris - https://github.com/NotKit/ and https://github.com/libhybris/
* Debian - https://www.debian.org/
* Kernel - https://android.googlesource.com/kernel/x86_64/+/refs/heads/android-x86_64-fugu-3.10-nougat-hwbinder , https://github.com/fcipaq/android_kernel_asus_fugu
* Lineage OS - https://github.com/lineageos
C R E D I T S
----------------------------------------------------------------------------
Special thanks goes to the Halium team, especially JBB and NotKit
And to Hybris, Debian and the LOS team
ROM OS Version: Debian 10
ROM Kernel: Linux 3.10.20
ROM Firmware Required: 5.x
Graphics drivers based On: Lineage OS 14.1
Version Information
Status: 7040 ok, 7840 untested
Created 2021-01-30
Last Updated 2021-02-25
Watch the demo on youtube:
20 days now, believe it or not but I have been waiting for something like that...sort of. Well, I'm gonna give it a try and see if I can provide you with some feedback.
Thanks, amazing idea.
Glad to finally get any feedback
Which device are you using? I have made some progress with the 7040 version - the attachable keyboard now works! I'll update the image file later.
Good luck with the installation and don't hesitate to contact me if you run in any difficulties...
I'm running the 7840. You wouldn't manage to get some kind of an installation script would you?
Well... I'm afraid a script is not possible as it includes to many different platforms...
However I can upload an image of the SD card (I'm currently already working on that) so that you would basically just have to put it onto a SD card.
Linux is running quite well now on the 7840. Even Bluetooth is working without any need of configuration...
So please be patient, may take some days...
fcipaq said:
Well... I'm afraid a script is not possible as it includes to many different platforms...
However I can upload an image of the SD card (I'm currently already working on that) so that you would basically just have to put it onto a SD card.
Linux is running quite well now on the 7840. Even Bluetooth is working without any need of configuration...
So please be patient, may take some days...
Click to expand...
Click to collapse
Amazing to hear that, thanks for your work. Really looking forward to that.
K, you got it! The links to the file system are online now, as well as the new kernels. Let me know how you like it!
PS: The kernel for the Dell Venue 7840 is running with reduced resolution. If you intend to only use the table in portrait mode I can post an boot image running full resolution...
Thank you, I'm currently very busy with exams, I'll look into it the end of this week. Thank you very much for your efforts.
Fingers crossed for your exams!
Also, I've now implemented the ability to set a custom wifi mac and country code using the kernel command line. This can be set by editing the image file with a hex editor (command line is right at the beginning of the file, there is no checksum which has to be recalculated).
Alright, working good so far. Battery drain is pretty high, I assume thats due to the lacking suspension mode. Oh and sound would ofc be nice x). Graphics acceleration would be nice to have and I guess improve battery run time.
Congrats you got it working (first confirmed!)
I find battery performance quite decent when actually running (i.e. using) the system. I get approx 8 hours of uptime, but I agree that standby performance is indeed terrible - as you already stated this is due to the lack of suspend mode. You actually need to shutdown the tablet when not in use.
Graphics acceleration is (I'm quite sure) not going to happen. Linux is lacking a PowerVR open source drivers, many have tried but no success so far afaik.
Sound drivers appear to be tricky. I found at least two pieces of code to be problematic in a 32 bit kernel, but might be working in a 64 bit kernel. However, Intel/Dell seem to do some initializing in user space code which is unavailable. So doesn't look to good for sound...
I installed Linux the the device's internal EMMC (purged Android) which is really boosting performance (internal storage is approx three times the speed compared to the external SD card reader's max speed...)
I tweaked the kernel a litte, it is now possible to choose between full and reduced resolution/color at kernel command line as well as a custom wifi MAC address and country code. I'll upload the updated kernel once I'll return from vacation...
PS: Hope your exams went well!
Awesome! I've been trying to figure out something interesting to do with my 7840. I'll likely have to wait until this weekend to flash it but am looking forward to doing so. Thank you for your work on this.
This is awesome!
I have been waiting for someone to do something exciting with this little guy. Thank you, seriously. I will be flashing this on mine and following along with your progress. This remains my favorite tablet to date (and I have gone through plenty), such a shame dell shut it down and it didn't get too much love from the community.
Well I had some issues with the state of my tablet after the last time I played with it; so things took a little longer to get going than I expected. But I was successful at getting this loaded and so far so good! I am not really seeing any slowness (using a Class 10 U3 mircoSD) but would be interested in the process to purge the Android file system as it would be more convenient at start-up.
I was able to connect to my WiFi using both wireless N and AC standards. In the little bit of testing I have done so far, sound and touch are working quite well. I did notice that the screen rotation script didn't redraw the desktop, but the touch locations seemed to change orientation. I have not yet tried to figure out why.
@fcipaq You have probably already seen libhybris but if not it may be worth looking at for 3D acceleration. I am not completely positive it is relevant as it may be specific to ARM processors. https://github.com/libhybris/libhybris/
It's been a while - sorry! I'm glad to get your feedback. I have been quite busy lately (and still am). I recently made only some minor tweaks/adjustments, e.g. patched to kernel against the blueborne vulnerabilty.
My 7840 is dead now as the connector failed (connected it too many times to my pc) - this is the sacrifice I made But I still have my 7040 up and running - which is basically the same device. I suggest you do a lot of the flashing from the linux command line or buy a magnetic charger cable ($5 on ebay) to reduce wear on the connector - it's quite delicate and really hard to repair (if you find any spare parts at all).
The rotation script is for touch only - this will not alter the screen rotation. The screen rotation (unfortunately) can only be changed by rebooting (or logging our and in again/restarting the X server).
@FairOh: Thank you for the hint. I am aware of that option but it would take quite some engineering effort and that is far beyond what I can do (alone). The current driver does not even give you 2D-acceleration...
I will upload an updated kernel asap as well as I will publish the kernel source so that others may contribute or study...
I benchmarked the internal EMMC and the SD-Card read/write speeds (I used a really fast SD card) and it turns out that the internal storage is about 3-4 times the speed of the external card. I think this is the card reader's limitation.
FYI: If anyone who reads this owns an Asus Zenfone 2 - this is almost the same hardware and a lot of code can directly be ported - I just took a quick glance at the Asus source code... (and to be honest, I took the wifi driver )
No rush, but curious if you have been able to get your source files uploaded/shared. Not that I'm much if a developer, but you gotta start somewhere.
@FairOh: I'm really sorry for my delayed response. I have been very busy lately...
BTW: it was my first project of that kind. I greatly appreciate your interest. Maybe you can figure something out.
Well source code is now online as well as the updated flashable boot images. Feel free to alter the source code in any way, republish, modify, share, learn etc...
I made some remarks inside the archive (readme file) to guide you to a running build quickly. I suggest you use the toolchain (compiler) from google (instructions provided inside the archive), otherwise the code might not compile properly.
Please let me now if you run into any difficulties compiling the code or setting up the build environment...
So far, so good
First of all, I want to thank you so much for your work on this.
I have a 7040 and I was really concerned about Blueborne vulnerability. I tried a few months ago this, but unfortunately I wasn't be able to get working the Bluetooth adapter, so the built-in keyboard/mouse weren't working (Firmware contents were in place, so I didn't really know what happened).
This time, December revision, I run into the same problem and also when I want to update the system, Ubuntu ask me the admin or root user password.
If you don't mind share the admin/root password, I would be very glad to try and fix the Bluetooth adapter in my system and maybe tweaking some system settings.
Finally, I want to thank you again. Our little loved devices can do so much things because of you. Maybe sometime in the future I will be able to dig in the source code and collaborate in these project (First, I have to learn a lot of things, but I think I will).
Glad you like it!
I might have forgotten to mention that the password is simply "password" sorry!
First of all you need to make sure that your bluetooth adapter is working at all (you may try to pair with any bluetooth device). All you basically need to do is to put the firmware files in place.
Connecting to the magnetically attachable keyboard is a whole different story. As Dell has not released the kernel source for the Dell Venue 7040 (but only for the 7840 model) I had to reverse engineer the driver for the keyboard. There are four pins (two inner pins and two outer ones) connecting the keyboard to the tablet. The outer ones are used to supply power whereas the inner ones serve to put the keyboard into pairing mode - using a "secret" protocol which I have not figured out. So here is what I did to get it working anyways:
1. Boot into Android
2. Delete the Dell keyboard from within the bluetooth menu (this will immediately cause Android to try and reconnect)
3. When prompted to enter the pin just click on cancel (the keyboard will remain in pairing mode for another minute awaiting incoming requests)
4. On another Ubuntu PC search for pairable bluetooth devices. Once the Dell keyboard has been detected connected to it.
5. On the Ubuntu PC tar/copy the key files in /var/lib/bluetooth/XX:XX:XX:XX:XX:XX
sudo tar czf btkeys.tar.gz XX:XX:XX:XX:XX:XX
(These are the keys the Ubuntu PC brokered with the keyboard - we are going to reuse these on the Android tablet)
Hint: Both PCs need to have the SAME bluetooth MAC address.
6. Reboot the tablet into Ubuntu and copy the tared file over to /var/lib/bluetooth.
7. Untar this file on the Android tablet in /var/lib/bluetooth
sudo tar xzf btkeys.tar.gz
8. Reboot (The Android tablet now has matching keys to connect to the keyboard).
BEWARE: Booting into Android will result in resetting the keyboard and you will have to do the procedure all over again. You may use electrical tape to disable the two inner pins thus preventing Android from telling the keyboard to go into paring mode)... It's a littel complex... I asked Dell twice to publish the source code but to no avail (did not even receive an answer)
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...