X
Tap here to go to the mobile version of the site.

Support Forum

My moto g is inaccessible after installing FF OS 2.5 dev preview. Help

Posted

I cannot believe you don't provide a tutorial on how to uninstall the preview. I installed the FF OS 2.5 dev preview on my Moto G 3rd gen. I made a mistake, I selected choose to open the Preview "Always" rather than "Just Once". I tried to uninstall the Preview in order to re-install and correct the initial mistake. I cannot recover my Android Home screen. I used General Settings to Force Stop FF OS 2.5, now I get a black screen when I unlock the screen from reboot. The Uninstall button is grayed out in Settings. Please help me recover Android Lollipop 5.1.1, and uninstall FF OS 2.5 Dev Preview. ASAP

I cannot believe you don't provide a tutorial on how to uninstall the preview. I installed the FF OS 2.5 dev preview on my Moto G 3rd gen. I made a mistake, I selected choose to open the Preview "Always" rather than "Just Once". I tried to uninstall the Preview in order to re-install and correct the initial mistake. I cannot recover my Android Home screen. I used General Settings to Force Stop FF OS 2.5, now I get a black screen when I unlock the screen from reboot. The Uninstall button is grayed out in Settings. Please help me recover Android Lollipop 5.1.1, and uninstall FF OS 2.5 Dev Preview. ASAP

Additional System Details

Application

  • User Agent: Mozilla/5.0 (X11; Linux i686; rv:41.0) Gecko/20100101 Firefox/41.0

More Information

jesobreira 7 solutions 51 answers

Hi, krobix!

I'm sorry for the inconvenience.

Are your developer settings and USB debugging enabled now?

Can you access settings by clicking the Configurations icon on the notification screen of your device, open "Applications", choose the Firefox OS launcher and click "Clear defaults"?

If you can't get into settings, could you try opening Google Play on your computer and installing a new ROM on your phone from there, like Google Now Launcher, to be able to access settings and uninstall it?

If you can't do any of these things, could you try booting into the recovery and cleaning Dalvik cache?

This shall not make you lose any data, but to avoid any problem, please backup your data to your computer before trying it.

