yashsingh1/xdaforums huggingface dataset:
[M.O.J.O. Android Development] TwistyTravster:
First, Gamecube emulation is not possible on the MOJO. It is too much for it to handle. You can feel free to try side-loading Dolphin emulator beta for Android, but I very much doubt it will work. Even if it does, I'd expect the frame rate to be terrible. Dreamcast emulation should work okay using a good emulator from the Play store.

Second, start by deciding what you want for an OS: stock, CyanogenMod 12.1, or Remix?

Third of all, how do you want to flash the new OS? towelroot, or directly with USB?

- towelroot has the benefit that you can install the new OS without even unplugging your MOJO from your TV. But it has risks and limitations, such as, if it doesn't work, then you are forced to use the USB method to fix it.

- USB method requires a USB male to USB male cable. My MOJO included a cable in the box, but some often don't and you need to go out and buy one. This method also requires you to have access to a Windows computer within proximity to a TV so that you can plug your MOJO into your computer with USB, and into your TV with HDMI at the same time.
[M.O.J.O. Android Development] Mojoddz:
Thanks for your help,I'll look over the os and pick one, I picked up a-a usb yesterday but I'll. Try towelroot first. Appreciate the advice, I'll have fun fiddling after I get work out the way this weekend
[M.O.J.O. Android Development] maverixz:
I used the Kingroot 4.8 on one MOJO and the USB method with another. The only problem I ran into with the USB method was that the drivers didn't work on Win 10 so I had to convert one of my laptops to Win 7 to successfully install the driver. I found out all this thanks to some good folks here who helped me when i was stuck with using the USB mode.
[M.O.J.O. Android Development] ConfuciusTse:
Agreed, the driver situation with Android and Win10 makes things difficult. That alone would make me go with a non-USB method first.
[M.O.J.O. Android Development] iperk7181:
How can I scale down the display output on TV

I have installed and have been running remix on mojo for a couple weeks, I changed to a new HDTV and the display is larger than the screen. Cannot find how to adjust via remix as the display size options are not in settings that I can see. My HDTV does not have options as it usually auto adjusts or my android boxes have the ability to adjust manually. Any help would be greatly appreciated.
[M.O.J.O. Android Development] shpitz461:
you could create a nandroid then perform a factory reset and see if the res will fix itself...
[M.O.J.O. Android Development] rkitect:
Thanks [MENTION=4911249]Unjustified Dev[/MENTION] for this beautiful ROM! I flashed it and settled for not having root since the device I use it on is mostly a family use device, playing PBS for Kids, Kodi for Movies and an occasional game for the kiddos. During the initial install and getting apps reinstalled from the play store I noticed it would lock up occasionally, then keep going and be fine. Even more recently these lockups would not unlock needing a hard reset of the device. Now it won't go more than a minute or two without completely locking up and sometimes without even opening any apps.

I switched to Remix from CM12 because CM12 would occasionally reset in the middle of video playback or just random restarts. I'm beginning to wonder if I got one of the lemon MOJO units, but I don't want to rule out something software related. Any thoughts on where to begin purging this demon?

I guess I should include some things I've already tried:

* Root

* Factory Reset

