Database Users

[Q] cm10 on NC: No Android Keyboard message

I’ve installed cm10 on Nook Color running on SD card and it looks like it is working, however I cannot get android keyboard and get a message "Android Keyboard (aosk) has stopped"
Before this, I had cm7 installed on the card and it worked fine. I was able to revert back cm7 for now and again all is fine.
Any ideas?
thank you,
p

poluekt12 said:
I’ve installed cm10 on Nook Color running on SD card and it looks like it is working, however I cannot get android keyboard and get a message "Android Keyboard (aosk) has stopped"
Before this, I had cm7 installed on the card and it worked fine. I was able to revert back cm7 for now and again all is fine.
Any ideas?
thank you,
p
Click to expand...
Click to collapse
I'd been getting the same thing. I prefer Swiftkey anyways, so I froze the Android keyboard in TitaniumBackup and only have Swiftkey active. I was getting that message even when I had Swiftkey chosen as my default, freezing it stopped the messages. Not sure what to suggest if you don't have another keyboard installed.

poluekt12 said:
I’ve installed cm10 on Nook Color running on SD card and it looks like it is working, however I cannot get android keyboard and get a message "Android Keyboard (aosk) has stopped"
Before this, I had cm7 installed on the card and it worked fine. I was able to revert back cm7 for now and again all is fine.
Any ideas?
thank you,
p
Click to expand...
Click to collapse
Make sure you use GApps 20121011 for JB 4.1.x version. Android Keyboard should be AOSP.

hwong96 said:
Make sure you use GApps 20121011 for JB 4.1.x version. Android Keyboard should be AOSP.
Click to expand...
Click to collapse
I was using gapps-jb-20121130-signed.zip
seemed like a correct version to use. I'll try the you mentioned.
thank you,
p

poluekt12 said:
I was using gapps-jb-20121130-signed.zip
seemed like a correct version to use. I'll try the you mentioned.
thank you,
p
Click to expand...
Click to collapse
That version is for JB 4.2 which is for CM10.1 which is net yet available for NC.

hwong96 said:
That version is for JB 4.2 which is for CM10.1 which is net yet available for NC.
Click to expand...
Click to collapse
Thank you so much. Correct gapps fixed the problem.

Same issue, despite GApps for 10 (not 10.1)
I was running into the same issue (although most of the time, the message flashes on the screen and then quickly closes, but sometimes it sticks and I get to see the "Android Keyboard (AOSP) has stopped" message). And actually, originally I used the wrong GApps package, so I thought "oh! well then, this oughta fix it." And yet, despite now running gapps-jb-20121011-signed.zip (with cm-10-20121223-NIGHTLY-encore.zip) I'm still getting the issue . . . making it hard to fix up my family's unused Nook Color into a gaming/web-browsing tablet as a stocking stuffer!
I'm really just posting here to say that, after going into Recovery, running a reset, clearing the cache, installing the nightly and then installing GApps . . . it still didn't work. But having done so a third time, it finally did! Hah! So, for anyone else having the same issue, don't give up hope.

New update buggered my xoom - plz help

Hello,
I tried updating from wingray version 155 to 156. Downloaded it etc, done the usual, installed it, installed the latest version of gapps, it said it all went fine. However once it had loaded and optimised apps, I couldnt get past the lock screen. When i put my unlock combo in it just froze. Tried rebooting a few times with no luck, just kept freezing.
I have then tried to go back to version 155 but its getting stuck at the logo screen (i think its the eos logo, with 4 different colours)
Any help would be greatly appreciated, i really need to use my xoom tomorrow!
Thanks
Adam

adamski88 said:
Hello,
I tried updating from wingray version 155 to 156. Downloaded it etc, done the usual, installed it, installed the latest version of gapps, it said it all went fine. However once it had loaded and optimised apps, I couldnt get past the lock screen. When i put my unlock combo in it just froze. Tried rebooting a few times with no luck, just kept freezing.
I have then tried to go back to version 155 but its getting stuck at the logo screen (i think its the eos logo, with 4 different colours)
Any help would be greatly appreciated, i really need to use my xoom tomorrow!
Thanks
Adam
Click to expand...
Click to collapse
You might get more help, if you post your question in the ROM specific to your 155 nightly, thread.

if you update to 156 without wiping everything
you're gonna have a bad time

Mj, the thread is now closed.. Therefore I can't.
I cleared dalvik/cache like every other time I've updated. I know I have problems, I'm hoping for some solutions!!

Solution. Wipe data. Cache and davlik aren't enough for an OS change even if they might be sufficient for updates to the same ROM.

063_XOBX said:
Solution. Wipe data. Cache and davlik aren't enough for an OS change even if they might be sufficient for updates to the same ROM.
Click to expand...
Click to collapse
Thanks, wish I had of just left it now
Is it worth going to eos 4?

When you get it working again...
adamski88 said:
Thanks, wish I had of just left it now
Is it worth going to eos 4?
Click to expand...
Click to collapse
Another piece of advice... Once you get your device working again perform a NAND backup so you can recover easier next time? Nightlies are a great way to see new features and bug fixes but they are still Testing software..
And yes, EOS 4 is worth going to but it is a little slow right now... give the team a little time to optimize it.

