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
Related
Thanks to our Senior Moderator dsixda , his Android Kitchen now has support for our Leo Nand too.
You can modify any Rom:
_Shipped
_Custom
_Nandroid Backups
It is easy to use with some automated features as:
_Deodex
_Zipalign
_Add scripts
_Add App2sd
_extract Kernel and initrd
_etc
Code:
===================================================================
HTC Android Kitchen - by dsixda (xda-developers.com)
===================================================================
Main Menu
1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all *.apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information
Advanced Options
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Unpack or re-pack a boot image
21 - Unpack data.img
22 - Sign APK file(s)
23 - Convert update-script or updater-script
24 - Run plugin scripts
99. Build ROM from working folder
00. About/Update kitchen
0. Exit
dsixda said:
How do I import a ROM into the kitchen to use as my base?
From a shipped ROM:
First, find the shipped ROM for your device, usually from htc.com or from searching xda-developers (check the Wiki or sticky posts under your device's sub-forum).
This link may help: Various devices
Please don't ask me for links, as I don't know everything or own all devices. ;-)
The shipped ROM can be found in three different formats. Identify the type you have downloaded:
If the shipped ROM is in a .ZIP format, then simply copy it to the kitchen's original_update folder.
OR if the shipped ROM consists of system.img and boot.img files, then copy those two files to the kitchen's original_update folder.
OR if the shipped ROM is in an .EXE format, then do the following:
In Windows, run the shipped ROM's .EXE file till it gets to the first dialog. Stop there but don't close the window yet.
Go to Start->Run and type: %TEMP%
When the folder opens, search for Rom.zip (use the "magnifying glass" Search button)
Copy Rom.zip to your kitchen's original_update folder
OR from a cooked/custom ROM:
Copy the update.zip (or equivalent ZIP file) to your kitchen's original_update folder
OR from a Nandroid backup (under /sdcard/nandroid) [NOT RECOMMENDED FOR NON-STOCK ROM BACKUPS]:
Copy the system.img and boot.img files from the backup folder to your kitchen's original_update folder
NOTE: The Nandroid-backup method of ROM customization is not the best method, because the kitchen may not account for various advanced options that were added outside of this kitchen (these options are in the update-script file which was in the original ROM but is not in the backup. The kitchen needs to re-create this file and 'guess' those options). However, it will support Nandroid backups that already have basic features like root, busybox and /data/app functionality.
Click to expand...
Click to collapse
Go to dsixda thread and grab your Kitchen now and have some fun with it!
KITCHEN THREAD
If you like it don't forget to hit thanks to dsixda and consider to him a donation for his work.
How to use HD2
Make Tut 4 HD2 plz....
oh em gee!
for those asking for a tutorial,
http://forum.xda-developers.com/showthread.php?t=633246
if you visit the kitchen's thread you will find much more information and step-by-step guide for all operating systems.
thanks
In the thread of dsixda everything are available step-by-step.
I can confirm that it is working and tested from the begin of implementation of this Nand support.
I used it for HD2, sometime work, sometime not work
Whenever I cook using this Awesome kitchen I successful have a zip file. When I try to flash it It gives me an error (Status 6) and I do not know what to do to resolve this issue.
Raptordin said:
Whenever I cook using this Awesome kitchen I successful have a zip file. When I try to flash it It gives me an error (Status 6) and I do not know what to do to resolve this issue.
Click to expand...
Click to collapse
Nice to know that an arabian is cooking
Waiting your builds because i'm sure you will be incorporating arabic roms and full arabic support by default!
This error sound of something wrong in updater-script, in this kitchen you must:
1. convert updater-script to update-script for working on it
2. convert it back to updater-script before make the zip process.
Anyway fore me it worked at 1st shot and this is what i made and in Dsixda thread there is a good tutorial and a video that explain all.
Raptordin said:
Whenever I cook using this Awesome kitchen I successful have a zip file. When I try to flash it It gives me an error (Status 6) and I do not know what to do to resolve this issue.
Click to expand...
Click to collapse
Life Engineer said:
Nice to know that an arabian is cooking
Waiting your builds because i'm sure you will be incorporating arabic roms and full arabic support by default!
Click to expand...
Click to collapse
I am still a noob when it comes to Android but will do my best, Used to be very good with WinMob bt still starting here, will try my best though.
af974 said:
This error sound of something wrong in updater-script, in this kitchen you must:
1. convert updater-script to update-script for working on it
2. convert it back to updater-script before make the zip process.
Anyway fore me it worked at 1st shot and this is what i made and in Dsixda thread there is a good tutorial and a video that explain all.
Click to expand...
Click to collapse
Thanks for your reply, I did convert it back and forth though but still same error. The tutorials are very nice and I did follow them to the letter. Will try again today after I get back home from work and will try to get another base to start from.
Np raptordin,
if you wanna say to me what build you are trying to mod and what mod you want to do, i can give it a go and see if i get the same error.
af974 said:
Np raptordin,
if you wanna say to me what build you are trying to mod and what mod you want to do, i can give it a go and see if i get the same error.
Click to expand...
Click to collapse
Will test again in an hour or so when I get home and report back. Thanks for your interest.
Just a reminder -- if you have a boot.img in your ROM's working folder, and it didn't get converted to "boot" folder after building the ROM, then you have to do the conversion manually.
1) Select option 20 - "Unpack or re-pack a boot.img"
2) Select option c - "Convert boot.img into NAND boot folder"
Then you can build.
If you are using a custom HD2 ROM then this step is probably not necessary, as the kitchen will aready have created the boot folder and removed the boot.img. To make sure, just open the .ZIP file that was created by the kitchen after building.
Thanks for info Dsixda,
I'm facing a couple of problems with the Kitchen, here they are:
1. In the Kitchen Rom info app2sd are not installed but it still in init.d
2. if i add /data/app (option 13) market apps installation end with an error.
Code:
Working folder information
Android OS version : 2.3.3
Device : bravo
ROM Name : GRI40
Rooted (unsecured boot.img) : YES
Rooted (Superuser.apk + su) : YES
BusyBox installed : YES
BusyBox run-parts support : YES
Apps2SD enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : YES
Bash shell support : YES
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I'm using this rom as base http://forum.xda-developers.com/showthread.php?t=933951
af974 said:
Thanks for info Dsixda,
I'm facing a couple of problems with the Kitchen, here they are:
1. In the Kitchen Rom info app2sd are not installed but it still in init.d
Click to expand...
Click to collapse
So you don't have an "a2sd" file under /system/bin or /system/xbin or anywhere else? What options did you select for apps2sd (e.g. runparts?).
2. if i add /data/app (option 13) market apps installation end with an error.
Click to expand...
Click to collapse
You need to be specific.. what is the error? And when you say 'installation' do you mean while the kitchen is adding the data/app folder, or while the ROM is booting?
Nope, there is nothing in there but there is the script in init.d " 10app2sd", though i'm speaking of original update.zip.
dsixda said:
So you don't have an "a2sd" file under /system/bin or /system/xbin or anywhere else? What options did you select for apps2sd (e.g. runparts?).
Click to expand...
Click to collapse
After the boot, i go to market and download an app but it cant be installed.
You need to be specific.. what is the error? And when you say 'installation' do you mean while the kitchen is adding the data/app folder, or while the ROM is booting?
Click to expand...
Click to collapse
Whoot! time to get my chef on!
Thanks you for this great tool
af974 said:
Nope, there is nothing in there but there is the script in init.d " 10app2sd", though i'm speaking of original update.zip.
Click to expand...
Click to collapse
Is it really apps2sd (apps to ext3) or is it just that hack that is used to move all apps to the fat32 partition of the SD card (the option that is in Settings of Cyanogen ROMs)? Can you paste the contents of that file here please (in
Code:
tags)
[QUOTE]
After the boot, i go to market and download an app but it cant be installed.[/QUOTE]
I don't know anything about that, probably your device's or ROM's issue because it works elsewhere. When the kitchen adds /data/app to the working folder it only sets the permissions for that folder when flashing.
Hi,
everytime I want to flash a new version of a rom I have to modify the zip file contents, i.e. delete some files etc, which is a very tedious process.
Thats why I created a little tool for Windows (requires .NET 3.5) that can do the following with a zip file of a rom:
- Delete files
- Add / Replace files
- extract .apk's, decompile them, modify (regex replace) inside text / xml files within, recompile them and put the updated version back into the rom zip.
The tool is still beta, so there could be many errors if you don't use it correctly... always make a copy of the rom zip before using this tool on it
The included apktool (for decompile/recompile of apk) requires JRE 1.6 and only works for Android Jellybean roms / framework-res.apk's - but I think you could just use another apktool version for different Android versions.
Included in the package is a sample configuration that is basically exactly what I am using. Of course you can change what files to add, delete and modify. Also there is a screenshot attached so you can see what it looks like - as you can see you need to have some basic knowledge of how android rom stuff works, I don't think this is useful to total noobs, sorry.
If you have any problems / suggestions feel free to write here.
I hope this is useful to someone
Regards
Abomb
Changelog:
1.0: Inital release
1.1: Some error checking, not all errors will be caught but at least some basic ones.
1.2: Files to delete and apk's to modify can now be selected from the zip file via file browser
1.3: Log during modify operation and bugfixes
1.4: More bugfixes, plus the settings are now stored in the image of a cat
This looks like it could be useful. Thanks for sharing.
Great!!! easy to edit a rom for me
Thx, great job.
New version 1.1 with some error checking released.
Version 1.3 released with the following changes:
- Files to delete and apk's to modify can now be selected from the zip file via file browser
- Log during modify operation and bugfixes
Last version don't work with last nightly CM10 and Jellybro when trying to modify Navbar DPI.
ZipTest Error.
Sorry for bad English.
DeadMetaler said:
Last version don't work with last nightly CM10 and Jellybro when trying to modify Navbar DPI.
ZipTest Error.
Sorry for bad English.
Click to expand...
Click to collapse
Yeah I noticed, the problem seems to be thatthe zip file contains some folders like "a" and "A" - which is no Problemon Linux, Android etc, but does not work under Windows I haven't found any solution yet, but I'll try to find a fix for it.
Hi all,
We have so much excellent JB SAMMY 4.1.2 ROMs on XDA. I9100 still here !!
For some reasons proper to DEVs, many files are removed from their flashable ZIP of ROM.
These files, APKs and dependencies, are frequently all the bloatwares from Samsung and Google.
Generaly, with ROM, DEVs never forget to upload their "Removed Apps Pack".
Their "Removed Apps Pack" are frequently a CWM flashable ZIP.
Sometime, we need some files from their pack and we dont need to flash the entire pack.
There is a simple solution :
In this post, i want to explain to ppl that if they only need one or two apks from the missed appq pack provided for their ROM installed, they have to delete all the others apks in the ZIP before flashing it. that's all.
updater-script doesn't need to be touch.
- open pack with winrar
- browse folders in winrar,
go to \preload\symlink\system\app\ and delete all you dont want
go to \system\app\ folder too and delete all you dont want too
- close winrar and let it work!
Merci and Thanks.
An pretty simple and easy guide
Good job Troubadour
Hi all.
before anything :
- this tool is for especialy for dualbooters because i havent tested in 1rst rom. but updater-script manage kernel flashed. prepare odin in case of bad flash, you're advised.
- always make nandroid before use and flash with my tool.
I saw that ppl have many trouble to install 4.4.2 kitkat roms on their device.
it seems that we have manu such "error status 7" , and these were about setting persmissions during flash.
so i decide to make an aroma to avoid this error.
if you flash an original 4.4.2 Kitkat rom and have the error, no need to flash another compatible recovery kernel to re-try, just use my aroma flasher with the steps i descride below. In the aroma advanced MENU, you will choose set_perm commands compatible flash instead of set_metadata commands persmission to see if flask process will work in fine
Sure, at end of process, a kernel will be flashed, dorimanx branch 8 i have put in pach you went to donwload, or another you have put instead like i describe in extra step 6 below too.
so, AROMA structure details is like this :
pach/AROMA
---------backupEFS <------- useful script, no need to touch.
---------KERNEL <------- place here your boot.img file. (original rom or other)
---------maliv2
-------------system/lib/egl/ <-------- maliv2 .so libs contents, no need to touch.
pach/data/app <--------- you can put som apks here, moved from /system/app/ (i often move in latinIME.apk from /system/app/ and then i free 40Mo on /system/ partition, its good for GAPPS)
pach/META-INF/....../ <--------- no need to touch.
the available download pach i use for some months now , is here :
UniversalAROMAinstallerFOR-4.4.2-ROMs-DefinitivePach.rar - 8.53 MB
how to use it
1 - download any kitkat 4.4.2 ROM your want to install I9100.
2 - try it normaly, and see if you have error on flash.
3 - when you got it, on PC, make a safe copy ot it somewhere, and open it with WINRAR. Then delete META-INF and other boot.img file. just let system folder in ZIP.
4 - uncompree my AROMA somewhere.
5 - drag and drop the 3 "bolded" folders (in aroma structured details) in ZIP rom you still have opened.
extra step 6 : in AROMA/KERNEL/ folder, you will find dorimanx branch 8 version (new @StanTRC recovery inside) i have put. You can replace it with any boot.img you want , even those from original rom zip you have safely somewhere on your PC. just extract boot.img from it and replace with in you new aroma installer rom zip you went to manage in steps 3, 4 and 5 .
aroma choice you will have :
"Compatibility of your Recovery Kernel",
"Your Kernel is compatible for set_metadata commands"
"Your Kernel ONLY understand set_perm commands"
"choose your based KK similar rom",
"AOSB BEANSTALK C-ROM EHNDROIX"
"CARBON"
"CM11 JELLYBAM"
"SABER PAC"
"PA"
"Resurrection Remix"
"SLIM SPIRIT"
"NEATROM AICP"
"SOKP"
"Backup EFS",
"Backup your EFS folder before flash"
"Skip"
"Kernel to flash at end of process",
"DorimanX 8 and MaliV2"<---------- option that serve to flash MALIV2 for dorimanX branch 8 users, dualbooters.
"any other kernel"
EXTRA TOOL : .db qulite bases "wiper" , it delete some .db files in some /data/data/com.android........../databases/ folders, usefull when we flash from <> based 4.4.2 roms, CM11 , RR , PAC , SLIM, PA....sometimes worked fines for me.
"Delete some SQlite .db files in ROM",
"YES ","Delete some SQlite .db from you installed rom to avoid com.android.phone FC or other FCs"
"NO thanks we can FLASH the ROM"
again, this is just for test and fun , dualbooters will like more that "normal" users. no risk to flash kernel in 2nd rom, but remember need maliv2 during AROMA....and i always afraid someone that try my work on 1rst rom will brick its device.....so i advertise everyone that before upload my "daily" works, i'm not always flashing them on my 1rst rom.
thanks.
How to use the pach
Hope image tuto are good readable .
1 - open ROM.zip with winrar
2 - delete some folders in ROM.zip
3,4 - what to copy from my pach to the ROM.zip
5 - explain about structure and tweak .
no image 6 - just flash new ROM.zip with my aroma.
thanks.
Ultimate Aroma Addons for KitKat 4.4.2 and JB 4.1.2 DualBoot Roms.
extracted Aroma Managment
Code:
"ROM TYPE",
"which type of rom do you use",
"JB 4.1.2
"KK ROM 4.4.2"
Code:
"4.1.2 rom runing",
"its on Normal install
"its on DualBoot install
Code:
"4.4.2 Options",
"apply or remove APKs",
"Addons apks
"Remove them
Code:
"Addons APKS",
"tick to add",
"Google Camera with Sphere"
"Google Keyboard"
"TW Launcher from PhenomRom TW Accuweather"
"S4 settings for KitKat
"S4 TW Launcher BY ANMOL7IFY need 25Mo on system
"Htc BlinkFeed v11 need 31Mo on system
"Htc BlinkFeed v11 on data partition
"Themes in data (2 cobalts themes added)
Code:
"Remove some added apks",
"tick to remove",
"Remove Google Keyboard
"Remove TW Launcher stuffs
"Remove S4 settings
"Remove S4 TW Launcher BY ANMOL7IFY
"Htc BlinkFeed v11 from all partitions
"remove Themes from data
Code:
"Google Play Sore 4.6.17",
"Install it or Not",
"Inverted Multi DPI Play Store
"Multi DPI Play Store
"Skip to Google Play Services 4.3.23
Code:
"Google Play Services 4.3.23",
"Install it or Not",
"Install it
"Skip
The Ultimate tool is here :
I9100Utimate-Aroma-AddonsFor-4.4.2or4.1.2ROMs-TouchWiz-GgSphere-GgKB-Themes-GgPLAY-GgServices.zip - 168.22 MB
thanks.
Troubadour666 said:
maybe another tool soon
Click to expand...
Click to collapse
hi
working perfectly, tested with crdroid built7
Flash session added in post 3
@nik60 , yes i think is good too
Troubadour666 said:
@nik60 , yes i think is good too
Click to expand...
Click to collapse
hi,
maybe you can added in aroma "pa micro gapps" that work in any rom
so people flash rom and gapps in one time
nik60 said:
hi,
maybe you can added in aroma "pa micro gapps" that work in any rom
so people flash rom and gapps in one time
Click to expand...
Click to collapse
i have made one pach with onle play store and google services , with others goodies, but i can re-script it with gapps. give me a way to follow what you think ppl need the most .
i mean this one, but i'm on some research about better way to use it, tomorrow i will post good version.
I9100-Aroma-addonsFor-KitKat-4.4.2-ROMS.zip - 180.81 MB
this one is that one i use in video review, you see i NEVER have trouble with space /system/ partition because initial ZIP ROM is modify with some apk in /data/app/ during flash, so i can add more goodies in /system/app/ using this aroma with play store, google sphere and touchwizz i use....see tuto how to move apks from /system/app/ to data/app/ before flash the rom and then gain space on /system/ to flash more files without disturbing /data/app/ we never want to full wipe to.
AND REMEBER external .sh script dont work well with dorimanx new recovery, i mean move choice in aroma so its better to have space in system before use and not use these options during aroma (i mean options to gain space)
thanks.
Troubadour666 said:
i have made one pach with onle play store and google services , with others goodies, but i can re-script it with gapps. give me a way to follow what you think ppl need the most .
i mean this one, but i'm on some research about better way to use it, tomorrow i will post good version.
I9100-Aroma-addonsFor-KitKat-4.4.2-ROMS.zip - 180.81 MB
this one is that one i use in video review, you see i NEVER have trouble with space /system/ partition because initial ZIP ROM is modify with some apk in /data/app/ during flash, so i can add more goodies in /system/app/ using this aroma with play store, google sphere and touchwizz i use....see tuto how to move apks from /system/app/ to data/app/ before flash the rom and then gain space on /system/ to flash more files without disturbing /data/app/ we never want to full wipe to.
AND REMEBER external .sh script dont work well with dorimanx new recovery, i mean move choice in aroma so its better to have space in system before use and not use these options during aroma (i mean options to gain space)
thanks.
Click to expand...
Click to collapse
hi,
i tink there is't problem with micro gapps and free space in system
i have crdroid , 461mb/495mb in system--crdroid is 208mb and was bigger rom (ONLY sokp is 228,but need your gapps)
is possible delete Google home in micro gapps for example(12mb)-any rom have launcher
Amazing.
Keep up the good work my friend.
Vivek_Neel said:
Amazing.
Keep up the good work my friend.
Click to expand...
Click to collapse
i think so too
Hi Troubadour666,
it is weekend and I'm testing on again.
Have just your "Ultimate Aroma Addons for KitKat 4.4.2 and JB 4.1.2 DualBoot Roms" installed and it works just fine.
"S4 settings for KitKat
"S4 TW Launcher BY ANMOL7IFY need 25Mo on system
Can you tell me what is the difference between TW ANMOL7IFY and TW PhenomRom ??
Am still looking for transparent accuweather ??
Regards Klaus
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