yashsingh1/xdaforums huggingface dataset:
[M.O.J.O. Android Development] Fastolfe18:
I've installed remix OS on my MOJO a few days ago, and like you I lost root access.

After hours of research, I found the way to get it back.

- On your MOJO sd card, copy a supersu.zip (I think 2.46 work)

- In a folder of your PC, copy the TWRP file "openrecovery-twrp-2.8.2.0-mojo.img"

- and in a TXT file, write : "fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img" (the name after boot must be the same than your file)

- Rename the TXT file in . bat

- With a male A to male A usb cable, plug the MOJO to your PC and plug power. On the screen of TV you should have "no driver key found... booting os" or something like that

- execute the . bat (I'm on windows). If you are on Windows 8 or newer, you must be desactivate driver signature, otherwise the PC don't detect properly the console. On windows 7 no problem.

- And now, you should be in TWRP. You can unplug the cable, flash supersu. zip and reboot.

If you use twrp 2.8.7.0, remix os don't work, only 2.8.2.0 work.

This work for me, hope this work for you !
[M.O.J.O. Android Development] efestus:
I followed the instructions, created the .txt file that says: "fastboot -i 0x0738-windows.exe boot OpenRecovery-TWRP-2.8.2.0-mojo.img", including the quotes, I called the file "OpenRecovery-TWRP-2.8 .2.0-mojo "and I renamed to .bat, connected to the console, when I launch the .bat file shows the command prompt windows but disappears immediately, I tried to run as administrator but nothing, the window of prompt disappears immediately, where am I wrong ????
[M.O.J.O. Android Development] TwistyTravster:
Why did you change the file type to .bat? I would strongly suggest changing it back to .img. You also don't need to create a .txt file as long as you enter the command correctly in command prompt. I usually have the root folder open next to the command prompt so that I can see exactly what I'm looking at as a reference while I'm typing the commands. I usually make mistakes otherwise.

Did you flash the openrecovery to the fastboot? It wont work if you don't do that first, then you can enter the boot command.

If you're still having trouble, I can try to record a video for you and post it to YouTube. Just let me know.
[M.O.J.O. Android Development] Fastolfe18:
Sorry, I forgot few things in my previous post.

I've placed the two files (recovery and .bat) in the folder of the modaco mod MMM, (who have a file called "fastboot-windows.exe). Without this, you can't boot on the recovery I think... I suppose twrp may be already installed, because without this you can't install Remix OS.

The file to change in .bat is the .txt, not the img of TWRP. He is not an obligation, but it allows you to boot without typing on keyboard the command line.
[M.O.J.O. Android Development] HECTORdroid:
I could finally solve the problem once again caused me to install a rom shoddy, I think as a programmer at the time of making a rom should be tested as much as possible such as trying to prove with a hard disk or mention that the rom is not root and as usual my towelroot kingroot or can not be used.

The rom is very incomplete and with many errors, I preferred console me back to the original

Here I have some screenshots to see that I could do root in rom and so to me back to jelly bean
[M.O.J.O. Android Development] HECTORdroid:
Here is a complete tutorial video of how to install the OS REMIX well explained :D

TUTORIAL - Install Remix OS in M.O.J.O. Mad Catz Console

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

:D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D
[M.O.J.O. Android Development] HECTORdroid:
In this video we did an almost complete review of Remix OS and its performance in the console M.O.J.O. Mad Catz with apps, emulators and high-end games android.-

:D

https://www.youtube.com/watch?v=SjltQT2D0iY
[M.O.J.O. Android Development] Unjustified Dev:
Please do not link my ROM elsewhere I really like to track downloads. Also I was given no credit whatsoever not that it means anything but you didn't link the original place you got it from.
[M.O.J.O. Android Development] shpitz461:
Was able to easily get root back:

Reboot into TWRP, easiest using following command:

Once there, flash this one: https://download.chainfire.eu/896/SuperSU/

I cleared cache/dalvik and rebooted, superSU works great.

I tried kingroot prior, but it got stuck on 22% for a long time, so I aborted it and did the above.
[M.O.J.O. Android Development] dudex1:
Kingroot 4.8 just worked for me. I'm rooted now!
[M.O.J.O. Android Development] dudex1:
View attachment 3648961
[M.O.J.O. Android Development] shpitz461:
I tried connecting via adb over network, i get a 'empty host name' error.

I installed trickstermod and set a hostname, even rebooted, to no avail.
[M.O.J.O. Android Development] cometdata1:
Thanks for a great rom Unjustified Dev

Use KingRoot 4.8 to root device

TWRP 2.8.2.0 to create backup, Wipe and install Remix OS, install SuperSU before reboot or just

use KingRoot again to root again.

Enjoy :)
[M.O.J.O. Android Development] paulie_gogetit:
I'm screwed. I did something in twrp, rebooted and now I'm stuck on bootloop. I haven't been able to get in to recovery. I have windows 10, which I could not update drivers to connect and launch Fast boot. This all happened when I went in to recovery to try and do a clean flash. I was afraid to wipe data because twrp wouldn't recognize my microsd. At that point I believe I selected fix permissions and rebooted. Here I am. Help!! (please)

