So i'm trying to modify an image in framework-res.apk but every time I try to push in the new one I get stuck in bootloops and have to format. I have tried a bunch of ways of accomplishing this from using adb wirless to push to the framework folder, to using CWM to install it inside a zip file but they all just cause bootloops. Also I found that if I were to copy framework-res.apk to somewhere else and then not touch it and copy it back, it would still cause a bootloop! So basically the act of trying to replace the current apk is always causing bootloops. Anyone find a fix for this?
There is something wrong with the modification you make to the framework-res.apk which makes it corrupt. Normally, you can copy the file from SD card into /system/framework/ and the NST would just restart. Also mind the rermissions of the file, just make it the same as all the other files in that directory.
To save time when you brick your device, use noogie instead of format. Just copy the old framework-res.apk back in (you should previous make a back of it).
For modification, use the APK-Multi-Tool. This might help you avoid some problems with repackaging.
Related
I am having issues with framework-res.apk.
I make some minor changes and add and replace these files into framework-res.apk using WinRar.
Then copy this into the update.zip file and
install from sdcard using clockworkmod.
But then my nookGL won't reboot, and I end up having to factory reset.
After the factory reset the changes I put in the framework-res are now showing up and working fine.
I then need to go through the process to root the nook etc.
This is a very long winded way for some minor changes.
Is there something I am doing wrong?
I am now very hesistant to try any more changes, even though I would love to, as I really don't want to have to go through the whole process again.
Any suggestions?
Framework.res has to be signed with the system signature.
You can copy over the original META-INF directory (most of the time) when you repack it.
Your problem could be one of three things:
1) You repacked it without the original signature.
2) You repacked it with a new (personal or debug) signature.
3) You repacked it with the original signature but you modified something important (like AndroidManifest.xml).
If you want to get heavily into mods you should resign your whole system with either the debug or your personal signature.
Yes! Thank You, Renata! That was it - problem solved!
Hey guys, just wondering how I go about making a flashable zip? Basically I edited my build prop and now my phone wont turn on, I don't want to go and have to wipe my phone as that's just a huge mess about. I did a backup of my build prop and copied over to my computer before editing so I do have the original. I'm rooted with TWRP installed, I've tried to sort it through adb when connected in recovery but the driver wont install so that's not an option at the minute. As I have the original build prop I wanted to know if it's possible to make a flashable zip so I can just replace the broken file with the working one? Cheers guys.
Daley87 said:
Hey guys, just wondering how I go about making a flashable zip? Basically I edited my build prop and now my phone wont turn on, I don't want to go and have to wipe my phone as that's just a huge mess about. I did a backup of my build prop and copied over to my computer before editing so I do have the original. I'm rooted with TWRP installed, I've tried to sort it through adb when connected in recovery but the driver wont install so that's not an option at the minute. As I have the original build prop I wanted to know if it's possible to make a flashable zip so I can just replace the broken file with the working one? Cheers guys.
Click to expand...
Click to collapse
Pretty easy: Copy the unmodified build.prop file to an SD card. Put said card in the phone. Boot to TWRP. Mount both System and SD Card. Then go to ADVANCED and FILE MANAGER. From there you can rename the modified one in /system, copy the original file from the SD card, and then set its perms correctly.
Your phone should boot properly then.
Hope this helps!
Like some people, I got really annoyed with the huge mouse cursor that appears when using the stylus in custom ROMs. After some tinkering, I finally found something that works.
DISCLAIMER: Try at your own risk. Bootlooping may occur, but can be easily solved by just flashing your current ROM over it. Still, make backups just in case.
Extract framework-res.apk from your current ROM (under /system/framework)
Use apktools to decompile it (this is a good tutorial http://forum.xda-developers.com/showthread.php?t=2213985)
Edit pointer_arrow.png under /res/drawable-mdpi using either GIMP or powerpoint to whatever you want your cursor to be (make sure you keep the same dimensions. I just replaced mine with a ridiculously small dot)
Use apktools to compile it back, BUT DO NOT SIGN IT (as what the tutorial says)
Open the original and newly compiled framework-res.apk in 7zip, and copy over META-INF and androidmanifest.xml from the original to the new one
Copy the newly compiled framework-res.apk to your phone, and change permissions to rw-r-r (found that it's better to move it to your root folder before changing permissions)
Replace the existing one with the new one
Reboot
Hope this helps!
So I rooted my device, hten followed a guide, that Instructed me to replace two files in the system/framework folder, services.jar and services.odex, i backed them up, but like a fool i backed them up in the same folder, which i can't access, I can restore from CWM and i was actually hoping someone had a system recovery that i could borrow, since i can't seem to figure out how to change the files back within my cwm backup.
callen2011 said:
So I rooted my device, hten followed a guide, that Instructed me to replace two files in the system/framework folder, services.jar and services.odex, i backed them up, but like a fool i backed them up in the same folder, which i can't access, I can restore from CWM and i was actually hoping someone had a system recovery that i could borrow, since i can't seem to figure out how to change the files back within my cwm backup.
Click to expand...
Click to collapse
Okay, slow down. You can fix this. There are only a few steps:
1. Download the stock odexed rom. You can find it here: https://www.androidfilehost.com/?fid=23622183712466565
2. Extract the stock rom.
3. Navigate to the system/framework folder
4. Copy services.jar and services.odex to your phone (download folder or anywhere on your sdcard is fine)
5. Since you are rooted, you can use a root file explorer to copy those files to your system/framework folder on your phone. Locate the two files you copied from the stock odex rom on your computer. Paste these into system framework, and overwrite the two existing files (you can use ES file manager or other root browser to accomplish this)
That's it! There are many other ways to do this, but this is probably the simplest.
I'd just flash a custom rom with hotspot though
I edited the platform.xml file to try to get read/write permission for the sd card, but I managed to mess up the platform.xml file. Now, the tablet bootloops a couple of times, then goes into TWRP. I'm trying to figure out how to fix or replace the platform.xml file. When I use the file manager in TWRP, I can't find the platform.xml file. It's supposed to be in /system/etc/permissions/platform.xml but that location doesn't exit. Does anybody have a suggestion about how to get this fixed? Source files or just a clean platform.xml file would probably do the trick.
Any suggestions appreciated.
================================
edit: Never mind: I found the file and used TWRP file manager to fix it.