ezterry's kernel triggering gapps upgrade after every reset - Acer Iconia Tab A100

I installed ezterry's kernel on my rooted/unlocked a100 (stock ICS) and now every time I restart, I get a message that Google is upgrading before I get to my home screen. It's a minor quirk, just wondering if there's a way to stop it from doing that. I've tried wiping the gapps data via the settings menu, titanium backup, and cleared cache/dalvik in recovery, no dice.

xda_rulz said:
I installed ezterry's kernel on my rooted/unlocked a100 (stock ICS) and now every time I restart, I get a message that Google is upgrading before I get to my home screen. It's a minor quirk, just wondering if there's a way to stop it from doing that.
Click to expand...
Click to collapse
This would do better in his release thread....but anyways it usually subsides on its own. Reboot it a couple times in a row without installing any apps.
You can also clear cache and dalvik in recovery, which should be done every flash anyways, it will force it again then should stop unless its needed again.
Tapatalked from my Galaxy S II - CM10

Sorry, I tried posting there, but I realized I'm still categorized as a new user (I'm mostly a lurker). And thanks, I'll try your suggestion! :fingers-crossed:

xda_rulz said:
Sorry, I tried posting there, but I realized I'm still categorized as a new user (I'm mostly a lurker). And thanks, I'll try your suggestion! :fingers-crossed:
Click to expand...
Click to collapse
Oh yeah forgot the 10+ post rule for dev lol
Tapatalked from my Galaxy S II - CM10

Okay, I rebooted into recovery and cleared cache/dalvik again, then did a full reboot 5 times (I let it set a few minutes between each reboot). Still keeps saying "Android is upgrading". Any other suggestions?

xda_rulz said:
Okay, I rebooted into recovery and cleared cache/dalvik again, then did a full reboot 5 times (I let it set a few minutes between each reboot). Still keeps saying "Android is upgrading". Any other suggestions?
Click to expand...
Click to collapse
You could restore the stock kernel and see if it goes away, then try to reinstall ez's kernel.

I've seen the kernel cause this before when I was doing his test builds, it always eventually subsided on it's own over a couple of days, other then being a longer boot time it doesn't cause any adverse issues.
If you have a backup from CWM or TWRP, what he's referring to is an advanced restore:
CWM: (this is from memory)
Go to back/restore
go to backup
go to advanced backup (it may be in the same menu as backup)
uncheck everything except Boot, don't restore anything else
restore
clear cache /dalvik cache
reboot
TWRP:
Go to restore
uncheck everything except Boot
restore
clear cache / dalvik cache
reboot

I'll give it a couple days to see if it subsides on its own and then try the recovery if it doesn't. Thanks for the help, guys! :good:

Related

CM7 Stuck in Bootloop

Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn

acer ring from flex reaper rom, questions