Edit: additionally I followed all instructions as in post #31 but no commands could be executed. :/
[M.O.J.O. Android Development] TwistyTravster:
You're not screwed. The same thing happened to me. You plug the MOJO in and it tries to boot to TWRP, then the screen goes black, and it reboots and does it over and over, right? As long as it still goes into fastboot mode when you plug in the USB to PC, then its still able to be corrected.

To fix this, I re-flashed the TWRP onto the fastboot.exe, and it cleared any errors and allowed TWRP to boot correctly. Just repeat the command lines in fastboot mode with the USB and it should eventually boot. I had to do it twice for it to work. If you can have the MOJO plugged into the PC with USB at the same time it is plugged into a TV with the HDMI, it helps significantly.
[M.O.J.O. Android Development] paulie_gogetit:
I have a bootloop at where "remix" on the screen just stays there and animates slightly. I've yet to get into fast boot. I originally rooted and flashed via USB stick. My command prompts tell me it's not a valid internal or external command.

---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------

Also when I double click fastboot it opens and closes real quickly. Running as administrator as well.
[M.O.J.O. Android Development] TwistyTravster:
You don't double-click fastboot. You do everything in command prompt. Go into the folder that fastboot.exe is in, then press shift + right click. Go to "Open Command window here".

Then once the command prompt window opens, it should show something like:

C:/[whatever your system file path is]/r3-mojo-superboot-mmm

That's when you enter the commands I posted above to flash TWRP to fastboot, then boot from TWRP using fastboot.

Make sure the file "openrecovery-twrp-2.8.2.0-mojo" is in the same folder as fastboot.exe as shown in the picture above.

Also, you shouldn't root and flash via USB stick. It is better to use a microSD card to do it.
[M.O.J.O. Android Development] paulie_gogetit:
Well I did the double click after. I entered the commands as described from cmd. I'm going to try a new usb cable for starters. Also, I'm on Windows 10 which doesn't have the feature you're displaying. Device manager couldn't update drivers either. I will try utilizing the microsd as you say. Not sure why but twrp wouldn't recognize my microsd either. I'll give this a go. Thanks for the replies. I'll update once I return from MOJO death.
[M.O.J.O. Android Development] TwistyTravster:
Yeah it could be the USB cable too. With the MOJO I received, it actually came with a USB to USB cable that has the same Mad Catz branding as the included HDMI cable.

Sorry, I didn't realize you're on Win 10. If you know how to use command prompt with the 'cd' command to locate the fastboot folder, then you can do it that way in Administrator mode. Did you update the drivers using the "windows.driver" folder in the r3-mojo-superboot-mmm (as shown in the above picture)? That is very strange that the microSD wasn't recognized by the MOJO during recovery. I wouldn't have a clue how to fix that. Maybe you're using the wrong file path for the microSD? The file path for the microSD should be: root\storage\sdcard0 (sometimes it is sdcard1).
[M.O.J.O. Android Development] shpitz461:
To boot into bootloader/fastboot, unplug power, plug USB, then plug power, you should see a black screen with text at the top left corner.

What i'm failing to understand, if you can't get into fastboot, how did you flash TWRP in the 1st place?
[M.O.J.O. Android Development] paulie_gogetit:
I was able to install TWRP through "Flashify"... I was able to execute the command prompt but i'm stuck at "Key driver not found.. Booting OS" After entering the commands it just says <waiting for device>

i've tried powering off and plugging back in...
[M.O.J.O. Android Development] jinsta:
Having install issues too with rom. can get into fastboot, install and use twrp to wipe, then install the remix rom....but upon reboot, just hangs on boot screen? Any ideas on what i need to do
[M.O.J.O. Android Development] shpitz461:
Oh I see. I never tried on W10, I'm only using Win7.

