In a trying to build Hebrew translated rom I was trying to to decompress my atrix system.apk but using apk manager but I'm having an errors over and over again and decompressing fails.
Any lead from devs will be helpful.
Sent from my Atrix 4G using XDA Premium App
You will more than likely have to decompile using option 10 (using dependencies). Are you pulling and including dependency files when you decompile?
You will have to post more information about your error before anyone can help you out. Sorry ;/
i get this error: "An Error Occured, Please Check The Log (option 21)".
when i'm trying option #10 it asks me to drag some file, i only want to modify the strings, so which file should i drag to the window?
log file: http://pastebin.com/AtnK5EbV
Related
I'm trying to edit framework-res.apk so I can theme my rom. Are these the correct steps?
pull framework-res.apk from my phone
decompile the apk
make the changes
rebuild the apk
sign
zipalign
push apk back to device
I'm not too sure on this method as after I pushed back my modified apk, I get a load of force close errors
Any advice would be welcome
don't sign and don't zipalign and all are fine
I tried without sign and zipalign but the rom wouldnt boot. If I sign, I get force close errors
Does the rom need to be deoxed?
How is your process to decompile and recompile what tools do you use
vibez said:
I tried without sign and zipalign but the rom wouldnt boot. If I sign, I get force close errors
Does the rom need to be deoxed?
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Is this an ODEXed ROM or a deOXEDed ROM? You can't mix and match. If you're not ODEXing any APKs after you've modified them then you need to make sure all APKs are deOXEDed.
setenza01 said:
How is your process to decompile and recompile what tools do you use
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I use apk manager to decompile and rebuild
Benjamin Dobell said:
Is this an ODEXed ROM or a deOXEDed ROM? You can't mix and match. If you're not ODEXing any APKs after you've modified them then you need to make sure all APKs are deOXEDed.
Click to expand...
Click to collapse
It is a stock rom but there is no framework-res.odex does that mean it doesn't need deodexing even though there are odex files for every other apk in my system folder?
maybe this little monster is some help to you:
http://forum.xda-developers.com/showthread.php?p=7377678#post7377678
FadeFx said:
maybe this little monster is some help to you:
http://forum.xda-developers.com/showthread.php?p=7377678#post7377678
Click to expand...
Click to collapse
Nice app but this theme also needs .xml changes which this app doesnt support
ok, i put him a note in his thread about the xml changing issue, we will see what hes answer will be...
edit:
also this software could do the trick: http://android.modaco.com/content/t-mobile-pulse-pulse-modaco-com/302404/ande-android-design-editor/
I've been playing around a little more today and it seems the issue is that no tool can rebuild the xml files correctly, they seem to be compressed/encoded.
Has anyone been able to edit an xml file in framework-res.apk and have the phone read it properly?
vibez said:
I've been playing around a little more today and it seems the issue is that no tool can rebuild the xml files correctly, they seem to be compressed/encoded.
Has anyone been able to edit an xml file in framework-res.apk and have the phone read it properly?
Click to expand...
Click to collapse
Refer to my signature. Apk manager.
Edit : just read ur op.
Never sign the system apk's. Simply keep the original signatures intact and after recompiling them, re-include them.
So here are the rules u must follow :
If u've modified the manifest.xml, u must stop core, push the apk, start core or push the apk while in recovery.
If u've modified anything else, a simple push / reboot will do the trick.
Note, u cannot flash a modified system apk the first time (as in on a clean boot), u must flash the original rom, let it build the dex's and then flash ur modified apk.
Daneshm90 said:
Refer to my signature. Apk manager.
Edit : just read ur op.
Never sign the system apk's. Simply keep the original signatures intact and after recompiling them, re-include them.
Click to expand...
Click to collapse
Hi, I am already using apk manager but the xml files it creates do not seem to work.
To prove this, I have done a test. See the attached xml files,
original_stat_sys_battery.xml was extracted from the original framework-res.apk
I then used apk manager to decompile and then recompile the same apk without making any changes.
recompiled_stat_sys_battery.xml is this recompiled file
I then opened up both files and they look different to me
vibez said:
Hi, I am already using apk manager but the xml files it creates do not seem to work.
To prove this, I have done a test. See the attached xml files,
original_stat_sys_battery.xml was extracted from the original framework-res.apk
I then used apk manager to decompile and then recompile the same apk without making any changes.
recompiled_stat_sys_battery.xml is this recompiled file
I then opened up both files and they look different to me
Click to expand...
Click to collapse
That shouldn't concern u. Apktool's method of rebuilding the apk/arsc file is slightly different than how android originally builds an apk. What should concern u is if the apk simply works. Now when u decompile the apk, can u check the log to see if it reports of any missing resources, if it doesn't ur fine. So decompile the apk, make ur changes, recompile the apk, move the original meta-inf folder into ur new apk and push it to ur phone following the guidelines in my previous post. if it causes problems, post ur log and i'll take a look.
Ok this time I have added meta-inf to the new apk, pushed it to my phone and the phone hangs on boot.
Here is my log
--------------------------------------------------------------------------
|08/08/2010 -- 18:36:30.87|
--------------------------------------------------------------------------
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the path specified.
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
'adb' is not recognized as an internal or external command,
operable program or batch file.
Could Not Find C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\place-apk-here-for-modding\../place-apk-here-for-modding/repackaged.apk
Could Not Find C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\place-apk-here-for-modding\../place-apk-here-for-modding/repackaged-signed.apk
Could Not Find C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\place-apk-here-for-modding\../place-apk-here-for-modding/repackaged-unsigned.apk
The system cannot find the file specified.
I: Loading resource table...
I: Decoding resources...
I: Copying assets and libs...
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'keyguard_password_attempts_count_pin_code' has no default translation in C:\Documents and Settings\Lee\Desktop\Apk_Manager_4.8\other\..\out\res; found: fr ko
I: Building apk file...
Click to expand...
Click to collapse
Oh lol i meant the log of ur phone.
Use adb logcat
lol ok, at which point should I run logcat - after the hang or as soon as I switch the phone on?
vibez said:
lol ok, at which point should I run logcat - after the hang or as soon as I switch the phone on?
Click to expand...
Click to collapse
When u switch phone On.
Ok here you are
vibez said:
Ok here you are
Click to expand...
Click to collapse
Heres ur culprit
Code:
java.lang.SecurityException: META-INF/MANIFEST.MF has invalid digest for AndroidManifest.xml
Now seems u modified the androidmanifest.xml ? If u didn't then heres my recommendation, copy over the original androidmanifest.xml from the original apk.
Hi all,
Trying to mod the framework for the first time.
I have no problem replacing the png. But when i try to modify the xml, i get bootloop.
I used the apk manager (4.9) to decompile the apk, then edit one xml before i recompile. I did notice that the recompiled apk is at least 2MB smaller than the original.
Am i missing a step here?
Sent from my GT-P1000 using XDA Premium App
Hi
yap ,,,the generated apk is unsigned...and no sign for system apk..so you have to copy by drag & drop the following files from the unsigned apk onto the original apk via WinRar and choosing ZIP archive format, NORMAL compression method.
- resources.arsc file
- res folder
- classes.dex file if exisit in the non-system apks
hope that help
good luck
Galaxyer said:
Hi
yap ,,,the generated apk is unsigned...and no sign for system apk..so you have to copy by drag & drop the following files from the unsigned apk onto the original apk via WinRar and choosing ZIP archive format, NORMAL compression method.
- resources.arsc file
- res folder
- classes.dex file if exisit in the non-system apks
hope that help
good luck
Click to expand...
Click to collapse
Ah,
I was thinking this as a possible workaround so it looks like it is thr solution?
Just a confirmation, if i change the battery_charging.xml, then i should compile, then extract out the battery_charging.xml from the recompiled framework-res.apk and insert into the original, signed framework-res.apk?
Sent from my GT-P1000 using XDA Premium App
I tried taking the compiled xml ( that defines the animation of battery charging icon on the status bar), put into the original framework-res.apk, and end up with non existent icon for the battery charging. Everything else remains working though.
What could have gone wrong?
Sent from my GT-P1000 using XDA Premium App
Hey,
Every one knows the problem: ran out of internel memory... I heard about something like edit the androidmanifest to let android install the app on sd unrooted, and without SDK, all stock.
Only, how do i edit the androidmanidest? I tried this: go with Astro file manager into the .apk file, and open the androidmanifest.xml file with xml editor, but it says error: unreadable. How can i change the manifest? (then i finely can install minebuilder)
Thanks in advance, but i dont want to root, SDK, or run costum rom
Sent from my GT-S5570 using XDA App
No ane that can answer?
Sent from my GT-S5570 using XDA App
I have a GT-P1000N with the factory default rom, installed CWM Recovery using Heimdall and work perfect, i can enter in recovery, wipe data and cache, but when try to install the rom cm-9.0.0-p1n.zip (get.cm /get/jenkins/5817/cm-9.0.0-p1n.zip) a message saying that an assertion ocurred with the model and cannot continue
I try to do the same with cm10 fro Humeros but with the same assertion problem.
Any help? Any idea?
You can remove the assert lines from updater script.
(META-INF/com/google/android/updater-script)
If on Linux, you can unzip and edit and zip back.
In windows you should open the zip, drag out the updater, edit, and drag back in, because rezipping will screw up the zip due to the file names.
And next time post in Q&A sub forum unless it is a discussion.
Sent from my GT-P1000 using xda app-developers app
Thread moved. Please post in the correct sections. All questions belong here in Q&A.
Thanks
AvRS
SOLVED
c.
priyana said:
You can remove the assert lines from updater script.
(META-INF/com/google/android/updater-script)
If on Linux, you can unzip and edit and zip back.
In windows you should open the zip, drag out the updater, edit, and drag back in, because rezipping will screw up the zip due to the file names.
And next time post in Q&A sub forum unless it is a discussion.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Thanks, only for reference to other people have the same issue i shar my procedure:
1. Extracted the files in the zip
2. Open the file updater-script in ./META-INF/com/google/android/ folder
3. Removed the first 3 or 4 lines when the assertion check is made
4. Saved the file and zip the whole directory again (take care to zip inside the folder, without the directory)
5. Continue with the steps of the tutorial.
I Decompile apk app and recompile it without any edit but the app is didn't install the error message : the package appears to be corrupt after Recompile
I tried
apktool + dex-tools + signapk
apk easy tool
apk editor studio
what is a problem?
i want edit mediabox launcher
how can i do it?
please help me.
this error
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Package couldn't be installed in /data/app/com.droidlogic.mboxlauncher-1: Package com.droidlogic.mboxlauncher has no signatures that match those in shared user android.uid.system; ignoring!]
Any luck in similar situations? Anybody?
Abo Battal said:
I Decompile apk app and recompile it without any edit but the app is didn't install the error message : the package appears to be corrupt after Recompile
I tried
apktool + dex-tools + signapk
apk easy tool
apk editor studio
what is a problem?
Click to expand...
Click to collapse
The error message "the package appears to be corrupt" usually indicates that there is an issue with the APK file itself, such as missing or corrupted files, incorrect file permissions, or a problem with the signing process.
It's possible that the decompilation process may have introduced some errors or corrupted files in the APK, even if you did not make any edits to the code. When you recompiled the APK, these errors may have been carried over, resulting in the "corrupt" package.
To troubleshoot this issue, you could try the following steps:
Make sure you are using the latest version of the APK tools (apktool, dex-tools, signapk, etc.), as older versions may have bugs or limitations that could cause issues.
Check the log files generated during the decompilation and recompilation process to see if there were any errors or warnings that may have contributed to the issue.
Try recompiling the APK using a different tool or method, to see if that resolves the issue.
If none of the above steps work, you may need to examine the APK file more closely to determine the root cause of the problem. This could involve examining the file structure, checking file permissions and signatures, or even using a more advanced debugging tool such as Android Studio.