This is something that's bothered me since upgrading to 4.1.1. Doing just what the title says. So far, I've tried clearing the dalvik cache, wiping the cache partition, uninstalling titanium backup and restarting, as well as uninstalling ROM toolbox and lucky patcher. I'm rooted with chainfire's "quick" method but I also had root before upgrading from ICS. I also tried bin4ry's universal ICS/Jellybean method after upgrading before finding chainfire's, witch, I am suspicious of bin4ry's causing the bug in the first place. The message shows briefly after the glowing "Samsung" boot animation. I have scoured to the bottom of the internet looking for an answer, but I really, really do not want to re-flash the stock rom again. Any reason why this happens? Any way to fix it without wiping my phone; if that works?
Sent from my SAMSUNG-SGH-I747
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Any reasons why this happens?
Mine is doing the same thing.
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
It's not wiping the dalvik cache. The system displays the message briefly with no application count. I just assumed it was normal on 4.1.1
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Several people seem to claim otherwise, Google shows. My tenant's and several of my friend's phones don't do it. I'll try reverting to factory and upgrading again in a few days if there are no other solutions.
Sent from my SAMSUNG-SGH-I747
Mine showed up after the Google wallet mod. Also had it happen after removing some stock apps although I'm not sure which caused it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've removed a lot of at&t's bloatware, along with S-Suggest, "help" and ypmobile. I've also frozen s-voice and the samsung keyboard in favor of SwiftKey. I've removed bloatware in both so far. Maybe once I revert, I'll try to find out more about the problem. Until my phone is sick of the cache partition wipes and ruthless dalvik cache destruction, I will continue to try in vain. For the good of my OCD.
Sent from my SAMSUNG-SGH-I747
Many ROMs and Kernels are set to ziplalign apps on boot to improve performance.
I want to say this was also implemented in stock JB, or its set in CWM's init.d script for the newer versions.
This also happens each time you wipe dalvik and/or if you have Titanium Backup set to intergrate sys dalvik into ROM
I just did the HOWTO root after upgrading to stock JB, and after reading this post I did a quick reboot and yeh, the message appears for me as well.
Never integrated sysdalvik w/ titanium backup. I've also rebooted the phone without clearing dalvik, and never had cwm. Probably a few things I should have mentioned earlier, but they never crossed my mind.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Fixed the problem. Turns out you do need to re flash the whole phone. Reset to factory in recovery, then wipe the cache AND the dalvik, then reset to stock using ODIN. IT IS IMPERATIVE THAT YOU RESET TO FACTORY. The phone will remain soft bricked otherwise. A tutorial can be found here: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/. The only tried and true way to get the bug out. As far as I know. If anyone has any more ideas as to how this problem occurs, I'd still like to hear them.
Sent from my rooted SAMSUNG SGH-I747. THANKS CHAINFIRE!!
I rarely reboot these days. I do my CWM backups online.
But when I do reboot, I do get that updating message and have been seening that from as far back as I can remember. It bugged me at first but not now. For me, it only does it for about 2-4secs so I don't bother trying to fix it.
I have the cause in my case but I don't have the solution. I flashed a mod I found here http://forum.xda-developers.com/showthread.php?t=2044449, apn_editor_1.1.zip. Now every reboot I get Android Is Upgrading.... Starting apps.
How do I stop the phone from trying to add this mod?
Just got the same problem. Had super SU on the phone (soft root), so i tried to fully root (i installed xblasttools, and had to flash pa-icons, so i could change the color of the battery, but i couldn't because it said signature failed). Downloaded philz kernel/root, flashed with recovery. Then i uninstalled the Super su rebooted and there it was; Andriod is upgrading ...
I'm on 4.1.2, Samsung GT-i9100. Help !
P.S Uninstalled the superuser that i got with the phil kernel and installed Super SU. Also i did wipe the davlik and cache. Same stuff.
I got the Android is upgrading message before. It was because I tried to convert a user app to a system app. Converted it back to a user app and it went away. I think it had something to do with having an apk file but no corresponding odex file for that app in /system/app
Sent from my SGH-I747M using xda app-developers app
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
magix01 said:
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
Click to expand...
Click to collapse
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
coffee black said:
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
Click to expand...
Click to collapse
Next time just cut odex files to other location, reboot phone and copy odexes back, this should be alot easyer
Try to reflash your rom that may help some how
Sent from my GT-I9500 using xda app-developers app
Related
Hi, I received a Samsung I9000. Would not go past "s".
Used odin to flash to Gingerbread- still would not boot. Flashed to stock 2.2.1.
Takes long to boot, then force close keeps on popping up for all applications installed. After startup, I noticed the same user data and applications on phone. I tried *2767*3855#. No luck. Booted into recovery and wiped cache and formatted, no luck. What else can I do?
This thread doesn't belongs here! Please mods. Move it!
Sent from my GT-I9000 using XDA Premium App
wynsak said:
Hi, I received a Samsung I9000. Would not go past "s".
Used odin to flash to Gingerbread- still would not boot. Flashed to stock 2.2.1.
Takes long to boot, then force close keeps on popping up for all applications installed. After startup, I noticed the same user data and applications on phone. I tried *2767*3855#. No luck. Booted into recovery and wiped cache and formatted, no luck. What else can I do?
Click to expand...
Click to collapse
AFAIK as long as you still notice same user data on phone, you won't get any luck repairing force closes.
Try to wipe data/factory reset first, then do flash any stock Gingerbread with repartition checked using Odin.
After that, you should have a clean ROM without FC.
Then it is best to redownload your installed apps from market.
If you would like to restore your apps using Titanium Backup try just to restore app only (without data).
Good luck and cheers...
Sent from my GT-I9000 using xda premium
TerraBuzz said:
AFAIK as long as you still notice same user data on phone, you won't get any luck repairing force closes.
Try to wipe data/factory reset first, then do flash any stock Gingerbread with repartition checked using Odin.
After that, you should have a clean ROM without FC.
Then it is best to redownload your installed apps from market.
If you would like to restore your apps using Titanium Backup try just to restore app only (without data).
Good luck and cheers...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
and also try to format the internal SD memory for more clean rom flash...
but dont forget to backup it 1st...
I have the same problem ,, the problem is that the internal memory won't format on any way or another ,, I used alot of methods to format it but nothing change .. I still able to read my memory and copy whatever I want but not able to remove anything or make any changes ,,,,,,,,,,, sorry for my bad english
Does anyone know if there are videos showing you step by step how to actually setup a rom, once u have it installed? Last night I installed the sleeper rom, and I couldn't figure out how to get the phone dialer installed. Plus I started getting system force closes. I'm assuming that I should install the zip twice or 3 times right? But really, videos on rom setup would really help.
Sent from my SPH-D700 using xda premium
There are some videos listed in the OP of SleeperROM but doubt it will cover what you are looking for. Replacing the dialer requires pushing the file to system\app folder with Root Explorer. FC's are a sign of corrupted data. A Factory Data reset will clear all data and you can then restore some stuff from Titanium if you had a backup before flashing. Try to not restore data for anything unless you HAVE to have it, like memos or something like that.
so in that case, you think i should do a dalvik wipe, cache wipe and a factory reset before installing the sleeper rom?
by the way, what do you me "op"?
androidmaster1 said:
so in that case, you think i should do a dalvik wipe, cache wipe and a factory reset before installing the sleeper rom?
by the way, what do you me "op"?
Click to expand...
Click to collapse
OP=Original Post which is Post #1 of the thread. I also read in there that it does not preserve data and you should do a full wipe of all 3 things before flashing for best results.
OP = original post (or first post). Yes, wipe everything before installing a ROM.
Edit: before installing most ROMs. Some of them are no-wipe, but i usually wipe anyway.
Sent from my SPH-D700 using XDA App
ok...i got it. now, if and when i reinstall the rom, would there be a problem installing the dialer from titanium backup? would there be any kind of conflict?
androidmaster1 said:
ok...i got it. now, if and when i reinstall the rom, would there be a problem installing the dialer from titanium backup? would there be any kind of conflict?
Click to expand...
Click to collapse
There shouldn't be. Sometimes Titanium is finicky about pushing system apps, but worth a try. If not pull it from a stock ROM and push it with Root Explorer.
Does any one here know if some of the Kernal cleanser zips from the s2 for TMO would work on the s3? If not are there any similar options?
Also is there a davlik wipe that works properly on the s3? Similar to the dark side zips. Cwm is not doing so correctly.
Sent from my SGH-T999 using xda premium
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
This is the link for superwipe for the Hercules
http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
Sent from my SGH-T999 using xda premium
Well not exactly what I was looking for but it will work for clean flashes. Thanks kind sir. This is from the same dev as the s2 so it's solid I am sure.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Wildchld has a Superwipe script in the op of his xquizit thread. That's the closest thing I can think of for us right now, but it wipes everything.
Don't use any from another device. Depending how its written it could brick you.
Should be pretty easy to make it work for ours. Ill try to find it and see if I can't get it working for us.
Do you have a link to it?
Just curious, how is cwm not doing the job for you? Does it error or just seem to not work right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
I have been using TWRP since I rooted my phone back in June, have not had 1 issue with it. Everything works flawlessly, I have flashed almost every AOKP, CM10, TW ICS & TW JB ROM out there thru TWRP and never lost my IMEI and the wipe functions in it work just fine. I usually wipe cache/delvik, system & factory reset 3 times. For me it seems to wipe pretty fast ( that's why I do it 3x ).Just to be safe.
belial20xx said:
It just seems not to work. It goes way to fast to seem to be working and throws the same extsd error as the s2 had done. How is twrp? Is it worth the try? I have heard many issue can occur with it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Well isn't this normal since there is no external sd ext partition? I mean sure one could write a simple zip to delete /data/dalvik-cache.
And there really isn't a way to check it either. Cause I don't think adb works in recovery mode.
Sent from my SGH-T999 using Tapatalk 2
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Aerowinder said:
The Dalvik wipe in CWM works fine. It's very fast (just a few files), and the "error message" can be safely ignored. It's more like an informative message, not an error message. If you don't think it worked, just reboot your phone, and you will see that it did, infact, work.
There are still people going on about IMEI loss with CWM. First of all, you should have backed up your IMEI with su > reboot nvbackup in a terminal emulator. When your IMEI is 0, what happened was your nvdata got corrupted, so the backups were restored. Problem is you didn't make a backup, so those partitions contained nothing but dummy data, instead of the nvdata they are supposed to contain. It's been theorized that this is a screw up at the factory level. Easily rectified.
Last I checked, no one has figured out why this corruption happens. Flashing a nightly flashes the kernel and copies system files. Which means it can happen with either CWM or TWRP. I suspect the disparity in user bases, combined with the rarity of the problem, is why you don't see people complaining about IMEI loss with TWRP.
Kernel cleanser? You don't need one. Just flash a new kernel, it will overwrite the old one (it's a partition).
What problems have you heard about with TWRP? My complaints are mostly nitpicks, and I'm biased. It works fine. Make sure you're always using the latest versions, though.
Click to expand...
Click to collapse
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
I made a dalvik cache wiper.
If you notice when you use CWM to clear dalvik cache, then reboot, it doesnt say android is upgrading at all. Making me think it doesnt work.
But when you just flash my script, it says its upgrading.
the zip is simple, all it does is delete_recursive("/data/dalvik-cache/") and thats it.
elesbb said:
Its actually not just a few files. Its quite some 60 megs depending how many apps you have installed
Click to expand...
Click to collapse
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Aerowinder said:
Obviously, it was an exaggeration.
After your report on dalvik wipe not working, I was inclined to try it myself, since I always wipe cache+dalvik when flashing a new rom. Wiping just dalvik, I was greeted with the optimizing apps prompt on the next boot.
Click to expand...
Click to collapse
So did i.. but it optimized the same amount of apps that the "wipe cache" option does. I seriously wonder now if they are one in the same. Like if they are coded to wipe /cache and /data/dalvik-cache. Cause when using my zip, i only optimize 58 apps.
Lately I am getting this on every boot. I wipe cache, dalvik. fix permissions. factory reset all that and it still happens. Anybody have any ideas on how to fix it.? I am really good at fixing phones but this is driving me nuts. Every rom I have installed in the past week has been doing the same thing. I used WHX roms. infamous, jellybam, etc. all of them I get the same thing. I used titanium backup to rejust apps only with no data and it still happens. Have apps2zip and used it ti flash my apps back I still get the same message " process system isn't responding" Appreciate any solutions thrown my way. I might figure it out myself but in the meantime I am up for suggestions. Thanks in advance.
Do you wipe system before you flash a new ROM?
Sent from my SGH-T989 using xda app-developers app
Everytime I figured it out though it was my mixer theme for some reason it doesn't work even though its a jb only theme apk. Moderator please close thread asap. Thanks
Sent from my SAMSUNG-SGH-T989 using Tapatalk
[Q] Phone was fine, ran out of battery, now "System Ui Has stopped" every few seconds
Hey,
Note 2 running PACMAN rom, android 4.3.
I woke up and checked it at 8am, no problems at all. Went to use it at 1pm and it had run out of battery. I plugged it into my computer to charge it, turned it on and it said "System UI has stopped. Blame Tyler" - and continues to do this every time you press OK, with about a 3 second gap in between each one.
I restart my phone quite regularly and I don't think I've installed anything that could be causing this. I've disabled XPosed but same problem. Any other ideas? Otherwise I'll have to just wipe it and start again, perhaps with CM. I need a working phone for tomorrow though!
Cheers
Maybe a silly question, but have you wiped cache and dalvik cache from recovery? If not try it.
Sent from my GT-N7100 using Tapatalk
chandoliasnikos said:
Maybe a silly question, but have you wiped cache and dalvik cache from recovery? If not try it.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
This seems quite sinisiter - thanks for the suggestion but it hasn't worked, and it's unearthed something more concerning about the state of my phone (the TWRP messages, see below). Can't believe I didn't think to do that myself though! (I haven't messed around with ROMs for quite a while so am out of practice, I've had this one for a few months).
Delvik cache completed, then said something like "updating partition details. E: Error opening '/data/system/...." I/O Error" and various APKs - one of which was system UI. Wiping the cache again told me done, but loads of errors of similar APKs (This time in /data/data/ though). This sounds incredibly ominous though and I've never seen that error before in any of the wipes or anything I've done.
Restarted it but the system UI error messages persist. I want to wipe and install a fresh ROM but I'm worried I'm going to be left with a totally useless phone if things won't wipe or flash properly. Any ideas would be great.
If anything goes wrong u still have the option to flash a new rom through odin.
Sent from my GT-N7100 using Tapatalk
chandoliasnikos said:
If anything goes wrong u still have the option to flash a new rom through odin.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
I'm currently downloading a rom to flash with odin. I tried to do a nandroid backup but the same I/O errors appeared. I have no idea what could have caused this as the phone was running absolutely fine yesterday!
try to fix permissions in recovery. On HD2 it helped in 90% of the cases
yaro666 said:
try to fix permissions in recovery. On HD2 it helped in 90% of the cases
Click to expand...
Click to collapse
Yup. This might be the solution.
Helped me 90% of the times. Go to TWRP -> Advanced -> Fix Permissions
Sent from my GT-N7100 using Tapatalk