Hey guys I get "Android is Updating" "Optimizing Apps" Window on Every Boot, just for a Few Seconds, It didn't use to do this, has anyone experienced this, I'm Running Hydra-H2o ROM and Siyah Kernel?
UPDATE, SOLVED, Thanks to SoLoR1 for the "Fix"
SoLoR1 said:
I found out what caused this message for me... It was Titanium Backup odex file. So you can do two things, you can remove and then install again Titanium Backup or go in to /data/app and remove TB odex file and reboot phone....
Click to expand...
Click to collapse
Mine only does this when I install a new app to the /system directory and reboot. As you said it only lasts a few seconds, nothing to get worried about.
Chris.
Sounds like it's a boot animation.
OP, does the "Android is Upgrading" occur after the boot animation or as part of the boot animation? I doubt it is a boot animation as I have had it before, and it is standard, just not after every boot. Are you changing something in the /system/app directory or flashing a new mod? These would trigger an "Android is Upgrading" message.
Chris.
Some form of zip align/ optimise at boot
Check your roms specifications .
With 42 posts you can ask in the rom thread .
jje
It could be your cache or delvik cache is being cleared. Do you have something like a cleanup cache program running.
Sent from my GT-I9100 using Tapatalk 2
First I want to thank everyone for your prompt replies it's nice to see how helpful this community is!
themadba said:
Mine only does this when I install a new app to the /system directory and reboot. As you said it only lasts a few seconds, nothing to get worried about.
Chris.
Click to expand...
Click to collapse
It does it every time, I'm not worried I'm Annoyed LOL
ctomgee said:
Sounds like it's a boot animation.
Click to expand...
Click to collapse
it's not boot animation
themadba said:
OP, does the "Android is Upgrading" occur after the boot animation or as part of the boot animation? I doubt it is a boot animation as I have had it before, and it is standard, just not after every boot. Are you changing something in the /system/app directory or flashing a new mod? These would trigger an "Android is Upgrading" message.
Chris.
Click to expand...
Click to collapse
It ALWAYS occurs after, I've only changed the Launcher in system/app dir could that be it?
JJEgan said:
Some form of zip align/ optimise at boot
Check your roms specifications .
With 42 posts you can ask in the rom thread .
jje
Click to expand...
Click to collapse
Hydra-H2o is Zipaligned could that be it?
bored_stupid said:
It could be your cache or delvik cache is being cleared. Do you have something like a cleanup cache program running.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I've wiped all caches, it still does it...
Try to install ultimate kernel cleaning script before you flash the rom.
http://forum.xda-developers.com/showthread.php?t=1363738.
RGNDI said:
First I want to thank everyone for your prompt replies it's nice to see how helpful this community is!
It does it every time, I'm not worried I'm Annoyed LOL
it's not boot animation
It ALWAYS occurs after, I've only changed the Launcher in system/app dir could that be it?
Hydra-H2o is Zipaligned could that be it?
I've wiped all caches, it still does it...
Click to expand...
Click to collapse
Thats what im talking about, when I wipe cache/delvik cache and when I reboot, the phone as to rebuild the delvik cache, hence andriod is upgrading. Never did it under gingerbread but i think its par of the course for ICS.
Sent from my GT-I9100 using Tapatalk 2
davidsgs23 said:
Try to install ultimate kernel cleaning script before you flash the rom.
http://forum.xda-developers.com/showthread.php?t=1363738.
Click to expand...
Click to collapse
I have it and I've Used it , but will give it another try, now that Siyah 3.2.3 is out!
Tried it super script and flash new kernel, didn't work, will try when the new rom is out
Sent from my GT-I9100
It isn't the dalvik cache being rebuilt that causes the "Android is Upgrading" because I just wiped my davlik cache as a test, and just a longer boot animation. I see that Hydra H2O is also an AOKP based ROM, like HydrogenICS, so I don't know, depends on the build version. Anyway, nothing to get annoyed about either. Just post on the developer's thread and see if anyone else has the same problem. Also, it isn't kernel related because I use Siyah Kernel too.
Chris.
I have same issue.... on every boot i get "Android is upgrading" window with Starting applications, i dont get any Optimizing applications, just Starting... for a sec or two... Didnt find the solution yet i also went and reflash same rom over with no success, only thing i didnt do is format /data partition since i cant be bothered to install all apps again....
edit: i found this since im runing stock XWLP9 with siyah krnel it might be it... however im sure i didnt have it few days ago...
SoLoR1 said:
I have same issue.... on every boot i get "Android is upgrading" window with Starting applications, i dont get any Optimizing applications, just Starting... for a sec or two... Didnt find the solution yet i also went and reflash same rom over with no success, only thing i didnt do is format /data partition since i cant be bothered to install all apps again....
Click to expand...
Click to collapse
Just found this. It does including optimising applications, but I think it gets to the point. http://forum.xda-developers.com/showthread.php?t=1365133&highlight=upgrading
Chris.
The thing is it didn't do it when it I did the clean install, it did it after the phone was completely set up...
Had a good think about this. Back in the days when we were all on gingerbread. We would install a new firmware and have to wait 10-20 mins for first boot," building the delvik cache, etc ". Prompting some noobs to think they were in a bootloop and pull the battery. ICS boots faster after first install," building aplication list, delvik cache, etc", can remember it stopping have way through to ask for data roaming to be enabled. After that, whenever we clear cache/delvik cache then reboot, it has to rebuild cache again. Only this time as a Andriod is upgrading message.
Sent from my GT-I9100 using Tapatalk 2
I found out what caused this message for me... It was Titanium Backup odex file. So you can do two things, you can remove and then install again Titanium Backup or go in to /data/app and remove TB odex file and reboot phone....
SoLoR1 said:
I found out what caused this message for me... It was Titanium Backup odex file. So you can do two things, you can remove and then install again Titanium Backup or go in to /data/app and remove TB odex file and reboot phone....
Click to expand...
Click to collapse
Dude you rock, I had a hunch it could be Ti but never did actually do anything I uninstalled it and installed it again worked like a charm
SOLVED!
Sent from my GT-I9100
Just FYI : This can be caused by modified ODEX files (maybe you've used some sort of patcher to remove ads, etc...) Simply remove all the modified ODEX files and you're done.
cyber9940 said:
Just FYI : This can be caused by modified ODEX files (maybe you've used some sort of patcher to remove ads, etc...) Simply remove all the modified ODEX files and you're done.
Click to expand...
Click to collapse
Where do I find the ODEX files exactly?
I'm having the exact same problem - I get "Android is upgrading - starting applications" every time I boot my phone. I've got a Galaxy S I9000 running CM9 stable I haven't modified any ODEX files (not that I'm aware of). I just uninstalled Titanium Backup but I'm still getting the same message.
I tried to locate the ODEX files using ES File Explorer but I can't find them. More specifically, I can see all the .odex files for the system apps within the /system/apps folder (I don't think I should touch those though, right?) - but when I go to the /data/app folder to look for the user-installed apps, there are only .apk files in there and no .odex files at all. Are they kept somewhere else?
And if I do find where they are kept, then what? Should I just delete all of them? Is that safe?
Related
I don't believe Ive seen this mentioned anywhere yet, so I figured Id remind those who know, and inform the newbies who don't know.
Ive heard people who have applied various lag fixes complain that their phone slows down over time when opening apps. This "fix" i am about to mention is really easy and can help anyone not just those who have problems with an applied lag fix.
If you open Rom Manager and use Fix Permissions, wait for it to finish, then select Reboot to Recovery, and wipe Cache, and then go to Advanced Settings, and wipe dalvik cache, then reboot normally, your phone will hang at the Galaxy S bootscreen for a few minutes, it might take a while because it is rebuilding the dalvik cache, you should notice things running smoothly again and apps opening quicker.
Hope this helps anyone out there!
Does wiping those 2 cache's screw up installed apps? Where you have to download them all again?
Bronk93 said:
Does wiping those 2 cache's screw up installed apps? Where you have to download them all again?
Click to expand...
Click to collapse
No, wiping the caches shouldn't affect your installed apps.
And all the same, if you still worry about it, just run a nandroid backup before you wipe the caches, then if you run into any issues, just restore, or advanced-restore only your data partition.
cheers,
=)
~ Jocelyn
So not a big deal cause I have replaced my update.zip with the clock work reboot update.zip and can reach clockwork still by "reinstalling packages" but I tried this fix and now can't reboot into recovery straight to clockwork through rom manager cause it says something to the effect of
E: can't reboot cause file /cache/update.zip missing
(bad)
Click to expand...
Click to collapse
Not exact but obviously there was a vital cached update.zip that was used in order to reboot directly into clockwork through rom manager.... Any idea on a fix? Think it would be unwise to just reflash clockwork through rom manager again to recache the file? Would anything else be effected like possibly overwriting my past nand recoveries? Thanks guys/gals for any help on this one.
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
Bump for the safety of reflashing clockwork to replace cache file?
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
p()()pypants said:
Bump for the safety of reflashing clockwork to replace cache file?
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
Click to expand...
Click to collapse
yes, your missing the update.zip that unzipps itself to run clockwork. So yes flash the update.zip again through rom manager.
I just creates the update.zip file so it will not do any harm.
Awesome I assumed just as much but wanted confirmation first, thank you much
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
I've done this, and it worked just fine.
Thanks OP!
it worked perfectly, thanks
speedysilwady said:
I don't believe Ive seen this mentioned anywhere yet, so I figured Id remind those who know, and inform the newbies who don't know.
Ive heard people who have applied various lag fixes complain that their phone slows down over time when opening apps. This "fix" i am about to mention is really easy and can help anyone not just those who have problems with an applied lag fix.
If you open Rom Manager and use Fix Permissions, wait for it to finish, then select Reboot to Recovery, and wipe Cache, and then go to Advanced Settings, and wipe dalvik cache, then reboot normally, your phone will hang at the Galaxy S bootscreen for a few minutes, it might take a while because it is rebuilding the dalvik cache, you should notice things running smoothly again and apps opening quicker.
Hope this helps anyone out there!
Click to expand...
Click to collapse
Thank you! Am trying this now and will post any impressions after.
EDIT: Immediately after re-booting, it definitely seems smoother and snappier - thanks again for this. I was wondering if I should do something like this, but didn't know what, because I'd flashed Eugene's Vibrant6 and a lag fix and then restored to my pre-flash nandroid. I thought the phone's performance was suffering after all that, and I definitely found this tip helpful, so really appreciated!
READ AT THE END OF THIS POST FOR THE SOLUTION
I accidentally used Titanium Backup's widget to frost all system and user apps, leaving mi phone in a infinite boot animation loop. I dont have aNandroid Backup and I would really love to solve this issue without flashing.
I found at Titanium Backup's troubleshooting webpage that I could use this command with adb to solve my issue:
Code:
Type the following command (replace with /dbdata/system/packages.xml if you have a Samsung phone):
busybox sed -n 's/<package name="\([^"]\+\)".*enabled="false".*/\1/p' /data/system/packages.xml | while read PKG; do pm enable "$PKG"; done
but it just says: No such file or directory (yes, I changed /data to /dbdata as stated in the webpage)
Any idea on how to solve this issue?
Thank you!
**EDIT:
This is the way I managed to get my phone working again without having to flash or wipe:
1. Boot in recovery mode and used adb pull command to extract "packages.xml" and "packages-more-backup.xml" from /data/system/
2. Open both files with Wordpad and replaced all protection="2" or "3" lines to protection="1".
3. Also, and very important, replaced all enabled="false" lines to enabled="true"
4. Boot in recovery again and used adb to delete old "packages.xml" and "packages-more-backup.xml" files and push the new ones.
5. Reboot and Voila!
6. Boot once again in recovery mode and fix permissions to avoid any problem.
Hope that this could be usefull to someone else having this horrible problem.
Thank you all!
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
nitox.n2o said:
Checked for that file on my phone, it doesn't exist in /dbdata/system/, but it does in /data/system/
Click to expand...
Click to collapse
I tried with /data too but same result.
shadow65781 said:
It's probably fixable from the command line with Linux but that is over my head, one option would be to Odin or heimdel back to stock, and start from scratch. You might need a jig to get into dlmode.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I know I could do that but I would really like to restore my system as it was
Help please
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Simba501 said:
I wonder what would happen if you removed the app (its apk) via adb from /data/app. Would it retain the freeze settings? Something to consider trying.
Click to expand...
Click to collapse
Pretty sure that's not gonna work because the frozen apps settings are at packages.xml file, but I can't access it I don't know why
jhermit said:
This happened to me. I reflashed the ROM without wiping and all was back to normal
Sent from my FrankenTAB using Tapatalk
Click to expand...
Click to collapse
I tried doing that right now but it didn't worked
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
shokuchi said:
I got a little too punchy with titanium on my 3 year old original Galaxy tab 7 and froze a samsung system app. Got irreversibly stuck is soft brickland - Tried various methods before giving up and hitting the wipe and reset to factory restore in the system recovery mode. Everything was backed up except recent photos, so it was more annoying than the end of the world.
Odd thing was when it reset to factory, it appeared to do just that, yet when I plugged it into PC and mounted it - the memory was full and all my files and app data files were there - untouched. The apps themselves have gone except one - Superuser is still there, Does Superuser somehow override being reset? and act as a guardian of your data in the event of reset?
Odd. I was expecting to run some file recovery software to a salvage what i could, but viola - it was all there.
Click to expand...
Click to collapse
Wrong forum dude
Sent from my Zanpakuto using Getsuga Tensho!
<deleted>
ZIP for unfreezing apps
For those, who accidentally frozen important system app: here quick solution without factory reset, reflashing and ADB
It automatically edits files as described in first post.
You should have unlocked bootloader. If no, ZIP useless because unlocking wipes all data.
Download both ZIP's and just flash them via custom recovery (TWRP / CWM)
If first throws error try second and vice versa. 2nd with mark "New" contains newer updater-binary that must be compatible with recent TWRP.
Then all apps will be unfrozen, so phone will boot.
Fix compatible with all Android versions.
Note: also you can somehow (ADB or filemanager in TWRP) delete file /data/system/0/package-restrictions.xml
More correct to edit that file which ZIP actually do, but deleting not harmful too.
tags: unfroze apps, auto-unfroze, defrost apps, unfreeze apps, 5596
Bonoboo said:
For those, who accidentally frozen system app there is quicker solution without factory reset and ADB.
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen.
Compatible with all Android versions.
Click to expand...
Click to collapse
THANKS MAN!! i just signed up to say thanks! you just saved my life :highfive:
Bonoboo said:
For those, who accidentally frozen system app here quicker solution without factory reset and ADB
It automatically edits files as described in first post.
Just flash this ZIP through recovery and all apps will be unfrozen, so phone will boot.
Compatible with all Android versions.
tags: unfroze apps, auto-unfroze
Click to expand...
Click to collapse
Thanks very much for the zip. It worked great
Same Problem
Does anyone have an updated version of that zip? I also froze an app linked to the device and it won't boot, even after factory resetting it. Tried running the zip on my t-mobile GS4 (probably newer than that zip) from the SD card in recovery mode, however it didn't unfreeze it.
Any help greatly appreciated!
pianoplayer55 said:
Does anyone have an updated version of that zip?
I also froze an app linked to the device and it won't boot, even after factory resetting it.
Click to expand...
Click to collapse
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Bonoboo said:
1. To flash that ZIP you need have custom recovery (CWM or TWRP), not stock.
No update needed, it still works in this case.
2. That strange. Maybe you not really performed reset?
Double check all and try again.
Click to expand...
Click to collapse
Yup, unfortunately I did select wipe data on the recovery screen. I am also stuck in an infinite boot up loop and cannot access the phone to install any apps. How can I use a custom recovery to run the zip file if i cannot access the phone? Instructions much appreciated. Thanks again.
pianoplayer55 said:
How can I use a custom recovery to run the zip file if i cannot access the phone?
Click to expand...
Click to collapse
ZIP – it's not app.
Again, you need to install custom recovery.
Here link to TWRP and how install it via Odin on PC.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Bonoboo said:
ZIP – it's not app.
Again, you need to install custom recovery.
You need place that ZIP on sdcard.
Enter in recovery (don't know how on your model), select Install > find ZIP > confirm > reboot,
Click to expand...
Click to collapse
Downloaded TWRP with Odin and ran custom recovery without a change after the zip (this must have been a deeper-rooted problem in the OS itself), however in the meantime I formatted the system partition, removing the operating system. Installed Kies and ran the update. It reinstalled the OS and I'm good now. Most stuff was backed up anyways. Thanks guys for your time :good::good:
Which apk is the culprit?
Man, I wish I'd found this thread before restoring my phones internal ROM. Had it rooted and set up in every way I like except removing bloatware.
Using TB, I froze a system apk that shut down my System UI and sent the phone bootlooping. What I'm trying to determine is WHICH apk(s) I froze that caused this. I thought I had researched each one that didn't seem obvious, but I musta missed one or one of the 'obvious' ones wasn't so obvious.
For instance, I delete most of the notification and ringtones that come with a mod. In fact, I've deleted all of them. I've achieved this using Root Explorer with RW enabled.
But when I go into Settings > Sound > Ringtone\Notification, some names show up. I've tried deleting cache, etc. But no matter how many times I do this the names show up; even after restarting my phone.
2 vanished somehow, but I still have 1 left. Specifically it's called "Teleport". There's no real file and no sound to play from. So when I highlight it, it doesn't play, because I've deleted it. I just want the name gone. The nonexistent files don't show up in any music list or even in file manager such as Root Explorer.
It's been like this for a while. How can I fix this? Any apps, tricks or something?
CM7/S-Off
You could try unzipping the rom, removing unwanted files and then rezipping it.
ovar said:
You could try unzipping the rom, removing unwanted files and then rezipping it.
Click to expand...
Click to collapse
Wouldn't that usually mess with the MD5 sum and make it corrupt? I could do that, but I'd have to install the rom again over a factory reset.
Hayzie said:
Wouldn't that usually mess with the MD5 sum and make it corrupt? I could do that, but I'd have to install the rom again over a factory reset.
Click to expand...
Click to collapse
So don't unzip, use winrar and just delete the files
I suppose.
I think I'm going to update to the latest CM7 rom, as mine is months old. So I'll just do that for the new rom.
Just a few quick thoughts...Have u tried clearing dalvik cache in recovery? Also if u are flashing the same/similar ROM u may not need to do factory reset / wipe data. Though u may need to clear data for Media Storage (and possibly wipe dalvik) before flashing so it has to recreate it after flashing the new ROM.
Odd little problem u have there. Could be worth while to just flash a clean rom and try deleting the files to see if it still happens. Also, u could always delete them from rom before flashing and then try to only restore data from a backup. Kinda doubt that would work but if all else fails.....
Sent from my Little Engine That Could using XDA App
DocHoliday77 said:
Just a few quick thoughts...Have u tried clearing dalvik cache in recovery? Also if u are flashing the same/similar ROM u may not need to do factory reset / wipe data. Though u may need to clear data for Media Storage (and possibly wipe dalvik) before flashing so it has to recreate it after flashing the new ROM.
Odd little problem u have there. Could be worth while to just flash a clean rom and try deleting the files to see if it still happens. Also, u could always delete them from rom before flashing and then try to only restore data from a backup. Kinda doubt that would work but if all else fails.....
Sent from my Little Engine That Could using XDA App
Click to expand...
Click to collapse
Yes, sir (sir?). I have done that as well. No luck.
I deleted the ringtones/notifications in the latest CM7 RC2 released on May 9th before flashing on a full wipe and it worked, but unfortunately the rom kept freezing and restarting so I went back to my nandroid backup. No matter how many wipes and cleans I do on this, plus fixing persmissions etc, nothing works. It's no big deal, really. It just bothers me because I've got OCD and I refuse to believe it's there, therefore not allowing me to pick what I really want (maybe I'm stupid about it that way).
I'm just going to wait until there's a stable release and just start over from there by getting rid of the ringtone/notifications in the rar.
Thanks!
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
TeamRainless said:
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
Click to expand...
Click to collapse
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Wanamlite. Latest version. And I sure did...
TeamRainless said:
Wanamlite. Latest version. And I sure did...
Click to expand...
Click to collapse
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
TeamRainless said:
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
Click to expand...
Click to collapse
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
kilometers4 said:
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
TeamRainless said:
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
Click to expand...
Click to collapse
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
TeamRainless said:
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
Click to expand...
Click to collapse
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
kilometers4 said:
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
It absolutely was. But what did it do and how could I fix it?
Boy I'm not having great luck with my hardware atm. My Nexus 7 has got some serious lag issue, probably needing a factory restore, and now my SGS2 is playing up and looking like it might need the same. I'd appreciate the help before I go to that - not sure where I am on backups, I think this problem has been lingering for a while unnoticed, and its possible my scheduled Titanium task hasn't worked in a while because of this.
So let me run through. I was trying to update a few apps in the app store, and I got 'the package file is invalid' errors over and over. I was a little confused, and suddenly I was getting a flickering alert for 'low on application space' that would come and go.
I went into applications to see what my space was and it was fine, 400mb free. But I noticed that all of the apps were reading as zero size. I tried removing one I knew was big, and the free space adjusted by a real amount, but no change to the sizes in the listing. I went thru and uninstalled a bunch just to be sure. Even after this, I could still not install any apps without getting the invalid message.
I decided to restart and wipe the cache, thinking maybe something had gone wrong there. No change. All the installed apps were working ok, though, no problems running things. So, I decide that something minor has corrupted, and that a reflash of the current firmware would maybe do the job (which is a stock XEU build of ICS). I have 'Mobile Odin' and keep the current firmware file on the SD just in case. I of course want to run a backup first, so I fire up Titanium, which fails to do the backup, with an error about something catching fire trying to 'do calculation'. I begin to figure that something worse has happened by this point.
I decide to go ahead with the reflash using Mobile Odin. It seems to load fine, I tell it to wipe the cache and so on. The flash goes fine, and the phone reboots. I expected it to go through the little optimising applications thing it does, and true enough I see this box load up, saying 'start applications' and the spinning wheel. Then, it abruptly closes, and I get my home panel...
But here's where it goes severely wrong - every app I can think of now crashes, displaying the 'unfortunately XXX has stopped'. Boxes and boxes, for basically every app that in any way runs at startup, every widget, even my Swift Key and Swipe keyboards. Yikes! After clearing the huge backlog of boxes, I start trying to open stuff, and it quickly becomes apparent that no app will work, save for those that are physically part of the firmware (such as Settings, Messages, Phone, Contacts, Memo, Camera). Basically, unless its a stock app, it's just dead. My SD apps show up as if they aren't found, with the little grey SD box. I can't even open the Play Store to try redownloading an app.
I'm going to try, once I'm home from work, reflashing the firmware using desktop Odin. But, failing that, I will need a factory restore it would seem. Basically, I'm looking help either fixing the problem without a factory restore, or a way to back up my data (messages and app data) in case my Titanium Backups are old or broken.
Thanks :/
Edit: When I do a *#1234#, my CSC comes up as 'Unknown'. Would this cause these issues?
Boot into CWM recovery and fix permissions.
unclebob_2000 said:
Boot into CWM recovery and fix permissions.
Click to expand...
Click to collapse
I don't have CWM recovery installed. Will it be possible for me to install it with the phone in this state? Any reasons why the permissions will have gone like this?
gyaku_zuki said:
I don't have CWM recovery installed. Will it be possible for me to install it with the phone in this state? Any reasons why the permissions will have gone like this?
Click to expand...
Click to collapse
Flash a CF root kernel using desktop Odin, reboot into CWM via hard keys vol+ home and power. Find fix permissions, run it, reboot, hopefully work...
Most apps that aren't granted the right permissions that allow them to fulfil there main task will usually end up in a FC.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Flash a CF root kernel using desktop Odin, reboot into CWM via hard keys vol+ home and power. Find fix permissions, run it, reboot, hopefully work...
Most apps that aren't granted the right permissions that allow them to fulfil there main task will usually end up in a FC.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
The phone is already rooted. Can I apply CWM as an update.zip from inside the current recovery?
gyaku_zuki said:
The phone is already rooted. Can I apply CWM as an update.zip from inside the current recovery?
Click to expand...
Click to collapse
Unsure. Most likely not. It would be like running 2 kernels at once... just wouldnt work. Wouldn't risk it. Could hard brick the phone.
Sent from Jelly Fuelled SGS2
First, Post your ROM and kernel details; Goto Settings - About phone, and post everything you see
Sent from my GT-I9100 using Tapatalk 2
Jokesy said:
First, Post your ROM and kernel details; Goto Settings - About phone, and post everything you see
Click to expand...
Click to collapse
No problem -
Model N: GT-I9100
Android V: 4.0.3
Baseband V: I9100XXLPS
Kernel V: 3.0.15-I9100XWLP7-CL340913 [email protected] #3
Build N: IML74K.XWLP7
I ask about the update.zip thing as it is a legitimate way to install CWM recovery according to various guides online.
Thanks for the help guys. Appreciate it.
gyaku_zuki said:
No problem -
Model N: GT-I9100
Android V: 4.0.3
Baseband V: I9100XXLPS
Kernel V: 3.0.15-I9100XWLP7-CL340913 [email protected] #3
Build N: IML74K.XWLP7
I ask about the update.zip thing as it is a legitimate way to install CWM recovery according to various guides online.
Thanks for the help guys. Appreciate it.
Click to expand...
Click to collapse
1. Backup your important data.
2. Uninstall apps you don't use
3. Using a ROOT capable explorer goto /data/app on your phone, delete all .odex files you find there
4. Disable System apps you don't need/use
- Goto Settings - Apps - All - Select the app you want to disable, select FORCE STOP, then DISABLE.
Repeat the step for each app
- Alternatively you can use titanium backup pro to freeze those apps
You can find the list of apps you can disable: here https://spreadsheets.google.com/spr...1gdDJRekl4QmkyNmIzUmRvX2h3UDVkQXc&output=html
5. Boot to recovery (the stock recovery)
- clear cache
- reboot phone.
6. If any user / system app gives you force stop warning, then clear the days of that/those app(s) in settings.
You should notice the difference!
Sent from my GT-I9100 using Tapatalk 2
Jokesy said:
1. Backup your important data.
2. Uninstall apps you don't use
3. Using a ROOT capable explorer goto /data/app on your phone, delete all .odex files you find there
4. Disable System apps you don't need/use
- Goto Settings - Apps - All - Select the app you want to disable, select FORCE STOP, then DISABLE.
Repeat the step for each app
- Alternatively you can use titanium backup pro to freeze those apps
You can find the list of apps you can disable: here https://spreadsheets.google.com/spr...1gdDJRekl4QmkyNmIzUmRvX2h3UDVkQXc&output=html
5. Boot to recovery (the stock recovery)
- clear cache
- reboot phone.
6. If any user / system app gives you force stop warning, then clear the days of that/those app(s) in settings.
You should notice the difference!
Click to expand...
Click to collapse
Thanks for that, but I'm sorry, what? I seem to be missing something - you've answered something that seems to be an entirely different problem! I can't even RUN an explorer let alone grant it root - so I can't reach the ODEXes, which aren't the reason for the FCs anyway.
This 'fix permissions' sounds like a good plan, I just need to know my best method for getting CWM onto the phone given it's state. I think I can use the update.zip method, but I may have to just wait until I can get to a machine capable of running Odin for me, to flash the CF kernel.
gyaku_zuki said:
Thanks for that, but I'm sorry, what? I seem to be missing something - you've answered something that seems to be an entirely different problem! I can't even RUN an explorer let alone grant it root - so I can't reach the ODEXes, which aren't the reason for the FCs anyway.
This 'fix permissions' sounds like a good plan, I just need to know my best method for getting CWM onto the phone given it's state. I think I can use the update.zip method, but I may have to just wait until I can get to a machine capable of running Odin for me, to flash the CF kernel.
Click to expand...
Click to collapse
Ok.
Let me tell you some things you need to know
1. Fix permissions only has much effect on system apps, only if their permission is broken
2. Flashing a new Kernel will never fix many FC
3. Have you booted to recovery and wipe cache? If after doing this and your problem still persist, then you might have perform a Factory Data Reset.
4. Flashing a new firmware via Odin will not dramatically stop Force close errors. You will still need a factory reset to fix that.
Sent from my GT-I9100 using Tapatalk 2
Jokesy said:
Ok.
Let me tell you some things you need to know
1. Fix permissions only has much effect on system apps, only if their permission is broken
2. Flashing a new Kernel will never fix many FC
3. Have you booted to recovery and wipe cache? If after doing this and your problem still persist, then you might have perform a Factory Data Reset.
4. Flashing a new firmware via Odin will not dramatically stop Force close errors. You will still need a factory reset to fix that.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I've tried wiping cache in recovery, yes. The only apps that run are the system ones. I can't explain why permissions may have been broken on the other apps, but it may be the case, so I'd like to try it. And, it was a flash via (Mobile) Odin CAUSED the FCs, so I don't know if that's true. Regardless, I'm heading home now, I can try flashing the CWM and run the fix permissions, and otherwise I need to figure out a backup solution before I factory restore.
I don't mean this wrong, but I'd prefer you don't just throw generic (yet good for general faults) advice if you don't have personal knowledge of the particular problem. It could be misleading.
gyaku_zuki said:
I don't mean this wrong, but I'd prefer you don't just throw generic (yet good for general faults) advice if you don't have personal knowledge of the particular problem. It could be misleading.
Click to expand...
Click to collapse
You know my aim wasn't to mislead you but to help. I actually missed somethings in your Original post like "Every apps now doesn't work" etc
Because the only apps that run now are the system apps proves that there is something wrong in the /data partition, a location where all user apps, settings etc are stored.
Anyway, it's always very good to try all other means possible before factory reset.
Sent from my GT-I9100 using Tapatalk 2
Jokesy said:
You know my aim wasn't to mislead you but to help. I actually missed somethings in your Original post like "Every apps now doesn't work" etc
Because the only apps that run now are the system apps proves that there is something wrong in the /data partition, a location where all user apps, settings etc are stored.
Anyway, it's always very good to try all other means possible before factory reset.
Click to expand...
Click to collapse
Oh, I'm sorry, I wasn't trying to offend you or have a go. I appreciate all the help about to try flashing the rooted CWM kernel, to try the permissions fix. If that doesn't work, I need to figure out some way of doing a backup of sorts, before I do a restore :crying:
UPDATE: After flashing the CF-Kernel to access CWM, I'm getting a message I'm unfamiliar with "The System UIDs are inconsistent" yadda yadda factory reset. I'm currently 'fixing permissions' It looks like it's stalled, but it may just take a while. I have a lot of apps. Anyone understand the UIDs message in my context?
Update 2: Had to factory restore, but was able to restore almost everything with no problems from a CWM nandroid backup. Thanks for the help.