'Key driver not found.. Booting OS' means the Mojo is in fastboot/bootloader mode, if the command on Windows says 'waiting for device' that means the Mojo is not recognized. When you connect it, open device manager in Windows and see if it is listed. If it is, but malfunctioning, you just need to update the driver for it.

The driver is included in the 'r3-mojo-superboot-mmm' package.
[M.O.J.O. Android Development] wtgvr4me03:
Look up how to disable driver signature verification in windows 10. It should work fine after that, I used windows 10 last week for mine.
[M.O.J.O. Android Development] paulie_gogetit:
Understood. I ran into a problem updating the drivers through the folder included. Windows recognized madcatz but said there was an error updating the drivers. Let's see if a new cable will help. It should arrive tomorrow.

---------- Post added at 03:07 PM ---------- Previous post was at 02:53 PM ----------

It worked!! OK -- I'm in TWRP!!

---------- Post added at 03:53 PM ---------- Previous post was at 03:07 PM ----------

New issue: Remix installed -- goes through boot process, "Remix OS" on screen. After that it clears and I'm stuck in a black screen. Went back in to recovery, wiped, reinstalled: same thing.... ideas?
[M.O.J.O. Android Development] TwistyTravster:
Did you install the Gapps file, right after installing Remix?

Gapps located here, select ARM > 5.1 > mini
[M.O.J.O. Android Development] paulie_gogetit:
No. Not sure what happened. I finally wiped again, then flashed cyanogenmod. That made my screen flicker randomly. Wiped again, reinstalled Remix and it worked this time. I went from a dead box to up and running again. Thanks guys.
[M.O.J.O. Android Development] TwistyTravster:
No problem. Glad we could be of assistance.

Screen flicker happened for me when I used an older 720p HDTV on through an HDTV receiver. I tried it on a 1080p HDTV with no receiver and the flicker stopped.
[M.O.J.O. Android Development] Zebdula:
Wondering whats best rom for Mojo

Hi all. I tried the TV one. I did get netflix working by ES file exploring netflix from my Note 4 to the Mojo and used side loader app. But after installing some games it crashed and stopped booting. Anyway. Whats best, this remix or Cryo? I want to Watch kodi, netflix, and play games! Like everyone else I guess haha. Thanks
[M.O.J.O. Android Development] jvianney94:
I honestly feel like the stock rom is the best rom. I tried cm12 and remix and both had major issues that I just couldn't accept. The stock rom appears to be polished enough that I don't have much crashing, accept with some apps that just don't appear to like the mojo. But it was significantly less crashing than cm12 and remix. However, I've only used it for a few hours, so perhaps, in time, I will find reasons as to why the stock rom is unacceptable and the other roms are more suitable. Just need to put some more time into it. My kids were having too much fun playing angry birds on a 22 inch touch screen and that didn't give me much time to tinker. Which leads me to this, I discovered that if I plug my monitor in via usb and hdmi, I can get full touch on my dell st2220t monitor. That is pretty amazing. Now, I've got a micro android console and 22 inch touchscreen all in one
[M.O.J.O. Android Development] TwistyTravster:
I prefer Remix out of any of them. It is the most flexible and doesn't seem to have compatibility issues with any Apps. And, of course, Apps are makes any Android device powerful. I'll admit that it has some quirks with regards to the settings. But the multi-tasking ability is definitely what makes it stand out from the rest.