[Q] UI Stopped

Hello everyone,
First of all, I would like to apologize for being dumb. I did a wrong thing.
I have the LG G2 for 2 weeks now and I rooted it, flashed a rom but when I wanted to restore all my files from Titanium Backup, it failed and all have dissapeared, inculing system files.
Now the device still works, but it appears an error message : Unfortunatly, UI stopped. I am not able anymore to go to my home sreen and I am locked. Could someone be kind enough to help susch a fool as I am ?
Thank you so much.
PS : Sorry for my bad English, it is not perfect.

NVHeartgrenade said:
Hello everyone,
First of all, I would like to apologize for being dumb. I did a wrong thing.
I have the LG G2 for 2 weeks now and I rooted it, flashed a rom but when I wanted to restore all my files from Titanium Backup, it failed and all have dissapeared, inculing system files.
Now the device still works, but it appears an error message : Unfortunatly, UI stopped. I am not able anymore to go to my home sreen and I am locked. Could someone be kind enough to help susch a fool as I am ?
Thank you so much.
PS : Sorry for my bad English, it is not perfect.
Click to expand...
Click to collapse
Edit : I fixed it on my own.

NVHeartgrenade said:
Edit : I fixed it on my own.
Click to expand...
Click to collapse
like to share how please?

surfed.tk said:
like to share how please?
Click to expand...
Click to collapse
I'm sorry, it seemed to work but it doesn't... A friend of mine which knows android well is trying to fix it... Unfortunatly, it still is a brick.

System UI
NVHeartgrenade said:
I'm sorry, it seemed to work but it doesn't... A friend of mine which knows android well is trying to fix it... Unfortunatly, it still is a brick.
Click to expand...
Click to collapse
mine works as long as i push OK as soon as that window pops up... the UI will load and all is good.
BUT, if i wait for a couple of seconds the screen becomes unresponsive to touch.
My System UI did not load after manual rooting but (maybe coincidence) the problem went to UI loading as long as I push OK right away after moving SU to system.

surfed.tk said:
mine works as long as i push OK as soon as that window pops up... the UI will load and all is good.
BUT, if i wait for a couple of seconds the screen becomes unresponsive to touch.
My System UI did not load after manual rooting but (maybe coincidence) the problem went to UI loading as long as I push OK right away after moving SU to system.
Click to expand...
Click to collapse
What happened to me was that I wiped everything with TWRP, even system files. Then I rebooted it and got all apps working except UI. A pop up opened and said "Unfortuntly UI stopped" ... At the moment the screen freezes on the LG logo as soon as I power it up. The only way to do something is to get into recovery mode and then TWRP appears but I can do nothing with it...

Fix for Infinite N4 Bootloop

I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome

YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?

If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.

Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app

Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..

boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out

HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here

Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....

YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057

I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.

Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.

Does anyone know what to do? There has to be a way to get a phone out of a soft brick..

YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014

22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol

22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...

Found a fix, check the forum page

[Q] Can't flash any lollipop ROM

having problems flashing a lollipop ROM. Ive never had any problems like these in the past, all other upgrades have gone smoothly
I am running into two problems. Either I will get stuck staring at a boot animation which never goes away, or I actually get through and all Google services go crazy and force close, with the google first time setup repeatedly trying to start and force closing itself so it is impossible to do anything on the phone.
The best I have done so far is flash a ROM without Gapps, but then for some reason I was not able to download any apks so there was no way to get the Play store on the phone.
If anyone could help me I'd appreciate it

brettzz said:
having problems flashing a lollipop ROM. Ive never had any problems like these in the past, all other upgrades have gone smoothly
I am running into two problems. Either I will get stuck staring at a boot animation which never goes away, or I actually get through and all Google services go crazy and force close, with the google first time setup repeatedly trying to start and force closing itself so it is impossible to do anything on the phone.
The best I have done so far is flash a ROM without Gapps, but then for some reason I was not able to download any apks so there was no way to get the Play store on the phone.
If anyone could help me I'd appreciate it
Click to expand...
Click to collapse
I was under exact same position. downloaded 2-3 lollipop rom, different size of gapps from diff sites same place.
solution is to flash factory image and everything works. now I am waiting for 5.1 OTA update and later try again few roms.
So best flash factory image as of now.

just as an update I tried a different kitkat rom and it went smoothly
not sure why lollipop is not working, one difference is when I reboot from recovery after flashing lollipop it tells me root may have been lost, and I get an option for 'yes, fix root' and it reboots.. when flashing kitkat didnt see that message it just rebooted

brettzz said:
just as an update I tried a different kitkat rom and it went smoothly
not sure why lollipop is not working, one difference is when I reboot from recovery after flashing lollipop it tells me root may have been lost, and I get an option for 'yes, fix root' and it reboots.. when flashing kitkat didnt see that message it just rebooted
Click to expand...
Click to collapse
What recovery and version are you using. You may have to update your recovery.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
What recovery and version are you using. You may have to update your recovery.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
hm looks like I was on a slightly outdated one I have updated and will see if this works now

brettzz said:
hm looks like I was on a slightly outdated one I have updated and will see if this works now
Click to expand...
Click to collapse
aha that did it
thank you very much!