Running cm10 official 9-13 with latest ktkernal. Had the problem last few flashes of official nightlys. Happened with both clean and dirty flashes. Reflashed gapps doing cache ans dalvik wipes after and before when one didnt work. Any idea?
Have you made sure you flashed the correct version of Gapps for your device and Rom?
Yes using cm10 so flashed signed gapps-jb-7/26
Sent from my SCH-I535 using xda app-developers app
What I'm thinking, is maybe the latest nightly has a bug in which it force closes the app. In which case, you'd have to report it to the developer.
Unless I'm missing something.
Related
I usually download both the ROM zip and the gapps zip, reboot into recovery, clear cache and dalvik cache and then install the ROM and Gapps.
My question is should I reinstall Gapps after installing the ROM or will the Gapps that is already there from the previous installation suffice?
My rule of thumb. Always clean wipe. Never have issues of leftover junk. Resetting up a fresh ROM is better then discovering a huge bug due to dirty flashing
Sent from my SCH-I535 using Tapatalk 2
libbrichus said:
I usually download both the ROM zip and the gapps zip, reboot into recovery, clear cache and dalvik cache and then install the ROM and Gapps.
My question is should I reinstall Gapps after installing the ROM or will the Gapps that is already there from the previous installation suffice?
Click to expand...
Click to collapse
As the CM10 nightlies install include a format of /system (which is where the gapps package installs), I'd say it's required. It certainly doesn't hurt to reinstall gapps after installing any AOSP rom (they may or may not format /system) and I don't think any will ever contain the google apps.
edit: flumoxed. Tested this with a format /system, install CM10, boot, no gmail, reboot, install gapps, reboot, gmail there, reboot, re-install CM10, reboot... gmail there. It sticks. Doesn't compute with the format command I see in the CM10 updater-script (along with a backup script of some sort). Will have to do some more testing. Still think it's best to always reinstall gapps.
hopesrequiem said:
My rule of thumb. Always clean wipe. Never have issues of leftover junk. Resetting up a fresh ROM is better then discovering a huge bug due to dirty flashing
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The problem with that is - I upgrade nightlies every couple of days and don't want to reinstall everything and make changes to my settings everytime I do it. Is there a one-click shortcut to restore everything if I clean wipe and install?
Go backup or titanium backup will get most things back for you painlessly.
On the contrary I've been dirty flashing cm10 nightlies for 3 weeks without reflashing gapps and I've experienced no issues so it's perfectly feasible but ymmv
Sent from my SCH-I535 using xda app-developers app
toddley said:
Go backup or titanium backup will get most things back for you painlessly.
On the contrary I've been dirty flashing cm10 nightlies for 3 weeks without reflashing gapps and I've experienced no issues so it's perfectly feasible but ymmv
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You're one of the very few then. The majority of problems in the official thread are people who have dirty flashed and when they finally do a clean wipe - problem solved.
This never used to happen until a month ago or so but any of the CM10 nightly install fine (I am using the right gapps). Any how I do a full wipe install and upon boot all the Google apps modules keyboard, media etc start force closing. Anything I am missing here this seemed to start happening middle Sept with any nightly I have tried installing. Thanks for any help with this!
Sent from my HTC One XL using Tapatalk 2
pfriederichs said:
This never used to happen until a month ago or so but any of the CM10 nightly install fine (I am using the right gapps). Any how I do a full wipe install and upon boot all the Google apps modules keyboard, media etc start force closing. Anything I am missing here this seemed to start happening middle Sept with any nightly I have tried installing. Thanks for any help with this!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Have you been re flashing gapps with each nightly? Also what version of gapps are you using, just to be sure.
Sent from my One X using xda premium
stnguyen09 said:
Have you been re flashing gapps with each nightly? Also what version of gapps are you using, just to be sure.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I have used gapps-jb-20121011-signed stright from goomanager and also the Cyanogen link (wiki) for CM10 -- this started around the middle of September (I dont recall the exact date to be honest). I am not installing ontop of its-self I am doing a fresh install (cache, dalvik, factory reset, system wipe, etc) in TWRP.
When I do a new install (each time doing a full wipe) all of the gapps start crashing when the phone boots up the 1st time...
I just dont know what else to try here honestly and hope I can find an answer!
pfriederichs said:
I have used gapps-jb-20121011-signed stright from goomanager and also the Cyanogen link (wiki) for CM10 -- this started around the middle of September (I dont recall the exact date to be honest). I am not installing ontop of its-self I am doing a fresh install (cache, dalvik, factory reset, system wipe, etc) in TWRP.
When I do a new install (each time doing a full wipe) all of the gapps start crashing when the phone boots up the 1st time...
I just dont know what else to try here honestly and hope I can find an answer!
Click to expand...
Click to collapse
just reinstall the gapps package
rohan32 said:
just reinstall the gapps package
Click to expand...
Click to collapse
Actually Rohan something else is going on here -- even if I dont install the GAPP package at 1st I get things like NFC force closing on boot. The really strange thing is I installed AOKP release 4 and it does not have this problem -- it installs fine it boots fine it has given me no errors like the CM10 nightly's have (great work btw).
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
StayingSober said:
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
Click to expand...
Click to collapse
What kernels did you flashed? And with what ROM?
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
jmxc23 said:
What kernels did you flashed? And with what ROM?
Click to expand...
Click to collapse
Basically tried flashing any compatible kernel with the ROM I was running at the time. For example yesterday I tried flashing the KT747 kernel for Jellybean with the current ROM I'm running, which is the most recent Liquidsmooth 4.2.2 ROM. Still no success
Here is the latest liquid...
Nightly Builds 04/29/13 for d2att, d2spr, d2tmo, and d2vzw available on GooInsideMe
http://goo.im/devs/liquidsmooth/nightly/042913 These Builds Are Very STABLE!
View changes & bug fixes made to our source code here http://github.com/LiquidSmooth
This is quoted from liquid0624 in the liquid smooth thread.
Sent from my SCH-I535 using xda app-developers app
redKrome said:
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry for taking forever to reply, I originally posted this on my lunch break and am finally out of work to reply freely. Anyways, I tried what you said, and downloaded the BMS 3.4 kernel that states is compatible with the version of Liquidsmooth 4.2.2 I am running. Let's just say I yet again had to restore twice once because it did exactly what I stated above, where it gives me the splash screen saying it's running the custom kernel and doesn't boot any further after the Galaxy S3 screen. The first time, I flashed it and then wiped cache/dalvik and fixed permissions before booting up like everyone says you need to do after flashing a kernel, no success.
Then, I read in the kernel's thread that there is no need to do that for this most up to date release, it says you just have to flash the kernel and reboot like with any other zip file. Well that didn't work either, and was forced to restore a backup a second time! What could the problem be?! I'm using the most updated version of TWRP, I'm on the most updated nightly of the Liquidsmooth ROM, I'm using a highly confirmed working and compatible kernel, and following the directions to the T! When it comes to flashing a different ROM, modem, rpm, backup, etc. I have no problem whatsoever. But trying to flash a kernel has never been successful for me so far
Any help from anyone else? It's frustrating that I've never been able to flash any kernels to any ROM I've ever run
Sent from my Samsung SCH-I535 running Liquidsmooth 4.2.2
Im no expert on any of this but this is what i would do. Odin back to stock ROM and reroot and unlock bootloader. Id do this cause i would want a clean slate so i know there is no previous kernel/rom files that may be effecting something. Make a new nandroid backup then reflash the rom ya want to use. Once booted up and everything is running, restart the phone and boot into recovery. Wipe the dalvik and cache like normal then flash the kernel. Hopefully that would take care of the problem.
Only other thing i can think of is to maybe wipe data/factory reset like 2 or 3 times and wipe the caches again and reinstall your current rom. Then flash the kernel. Other than that im out of ideas. Hopefully someone can get your problem solved!
Sent from my SCH-I535 using xda premium
I have couple of question and need some help. With the new AOKP nightlies being release every 3 days or so, I would like to stay updated on them. So when I download them and proceed to update and flash over the old nightly. (Wipe Cache, Wipe Dalvik Cache) Upon reboot everything is gone icluding Gapps and seems that it instead of just updating the rom and keeping everything, It updates everything and wipes clean as if it was a fresh flash instead of a update flash ("Dirty flash"). Does anybody know why this happens? Is it that with the AOKP nightlies, you just have to always do a clean install and flash?
MichaelDrakeMS said:
I have couple of question and need some help. With the new AOKP nightlies being release every 3 days or so, I would like to stay updated on them. So when I download them and proceed to update and flash over the old nightly. (Wipe Cache, Wipe Dalvik Cache) Upon reboot everything is gone icluding Gapps and seems that it instead of just updating the rom and keeping everything, It updates everything and wipes clean as if it was a fresh flash instead of a update flash ("Dirty flash"). Does anybody know why this happens? Is it that with the AOKP nightlies, you just have to always do a clean install and flash?
Click to expand...
Click to collapse
When I do this it causes my keyboard to f/c but my apps are still there
Sent from my Galaxy Nexus using xda app-developers app
dustinhayes93 said:
When I do this it causes my keyboard to f/c but my apps are still there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can see why the keyboard won't work. That might be due to having to re install Gapps. But I don't understand why every time I update to the new nightlies, all my stuff is gone and it's like a full wipe fresh install/flash. Does anybody know how to avoid this from happening? Or is it that AOKP nightlies won't allow these types of updates.
I don't think there is a way around this. I've been using aokp for awhile and i just keep all my apps backed up so i can restore them after install.
Okay. Thank you for the help.
Sent from my One X using xda app-developers app
My brother just got himself a skyrocket he's on the newest radio w/custom recovery installed but can't seem to flash anything but cm 10.1 with an old 4.2 GApps package.
Kinda frustrating because I haven't seen anyone else having this issue in any other thread. I did to his all I did to mine and I'm running Wantowan2's DU. Just says installation failed and we can't even flash other recovery from within recovery. Where should we go from here
Sent from my SGH-I727 using xda app-developers app
Odin back to stock and start over. Something got messed up in your recovery
Make sure you've got the proper recovery for 4.3 as well.
Sent from my SGH-I727
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
K
Boot_Derran said:
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
The gapps isn't right for 4.3, cm 10.1. Flash the 8-13-2013 gapps
Edit, you can find it on the OP of this http://forum.xda-developers.com/showthread.php?p=46685423
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Boot_Derran said:
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What is the exact error message that TWRP is giving?
Gotta wait for my bro to get off work but will post as soon as I can get his phone and give it another go
Sent from my SAMSUNG-SGH-I727 using xda app-developers app