yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] my1stSmartPhone:
Sorry for the delayed follow-up. I had only fragmented opportunities to examine the content that you linked to (a few times), then things went crazy in the home stretch of 2014 at work, before the holiday season. Then the holiday season came in at full force (not that I'm complaining). Only now having a chance to look at this again, and a limited chance at that. Will respond with more thoughts/decisions as soon as possible.
[Nexus 5 Q&A, Help & Troubleshooting] QA Bot:
Q&A for [ROM][5.0.1][LRX22C][hammerhead] Lollipop Dream [Build 7][20141211]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][5.0.1][LRX22C][hammerhead] Lollipop Dream [Build 7][20141211]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Nexus 5 Q&A, Help & Troubleshooting] DjSeNaSs:
Gps disfunction

Am I the only one that encounter problems with gps. It does'nt work at all. In google maps, waze, ingress (google game).

I tried to reflash, change kernel and it changes nothing. Any sugestions?
[Nexus 5 Q&A, Help & Troubleshooting] hoi273:
Black screen by incomming call

I love the Rom en the custom stuff

But screen doesn't turn on with incoming calls while the screen is locked,

While the screen is locked, incoming call is shown as notification on the locked screen.

It needs to be tapped twice to open and then swipe to respond to the call.

I haven already double-check my priority notification settings.

Pleas help.

And sorry for my bad Engels I'm from Holland.

also i cannot unlock my simcard via the sim Pin code

I don't sie the enter button after typing the correct pin
[Nexus 5 Q&A, Help & Troubleshooting] El Daddy:
Closed by OP request. Please use link in the first post.
[Sony Xperia T, TL, TX, V] Frosty4810:
Hey all, hopefully someone can help me out. Ill post the full story and the tl;dr version at the end.

So, my Xperia TL (LT30at) has been rooted for over a year and a half. Since i rooted it it never charged when turned off. I did research and couldnt figure out why, so i left it and have lived with it for the last year and a half. However, i just updated my phone to JB 4.3 by Dark Lord (Ultimate Pure XT ROM) so the model number is actually Xperia T (LT30) Anyways, the phone dies a lot quicker than before so the other day it died and because it wont charge when it is off i usually wrap a rubber band over the power button so itll charge enough to turn on and then charge by itself after that. However, it would only charge enough this time to boot, but then turn right back off. I did this for well over a day and got sick of it not working so i tried messing with things. In the process, I was in recovery (it was philz cwm or something like that, by the way im quite a noob when it comes to all of this, hence why im having problems) and i flashed the xposed disabler zip, thinking it would get rid of cwm because i didnt know what I was doing. It did end up getting the phone to turn on, and its charging great. However, the system UI crashes, and the "unfortunately the system UI has stopped working" pops up repeatedly so you cannot physically do anything on the phone. I tried going back into recovery to flash my backup to fix everything, but it was downgraded back to an older version of cwm, the version i origonally had on it before the 4.3 update. its like 6.0.3 or something, by david marcos or something. Anyway, itll go into recover but a bunch of error messages come up, like unknown volume path, no etc/recover.fstab, stuff like this. There is no way to flash any recoveries because it basically says it cannot find the paths. It will not backup, restore, wipe anything, flash from sideload, nothing. Ive tried all i can think of. Basically cwm comes on but i cant use it for anything. Instead i tried reinstalling cwm to try to fix it, but when i do it says "system cannot find path specified" so it wont download.

tl;dr version, cwm wont work at all after flashing xposed-disabler.zip. i cannot flash any recoveries or install anything through the usb. What do i need to do to fix this? because the system ui keeps crashing my phone is basically useless. thanks for dealing with a numskull..thanks in advance.
[Sony Xperia T, TL, TX, V] arniks8:
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.

Sent from my Xperia T using cm12
[Sony Xperia T, TL, TX, V] Frosty4810:
why i didn't think of that, i dont know.

This worked as far as getting the phone to boot and whatnot, however the phone died and because it doesnt charge when it is off, i cant turn it on. it will boot and itll get all the way to the home screen but it immediately shuts back down, even though it is plugged in. Is there any way to fix this charging bug? i did some research and found it is linked to cwm, however now that i flashed the stock rom i no longer have cwm on the phone, so why does it still not charge when off? Thanks for the help by the way..
[T-Mobile, Samsung Galaxy SIII] leuch3rd:
Hey guys,