I use Remix on my old Dell Mini 10 Netbook. It has a 1.6Ghz Intel Atom and 2GB RAM, so it was basically useless with Windows, and slightly less useless with Linux and Mac operating systems. However, Remix is amazing for what it can do. It took an old machine and made it new again. So I guess I'm somewhat biased in that respect, but I feel that fits the exact way for what it does for the MOJO as well.
[M.O.J.O. Android Development] jinsta:
Still strugling with this rom :( have twrp installed via fastboot, performed wipe, installed rom, installed superSu, reboot but rom still wont work, does the remix os screen which shimmers for a bit them just hangs in black screen. I can move cursor around which shows up in white but ultimately screen goes black again and just hans here. i have tried to wipe, install remix followed by gapps....then supersu but same thing, hangs in the boot cycle???? any ideas
[M.O.J.O. Android Development] paulie_gogetit:
This happened to me. I got pissed and installed cyanogenmod. My screen kept flickering. I wiped again then flashed remix a 4th time. 4th time is the charm. I actually want to go back to stock. Problem is I don't have a backup and the rom online isn't flashable.

---------- Post added at 07:57 PM ---------- Previous post was at 07:56 PM ----------

I want to go back to stock but don't have a backup. The online zip doesn't seem flashable. Suggestions on how to get it?
[M.O.J.O. Android Development] TwistyTravster:
Did you follow my instructions in the other thread? The zip file mojo-signed-ota-MO0205-TS worked for me when I installed it through TWRP recovery.
[M.O.J.O. Android Development] paulie_gogetit:
It failed, but what I did was flashed SU zip, then tried flashing stock zip again and it worked. Thanks!
[M.O.J.O. Android Development] TwistyTravster:
If you go back and read the past couple of replies, paulie_gogetit seemed to have the same issue with black screen on Remix. I honestly don't know why Remix sometimes fails to install. Just keep trying it. Maybe flash the stock ROM and then try installing Remix again? Persistence seems to be the key here, but once it works, it works.

---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------

I had the screen flickering issue with Cyanogenmod as well. It seems to happen when you use an HDMI receiver, or when you run the MOJO in 720p. If you use a TV with 1080p and no receiver, the issue disappears.
[M.O.J.O. Android Development] jinsta:
Just dont understand what i'm doing wrong, i've tried install around at least a dozen times now...

...with/without Gapps

...with superSU from default TWRP/from zip using latest stable version

...the stock rom you linked me to before installs flawlessly and been here twice too as thought installing after this stable env would help, but no difference

All my install attempts lead to either a blank screen or best case a screen where it says starting or something similar, but hangs here. I've left overnight too, but still stuck on same screen thereafter.

With relation to wipe. I have previously wiped the internal storage. TWRP was installed afterwards again - is this perhaps a factor? Noticed there is a full format option in here...is that worth doing to clear all traces or not something to touch like.

Just going back to Gapps for sec, noticed when it was installing it said something about some of the apps being there already and presume it kind of writes over some in remix if installed after the rom - is that ok/norm. I know you recommended the mini flavour of install, but i was getting an failed message code (70 i think, which basically meant i was short on storage space) so had to use a smaller variant (nano), on the comparison chart It still has all the base files, just omits some goog apps which i was going to just install later once in the environment direct

Will try to install CM12 and then wipe again to install Remix, but i would assume a wipe is a wipe and shouldn't influence how Remix installs

Anyone know if there is any alt coming to the 2016-01-25 rom?
[M.O.J.O. Android Development] kevinthefixer:
Well, a wipe isn't always a wipe. Doing a standard wipe in TWRP is all fine and everything, but doesn't wipe everything, it leaves /data/media alone on the assumption that you want to keep your documents and pics and such. And it does nothing for a faulty filesystem. I recommend you try a full format of both /data and /cache in TWRP before trying to flash the ROM again, and just do the ROM, you can flash the GAPPS and SuperSU later if it works. The format of /data will take a LONG time, up to an hour, but DO NOT INTERRUPT IT! You will wind up with a pristine, error-free partition with any bad blocks marked for non-use.

Also, if you are having problems flashing the one ROM but not another--Did you check your MD5 sum on your download? I'm not sure how on Windows (I'm a foaming-at-the-mouth Linux user) but I know it can be done, check Google.

Wiping Cache and Dalvik after flashing, and before rebooting into system, sometimes helps. Hope I did!

BTW thanks to Unjustified Dev for all this. I just aquired a MOJO (the Woot sellout) but I'm not allowed to play until taxes are done. Damn!
[M.O.J.O. Android Development] jinsta:
Wooooooohoooooooooo! So thats did it...used format option in TWRP.....took a min max, so was slightly skeptical it did it, but ran the remix rom, rebooted and all is g double o d good :victory:

:good::good: Thank You Mr fixer! Thanks Twisty and Thanks Mr Dev :good::good:
[M.O.J.O. Android Development] gobeye:
Has anyone managed to get tincore to work with this Rom? It installs ok but the overlay is not visible and it doesn't seem to see the ctlr.