* Reflash of Remix
[M.O.J.O. Android Development] shpitz461:
You could nandroid, the go back to Mojo's original firmware, then see if the problem persists. If not, try remix from scratch. If still issues, maybe try to RMA...
[M.O.J.O. Android Development] rkitect:
Hey, [MENTION=583152]shpitz461[/MENTION], thanks for the reply. Unfortunately things have gone [WAY] downhill since I posted that. I can't even get the device to boot anymore. Stuck at a black screen and can't get a recovery reboot to work with either a USB-USB and fastboot or an external keyboard. I've had the unit for just shy of a year, I don't think an RMA is in the realm of possibility but I could always check.
[M.O.J.O. Android Development] shpitz461:
I see. Sounds like your unit is kapoot :(
[M.O.J.O. Android Development] LM209:
Nice work. Looking good. :good::good:
[M.O.J.O. Android Development] kevinthefixer:
Live Linux CD for Fastboot and ADB

My suggestion is to use a Linux live-CD with fastboot installed, or install a Linux distro on a spare PC. Driver problems simply disappear, presumably because Android is so close to Linux (some consider Android just another flavor of Linux).

Here is an older version of Puppy Linux with fastboot and adb installed:

http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso

I have this installed on an old netbook and use it to flash Droids, including the MOJO. Simply open a console in the folder your flashable .zip is in, and

fastboot -i 0x0738 flash recovery twrp.zip

assuming you want to flash recovery and have renamed your file twrp.zip (I do that to save typing).

Interesting aside: (OK, it's interesting to me anyway): fastboot devices shows nothing with the MOJO, but given the device ID (that's the -i 0x0738) flashing or booting works. Dunno why.
[M.O.J.O. Android Development] ConfuciusTse:
THANKS! That's very helpful. Would you be able to suggest a simple Linux on USB distro (preferably with fastboot and adb also installed)? Or can I just use this package?
[M.O.J.O. Android Development] kevinthefixer:
You can use this package with a utility designed for the purpose such as unetbootin:

https://sourceforge.net/projects/unetbootin/

I've never used it but some have reported it works well. I used Puppy as my daily driver for about a decade, so I just got used to using the tools built into it. But that requires burning a CD and booting a PC to that. I do that regularly as a matter of course anyway so it was no biggie for me.
[M.O.J.O. Android Development] LSDArcade:
To get the driver to work with Windows 10 follow these steps:

Go to Settings/Update & Security/Recovery/Advanced Startup/"Restart Now"

When computer reboots, select 7: Disable driver signature enforcement.

Go to device manager and update drivers for fastboot.

Select Browse my computer for software driver and point it the r3-mojo-superboot-mmm folder.

Done.
[M.O.J.O. Android Development] silverbox750:
Any soloution to enable audio pass through?

Using remix os but still getting only force dts stereo witch is annoying
[M.O.J.O. Android Development] andrzejeq:
I just noticed that automatic time setting does not work on my MOJO with RemixOS. Anyone else experienced this?
[M.O.J.O. Android Development] K-Project:
COMPLETE Android flashing newbie here. :D

Can anyone help, with preferably an idiot's guide to how to do this? I followed Mad Catz guide on their modding site to go root on my new Mojo, and then followed a YT tutorial by MU.TO to install Remix OS, which was completed successfully. I followed these guides to the letter, the OS installed successfully, and I have to say it is extremely impressive. :)

However, it appears I am no longer root despite selecting the option go root before rebooting, and I think I have to be to get some of my apps and games to work properly. Try as I might I cannot get anything to work to gain root, and none of the commands or apps (Kingo Root) recommended seem to work. I'm using Linux, so usually very comfortable installing OS's, but this has me beat! I've had to Mojo connected to an Ubuntu laptop, which got me everything done bar for regaining root so I can begin to have fun.

Like I say, I've read the thread from top to bottom but am stumped. Please help!
[M.O.J.O. Android Development] shpitz461:
Try flashing BETA-SuperSU-v2.66-20160103015024.zip, this should bring your root back.
[M.O.J.O. Android Development] K-Project:
Hi, thanks for replying. How would I go about doing this? I've been returning to my original steps of rooting the Mojo as per the modding pages at Mad Catz, but it gets me nowhere. The OS reboots, but Flashify says no root access and SuperSu says no binary available.

Sorry guys, like I say I'm a complete noob. Can't believe I got this far.
[M.O.J.O. Android Development] shpitz461:
You need to flash TWRP 2.8.2.0, then flash with TWRP the SuperSU zip i mentioned above, that should bring your root back. The key is the custom recovery.
[M.O.J.O. Android Development] K-Project:
Yes I read that earlier in the thread, but it seems I am in a catch 22. I cannot flash TWRP without root, and I can't get root without TWRP. When I attempt to follow the original guide on Mad Catz Modding (sorry, it won't let me link the guide), it doesn't work. Remix still tells me I have no root.

I'm rubbish at this.
[M.O.J.O. Android Development] K-Project:
EDIT: I'm an idiot. Serves me right for copy pasting commands. Try adding

at the beginning of the commands, fool. :silly: And how long have I been using Linux? Yeesh.