I have a T999L running 4.3 stock, TWRP 2.7.0.0, rooted, de-knoxed. I performed a nandroid backup in TWRP, went back into TWRP to install a custom rom but now TWRP cannot mount my SD card nor my internal memory. I Odin'ed 4.3 stock back on the device, reinstalled TWRP, but still no dice - TWRP will not mount SD card/internal memory. I flashed CWM over TWRP but the issue persisted. I have been looking at other posts but haven't found a solution to fix this (Maybe use droid explorer or ADB?).

Any help you guys can offer will be greatly appreciated. Thank you!

Additional information:

Qualcomm Secureboot: Enable

Custom Binary Download: Yes (8 counts)

Bootloader AP SWREV: 1
[T-Mobile, Samsung Galaxy SIII] scoutsdoitbetter:
same

I'm having the same issue. Very frustrating.
[T-Mobile, Samsung Galaxy SIII] QuatroQuatro:
Brand new install, nothing

I just bought a t999L, but I've also had this issue on previous Sprint S3's and T999. Seriously nobody can even recognize this issue?
[T-Mobile, Samsung Galaxy SIII] JoeMoDo:
I read something on here about the twrp issue being caused by method of root... I towel rooted, and have this issue, while root66ers and others do not. Not positive it had anything at all to do with it, but that's 'what I heard'. Anyway, cwm and philz work fine for me, and while I would prefer team win, those work. Not much help, but it's something to look into!!
[Micromax Canvas 2 Plus A110Q] :
[Q&A] [DISCONTINUED][XPERIA][4.4.2-LIKE] PureXperia Z2 FOR CANVAS 2 PLUS[A110Q][Per

Q&A for [DISCONTINUED][XPERIA][4.4.2-LIKE] PureXperia Z2 FOR CANVAS 2 PLUS[A110Q][Performance + Battery Life]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [DISCONTINUED][XPERIA][4.4.2-LIKE] PureXperia Z2 FOR CANVAS 2 PLUS[A110Q][Performance + Battery Life]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Micromax Canvas 2 Plus A110Q] Akki7827:
Album Force closed problem

Can anyonr tell how yo solve Purexperia z2 Album force closed problem??

Plz:confused:
[AT&T Samsung Galaxy Note 4] ElCamino:
Got a hold of the Galaxy Note 4 Blossom Pink unlocked. Here is a video overview and also a quick benchmark vs the Snapdragon Galaxy Note 4.

http://youtu.be/tVCvosTiHQA

[youtube]tVCvosTiHQA[/youtube]
[Nexus 7 General] skallal:
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.

So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?

Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.

Thanks in advance...
[Nexus 7 General] mtbgus:
N7 2013 forum is best place for you - http://xdaforums.com/nexus-7-2013
[Nexus 7 General] skallal:
Tapatalk won't let me post to that forum. I'll try a browser...
[Xiaomi Redmi 1S] aliennastik:
whenever i tried to use roesoft ram expander on any cm11 based rom...i got an error "invalid argument"....i tried to use external memory card foe swap file...

help me guys
[Xiaomi Redmi 1S] otidotid:
make sure you read how to used the apps..

you have to make a ext3 partition in your sdext
[M.O.J.O. Android Development] Unjustified Dev:
INSTALLATION:

* Download MoDaCo Mod for MOJO Here . This zip contains the adb and fastboot binaries for Linux, Mac , and Windows. If you have windows install the drivers inside the zip if not continue.

* Place the downloaded image in the root of the r3-mojo-superboot-mmm folder

* Enter fastboot mode by unplugging the device and connecting the male A to male A usb cable to the device and the computer and plugging in the power adapter. Once in fastboot follow the below commands.

* To exit fastboot mode remove the male A to male A usb cable and plug in the power adapter to start a normal boot.

WINDOWS - open cmd prompt in the root of the r3-mojo-superboot-mmm folder

To install the image to device:

fastboot-windows.exe -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img