Hi, krobix! I'm sorry for the inconvenience. Are your developer settings and USB debugging enabled now? Can you access settings by clicking the Configurations icon on the notification screen of your device, open "Applications", choose the Firefox OS launcher and click "Clear defaults"? If you can't get into settings, could you try opening [http://play.google.com Google Play] on your computer and installing a new ROM on your phone from there, like Google Now Launcher, to be able to access settings and uninstall it? If you can't do any of these things, could you try booting into the recovery and cleaning Dalvik cache? This shall not make you lose any data, but to avoid any problem, please backup your data to your computer before trying it.

Modified by jesobreira

Question owner

I tried everything from Android recovery, including cleaning the cache. I don't know what the Dalvik cache is. Your response to my serious problem was not forthcoming so I did a full wipe and factory reset. Took about 3 hours to get to a stopping point, because Moto G is only stock Android with very few OEM amenities, requiring much installing from Google Play. I will eventually root this device because it has a major handicap that it will not output audio in mono. Apple, Samsung, and LG ouput audio in mono, but stock Android doesn't have a Stereo-Mono switch, even though a mono stream is probably available in ALSA without necessitating downmixing stereo to mono.

If you cannot give me a satisfactory explanation for what happened to my Moto G when I ran your FF OS app, I will be very unlikely to try it again.

I tried everything from Android recovery, including cleaning the cache. I don't know what the Dalvik cache is. Your response to my serious problem was not forthcoming so I did a full wipe and factory reset. Took about 3 hours to get to a stopping point, because Moto G is only stock Android with very few OEM amenities, requiring much installing from Google Play. I will eventually root this device because it has a major handicap that it will not output audio in mono. Apple, Samsung, and LG ouput audio in mono, but stock Android doesn't have a Stereo-Mono switch, even though a mono stream is probably available in ALSA without necessitating downmixing stereo to mono. If you cannot give me a satisfactory explanation for what happened to my Moto G when I ran your FF OS app, I will be very unlikely to try it again.
jesobreira 7 solutions 51 answers

krobix said

I tried everything from Android recovery, including cleaning the cache. I don't know what the Dalvik cache is. Your response to my serious problem was not forthcoming so I did a full wipe and factory reset. Took about 3 hours to get to a stopping point, because Moto G is only stock Android with very few OEM amenities, requiring much installing from Google Play. I will eventually root this device because it has a major handicap that it will not output audio in mono. Apple, Samsung, and LG ouput audio in mono, but stock Android doesn't have a Stereo-Mono switch, even though a mono stream is probably available in ALSA without necessitating downmixing stereo to mono. If you cannot give me a satisfactory explanation for what happened to my Moto G when I ran your FF OS app, I will be very unlikely to try it again.

krobix, unfortunately this issue happens to other launchers as well. I've faced the same problem using Nova Launcher. At the time, I could solve it by uninstalling Nova through "adb", using my computer, but I had USB debugging enabled...

It seems like, due to some reason, the app data becomes corrupted and the launcher can't get to open. Android does not recognize whether the launcher is running fine or not.

After facing the same issue with this other launcher, I started using ways of prevention, so if it happens to me again, I will be able to get my phone back without wiping it. I suggest you to download and install AirDroid from Google Play, it's an Android device manager. It allows you to uninstall apps using your computer (Google Play also allowed uninstalling apps in the past, but it does not work anymore), so if it happens again with Firefox OS or any other launcher, you will can login into AirDroid Web and uninstall the problematic launcher from your computer, remotely.

Unfortunately, as we have many devices to code for, and many different environment and circunstances, situations like yours are unpredictable. We do, however, our best to avoid these. Your problem was registered on the official repository, so that our developers will investigate it further to avoid it to happen in the future.

Our apologies, one more time, for the inconvenience.

''krobix [[#answer-806503|said]]'' <blockquote> I tried everything from Android recovery, including cleaning the cache. I don't know what the Dalvik cache is. Your response to my serious problem was not forthcoming so I did a full wipe and factory reset. Took about 3 hours to get to a stopping point, because Moto G is only stock Android with very few OEM amenities, requiring much installing from Google Play. I will eventually root this device because it has a major handicap that it will not output audio in mono. Apple, Samsung, and LG ouput audio in mono, but stock Android doesn't have a Stereo-Mono switch, even though a mono stream is probably available in ALSA without necessitating downmixing stereo to mono. If you cannot give me a satisfactory explanation for what happened to my Moto G when I ran your FF OS app, I will be very unlikely to try it again. </blockquote> krobix, unfortunately this issue happens to other launchers as well. I've faced the same problem using Nova Launcher. At the time, I could solve it by uninstalling Nova through "adb", using my computer, but I had USB debugging enabled... It seems like, due to some reason, the app data becomes corrupted and the launcher can't get to open. Android does not recognize whether the launcher is running fine or not. After facing the same issue with this other launcher, I started using ways of prevention, so if it happens to me again, I will be able to get my phone back without wiping it. I suggest you to download and install AirDroid from Google Play, it's an Android device manager. It allows you to uninstall apps using your computer (Google Play also allowed uninstalling apps in the past, but it does not work anymore), so if it happens again with Firefox OS or any other launcher, you will can login into AirDroid Web and uninstall the problematic launcher from your computer, remotely. Unfortunately, as we have many devices to code for, and many different environment and circunstances, situations like yours are unpredictable. We do, however, our best to avoid these. [https://github.com/fabricedesre/b2gdroid/issues/2 Your problem was registered] on the official repository, so that our developers will investigate it further to avoid it to happen in the future. Our apologies, one more time, for the inconvenience.

Modified by jesobreira