Hello
I modded a few apks which also have .odex files. If I delete the .odex files the apk isn't shown in the app section. But of course those .odex files are old and belonged to the original app.
Is it possible to force ICS to create new .odex files? It doesn't seem to do so on boot.
I simply sent the new apks via bluetooh to my phone and then copied them to where they came from (/system/app).
Anybody have any idea how I can make ICS build new .odex files based on my new apks?
Any help would be much appreciated
I have a rooted Galaxy M Style phone with stock Gingerbread 2.3.4 firmware. I am trying to customize my stock camera app, but am not sure what I'm doing wrong. I plan to replace the autofocus_ok.ogg with a different tune from my phone. I checked the properties of the autofocus_ok.ogg and saw it's a mono, 44100hz, and 96 bitrate file. The tune that I have has the same properties. So this is what I have done so far:
I backed up camera.apk to /system/app/camera.apk.bak and the camera.odex to /system/app/camera.odex.bak. I left a copy of camera.odex in /system/data. I copied the camera.apk to my memory card and placed the file on my computer. I renamed the file to a .rar. I then deleted the autofocus_ok.ogg and placed the tune that I wanted in that directory. Then I renamed it to autofocus_ok.ogg. I renamed the file back to .apk and transferred the file back to the memory card, then over to /system/app. The camera app will not install/not showing up on my phone. I am transferring the files through root explorer on my phone.
I worked with the original apk file again with apktool. I was able to decompile and replaced and renamed the files that I needed again. I compiled the file and transferred the file to /system/app again, but the apk will still not install. I checked the complied apk file and noticed that the file didn't have the META-INF folder, so I copied that over to. Tried to install it again by copying the file to /system/app, but it still won't show up on my phone. Is there anyway for me to change the autofocus_ok.ogg without a custom rom?
Thanks.
ImAhNoBoDy said:
I have a rooted Galaxy M Style phone with stock Gingerbread 2.3.4 firmware. I am trying to customize my stock camera app, but am not sure what I'm doing wrong. I plan to replace the autofocus_ok.ogg with a different tune from my phone. I checked the properties of the autofocus_ok.ogg and saw it's a mono, 44100hz, and 96 bitrate file. The tune that I have has the same properties. So this is what I have done so far:
I backed up camera.apk to /system/app/camera.apk.bak and the camera.odex to /system/app/camera.odex.bak. I left a copy of camera.odex in /system/data. I copied the camera.apk to my memory card and placed the file on my computer. I renamed the file to a .rar. I then deleted the autofocus_ok.ogg and placed the tune that I wanted in that directory. Then I renamed it to autofocus_ok.ogg. I renamed the file back to .apk and transferred the file back to the memory card, then over to /system/app. The camera app will not install/not showing up on my phone. I am transferring the files through root explorer on my phone.
I worked with the original apk file again with apktool. I was able to decompile and replaced and renamed the files that I needed again. I compiled the file and transferred the file to /system/app again, but the apk will still not install. I checked the complied apk file and noticed that the file didn't have the META-INF folder, so I copied that over to. Tried to install it again by copying the file to /system/app, but it still won't show up on my phone. Is there anyway for me to change the autofocus_ok.ogg without a custom rom?
Thanks.
Click to expand...
Click to collapse
erm... is the permissions set correctly rw-r--r-- ?
MoonBlade said:
erm... is the permissions set correctly rw-r--r-- ?
Click to expand...
Click to collapse
Yup, permissions were set correctly like rw-r--r--. Owner is root:root. Those are the permission that I set on the apk file like they were on the original file. I just realized that the compiled apk's from apktools doesn't show up on my phone. The apk that I created by opening up winrar and just replacing the .ogg files do show up, but I get the error "The application Camera (process com.sec.android.app.camera) has stopped unexpectedly. Please try again."
Anything else I can try or a thread to refer to?
ImAhNoBoDy said:
Yup, permissions were set correctly like rw-r--r--. Owner is root:root. Those are the permission that I set on the apk file like they were on the original file. I just realized that the compiled apk's from apktools doesn't show up on my phone. The apk that I created by opening up winrar and just replacing the .ogg files do show up, but I get the error "The application Camera (process com.sec.android.app.camera) has stopped unexpectedly. Please try again."
Anything else I can try or a thread to refer to?
Click to expand...
Click to collapse
why dont you try to push the modified apk manually using root explorer or so instead of pushing via adb ..
after decompiling apk and modifying it, compile it into some folder and then copy it into you sd card then use root explorer and manually push(copy) the apk into system/app .. give proper permissions and then reboot your phone..
Here are some guides to use apktool
http://forum.xda-developers.com/showthread.php?t=1891686
http://forum.xda-developers.com/showthread.php?t=1989533
MoonBlade said:
why dont you try to push the modified apk manually using root explorer or so instead of pushing via adb ..
after decompiling apk and modifying it, compile it into some folder and then copy it into you sd card then use root explorer and manually push(copy) the apk into system/app .. give proper permissions and then reboot your phone..
Here are some guides to use apktool
http://forum.xda-developers.com/showthread.php?t=1891686
http://forum.xda-developers.com/showthread.php?t=1989533
Click to expand...
Click to collapse
I have been pushing the modified apk through root explorer all this time. I don't even have adb install, haha. The procedure you explained have been the way I have been doing it the whole time, lol. I read the threads you posted and the procedure is the same as I've been doing it, except for the second thread. I can't grab the apktool from 4shared because I don't have an account. I am using the latest apktool 1.5.2. Also, I didn't understand what PulseDroid was talking when he said "We are NOT done just yet, we cannot use the new apk's... we have to take what we did and add it back to the original apk file to keep proper signature use something like 7zip, take the 'resources.arcs' file and any other xml files you edited out of the "-new" apk and copy them into Original apk". So I'm suppose to replace the resources.arcs and the .ogg files that I created from the new apk to the old apk? I didn't mess with any xml file.
Anyways, is there anything else I can try?
EDIT: ........I feel so embarrassed. I checked out this thread http://forum.xda-developers.com/showthread.php?t=2378177 and saw this post "Drag your replacement files into WinRAR and (here's the important part) in the Compression Method drop-down choose "Store"." All this time I have been compressing the file as "Normal" in Winrar, instead of "Store".
All in all, I did not need apktool at all. I used the original apk and opened it up in Winrar. I deleted the files that I wanted to replaced and put in the files that I wanted. Each time I put something in the file in Winrar I get a prompt for compression and instead of "Normal" compression just use "Store". It was that simple.
This helped me, thank you!
Hey I need your help , thanks in advance
I have lg p765 4.1.2 v20c
How to know corresponding lib file of system/apk in system/lib ….
I tried decompiling apk but I didn’t found any relation with lib file by seeing android manifest.xml
Or u have any list that *.apk uses *.so files or something
for example old chrome apk uses lib file system/lib/libchromeview.so
but update uses different lib files (as I have removed system/lib/libchromeview.so with never lib file found in apk/lib folder and removing from apk saves space(both on system partion and internal memory) and so far I have no force close works perfect)
this things I want to know because want to remove unwanted app and update gms
Here you go.
http://forum.xda-developers.com/showthread.php?t=2737126
[TUTORIAL] Find out which shared libs (.so) are missing
If you have an detailed list of library files for in build apps (especially for HTC) like the one you mentioned of the chrome library file please share it with me.
HTC desire X, JB , TWRP
Hello,
I extracted an app (for eg FMRadio.apk) from Cyanogenmod rom. Now there is a libs folder that contain some .so files. Now when i install that app as a user app, it doesn't install. So how should i combine the .so files to the apk so that it gets installed as a user app? Thanks.
Hello All,
I am trying to add/edit xml files found inside "assets", "vendor" directories of an APK included in system.img (priv-app directory) of a ROM.
The APK is available at
system/priv-app/CarrierConfig/CarrierConfig.apk
system/priv-app/CarrierConfig/oat/arm64/CarrierConfig.odex
system/priv-app/CarrierConfig/oat/arm64/CarrierConfig.vdex
I have used apk tool to decompile and re-compile the apk. I also zipaligned, signed with my own key. I copied the file to priv-app directory in the phone and restarted the phone. This did not work. I did have 644 permission for apk file after replacing. Also, I did clear the dalvik cache and cache after APK replacement.
1. Do I need to change the odex or vdex files? I did not touch them since my changes were in xml files.
2. Should I sign with originally signed signature?
3. I could not see the odex and vdex file in the priv-app directory in the phone after the ROM install(when I tried to replace the APK). Why is that?
4. Should I build a rom zip file to flash(along with existing odex and vdex files) as opposed to replacing the APK in the device?
Any help?
http://www.w3.org/2001/XMLSchema
I was looking into this as well. Everything I read said you have to be registered as carrier to make modifications to carrier config.apk , unfortunately:-/ Let me know if you did find a solution, though.