Dalvik cache wipe. Now EVERYING FC *resolved - Hero CDMA Android Development

So I did this once before and had to nand restore. I just did it again on a new install of fresh 1.1 with apps2sd and it did the same thing. Instant FC on ALL apps at boot. I'm doing this from RA menu. why is this happening?!

beyondinferno said:
So I did this once before and had to nand restore. I just did it again on a new install of fresh 1.1 with apps2sd and it did the same thing. Instant FC on ALL apps at boot. I'm doing this from RA menu. why is this happening?!
Click to expand...
Click to collapse
Adb into the phone, erase *the contents* of /data/dalvik-cache (not the directory itself), reboot the phone.

I understand that but It just makes me a little nervous that it doesn't work from RA.
And I don't know why but this thread got posted twice. Mods please combine? TY

If you are using the v1.5.2 I had this same problem along with others users (i run fresh 1.1 also) and i reported this problem in the RA-heroc-v1.5.2 thread, but got thumped on about how this ROM had no problems. I didn't have this issue in 1.2.3. Everytime you do a wipe in this new Recovery whether it tells you to ADB or not, it will cause your phone to FC everything on reboot.

Found It:
29th December 2009, 12:04 AM
rvm23
Junior Member Join Date: Nov 2009
Posts: 4
--------------------------------------------------------------------------------
Quote:
Originally Posted by gu1dry
"And it says when it fails to clear the Dalvik Cache, to do a simple adb command, sheesh, people are lazy... "
This made me decide to try something. The typical instructions for clearing the caches are:
Quote:
adb remount
adb shell
rm -r /data/dalvik-cache
rm -r /data/boot-cache
reboot
"I tried only the "rm -r /data/dalvik-cache" command in adb, and had the same problem with endless FCs that the wipe dalvik option in the recovery has been causing. I then used adb to do "rm -r /data/boot-cache and rebooted again. Once it reboots, everything appears to work fine.
So it seems like the boot cache needs to be cleared after the dalvik, and the recovery tool isn't doing that."

FYI the clear cache button inside fresh kitchen does do dalvik-cache and boot-cache.

flipzmode said:
FYI the clear cache button inside fresh kitchen does do dalvik-cache and boot-cache.
Click to expand...
Click to collapse
Thanks Flipz! That will save some time!

Agimax said:
Ii reported this problem in the RA-heroc-v1.5.2 thread, but got thumped on about how this ROM had no problems.
Click to expand...
Click to collapse
No, you got thumped for recommending that people stay on 1.5.1, which has known problems with backups.

posguy99 said:
No, you got thumped for recommending that people stay on 1.5.1, which has known problems with backups.
Click to expand...
Click to collapse
I Recommended using 1.2.3, not 1.5.1 or 1.5.2
25th December 2009, 06:50 PM
Agimax
Junior Member Join Date: Nov 2009
Posts: 20
--------------------------------------------------------------------------------
Quote:
Originally Posted by rvm23
Is there a problem with wiping the dalvik-cache in the most recent version of the recovery? Every time I try, I get an error saying it failed and then then get an endless string of force closes after my phone reboots. I then have to restore a nandroid backup in order for my phone to function properly again.
I've had the force close problem twice tonight, and it dawned on me that I had tried wiping the cache in recovery both times. I then tested it a third time and had the same result.
Edit: It would've helped if I had spelled dalvik correctly when searching this thread. Post #85 is about a similar sounding issue.
I have the exact same problem. Now with this new Recovery when i wipe the Dalvik Cache, the phone has a Zillion FC's. I couldn't even use the Nandroid backup, it still had the force closes after i pulled a backup. I just did a Factory Wipe and put Fresh 1.0 back on. Pain In The A**!!!
My Advice To All: Just Don't Wipe The Dalvik Cache Till It Gets Checked Out By Developers Or Go Back To v1.2.3 ...
EDIT: To Be More Clear, I Could Use Nandroid Backup Just Fine, But It Still Had FC's All The Time After Using A Backup.
--------------------------------------------------------------------------------
Last edited by Agimax; 26th December 2009 at 11:36 AM..
* See people like to defend thumping, cause they didn't see a problem at the time *

Well I'm very happy to hear some kind of explaination. Thanks guys!

