yashsingh1/xdaforums huggingface dataset:
[M.O.J.O. Android Development] TwistyTravster:
If you managed to get the stock firmware on your MOJO, then installing Remix is just as easy. You repeat the same procedure as you did to install the stock firmware in TWRP recovery, except you install 2 different zip files, one after the other, on the INSTALL screen, instead of just one file.

First go into TWRP recovery, re-wipe everything as you did before, install the Remix OS zip file, then install the Gapps zip file (located here - ARM : 5.1 : mini) right afterwards, all from the microSD card. You didn't need to install a Gapps zip file for the stock firmware because it was already included. The Gapps file includes the Google Play Store, and basic Google apps. After this is done, reboot the MOJO, unplug the USB cable and it should boot into Remix 2.0.

Again, you can always go back to the stock firmware if you don't like Remix or if you run into any problems. However, I found the stock firmware was prone to freezing up after a while.
[M.O.J.O. Android Development] jinsta:
Hi. thanks for the assist again! i followed above, downloaded the mentioned GAPPS file. In twrp, i perform wipe, install remix and then i try to install gappz but it it comes up with error and doesnt install

Error code 70

E:error executing updater binary in zip....

error flashing zip...

Its deffo the arm/5.1/mini that i used, are any of the alts also compatible that i could try?

Update: Two additional factors are...

1) my 'internal storage' was wiped on TWRP

2) not sure if this is an issue, but from within last stock image when it was running, i updated SuperSU to latest version from playstore and this caused some issue with binary

Would this impact on why i am receiving the above errors?

The error code 70 was caused because i didn't have enough space on the install partition. Using a lighter version of the GAPPS installs error free. I'm not sure what the size of the partition is but its not using the 16gb space, merely a small section of it. Using the NANO size GAPPS fits alongside REMIX if of any help to anyone. Remix Rom still doesn't install, but moved this issue to the Remix thread as more relevant.

Big shout & Thanks to TwistyTravster for taking time to input on this!
[M.O.J.O. Android Development] maverixz:
Okay I just screwed up. I was in TWRP and had just wiped the system to install RemixOS when my son accidentally tripped on the MOJO's power cable and it powered down. Now all I get is a black screen. Is there any way to access the recovery?
[M.O.J.O. Android Development] TwistyTravster:
TWRP may have created an error. You need to re-flash TWRP recovery to fastboot, and then boot from TWRP rocovery using the fastboot via USB. Follow the first few steps in these instructions to fix and restore TWRP recovery. The instructions I linked are for how to re-install the Stock firmware, but the first bit will help you get back into recovery to install Remix instead.
[M.O.J.O. Android Development] HECTORdroid:
3 Methods To enter recovery mode in M.O.J.O. Mad Catz

https://www.youtube.com/watch?v=fBzbGe-P2vE
[M.O.J.O. Android Development] maverixz:
Thank you very much.

Thank you very much.
[M.O.J.O. Android Development] maverixz:
Gents I tried the 2 methods and so far no luck. Is there anything I could be doing wrong? When I used the USB male to USB male method, I got the "Key driver not found... booting OS" message but when I typed the command to install the twrp image, it says "waiting for device" then hangs there. I tried using a USB keyboard to use the ALT+PRTSCRN+i key combo, no luck there either.
[M.O.J.O. Android Development] TwistyTravster:
Just trying to come up with reasons why it wouldn't be working... hmm... maybe a bit of troubleshooting is in order.

For the USB to USB method, does Windows correctly detect the "Mad Catz ADB Interface" driver for "fastboot" when it is plugged in? My first time using the USB to USB method, Windows didn't detect the drivers fully, and I had to manually update it using the folder called "windows.driver" in the "r3-mojo-superboot-mmm" folder. Apparently Windows 10 users need to select "disable driver signature verification". I don't have Windows 10, so I can't show you; you'll have to look that up.

Did you make sure that the TWRP image file is in the same folder as the fastboot file?