Rooted and booted. Thanks for a marvellous OS. No doubt be posting back with more stupid questions soon enough. :)
[M.O.J.O. Android Development] kevinthefixer:
I don't think you're an idiot, but I'm confused. Which procedure were you using, and did you need sudo in the Ubuntu terminal, or in Remix OS' terminal? I'm a Linux user myself but have little experience with Ubuntu. But I would think that if you are having to execute Fastboot or ADB commands as root, you have problems with permissions on the binaries. If you used the tools available here in the XDA MOJO forums, and installed them in your /home folder or a subfolder, you should not need root permissions to execute them. And if sudo worked under RemixOS terminal, you had to have had root already!

Incidentally, if you're an old Linux hand, you'll be right at home in Android. Some consider Android to be just another flavor of Linux, with some justification. Same kernel, same CLI (BASH), much the same folder structure. The main defining difference I've seen is that while Linux will (usually) tolerate different folders installed to different partitions, Android insists on it, thus allowing the /system partition to be mounted read-only under normal conditions and so minimizing the possibility of file corruption there.

Anyway welcome to the club of Android flashaholics anonymous.
[M.O.J.O. Android Development] K-Project:
Thanks for the reply and the welcome. :)

The procedure I was following was to try to regain root again, so I was using the commands from the TWRP recovery thread here. The commands I was using are below:

LINUX - Open a terminal in the root of the r3-mojo-superboot-mmm folder

Code:
chmod +x fastboot-linux
To install the image to device:
Code:
./fastboot-linux -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img
To boot the image:
Code:
./fastboot-linux -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img

I have a dual boot laptop with Windows 7, but using either Ubuntu or W7 it just kept saying "Waiting for device" and would not proceed. Like you, I suspected an issue with permissions on the files contained in the folder but after manually checking this did not appear to be the case. Then, I just thought maybe I need to use sudo, and this had the desired effect.

In doing things this way, is it likely to cause any issues with my install on the Mojo? Should I reflash using a different method? Many thanks. :)
[M.O.J.O. Android Development] K-Project:
Answering my own questions here really. :D Got this little beauty all up and running with everything I need and want it to be able to do. I could not be more thrilled with this set up. This is clearly a very powerful machine, and it clearly needed this OS to bring the best out of it. Thanks so much to the devs and everyone here also who takes time to help others. It can be daunting for a newbie, but with a bit of time (preferably a free weekend!) and patience it is clearly well worth the effort.

I came to this from the Ouya, which is a wonderful console and I have no intention of getting rid of it. But I wanted something that had this type of community creation and future proofing that a company like Razer cannot provide. I'd also tried out the Minix Neo U1, but this couldn't do what I needed it to do, chiefly gaming. The Mojo with Remix however, is now going to become my main box. :) Thanks again.
[M.O.J.O. Android Development] kevinthefixer:
Well I see you already answered your own questions. But no I wouldn't think you'll have any problems, fastboot flashing either works or not, in your case it did. I still have no idea why you needed sudo but it's a trick I'll put in the toolbox. Maybe you couldn't access the folder itself, even though your files had the correct permissions? Or perhaps even the USB buss itself? IDK but if it ain't broke I wouldn't fix it any more.

I was pretty sure I'd end up using Remix OS also, but it turned out that CM12.1 works much better with my oddball display hardware, it has more configuration options. I still ended up editing build.prop to force it to 720p resolution. But you're absolutely right, it's a very capable little box, and will probably end up replacing the ridiculously powerful desktop computer currently serving as a TV tuner in my living room. I really don't need a full-on gaming machine with 32GB RAM to do that! And in case you missed it, there's a bitty little USB TV tuner that works well with the MOJO and it's even cheap! It's the MyGica A681 and there's a thread here for it.
[M.O.J.O. Android Development] K-Project:
Oh my gosh that looks fantastic! May have to partake. :)

