Related
I recently flashed the Super_Z2.4 rom, was running SR3.5. I have now developed an issue where Titanium force closes, the app will not even start. I have re-installed Titanium several times, thinking I may have a corrupt download, and even downloaded an older version from the dev's web site. I never had this issue with any of the SR roms, never had this problem at all. I am still tunning the kernel that came with the Super_Z rom. Any thoughts, ideas, or suggestions would be great. Thank you.
Couple things to try:
Clear the cache for the TB app. Settings>Applications>Manage Applications>Downloaded>TB - clear data and cache.
and/or
Uninstall TB, boot into recovery, run fix permissions from recovery, clear cache in recovery, clear dalvik in recovery, reboot, d/l TB from market.
I already tried running the fix permissions, from both Rom Manager and by rebooting into Clockwork. I just flashed back to my nandroid of SR3.5 and TB works perfectly there. I'm not sure if it is a rom issue or a kernel issue. I'm gonna PM the dev of the Super_Z rom and ask him, as I am not yet able to post in the dev forum to ask there.
Just flashed back to Super_Z and tried clearing the cache for TB, no dice....
Wow .... sounds like a ROM thing.
Sent from my ADR6300 using XDA Premium App
Hello potential helpers in the CM community.
So long full days work or android updating story short, I was running 7.0.2.1 and updated to 7.0.3 with rom manager. I decided to not wipe all data, but to just clear the dalvik cache. After the update all the apps tried to reinstall again. I tried to do a titanium backup restore on top of that and everything froze up. I rebooted and tried again. Same thing happened. So i reverted to the nandroid 7.0.2.1 and did the entire thing over again but this time wiped the cache, and the same thing happened. So I wiped the data and cache, did a nandroid restore to the original 7.0.2.1 and then tried to do some different options. i changed up th order in which I did a restore, what cached I cleared, and anything I could think of. But Now I am stuck at either my nandroid 7.0.2.1 or 7.0.3. Both of these ROMs work fine with no issues EXCEPT whenever I try to install an app it fails. I have cleared the market app data and cache, but nothing seems to work. Any ideas?
Thanks
2 things.......
1. You should have posted this in the CM7 thread.
2. I would try reloading a fresh market .apk and see if that takes care of your issue. Usually just clearing cache and data will take care of those issues.
Sent from my CM7 Droid Incredible using XDA App
Also its good to make it a habit to flash ROMs in recovery after a cache and dalvik wipe instead of using RM
Sent from my CM7 Droid Incredible using XDA App
I will try that
Firstly, sorry have not been on XDA scene cm7 was out, didnt even check for that, and secondly I will try that. Thanks for the tips
justinmburrous said:
Firstly, sorry have not been on XDA scene cm7 was out, didnt even check for that, and secondly I will try that. Thanks for the tips
Click to expand...
Click to collapse
NP good luck, hopefully re-flashing market fixes your issues. You can find the .apk floating around XDA. Let me know if it work.
fixed
So I ended up just reverting back to the nandroid and then flashing 7.0.3 before I reflashed the market. However the market worked fine right after reflashed the new version of CM. I did not change anything from what I did in the past, but it is fixed. Thanks for your. help.
justinmburrous said:
So I ended up just reverting back to the nandroid and then flashing 7.0.3 before I reflashed the market. However the market worked fine right after reflashed the new version of CM. I did not change anything from what I did in the past, but it is fixed. Thanks for your. help.
Click to expand...
Click to collapse
Anytime. Glad everything is back to normal.
i find that the nightly build is cool and is awesome. the problem is when i use system panel task manager, the phone reboots. i dont know why and its more laggy than the cm7 mod please tell me its me doing something wrong not my phone's or the mod's fault.
and it svery irritating that it keeps hanging. please someone help me with the nightly mod thing i want to use.
Go for nightly#205. And do a full wipe including data,cache,dalvic cache, and perform a factory resetting from cwm before you flash the nightly. Also use latest buzz kernal so that you can overclock your phone.
Sent from my HTC Wildfire using XDA App
I know how to clear data and cache from clockwork mod. How to clear devik. Ache and factory reset from clockwork mod. And the kernel from where? Can please tell me and post link for kernel?
ongtengjun said:
I know how to clear data and cache from clockwork mod. How to clear devik. Ache and factory reset from clockwork mod. And the kernel from where? Can please tell me and post link for kernel?
Click to expand...
Click to collapse
i had problem with my previous nightly # 177 when i used darktremor APP2SD script .. even when i re flashed nightly #205 .. things were the same (Talking about random reboots upon opening task manager / and installing apps etc. ) ..
then i repartitioned my SD and didn't flashed the script... now its fine .. ..
so how did you install it? how to repartition sd card and not flash the script? how to install?
V0odo0 said:
i had problem with my previous nightly # 177 when i used darktremor APP2SD script .. even when i re flashed nightly #205 .. things were the same (Talking about random reboots upon opening task manager / and installing apps etc. ) ..
then i repartitioned my SD and didn't flashed the script... now its fine .. ..
Click to expand...
Click to collapse
Lol you may have used beta 4 script, try beta 3, need to use atleast ext3 as your secondary partition. Try it with latest original cwm recovery. 5.xxx to partition. Do a clean install after partition.
And a personal suggestion. S2e app in market is good than dta2sd, though it have not much functions, but what it have, it does its best. I use it.
Sent from my HTC Wildfire using XDA App
ongtengjun said:
I know how to clear data and cache from clockwork mod. How to clear devik. Ache and factory reset from clockwork mod. And the kernel from where? Can please tell me and post link for kernel?
Click to expand...
Click to collapse
Dude, explore options in cwm, don't do formatting boot, system, data, unless you learn what it does.
Options may vary from version to versions of cwm. So you have to say which cwm version you have. Mine is latest 5.xxx.
In it, data- factory format( user data or wipe user data, which ever it is called) is in main menu. And dalvic cache wipe is in advanced menu.
Lol you must carefully read topic named" complete wildfire index, then ask doubts, after all you can learn new things from every topic.
Your kernal will be in that topic. Check it out.
Sent from my HTC Wildfire using XDA App
another problem
now i got another problem. my wildfire will hang every now and then and i have to pluck out the battery and switch it back on. its very irritating and having to keep doing that will kill my bat very quickly so could anyone tell me any solutions?
To solve your problem, you must say. Your current configuration, rom, kernal, radio, tweeks, and what have you done just before you got the error
Sent from my HTC Wildfire using XDA App
well i am using the cm7 nightly build #205. kernel is buzz-kernel-2.6.35. i just downloaded some apps that were in my phone when i was using cm7 stable. and there wasnt a problem. do i have to upgrade to latest build and kernel? oh and just a question. if i want to upgrade from #205 to #208, do i have have to like wipe my data and cache and dalvik cache? i wouldnt wanna redownload and change everythin again
You can install the nightlies on top of one another without wiping anything, sometimes it seems better to wipe the cache to me but not always necessary, leave data alone.
Word of warning though, always make a nandroid backup before installing a new rom, although they're stable they are still called experimental for a reason, and sometimes (not very often) things can still go wrong.
Sent from my HTC Wildfire using xda premium
i wiped both the dalvik and partition cache and installed the #208 nightly build and the latest kernel but then the phone would just restart automatically. do i have to wipe data as well?
Yes do a "Wipe Data / Factory Reset" in Clockworkmod if it is giving you issues. Then try a fresh install and check again for instability.
Note - Performing a Wipe Data / Factory Reset will erase all data (Except SD Card)
well i not sure but i think the problem still occurs.. yes it does. i wiped data, cache and dalvik cache, did a install using cwm and it still reboots WHAT TO DO NOW
showlyshah said:
Lol you may have used beta 4 script, try beta 3, need to use atleast ext3 as your secondary partition. Try it with latest original cwm recovery. 5.xxx to partition. Do a clean install after partition.
And a personal suggestion. S2e app in market is good than dta2sd, though it have not much functions, but what it have, it does its best. I use it.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Hey thanks dude .. yup i was using beta 3 last time.. beta 4 was a disaster to CM7.. .. i tried that too ..
but i think my partition was ext2 coz i am using CWM 3 .. will try with CWM 5 .. and sure... S2e too ...
Do you let it boot up before flashing the kernel?
Sent from my HTC Wildfire using xda premium
For i always keep a backup of my contacts in sd. Also apps using titanium backup, i had never used a nandroid backup till now, i alwayz do fresh installs, wiping every thing but not fat32. And always keep things updated.
Sent from my HTC Wildfire using XDA App
ok now i have another problem. my phone will just reboot after hanging when i open system panel task manager. please some one help me
ongtengjun said:
ok now i have another problem. my phone will just reboot after hanging when i open system panel task manager. please some one help me
Click to expand...
Click to collapse
dude is it the same one you had before? thats why we mention to give your current spec. with out it we cant do any thing or we cant help you.
Hi Guys,
I read through a lot of rebooting threads on here, but none talked about the rebooting issue after a radio update. My EVO NEVER, EVER had a rebooting issue. I just upgraded the radio, and now the phone keeps rebooting nearly IMMEDIATELY, when it loads into the ROM.
Even downgrading to the original radio version I had, the phone was still rebooting.
The rebooting threads don't really offer a solution that worked. Can someone please confirm for me if anything worked for them, minus the replacement phone, cause I can't have that, I got mine off of Craigslist. Thanks for your help and thanks for reading, looking forward to your responses!
Have you tried wiping cache and dalvik cache then fix permission?
I've never had that happen from radios but earlier today my sdext got messed up some how and my phone was doing that and then it just wouldn't boot after a while I did the fix sdext thing in Amon Ra recovery and it fixed my issue not sure if that helps you in any way though.
Sent from my PC36100 using XDA App
linsalata28 said:
Have you tried wiping cache and dalvik cache then fix permission?
I've never had that happen from radios but earlier today my sdext got messed up some how and my phone was doing that and then it just wouldn't boot after a while I did the fix sdext thing in Amon Ra recovery and it fixed my issue not sure if that helps you in any way though.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I haven't tried wiping the data, or the caches, yet. I wanted to be sure of it, before I did that. I did a NANDROID as well, but not sure if that will be any useful IF the fix was clearing the cache.
Any other ideas, guys?
ProFragger said:
I haven't tried wiping the data, or the caches, yet. I wanted to be sure of it, before I did that. I did a NANDROID as well, but not sure if that will be any useful IF the fix was clearing the cache.
Any other ideas, guys?
Click to expand...
Click to collapse
Try just wiping cache and dalvik cache and fix permissions and see if that helps.
FYI you can wipe those caches and no harm will come to your ROM you should always wipe them before you flash anything.
Sent from my PC36100 using XDA App
Did you just flash the radio or did you flash the combo? If you upgraded everything but only downgraded the radio, it could be one of the other components (pri/nv, wimax).
Once you've tried wiping cache/dalvik, try flashing a different radio if you only flashed the radio to begin with, or downgrading everything else if you used the combo zip and are still experiencing reboot issues.
By the way, you can still insure a phone that was purchased somewhere else. You may want to do that in the future.
If none of the suggestions work, it could be something other than the radio. You can always make a backup and do a full wipe to see if that helps - or run an RUU and return to stock if all else fails.
Sent from my Evo + MIUI using Tapatalk!
Some of the radio updates that I have seen posted also indicate that you may need to reflash your kernel after loading the radio update.
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