I've been looking for a few hours for an answer to this question, and I can't seem to figure it out. Sorry if it's already been answered and I just overlooked it.
I have flashed 3-4 different ICS/JB ROMs, and each time I flash the associated gapps, those apps simply do not appear when I boot up. Each time I flashed, I wiped 3 times, and the last time, I wiped everything but system, cleared the SD card, repartitioned it to ext4 - still nothing.
Anybody else had this problem? Any ideas on what I can do to fix it?
What Gapps are you using presently?
I'm running swiperrat's Baked Black Bean 2, and I used the gapps linked off that thread (http://forum.xda-developers.com/showthread.php?t=1836790). Right now, I'm using the inverted gapps 20121016 off of the Baked site. But, I have had the same problem with Mazwoz Evo 4.1.2 and TroNit's Provision port when I use the gapps recommended on those threads too.
Still haven't resolved this issue, but I did go to the market and d/l the usual google apps.
thetravatar said:
Still haven't resolved this issue, but I did go to the market and d/l the usual google apps.
Click to expand...
Click to collapse
Btw, I'm having the same issue in an entirely different platform and scenario: I have a OG DROID with Kfazz's ICS build based on CM9.
Naturally, I need a minimal build of Gapps for ICS because my RAM is only 256MB. Anyways, I've tried many different Gapps flashes. Always, the same deal...
The apps don't show up at all when I boot up, not even PlayStore
if you are using just a gapps flashable zip, try one of the aroma installers and select which parts of gapps you want to use and leave out the rest. hopefully that would do it, otherwise maybe a different recovery program.
firander said:
Btw, I'm having the same issue in an entirely different platform and scenario: I have a OG DROID with Kfazz's ICS build based on CM9.
Naturally, I need a minimal build of Gapps for ICS because my RAM is only 256MB. Anyways, I've tried many different Gapps flashes. Always, the same deal...
The apps don't show up at all when I boot up, not even PlayStore
Click to expand...
Click to collapse
Related
For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972
Hi.
I installed a custom ROM (CM10) yesterday but ever since then, when the screen is turned off, it will restart after about 1 minute. If I try to turn the screen on again before 1 min, it'll restart. In other words, when it goes to sleep, restart will be required. Please help me on solving this issue. I searched a lot and I thought maybe it has to do with the maximum CPU frequency, I tried changing it but didn't help.
Any ideas on how to solve this problem?
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
RE
Romman0 said:
What did you wipe during the install? And what ROM did you install?
Probably to start the best thing to do is redownload the rom, do a full wipe (cache, davlik cache, data, and system), then reflash the rom.
Click to expand...
Click to collapse
Thank you for the response.
Yes I did wipe the tablet (a full wipe as you mentioned) before flashing the ROM.
First I had tried Jellytime Sosei and when I realized the problem, I tried "Build 4 Linaro Stock" from this post but still the problem exists :/ Before installing the first ROM, I had done a full wipe, but not for the second one.
Thanks again for helping me.
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Its screaming bad install or bad settings, wipe twice then flash again, make sure to change nothing for speed, governor, io scheduler, and stock included kernel.
Don't even install an app for OC. It may be a huge bug showing for the first time, if we go carefully we'll find it, or get it going properly again. Occasionally the blackhole wipe used can clear up flash issues, but wipes internal sd as well.
Tapatalked from my HTC DNA
Thank you guys. I'll try what you said when I get home.
Romman0 said:
Try a full wipe to build 1 from the sosei thread, build 1 or 2 from the linaro thread, or the original cm10 thread. Those were the most stable for me. It's a weird issue, so it's probably a bad download or flash issue.
Click to expand...
Click to collapse
I'm gonna give those three that you said a try, when I get home. But, can you give me the link of the original CM10 thread that you're saying? I thought there isn't one for A100, since I didn't find it on their website. Is there a official CM10 ROM for A100?
There is no Official CM10 for the A100, Romman was referring to this link for the original CM10: http://forum.xda-developers.com/showthread.php?t=1792634
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
aminbandali said:
OK, after wiping everything twice and also wiping internal SD, I flashed "Build 2" from CM10 Unofficial Builds thread. Apparently this one doesn't have that bug and everything is fine, but the problem is that it's buggy and clock doesn't show well and when you press recent apps button, the overlay doesn't cover the bottom of the screen. So, I'm gonna try and flash Build 1 or maybe newer Builds and see what I get.
But is there a work around for the clock and other bugs problem in Build 2?
Click to expand...
Click to collapse
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
pio_masaki said:
There isn't one, no, but it was corrected in B4. I think. I'm building this stuff without the device so I can only go by reports. You're reporting issues that no one else has, is your device functional otherwise? Like is it ok on a stock Rom? Using the correct gapps, any other changes or mods?
Tapatalked from my HTC DNA
Click to expand...
Click to collapse
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
aminbandali said:
It was totally OK on the stock ROM and this never had happened, not even once.
I'm using the gapps that I got from your CM10 ROMs thread, which is apps for v 4.1.2. I haven't changed ANYTHING else in the tablet, no mods or customization at all... :/
P.S. I tried Build 4 again, this time I fully wiped everything before flashing, but again, the bug still exists. gonna try some other guys' ROM to see if the problem is with this ROM or it's from my device.
Click to expand...
Click to collapse
If its fine on stock then its gonna be Rom or kernel, just never heard of this happening before. What governor did you use?
Tapatalked from my HTC DNA
I've tried on 4, yes 4 different sprint galaxy s3's model sph-L710. I started with liquid smooth rc7, rc9 now liquidsmooth 4.2.2 and also carbonrom 1.4 and 1.5 and have tried every version on each of my 4 phones. I get the exact or very similar issues on every variant. The issue is the camera crashes, simply reboots the phone or I get an error message stating cannot connect to camera. I've tried different gapps, flashing and reflashing, camera and gallery apks from other model phones, installing the apks all different ways. I'm at my wits end and would sooo love to use either liquid smooth or carbon ROM as my primary phone, but no camera = useless ROM. Please provide any suggestions as I've got so many hours lost sleep and am now ready to either rip my hair out or throw in the towel on these ROMS, but I so don't want to do either.
I don't know if this is allowed but I'm willing to pay anyone who can fix my issue and have my camera run solidly on either liquid smooth or carbon ROM For 30 days. At whick point i will paypal or send a check for $100 to the individual who fixs the issue.
Zaileion said:
I've tried on 4, yes 4 different sprint galaxy s3's model sph-L710. I started with liquid smooth rc7, rc9 now liquidsmooth 4.2.2 and also carbonrom 1.4 and 1.5 and have tried every version on each of my 4 phones. I get the exact or very similar issues on every variant. The issue is the camera crashes, simply reboots the phone or I get an error message stating cannot connect to camera. I've tried different gapps, flashing and reflashing, camera and gallery apks from other model phones, installing the apks all different ways. I'm at my wits end and would sooo love to use either liquid smooth or carbon ROM as my primary phone, but no camera = useless ROM. Please provide any suggestions as I've got so many hours lost sleep and am now ready to either rip my hair out or throw in the towel on these ROMS, but I so don't want to do either.
I don't know if this is allowed but I'm willing to pay anyone who can fix my issue and have my camera run solidly on either liquid smooth or carbon ROM For 30 days. At whick point i will paypal or send a check for $100 to the individual who fixs the issue.
Click to expand...
Click to collapse
Well, if you're having issues, something you're doing is causing it to crash; when you install do you do it from a clean install?
If you want to use carbon / liquid smooth, I'd recommend flashing the rom with a full wipe, everything except in/external sd card, flashing a kernel if you choose; personally recommend kt747 kernel. If you need moar help, just pm me.
yes did ckean install same kernel
Yes, it was a clean wipe and install, and yes I use the k747 kernel. Like I said I've flashed dozens of ROMs on dozens of phones (for friends and family) and I'm an IT integrator by trade so I'm quite savvy.
Notable info:
If I wipe everything including delvik and flash new liquid smooth or carbon, and do NOT install any gapps the camera works perfectly every time... As soon as I flash the gapps the issue begins. Soooo Weird.
Zaileion said:
Yes, it was a clean wipe and install, and yes I use the k747 kernel. Like I said I've flashed dozens of ROMs on dozens of phones (for friends and family) and I'm an IT integrator by trade so I'm quite savvy.
Notable info:
If I wipe everything including delvik and flash new liquid smooth or carbon, and do NOT install any gapps the camera works perfectly every time... As soon as I flash the gapps the issue begins. Soooo Weird.
Click to expand...
Click to collapse
Go into gapps package remove camera/gallery included in gapps then flash gapps over clean install.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Here is another new and noteworthy discovery:
if i flash the gapps and do not sign into any google account or anything the camera works every time. immediately after i sign into a google account the camera/gallery screws up. What Gives!?!
edfunkycold said:
Go into gapps package remove camera/gallery included in gapps then flash gapps over clean install.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
i am currently waiting for the just released an hour ago, gapps to download, at which point i will extract, and remove any traces og camera/gallery i can find, zip the file and reinstall. followed by the available gallery2 flash-able zip file. and update you.
Thanks a million for the assistance weather it works or doesn't i am quite grateful.
edfunkycold said:
Go into gapps package remove camera/gallery included in gapps then flash gapps over clean install.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
well removing the camera/gallery from the gapps.zip file is proving more difficult that initially thought. I've extracted the file, searched for the following (gallery, gallery2, camera, camera2) and found only 3 gallery2.apk's files of which i deleted and re-compressed the file. installed and the camera remains, with no luck on resolving the issue. Curses! Curses!!
Any other suggestions... anyone... anyone...
also does anyone have any further details on how to remove any traces of camera/gallery from the gapps.zip file. I have done the above stated procedure but the camera remains. Note: there is no gallery or camera apk of any sort in the system/app file of the extracted gapps.
Don't extract the gapps, open them as an archive in 7zip then right click the app and delete then flash the gapps. Extraction can break the sig on the zip. There should only be 1 file named gallery.apk or gallery2.apk as the new aosp camera is integrated into the gallery apk
I like to break stuff!
I hate to create threads, but I haven't seen this issue anywhere. First, I know all phones are not created equal. But, they ought to be somewhere in the ballpark, I'd hope. Currently, I'm running Slim 4.2.2, 3.0-based, no problems. However, I wanted to try out a few different 3.4-based ROMS to see how unstable/stable they were and what they had to offer, as I'm sure Slim will be moving to 3.4 in the future. The problem is that I can only run CM10.1's newest nightly. I don't have any problems with that. Now, any other 3.4-based ROM causes all sorts of problems. This includes, but is not limited to, AOCP, Task's AOKP, and PA (all the newest versions as of today in the Development thread). What happens is when I flash - and I always wipe EVERYTHING except external SD... data, factory reset, cache/dalvik, internal SD, EVERYTHING - the phone boots, but as soon as it boots, everything starts crashing. I can't even get past the setup wizard. I've tried fixing permissions, reflashing over and over, different recoveries, you name it. I've tried different 3.4 kernels figuring it was kernel related. Same thing. Nearly every app on the thing starts crashing. Does this sound like a case where my phone just doesn't like the 3.4 bases yet? And if so, why no problems with CM? I'm not flashing anything besides the ROM base and the GAPPS. I'm just curious if anyone else is having these issues. I understand there's some problems with 3.4 at this time, but from what I've read in the threads, most people are able to boot and get things set up. Any help is appreciated.
Not at all sure if this is your problem but are you sure your using the right gapps package. Just a suggestion.
Sent from my SGH-I747 using xda premium
ragzdincs said:
Not at all sure if this is your problem but are you sure your using the right gapps package. Just a suggestion.
I appreciate the response! I'm actually back on TW for a bit. I was using the correct gapps, but I never actually verified my MD5's, so it's possible I just had a few bad downloads. Once things get straightened out with 3.4, I'll make the move back. I seem to be the only one with this particular problem, so it has to be either my phone or simply corrupt files. Thanks again for your help.
Click to expand...
Click to collapse
Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work