So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?
trevor7428 said:
So i just flashed this rom. and everything worked fine including the ring. So after, i flashed diff mods and colors for the acer ring and also the fix (that was updated 6/2/12 i believe?
then after taking some screen shots. a pop up said,
system ui has stopped unexpecticly. or something like that.
and now the botton in the center is gone. So i cant use it at all.
Checked settings and it is enabled.
What should i do to fix? just reflash any acer ring or just the fix. or just flash the hole rom again?
Click to expand...
Click to collapse
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.
pio_masaki said:
Reboot into recovery then wipe cache, dalvik, fix permissions then reboot check the ring.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ya. i got it working again.
i get nervous going into recovery to flash something. i already bricked my transformer tf300 last week. but i got it back up and running. i just get scared. I'm gunna do a noob mistake and permently brick one of my devices.
but i didnt wipe anything. i rebooted, but it was still gone, went in settings unchecked, checked acer ring, rebooted again then it was back
btw do you no how to change bookmarks in acer ring. too ur google/ chrome bookmarks instead of the stock ones?
I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.
pio_masaki said:
I haven't noticed a way it seems to only show the stock browser, import them into the stock browser should put them on the ring too. Also delete from the stock any you don't want.
Huge edit: forgot to mention, any changes like flashing rings or mods etc. Should be followed by cache and dalvik wipe, and maybe fix permissions. That way old info is wiped so the new info can settle instead of it finding new info where it expects old info...make sense?
Flashing is fine provided you know what you're doing. Don't just do random things and you'll be OK. Only flash for your device, and mods meant for your rom, like the stuff civato posts for his FR rom. Recovery is safe as long as you use common sense and caution. If you don't know what something does, don't use it. Google it or ask, better to wait and know then guess and brick.
Generally always safe to do is wipe cache dalvik fix permissions. No data loss that you see occurs.
Safe if something broke and won't boot BUT you lose apps and settings is wipe data/ factory reset, done with wipe cache and dalvik and maybe fix permissions.
Wiping system wipes out android and you must flash a new rom or restore to boot into the system, and is always done with cache dalvik and data.
I strongly advise against partitioning from recovery if possible. If you must partition your SD card then use a PC tool not recovery. Don't initiate sd-ext wipes directly, if it happens on resets that's fine just don't do it by itself. I only mention this because on my phone we had a string of bricks due to bad recovery mapping and it was nuking our loaders instead. Stick to what I said and you're safe in recovery and flashing. I'm sure others can chime in with more info on this too.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?
trevor7428 said:
i thanked you for your last post i feel i owe you more thanks than replies you made specifically to me lol. yah i had no idea you had to wipe cache and dalvik and fix permissions. when flashing the acer ring. i thought only do that on roms. thats probably why my acer ring was giving me problems. havn't had one problem with it since i wiped.
but just to clarify, do you wipe cache/ dalvik before or after you flash (Acer ring for example) or both?
Click to expand...
Click to collapse
Either or. Some say before flashing some say after. I do before and after but that's just because of my scripts doing it before I flash (full rom). Something like the ring I flash then wipe cache dalvik fix perms after, so any of the mods etc that are not rom installs. Full rom installs I full wipe before then flash everything then clear cache and dalvik. I only fix perms if I get FCs.
Tapatalked from my Galaxy S II.

Problems with latest CM10 nightly

Need a little help here... Been on CM 10 from the beginning on my TMobile s3 with no problems. After I downloaded the 8-18-12 nightly my phone will not get past the android setup screen?? Anyone else having this issues and what can I do about this? Thanks!!
I just installed it and it works fine so far. Try another wipe and install. Or maybe your download is bad.
CM 10 nightly issues
sswb27 said:
I just installed it and it works fine so far. Try another wipe and install. Or maybe your download is bad.
Click to expand...
Click to collapse
Tried nightly download from cyanogen site & rom mgr. to no avail?? My rom mgr is updated, did full wipes and no luck. Reverted back to 8-14 with no issues. Haven't heard anyone else having this issue and I've never had any issues downloading CM before?? Weird. Thanks for the info.
sswb27 said:
I just installed it and it works fine so far. Try another wipe and install. Or maybe your download is bad.
Click to expand...
Click to collapse
First time I installed it, it worked out fine but there was a few minor issues like camera won't upload pictures and videos to facebook, Unable to update status. I decided to flash it again but this time I wiped dalvik 3x cache and data 2x format system cache data 2x each. After doing that everything worked out fine.
ak4life23 said:
First time I installed it, it worked out fine but there was a few minor issues like camera won't upload pictures and videos to facebook, Unable to update status. I decided to flash it again but this time I wiped dalvik 3x cache and data 2x format system cache data 2x each. After doing that everything worked out fine.
Click to expand...
Click to collapse
Yes, I had the same problem. It seems to work sometimes, sometimes not. Just do the 3 types of wipes, and try again- it should work.
One hint: during the installation of the ROM when it says "unleashing the evil"- it should take a good 20 seconds (or so) to "unleash". On the installations that failed for me it said "unleashing the evil" and immediately finished installing- and then the boot after that failed too....
Wipe 3x's?
jon.s.nelson said:
Yes, I had the same problem. It seems to work sometimes, sometimes not. Just do the 3 types of wipes, and try again- it should work.
One hint: during the installation of the ROM when it says "unleashing the evil"- it should take a good 20 seconds (or so) to "unleash". On the installations that failed for me it said "unleashing the evil" and immediately finished installing- and then the boot after that failed too....
Click to expand...
Click to collapse
Thanks for all the info. This morning I tried the download again from ROM mgr. and it worked fine Didn't do anything different but it worked!! Also, when you say wipe 3 x's, how do you do this? I installed today from ROM mgr. and it pops up to wipe and I check all boxes. After install is complete it auto boots into new build. Should I go back to recovery and wipe again or?? Thanks again.
Since I used the recovery to wipe, I was taking about wiping the 1) user data (factory re set), 2) the cache, and 3) the dalvik cache. If you're using the ROM manager, I'm sure what you did was fine. Truth is, I don't think all of the 3 wipes I did are always necessary especially if you're just upgrading from a previous build... Good luck!
Sent from my SGH-T999 using xda app-developers app
jon.s.nelson said:
Since I used the recovery to wipe, I was taking about wiping the 1) user data (factory re set), 2) the cache, and 3) the dalvik cache. If you're using the ROM manager, I'm sure what you did was fine. Truth is, I don't think all of the 3 wipes I did are always necessary especially if you're just upgrading from a previous build... Good luck!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Went ahead and booted into recovery and did the wipes again anyway. Seems to be working great.
I had that problem last night.
What I did was go into Clockwork and installed google apps. Then rebooted and it went through the setup without any problem.
Thanks Cyanogen & Crew
Just wanted to say thanks to all that works on CM 10. I'm running the 9-6-12 nightly on My mobile Beastly S3 & we are very close to stable! Thanks for all your hard work.