To boot the image:

fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img

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

chmod +x fastboot-mac

./fastboot-mac -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img

To boot the image:

./fastboot-mac -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img

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

chmod +x fastboot-linux

To install the image to device:

./fastboot-linux -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img

To boot the image:

./fastboot-linux -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
[M.O.J.O. Android Development] Unjustified Dev:
USING TWRP:

* You must have a usb mouse installed. Alternatively you can use the C.T.R.L.R in mouse mode to navigate the UI.
[M.O.J.O. Android Development] Unjustified Dev:
[MENTION=5638480]gwaldo[/MENTION] [MENTION=6228629]Sir Jaxxy[/MENTION] I have posted a new build . The name of the image is exactly the same so it matches the instructions so make sure you delete the previous image. The issue was a file was missing landscape.xml and the reason mine didn't fail is because I had a custom theme applied which included this file. Enjoy!!
[M.O.J.O. Android Development] shabbypenguin:
Top notch work :)
[M.O.J.O. Android Development] gwaldo:
It's booting, but I'm not getting no display (No DVI-D Cable is displayed on monitor)

Also, ALT+SYSREQ+I doesn't re-init the display.

At the end of the recovery.log
[M.O.J.O. Android Development] Unjustified Dev:
This is very strange as it seems to be displaying ok for me and another guy. Try flashing the image first then using an app such as Quick reboot to boot into recovery and see if it loads. That error is there because there is no backlight as the device has no display I see that error when flashing or wiping. I've also disabled screen timeout because it's kind of useless for it to be implemented on a device such as this one.
[M.O.J.O. Android Development] gwaldo:
nope :(

I've used the newest img, can you upload the original, that one had a resolution issue not a display, issue for me.

Flashed it,

booted normally,

bootmenu reboot, rebooted into recovery

Same 'No DVI-D cable'

I tryied pluging in the HDMI cable at different times before boot/after boot, but same.

I'll try on the TV later today, but i'm not optimistic :/

I guess it's not using the mojo's kernel right?

the keyboard ALT+SYSREQ+B and O don't work (reboot, shutdown)

How's the another guy?

Maybe he was being nice?
[M.O.J.O. Android Development] Unjustified Dev:
He's already running cyanogenmod. Try deleting that theme you placed in the sdcard. I'm not sure the exact error but I too end up with no signal only if the TV was powered off before recovery booted or if I turn the TV off and try to turn it back on. I can used adb devices and it still shows it's in recovery not sure the exact cause of that issue.
[M.O.J.O. Android Development] kgersen:
is there a way to enter recovery (or reboot to recovery) from the mojo itself ? that is without the need of an usb cable, a computer and typing the "fastboot... boot" command.

I tried the 'reboot to recovery' function of this app: https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager but it didn't work
[M.O.J.O. Android Development] Unjustified Dev:
Did you fastboot flash the image? It won't stick if you don't flash it. You can type adb reboot recovery via wireless adb. You can also try the quick reboot app
[M.O.J.O. Android Development] Sir Jaxxy:
I use this app and it works great :)

https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
[M.O.J.O. Android Development] Unjustified Dev:
Yeah that's the app. [emoji3]
[M.O.J.O. Android Development] gwaldo:
You need to flash the recovery to mojo once, then yes it *should* work.

I don't have a display which can handle the initial display and need a keyboard to do a ALT+PrtScn+I to reinitialize before seeing it.
[M.O.J.O. Android Development] kgersen:
yeah that one worked, thx.
[M.O.J.O. Android Development] Enectic:
Just letting you guys know that I was able to successfully flash the recovery using this app. Worked without issue and it's an option for those without a USB cable.
[M.O.J.O. Android Development] gwaldo:
2.8.2.0 works for me using the HDMI capture... Haven't tried on a TV yet.

It pairs with the CTRLR (blue light comes on) but doesn't work, keyboard doesn't work either, mouse is the only working input.
[M.O.J.O. Android Development] Unjustified Dev:
Are you in mouse mode seems like it's the only mode that works for us.
[M.O.J.O. Android Development] gwaldo:
Yip, i switched to all modes didn't work...

