Related
Hey all,
I was wondering whats the process to modify the stock multi-touch keyboard for the Droid 2? I was able to do it with the multi-touch keyboard that Punk.Kaos ported to the Eris, using some Windows batch files for extracting the apk source, compiling, signing, etc. I just can't remember for the life of me what that little program was called. Any ideas?
Thanks!
it would be nice since the space bar is soooo small i keep pressing . instead of space 70% of the times
Alright, I was able to get the program I was thinking of, it is called APK Manager. But the keyboard is a odex file... Which I don't know how to extract the XML files from... Yet.
I'd de-odex before you try to extract. It will be a lot easier. There's the method I used here.
What exactly is de-odex'ing? How will it affect my phone?
Deodexing just means that all of the stray .odex files will be put back into the correct .apk files this is done mostly for theme purposes in order to edit the services.jar file which has to be de-odexed before it can be edited. It won't corrupt anything if you do it right nothing should change on the outside the phone devs leave the .odex files out for loading reasons but nothing significant should change but you might experience a slightly slower boot up process but like I said nothing significant. Most ROM's now are de-odexed though.
So I deodexed my phone so I could work on the LatinIME.apk package. Using the APK-Manager for Linux, I was able to (0) pull the APK from my phone. Then I (9) decompiled the APK, edited the XML files as I wanted.
Now, from here I'm not entirely sure which direction to take. I tried running (13) Compile APK / Sign APK / Install APK, but I got an error saying something on how the signatures didn't match up. Then I tried running (3) ZIP APK (5) Zipalign APK then (8) ADB push, but now I don't even have the keyboard on my phone anymore.
How can I go about doing the correct way to compile my modified code and install it on my phone?
Here are the options I can do, if you're not familiar with APK Manager:
Code:
------------------Simple Tasks Such As Image Editing----------------------
0 Adb pull
1 Extract apk
2 Optimize images inside (Only if "Extract Apk" was selected)
3 Zip apk
4 Sign apk (Dont do this if its a system apk)
5 Zipalign apk (Do once apk is created/signed)
6 Install apk (Dont do this if system apk, do adb push)
7 Zip / Sign / Install apk (All in one step)
8 Adb push (Only for system apk)
-----------------Advanced Tasks Such As Code Editing-----------------------
9 Decompile apk
10 Compile apk
11 Sign apk
12 Install apk
13 Compile apk / Sign apk / Install apk (All in one step)
---------------------------------------------------------------------------
14 Batch Optimize Apk (inside place-apk-here-to-batch-optimize only)
15 Sign an apk (inside place-apk-here-for-signing folder only)
16 Batch optimize ogg files (inside place-ogg-here only)
17 Quit
****************************************************************************
Anyone? I would love to get my stock keyboard back!
Sent from my DROID2 using XDA App
Has anyone had any success deodexing these three files on a Verizon Tab? Every other apk deodexed just fine but I can't get these three done at all.
If anyone has had any success would you please post them for me, or let me know what dependencies you had to manually add in.
Thanks!
+1 here
Sent from my Verizon Tab using XDA App
When I used xUltimate to deodex files from my Motorola I1 several files failed to deodex. I deodexed them manually by running (in a command prompt) for each one something akin to the following line:
java -jar baksmali-1.2.5.jar -c :am.jar:android.awt.jar:android.motorola.videoplayer.jar:...etc. -x Camera.odex
I included as dependencies(the jar list after the "-c") every jar that was in /system/framework(I copied all the deodexed framework jars to my working directory, as well). For each odex file this created an "out" folder. I used smali to compile this out folder into a classes.dex, which I then inserted into the corresponding apk file.
Good luck
Hey Guys,
This is a small tutorial for those who want to Deodex a Single Application manually.
Deodex And Odex:
The APKs or JARs of Android contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.It will make your faster theoretically even though it would be too small to notice.When deodexing the .odex file is changed to classes.dex file. Deodexing also allows us to theme and install mods.Many of the Stock Roms and CyanogenMod 7 roms are now odexed and to theme them or to add mods we need to have it deodexed. So lets learn how!!
Deodexing:
Preparation:
Hope you have Java Development Kit installed on your computer to run the scripts.Get it from: here.Select you OS from the list and download the suitable package.(We would need the full thing and not the Demo versions.)
Download the Attached .zip File
Extract its Contents to a Folder.(Extracting to a New Folder in the Desktop is Preferred for Ease)
We will name this Folder with the Extracted Contents as Deodex(or any name that you like)
Procedure And Explanations:
First of all copy the Application file that you need to Deodex.A Android Application file is the .apk file found in the system/app directory.Copy the .apk file and the .odex file of the application that you want to Deodex and paste in the Deodex folder(Folder to which the attachment's contents was extracted)
Now go to your system/framework directory and you can see a lot of .jar and .odex files in this folder and copy all its contents to the folder to which the attachment's contents was extracted.
Before doing anything more backup your rom and the application file(If anything goes wrong you can use it then)
To Deodex a application you need to specify its "BOOTCLASSPATH" files. BOOTCLASSPATH are files that contain the classes for an application or in simple language BOOTCLASSPATH files are those files that are required by a android application to run properly. They are actually those files that we have copied from the system/framework directory to our Deodex folder. There are mainly 5 BOOTCLASSPATH files for every android rom.They are: android.policy.jar , core.jar , bouncycastle.jar , ext.jar , framework.jar
All apps are dependent on these files but some apps are dependent on some other BOOTCLASSPATH files.So sometimes the problem is that we actually dont know to which of these files is a particular app dependent to.So we will have to specify all the BOOTCLASSPATH files or the .jar files in the system/framework directory.So problem solved!! Now enough with the theory class,lets proceed to the practical classes!!!!!
Open Command Prompt.
As an example we will Deodex Settings.apk
Type in this command in Command Prompt:
Code:
java -Xmx1024m -jar baksmali.jar -c :am.jar:android.policy.jar:android.test.runner.jar:bmgr.jar:bouncycastle.jar:
com.android.location.provider.jar:com.google.android.maps.jar:sonyericsson.suquashi.jar:
core.jar:corej-unit.jar:ext.jar:framework.jar:ime.jar:input.jar:java.awt.jar:javax.obex.jar:monkey.jar:pm.jar:
:services.jar:sqlite-jdbc.jar:svc.jar -x Settings.odex
Here:
-Xmx says the heap memory needed.In the above command it is given to 1024m. Sometimes deodexing may have errors due to the low heap memory.So set it to 1024m itself.
-jar baksmali.jar says the program to run baksmali.jar file.
-c says that the following files are the BOOTCLASSPATH files of the application we are deodexing.
-x says the name of the application that we are deodexing.It should end with .odex extension.
Note:
When you specify the .jar files just add all those .jar file names in the system/framework folder(only add the .jar files and not the .odex files).Ensure that you have added the .jar extension at the end of each file. Separate the .jar files with colon " : " symbol.
If you have made no spelling errors and have done everything mentioned you will get a folder named "out".
Now we have to smali the out folder into classes.dex file.
So again type in the Command Prompt:
Code:
java -Xmx1024m -jar smali.jar out -o classes.dex
Here:
-o says what the output file should me named to.Dont rename the classes.dex file into anything else.
Now you will have a file in our Deodex folder(Folder to which the attachment's contents was extracted) called "classes.dex".
Finalizing:
Now open the application's .apk file(which you were trying to deodex) with WinRar.
Move the classes.dex file that you got to this .apk file.(Just drag and drop it to the .apk file opened with WinRar.)
Now you will have a deodexed .apk file.
Note: After deodexing you will have to delete the .odex file of the particular application which you had deodexed.
I will make a guide to Odex back a Deodexed application soon!
Hope this guide helps you....
For any doubts or questions please post it here in this forum and I will try to attend to it.........
Re: Deodex A Single Application
Thanks bro..
Good tut..
sent from my phone using hands and brain...
thanks
Re: Deodex A Single Application
Good tut...
But quite long
Sent from my W8 using xda app-developers app
hey...nice tutorial and nice explanation :good:
thanks
Re: Deodex A Single Application
But helpful too...
sent from my phone using hands and brain...
Gogeta said:
Good tut...
But quite long
Sent from my W8 using xda app-developers app
Click to expand...
Click to collapse
I made it long so that everyone understands.Even those who are very new to android
i'm stucked when i try to deodex settings.odex..
any suggestions???
Hidzrie said:
i'm stucked when i try to deodex settings.odex..
any suggestions???
Click to expand...
Click to collapse
you must deodex
settings.apk + settings.odex.....
i've already follow exactly like the tutorial above but cmd just stucked...
in 'out' folder there are \com\android\settings\ folder and these files were in it and nothing more:
AccessibilitySettings$1.smali
AccessibilitySettings$2.smali
AccessibilitySettings$3.smali
AccessibilitySettings$4.smali
AccessibilitySettings$5.smali
AccessibilitySettings$6.smali
AccessibilitySettings.smali
please anyone help..
Credit/thanks: http://forum.xda-developers.com/showthread.php?t=1208320 ?
Hidzrie said:
i've already follow exactly like the tutorial above but cmd just stucked...
in 'out' folder there are \com\android\settings\ folder and these files were in it and nothing more:
AccessibilitySettings$1.smali
AccessibilitySettings$2.smali
AccessibilitySettings$3.smali
AccessibilitySettings$4.smali
AccessibilitySettings$5.smali
AccessibilitySettings$6.smali
AccessibilitySettings.smali
please anyone help..
Click to expand...
Click to collapse
follow the highlighted lines and try again and deodexing takes time according to your computer's ram.so be patient.if you still cant do it then just upload the system=>framework folder and the app you want to deodex and its odex file and Private Message me the links. I will check whats the problem.
L_S said:
Credit/thanks: http://forum.xda-developers.com/showthread.php?t=1208320 ?
Click to expand...
Click to collapse
this can be found in the android sources site but it not so easy to understand for beginners so i made it a little easier to understand and i didnt refer that guide because all is clearly written in the android sources site.
i understood why some of you are making mistakes when trying to deodex a apk or jar file.
its because you are copying exactly the same bootclasspath files that i specified in the guide.
it varies depending on your device and your rom. So I have made some changes in my guide.some lines are highlighted in red.
follow those lines.
Hidzrie said:
i'm stucked when i try to deodex settings.odex..
any suggestions???
Click to expand...
Click to collapse
Specify your device and rom that you use. Are you sure that you followed what i told itself? Try it once more as I have made some more changes in the guide to help you guys.
Still if you cant do it then just copy your framework folder and the apk and .odex file that you want to deodex and pm me. I will try to deodex it.
fotak-x said:
you must deodex
settings.apk + settings.odex.....
Click to expand...
Click to collapse
no fotak we dont need to deodex settings.apk. We only need to deodex the .odex file but we will have to keep the apk file also in the same folder.
Leon1234 said:
Specify your device and rom that you use. Are you sure that you followed what i told itself? Try it once more as I have made some more changes in the guide to help you guys.
Still if you cant do it then just copy your framework folder and the apk and .odex file that you want to deodex and pm me. I will try to deodex it.
Click to expand...
Click to collapse
I'm using samsung gt-s5830i.. Rom simplicity v4..
I've tried like many times..still wont work..
Hidzrie said:
I'm using samsung gt-s5830i.. Rom simplicity v4..
I've tried like many times..still wont work..
Click to expand...
Click to collapse
dont worry,we can figure it our!
what error are you getting in command prompt?
can you give the lines that come up in command prompt?
Leon1234 said:
dont worry,we can figure it our!
what error are you getting in command prompt?
can you give the lines that come up in command prompt?
Click to expand...
Click to collapse
There are no error appear on cmd..
After I insert a command to deodex settings.odex and press enter, it just like nothing happen...
There are no error appear on cmd..
After I insert a command to deodex settings.odex and press enter, it just like nothing happen...
Click to expand...
Click to collapse
you will have to wait for some time when deodexing depending on the ram of your device.
what is the ram of your computer?
and do you have java 7?
Hey guys! Since deodexing older Z series phones with this latest update has been a pain in the *** for deodexing here's a detailed guide on how to get a correctly deodexed system folder and avoid bootloops...
First part: Getting files from the phone.
To get the files from our phone first we'll have to install ADB Drivers, you can find them here on xda or go google it. Once you have adb drivers installed go to the folder where you installed them. Press Shift while right clicking on the folder and select Open command promp.
Here are the commands to get the folders with apk, note that you'll find them in your C:\ folder.
- To get app folder:
Code:
adb pull /system/app /app/
- To get framework folder:
Code:
adb pull /system/framework /framework/
- To get priv-app folder:
Code:
adb pull /system/priv-app /priv-app/
You will get apk's only on app and priv-app folders, the only folder with odex files (arm folder) will be framework.
------------------------------------------------------------------------------------------------------------
Now let's go for sqsh files to get odex files for app and priv-app folders.
- To get odex.app.sqsh:
Code:
adb pull /system/odex.app.sqsh
- To get odex.app.sqsh:
Code:
adb pull /system/odex.priv-app.sqsh
You'll find these files inside the same folder where adb.exe is
Second part: Unpacking .SQSH files
To resume a little, you may refer to IaguCool's guide
Once you have downloaded SquashFS Tool, move both .sqsh files to the folder.
When you have opened the command promp use these codes to extract files...
> To get odex files for app folder (After extracting rename the squash-root folder to app):
Code:
unsquashfs -no-xattrs odex.app.sqsh
> To get odex files for priv-app folder (After extracting rename the squash-root folder to priv-app):
Code:
unsquashfs -no-xattrs odex.priv-app.sqsh
Third part: Merging files
Create a folder named system and move app, framework and priv-app folders from C:\ to the new folder.
After that grab the folders you extracted with SquashFS Tool and merge them with app and priv-app folder.
After doing this move SemcGenericUxpRes folder to priv-app folder
Fourth part: Deodexing
Download JoelDroid's Lollipop Batch Deodexer and replace the file named oat2dex.jar found on /tool folder with this one: Latest oat2dex
Then open the program and select the /system/ you've created to start the process.
Once it has finished, grab SemcGenericUxpRes folder and move it back to /framework
Now you can either replace folders manually on your phone using TWRP by moving the deodexed system folder to your phone and mounting System partition, erasing app, framework and priv-app folder and then pasting the ones from the deodexed folder. OR make a flasheable zip.
How to manually move folders to /system partition
> Boot to recovery (TWRP MANDATORY)
> Mount system partition
> Go to file manager and go to: /system/ partition
> Manually delete app, framework and priv-app folder (you must first open the folder, then open the menu and delete)
> Then go to where you put the deodexed folders, open app folder, open menu, choose copy and paste on /system/ folder, same process for priv-app and framework.
> Once you're done go to Wipe option, choose advanced wipe and wipe Dalvik-cache and cache.
> Boot and you're good to go! No need to fix permissions
In both cases, after you have either flashed or replaced the folders, go to Wipe option > Advanced Wipe and clean Dalvik-cache and cache to avoid problems.
Does it have issue with OpenGL and Play Store?
Sent from my D6503 using Tapatalk
RyTekk said:
Does it have issue with OpenGL and Play Store?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
No, that's why you need to download latest oat2dex version See deodexing part
Why not just copy App, priv-app and framework folder from system and deodex them?
Black_Eyes said:
Why not just copy App, priv-app and framework folder from system and deodex them?
Click to expand...
Click to collapse
Cause you get bootloop if you just replace odex files present in app and priv-app (Especially after replacing the deodexed framework folder in system).
If you extract via adb you'll get app and priv-app folders clean, without odex files. That way you can make a cleaner deodex since you don't replace .odex files, just merge both folders in one, app with .apks and app with .odex
I wish it was as easy as in 5.0.2 but no, on 5.1.1 is way more complicated to have a properly deodexed system.
BTW i've tried by deodexing manually by copying folder and then boot into recovery delete app, priv-app and framework folder via TWRP file manager and then flashed the deodexed zip and it worked
C:\adb>adb pull /system/odex.app.sqsh
remote object '/system/odex.app.sqsh' does not exist
C:\adb>adb pull /system/odex.priv-app.sqsh
remote object '/system/odex.priv-app.sqsh' does not exist
help
Everything was fine except google play services, it crashes every time i want add account
Perfect work @xkeita ,
I saw you asking so many guys about deodexing .222 firmware these days and finally you managed!
Great work, great tutorial. I will try asap.
could you provide the zip? or the zip from this thread http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596 can be used?
zyclops1 said:
C:\adb>adb pull /system/odex.app.sqsh
remote object '/system/odex.app.sqsh' does not exist
C:\adb>adb pull /system/odex.priv-app.sqsh
remote object '/system/odex.priv-app.sqsh' does not exist
help
Click to expand...
Click to collapse
same problem..
edi194 said:
Everything was fine except google play services, it crashes every time i want add account
Click to expand...
Click to collapse
Same here bro
I thought I had accidently deleted some necessary google services files while removing bloatwares so I tried flashing latest Gapps for 5.1.1 over stock sony FW but no effect. Can't figure out why
I'm having Xperia ZR (5.1.1 Stock)
zyclops1 said:
C:\adb>adb pull /system/odex.app.sqsh
remote object '/system/odex.app.sqsh' does not exist
C:\adb>adb pull /system/odex.priv-app.sqsh
remote object '/system/odex.priv-app.sqsh' does not exist
help
Click to expand...
Click to collapse
gundam_warlock said:
could you provide the zip? or the zip from this thread http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596 can be used?
same problem..
Click to expand...
Click to collapse
If you have an Xperia Z1 it might differ from this a little bit, I think those don't have odex.xx.sqsh on their filesystem, check if you have odex files in app and priv-app.
Phones that I know that so far work with this sqsh filesystem are Xperia Z, ZL, ZR, Xperia Tablet Z
edi194 said:
Everything was fine except google play services, it crashes every time i want add account
Click to expand...
Click to collapse
sshivampp said:
Same here bro
I thought I had accidently deleted some necessary google services files while removing bloatwares so I tried flashing latest Gapps for 5.1.1 over stock sony FW but no effect. Can't figure out why
I'm having Xperia ZR (5.1.1 Stock)
Click to expand...
Click to collapse
Did you clear dalvik-cache and cache? If it still gives you googleplayservices fc, manually download the GooglePlayServices from APKMirror and install as normal app
xkeita said:
If you have an Xperia Z1 it might differ from this a little bit, I think those don't have odex.xx.sqsh on their filesystem, check if you have odex files in app and priv-app.
Phones that I know that so far work with this sqsh filesystem are Xperia Z, ZL, ZR, Xperia Tablet Z
Click to expand...
Click to collapse
I tried to deodex directly without pull sqsh, everything except nfcnci failed, when i tried to copy to system and reboot, nfc is fc. When check nfcnci folder only apk and lib folder exsist, but nothing exsist inside lib folder.
Where do i wrong?
xkeita said:
Did you clear dalvik-cache and cache? If it still gives you googleplayservices fc, manually download the GooglePlayServices from APKMirror and install as normal app
Click to expand...
Click to collapse
Dalvik-cache & Cache ! I tried wiping the whole data, it didn't work.
App install window goes on forever and app not installing.
Got it working by installing latest play services before deodexing. (as the updated play services app in the data partition runs, no matter if system is having broken play services package)
Fixed it for now but still wondering what causes the issue
sshivampp said:
Fixed it for now but still wondering what causes the issue
Click to expand...
Click to collapse
same issue here , how can i fix this?
@xkeita Bro if not ask for much could create a video tutorial ? ?????
Hamidreza2010 said:
same issue here , how can i fix this?
Click to expand...
Click to collapse
what I did is flashed the ftf (to go back to stock)
installed latest play services via play store
then followed the deodexing guide
Note: after deodexing, do not wipe data or uninstall updated play services otherwise error will occur again
works fine thank you
ZR 5.1.1
After download the rom by XperiaFirm I must continue this step?
Second part: Unpacking .SQSH files
To resume a little, you may refer to IaguCool's guide
Once you have downloaded SquashFS Tool, move both .sqsh files to the folder.
When you have opened the command promp use these codes to extract files...
> To get odex files for app folder (After extracting rename the squash-root folder to app):
Code:
unsquashfs -no-xattrs odex.app.sqsh
> To get odex files for priv-app folder (After extracting rename the squash-root folder to priv-app):
Code:
unsquashfs -no-xattrs odex.priv-app.sqsh
Third part: Merging files
Create a folder named system and move app, framework and priv-app folders from C:\ to the new folder.
After that grab the folders you extracted with SquashFS Tool and merge them with app and priv-app folder.
After doing this move SemcGenericUxpRes folder to priv-app folder
Fourth part: Deodexing
Download JoelDroid's Lollipop Batch Deodexer and replace the file named oat2dex.jar found on /tool folder with this one: Latest oat2dex
Then open the program and select the /system/ you've created to start the process.
Once it has finished, grab SemcGenericUxpRes folder and move it back to /framework
After update from nougat to oreo, I've have problem with integration updated apps in to /system.
I do it like this:
1. copy apk file from data/apk to sd card
2. rename copied apk file to name of /system apk
3. extract lib folder from apk
4. copy newer file to proper folder in /system/app or /system/priv-app and replace file in it
5. Copy lib files extracted form apk to right folder /system/lib or /system/lib64
6. Uninstall update from /data/app
7. reboot + dalvik-cache wipe
In nougat it was working, but in oreo, app after integration, breaks. It cannot be open, and app name changes to random words (ex. google docs name changes to "write com.android").
To repair integrated apps I have to perform a full /data/ wipe.
Is it a some kind of protection? How to do it properly?
TitaniumBackup and Link2SD cannot integrate updates to rom properly without errors since Lolipop.
So no one knows?
or just nobody wants to write?