I am trying to edit an .xml file in settings.apk, i can't remember the name as im away from my computer, but i tried decompiling manually and recompiling and i jsut get force closes when i copy back to system\app. I also tried apk manager and get the same force closes. I did sign them .apk and also include the twframework.apk as a dependency when compiling/decompiling. Any tips as why i could possibly be getting all force closes? I removed touchwiz from system/app could this effect it?
I don't have experience with your specific case, but when it comes to removing touchwiz from system/app I have noticed problems. For one, when I select Airplane mode, phone lags and I get a force close error. Another, I experience longer (not considerably longer, but still longer) boot times. Tried various things such as factory resets, flashing touchwiz-less systems, but still got these error.s Both issues remedied by putting touchwiz back in system/app.
So yea, not directly answering your specific case, just saying it's possible since removing touchwiz seems to cause problems for myself.
Related
This isn't what I would call a troublesome thing, but I found it odd. I'm trying to learn all I can about Android's inner workings, so perhaps someone around here could clue me in on this behavior.
I decided earlier to tweak my SystemUI.apk. I pulled it, tweaked it, pushed it back, and it started into an FC loop. In retaliation, I deleted it, rebooted, and restored the TB copy. I tried my tweak again, pushed it back, and noticed no reaction from Android whatsoever. I took a peek at my /system/app directory, and saw that my SystemUI.apk was now neighbored by a com.android.systemui.apk that TB dropped in there.
This is where it gets a bit odd. For yucks, I deleted both apks, cleaned the DC, booted recovery, and dropped in a brand new SystemUI.apk extracted from the ROM I'm currently using. After rebooting, I had no status bar, TB reported it as not installed, and logcat complained about it missing.
So, I deleted my SystemUI.apk, cleaned the DC - it found one file - rebooted, restored the TB backup, rebooted, and all was fine. I renamed com.android.systemui.apk to SystemUI.apk, cleaned the DC, rebooted, and still no problems. I deleted SystemUI.apk, pushed a fresh copy from the ROM again, and still no problems.
That brings me to my question. Could anybody provide insight as to why Android was ignoring SystemUI.apk after having removed com.android.systemui.apk and rebooting?
When I installed the latest google music, I renamed MusicPlayer.apk to MusicPlayer.apk.bak, effectively uninstalling it.
I want to go back, as the default music player is the only one that's ever been capable of displaying the track title/etc on my Mazda's little display screen.
When I rename the file back to MusicPlayer.apk, nothing changes. Tried placing a clean copy of the stock MusicPlayer apk in /system/app, that didn't work either. Tried it using ADB, using a file explorer on the phone itself, nada.
Halp?
Confirm that the permissions are correct (rw-r-r), and reboot. Beyond that, idk.
Yeah, I did chmod 644 before rebooting. :-/
Reflash ROM without wipe?
Wow. This is a new level of stupidity on my part.
Somehow, it'd gotten hidden in my go launcher settings. it may have been there the entire time, for all i know.
Thanks to those who tried to help me. Clearly I'm beyond any sort of human intervention. Gonna go hide in a hole and try not to break things now.
Hello,
I am using cm7, but this is a general question about replacing files in roms. I have been working on an issue that involves opening the zip file and then edit and replace certain files. I have seen a few posts in the past where it says to replace certain files in a rom, but everytime that I do I get an error after flashing. After flashing and boots to the main screen that asks you to touch the android, I get an error that says "Sorry, the process com.android.phone has stopped unexpectedly" and the only option is to click on Force Close, but it just keeps coming back. Something is definitely not right with replacing files in a rom, but Im not sure if there's even a correct way. Im using winrar as everyone has mentioned. I have tried using the Fix Permissions option in the Clockwork Recovery also, but no luck. Only option is to reflash. Anyone have any ideas? Does the whole rom need to be recompiled?
aa
aa
After attempting the OGBatteryMod, my phone now has a black background, no notification bar, and no settings app. I am guessing there is a problem with SystemUI.apk and SecSettings.apk so I tried to reinstall them. However android fails to install them. The phone is rooted using exynos abuse. I have searched around and apparently this can be caused by flashing custom ROMS but I have done no such thing. A system restore might be necessary, but I would prefer not to if possible. Any help would be great!
FIX: Moved .apk files from folder "og" to system/app using root explorer. Mods: please remove this if needed
Using Rooted Samsung Proclaim:
(I have used both of the root kernels and the stock kernel)
I've read multitudes of online problems involving bootloops. I've even fixed one of my own a few months ago using adb. (In that case I renamed the framework-res.apk file because I was messing around with changing the emoticons, this turned out to be a terrible Idea, but easily fixed after about 12 hours of frantic trial and error.) I learned that ADB is quite awesome.
Anyway, I recently used System Tuner Pro to boil the stock Video Player after installing and uninstalling a few video players from the play store. I like to freeze most stock apps to see whether I really want to use them or not. I didn't pay attention to the toast which warned me that I might need to reboot for the change to take affect. So after I couldn't find the Video Player in my apps, I boiled it again. This time noticing the toast warning. So I rebooted. Now I'm stuck at the bootanimation loop.
I can still connect with adb from the bootloader and during the bootanimation loop. I have pulled most of the system files just to see if everything is still in there. I have also removed the VideoPlayer.apk file thinking the double boil had something to do with it. Still loops.
I've tried reinstalling the framework-res file that was still on my computer from the last time I had trouble. It installed just fine but still looping after reboot.
There must be some unresolved conflict during the bootanimation but I have no Idea which files to replace or reinstall. I have even wiped everything using the factory reset in the bootloader. I have attempted to wipe with adb but this always seems to give failures and permission troubles.
Any Ideas?
Well now I've really gone and messed things up. Pretty sure it's out of my realm of possibilities now.
After pushing my wife's (same phone) bin folder into mine i have lost all permissions due to system/bin/sh.
Now I can't do anything with adb except connect to the phone. So technically its all still there.
I just need to write over the bin with my original bin and then I might hopefully be back at the previous problem.
Also, it's looping at the Samsung logo now so I've definitely gone backwards.
This is what I get for messing with things that I don't fully understand.