[Q] liquidsmooth rc9, with the recommended 20121212 singed gapp.
"unfortunately ** keyboard has stopped" keeps popping up. I have tried installing a new keyboard and setting it default, but it stops too.
After searching, I tried going to manage apps-keyboard and clearing data, and going to manage apps-dictionary and clearing data, which did not work.
I have done full wipe and install twice, which got the keyboard working on another install, but that is not working either....
full wipe with cwm-
factory data/reset 3x,
wipe cache 3x,
wipe dalvik cache 3x,
format sytem, data, and cache 3x each...!
Any other ideas? Can I manually delete something?
that version of gapps u are using may be the issue. I recall reading issues about incompatibility with the new 4.2 gapps? give 20120726 a try and see how u fair
icenight89 said:
that version of gapps u are using may be the issue. I recall reading issues about incompatibility with the new 4.2 gapps? give 20120726 a try and see how u fair
Click to expand...
Click to collapse
Thanks, I did try that I should have mentioned it.
I got slimbeam w/ slimgapps working, maybe I should try the slimgapps with liquid smooth??
I am also considering formatting the internal drive, and then installing the OS from Odin.
slimapps is based off the same gapps version I told u to try lol. that being said give it a go with liquidsmooth before u go giving yourself extra work with wiping internal and odi
icenight89 said:
slimapps is based off the same gapps version I told u to try lol.
Click to expand...
Click to collapse
Aha! Yeah I doubled checked, it is gapps-jb-20120726-signed.zip that I also tried...maybe I had not wiped it correctly when switching over. Also that was before I switched over to team recovery, which seems to wipe better.
Thanks again for the advice.
thanks button bro, and ur welcome :good:
Related
You can get it here:
http://download.cyanogenmod.com/?device=p999
Also, mirrored here:
http://www.multiupload.com/GPC6UIWZWT
Thanks CyanogenMod team!!!!
Do I install it with ROM Manager?
Thanks Cyanogen ModTeam
i haven't used a custom rom hehe i hope it fix some bugs like wifi etc
Well, hows it workin for everybody?
rroyter said:
Do I install it with ROM Manager?
Click to expand...
Click to collapse
Yup! It's flashable with ClockworkMod Recovery...just flash it like any other flashable ZIP.
Okay so I backed up the stock ROM, installed ROM from SD and said Wipe Data and Cache. It rebooted, I had to setup the google account again, but in the settings it still shows version 2.2.2. Maybe I should do a manual wipe?
rroyter said:
Okay so I backed up the stock ROM, installed ROM from SD and said Wipe Data and Cache. It rebooted, I had to setup the google account again, but in the settings it still shows version 2.2.2. Maybe I should do a manual wipe?
Click to expand...
Click to collapse
That auto wipe that pops up has never worked right for some reason. Do it manually when youre in recovery- wipe data, wipe cache, wipe dalvik cache.
also do the update through recovery manually.
I've only flashed roms after downloading them through Rom manager, never had to boot into recovery. Is there a good video anyone can recommend on how to do this?
Here's a link to the wiki to assist with installing.
HTH
Ok so I wiped it manually and installed the rom. Make sure you put the rom onto external SD partition because in recovery mode you wont be able to access the internal SD.
So far looks like the basic functionality is working. I had a lot of force closes and the reported battery voltage is wrong, shows 3mV instead of 3000. As for battery life I'll report back tomorrow.
Sent from my LG-P999 using XDA Premium App
My Wifi-Only US Xoom is rooted with the universal xoom root, and has the EOS-Wingray-60 Rom successfully installed, but everytime I try to download Gapps, this comes up:
How do I fix that?
EDIT: That is no longer the problem. Everytime I flash Gapps now, my xoom ALWAYS gets stuck on the dual core screen after reboot.
Double EDIT: I was too lazy to stock flash it, so I simply wiped everything again, downloaded EOS wingray 60, Then I wiped my cache and my dalvik (Not data), then reinstalled Gapps, and fixed permissions and it finally loads now. Thank ****ing god.
Can anyone help me with this please??
Slayergramp said:
Can anyone help me with this please??
Click to expand...
Click to collapse
Okay
1. Dont use v9 gapps you should always use latest v10.5 is the latest...
2. Check the md5 of the file
3. Wipe cache and dalvik cache
4. Install said gapps
5. Fix permissions
6. Win
Sent from my mind control device
Where's v10.5?
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Slayergramp said:
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Click to expand...
Click to collapse
Go to the eos rom.. There is a gapps link.. Click it and it will take you to all the gapps packages ... Download 10.5 check the md5
Sent from my mind control device
Goo-inside.me/roms/teameos/gapps
Download the most recent EOS gapps from there. The (bad) in your attempted install means the zip is corrupt.
Sent from my MB860 using xda premium
Alright, so my problem continues. I was running stock unrooted ICS, then flashes recovery. Then I wiped data, cache and dalvik. Then I rooted with the Xoom universal root. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, and flashes eos Rom 60. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, successfully installed gapps 10.5 for the first time, it wasn't (bad). Rebooted, andddd stuck. After I rebooted in permanately stuck on the dual core Motorola logo thing. What did I do wrong?
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
okantomi said:
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
Click to expand...
Click to collapse
When I flash them, is there anything I need to wipe or clear? Or do I leave everything alone?
God Dammit! This is pissing me off!!!!!!!!!!!!!!!!!!!!! It ****ing takes for ever to upgrade back to ICS when I have to flash the ****ing stock of 3.0!!!
I upgraded to ICS, after flashing 3.0, I flashed the R4c Recovery, I did a factory reset, and wiped Dalvik and Cache, then I installed the Universal root (Is there a different root I should use?), then I went back (Still in recovery mode) and did a factory reset, and wipe cache and dalvik. Then I install Wingray-60, then *immediately after* I installed Gapps v10.5!!!! I rebooted and my ****ING xoom is stuck on the dual core screen AGAIN!!!
WHAT THE ****.
Not quite sure what those first few steps were, but boot to recovery, go to mounts and storage and wipe system and cache, then go to the wipe menu and do a data wipe and dalvik wipe.
Then flash ICS and gapps.
Shouldn't have any problems after that unless your Xoom doesn't like ICS for some strange get reason.
Sent from my Xoom using xda premium
Hi, I recently rooted my LG Optimus Black (P970) and flashed the Surpressed ROM. Everything is working fine, but whenever I set the time to use network-provided values the clock goes to the wrong time.
Most of the researching I've done on this has pointed towards people not wiping the cache when flashing a new rom.
I wiped the cache and dlavik cache before flashing Surpressed V7, then flashed the updates immediately after (7.1, 7.2, 7.3, 7.5). I DID NOT wipe the cache before installing the updates, assuming it wasn't necessary because I literally flashed V7.0, rebooted, flashed the 7.1 update, rebooted, etc. until 7.5 was installed. Was it necessary for me to wipe the cache between updates?
I have wiped the cache and dlavik after installing 7.5, but that didn't solve my problem. Just wondering if anyone has thoughts about what I should do next. Should I wipe the caches and install 7.5 from the SD again? or do I have to do a factory wipe and restart at flashing 7.0, then flash the updates (wiping cache in between each)?
Thanks in advance for any help!
Most probably you do not need to reflash them all. If I am not mistaken every time you reboot the cache is build from scratch (that's why it takes some time to boot the first time). What you can do is to fix permissions to check whether it helps, then you can always try to reflash the last update and before and after you flash it wipe cache and dalvik cache. If you factory reset your mobile you will still be on the same last update. What it does is only removes the data not the system.
steven8590 said:
Most probably you do not need to reflash them all. If I am not mistaken every time you reboot the cache is build from scratch (that's why it takes some time to boot the first time). What you can do is to fix permissions to check whether it helps, then you can always try to reflash the last update and before and after you flash it wipe cache and dalvik cache. If you factory reset your mobile you will still be on the same last update. What it does is only removes the data not the system.
Click to expand...
Click to collapse
Thanks for the advice and clarification. Sorry, but what exactly do you mean by "fix permissions"?
srix9 said:
Thanks for the advice and clarification. Sorry, but what exactly do you mean by "fix permissions"?
Click to expand...
Click to collapse
Nevermind - just realized that this is a function in ROM Manager. I'll give it a try and see how it goes. If it doesn't work, I'll try wiping cache and flashing the latest update of Surpressed.
srix9 said:
Nevermind - just realized that this is a function in ROM Manager. I'll give it a try and see how it goes. If it doesn't work, I'll try wiping cache and flashing the latest update of Surpressed.
Click to expand...
Click to collapse
UPDATE - I fixed the permissions, rebooted, and so far after a couple hours of running the time seems to be staying correct. Thanks again for the suggestion stevens8590
srix9 said:
UPDATE - I fixed the permissions, rebooted, and so far after a couple hours of running the time seems to be staying correct. Thanks again for the suggestion stevens8590
Click to expand...
Click to collapse
And it looks like I spoke too soon. The clock is currently 3 hours 45 minutes behind the actual time. With it being off by that amount I would assume that it isn't a timezone issue. I will try wiping the cache/dlavik, reinstalling Surpressed 7.5, wiping cache/dlavik and rebooting. Will update on that once I have it running for a while. In the meantime, any other thoughts are more than welcomed!
Help, I'm slowing going out of my mind. I've been trying to figure out the problem but no joy here so far.
I think I've successfully upgraded to KissKat 4.3 from EOS 118 . Everything loads, asks me to set up tablet etc but I keep getting the " AOSP keyboard has stopped" so I can't actually finish the set up or see if I've actually upgraded properly.
I use TWRP 2.5 version, all the Gapps and version 20 from the 1st page. I've reflashed and rebooted many times changed the keyboard settings but ended up the same message. I also get the google text to speech has stopped as well and I've disable that as well.
Any suggestions would be appreciated. :good:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.
frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
GMTN said:
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.
Click to expand...
Click to collapse
LOL. I can tell you I've done that 4 different times with 4 different download all from the 1st page but it worked on this 4th and I'm not sure why.
Now to see tomorrow if this ROM lives up to all the troubles ( 3 hours worth ) and praise . Thanks for your guides by the way.
Glad it is sorted. I hope you find it worth your time.
So I'm running PAC ROM; I have a slight issue, I want stock GApps on my phone to add some features I've been wanting. When I flash it (tk_gapps-stock-5.1.1-20150809-signed.zip) on the official Nexus 5 lolipop ROM I got an error message, I read it and it says that I need to flash is ontop of another TK GApps, unless I wipe my cashe partition. So I wiped my Davlick Cashe and Cashe. Still have me the same message. Did I read it wrong? Any tips? Thanks
Hskom said:
So I'm running PAC ROM; I have a slight issue, I want stock GApps on my phone to add some features I've been wanting. When I flash it (tk_gapps-stock-5.1.1-20150809-signed.zip) on the official Nexus 5 lolipop ROM I got an error message, I read it and it says that I need to flash is ontop of another TK GApps, unless I wipe my cashe partition. So I wiped my Davlick Cashe and Cashe. Still have me the same message. Did I read it wrong? Any tips? Thanks
Click to expand...
Click to collapse
It's better to provide the error code provided by the log. When switching to another GApps package you should wipe /system partition.