Short of that, just make sure that the command prompt window is being run as Administrator, and that the commands are being entered correctly.
[M.O.J.O. Android Development] maverixz:
You are amazing. I discovered, thanks to your posting, that the "Mad Catz ADB Interface" wasn't well install;ed on my Windows 10 Pro laptop. Each time I tried to re-install the drivers it came up with an error message.. I have no Windows 7 box in my house so I'm taking one of the laptops and installing Win 7 on it.
[M.O.J.O. Android Development] maverixz:
Update: Windows 7 installed on a laptop, driver was correctly installed and process went smoothly. Running CM 12.1 now on the MOJO. Thank you very much.
[M.O.J.O. Android Development] greevedogg:
I buggered something up with trying to revert from RemixOS to stock. Now, I'm stuck on RemixOs with no Gapps...No Play store, no Google Drive, etc...

I can't get the MOJO to recognize a USB drive or external sdcard(maybe I don't know how?) How can I get Gapps installed? Via wireless adb? Or better yet, how can I get the stock ROM in some sort of readable location that I can flash during TWRP? Like a 'tard, I failed to make a backup lol. TIA

Edit: Back up and running stock MOJO...Couldn't ever figure out sideloading, but I finally did get my external sdcard to be recognized in TWRP, which I was then able to flash the stock ROM from zip within recovery. I would like to know how to use adb to push files and sideload, in the event that I screw something up again, which is inevitable...At least this time, I made a nandroid backup!
[M.O.J.O. Android Development] kevinthefixer:
You can simply remove your microSD card and plug it into your PC's card reader and copy an APK file to it. Then use a file manager to find the APK, click on it and it'll ask you if you're sure you want to install.

ADB is a little more complex. With the MOJO booted into recovery, plug the USB cable from the MOJO to the PC. Open a terminal (or DOS Box) in the folder with the ADB and fastboot commands, enter:

adb devices

It should return whatever it thinks is the serial # for the MOJO and "Recovery", but as long as you get a return you're good. Then:

adb push (filename.apk) /data

Reboot into Android and your APK file is in the root of the /data partition. This can be done by:

adb reboot system

(I can never remember if there is a dash between reboot and system or no).

There is also an install function in ADB:

adb install filename.apk

In both cases, make sure the file filename.apk is in the adb/fastboot folder.

I've never used wireless ADB but U. Dev posted the command just a few posts back to connect. You'd do that in Android system, not recovery.

Perhaps one of you Windows users could go over what I just wrote and make sure I didn't screw up too badly? I rarely use Windows at all, and never for adb/fastboot operations. Linux is SO much easier, and you don't have to worry about drivers. I'm looking forward to trying it on my new MOJO, but I'm not allowed to play until taxes are filed!
[M.O.J.O. Android Development] rkitect:
I'm posting this in the TWRP thread since this happened to me while in TWRP.

Well, it appears I managed to brick the unbrickable. While trying to do a fresh install of a ROM I ended up in TWRP after having just wiped system when I lost HDMI connection to my monitor. I was unable to recover video output after plugging the HDMI cable back in and trying multiple monitors. I ended up unplugging the device in hopes to be able to get it to boot into recover using a keyboard or USB cable method. Ever since, I have not been able to get anything other than a black screen after power up. None of the PCs that I plug USB into with the mojo will even recognize that a device is plugged into the USB port. Hopefully someone will read this and learn from my mistakes and this post will have gone on to prevent someone else from ruining their unit! Thanks everyone for the development and help. Keep up the great work!
[M.O.J.O. Android Development] TwistyTravster:
Understand that this is a long shot, at best. I would never recommend this under any other circumstance.

