Hey Guys,
I have been attempting to mod my framework-res.apk to try and add a percent battery icon (unsuccessfuly so far). Here is my issue, after finding that my modded framework file isnt working properly, I go to try and restore the original. After restoring the original I still get tons of FC's and the only way to get things back to normal is to restore my backup from CWM.
The method I am using to replace my framework-res.apk is to use a root explorer (ES File Manager) to copy the file to /system/ then from there I modify the permissions and then move the file to the framework folder, overwriting the existing file. After this, I reboot the phone.
My question is, why is my original framework-res.apk file causing force closes? It is starting to make me think that even my modded files are ok, but that the issue is arising in the manual transfer.
Sorry if the answer is posted elsewhere, I googled and was only finding issues with the apk not being compiled correctly, but that shouldnt be an issue with the original apk.
*EDIT* I figured it out. It appears it was because Jkay Deluxe was installed. I decided to reflash the rom and try with a fresh copy of the framework-res.apk and everything appears to be working now.
Related
(I'm new at this, any help would be appreciated)
I'm using Daneshm90's (very awesome) APK Manager to mess around with my framework-res.apk file. I've sucessfully reskinned some pngs and changed some xml files and stuff like that.
Why does the following cause a bootloop?
1) Decompile Framework-res.apk
2) Make a copy of res\drawable\btn_default_small.xml and rename it btn_default_small2.xml
3) Change the background of something to android:background="[a]drawable/btn_default_small2"
4) Compile\flash to phone etc, watch it bootloop
(please note: [a] is really the email 'at' symbol, the forums get mad at me for using it)
I can edit existing files just fine, but whenever I try to add and use a new file everything grinds to a halt, even if its just a copy of a working 'stock' file. What am I missing? Is there a list of files somewhere I need to add my new xml file to? Should I be building from source instead of using apk manager?
So i have been attempting to create a battery mod using some of the ones for the i9100 and i have been failing. I'm currently running Cognition V2. I only want the battery icon to change. and i know the files are in the framework-res.apk in the drawable-hdpi. I was told i can put all the image files in a modified Framework-res.apk and put in the framework folder. then rename the one the phone is using and then rename the modified one to exactly what it is suppose to be. It works for him but when i do it i instantly get FC when i change the name of the file. then after a reboot the correct battery icon is there but i get lots of FC's including the all important android.phone.com. So i must be doing something wrong. i was conversing in the Cognition section but since its off topic i moved it here. any help and tips are appreciated.
thejanitor86 said:
So i have been attempting to create a battery mod using some of the ones for the i9100 and i have been failing. I'm currently running Cognition V2. I only want the battery icon to change. and i know the files are in the framework-res.apk in the drawable-hdpi. I was told i can put all the image files in a modified Framework-res.apk and put in the framework folder. then rename the one the phone is using and then rename the modified one to exactly what it is suppose to be. It works for him but when i do it i instantly get FC when i change the name of the file. then after a reboot the correct battery icon is there but i get lots of FC's including the all important android.phone.com. So i must be doing something wrong. i was conversing in the Cognition section but since its off topic i moved it here. any help and tips are appreciated.
Click to expand...
Click to collapse
The key is to move the modified framework-res apk (correctly named and ready to move) into system (not in a subfolder), change the permissions to the appropriate ones there (sd card won't let you do them). I'm pretty sure the permissions are rw-r-r. They have to match the permissions of the file it's replacing. This is why you get the FCs. From here, move it into the framework folder, it'll prompt if you want to replace, hit yes or ok. Reboot.
After rooting via Indirect's method, many sub-menus are not readable due to the text being the same color. Has anyone found a standalone fix for this? (I noticed snowball mod addresses it but am already rooted).
there is a partial fix available, but as of now it isn't practical to implement.
btw, there is a discussion about this later down the board. I can't link to it right now. I asked the same question, and I was told to use search instead of the answer and a link to the discussion. I wanted to let you know better than I was told what was going on about this issue.
From what I understand this is a non-trivial problem to solve.
The snowball root method has the fix for this, but its injected while in the root process, but i have read that the framework-res.apk provided in the snowball-mod.zip contains the fix (replaced files) and apparently by just replacing this .apk to your existing system/framework/framework-res.apk it should do the job. However i haven't found someone that has tested this yet and i dont have my nook yet so if you want to give it a try DO IT AT YOUR OWN RISK. Dont worry if it doesn't work you may get bootlops or FC's nothing major and by doing the "magic card" method for go back to stock you be fine again.
I will attach the framework-res.apk if someone wants to give it a try and please report back the results.
*NOTE: You need to uncompress first and inside you will find the .apk
Path: system/framework/
1. Copy the .apk to your sdcard
2. Using a file explorer (eg. root explorer, es file explorer) navigate to your sdcard find the .apk you just copied and copy it
3. Go back and navigate to system/framework/
4. rename the existing framework-res.apk to framework-res.apk.bak
5. immediately hit paste
6. reboot
7. report back
Veronica
lavero.burgos said:
The snowball root method has the fix for this, but its injected while in the root process, but i have read that the framework-res.apk provided in the snowball-mod.zip contains the fix (replaced files) and apparently by just replacing this .apk to your existing system/framework/framework-res.apk it should do the job. However i haven't found someone that has tested this yet and i dont have my nook yet so if you want to give it a try DO IT AT YOUR OWN RISK. Dont worry if it doesn't work you may get bootlops or FC's nothing major and by doing the "magic card" method for go back to stock you be fine again.
I will attach the framework-res.apk if someone wants to give it a try and please report back the results.
*NOTE: You need to uncompress first and inside you will find the .apk
Path: system/framework/
1. Copy the .apk to your sdcard
2. Using a file explorer (eg. root explorer, es file explorer) navigate to your sdcard find the .apk you just copied and copy it
3. Go back and navigate to system/framework/
4. rename the existing framework-res.apk to framework-res.apk.bak
5. immediately hit paste
6. reboot
7. report back
Veronica
Click to expand...
Click to collapse
i can confirm that this works. the only thing you would need to double check before replacing the framework-res.apk is to check the permissions and make sure they are correct because once you replace the apk, the NT auto reboots and if you did the process correctly it will boot up normally, otherwise you will be stuck in an infinite boot loop...
The fix did not work for me I made sure the permissions were the same but my go launcher settings are still white on white
Montisaquadeis said:
The fix did not work for me I made sure the permissions were the same but my go launcher settings are still white on white
Click to expand...
Click to collapse
If you got the snowball bootanimation then the framework-res.apk applied just fine.
However, as I may have mentioned above, but have certainly mentioned elsewhere: the white-on-white fix in snowball-mod is a stop-gap for one specific set of menus (and could even cause black-on-black for those menus!)
We cannot fix all white-on-white, and black-on-black problems without entirely retheming just about everything in the framework-res.apk, which involves the backgrounds and the texts.
As noted above: "this is a non-trivial solution".
Does the snowball animation say hack by Barnes & Noble?
Edit Looks like the modified framework-res.apk file is what is causing the nook not to charge while its on as my nook has stopped charging when its on which sucks as I use the nook constantly through out the day.
Well, if you want to just spill the beans like that... yes.
Just wanted to make sure it had taken as I havent payed any attention the boot animation in the past
i installed the transparent statusbar mod in my xperia mini st15i.. i just want the original one back. i don't have a nand backup. can someone post the related apks here and tell me how to install them if a specific procedure is to be followed.
gandhar said:
i installed the transparent statusbar mod in my xperia mini st15i.. i just want the original one back. i don't have a nand backup. can someone post the related apks here and tell me how to install them if a specific procedure is to be followed.
Click to expand...
Click to collapse
Someone with mini have to help you. But since no one replying, and to save your time from searching all over the web;
To know which apk that has been modified, open the mod that you have applied using archive apps (winrar should do if you are in windows) and see what apk is inside (generally it should be framework-res.apk and/or SystemUI.apk)
To revert back, one of the way is to extract that apk from stock fw file, copy to your /system/ then change permission rw-r--r-- (if you dont know what it means, just refer to any apk inside /system/app/ permission's, they are all the same generally for /system/app/ and /system/framework/ ). Then, move it to appropiate folder replacing the current file (SystemUI.apk into /system/app/ for example. Better to replace systemui.apk first before framework-res.apk to avoid unexpected fc in the process)
Once done, reboot.
Other ways, ask anyone to make cwm compatible zip file for you to revert back to original or wait for someone to post the apk's here for you.
Thats a very good lessons actually, do a backup first before doing/modifying anything. Dont just simply flash any zip file, see first whats inside, backup whatever files that is affected by that zip to your sdcard is the fastest way (but not 100% reliable compare to make a backup in cwm.
Anyhow, good luck. cheers fren.
Sent from my SK17i using XDA App
feed3 said:
Someone with mini have to help you. But since no one replying, and to save your time from searching all over the web;
To know which apk that has been modified, open the mod that you have applied using archive apps (winrar should do if you are in windows) and see what apk is inside (generally it should be framework-res.apk and/or SystemUI.apk)
To revert back, one of the way is to extract that apk from stock fw file, copy to your /system/ then change permission rw-r--r-- (if you dont know what it means, just refer to any apk inside /system/app/ permission's, they are all the same generally for /system/app/ and /system/framework/ ). Then, move it to appropiate folder replacing the current file (SystemUI.apk into /system/app/ for example. Better to replace systemui.apk first before framework-res.apk to avoid unexpected fc in the process)
Once done, reboot.
Other ways, ask anyone to make cwm compatible zip file for you to revert back to original or wait for someone to post the apk's here for you.
Thats a very good lessons actually, do a backup first before doing/modifying anything. Dont just simply flash any zip file, see first whats inside, backup whatever files that is affected by that zip to your sdcard is the fastest way (but not 100% reliable compare to make a backup in cwm.
Anyhow, good luck. cheers fren.
Sent from my SK17i using XDA App
Click to expand...
Click to collapse
i got it from a friend, thanks anyway.
Hi, I already took a look around this forum and searched for this problem on Google, but i can't find an useful solution that is not "reinstall the ROM"
and i would like to avoid it.
I'm trying to edit my SystemUI.apk, to make the status-bar background back to black. (right now it's trasparent and it's driving me crazy)
with apktool i installed the framework-res.apk and the systemui.apk, then i extracted the systemui.apk, modified it, i placed inside the resources.arsc then recompiled it, i took the apk into systemui/dist and placed back on my cellphone, then i replaced the original SystemUI.apk with fx root explorer and my jiayu rebooted by himself.
Then I saw that the status bar, notifications, wallpaper, everything, was disappeared, i can't toggle anymore my smartphone to the pc.
There was a backup of the systemui.apk, systemui.odex and framework-res.apk, so i placed back the systemui.apk and the systemui.odex (like always).
Then i rebooted the smartphone manually but the wallpaper/statusbar/etc. (all the informations inside systemui.apk) still won't load.
I tried replacing them again, shutting down, remove the battery, rebooting, replace the framework, i tried everything that was coming to mind to me.
On the internet i found a way to solve this problem with ADB toggle, but I can't find a way to make it work: it tells me that the application is installed on the SDCard where i don't even have an SDCard attached.
and i'm not able to install the SystemUI.apk using Terminal emulator either (another solution found on the internet).
Is there someone that knows how to solve this problem without installing the rom again? i would like to avoid the problem to put back in all of the stuff i have on my smartphone... there's maybe a way to regenerate the contents inside system/app without the entire rom.
Putting that stuff back in manually won't work...
-----------------
EDIT: Solved... Please delete this post and sorry for the troubles... The solution was easy: application list -> systemui -> delete updates and cache -> reboot.
Solved...