Asung415
Member
I had tried that after getting the "starting apps", which would result in the boot animation loop.I think TWRP has that. In advanced settings. Its called fix permissions.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I had tried that after getting the "starting apps", which would result in the boot animation loop.I think TWRP has that. In advanced settings. Its called fix permissions.
Does everyone that have cm11 working on their phones have the same phone as you?I had tried that after getting the "starting apps", which would result in the boot animation loop.
I'm not sure. I have the Canadian model, SM-G386W, Core LTE, they are basically the same phone, just re branded and sold in different regions.Does everyone that have cm11 working on their phones have the same phone as you?
It should work ur phone is the canadian version of the avant afyonltecan. Im gonna have to download ur stock rom to check it out.I'm not sure. I have the Canadian model, SM-G386W, Core LTE
Mine is the virgin mobile one. November 2014It should work ur phone is the canadian version of the avant afyonltecan. Im gonna have to download ur stock rom to check it out.
Well aware, but stock slim worked....Remember that he has the galaxy core lte not the avant which is probably why he is having problems that nobody else is having.
Actually the data you are referring to isn't generated until you boot into android. I almost always wipe both before and after flashing a rom and it has never once caused a problem for me. As long as you don't wipe system after flashing it isn't a problem.
Have you gotten any info from the build.prop i sent you?Okay will do.
i just wanted to check the ro.product.device and ro.product.nameHave you gotten any info from the build.prop i sent you?
You should start a new thread so when you get the bugs fixed you can let us know and push updates easier. Plus we could have some where to post bug reports after the obvious major ones are fixed.i just wanted to check the ro.product.device and ro.product.name
I'd argue not yet. I had thought about mentioning the same, but I'm not sure for how early it isYou should start a new thread so when you get the bugs fixed you can let us know and push updates easier. Plus we could have some where to post bug reports after the obvious major ones are fixed.
I think I reproduced the same result cause I restored to stock yesterday morning and when I got home I flashed cn11 and it wasn't booting staying stuck on cyanogenmod bootanimation. I had to wipe /system partition clean with adb within recovery. Try thisGot it installed and booted, but its stuck at android is upgrading "starting apps"
Sorry, but how do I go about sending the commands through adb? I'm a complete noob at this stuff.I think I reproduced the same result cause I restored to stock yesterday morning and when I got home I flashed cn11 and it wasn't booting staying stuck on cyanogenmod bootanimation. I had to wipe /system partition clean with adb within recovery. Try this
1. Boot into recovery
2. Connect phone to PC
3. Adb shell
4. Type " mount /system"
5. "cd /system"
6. "rm -rf *"
7. Then flash cm11
Those steps should fix your problem.
Are you on a Windows pc?Sorry, but how do I go about sending the commands through adb? I'm a complete noob at this stuff.
Yes.Are you on a Windows pc?
Any ideas about calling? If you need logs let me know which ones and I'll see about getting them to youTouchscreen bug is due to some missing files like tsdaemon wsdaemon and some firmware files i forgot to add. I adb pushed them to my phone and touchscreen is working perfectly
adb shell gives "error: closed", adb devices shows my device.I think I reproduced the same result cause I restored to stock yesterday morning and when I got home I flashed cn11 and it wasn't booting staying stuck on cyanogenmod bootanimation. I had to wipe /system partition clean with adb within recovery. Try this
1. Boot into recovery
2. Connect phone to PC
3. Adb shell
4. Type " mount /system"
5. "cd /system"
6. "rm -rf *"
7. Then flash cm11
Those steps should fix your problem.
That's what I meant, my bad.Whats wrong with calling .as far as i know calls can be made or received but theres no audio at all
Clear the data of the app? Or maybe completely uninstall and re-install?Ive encountered a weird error after restoring my stock rom. Everything works perfect how it did but for some reason my snapchat no longer sends pics, cant view videos or stories, but still sends text. Any ideas? Maybe fix permissions?