Database Info

[Q] Gapps won't work {I have a picture :O}

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

[Q] liquidsmooth rc9 keyboard has stopped

[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:

TWRP 2.8.6.0 won't flash latest cm12.1 nightly

I'm trying to flash the latest /bacon nightly zip file on top of the stable cm12.1 with TWRP 2.8.6.0 and I'm getting an error that said cannot install this and advice me to do a factory reset instead. What do I do wrong?

bogdananglia said:
I'm trying to flash the latest /bacon nightly zip file on top of the stable cm12.1 with TWRP 2.8.6.0 and I'm getting an error that said cannot install this and advice me to do a factory reset instead. What do I do wrong?
Click to expand...
Click to collapse
What exactly are you trying to flash over the top of? When you say stable do you mean the stock ROM (Cyanogen OS 12.1)? If so, you can't do that, they're different ROMs. When going from the stock ROM to a nightly (or vice versa) you need to wipe properly (system, data, cache, dalvik cache) first.

Heisenberg said:
What exactly are you trying to flash over the top of? When you say stable do you mean the stock ROM (Cyanogen OS 12.1)? If so, you can't do that, they're different ROMs. When going from the stock ROM to a nightly (or vice versa) you need to wipe properly (system, data, cache, dalvik cache) first.
Click to expand...
Click to collapse
Thanks for the answer, this I was after.

Is clean flash really clean?

I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
1. So I first tried to uninstall that app with Rom Toolbox. Didn't help.
2. Then I cleared data and cache from Phone services. Didn't help.
3. Then I booted to recovery and wiped cache. No help.
4. Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
5. So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.

Yep, wiping everything is clean flash, or wipe everything but internal storage (if still problems, delete . Android folder beforehand).
Sent from my Pixel using XDA-Developers Legacy app

simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
for mw to be clean i would flash stock firmware then do the following procedure here
https://forum.xda-developers.com/tmobile-g4/development/turbo-cleaning-proceure-h811-t3417606

simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue

rob rich said:
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue
Click to expand...
Click to collapse
OK, thanks. Maybe in my step 4 above I thought that factory reset was enough but I didn't notice that it does not wipe system. So I went too far and wiped all my data, too.
But earlier when I have flashed different roms and they always tell that you must do clean flash, I didn't wipe system. So I thought clean flash was just factory reset. Still those different roms were working ok. Next time I try to remember wipe system also.

'There is an internal problem with your device...' error ) After Flashing Aosp Exten

Dear friends. I did a clean wipe with four wipe , didn't wipe vendor. And flash Aex latest rom. It shows that error 'there is an internal problem with your device contact your manufacturer for details' when it get setup (welcome) screen.
I can't solve that problem since a few days. Please say me how i solve it. Thanks for all.

Hi,
what was you previous rom?

zaqm said:
Hi,
what was you previous rom?
Click to expand...
Click to collapse
It was same Aex 6.1 . Is problem about vendors maybe?

Yes, they recommend a clean flash between roms because they are very different. Wipe System, Data, Cache, Dalvik and Vendor and flash the rom again - use latest official TWRP (3.2.3.1)