AOSP Keyboard has stopped??? - AT&T, Rogers HTC One X, Telstra One XL

Ok, I did a system wipe, cleared the dalvik and cache, rebooted to fastboot flashed the stable cm10 rom, went back into recovery and flashed rom and flashed gapps. cleared cache and dalvik and rebooted. Everything works fine but i keep getting a warning that states "Unfortunately Android(AOSP) keyboard has stopped. Would Gapps have anything to do with this?

RC196 said:
Ok, I did a system wipe, cleared the dalvik and cache, rebooted to fastboot flashed the stable cm10 rom, went back into recovery and flashed rom and flashed gapps. cleared cache and dalvik and rebooted. Everything works fine but i keep getting a warning that states "Unfortunately Android(AOSP) keyboard has stopped. Would Gapps have anything to do with this?
Click to expand...
Click to collapse
What hboot are you on bro? If its the latest, you need to flash the boot img FIRST. Then go and wipe all cache types, system and factory reset. Then flash CM.
Sent from my One X using xda premium

ToxicWaste said:
What hboot are you on bro? If its the latest, you need to flash the boot img FIRST. Then go and wipe all cache types, system and factory reset. Then flash CM.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I did all that. Sorry didn't provide all of it in details. I guess its becaue of Gapps 4.2. I'm flashing an older version of gapps.

Yep that was the problem. I wiped everything and reflashed rom and older version of Gapps and problem solved.

Related

[Q] CM7 with gapps built in?

Hi all,
on my very first flash of CM7, I had to install gapps. All worked well and I was happy.
Since then, every time I flash CM7, I get gapps already installed (yes I wiped all, yes I cleared dalvik cache, I even did the lock/unlock thing in order to clear all data).
I somehow get the feeling that my flashes are not a "clean" install.
did anyone else experience this as well?
thanks...
On your first time on CM7, wipe everything, flash cm7, flash gapps. When you want to update cm7, jus wipe cache and dalvik, then flash the updated cm7. No need to reflash gapps, no need to do a full wipe either.... unless you want to.
-Nexus S
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
asafru said:
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
That's not what he meant. He meant that if you are upgrading CM7, you do not need a full wipe at all.
But after a full wipe your Gapsps should be gone. It's weird that it is still there after a wipe. :S
It's still there after a wipe... is there a way to make sure I full wipe correctly?
Sent from my Nexus S using XDA Premium App
asafru said:
It's still there after a wipe... is there a way to make sure I full wipe correctly?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Wipe Factory/Dalvik/Cache: Full Wipe
Wipe Factory: Removes Apps + Settings
Wipe Dalvik/Cache: Wipes the cache but your apps + settings remain.
Wiping factory will delete your Gapps.
Proper way to flash CM7:
1. Wipe Factory/Dalvik/Cache
2. Flash CM7
3. Flash Gapps
4. Flash Kernel (Optional)
5. Reboot
Proper way to upgrade
1. Wipe Dalvik/Cache (Optional)
2. Flash Kernel (Optional)
3. Flash CM7
3. Reboot
asafru said:
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Upgrading to newer versions will now keep all your data in tact, so gapps will be there etc.
great, I think it's all sorted out now.
just one question though, I've read that CWM dalvic cache wipe doesn't work. Is that true?
If so, what is the best way to wipe dalvic cache and do factory reset (fastboot/adb commands are also welcome..)
asafru said:
great, I think it's all sorted out now.
just one question though, I've read that CWM dalvic cache wipe doesn't work. Is that true?
If so, what is the best way to wipe dalvic cache and do factory reset (fastboot/adb commands are also welcome..)
Click to expand...
Click to collapse
It works. Somebody confirmed this, the error that pops up during CWR is SD EXT.
You can check for yourself, run a logcat (search the forum) while the phones booting.

[Q] what happens if i didnt wipe cache and delvik before updating cm10?

so i updated cm10 to a newer version and i didn't wipe anything i just flashed the zip file and everything booted up fine but now im worried that something may go wrong in the future can anyone help??
Boot to recovery and wipe cache and dalvik. Reboot and you should be good.
If you start getting issues, consider reflashing will all the wipes.
Sent from my Transformer using xda app-developers app

Can't install any roms?