Great work btw!
[M.O.J.O. Android Development] kevinthefixer:
Interesting. In the TWRP versions I've been using on Asus transformers, it's been doing a full "secure" wipe, actually writing to each block in the partition and then reading it to make sure it's good. Now, the TFs are known for having cheap slow flash memory, but my TF700 with a 32GB drive (maybe 28GB /data partition?) takes forty-some minutes to accomplish it. Plenty of time for a coffee-and. Or a couple brews, if you're a drinking man. But I find it hard to believe it did that in under a minute, so either it didn't do a secure wipe, or the MOJO is flame-out fast! Can't wait to play with mine. Anyway glad it worked! FWIW this is called a "clean" flash and is recommended any time you are changing ROMs. Usually you can get away with dirty-flashing an upgrade to your existing ROM, but even then it's said to re-flash clean if you have any weird problems.
[M.O.J.O. Android Development] shpitz461:
I updated the stock image with build MO0205, then started doing the rooting and flashing of TWRP and RemixOS.

Never had a single issue, wiped all partitions prior to flashing RemixOS.

You need to use TWRP 2.8.2.0, nothing else. BETA-SuperSU-v2.66-20160103015024.zip works like a charm for me.

If you're having issues, maybe redo it from scratch and follow the instructions carefully.
[M.O.J.O. Android Development] jinsta:
Newbie, but Format looks very straight forward on TWRP (no config), just type a nervous YES to proceed and away it goes....really really quick. I'd performed a 'dirty flash' before hand so that may be a factor, but even that only took a min. Installing the ROM took longest, but even that's only like 5-6mins max :laugh:

I've not had device long, but it seems quite snappy so far!

One bug I've noticed is with Alert/Dialog Boxes - box itself will be black/dark, but the text/script that would be in it is just not visible....the OK/CANCEL (Selection text at bottom) is however fine.

So far, noticed it with the approval boxes that typically pop up via SuperSU on apps, but also came across one whilst in Mame4Android. Its somehow an issue with how OS displays them, I''ll update this post with screenshot later to help clarify issue.
[M.O.J.O. Android Development] kevinthefixer:
Perhaps try applying a different theme?
[M.O.J.O. Android Development] jinsta:
If you mean within SuperSU, I've tried 4-5 colour schemes and didn't help, but yet to try all. If its within system.... I've not even looked for this option :o i'll give it a go later!
[M.O.J.O. Android Development] kevinthefixer:
Never thought of theming the SuperSU app itself. I meant for the entire system. Surely there are canned themes available? If not, maybe try playing with accessibility options?
[M.O.J.O. Android Development] greevedogg:
I noticed this black lettering on dark notification blocks as well.

I was having problems with the CTRLR not working in games that it should have been. Had to flash back to stock to check, but for me, I couldn't get the game pad to work in Dead Trigger 2, even trying to use a keymapper...
[M.O.J.O. Android Development] jinsta:
No main theme changes in menu system. I've hidden problem i think by just not having supersu bring up its verification messages. Not seen any since but prob not great on the security front.

Same issue on dead trigger too, controllers just not mapped :(
[M.O.J.O. Android Development] kevinthefixer:
Just to make it easy: https://download.chainfire.eu/896/SuperSU/BETA-SuperSU-v2.66-20160103015024.zip?retrieve_file=1
[M.O.J.O. Android Development] silverbox750:
Hi there .want to know is the dts audio output issue fix in that os ? As im getting only all channle stereo when I play movies from kodi etc ..also fwtting very dark picture and thereis no settings to fix it .my main issue is the dts audio as when I play movie I get audio from all channles rather then effects from surrounds etc
[M.O.J.O. Android Development] ZigmaDK:
It's really awesome the work you do for the MOJO. Very much appreciated.

I haven't tested this rom yet, because I wanted to ask if it supports 4K resolution first?
[M.O.J.O. Android Development] jinsta:
Got Dead Trigger 2 working. Turns out the issue was just it not being set on full screen mode. Simple change of app properties and its all OK on the controller front :)

Notice it cant be set to the highest resolution as causes bad screen tearing. I cant be asked to rollback now, but sure this setting was fine on the stock rom, driver issue perhaps? not a biggie as main thing is it works again!
[M.O.J.O. Android Development] Mojoddz:
emulation

Hi there, I just got my mojo, primarily for emulators, I have a basic knowledge of such things and using the ones from play store. I'm interested in gcube and dreamcast which are iso. How do I get them working. Is there a better way to have emulators?

What do you guys recommended doing to my mojo from the start. Alot of what I've been reading here sounds complicated and I could do with a starting point.

Many thanks
[M.O.J.O. Android Development] greevedogg:
Good to know! I'm kinda digging my stock/rooted setup, so I'll probably be sticking with it for now.

On stock/rooted, I was able to get Trials Frontier to work on the Mojo with keymapper. Well worth the $6 for the full version.