If your MOJO truly will not boot to anything at all, then something must be screwed up in your fastboot. If you open up your MOJO, there may be some possible way to reset your CMOS with a button, or maybe by removing the battery and reinstalling it. If it even uses a removable battery at all, I don't have a clue. Short of that, I don't know of any other way of fixing something like this.
[M.O.J.O. Android Development] kevinthefixer:
Guess it won't hurt to try. I doubt the MOJO has a battery; it does not keep real time when powered off, and of course it's designed to be an always-on thing. So any buttons inside won't do anything unless the machine is powered on. It should be safe enough, though, it only runs on 5 volts. There is probably a PROM chip in there that could be re-programmed if it's a firmware problem, but it's likely to be soldered onto the board and so would require lots of time and equipment to do that. There is a procedure to reflash Nvidia processors, but AFAIK it has not been implemented for the MOJO, and in any case it must be set up beforehand for each individual device. In other words, more work than the MOJO is worth and too late anyway.
[M.O.J.O. Android Development] rkitect:
I can certainly give it a shot. I have a note in to Madcatz support to see if there's any response. I'll be waiting on that response to decide if I should open it up. Thanks again for the suggestions.
[M.O.J.O. Android Development] kevinthefixer:
I was just browsing the "general" section, there's a thread there about power and reset buttons. It gives a very good howto open the box.
[M.O.J.O. Android Development] xxhtownutzxx:
So I flashed to CM12 and was loving it until today. I went to change my theme and noticed you can download themes from playstore so i did. Once I applied it everything went to ****e. For example I cannot open things like playstoreand other apps,ES file explorer doesn't recognize my internal memory, etc. I tried to reboot into recovery but I cannot do that either, all that happens when it reboots is a dead looking droid with its stomach open and a red exclamation triangle pops up on screen. After a few seconds it reboots again to home screen. So i dont think I'm completely bricked but cant do much now without getting into TWRP. Pics below are of my mojo screen during reboot into recovery and the theme i applied that caused all these issues. Please help!
[M.O.J.O. Android Development] shpitz461:
Just dirty flash the rom again.
[M.O.J.O. Android Development] kevinthefixer:
This is a double post

Please do not post the same question in different sections.
[M.O.J.O. Android Development] aeshma:
Twisty I have sent you a private message.

I run prompt as admin and try to run flash recovery but I get the following message:

"C:\r3-mojo-superboot-mmm>fastboot-windows.exe -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img

target reported max download size of 643825664 bytes

sending 'recovery' (7312 KB)..."

The Booting OS logo starts flashing...

How long should it take? Is it me that it is not waiting enought (awaited 10 minutes) or is it stuck?

Please help.

Edit** IT WAS THE USB CABLE!!! I MANAGED TO REVIVE THE MOJOOOO I CAN'T BELIEVE IT! When I was going to flash the stock rome I finally realized what was the error "BACKLIGHT LED ERROR".

TWISTY YOU ARE A HERO!!!! THANK YOU VERY MUCH!!!!!
[M.O.J.O. Android Development] kal357:
Can someone please look at the post I created under can someone please help me under General
[M.O.J.O. Android Development] gbrooke:
im getting same led/backlight error and booting to a black screen...im using the usb cable that came with my mojo, please help!!!!
[M.O.J.O. Android Development] blonde410:
I'm in recovery mode won't respond to controller or any mouse. Does the mouse need to be a wired one?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] sidramobilecare:
dear friends

n7000 was working well but baseband was null,

hangs on logo after efs write with riff,

even full flashing with N7000DDLSC_ODDLSC_India_Android_4.1.2 not solved.

philz_touch_6.48.4-n7000.tar flashing with odin also fails