What's the point of wiping the dalvik-cache?

jonnythan said:
What's the point of wiping the dalvik-cache?
Click to expand...
Click to collapse
That's the cached java bytecode for your applications. If you erase it, the phone will recreate it the first time you run the application again.

posguy99 said:
That's the cached java bytecode for your applications. If you erase it, the phone will recreate it the first time you run the application again.
Click to expand...
Click to collapse
Actually, to be a bit more specific, Dalvik is android's own native language based off of java. It is structured and runs just like java bytecode. Of course we don't code applications in bytecode so we use something familiar which is java source code, then with some help from an interpreter, we take said java source and convert it to dalvik bytecode for running on android.
The reason you may want to clear the dalvik cache is as follows. The Dalvik virtual machine which runs within android caches an optimized version of the bytecode to improve app loading and performance. If you get random force closures it is very possible that the cache for your apps may be incompatible with your current version of the app for any of a number of possible causes.
Clearing the cache forces the Dalvik virtual machine(DVM) to correctly rebuild the cache to what you currently have installed, and in many cases it fixes the force closures. Usually dvm and boot caches are normally the culprit when you install a new rom and experience force closure problems.

Thanks for the help guys! Mods please rename the thread "resolved"

Same problem here.
However, I don't have any boot-cache so I'm stuck with a clean dalvik cache an a ton of FC!
What to do?

Related

"System UIDs Inconsistent" with JF1.5

Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Vermithrax said:
Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Click to expand...
Click to collapse
wipe and re-set your symbolic links .. all your apps will be back but not their data..
Thanks... I guess I will just take the easy way out and wipe the phone... I have tried various ADB and busybox commands to no avail... What I do not understand is the phone works perfectly after the Nag screen is gone... No force closes... no missing functionality...
I will not do the wipe until this afternoon... Just in case some Linux guru has any ideas...
L8r,
Vermithrax
Unless the nag screen bothers you, or shows up more than once per boot, Id leave it. If you start seeing instability or forcecloses then Id wipe.
Unless there is a good reason to Id avoid a wipe. Of course I dont have OCD so one nag per reboot wouldnt bother me. If you do or it does bother you then yeah wipe.
Solved... For me at least...
I had solved this problem some time ago, but I just thought I would add this to the thread in case others find their way here through a search...
All I did was move the /data/data back to the internal memory...
rm /data/data
busybox cp -a /system/sd/data /data
rm -r /system/sd/data /data
reboot
Had a couple of stale NFS file errors, so I could not really delete the /data directory from the /system/sd. However, there are threads that help with this issue.
Probably the cleanest solution HERE

[ROM] Barebone SGS4G KJ6 1.1.3