Well, I have had a full day playing with this amazing OS, and yep, for me it's more than up to the job. Had a bit of fun configuring Mame4Droid (white text on white background meant finding the external drive with the roms on a hilarious proposition!) but managed to get that sorted too. About the only real issue I am having is with Paragon NTFS. I use an external 2Tb WD drive formatted to NTFS with everything on, and for some reason despite having the option ticked it will not mount the drive automatically at boot. I have to open the Paragon app every time before attempting to use any other app that needs the drive (Kodi for example). I also notice that it says device not mounted even when it clearly is mounted. :confused: But besides that one small thing - awesome!
[M.O.J.O. Android Development] kevinthefixer:
Perhaps if you started Paragon at boot? Otherwise, as long as we can find out exactly what Remix names the drive, we should be able to write a script to mount it. Shouldn't be much different than one you'd use under Linux.
[M.O.J.O. Android Development] K-Project:
Sorry for late reply. Yes, if anyone has an idea how to get the OS to recognise the drive when the MOJO is powered on that would be great. I've set it in the options for Paragon, but it's makes no difference - I have to manually start the Paragon app before SPMC or any of my apps will recognise the drive. Basically I just need the MOJO to work much like the Ouya for the missus; so that she can plug in both the MOJO and the external drive, switch them on and go straight to the apps she needs without having to add a step to mount the drive.

I also notice in the settings for paragon that although I set it for permissive SELinux mode, it appears to reset to enforcing on the next boot. Could this be the issue, and can it be fixed? Thanks guys.
[M.O.J.O. Android Development] kevinthefixer:
This would be easier if I had your system in the same room with me. I think the main problem will be figuring out what the MOJO calls the external drive before it's mounted. If we get really lucky and you went to church on Sunday, it'll be /dev/sdb1, but that seems a bit much to ask for. But try something like this in terminal: (you do have root, yes?)

su

mkdir /data/extdrv

mount -t ntfs -rw /dev/sdb1 /data/extdrv

If this works OOTB then quit screwing around with computers and go find the nearest poker game or lottery retailer, and don't forget to send me 10%! In the much more likely case that it doesn't, write down all the error messages and post back here. Also, with the external drive not mounted, post the output of

ls usb

while you are still root. And maybe try the same command after mounting with Paragon. I know I'm fishing but I need as much info as I can get, my CLI skills are rusty at best. Luck!
[M.O.J.O. Android Development] K-Project:
Yes I have root on the system. :)

Thanks for your reply again. Sorry, work is getting in the way of MOJO fun, so replies are taking ages!

What do I use to enter these commands? Ubuntu with the MOJO plugged in? Paragon reports that the drive is /DEV/BLOCK/SDA1. I'll certainly give the commands a go, I just expected there would be a sort of one-click solution in Paragon or something. Maybe there's a better NTFS app I could try? I don't need write access, just read really as we use it for media files and roms and I plug it into my desktop to add and delete files. Thanks so much for your replies and help. :)
[M.O.J.O. Android Development] kevinthefixer:
Hmmm, I didn't play with RemixOS long enough to remember whether it has Terminal Emulator already installed. But if not, simply install it from Play Store. The usual one is (IIRC) by Jack Pavlovich or a similar name, but really any one will do. It just gives you command-line access to Android, same as the terminal on your Linux system. I find plugging in a physical keyboard a very good idea, YMMV. But that's where you'd type in the commands. I can't imagine trying that with the CTRLR and a virtual keyboard.

So where I put /dev/sdb1, insert /dev/block/sda1. You can leave the -rw off if you prefer. You can change the mount point too if you'd like, maybe to wherever Paragon puts it for consistency's sake. At this point we are just trying to put together a working command, then we'll figure out which system script to add it to. Just make sure you have a current Nandroid!

BTW do you have ES File Explorer? I recommend that too.
[M.O.J.O. Android Development] K-Project:
Wait - there's a terminal emulator for Android? :eek: I had no idea! I'll have a look into that and see how it works. Thanks for letting me know! :)
[M.O.J.O. Android Development] kevinthefixer:
Lots of them. Most if not all are free. Many custom ROMs include one, I couldn't remember if RemixOS did or not. Just search Play Store.
[M.O.J.O. Android Development] K-Project:
Thanks for all your help KTF. Just wanted to post up that I thought I'd try a couple of alternate apps first before going down the root commands route. I tried one called Stickmount, and this actually appears to do what I need. It mounts at boot just fine. You have to select your options at initial run, and then reboot the console, whereupon it will ask again and you can click "don't ask again" and that's you done, if I remember correctly. I've rebooted a few times now and it's working brilliantly. I'll post up if anything changes.
[M.O.J.O. Android Development] kevinthefixer:
If you guys keep solving your own problems I'll never get the CLI practice I need! Seriously, all manner of things is fine, glad it worked out.
[M.O.J.O. Android Development] tcbj:
Try this. Worked for me.

