Hey guys,
I just started the long journey of android rom development/cooking using an app called Android Kitchen, and I'm looking for some help from the more experienced. I extracted a custom rom folders (for personal use), and started to edit some of the extracted files (replacing and deleting), but I'm quite lost when it comes to merging flashable .zip folders (like lockscreens and mods) with the extracted rom file.Should I copy and paste whats inside the flashable zip into the rom file? Or should I use note editor to copy what's inside the mod file itself, copy the text, and add it to the original one? I really want to add these mods through this app rather than recovery mode. And can I emulate edited roms on my computer rather than risking my phone?
Thnx...
Hey folks,
I'm running OmniROM on my Nexus 5 and was very much missing the option to change the NavBar height from AOKP on my Nexus 4.
I did a feature request for OmniROM but until it will be implented in the future I'm helping my self and wrote a little How-To on my Android 4.4 experiences.
Use at your own risk!
I'm not responsible for what you do on your phone.
If you don't even know how to flash a ZIP stop reading here this goes far more into detail.
Download for
omni-4.4.2-20140224-hammerhead-NIGHTLY
(it can work with newer or older versions too, It changes the framework-res.apk and SystemUI.apk, if they are changed on later nightlies I't will not work)
Screenshot with original 48 DPI NavBar
If you want to make a smaller NavBar by yourself I have made a little 20 Step How-To for you, based on this Guide by APatte111 and using this great Tool by Flextrick
you need AndroidMultitool, Java, Notepad++ and 7-Zip on your PC (this How-To is made for Windows).
(don't forget to add "C:\Program Files (x86)\Java\jre7\bin" (for your Java Runtime) to the PATH Var. in your Windows System Settings)
Here is the How-To:
Folder structure of the AndroidMultitool
GUI of the AndroidMultitool
1. Extract SystemUI.apk (system\priv-app) and framework-res.apk (system\framework) from ROM-ZIP
2. put both original files into a Recovery flashable ZIP, "framework-res.apk" under (system\framework) and "SystemUI.apk" under (system\priv-app) for restoring.
3. Copy both files to the "Files" folder of AndroidMultitool
4. Install Framework in AndroidMultitool
5. Decompile framework-res.apk
6. Go to "decompiled_apk" into "res\values" and open "dimens.xml" with Notepad++
7. Look for the "navigation_bar_height", "navigation_bar_height_landscape" (only matters for tablets) and "navigation_bar_width" entry
8. Change the DPI values to your preferences, for example 36.0dip/36.0dip/32.0dip and Save
9. Take a look into "decompiled_apk\framework-res\res" for folders like "values-mcc310-mnc-1" and delete the "-" in front of the last number it have to be "values-mcc310-mnc1" for compiling without errors.
10. Under compiling choose the folder of the decompiled framework-res "decompiled_apk\framework-res" and click compile
11. Open the new framework-res.apk under "Compiled_apk\framework-res" with 7-Zip and extract the "resources.arsc" file (thats the only one wich includes our changes)
12. Open the Original "framework-res.apk" with 7-Zip and put the resources.arsc into it, apply the overwriting and close 7-Zip
13. Decompile SystemUI.apk
14. Go to "decompiled_apk" into "SystemUI\res\layout" and open "navigation_bar.xml" with Notepad++
15. Search for "@drawable/ic_sysbar_back" and "@drawable/ic_sysbar_back_land" and delete the line " android:scaleType="center" " after it and save.
16. Under compiling choose the folder of the decompiled SystemUI "decompiled_apk\SystemUI" and click compile.
17. Open the original extracted "SystemUI.apk" with 7-Zip and extract the "META-INF" folder and "AndroidManifest.xml"
18. Open the new SystemUI.apk under "Compiled_apk\SystemUI" and insert the "META-INF" folder and "AndroidManifest.xml" file from the original "SystemUI" in it, apply the overwriting and close 7-Zip
19. Put both changed files into a Recovery flashable ZIP, "framework-res.apk" under (system\framework) and "SystemUI.apk" under (system\priv-app)
20. flash the ZIP in recovery and see your changes (if it failes, install your Restore-Zip from 2. and try the steps again)
Have fun with your new NavBar guys :highfive: :victory:
Changelog:
- version updated for OmniROM 4.4.2 20140224 (2014-02-24)
- version updated for OmniROM 4.4.2 20140206 (2014-02-07)
- version updated for OmniROM 4.4.2 20140203 (2014-02-03)
- version updated for OmniROM 4.4.2 20140128 (2014-01-28)
- version updated for OmniROM 4.4.2 20140123 (2014-01-23)
- version updated for OmniROM 4.4.2 20140117 (2014-01-17)
- version updated for OmniROM 4.4.2 20140115 (2014-01-15)
- version updated for OmniROM 4.4.2 20140105 (2014-01-05)
- version updated for OmniROM 4.4.2 20131227 (2013-12-27)
- version updated for OmniROM 4.4.2 20131217 (2013-12-17)
- version updated for OmniROM 4.4.2 20131212 (2013-12-12)
- version updated for OmniROM 4.4.1 20131208 (2013-12-09)
- 20131201 Version works flawless on Nightly 20131204, name changed (2013-12-04)
- version updated for OmniROM 20131201 (2013-12-02)
nvm, solved
auggie246 said:
nvm, solved
Click to expand...
Click to collapse
?!
tested on 20131204 and it works fine because there are no changes to SysUi and framework
next update will come after 4.4.1 OmniROM is available
Updated to 4.4.1 (Nightly 20131208)
which file should I modify to CM11? i can't find the string: "@drawable/ic_sysbar_back" and "@drawable/ic_sysbar_back_land" in SystemUI.apk... Can you help me?
[email protected] said:
which file should I modify to CM11? i can't find the string: "@drawable/ic_sysbar_back" and "@drawable/ic_sysbar_back_land" in SystemUI.apk... Can you help me?
Click to expand...
Click to collapse
are you looking in the navigation_bar.xml under the Decompiled "SystemUI\res\layout" folder?
€: OK, I've checked it and it is true there are not such values in CM11 SystemUI, so just try it with just the modified framwork-res.apk and see what happens, if the back button is not awkwardly big all is fine
Edit: - version updated for OmniROM 4.4.2 20131212 (2013-12-12)
No, I tried and does't work
[email protected] said:
No, I tried and does't work
Click to expand...
Click to collapse
Seems like CM is using some different code, and if you just change the values in the "dimens.xml" nothing happens?
€: - version updated for OmniROM 4.4.2 20131217 (2013-12-17)
I tried just changing the values in "dimens.xml" and doesn't change
kabauterman said:
Seems like CM is using some different code, and if you just change the values in the "dimens.xml" nothing happens?
€: - version updated for OmniROM 4.4.2 20131217 (2013-12-17)
Click to expand...
Click to collapse
updated to 20131227
anyone tried if it works with 20140103?
€: Doesn't work, I tried it.
can you please build a new version of your mod for omnirom 2014-01-03?
illnez said:
anyone tried if it works with 20140103?
€: Doesn't work, I tried it.
can you please build a new version of your mod for omnirom 2014-01-03?
Click to expand...
Click to collapse
for 20140105
https://drive.google.com/file/d/0B4ESb_YBhAxIRzhqelFWYmxRNnM/edit?usp=sharing
Thanks kabauterman for this mod.
It works with latest build also omni-4.4.2-20140113-hammerhead-NIGHTLY but with some problems,please can you fix it?
Thanks in advance
micr0g said:
Thanks kabauterman for this mod.
It works with latest build also omni-4.4.2-20140113-hammerhead-NIGHTLY but with some problems,please can you fix it?
Thanks in advance
Click to expand...
Click to collapse
I have made a how-to for all of you wich use a version of Omni I havn't made yet
Now you can find 20130115 in OP :victory:
https://drive.google.com/file/d/0B4ESb_YBhAxIYWZWWkdiX3dYWXM/edit?usp=sharing
20140117 added to OP
20140123 online
You can find 20140128 in Post #1
Pretty cool change to OmniROM, changing the SystemUI if no more needed thanks to the new NavBar changes possible in OmniROM.
And it seem that the framework-res file is still the same then in the last releases. :good:
Post #1 updated
So i pulled stock system folder and deodexed, zipaligned and signed.
Wanted to try flash it by twrp. So i copied one of custom roms meta inf folder but i get sysmapfile error.
Created certificates with signapk but there is no update-binary and update-script file. So i searched and learnt sth about update-script but what is exactly update-binary do? How can i edit for my rom or create one? can i use one of them with all devices rom?
Btw editing update-script didnt solve my sysmapfile error. Can someone guide me about meta-inf folder? All other articles just tells using another roms meta inf but it simply didnt work for me.
The update-binary file is different from one ROM to the next. For example, a CyanogenMod binary will be different from one in a custom ROM based off stock. In general, look at http://wiki.cyanogenmod.org/w/Doc:_About_Edify for an explanation of what the binary is. You will need to pull a binary from a custom ROM based off stock, preferably from the same version of Android.
I have a SM-T230NU Tablet I am trying to extract the patched v2.0 stagefright library from the stock rom :
T230NUUEU0APA1_T230NUXAC0APA1_XAC
By the way, I extracted by flashing the ROM to the device and then copied the files to an sd card and so on
I copied every thing from system/lib that begins with the name stagefright (total of 29 files) and tried to flash it in to a rom that doesn't have v2.0 patched but it doesn't work o.o Am i missing something. Or can anyone help me extract the files and make me a patch please
Hi,
Do you know how to extract kernel from installation file of rom and make flashable (in TWRP) zip kernel file ?
I need extract ant make flashable kernel file from [ROM][AQF5][6.0.1][G900x]SkiesROM UX v3.1 A7 2017
I will be grateful for your help
tomaasz said:
Hi,
Do you know how to extract kernel from installation file of rom and make flashable (in TWRP) zip kernel file ?
I need extract ant make flashable kernel file from [ROM][AQF5][6.0.1][G900x]SkiesROM UX v3.1 A7 2017
I will be grateful for your help
Click to expand...
Click to collapse
Hi,
Sorry for the delayed reply.
Can you be little more specific? Do you want to 1) extract the kernel (that is an "zImage") image or 2) simply the "boot.img"?
The second task is simple as you can simply copy the "boot.img" from the ROM zip. You can flash "boot.img" directly via twrp (no need to make flashable zip).
The first task, however, is bit complicated as it requires the use of some tools like mkbootimg or Android Image Kitchen to split the "boot.img". You can flash the obtained "zImage" by simply copying that into an existing anykernel based klte custom kernel. :laugh:
Feel free to contact me for any further clarification/help.
Hi,
Thanks for your answer. I needed flashable zip kernel file extracted from SkiesRom.
I wanted patch this by DualBoot
tomaasz said:
Hi,
Thanks for your answer. I needed flashable zip kernel file extracted from SkiesRom.
I wanted patch this by DualBoot
Click to expand...
Click to collapse
Hi, if you have a Linux, you can easily extract the zImage from the "boot.img" using mkbootimg (see previous comment for links). If you want me to do that job, feel free to send the "boot.img" of that mentioned ROM (I'll make a flashable anykernel zip file for you so that you can flash over any ROM).
Regarding the DualBoot, I really do not know...