I'll trying booting with it on mouse mode
[M.O.J.O. Android Development] Unjustified Dev:
Have you tried switching USB ports?
[M.O.J.O. Android Development] gwaldo:
Ha, that could be it,

It should work without the dongle.. haven't tried.
[M.O.J.O. Android Development] gwaldo:
This is great, I'm going to try it out
[M.O.J.O. Android Development] Dimitris Dinozzo:
I flashed this recovery and then I wanted instalieren a rom, then I accidentally removed the HDMI cable, now I have no picture and no rom to boot only the recovery, how can I boot the recovery now? :crying::crying:
[M.O.J.O. Android Development] Unjustified Dev:
Plug in the USB then power and it will be in fastboot next just fast boot boot the image
[M.O.J.O. Android Development] 2k1197:
HELP

So after wiping the android tv software from my mojo so that I could install cm12 my internal storage had been wiped for some reason, I am unable to transfer any rom over to the mojo as sd card & usb storage does not work on the current twrp recovery...I have no OS to boot into please advise? I can get into recovery via fastboot but that's about it..if someone can fix usb or sd card storage I should be able to fix my mojo.
[M.O.J.O. Android Development] Unjustified Dev:
Sdcard works just fine for me I am unsure why you can not transfer the file. Enabling usb storage would break adb connection in recovery you should be able to side load a zip.

Sent from my LGMS395
[M.O.J.O. Android Development] Harry44:
I haven't used my Mojo in a while now. So happy when I just saw this. Thank you for your hard work.
[M.O.J.O. Android Development] Harry44:
For some reason it wont boot into recovery, just shows no signal on the tv.
[M.O.J.O. Android Development] HUYI:
in the same boat and i'm fked, sd card, usb drives, micro sd, nothing works so i can't install anything on the mojo, how did you get to recovery from fastboot? i've tried this command;

fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img

but it just says write error, man i'm peeved right now, there must be a way to install a rom somehow.
[M.O.J.O. Android Development] gwaldo:
RE: no signal on the tv.

Plug a usb keyboard, wait for the blue light to come on the MOJO and give it 1m.

Make sure the keyboard has lights (caps/num etc).

Then hold down LEFT ALT together with PTRSCN and hit the i key once.

It will display.

Also, recovery doesn't work on my TV, I have to use a PC monitor.

If the keyboard trick doesn't work, try a monitor.

I wrote about this from the start, so it's not new :rolleyes:

---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------

You can't brick the MOJO, it will ALWAYS going into fastboot mode.

Does being peeved stop you from google'ing how to use fastboot?
[M.O.J.O. Android Development] HUYI:
i've spent the past 6 hours trying to get into recovery on my mojo, so believe me i've tried, i was hoping people from here would have some expert advice on what to do in my situation, telling me the obvious is not helping at all.
[M.O.J.O. Android Development] gwaldo:
maybe watching 'two girls and a cup' will lift your spirit:cool:
[M.O.J.O. Android Development] HUYI:
maybe you should stop dancing around like a chimpanzee with a teapot on your head and posting random crap that doesn't make any sense or is very helpful.
[M.O.J.O. Android Development] shpitz461:
Got my MoJo today, bought it on sale from woot.

Was able to upgrade the OS to build 0205 by using a USB stick.

The console came with a male A to male A usb, and it works on the USB 2.0 port.

flashed TWRP per instructions, already created a nandroid :)

Thanks OP for all you've done!

Questions:

1. Every time I want to boot into recovery I need to issue the boot command above? can't issue adb commands?

2. Should I flash TWRP 2.8.7.0?

3. Is USB storage supported in TWRP? No option to mount usb storage that I can see, only SD. The USB stick I'm using is available and works great when running android.
[M.O.J.O. Android Development] Unjustified Dev:
1. Yes, you would need to fastboot boot unless you install an app that allows you to boot in recovery they exist.

2. Twrp 2.8.7.0 is nice but it has a few issues installing ROMs such as Remix OS.

3. USB storage is not supported in recovery to do so I would have to disable adb. the MOJO's ports don't allow adb and storage at the same time. I felt adb was more important.
[M.O.J.O. Android Development] shpitz461:
Thanks for the info!