http://en.code-bude.net/2015/08/19/how-to-install-unsigned-drivers-in-windows-10/
[M.O.J.O. Android Development] K-Project:
Don't worry, I'm back with more dumb questions! :laugh:

Seriously, I'm really enjoying the OS, but just a couple of queries - firstly, can Remix be set to 720p rather than full 1080p? I have one of those "HD Ready" sets, a Samsung, that displays the console fine but video playback is a bit jittery. The Ouya was the same and there was never a way to fix it. Is there a setting that can be tweaked on Remix? Also, will there be any updates to the OS, or is this a finished item, and if there are any updates will I need to reflash a fresh install?

Thanks!
[M.O.J.O. Android Development] K-Project:
Also! I installed one or two apps that don't seem to remove the navbar at the bottom, specifically Zen Pinball. I have set the bar to autohide, but Zen still seems to reserve a place for it and has a dark grey bar at the bottom. I checked the settings for Zen but could not find anything relevant.

I know, I know... you thought I'd gone away. :D
[M.O.J.O. Android Development] kevinthefixer:
You would have to take up the update subject with the developer, [MENTION=4911249]Unjustified Dev[/MENTION]. Certainly no automatic updates as it isn't an officially supported version.

AFAIK the only way to force 720P is to edit the build.prop file. I had to do that to my CM12.1 install to work with my hardware, and it worked well for me. But make sure you shoot a Nandroid first and be prepared to restore it if it flops.

http://xdaforums.com/showpost.php?p=65697775&postcount=37

Look and see if you have a "force immersive mode" setting in settings>user interface, see if that does the trick for you. Otherwise, e-mail the app developers.
[M.O.J.O. Android Development] K-Project:
Thanks for your advice. :) I ended up staying with 1080P, as I got my playback of media sorted OK. The trouble I have is that I have a lot of PAL content, which is 50Hz. If you don't address it, you end up with a lot of stutter during playback. I think I've got it fixed now though via Kodi's settings.

A couple of weeks into using the MOJO and Remix, and it is really fantastic. I will certainly donate a couple of drinks to UJD for this. However, I am having an issue when powering the MOJO on. We like to power down our devices and then switch them on when needed rather than leaving them on all the time. But twice now I have had the device switch on to a black screen that does not progress anywhere, leaving me seemingly no option other than to hard reboot. After this things seems OK (once Android has done its checks), but I live in fear of the next occurrence. What could be causing this?
[M.O.J.O. Android Development] kevinthefixer:
The MOJO is very particular about its HDMI output, if it doesn't like your TV/monitor/display/whatever it simply won't put anything out. Make sure your display is completely booted up before you power on the MOJO is all the advice I have.
[M.O.J.O. Android Development] K-Project:
Thanks for that, it's definitely something I'll be keeping an eye on. Can I also ask - I'm not a big fan of hard rebooting devices when things like this happen. With Android and the MOJO, should I be performing a filesystem check after doing this, or is there anything else I should bear in mind? Basically, am I likely to have knackered in the storage?
[M.O.J.O. Android Development] kevinthefixer:
Not likely, no, but anything's possible. This is where keeping a current Nandroid backup (a backup created by TWRP recovery) is critical. We all hope for later, but sooner or later something will go wrong. If you have a good Nandroid you are a few minutes away from back-in-business; either boot the MOJO itself into TWRP, or if that isn't possible, hook up a PC, boot it into fastboot mode, and into TWRP from there. TWRP is an amazing piece of software, it contains filesystem tools, a file manager, a terminal emulator, and of course all the backup/restore tools you need, all in under 8 MB.

But to stop rambling, and get to your question: messing with the filesystem is more likely to cause problems than prevent them. As long as it ain't broke, negative perspiration. An occasional reboot (with a proper shutdown of course) is a good idea, just to get the cobwebs out of the corners of the RAM. Try SimpleRebooter or PowerMenu for this if you haven't already.
[M.O.J.O. Android Development] mrhoque:
I am getting black screen after flashing and reboot. Is there any way I can go back to recovery and flash again? thanks
[M.O.J.O. Android Development] kevinthefixer:
Certainly. Read the TWRP recovery thread and follow the instructions to boot the MOJO to recovery rather than flash/install it.

Check your md5!