[Q] CWM wipe does not work?

Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Runge2970 said:
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Click to expand...
Click to collapse
flash twrp recovery via fastboot
simms22 said:
flash twrp recovery via fastboot
Click to expand...
Click to collapse
okay, just did. Tried the wipe and cleat options on that, but whit same results...
Runge2970 said:
okay, just did. Tried the wipe and cleat options on that, but whit same results...
Click to expand...
Click to collapse
are you wiping data(factory reset) or are you just wiping your dalvik and cache?
Runge2970 said:
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Click to expand...
Click to collapse
OK do what simms22 has explained. That should work.
But from what I am interpreting is that you are doing cache not wipe. So you go to "wipe data/factory reset" menu and hit/press yes. It should wipe it and done. BTW it might have been in a boot loop because you might of dirty flashed or you didn't wipe cache and dalvik cache. That is very important to remember. Never dirty flash and also wipe cache and dalvik cache.
Also did you play with tweaks and such before this was happening. Like voltage or over clock because that could be the problem too.
Dalvik cache and cache are hash signed by the last rom that was flashed. New rom, new hash sign. No need to wipe caches, just data.
Sent from my i9250
Cwm is notorious for failed wipes.
Definitely upgrade to twrp, and if your phone is so messed up twrp can't wipe it, use the android revolution wipe script.
Sent from my Galaxy Nexus using xda premium
If you're backed up and don't mind losing EVERYTHING, yes, EVERYTHING in /data, then boot into fastboot mode and run
Code:
fastboot erase userdata
from your computer. (Might need root privileges if running on Linux)
Hi guys. I got it to work finally. I didt some tweaking whit the DPI. Maybe that was the cause of the crash ??
But i went to use the Galaxy Nexus toolkit, first of all to flash the other recovery program. But since it dint work either i flashed it whit sock rom, from the same toolkit at started all over. That did work, but hell of a way to go

Tried flashing Moon ROM, can't get past TWRP

Step by step:
1. Cleared data, cache, dalvik. Flashed Moon ROM, went through the install, it installed, rebooted, couldn't get past splash screen.
2. Pulled battery, cleared data, cache, dalvik and rebooted, stuck on the same splash screen.
3. Repeated step #1.
4. Cleared system. Now when I try to reboot I get "Your device does not appear to be rooted. Install SuperSU Now? This will root your device." Answering yes or no to this just reboots it to TWRP.
tl;dr So right now I can't get past TWRP.
Hotwir3 said:
Step by step:
1. Cleared data, cache, dalvik. Flashed Moon ROM, went through the install, it installed, rebooted, couldn't get past splash screen.
2. Pulled battery, cleared data, cache, dalvik and rebooted, stuck on the same splash screen.
3. Repeated step #1.
4. Cleared system. Now when I try to reboot I get "Your device does not appear to be rooted. Install SuperSU Now? This will root your device." Answering yes or no to this just reboots it to TWRP.
tl;dr So right now I can't get past TWRP.
Click to expand...
Click to collapse
Have you checked md5sum of the Rom?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
"The codes match!"
I'm tinkering around right now. I assume I still have root even though it thinks I don't....?
Fixed: I think it was because I selected a non-stock kernel... Not sure. I also unchecked all of the additional "tweaks" it asked if I was interested in.
Hotwir3 said:
Fixed: I think it was because I selected a non-stock kernel... Not sure. I also unchecked all of the additional "tweaks" it asked if I was interested in.
Click to expand...
Click to collapse
Glad to hear its fixed
suggest you to change the thread title as [Fixed] that should avoid us to come in and check

Categories

Resources