[11/22/2014 8:03:36 PM] [START OPERATION_ID = DCC_WRITE_MEMORY]
[11/22/2014 8:03:36 PM]
[11/22/2014 8:03:36 PM] Current Settings:
[11/22/2014 8:03:36 PM] -----------------
[11/22/2014 8:03:36 PM] Address: 000000400000
[11/22/2014 8:03:36 PM] Length: 000001400000
[11/22/2014 8:03:36 PM] Address Space: ROM1
[11/22/2014 8:03:36 PM] AutoFullFlash: UNCHECKED
[11/22/2014 8:03:36 PM] Use End Address: UNCHECKED
[11/22/2014 8:03:36 PM] ECC Module Enabled: UNCHECKED
[11/22/2014 8:03:36 PM] Image File is Used: UNCHECKED
[11/22/2014 8:03:36 PM] Use Address as Offset: UNCHECKED
[11/22/2014 8:03:36 PM] Main (CHECKED): C:\Documents and Settings\Admin\Desktop\N7000_GB_256MB_Live\n7000 256mb.bin
[11/22/2014 8:03:36 PM] Redu (UNCHECKED):
[11/22/2014 8:03:36 PM]
[11/22/2014 8:07:15 PM] Open serial port...OK
[11/22/2014 8:07:15 PM] Connecting to the RIFF Box...OK
[11/22/2014 8:07:15 PM] Firmware Version: 1.37, JTAG Manager Version: 1.56
[11/22/2014 8:07:15 PM] Selected Resurrector: [Samsung N7000 V1.0.4860.58267]
[11/22/2014 8:07:15 PM]
[11/22/2014 8:07:15 PM] Connecting to the dead body...OK
[11/22/2014 8:07:15 PM] Detected dead body ID: 0x4BA00477 - CORRECT!
[11/22/2014 8:07:16 PM] Set I/O Voltage reads as 2.81V, TCK Frequency is 8 MHz
[11/22/2014 8:07:16 PM] Settings Code: 0x20010B00000000400000000001400000
[11/22/2014 8:07:16 PM]
[11/22/2014 8:07:16 PM] Resurrection sequence started.
[11/22/2014 8:07:16 PM] Establish communication with the phone...OK
[11/22/2014 8:07:16 PM] Initializing internal hardware configuration...OK
[11/22/2014 8:07:16 PM] Uploading resurrector data into memory...OK
[11/22/2014 8:07:16 PM] Starting communication with resurrector...OK
[11/22/2014 8:07:16 PM]
[11/22/2014 8:07:16 PM] Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
[11/22/2014 8:07:16 PM] Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (VYL00M, 0x000000080000 Bytes = 0.50 MB)
[11/22/2014 8:07:16 PM]
[11/22/2014 8:07:16 PM] Writting FLASH1 memory from 0x000000400000 to 0x0000017FFFFF
[11/22/2014 8:07:16 PM] Completed in 00:03:37.859 (Average Transfer Rate: 94.01 kB/s)
[11/22/2014 8:07:16 PM] [FINISH OPERATION_ID = DCC_WRITE_MEMORY]

how to recover it please
[Moto X Q&A] koolguy366:
i have searched a lot n didnt find the apk, and my data pack here in india is very limited hence downloading the whole cm12 rom n extracting the apk is not an option for me :):p
[Moto X Q&A] piskr:
Attached.
[Moto X Q&A] Travisdroidx2:
I don't need the launcher. However, I gave you a thanks since the OP did not.
[Moto X Q&A] jco23:
Soooo... Will this launcher work on KitKat? I mean, I alreeeeeady know, just perhaps to let others know as well........[emoji12]
[Moto X Q&A] piskr:
Thank you. It's always good to know that you helped somebody. Otherwise I don't use that launcher either. Currently I'm still on KitKat and I have launcher with more options and customization possibilities. Apex, Epic or other variants of 4.4 launchers are better choice. I'm yet to choose better Lollipop launcher when it becomes actual.

---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------