Barebone SGS4G KJ6 ROM
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this ROM.
Here is a ROM that I made for myself, but what the heck, let's share. This ROM is very stock-like with just few usability mods.
Features
Will not wipe your programs or data, /data is preserved upon install
Heavily debloated. Most essentials apps are still there (like WiFi Calling)
No extra programs added, you need to add your own
ODEXed to save space in /data
CarrierIQ is completely removed
Extended Power Menu (including Screenshot)
Extended Quick Panel (10 buttons, including Data toggle)
1% battery (horizontal)
CRT-Off
Time zone version 2012b
/etc/hosts to cut ads out of the box (keep up to date with AdAway or similar)
Few conservative presets in build.prop and init.d
Basic with a Twist 1.1.3 kernel included
Notes
* Don't get confused about ODEXing, it's actually better to run and saves quite a bit of space in /data.
* Some Google apps (Maps, Streets, Voice) and Adobe Flash are removed from /system. Install them from market. Benefit - they can be moved to SD card this way.
* Original Swype is removed, is somebody needs it flash this.
* In case you need it, use this thread to add some bloat back.
* Factory Reset is removed from Settings->Privacy, use CWM if you ever need to reset all data.
* KJ6 modem included. Use this thread to flash a different modem if needed.
Install
Flash with CWM. Wait until the system boots up, then wait few more minutes for it to settle.
Download
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.8
Changelog
1.1.3
Removed "Mobile data connection disabled. Connect?" popup on boot
1.1.2
Removed Factory Reset from Settings->Privacy
Updated kernel
1.1.1
Fixed voicemail notifications not working without Visual Voice Mail installed
1.1.0
CIQ is properly removed
Some neutral cosmetics (logo, animations)
Minor update to the kernel
1.0.8
Fixed slow stock browser scrolling
1.0.7
Extended Quick Panel
1.0.6
Added Screenshot to power menu
1.0.5
Removed DriveSmart and Software Update from Settings menu
1.0.4
Put original framework-res.apk certificate back
1.0.3
Added power menu mod
1.0.2
Original public release​
does it have a screenshot option from the power menu??
m0bstr said:
does it have a screenshot option from the power menu??
Click to expand...
Click to collapse
Nope, never bothered with power menu. I don't reboot the phone too often and to say the truth don't even remember when last time I needed to take a screenshot. I use ShootMe and QuickBoot when I need to, they both do the job just fine.
Yes, power menu is fully modded now, including Screenshot option.
Thank you for this, Anton! Love your kernel. Is this ROM ok for OC/UVing with you OC/UV kernel? I think this will be the second ROM I have ever installed. Haven't bothered to try anything since first getting Val Final.
Download link is not working
Sent from my SGH-T959V using XDA
Does this come pre-rooted?
Blaggah said:
Does this come pre-rooted?
Click to expand...
Click to collapse
Yeppers it does.
I updated the link. I actually took it down on purpose, wanted to look at something but never had time.
I was troubleshooting an error message during boot time, so I traced it to the CIQ trying to execute some on-boot code, which was removed by Krylon. Strangely the original code itself doesn't do much, it's initilizing a broadcast receiver with an empty onReceive method. Removing this was a moot point, it probably didn't do much. I disabled the BOOT_COMPLETED permission for the service to avoid the error message.
So I looked at the CIQ more closely. What I found is a little peculiar. The main CIQ code is integrated quite deeply into the framework, it cannot be removed easily, there are just too many calls that send various metrics to the CIQ Agent. The main CIQ classes are not in the framework.jar, they are in ext.jar. Probably that's why nobody noticed them and never tried to modify them. What is strange that many calls seem to be not implemented. For example the sumbitMetric is an empty method, shouldSubmitMetric always returns zero, etc.
It's possible that T-Mobile decided not to use CIQ on our phone (at least extensively), but instead of removing it completely just plugged few calls.
I'm removing the "CIQ removed" description because it's actually not removed, although may not be doing much.
I cannot get it to boot. After the "Galaxy S 4G" screen, the screen goes back then nothing ever happens. I rebooted into CWM (which still shows Team Acid's logo) and tried fixing permissions to no avail.
Given that the OP says it won't wipe programs, data, etc, was it possibly a Bad Idea™ to have wiped everything before installing this ROM?
Update:
Indeed, installing from a blank phone (literally, I wiped everything) didn't work for me. I flashed Bryan's one-click with CWM, it booted, rebooted into recovery, flashed this, and it booted. Now for testing. Thanks, Anton!
I had the same issue as well... Thought it was just my phone
Sent from my SGH-T959V using xda premium
Would be interesting to look at the logcat to see where it's stuck.
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
wont flash
I wipe everything, the ROM installs, and then black screen...noting. Let it sit for 20min however this did not resolve issue. I was able to install Valhalla no prob. flashed your rom on top of Valhalla and then my phone boots your rom. Do i need to install on top of another rom? I should just be able to whipe my phone and install your rom correct?
AntonX said:
Would be interesting to look at the logcat to see where it's stuck.
Click to expand...
Click to collapse
I can probably capture that because I can use adb to get into the OS. I ran top to see what, if anything, was hogging CPU but there was nothing obvious & CPU usage was minimal. I have the phone running now but I'm willing to wipe it again and re-flash. Mind you, I did more than factory reset. I was quite literally trying to start from scratch, so here's what I did (if this helps at all):
Backed up /efs to my PC
Backed up the SD card to my PC
Wiped cache
Wiped Davlik cache
Wiped battery stats
Performed a nandroid backup
Copied the backup from /sdcard/clockworkmod/backup to my PC
Formatted /data, /system, & /sdcard
Rebooted back into recovery
Copied the ROM to the SD card
Flashed it
Let it cook for ~20 minutes
So it was quite literally a blank slate.
AntonX said:
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
Click to expand...
Click to collapse
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
stephen_w said:
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
Click to expand...
Click to collapse
Wow, you really wiped everything from your phone
I'd appreciate if you send me the log. All you need to do is to save the file with "adb logcat -d >MyLogFile.log" after couple of minutes of this black screen. On an factory reset phone ODEXed ROM should boot very fast the first time because it doesn't have to build Dalvik.
I just tried downloading from my own link and reinstalling, everything seems OK. I also tried installing after full phone reset yesterday, it went fine too. I don't want to reset and restore everything anymore, too lazy
If it proves to be the certificate in the framework-res.apk, I may need to put the original AndroidManifest.xml back.
Hey Anton,
You can snag the logcat from here. In case anyone wants them & to clarify what I did, here are the steps I followed (similar to above but more detailed):
- Boot into CWM
adb reboot recovery​- Disable voodoo lagfix
- voodoo lagfix​- disable lagfix​- /system lagfix off​- Reboot
- Create a backup directory structure on your PC (mine is in C:\Users\username\Downloads\SGS4G)
mkdir backups​cd backups​mkdir efs nandroid sdcard​- Backup /efs to your PC
cd efs​adb pull /efs/​- Backup /sdcard to your PC
cd ..\sdcard​adb pull /sdcard/​- Boot into CWM
adb reboot recovery​- Wipe cache
- wipe cache partition​- Wipe Dalvik cache
- advanced​- Wipe Dalvik Cache​- Wipe battery stats
- Wipe Battery Stats​- Create a nandroid backup
- +++++Go Back+++++​- backup and restore​- backup​- Copy the backup to your PC
cd ..\nandroid​adb pull /sdcard/clockworkmod/backup/​- Format /data
- mounts and storage​- format /data​- Format /sdcard
- format /sdcard​- Format /system
- format /system​- Reboot into CWM (necessary for CWM to see the sdcard contents)
- +++++Go Back+++++​- advanced​- Reboot Recovery​- Copy the ROM to the sdcard (this is from the directory in which the ROM is located on your PC)
adb push ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip /sdcard/​- Flash the ROM
- install zip from sdcard​- choose zip from sdcard​- ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip​- Reboot & let it sit for ~10 minutes
Sorry for the lengthy post, but I wanted to ensure there was transparency in what I did.
stephen_w,
Seems that it's not framework-res.apk issue, it's not complaining about any certificates.
A lot of unknown permissions in the log, but it's OK, we've removed some of the system packages that grant those permissions but they do more harm than good in the end.
The crash has something to do with that: *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService. Hm......
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Weird...it flashed fine for me with no wipe....
I did move on and never gave it a break in....but it did work
Sent from my SGH-T959V using xda premium
AntonX said:
stephen_w,
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Click to expand...
Click to collapse
I usually don't do it that extensively at all. I was writing a process for myself in case I wanted to really clean it out So this gave me a good excuse to test it. I was having some weirdness which prompted me to write the instructions for myself.
I haven't tried shutting it down after the install. I can certainly try that for you, if you like.
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Sent from my SGH-T959V using xda premium
Lawful123 said:
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Click to expand...
Click to collapse
Doubtful. Nothing I can think of, off-hand. I have to wait until later this afternoon/evening to reflash it and try powering off vs. rebooting from recovery. If you have the chance, please feel free and let us know what happens.

[Q] What should be wiped when flashing new ROMs?

I’m using ClockworkMod Recovery v5.0.2.0 (on an LG Optimus T). I’m experimenting with different ICS ROMs. From reading various posts on this wonderful forum, I’m fairly sure one should always wipe the cache and Dalvik Cache when moving to a newer release of a ROM or to a completely different ROM. Is that correct? And, if one is going to a completely different ROM altogether (even if the old and new are both ICS) then one should also wipe data/factory reset?
Does that make sense? If so, is the reason one doesn’t wipe data/factory reset when going to a newer release of the current ROM because then that data is carried over to the new ROM and it saves time in terms of reconfiguring settings...?
Thanks in advance for your help.
Dave
a wipe is always suggested when installing newer version of rom or totally different flavor to avoid data errors or mismatches in settings depending on the degree of change from previous release. i guess most have been able to manage to retain same data and not do a total wipe out to factory because of customizations which is very annoying to do all over again.
if you want to experience the full potential of a certain rom, i suggest to do a full wipe.
note: i have been able to switch from CM7 to CM9 and back with only dalvick, cache, and battery stats wipes. although, i get to reinstall a few apps like Titanium due to FCs.
New release of same rom : Wipe cache and dalvik cache. (If any errors arise with the apps later you should do a full wipe)
Different rom : Wipe data/factory reset, cache, dalvik cache. Sometimes it is recommended to wipe /system too.
Thanks for the responses. Sincerely appreciated. So, if I'm trying a different ROM, I need to do the factory reset, cache and Dalvik Cache wipes - and if just going to a newer version of a ROM, I can skip the factory reset - and go back and do the factory reset if problems arise with any apps. If I do experience issues with my apps, does that mean I just have to do a factory reset - or do I need to reinstall the ROM first and then do the factory reset...?
I presume the benefit of not doing the factory reset is that there is then no need to reinstall apps, fix settings...
When you say "Sometimes it is recommended to wipe /system too", which option is that in CWM or do I have to do that from my PC...?
Thanks in advance for any clarification.
Dave
If you get FCs with some apps while going to a new version of the ROM(without a /data wipe), try clearing the data of that app alone. That might help.
To wipe system, you can use the zip attached. It was provided with some ROM when there was an error in formatting /system automatically before the new rom installation. Just flash it like any other zip and it will format your /system.
You can use Titanium Backup to backup/restore your applications. Just be carefull with system apps, restoring data from different roms can cause fc.
Sent from my GT-I9100 using XDA
Check this thread for info on partitions and cwm options......
CWM - Clockworkmode menu options & Partitions– GENERAL KNOWLEDGE
Though it is already mentioned in above thread..i again remind you to NOT format the boot partition as this is one of the only few things which can brick your device while using cwm......
Click Thanks on above thread if it helped you.....
---------- Post added at 10:38 PM ---------- Previous post was at 10:01 PM ----------
aravindsagar said:
To wipe system, you can use the zip attached. It was provided with some ROM when there was an error in formatting /system automatically before the new rom installation. Just flash it like any other zip and it will format your /system.
Click to expand...
Click to collapse
Are you sure it works with clockworkmod recovery???
show_progress 0.1 0
format SYSTEM:
show_progress 0.2 0
show_progress 0.2 10
This script has two problems in my opinion:
1.AFAIK this type of script format(amend) is not supported by cwm now.
2.When editing with n++ it shows CR LF at end of each line......
and "carriage return" line code is used in windows while unix uses LF (line feed) for it's text.....so there should be LF only.....i think
Please correct me if I am wrong as i am just trying to learn here.....:fingers-crossed:
gargujjwal said:
Check this thread for info on partitions and cwm options......
CWM - Clockworkmode menu options & Partitions– GENERAL KNOWLEDGE
Though it is already mentioned in above thread..i again remind you to NOT format the boot partition as this is one of the only few things which can brick your device while using cwm......
Click Thanks on above thread if it helped you.....
---------- Post added at 10:38 PM ---------- Previous post was at 10:01 PM ----------
Are you sure it works with clockworkmod recovery???
show_progress 0.1 0
format SYSTEM:
show_progress 0.2 0
show_progress 0.2 10
This script has two problems in my opinion:
1.AFAIK this type of script format(amend) is not supported by cwm now.
2.When editing with n++ it shows CR LF at end of each line......
and "carriage return" line code is used in windows while unix uses LF (line feed) for it's text.....so there should be LF only.....i think
Please correct me if I am wrong as i am just trying to learn here.....:fingers-crossed:
Click to expand...
Click to collapse
Sorry, I'm not the developer of that zip, I just got it long back from some other thread. Couldn't locate that thread, so just attached it again.
Anyway, it works fine with my ThunderG recovery, which has not given me any problems till date.
mihir287 said:
New release of same rom : Wipe cache and dalvik cache. (If any errors arise with the apps later you should do a full wipe)
Different rom : Wipe data/factory reset, cache, dalvik cache. Sometimes it is recommended to wipe /system too.
Click to expand...
Click to collapse
This right here.

[Q] Wiped Dalvik cache, now apps are gone... how to restore?

Posted this on Android Central, but the only answer I've gotten so far is "Upgrade to CM9" -- which isn't feasible on my device. Yet.
Anyway, here's my issue. I have CM 7.0.3 running on my MyTouch 3G Slide. Before you guys jump all over me for having an old CM7 release, the SYM key does NOT work in any releases above that. Since I actually use that key, I can't update. It's a known issue (see #4570 on CM bug tracker).
If this helps: I used data2ext to move dalvik cache to the sdcard.
[This part is important. I think.] CM7 has a history of wifi issues on the MT3G slide -- there's something weird with the tiwlan.ini, so the solution is to revert to the 6.x version. I did that, it fixed it, and then yesterday it went back to its old behavior. I went into the phone terminal and recopied the 7.x tiwlan to /etc/wifi to see if that would fix it. (E.g., this meant remounting /system to rw.) No go, so I went back to the 6.x tiwlan.ini. Still nothing.
Finally I went into recovery and deleted the cache and Dalvik cache in hopes it might force it to start working again. Good news is that the wifi seems to be working. The bad news is that all my apps have disappeared from the drawer. They're still on the device (visible in Manage Applications). I'm thinking the cache may have not rebuilt itself and therefore can't load any of the apps...?
I have access to CWM, but I can't get anything else to install on the device (e.g., TiBu). When I used adb to try and reinstall Titanium, it gave me this error: "Failue: [INSTALL_FAILED_DEXOPT]."
I'm at a loss. Any ideas?
Quick update: looks like my dalvik-cache moved itself back to /cache instead of /data. Searching on how to fix this... any leads are helpful! :laugh:

[Q] Adfree java.io.IOException Error on Samsung Admire

Hi, I have a Samsung Admire and have been using Adfree perfectly fine before. However, after upgrading Android from 2.3.4 to 2.3.6 to fix the WIFI error, I can't seem to get Adfree to work again.
I get the following error message when trying to install the Hosts:
java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
How do I get this app to work again?
Uninstall & reinstall. Try to clear cache & dalvik cache in recovery. Worst case scenario, I think, is to wipe everything and install from scratch.
post-mortem said:
Uninstall & reinstall. Try to clear cache & dalvik cache in recovery. Worst case scenario, I think, is to wipe everything and install from scratch.
Click to expand...
Click to collapse
I tried uninstalling, reinstalling, and wiping cache in recovery before, but to no avail. I didn't try wiping dalvik cache before. After uninstalling, wiping out cache and dalvik cache in recovery, and reinstalling, the error is still there.
I am not sure what you mean by "wipe everything and install from scratch". I would understand how to do that if it was on my PC, but not on my smartphone.
By that I meant, as a last-resort option, to completely wipe everything as if you're gonna flash a new ROM. Format everything through recovery, flash ROM, kernel (if applicable), gapps, whatever else. Then set up your google acct. & restore apps from titanium backup, or reinstall all apps from scratch.
BTW, you shouldn't restore Adfree, it should definitely be installed fresh from Google Play.
post-mortem said:
By that I meant, as a last-resort option, to completely wipe everything as if you're gonna flash a new ROM. Format everything through recovery, flash ROM, kernel (if applicable), gapps, whatever else. Then set up your google acct. & restore apps from titanium backup, or reinstall all apps from scratch.
BTW, you shouldn't restore Adfree, it should definitely be installed fresh from Google Play.
Click to expand...
Click to collapse
As much as I would like to give your method a try, it seems too complicated to do. First of all, I never format my phone before. Even though I know how to format a PC, doing the same thing on the phone seems to be new and unfamiliar to me.
Second of all, it seems to be quite a lot of troubles just to fix that error. I wonder if there is a manual method of removing the ads.
Ok, just to be sure you don't have a problem with su, go into the Superuser app, check for updates, and force an update even if there's no new version (it also makes sure the file has the proper permissions).
post-mortem said:
Ok, just to be sure you don't have a problem with su, go into the Superuser app, check for updates, and force an update even if there's no new version (it also makes sure the file has the proper permissions).
Click to expand...
Click to collapse
Yay! That was the problem. Thank you so much! Wow, AdFree app didn't get rid of most of the ads as it used to, but oh, well...it is better than nothing.

Categories

Resources