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!
Related
i attempted to replace most of the .apks in the system app folder with the same .apks from an ealier version of the rom (because i prefer black to blue/black). i replaced them in the .zip before i flashed it, hoping it would work.. but it didnt.. in the recovery menu it says:
....
verifying update package...
e:wrong digest:
system/app/browser.apk
e:verification failed
browser was one i replaced. how do i make this work? i dont want to use root explorer to manually replace each ****ing thing, and i have no patients for adb. i must need to sign the package or something? i never unpacked anything, just replaced some contents.. thought id be fine..
on a related note there may be more issues to come. unzipped the framework-res.apk to my computer, renamed it .zip, went inside and replaced the battery icons, renamed it back to .apk and replaced the modified file in the rom. who knows what chaos i might have caused there.. if you know what to expect and how to fix it please feel free to help!
if it matters at all, the rom im modifying and flashing is nonsensikal 9.5 black/blue, the system apps came from version 8.2 black, and battery icon .pngs came from 5.4 black.
Id try and resign the whole rom after you make your changes it should be just fine
you cannot simply replace the apks in the zip, then flash. after replacing, use one of the following methods:
if you use linux, use EasySign (http://android.grdlock.net/index.php?&direction=0&order=&directory=HTC Droid Eris/Extras) or the Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246).
if using Windows:
Use AutoSign (http://androidforums.com/developer-101/8665-how-signing-roms.html).
Thanks. I'll get on the computer and give it a shot.
Sent from my nonsensikal froyo using XDA App
if you've unzipped the framework-res.apk then none of this will work anyway. You need to pull the images out of the old framework-res.apk and drag and drop them back into the new framework-res.apk without unzipping it. You shouldn't even need to rename it to zip. Just open it with a program like 7zip without unzipping and drop the png's in the correct folders. Then you can put the .apk back in the rom and resign from the links directed above.
Oh it all worked fine. I never unzipped framework, just extracted it from the Rom and renamed it, then replaced files, renamed back to apk, and replaced in original .zip. it worked great.
To achieve full 9.5 black I have to copy all of the previous versions (black) framework .pngs to the new Rom though.
I think the file is like, drawable-mpdi or something. Not landscape or non. I don't really know.. not in right frame of mind
Sent from my nonsensikal froyo using XDA App
I'm trying to modify Email.apk. I'm currently running stock 3.1 from http://forum.xda-developers.com/showthread.php?t=1154492
Here's what I did:
1. Extracted Email.apk from update zip and dumped using APKTools.
2. Made my modifications - specifically I'm editing a .smali file with my desired changes.
3. Rebuild Email.apk using APKTools.
4. Renamed existing Email.apk and Email.odex for backup.
5. Copy my Email.apk to system\app and set permissions.
6. Reboot into CWM and wipe davlik cache (not sure if this is required).
7. Reboot.
Now the email app no longer exists in list of applications.
What steps am I missing?
If I'm not mistaken You can't edit odexed firmware!
You must first flash a deodexed rom and then change it to your heart's desire.
I guess I'll have to try deodex the rom myself then.
Thanks!
I'm now using Virtuous Picasso which is deodexed and am now able to modify /system/app applications.
However I think the actual problem was I forgot to sign the modified Email.apk. (Also had to sign Exchange.apk also as they need to be signed with the same certificate)
I think as long as the device is rooted you can replace /system/app applications?
See my signature for signing - piece of cake!
If you have a good and clear deodexing tutorial I'd appreciate it
These are the steps explaining you how to create a custom firmware based on the SmartQ firmware releases.
Warning : Creating a firmware and changing the files may cause your device to stop working, I won't be held responsible for any damage caused by this.
Creating a firmware file is actually very easy, not much is involved and nothing more than some basic software is required to create the files. If you don't understand the steps below than maybe you shouldn't fiddle around with this and wait for other members to create these.
There is nothing explained here about the flashing itself, as I will create a seperate How-To about that with pictures explaining the steps of the recovery.
Also there is nothing explained about kernel building itself, I have no clue how to do that and I'll leave that up to SmartQ.
Use the instructions below to make your own Firmware file with the software you want in it and make all configuration changes you want.
1. If you haven't already download the latest official firmware from SmartQ.
2. Extract the zip file. You then have 2 files, a Chinese .txt file with the release notes. And a file called "SmartQT15".
3. Rename the file "SmartQT15" to "SmartQT15.zip". Accept any warning about making the file useless, as in fact you are making it useful.
4. Extract the zip file. Then you end up with 4 new folders :
"boot" - This will be the files required for booting the OS. And possibly the recovery.
"data" - The user apps and data are in this folder.
"META-INF" - The certificate SmartQ used is in this folder and also the update script that manages the update process.
"system" - The actual Android OS.Stay clear of the boot folder, unless you are 100% sure about what you are doing, this may cause a bricked device without the possibility to reflash.
Add apps to the app subfolder in the data folder. Make sure if you do add apps to set the permissions in the update script file and make changes accordingly. The data-extra.tar file is extracted during the update process.
In the "META-INF\com\google\android" folder you can find the updater-script file, you can edit this with Notepad++. This file tells the CWM based recovery what to do and in this file the permissions are set for apps. Also is it required to edit this if you want to create a pre-rooted firmware.
Be carefull what to change in the system folder it can cause your OS not to boot, but it should be no problem to revert back to another build that did work previously as you didn't touch the boot folder and the recovery should work normally.
Once you have made all the changes you wanted to do. You follow the steps back.
5. zip the 4 folders backup using Winzip or WinRAR, whatever suits you best (You can use compression, I tried out Fast, Normal, Good compression in WinRAR and the firmware flashed without problems). Make sure you have the 4 folders in the "root" of your zip file. Use for filename "SmartQT15.zip"
6. Rename the "SmartQT15.zip" file to "SmartQT15" and accept any warning again about changing the extension of your file.
You have now created a flashable firmware file for the SmartQ Ten3 T15.
Copy his file to the root of an empty microSD card and follow my How-To about flashing Custom Firmwares.
Don't use the guide to flash original SmartQ firmwares as this won't work, by changing the firmware package you break the firmware signature and the recovery will check for this during flashing.
Signature checking can be disabled though in the recovery as I will explain in the new How-To.
If you have any questions feel free to post below and I'll do my best to answer them, all the above is based on my experience and from what I could find out on the Internet.
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.
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!