It works also on the KitKat.
[Moto X Q&A] koolguy366:
i know its damn late for a reply... but thank youso much Piskr :)
[Moto X Q&A] Rohitagni:
Can you please upload all of the cm12 apps?
[Moto X Q&A] Travisdroidx2:
If he uploads the gapps then you still have to download them. Why not just download the gapps posted for cm?
[Moto X Q&A] richard el renthlei:
Cm12 launcher not working kn kitkat 4.4.4 , it gives unfotunately force close?
[Moto X Q&A] Rohitagni:
Can u please upload the file manager and the Audio FX app?
[Moto X Q&A] heyis4horses:
Here you go https://www.dropbox.com/s/h4lxrenpr5jthyf/here.zip?dl=0
[Moto X Q&A] Rohitagni:
Thank You.:D
[Moto X Q&A] richard el renthlei:
This is not cm12 launcher it is not trebuchet:thumbdown:
[Transformer TF300T Q&A, Help & Troubleshooting] Drahric:
Is there a possiblity that a shut down animation can be added to tf300 roms and is it as simple and adding a shutdownanimation.zip to /system/media?

Thanks

Sent from my TF300T
[Android Q&A, Help & Troubleshooting] ATGkompressor:
I'm using Apktool for Android v'4.1.1 on a Verizon SGS3 4.4.2...I'm trying to decompile Systemui.apk in hopes that I can port the card stack view in the recents panel, like in lollipop or the Note 4.

I keep getting an error while decoding the resource files. It's says that it can't decode attr value: using undecoded value instead for numerous things.

I have SELinux set to permissive, apktool if framework, etc...I can decompile AOSPA Systemui.apk no problem. It even creates .yml file as well. But I can't recompile directly after decompile without editing anything either. This is driving me nuts!

HELP!!!!
[Fire TV Q&A, Help & Troubleshooting] danknasty:
I finally managed to get spmc to show up on the home screen of my fire tv stick and it will open the app when i click the icon. But if I click information it still acts as if i did not purchase it and when I try to purchase it says this app is not compatible with my device. It also does not show up in the app menu so if it ever disappears from the main screen i have to go all the way to settings etc. Is this how it is supposed to behave and will it still get auto updates?
[Fire TV Q&A, Help & Troubleshooting] Skater4599:
This depends on how you did this, there's a variety of options I've seen on getting SPMC on the homescreen, using llama or even the deregister/register method. But in either case, no sideloaded apps will not be auto updated, you will have to manually update them. infact SPMC released an update yesterday 13.4.0.

Amazon has yet to officially mark SPMC as compatible with FTV, and at this point it looks like they may not ever do it. So if you used the deregister/register trick, it showing incompatible is what I would expect to see as normal.
[Fire TV Q&A, Help & Troubleshooting] danknasty:
I just updated to the new version I was worried I would have to restore my whole xbmc backup but when I installed the latest apk it just overwrote the current one, cleared the cache and did the initial first time run thing. Then it loaded straight back to my setup. Out of curiosity I have just been installing the launcher version on all my devices ftv or stick, does it make a difference?
[Fire TV Q&A, Help & Troubleshooting] Skater4599:
The launcher version is made to function as the default launcher if you wanted that option. However it requires root and rbox's xposed module to make it work on fire TV. So you're just not see'ing any difference in it, if/when you gain root it will make a difference depending on how you want it set up.
[Fire TV Q&A, Help & Troubleshooting] danknasty:
Yea I have it on all my rooted aftvs and just out it on my ftv sticks as we. Just making sure there's no disadvantage to having it on a non rooted device.
[General Topics] Mokele Mbembe:
Dear folks,

I need to hear your thoughts about rugged phones.

Basically, i an tired of drowning and destroying my phones during my outdoor activity (mostly fishing and hunting). I have had great Motorola defy, but recently got a nice corporate plan on Telus with a decent coverage, and a lot of data. Bought myself a moto g lte edition as a temporary solution, but need something nice and sturdy. Thought originally about any xperia z (1, 2, 3, whatever), they are indeed waterproof, but look flimsy. Recent Kyocera phones look nice, but brigadier is out of question, as it's for Verizon only and no one rooted it yet. Duraforce could be unlocked, i know, and used for telus, but no one knows about it. Samsung rugby is a but outdated. What would you guys buy (especially those who spend a lot of time in the wild)?