Hey guys,
I'm on stock 4.4 with bricked kernel, but when I try to install any roms, I either get stuck on the boot screen or get bootlooped. I've tried several roms and kernels with every combination possible, and none work. For example, droidkang and elementalx 11.0->bootloop, droidkang and bricked -> bootloop, droidkang and chaos ->stuck on boot screen, cataclysm and chaos ->bootloop, catacalysm and bricked->stuck on boot screen, elemental and stock->bootloop, latest bricked and stock->bootloop. I've factory reset, wiped cache, wiped dalvik cache every single time I've flashed something new. I have absolutely no idea where I could possibly go wrong. Everything I flash either ends up in bootloop or gets stuck on the bootscreen. Does anyone have any ideas?
Why not try just flashing the ROM and rebooting with the included kernel, let it boot, then try flashing kernel?
sent from my HAMMERHEAD neXus
CRIME INC. said:
Why not try just flashing the ROM and rebooting with the included kernel, let it boot, then try flashing kernel?
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
Yea, I've tried that as well. I let droidkang boot once, then went back into recovery and flashed elementalx, and it bootlooped, so I restored my backup.
What exactly are you wiping before flashing kernel?
sent from my HAMMERHEAD neXus
---------- Post added at 02:05 PM ---------- Previous post was at 01:59 PM ----------
Reason I ask is, according to your post you're doing a factory reset before flashing the kernel, which isn't necessary. Cache and dalvik wipe are enough
sent from my HAMMERHEAD neXus
CRIME INC. said:
Why not try just flashing the ROM and rebooting with the included kernel, let it boot, then try flashing kernel?
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
CRIME INC. said:
What exactly are you wiping before flashing kernel?
sent from my HAMMERHEAD neXus
---------- Post added at 02:05 PM ---------- Previous post was at 01:59 PM ----------
Reason I ask is, according to your post you're doing a factory reset before flashing the kernel, which isn't necessary. Cache and dalvik wipe are enough
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
I factory reset, wipe cache, dalvik cache, before installing the rom, and let it boot, then I go back into recovery, wipe cache, dalvik cache, and install the kernel then reboot.
haloXgod117 said:
I factory reset, wipe cache, dalvik cache, before installing the rom, and let it boot, then I go back into recovery, wipe cache, dalvik cache, and install the kernel then reboot.
Click to expand...
Click to collapse
When you say stuck on boot screen how long do you wait? First boot is the longest<10 min. Do standard wipe flash ROM gapps reboot. Setup ROM reboot recovery flash kernel no wipe. Make sure kernel is compatible with ROM.
Sent from my Nexus 5 using Tapatalk
full wipe: data, cache, dalvik, system.
haloXgod117 said:
Hey guys,
I'm on stock 4.4 with bricked kernel, but when I try to install any roms, I either get stuck on the boot screen or get bootlooped. I've tried several roms and kernels with every combination possible, and none work. For example, droidkang and elementalx 11.0->bootloop, droidkang and bricked -> bootloop, droidkang and chaos ->stuck on boot screen, cataclysm and chaos ->bootloop, catacalysm and bricked->stuck on boot screen, elemental and stock->bootloop, latest bricked and stock->bootloop. I've factory reset, wiped cache, wiped dalvik cache every single time I've flashed something new. I have absolutely no idea where I could possibly go wrong. Everything I flash either ends up in bootloop or gets stuck on the bootscreen. Does anyone have any ideas?
Click to expand...
Click to collapse
Before flashing a Rom do you wipe data, cache and dalvik first?
Sent from my Nexus 5 using Tapatalk

Can't Flash Any Other ROM But CyanogenMod 9.1!

Hi Guys. As my title shows I can't flash any other rom other than the official CyanogenMod 9.1. I do a full wipe of data, cache , and Dalvik Cache before I try a flash and as soon as I reboot I go into a bootloop. Any help would be great.
Boot to bootloader and write down everything from that screen
Boot to recovery and write down what version
Also name ROM you tried
Sent from my Nexus 4 using XDA Premium 4 mobile app
[email protected] said:
Hi Guys. As my title shows I can't flash any other rom other than the official CyanogenMod 9.1. I do a full wipe of data, cache , and Dalvik Cache before I try a flash and as soon as I reboot I go into a bootloop. Any help would be great.
Click to expand...
Click to collapse
Be sure to flash the boot.img, I currently have KitKatDS and any other rom will black screen on start up without first flashing.
Good Luck, Conner.
If not boot.img, your recovery may be out of date. Have you tried using one of these?
CWM: http://www.rootfiles.org/pub/mirror/silverl/cwm6046.img
TWRP: http://www.rootfiles.org/pub/mirror/silverl/twrp2630.img

[Q] Fixing A Messed Up Flash

So I flashed a custom ROM and did the usual steps. Install, wipe caches, etc., and the ROM itself loads. It's a custom 4.4.2 ROM for GT-P31XX and I used CWM 6.0.4.5 recovery to flash it. Problem is that when I boot, I get to the lock screen but System UI, Settings, and AOSP Keyboard always fail. I can't seem to boot into recovery any more but I want to install a different ROM or reinstall stock JB and start over. How would I go about fixing this situation?
Okay, I can boot into recovery actually.
KingMotion said:
Okay, I can boot into recovery actually.
Click to expand...
Click to collapse
Did you wipe everything first then install? Because you want to wipe, install, boot. Cache, dalvik, data, system are the main ones, always wipe these when flashing a new ROM.
Sent from my GT-P5110 using XDA Premium 4 mobile app

Categories

Resources