Related
What you will need:
Basic tools
- Notepad++
- ZIP manager tool like 7zip
Advanced tools
- Cygwin
- smali (assembler/disassembler)
- APKTool/APK Multi-tool
Lets Begin:
Download a ROM (we use CM in this guide) of your choice (don’t forget to get the permissions for it modding from the developer) and extract it. When you extract it, you will see at least two folders and one file
Folders
- system
- META-INF
Files
- boot.img [this is not present in defy/defy+ ROMs so don't worry about it ]
NOTE THAT I AM ONLY GIVING DETAILS ABOUT THOSE FOLDER WHICH YOU CAN REMOVE/EDIT
THE \system\bootmenu\2nd-boot\ FOLDER
In this folder you'll find the kernel [zImage] file of the ROM here you can change it with the one you compiled or by others.
The Tts folder
The ‘TTS folder’ is all about Text-To-Speech. It contains all the files needed by the Android system to get Text-To-Speech working. If you are removing the TTS feature from your ROM, make sure you remove this entire folder and the TTS related apps from the ‘system folder’, as this will save a lot of space.
The WiFi and Usr folders
The WiFi folder contains the drivers required by the WiFi module to function. So i strongly recommend NOT to touch this folder. If you delete any file from this folder, you will mess up the WiFi functionality.
The usr folder contains some miscellaneous but very important stuff. It may contain anything and everything needed by the Android operating system. For instance, this folder contains all the key-mapping. If such files are messed with, your device will be non-functional although it will boot.
The Build.prop
The build.prop file is pretty self-explanatory. Here, you can change the most basic things, like the android version that setting shows. Wondered how people are making 2.3.4 look like 4.0.3 in settings? Its build.prop. Also,you can change what ‘About phone’ shows here.
Other things,you can change things like,how long your wifi scans,how much battery your phone saves while in sleep, Dalvik VM heapsize and default ringtones. If you are wondering what # stands for, it signifies that, the particular line is commented out, and the system does not read it. You can use it add comments to the build.prop. This helps others understand, what is the function of a particular tweak.
A guide for some basic build.prop tweaks can be found here.
Please be aware that, these build.prop modifications are not universal. So, you will have to experiment with the tweaks and their values.
The META-INF folder
This folder contains instructions for the Android Recovery about how to work with the files present in the zip. This folder contains many folders, but the only one we need to edit is the update-script file.
Making Flashable ZIP
In order to create a flashable zip, first zip the ‘system, META-INF’ folder and the ‘boot.img’. Let’s name this zip as ‘update.zip’. Next we need to sign the zip. Get a signer here. Put your update zip in the same folder as the signer. Then run the ‘signer.bat’ file. This will sign your zip file. After the signing process is complete, you can change the name of the zip to your liking.
confused
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
gwesal said:
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
Click to expand...
Click to collapse
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
coolshahabaz said:
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
Click to expand...
Click to collapse
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
gwesal said:
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
Click to expand...
Click to collapse
The one I edited had that prob of crashing, n the one on official site is about 240mb ty its taking time
D5+/cm11/1.2GHz.
Sent from Tapatalk app
This is deodexed system part of G900FXXU1BNL2 ROM.
It's for chiefs and devs only and cannot be flashed directly.
Because i don't have S5 device, i cannot test it by myself. So, i'm asking qualified devs with S5 to try to make ROM based on this package and make a report if it can boot or even work.
Some important notes:
1) Because almost all APKs were originally odexed, all of them were required deodexing and then signing. So, original signatures are lost. I've used standard android development test certificate. Usually it's ok for system APK which never update from Play Store (only through ROM updates).
Thus, probably some APKs won't work correctly. You can delete such APK and replace it with one from Google Play store. Btw, Play Store is also resigned and may be won't work with Google servers (need to check).
Also, all resigned APKs won't be able to update in Play Store - so you need to replace such APKs with those from Play Store as well.
2) Following APKs i wasn't able to deodex without errors and not include in package:
Maps.apk
Music2.apk
DocumentService.apk
3) In Android 5.0 APKs having library, they are placed in lib folder of APK sub-folder. While deodexing, i've put these libs inside APKs. Probably, you need to extract these libs and put them all into /system/lib (same as all pre-5.0 ROMs).
4) I've placed APKs similar to pre-5.0 way (not every apk in its own folder). I hope it will work this way. If device won't be able to boot, then place them as in original system structure.
Those, who can build the ROM, please test it and tell me about result.
https://mega.co.nz/#!A4kynJpR!pobkpLuFBAUnhtnUwgJSa2KfT6S8apqWwYD5Asb83DU
Update 1:
- contains only modified parts of system, i.e.: only framework, app, priv-app dirs.
- app and priv-app dirs now have correct structure: each apk in its own dir and lib sub-dir.
- not re-signed, i.e. all apks contain original Samsung or Google certificate
- oops, i've forgot to delete Maps.apk, Music2.apk and DocumetService.apk - they were deodexed with errors and most likely won't work.
https://mega.co.nz/#!1l1BlSza!QN1fNyrU7qtwBu6xqkBRH85h3rL81Rvlc-JZv1OtMeE
Nice build
Sadly im just a normal rom builder with knowledge on v4.4 and below, idunno on v5.0 have to learn it to make good roms out of it
Procedures with 5.0 should be the same. The only difference i've found is placing apks in separate subfolder. I think, it required only for pre-odexed ROMs. So, just need to make an usual ROM, same as 4.4 and then check if it work.
sorg said:
Procedures with 5.0 should be the same. The only difference i've found is placing apks in separate subfolder. I think, it required only for pre-odexed ROMs. So, just need to make an usual ROM, same as 4.4 and then check if it work.
Click to expand...
Click to collapse
Very good than ill give it a try when home
But im not an advanced dev sadly dont expect much [emoji14]
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
edgarf28 said:
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
Click to expand...
Click to collapse
No log?
edgarf28 said:
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
Click to expand...
Click to collapse
logcat would be helpful.
Also you can try it step by step. At first, use odexed framework, and my deodexed APKs in subfolders (use my framework.apk and twframework.apk for certificate match).
Then try to put deodexed APKs into common folder (like 4.4 ROM).
If either of above will work, then try to replace the framework jar files.
It's not exactly because of wrong deodexing. May be you need to keep /arm/boot.* files in order to pass initial boot. And then may be OS will re-create new boot.
So, need to try different combination and look what you get in logcat. May be 5.0 requires some additional steps for deodexed ROMs.
Btw, after extracting libs, don't delete them from APKs.
Just checked CM12 ROM structure:
1) copy each APK in its separate folder (same as stock 5.0 ROM).
2) extract lib to separate lib folder (same as stock 5.0 ROM)
3) all arm folders should be deleted (including framework/arm)
http://www.xda-developers.com/android/deodex-lollipop-system-apps-with-ease/ ???
I've tried to replace some apps by deodexed singly (e.g. SamsungCamera3, SecMms_Candy, TeleService), of course with deleted corresponding arm folder
Unfortunately, none of them work (even completely unmodified), only FC ...
_alexndr said:
I've tried to replace some apps by deodexed singly (e.g. SamsungCamera3, SecMms_Candy, TeleService), of course with deleted corresponding arm folder
Unfortunately, none of them work (even completely unmodified), only FC ...
Click to expand...
Click to collapse
can you provide logcat? FC may be related to incompatible certificate.
sorg said:
can you provide logcat? FC may be related to incompatible certificate.
Click to expand...
Click to collapse
See attachment... logcat while I'm trying to run deodexed SamsungCamera3
_alexndr said:
See attachment... logcat while I'm trying to run deodexed SamsungCamera3
Click to expand...
Click to collapse
I don't see anything about SamsungCamera3 in logcat... If you get FC, then at least FC reason should be shown in logcat.
If it fc post the dumpstate_app_error.txt.gz from data/log rather than taking a log. Guaranteed to include all info
sorg said:
I don't see anything about SamsungCamera3 in logcat... If you get FC, then at least FC reason should be shown in logcat.
Click to expand...
Click to collapse
My mistake. I have not looked at sending and uploaded incomplete file. Now it should be ok
Goldie said:
If it fc post the dumpstate_app_error.txt.gz from data/log rather than taking a log. Guaranteed to include all info
Click to expand...
Click to collapse
This file is also attached
Assuming this permission is in manifest to start with it looks like some issue with actually reading the manifest?
12-12 09:09:30.688 6530 6530 E AndroidRuntime: Caused by: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
Goldie said:
Assuming this permission is in manifest to start with it looks like some issue with actually reading the manifest?
12-12 09:09:30.688 6530 6530 E AndroidRuntime: Caused by: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
Click to expand...
Click to collapse
While deodexing i didn't touch neither resources nor manifest, only injected dex then signed and then aligned. Probably, because re-signed apk uses different certificate (obviously, i don't have Samsung's private key), OS denies some system level access.
Usually, when i create custom ROM i resign all APKs which use Samsung certificate - thus all system APKs share the same signature and everything works.
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Goldie said:
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Click to expand...
Click to collapse
No problem, i will update pack with updated structure without resigning.
In my custom ROM i do many changes, sometimes including manifest change and adding additional system APKs imported from other devices or written by myself.
sorg said:
While deodexing i didn't touch neither resources nor manifest, only injected dex then signed and then aligned. Probably, because re-signed apk uses different certificate (obviously, i don't have Samsung's private key), OS denies some system level access.
Click to expand...
Click to collapse
Goldie said:
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Click to expand...
Click to collapse
And... this was the cause :laugh:
I've put classes.dex from @sorg 's apk to original SamsungCamera3.apk and it works as deodexed !!!!!!
I will try to baksmali, then modify the code and smali again
So I typically like to tinker when I get new phones/tablets. One of the first mods I always attempt is an extended power menu. That means android.policy.jar and framework-res.apk need to be pulled to my computer for decompiling. Not to mention, deodexing the jar file. But for the life of me, I cannot find the odex component for android.policy.jar. Has anyone else found it? In past OS versions they were there beside their jar/apk mates. And in lollipop, looks like in /system/framework there is an /art folder which has SOME of the odex files but not all.
There are no odex files because they are deodexed by default.
There is no android.policy.jar for Android 6.0 both GPE and Sense.
If you want to add in Advance Power Menu, you need to see services.jar & framework-res.apk
Hint : \services.jar\smali\com\android\server\policy
If you manage to make one, let me know (by PM also ok) because I don't have the time to look further into it.
Hi guys, i've found a beautiful watchdogs inspired bootanimation that the user Nin9 made for nexus device, I've tried to modi it to adapt to my device, but doesn't work (surely i've made wrong something):
Is there anybody who can do it or can teach me how to do it?
- That's the thread where i found the boot animation:
http://forum.xda-developers.com/nexus-4/themes-apps/boot-animation-watchdogs-v2-1-t2733053
- The versione is "v2.1"
Thanks a lot to all, and sorry for my bad english:laugh:
ULT][MO said:
Hi guys, i've found a beautiful watchdogs inspired bootanimation that the user Nin9 made for nexus device, I've tried to modi it to adapt to my device, but doesn't work (surely i've made wrong something):
Is there anybody who can do it or can teach me how to do it?
- That's the thread where i found the boot animation:
http://forum.xda-developers.com/nexus-4/themes-apps/boot-animation-watchdogs-v2-1-t2733053
- The versione is "v2.1"
Thanks a lot to all, and sorry for my bad english:laugh:
Click to expand...
Click to collapse
Do you not know how to install it, or are you saying you want it resized? Here is a 720 version
https://drive.google.com/file/d/0B1niPALD2vPeZVNTX3VhTE11b3M/view?usp=docslist_api
Thanks levone, yes, i tried to flash original version with TWRP but ibtained "FAILED" message, so I tried to manually insert it in the directory "system/media" but at the boot the screen is black, now i try to flash it.
ULT][MO said:
Thanks levone, yes, i tried to flash original version with TWRP but ibtained "FAILED" message, so I tried to manually insert it in the directory "system/media" but at the boot the screen is black, now i try to flash it.
Click to expand...
Click to collapse
Update: inserted manually on the directory, it works fine!...but probably it's the 3.0 version, and i looking for 2.1.
Update2: Fixed it!!
- Renamed all images from .png to .jpeg,
- Used the code content in the "desc.txt" of the bootanimation you linked
- Compressed all folders as a .zip. (in method of compression setted "store", or "memorizzazione" for those who have Italian version of win rar)
- Moved manually to the directory "system/media" using ES File Explorer
and wooooow
Thanks a lot levone for your support and pacience
ULT][MO said:
Update2: Fixed it!!
- Renamed all images from .png to .jpeg,
- Used the code content in the "desc.txt" of the bootanimation you linked
- Compressed all folders as a .zip. (in method of compression setted "store", or "memorizzazione" for those who have Italian version of win rar)
- Moved manually to the directory "system/media" using ES File Explorer
and wooooow
Thanks a lot levone for your support and pacience
Click to expand...
Click to collapse
No prob. I didn't really look - what's the difference in versions?
change some parts of animations
Update3: after cm 12.1 nightly update, the bootanimation doesn't work, except the version you linked. It still working fine... s*it!!!
I have been able to deodex my stock rom using TickleMyAndroid tool (it can be found on xda )
Some of 32bit apps could not be deodexed so i had to do it manually (like Bluetooth.apk)
Just saying if anyone need it i can tell the steps
Sorry i can't upload because i have a slow connection
And i need help with something
After deodex some symlinks seems to be broken like this file
/system/lib/libbluetooth_jni.so
I have to copy it to
/system/app/bluetooth/lib/arm
to get the bluetooth working
Any idea what's going on?