Thanks in advance!

P.S. Please don't suggest me an otterbox or a bag. The phone must be waterproof and LTE enabled
[General Topics] Mokele Mbembe:
2G only on Telus :crying:

But thanks anyway
[General Topics] retconnie:
Get an old razr phone
[General Topics] Mokele Mbembe:
Razr Max?

"splash resistant " only
[General Topics] retconnie:
lolz no old razr. Flipy fone. Imposbile to break. they work so good motorola must make new version that break easier, make moar monies.

Look, you have special needs for fone. Nobody wants make fone for you, it's not profible. You can get good waterproof phone, but you must sacrifice. Can't have it all. Either get ottobox or get fone designed for waterusage. Extreme sprots phone.

youve already done you reserch, asking here won't change fone market. You must choose what's most imporant for you
[General Topics] Mokele Mbembe:
Thanks, I was asking about personal thoughts and experiences. For now, I am kind of torn between Kyocera duraforce and galaxy s5 active, but that may change. I have few more months before new season.
[General Topics] retconnie:
Hope you get good new phone! Never fun to compromise. When fones first designed, engineers design them to last for 5 years. Phone companys say thats bad, plan obsoletence make moar money. Engineers want to give u good fone. It's thanks to greed we get what we has

engineers take pride in work. Take antennas for example. Thanks to new fractal designs, huge annetta fit in tiny new fone. Signal amazing compared to old fones. Engieers and math people make brilliant work. But it only included because it profitble for fone companies. Wish engineers were allowed to do moar for us.
[General Topics] Mokele Mbembe:
The world is not perfect my friend. You are right : more phones become waterproof means less phones drown, which means less replacement phones are purchased - sales go down = non-profitable
[General Topics] Davek30:
I have the duraforce and like the ruggedness of it, wish i could root it though. My wife has the s5 active and she has already dropped once and cracked the glass. The S5 active is not near as durable as the duraforce in my opinion. Note i have dropped mine and put it in water and it still works perfect.
[General Topics] Mokele Mbembe:
Thanks.

Went to bell store, and they only had a dummy one to look at. I wonder if the power button sticks out too much and could be accidentally pressed in the pocket
[General Topics] ekowi:
get an kyocera brigadier, best rugged... but till now still waiting rooted metode coz apn setting is locked.
[Android One (First-Generation) Cross-Device Themes] Swapnil Solanki:
Guys Are you Waiting For a Port of MIUI??

If yes, Then dont wait Try this theme.

Features::

1.) Full MIUI V6 Finishing.

2.) MIUI HD Boot Animation.

3.) MIUI V6 Fonts.

4.) MIUI V6 Toast.

5.) MIUI V6 Ringtones (ui, alarm,notification, ringtone)

6.) MIUI V6 Apollo Theme. (Full)

7.) MIUI V6 Lockscreen.

8.) Many More of MIUI V6. .

Download Link::

http://xdaforums.com/android/themes/theme-miui-v6-cm11-pa-xda-edition-08-03-t2837378

A Special thanks to the recognised themer [MENTION=2563179]jasonevil[/MENTION]

Please Press Thnx or Donate him.

If U liked it Then press thanks button.
[Android One (First-Generation) Cross-Device Themes] srijan041:
You should have given a screenshot
[Android One (First-Generation) Cross-Device Themes] xenreon:
Nice share
[Samsung Gear VR] yzf750:
So I got to thinking, I have the Samsung screen mirroring HDMI dongle on my home theater setup. I turned it on , mirrored the screen and put my Note in the headset. It then shows up on my 10 foot screen and I set my projector to 3d side by side and it works great. You can now have one person with the headset on doing stuff and everyone else can watch it on the big screen in 3d also :)
[Samsung Gear VR] AspenMan:
That's awesome! Wish I had the TV setup to do it. How's is a big projection screen in 3D?