So adb can only be used while in recovery? When the OS is running, the MoJo is not detected at all as a USB device.
[M.O.J.O. Android Development] Unjustified Dev:
Wireless adb is enabled. Same issue if you want adb in ROM then there will be no USB storage support.

To use

adb connect ipaddress
[M.O.J.O. Android Development] shpitz461:
Ah, gotcha, thanks, makes sense now!
[M.O.J.O. Android Development] HECTORdroid:
Sorry friend, hiceel score the 2 videos ( Installation and Review) leaving the ROM on your link original accommodation and referring to XDA d { forum andole you the crédit it deserves in style as it is you who we maniene live our MOJO console :good:
[M.O.J.O. Android Development] TwistyTravster:
What types of issues exist? I installed Remix OS without a problem... unless there is something and I'm unaware of it yet.
[M.O.J.O. Android Development] greevedogg:
HOT D@MN! I get my MOJO in the mail on Monday...Chomping at the bit to get OS Remix up and running! Thanks, Unjustified for all your hard work!
[M.O.J.O. Android Development] jinsta:
Is there any way to get help with under 10posts - think i bricked my remix rom. I need to get into TWRP again to flash back to my stock image, but my boot currently goes from the remix logo to blank screen. i can move the cursor on screen but remains black.

I can get connected via usb, but dont know what cmd prompt txt will make the mojo boot twrp. i've tried the mentioned on the instructions but dont work :(
[M.O.J.O. Android Development] TwistyTravster:
You'll be happily surprised that it it almost impossible to brick the MOJO. I'm guessing you used the towelroot way to boot into recovery the first time? And it obviously wont work because the MOJO wont boot into anything? I'll do my best to explain the USB way in a simple way to revert back to the Mad Catz stock android.

You will need:

- USB to USB cable

- HDMI cable

- MOJO plugged in with USB and HDMI at the same time

- MoDaCo Mod zip

- TWRP Recovery image

- Mojo stock firmware (see below for download) saved to microSD card inside the MOJO

First start by having your MOJO plugged into the PC with a USB to USB cable, and plugged into the AC power, as well as a TV all at the same time. When you plug the power into your MOJO, while the USB cable is plugged into the PC, it will show a black screen on the TV with text that says "Key driver not found... booting OS", and it will stay at that screen.

Next, you need to have the MoDaCo Mod unzipped into a folder, preferably directly in your C:/ folder for simplicity. Open a command prompt window as Administrator and navigate to the folder called r3-mojo-superboom-mmm.

Command prompt should show this:

C:\r3-mojo-superboom-mmm

Once there, you need to enter these commands in order:

After that, the MOJO screen should say "Booting downloaded image" for a split second before booting into the TWRP recovery. You need to go into WIPE, and check the boxes for Dalvik Cache, System, Cache, and Data. Then slide to wipe. Next go back to the Home screen and go into INSTALL. You will need to navigate through the folders to find the mojo-signed-ota-MO0205-TS (download here) zip file on your microSD card and select it. Then you need to slide to confirm flash. Next step is to reboot the system and it should boot into the Stock Mad Catz version of Android.
[M.O.J.O. Android Development] maverixz:
Hell good people, I forgot to install root when I was installing the Cm 12.1 Rom and I am wondering if anyone know how to boot into the TWRP recovery. The reboot apps I have all require root.
[M.O.J.O. Android Development] Unjustified Dev:
Enable root from developer options
[M.O.J.O. Android Development] jinsta:
Thank You TwistyTravster! I followed the instructions to the t. think i was trying to be clever with sub folders etc and it wasn't giving me desired result. everything to c: as per instructions and its gets me back into twrp :) thanks for the stock image too as my original backup didnt seem to work so that got me going and back into stock mode!

With me new found confidence, i went back to twrp, wiped and tried to get the 'remix' rom installed. Process on twrp went fine...but the rom itself after reboot is just hanging on boot screen with flashing 'remix os'. I dont think its actually booting.....think i'm destined to stay on stock firmware :(
[M.O.J.O. Android Development] maverixz:
Thanks for your response UD, your help with developing ROMS for this device is the reason I got the MOJOs. :good: