I flashed my S5 with XtreStoLite and initially selected the option to use the Google keyboard. Now I want to go back to the Samsung keyboard with secondary symbols and I can't figure it out. I've literally spent a couple hours on this.
I figured out that I have to use Aroma to get the Samsung keyboard and re-flash XtreStoLite ROM to get the secondary symbols. The first part works (I get the Samsung keybord back), but when I add the symbols, it reverts back to the Google keyboard and the Samsung keyboard is uninstalled. I've tried wiping cache, not wiping cache, re-flashing ROM/Aroma with and without a reboot between, running Aroma first, re-flashing ROM first, etc. I always get the same result.
I guess my next step is a full wipe and restore, but I'm hoping there's an easier fix.
I've searched and could only find suggestions for things I've already tried.
Thanks.
Ok, I'm pretty confident this cannot be done -- I'd love to be proved wrong.
I wiped my device with the bootloader (wiped both caches too), installed XtreStoLite, selecting "add secondary symbols," then, without rebooting, installed the Samsung keyboard with Aroma. Then I rebooted and there are no secondary symbols on the Samsung keyboard. Went back, installed XtreStoLite agian -- without wiping device this time -- selected "add secondary symbols" and I'm back to the Google keyboard.
I think the "add secondary symbols" check box doesn't do anything because the XtreStoLite ROM deletes the Samsung keyboard and installs the Google one.
Oh well. I still like the ROM and the shortcuts on the keyboard, so I guess I'll live with it until/unless a fix comes out.
Related
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
JesseBeckett said:
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
Click to expand...
Click to collapse
Could be a long way off here, but are you sure the download wasn't corrupted, a statusbar and black screen sounds to me like the launcher wasn't opening, or wasn't flashed.
Also what version of CWM are you using? I would download rom manager and flash the latest version, then try flashing slim again.
JesseBeckett said:
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
Click to expand...
Click to collapse
First of all, the newest version of Slim Bean available for the S3 is 3.1, which you can download here:
http://www.slimroms.net/index.php/downloads/all/viewcategory/152-i9300
I would suggest doing a full wipe and installing this (much newer) version... I'm using it and it's awesome. Hope this helps.
Wrong section, post in QA
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I just completed a fresh Install of Slim Bean and Gapps based on the directions I found here: http://forum.xda-developers.com/showthread.php?t=2222626
CWM to wipe the system, then CWM to install Slim Bean and then Gapps. Reboot. After Slim Bean loaded up I got two messages, one that hung waiting for an ok: "Unfortunately Hangouts has stopped working." I assume this is google hangouts, honestly I don't know and probably don't care, but a prompt that flashes and instantly disappears reads: "Unfortunately android keyboard (AOSP) has stopped working."
Any time I try and type into a box this prompt either flashes the screen or pops up waiting for an okay. I've also noticed a light flashing when I'm in the novalauncher menu, the web browser blinks up and instantly closes(possibly because of the lack of wifi being connected, don't know), and that's about it on the problems list.
The last post on the thread, whose directions I followed exactly, is this:
jakaro
Senior Member
Thanks Meter 6
Posts: 127
Join Date: Jun 2010
my keyboard is force closing, and can't open aosp android keyboard at all
So this doesn't appear to be limited to me. Please help! I can't connect or do anything at all because I need the keyboard to get into the appstore. If someone knows of an app I could manually install that would fix this that would be lovely. This NT was previously rooted with cyanogen and I never had any trouble with the keyboard.
I haven't used that ROM but when I've had similar issues I have reflashed gApps. If it's still not working I've made a fresh download as well and when flashing again it has always worked for me. But like I said I haven't used this particular ROM.
Sent from my BNTV600 using Tapatalk 4
@RSomnambulist:
If your NT ran a different ROM before flashing Slimbean, you need to do a clean installation using CWM's "wipe /data & factory reset" and 'wipe cache".
digixmax said:
@RSomnambulist:
If your NT ran a different ROM before flashing Slimbean, you need to do a clean installation using CWM's "wipe /data & factory reset" and 'wipe cache".
Click to expand...
Click to collapse
Yep, like I said I wiped everything with CWM, top to bottom. Data, cache, and system. I'll try reflashing gapps per asawi's suggestion and let you know the results.
Hey guys here at xda!!
I've got a little problem and i'd like to know if someone can help me fix it
So, yesterday i used Rom Toolbox to disable some receivers for some apps....nothing too special, i just disabled the ones i though weren't really needed for those apps....also some notification ones or at boot time ones i think (also i don't remember touching any startup apps because i already had handled those with startup manager free)....anyway: now reboot is stuck...at, well, reboot (bootanimation)...
Does anyone know how i can restore Rom Toolbox changes, or reenable all receivers from recovery?
Or something else which might help?
Unfortunately, i don't have either a recent nandroid nor a recent titanium backup. So switching roms would be a pain...
MY ROM: Foxhound 0.1 for Galaxy S3 based on stock 4.2.2 (kernel is stock) and i have xposed framework, just in case that might help:good:
I really appreciate your help guys! PEACE!
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
boomboomer said:
Reflash your rom, without a wipe, first. If you've broken the framework that will enable it to boot.
If you still can't boot due to a broken app then start in safe mode, uninstall the apps you changed then reboot.
Click to expand...
Click to collapse
thanks for the reply!
safe mode (which i had never even known existen on android) appears to not be working....i mean it keeps getting stuck at boot so who knows why,
i flashed the rom, rebooted, it booted (yay) and then the usual message popped up with "updating applications x out of x", and after having finished it appears to be stuck at the same message with "opening applications under way" (translation from italian). the title of the message is "updating/upgrading android os"...
i think i might be force to flash a new rom
This is my first post on this forum and I am nowhere near as tech savvy as most people on here, so I apologise in advance if anything I post sounds daft or if I have broken any forum rules which I have tried to follow.
I have a Galaxy S2 GT-I9100 which was on Android 4.1.2 and which I am trying to flash to Kitkat with limited success using Slim Sabre.
If I unzip Slim Sabre by itself the phone "works" - I can make calls use internet, text etc, but when I install gapps all I get is messages stating "the android process (name of process) has stopped" - the processes include keyboard, location, calendar and a couple of others. I've tried flashing different versions of gapps, as well as Slimkat but keep getting the same thing.
I would really appreciate it if someone can point me in the right direction as to what I need to do to get kitkat working on my phone.
Again, my apologies if I have forgotten to include information or breached any rules, and thanks in anticipation for any assistance.
The following is currently what I have on "about phone"
Android version: 4.4.2
Kernel version: 3.0.80+ [email protected] #1
Slim version: Slim-4.2.2.build.5-OFFICIAL-4068
Build number : slim_i9100-userdebug 4.4.2 KVT49L 4068 test-keys
Update
Just to update, after switching my phone off and on again, the only message now appearing is "android keyboard (AOSP) has stopped". I am not getting any of the other messages for some reason.
I've tried clearing data from Keyboard app as well as dictionary and also tried clearing the cache on both. The cache for the dictionary was at 12 kb and when I pressed the clear cache button nothing happened (though I did get haptic feedback so I know it was pressed).
I've also tried installing LatinIME.APK but it fails to install (I have allowed unknown sources).
Also tried fixin permissions.
I would really appeciate any help and guidance on this - I am very new to all this flashing and rom business as you might guess!
Many thanks
rk001 said:
Just to update, after switching my phone off and on again, the only message now appearing is "android keyboard (AOSP) has stopped". I am not getting any of the other messages for some reason.
I've tried clearing data from Keyboard app as well as dictionary and also tried clearing the cache on both. The cache for the dictionary was at 12 kb and when I pressed the clear cache button nothing happened (though I did get haptic feedback so I know it was pressed).
I've also tried installing LatinIME.APK but it fails to install (I have allowed unknown sources).
Also tried fixin permissions.
I would really appeciate any help and guidance on this - I am very new to all this flashing and rom business as you might guess!
Many thanks
Click to expand...
Click to collapse
Reboot to recovery and then Simply reflash the rom zip file once again without any wipe and see
Thanks for responding. Ive done as you said but still get the same thing.
Boot into recovery - wipe/factory reset.
Still no joy. Ive read that another cause is flashing the wrong version of android. Does the info ive put in my first post suggest this?
Really do appreciate the help being provided.
Just tried iWnn IME but get the same problem if that sheds any light
Umm... Gone quiet on here! Will it be worthwhile trying a new rom, kernel etc and see if that works or is the problem indicative that nothing will work?
Turns out I was using wrong version of gapps. Got the correct one now and all seems to be running OK. However Play is now telling me that Candy Crush is not compatible with my device but it was before. Any ideas what that is all about? I need it to keep me sane at work!!
Hey all
So after a botched Cyanogenmod install on my AT&T GS3, I am having some issues with the stock ROM. Here's what happened: I tried to install CM using the windows installer, everything went well until the end and then I got a prompt on the phone prior to it rebooting "Root access lost, fix? Yes/No". Regardless of choice, phone would always boot back to stock ROM. Asked for some advice on the CM forum and was told KNOX was the issue. I then rooted the phone using Towelroot, and then installed Super SU. Super SU when opened for the first time said KNOX was installed, did I want to disable it, I chose YES. Re-tried CM installer, same issue, just boots back to stock ROM.
At this point I gave up and just re-installed all my apps and settings, synched my Google account etc. Since then I can no longer download anything from any Google app, it just says "Download failed". So Gmail attachments, links, Chrome etc. nothing downloads. Although stock Internet downloads are fine. Swiftkey now errors saying "Cannot save language pack" then crashes, Swype keyboard keeps on re-enabling itself after I turn it off, and apps that worked fine before are crashing like crazy.
Last night I performed a wipe/factory reset after starting in recovery mode. This did not help. I also noticed that recovery mode boot screen is Cyanogenmod boot screen still, so guessing factory reset is not exactly a full factory reset and it just wipes data/cache etc.
Seems to me like some kind of permissions issue. I downloaded Root Explorer and had a poke around. Permissions look fine (read/write etc.) on Downloads folder. Only thing that looked odd was there are 3 different file system areas so 3 different downloads folders (ie sdcard0/0/Downloads, storage/0/downloads and storage/legacy/downloads). Not sure if that is normal.
Just want to put it back to how it was. Any suggestions what to do next?
Cheers.