Hey, I was trying to uninstall key.apk from JF1.5, by deleting the apk and its dalvik-cache, but that's just made my phone boot loop -_-
Can somebody tell me how I can repair this, without wiping?
If someone can install key.apk, and pull /data/app/com.htc.android.htcime.apk, and /data/dalvik-cache/[email protected]@[email protected] for me, I think I can fix it.
[Edit: Argh, nevermind, that didn't work. Does anybody know if I can adb install an app from recovery? ]
Related
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
Hey guys
Hoping someone can help me sort out my Galaxy Ace.
I've royally f**ked up my phone while trying to re-install stock email.
Followed some instructions and accidentally disabled execute rights to system/app folder using root browser in ROM Toolbox.
Phone is now in a boot loop.
I've updated from sd card to installed Clockworkmod recovery.
So far I've tried wiping cache and dalvik cache with no joy.
Also tried fix permissions, still nothing.
Hoping you can guide me through a fix for this.
Would greatly appreciate your help.
Cheers
Paul
factory reset it
tried that - not working either
mitchst2 said:
Hey guys
...accidentally disabled execute rights to system/app folder using root browser in ROM Toolbox.
Click to expand...
Click to collapse
Show us the instruction.
What exactly did you do?
Can't you connect your phone to the computer, maybe during recovery.
Open adb shell, and fix the permissions ?
chmod +x /system/app ?
Might have to remount system readwrite before that.
Hi there,
I'm using Revolution HD 6.5.1 XE at the moment and it worked quite fine. But since I plugged in to a Laptop without any drivers for the Sensation to copy some data I get the pop up which says "Process Android.process.acore has stopped unexpectedly". It pops up right again after pressing OK.
I took some researches here and found out that the codeline (chmod 666 /data/data/com.android.providers.contacts/files/*) I entered to see the facebook pictures in the contact list is causing this problem.
In THIS thread someone says that I have to fix permissions and wipe cache/dalvik. So I deleted the su permission of the terminal and wiped cache and dalvik, but it still pops up right after starting the device.
Can someone help me please?
Thanks in advance!
greetings
Phil
Clear Cache in recovery.
Also, if you'd have searched the ARHD thread you would have found the fix.
I already said that I wiped cache and dalvik. So I tried today again to wipe just the cache but it didn't change anything.
I really searched for that problem in the ARHD thread and found just what I wrote in the first post.
I wonder whats exactly the meaning of fix permissions. Do I have to delete the root permissions?
does nobody have an idea?
Reboot into Recovery > Select Fix Permissions.
I wiped cache and dalvik cache, then installed the ZIP -- and after more than five minutes, the screen is still on "Installing update..." How long does this take?
Ten minutes later, I took the battery out to hard reboot the phone. It all came back OK (took a while because it had to build back the cache), but I'm not sure if the update took.
I did notice this error:
E:can't mount /dev/block/mmcblk1p2
(File exists)
But then it said it did delete the dalvik cache, so I thought it was all right, but maybe it didn't quite work. I'm using System Recovery to go into Recovery GFAN.COM V2.5.1.8. How do I successfully wipe the dalvik cache?
Are u using Full Touch Recovery?
If yes - change to normal recovery, I had this problem and now it works.
If no - I don't know, maybe someone other helps you
ch3mn3y said:
Are u using Full Touch Recovery?
If yes - change to normal recovery, I had this problem and now it works.
If no - I don't know, maybe someone other helps you
Click to expand...
Click to collapse
No, I'm not using FTR. I'm not even using ROM Manager -- I use System Recovery (an apk I found). It's the Moto A4 bootstrap that's based on Koush's CWM Recovery.
There is a problem with my signing on linux, I'll try and get a quick fix for the .zip tonight... until then:
1. Push files to correct folders.
2. Fix permissions to rw-r-r
3. Reboot
EDIT:
This is for the x2 right?? You should post in the Droid x2 Q&A section if so. It's not for other phones, only the Dx2.
Regardless, Problem fixed.
Are you saying I should unzip the files and then change their permission? What you describe, rw-r-r, is chmod 644. So I should extract, chmod, re-zip, then run the flash update? And yes, this is for the X2.
No l, just redownload, I fixd the problem.
Tapin' the Talk on my HTC Trophy
Just re-downloaded it, but nothing's different -- still having the same issue where it freezes at Installing update. I noticed there are two directories off of root now, Dx2_GB_BatteryFix and META-INF -- is that correct?
I am having the same issue with the zip file. Although I wouldn't say I am a noob, pushing these files is something new to me. If the zip cannot be properly signed or there is difficulty unforeseen in being able to do so, can someone explain in some detail how to push this?
Many thanks!
EDIT: So I figured it out using File Expert. Copied and overwrote battd to system/bin and libbattd.so to system/lib and corrected the permissions as you stated, rebooted and wiped cache and dalvik cache. All seems good now! Thanks for the fix.
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.