Database Info

[DEV] sdat2img 1.1 - img2sdat 1.7 ◦ Unpack/re-pack android DAT files

Introduction
You probably know already that starting from Android 5.x (Lollipop) compiled roms (aosp,cm,stock) are not compressed anymore the way they used to be on previous android versions. On previous versions all content inside /system folder that has to be extracted within our device was either uncompressed (simple /system folder inside our flashable zip) or compressed in a system.img file, which it is a ext4 compressed file; both of these, anyway, were readable and we could see all system files (app,framework, etc).
The problem comes in >=5.0 versions, this method is not used anymore. Why? Because roms started to be always larger, so it is necessary to compress them even more.
What does new Android zips (full roms, but also otas) contain?
New Android flashable zips are made this way:
boot.img (kernel)
file_contexts (selinux related)
META-INF (folder containing scripts)
system.new.dat (compressed /system partition)
system.patch.dat (for OTAs)
system.transfer.list (see explanation below)​
What does updater-script contains then?
The updater-script uses a brand new function: block_image_update(), this method basically decompresses necessary files inside the device. Let's study it.
From google git source code, if we go inside the new file /bootable/recovery/updater/blockimg.c, we find at the end of it the registration of the function block_image_update() as the method BlockImageUpdateFn() which starts at line 254. Here finally we find all information we need to know about the decompression of the .dat file(s). First file we analyze is system.transfer.list which Google tells us:
The transfer list is a text file containing commands to transfer data from one place to another on the target partition.
Click to expand...
Click to collapse
But what each line means?:
First line is the version number of the transfer list; 1 for android 5.0.x, 2 for android 5.1.x, 3 for android 6.0.x, 4 for android 7.x/8.x
Second line is the total number of blocks being written
Third line is how many stash entries are needed simultaneously (only on versions >= 2)
Fourth line is the maximum number of blocks that will be stashed simultaneously (only on versions >= 2)
Fifth line and subsequent lines are all individual transfer commands.
Click to expand...
Click to collapse
Ok, but how to decompress the system.new.dat file?
All instructions are below. sdat2img, rimg2sdat and img2sdat binaries are involved. Please read carefully step by step.
NOTE for OTAs
If you are looking on decompressing system.patch.dat file or .p files, therefore reproduce the patching system on your PC, check imgpatchtools out by @erfanoabdi.
You can use/modify these files and/or include them in your work as long as proper credits and a link to this thread are given.
If you have questions or problems write here
Are you building from source and want to revert to the old flashing method without DAT files?
Do this (thx @Elluel):
1 - Delete this line
2 - Make sure you have this commit
Thanks
- howellzhu & luxi78 - for initial source codes
- all contributors from github

Ubuntu
Ubuntu 64-bit - Guide
Step 1 - Decompressing = DAT (sparse data) -> EXT4 (raw image)
We're now using sdat2img binary, the usage is very simple (make sure you have python 2.7+ installed):
./sdat2img.py <transfer_list> <system_new_file> [system_img]​- <transfer_list> = input, system.transfer.list from rom zip
- <system_new_file> = input, system.new.dat from rom zip
- [system_img] = output ext4 raw image file
and a quick example:
./sdat2img.py system.transfer.list system.new.dat system.img​by running this command you will get as output the file my_new_system.img which is the raw ext4 image.​
Step 2 - Decompress EXT4 (raw image) -> OUTPUT folder -> Compress EXT4 (raw image)
Now we need to mount or ext4 raw image into an output folder so we can see apks/jars etc.
To do this we need to type this command:
sudo mount -t ext4 -o loop system.img output/​As you can see there is a new folder called output which we can edit/modify/delete your files (not able to? see here)
Now we need to compress it back to a raw ext4 image, to do this we need the make_ext4fs binary. Make sure you have the file_contexts file (taken from the Rom zip) inside the make_ext4fs path. Then type this (got issues? see here)
./make_ext4fs -T 0 -S file_contexts -l 1073741824 -a system system_new.img output/​You will get the new raw ext4 image called 'system_new.img' ready for the next step.​
Step 3 - Converting = EXT4 (raw image) -> IMG (sparse image)
Now we need to convert the ext4 raw image into a sparse image. For this you need img2simg binary you can find here (thx to @A.S._id).
The usage is simple:
img2simg <raw_image_file> <sparse_image_file>​Pretty self-explanatory, the output will be a new sparse image (.img).​
Step 4 - Converting = IMG (sparse image) -> DAT (sparse data)
Now we need the img2sdat binary, the usage is very simple (make sure you have python 2.7+ installed):
./img2sdat.py <system_img>​- <system_img> = name of input sparse image file (from step 3)
As you can see the output is composed by system.transfer.list, (system.patch.dat) & system.new.dat, ready to be replaced inside your Rom zip.​
DOWNLOADs
sdat2img.py
- github.com
make_ext4fs
- mega.co.nz
img2sdat.py
- github.com

Source - Changelog
sdat2img
Repo: https://github.com/xpirt/sdat2img
Changelog: https://github.com/xpirt/sdat2img/commits/master
Source: https://github.com/xpirt/sdat2img/blob/master/sdat2img.py
img2sdat
Repo: https://github.com/xpirt/img2sdat
Changelog: https://github.com/xpirt/img2sdat/commits/master
Source: https://github.com/xpirt/img2sdat/blob/master/img2sdat.py

Windows
Windows 32/64 bit - Guide
Step 1 - Decompressing = DAT (sparse data) -> EXT4 (raw image)
We're now using sdat2img.py binary, the usage is very simple (make sure you have python 3.x installed):
sdat2img.py <transfer_list> <system_new_file> <system_ext4>​- <transfer_list> = input, system.transfer.list from rom zip
- <system_new_file> = input, system.new.dat from rom zip
- <system_ext4> = output ext4 raw image file
and a quick example:
sdat2img.py system.transfer.list system.new.dat system.img​by running this command you will get as output the file my_new_system.img which is the raw ext4 image.​
Step 2 - Decompress EXT4 (raw image) -> OUTPUT folder -> Compress EXT4 (raw image)
Now you should either move to Ubuntu x64/x86 or follow the 2nd step from the Ubuntu guide on cygwin 32 bit.​
Step 3 - Converting = EXT4 (raw image) -> IMG (sparse image)
Now we need to convert the ext4 raw image into a sparse image. For this you need img2simg binary you can find here (thx to @A.S._id).
The usage is simple:
img2simg.exe <raw_image_file> <sparse_image_file>​Pretty self-explanatory, the output will be a new sparse image (.img).​
Step 4 - Converting = IMG (sparse image) -> DAT (sparse data)
Now we need the img2sdat binary, the usage is very simple (make sure you have python 2.7+ installed):
img2sdat.py <system_img>​- <system_img> = name of input sparse image file (from step 3)
As you can see the output is composed by system.transfer.list, (system.patch.dat) & system.new.dat, ready to be replaced inside your Rom zip.​
DOWNLOADs
sdat2img.py
- github.com
make_ext4fs
- mega.co.nz
img2sdat.py
- github.com

Is there any tool to browse (and/or manipulate) these .dat files in Windows?

01 Vlatce said:
Is there any tool to browse (and/or manipulate) these .dat files in Windows?
Click to expand...
Click to collapse
i don't think so, though you can install ubuntu in a virtual machine as 64-bit and decompress there without problems.
edit: windows binaries added to OP.

xpirt said:
i don't think so, though you can install ubuntu in a virtual machine as 64-bit and decompress there without problems.
Click to expand...
Click to collapse
I found one, Ext2Explore, it can browse and extract lollipop .dat files

01 Vlatce said:
I found one, Ext2Explore, it can browse and extract lollipop .dat files
Click to expand...
Click to collapse
Can you explain how to work in more detail ? Thanks.

chihliouma said:
Can you explain how to work in more detail ? Thanks.
Click to expand...
Click to collapse
With that application you can open the system.new.dat file like a zip archive
Sent from my Nexus 5

xpirt said:
i don't think so, though you can install ubuntu in a virtual machine as 64-bit and decompress there without problems.
Click to expand...
Click to collapse
01 Vlatce said:
I found one, Ext2Explore, it can browse and extract lollipop .dat files
Click to expand...
Click to collapse
Confirmed.
Works perfectly..
Thanks a lot! This will save a lot of time theming.. (pulling the system, settings, framework without having to flash the rom first)
Oh, just for s&g's i extracted ("decompiled") the system.new file, the files (app, prive-app, framework, media, etc) all got placed on my desktop -- i deleted the system.new file from the rom -- i then placed the folders and files that got extracted and placed them in the rom -- i flashed it -- it booted! lol.. didnt think it would... but anyways, there's that.
For those who want to try:
--- > its basically self explanatory.
- once downloaded (the link above) extract the contents from the zip (i just went ahead and extracted to my desktop)
- right click the linux penguin
- run as administrator - the window will pop up
- go to file > open image > find your system.new image (should already be extracted from the rom and placed on your desktop)
- click open
- you should now see your image (or path) in the windows -- double click them (i doubled clicked both the right and left side)
- now you should be able to see all the folders
---> if you want to extract those folders
- just go up to the top
- click save and choose an extraction (i chose Desktop)
Hoped i helped -- any questions or confusion, dont be shy to ask -- i probably went too fast, idk lol
Enjoy!

Incredible_Culp said:
Confirmed.
Works perfectly..
Thanks a lot! This will save a lot of time theming.. (pulling the system, settings, framework without having to flash the rom first)
Oh, just for s&g's i extracted ("decompiled") the system.new file, the files (app, prive-app, framework, media, etc) all got placed on my desktop -- i deleted the system.new file from the rom -- i then placed the folders and files that got extracted and placed them in the rom -- i flashed it -- it booted! lol.. didnt think it would... but anyways, there's that.
For those who want to try:
--- > its basically self explanatory.
- once downloaded (the link above) extract the contents from the zip (i just went ahead and extracted to my desktop)
- right click the linux penguin
- run as administrator - the window will pop up
- go to file > open image > find your system.new image (should already be extracted from the rom and placed on your desktop)
- click open
- you should now see your image (or path) in the windows -- double click them (i doubled clicked both the right and left side)
- now you should be able to see all the folders
---> if you want to extract those folders
- just go up to the top
- click save and choose an extraction (i chose Desktop)
Hoped i helped -- any questions or confusion, dont be shy to ask -- i probably went too fast, idk lol
Enjoy!
Click to expand...
Click to collapse
I can't get this to work at all. I'm using Win 7 Pro and I've actually used this app before with stock Nexus 7 factory images and it worked fine.. What file did you actually download? I d/l 2 different versions, one was beta 2.0 and the other was a zip that said 2.2.71 but the about on the exe says 2.1, which is the version I've been using for quite a while.
With the beta 2.0, there's not even an option to open a file and with the 2.1, it errors out every time. After opening system.new.dat image and double clicking, it just hangs and the program stops responding. If I try clicking on it and selecting save, it allows me to select a folder to save it in but I just get a dialog box that says saving files and then hangs at 24% every time, finally crashing with a Microsoft C++ runtime error.
Oh btw, you didn't go too fast LOL, this is really a simple app to use but it's just not working for me with these block image files. Maybe I'm missing something but it's got me scratching my head. :laugh: If you have any ideas, I'm all ears.
Thanks,
Mike T

webdroidmt said:
I can't get this to work at all. I'm using Win 7 Pro and I've actually used this app before with stock Nexus 7 factory images and it worked fine.. What file did you actually download? I d/l 2 different versions, one was beta 2.0 and the other was a zip that said 2.2.71 but the about on the exe says 2.1, which is the version I've been using for quite a while.
With the beta 2.0, there's not even an option to open a file and with the 2.1, it errors out every time. After opening system.new.dat image and double clicking, it just hangs and the program stops responding. If I try clicking on it and selecting save, it allows me to select a folder to save it in but I just get a dialog box that says saving files and then hangs at 24% every time, finally crashing with a Microsoft C++ runtime error.
Oh btw, you didn't go too fast LOL, this is really a simple app to use but it's just not working for me with these block image files. Maybe I'm missing something but it's got me scratching my head. :laugh: If you have any ideas, I'm all ears.
Thanks,
Mike T
Click to expand...
Click to collapse
hmm interesting..
im using windows 8.1
idk how much help i can be because i just downloded the first option (provided by the link above) and went from there.
like you said, theres two.. the .exe and the .zip.. i downloaded the .exe

Incredible_Culp said:
hmm interesting..
im using windows 8.1
idk how much help i can be because i just downloded the first option (provided by the link above) and went from there.
like you said, theres two.. the .exe and the .zip.. i downloaded the .exe
Click to expand...
Click to collapse
So, did you d/l the zip that was modified 2006-8-26, which is version 2.0 beta, or did you click the link which said download latest release?
Mike T

webdroidmt said:
So, did you d/l the zip that was modified 2006-8-26, which is version 2.0 beta, or did you click the link which said download latest release?
Mike T
Click to expand...
Click to collapse
ha! didnt even see there was a latest release..
i downloaded the 2006-8-26 apparently -- didnt even look at that date either LOL
i dont want to try the latest now -- this one works fine for me lmao -- dont want to ruin it.. ah, screw it, im downloading the latest now
EDIT: Ok, i lied.. i just checked my trash.. i did download the lastest release .zip .. the 2271..

@webdroidmt @Incredible_Culp Download from here lol: http://sourceforge.net/projects/ext2read/

Maybe something with my PC setup or Win 7 because the 2006-8-26 version doesn't even give me an option for opening a file image. It actually loads up looking like an incomplete application, it's also a very small filesize. Did you just d/l the ext2explore exe, or did you also d/l ext2read2 beta zip?
Mike T

webdroidmt said:
Maybe something with my PC setup or Win 7 because the 2006-8-26 version doesn't even give me an option for opening a file image. It actually loads up looking like an incomplete application, it's also a very small filesize. Did you just d/l the ext2explore exe, or did you also d/l ext2read2 beta zip?
Mike T
Click to expand...
Click to collapse
Use the download link in the above post and click the green download button, and it should be the correct version, from 2012 rather than 2006.

Lethargy said:
@webdroidmt @Incredible_Culp Download from here lol: http://sourceforge.net/projects/ext2read/
Click to expand...
Click to collapse
That's the one I've been using for quite some time. As mentioned in my previous post, the system.new.dat file just "appears" to be saving but hangs at 24%, then eventually crashes. I'm stumped, should be so easy but it doesn't want to cooperate. LOL
Thanks anyway,
Mike T

webdroidmt said:
That's the one I've been using for quite some time. As mentioned in my previous post, the system.new.dat files just "appear" to be saving but hangs at 24%, then eventually crashes. I'm stumped, should be so easy but it doesn't want to cooperate. LOL
Thanks anyway,
Mike T
Click to expand...
Click to collapse
Weird. Try redownloading the ROM you're trying to extract?

Lethargy said:
Use the download link in the above post and click the green download button, and it should be the correct version, from 2012 rather than 2006.
Click to expand...
Click to collapse
Thanks for trying guys, that is exactly the one I've been using. I downloaded it again a few seconds ago and still getting the same result. :laugh:
Thanks.
Mike T
---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------
Lethargy said:
Weird. Try redownloading the ROM you're trying to extract?
Click to expand...
Click to collapse
I've actually tried with images from 3 different roms and they all give me the same result. It's cool, I just won't be able to play around as much as I used to porting stuff.
Mike T
---------- Post added at 01:15 AM ---------- Previous post was at 01:09 AM ----------
Lethargy said:
Weird. Try redownloading the ROM you're trying to extract?
Click to expand...
Click to collapse
Just curious, you guys aren't changing the file extension to something other than .dat, right?
Mike T

How to port roms to your mtk with android device

HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE
Most of us have always wanted to use custom roms but there just no custom roms for our devices so we just use different app launchers and uninstall some bloatware to make our stock rom feel good.
Rom porting makes it possible to use a custom rom on your mtk device provided in this tutorial they have the same chipset (example: mtk 6582 ported to mtk6582).
THINGS NEEDED :
1. B1 archiver / ES FILE EXPLORER
2. Root Browser.
4. A rooted device is also needed but not much important if you have CWM INSTALLED WITHOUT ROOT.
PROCEDURE :
1. Make a backup of your current rom, preferably CWM backup. You can either use MTK DROID TOOLS or ROM MANAGER...
The location of the backup will be at clockwork/backup/"date and time of the backup ". This is very important since we will need stuff from the back up and we will also use the backup to recover the phone should the ported rom give any problems.
2. At this point I presume you have already downloaded the apps needed and the custom rom you want to use which is in a zip format( this was not important but I had to bring it up cause I know zombies could be reading this.
3. Now extract the custom Rom with Root Browser. if you extracted with Root Browser then the location will be "speedsoftware/extracted/"folder with the name of the custom rom "".
4. Now open Root Browser and open the folders side by side "custom rom which will be ported at one side and other side will be used for searching for the location of the things needed for the custom rom.
5. Delete the following from the Custom rom:
Boot.img
logo.bin (You do this only when you like the Your current logo.bin)
system/vendor
system/usr
system/lib/hw
system/lib/modules
system/lib/libncurses.so
system/etc/firmware
system/etc/vold.fstab
system/etc/vold.fstab.nand
system/etc/bluetooth
6. Now that you have deleted them from the custom rom replace them. You will find the boot.img at clockworkmod/back/"folder with date and time"/boot.img. The rest of the files and folders will br located in the Root /system. Just copy and paste
7. Now at the custom Rom panel go back to where you find the "META-INF" folder,open /google/android will now long press on "updater script" and tap on open with then select text editor.
8. Check The mount & format point check something like this mmcblk0p. A number is always written after the "P" replace the number of your BASE to PORT.
9. Check multi select in B1 archiver Select ( do not archive the folder the files are in but the individual files in the folder containing the extracts)
10. Compress to ZIP file wait till the process finished. Now boot to recovery and flash your ROM
Good luck in porting Your Rom... I have used this method to port 5 roms including AROMA ROMS. and I have never ported a Rom with a pc before
MAYBE U NEED TO EXTRACT THE BOOT IMG TOO IF THIS DIDNT WORKED
DO IT AS FOLLOWS
Requirements:
-- BusyBox (cpio, gunzip and gzip is mandatory)
-- /System Write Permissions (Does not need to be a modified kernel)
-- Terminal Emulator
-- ES File Explorer (or similar)
-- Hex Editor (or use of DD)
-- Open up your android terminal emulator.
-- Now go ahead and pull your boot.img from your device (or use another one if you wish)
-- Open up your boot.img with the Hex Editor and look for: ANDROID!. Remove everything before it so that the ANDROID! header is the first to be read then save it over top of the boot.img. NOTE: This is only required if you are using a stock boot.img.
OR USE THIS IF U DIDNT UNDERSTOOD THIS
Hello Everyone, I’ll show you how to Unpack and Repack your Phone’s Boot.img & Tweak Karnel. Lets start.
Make a new folder named “boot edit” in cache/
image
Pull your boot.img in this folder
image
Now open ApkTool. Long press on “cache“, click on Get Access Permission.
image
Open cache folder and do same with boot edit. Give ApkTool access permission
image
Open boot edit, click on boot.img select Expack(MT65xx), press ok
image
It will unpack your boot.img.
image
Now open file manager & go to cache/boot edit/. You wil find your unpacked boot.
image
Now edit/modify the files or tweak karnel.
Again open ApkTool. Goto cache/boot edit click on ramdisk select repack-mt65xx.
image
It will repack your boot.
image
You will find an img file named new.img
image
This file is your Tweaked/edited/custom boot.img!!
Flash it via Recovery or Flashify & Enjoy..
FOR DETAILED AND STEP WISE GUIDE WITH SCREEN SHOTS SEE HERE
Mod Edit: link removed
XDA:DevDB Information
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE, ROM for all devices (see above for details)
Contributors
manhar2108, manhar2108, 2108kick
Source Code: Mod Edit: link removed
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: all
Version Information
Status: Stable
Created 2015-08-16
Last Updated 2015-08-16
HIT THANKS IF I HELPED U

Good guide..
Especially for noobs....

Darshan601 said:
Good guide..
Especially for noobs....
Click to expand...
Click to collapse
i too am a noob so i tried and made this guide

how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel

manhar2108 said:
i too am a noob so i tried and made this guide
Click to expand...
Click to collapse
Yeah....Even I am a noob

gunzgunz said:
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
Click to expand...
Click to collapse
just replace all these files and use stock kernal to port them
good luck

Sir i tried your guide in porting rom. Mt6582 tp mt6582 chipset roms.. But after replacing those files you mentioned and when i flashed it to my phone, it was tuck in boot screen and keep on restarting. How am I going to fix this?

Thread closed. Pay per click links are not allowed on XDA.
Darth
Forum Moderator

[Guide] Cyanogenmod 13 Porting for Mediatek MT6592 Devices

Guide to port Fire855's Cyanogenmod 13 to Mediatek Devices
Here I am posting guide how to port Fire855's Cyanogenmod 13 to Mediatek devices based on MT6592 SoC.
@fire855 Cyanogenmod 13 thread --> http://forum.xda-developers.com/android/development/rom-cyanogenmod-13-kingzone-k1-turbo-t3360336
Required Tools
Java Development Kit
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
Dat File Extractor
https://goo.gl/NxNe97
Cygwin
https://goo.gl/uMvH7C
Android Kitchen
https://goo.gl/rMH3kX
Meta-Inf Folder
https://goo.gl/y2WZZI
Notepad++
https://notepad-plus-plus.org/download/
Extracting system.new.dat file from Fire855 build
- Use extractor
- First Extract fire855 build zip using Winrar or 7z software.
- Put following files in "place_for_supported_files_here" folder
- file_contexts
- system.new.dat
- system.patch.dat
- system.transfer.list
- Run Extraktor_En.cmd
- Type 1 and press enter
- Your files will be extracted in "extract_file_here" folder
- Now copy these files from "system.dat" in "system" folder of Fire855 build
- Delete ".jounal" file from "/system" folder
Before Porting
- Delete Meta-Inf folder from Fire855 build
- Delete "system.new.dat", "system.patch.dat", "system.transfer.list
- Replace it with the Meta-inf folder given above
- You will have these folder and files now
- Install
- Meta-inf
- System
- boot.img
- file_contexts
- Now compress these above files and folder in one standard zip format.
Setting up Android Kitchen and Extracting Boot.img
1. Extract the Cygwin. In this folder you will find another folder named cygwin_packages and a file named setup. Copy these to C :\cygwin (create a folder named cygwin if it doesn't exist)
2. Open the cygwin folder in C:
3. Now in cygwin folder right click on the setup.exe and Run as Administrator
4. Click Next and then select Install from Local Directory
5. Select the path to the cygwin folder in C: then click Next
6. Select the path to the cygwin_packages folder (C:\cygwin\cygwin_packages) then click Next
7. Click Next. A message will appear click OK
8. Single click in the area between the Red box
9. Click Next. A message will appear, click Next. After this, installation will take place. After the installation process is complete check / tick the Create icon on Desktop and click on Finish. After this Right click on the Cygwin desktop icon and Run as Administrator. Some processes will take place after the completion of the process, close it
10. Now open C Drive. In the drive you will find a folder named Cygwin, Open it
11. Now open the home folder. In this folder you will find another folder having your Username, open it
12. Don't delete any file. Make a new folder named Kitchen
13. Open the folder named Kitchen. Now extract the file named dsixda Android Kitchen that you copied on your computer's desktop, then open the extracted folder of dsixda Android Kitchen
14. Copy all the files that are in the extracted folder of dsixda Android Kitchen and paste them in the Kitchen folder that you made
15. Now do Right click on the Cygwin desktop icon and Run as Administrator
16. Cygwin window will open. Now type "cd kitchen" (without "") then press Enter
17. Now type "./menu" then press Enter
18. After this Android Kitchen will open
You're good to go!
(You can use pictorial guide given on (https://forum.hovatek.com/thread-647.html)
Files needs to be ported
In Boot.img
- zimage (simply your device kernel)
- uevented.rc (if only device get bootloops)
Lib files need to replace from your Stock ROM
From "/system/lib/hw" folder
- hwcomposer.mt6592.so
- sensors.default.so (first rename this file to sensors.mt6592.so and then copy it same location in Fire855 build)
From "system/lib" folder
- libMali.so
- libaudio.primary.defaults.so
- libcameracustom.so
- libfeatureio.so
- libcamdrv.so
- libcamalgo.so
- libdpframework.so
- libcamparamsmgr.so
From "system/bin" folder
- gsm0710muxd
- gsm0710muxdmd2
- rild
From "/system/etc" folder
- Bluetooth folder
- Wifi Folder
- Firmware Folder
Making changes in boot.img only for devices having Emulated storage
Note: (No need of change for Non-emulated storage devices)
Edit fstab file in ramdisk folder after extracting boot.img in Android Kitchen
Refer this post by @Typhus_ --> http://forum.xda-developers.com/showpost.php?p=66440098&postcount=228
Note : Edit system and data mount points according to your device in updater-script using Notepad++.

Unpack/Repack Boot.img using Android Kitchen
1) First you need to set up working folder.
2) Place the zip you have created from above instructions in Original_Update folder.
3) Type 1 and press enter.
4) Select zip.
5) No need to rename working folder.
6) Also when it asks to do changes in updater script, Type 2 and press Enter for "Do nothing" and keep updater script as it is.
7) Now working folder is set up.
8) Go to advanced settings. Type 0 and press Enter.
9) Then type 12 and press enter.
10) Then type "w" (without "") and press enter.
11) A folder will be creatred name Boot-Extracted.
12) Now type "a" (without "") and press enter.
13) A messege will appear and a new folder will create by name Boot-img(Date)(time)
14) Place your stock boot.img in it and then come back to cmd window and press enter.
15) Now replace necessary files from stock boot to boot-extracted (zimage, uevented.rc etc)
16) Make changes in fstab file and other related files (for devices having emulated storage)
17) After making all changes in android kitchen cmd window type "b" and press enter. This will compile boot.img and repack it and get saved in working folder.

You can use to MTKbootimg Tool to Unpack and Repack boot.img
Link --> https://goo.gl/6NJJVx

I think carliv image tool is much better to exctract boot and recovery.img. much better than kitchen

vickdu31 said:
I think carliv image tool is much better to exctract boot and recovery.img. much better than kitchen
Click to expand...
Click to collapse
not really. but that's just a subjective opinion, isnt it? its a lil bit harder but it worth

vickdu31 said:
I think carliv image tool is much better to exctract boot and recovery.img. much better than kitchen
Click to expand...
Click to collapse
Cata Versi said:
not really. but that's just a subjective opinion, isnt it? its a lil bit harder but it worth
Click to expand...
Click to collapse
bravonova said:
You can use to MTKbootimg Tool to Unpack and Repack boot.img
Link --> https://goo.gl/cHhCsZ
Click to expand...
Click to collapse
It depends on which tool we get easier to use. It can be vary person by person. I am using Android Kitchen for very long time and get used to it now.

I have only a bug after porting procedure: in video Facebook app there is a green vertical bar...
How can I solve?
Inviato dal mio Elephone P8000 utilizzando Tapatalk

stefano91av said:
I have only a bug after porting procedure: in video Facebook app there is a green vertical bar...
How can I solve?
Inviato dal mio Elephone P8000 utilizzando Tapatalk
Click to expand...
Click to collapse
Replace "gralloc.default.so" and "gralloc.mt6592.so" from "/system/lib/hw" folder

Google Maps Compass & video playback!
How do I fix compass on Google maps? Its arrowhead is stuck on one position and never rotates. Compass/magnetic sensor works on all other apps except for Google maps.
Also
I have issue with video playback. I cannot stream videos from certain apps such as SonyLiv. However hotstar works fine. Also I have green YouTube videos problem on only certain few videos(with certian quality say 360p and/or live videos).

bravonova said:
It depends on which tool we get easier to use. It can be vary person by person. I am using Android Kitchen for very long time and get used to it now.
Click to expand...
Click to collapse
I mean this one : http://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
This is just way faster and easier ! And available on linux and windows

bravonova said:
Replace "gralloc.default.so" and "gralloc.mt6592.so" from "/system/lib/hw" folder
Click to expand...
Click to collapse
Thanks for the advice. I just tried it always turns out that problem .
Look at the picture ...

ivanmaria said:
How do I fix compass on Google maps? Its arrowhead is stuck on one position and never rotates. Compass/magnetic sensor works on all other apps except for Google maps.
Also
I have issue with video playback. I cannot stream videos from certain apps such as SonyLiv. However hotstar works fine. Also I have green YouTube videos problem on only certain few videos(with certian quality say 360p and/or live videos).
Click to expand...
Click to collapse
Copy sensors.defaults.so from stock rom. Rename it to sensors.mt6592.so and place it in /system/lib/hw folder.
Also add compass/magnetometer permission xml file from /system/etc/permissions to ported rom.
There is streaming issue in some apps.
Use youtube app given in second post of @fire855 CM 13 thread.

stefano91av said:
Thanks for the advice. I just tried it always turns out that problem .
Look at the picture ... /QUOTE]
Try this patch by @jpower73 it worked for me. I kept hwcomposer from stock.
Click to expand...
Click to collapse

ivanmaria said:
stefano91av said:
Thanks for the advice. I just tried it always turns out that problem .
Look at the picture ... /QUOTE]
Try this patch by @jpower73 it worked for me. I kept hwcomposer from stock.
Click to expand...
Click to collapse
Use these particular files to solve green line in FB videos. Copy and paste (replace old) in "/system/lib/hw" folder
Credits : @jpower73
Click to expand...
Click to collapse

bravonova said:
ivanmaria said:
Use these particular files to solve green line in FB videos. Copy and paste (replace old) in "/system/lib/hw" folder
Credits : @jpower73
Click to expand...
Click to collapse
Thanks so much. fantastic! :laugh::good:
Finally facebook operating at 100 % .
I noticed another problem ( see picture) : during charging the animation is wrong ... how can I solve?
Click to expand...
Click to collapse

stefano91av said:
bravonova said:
Thanks so much. fantastic! :laugh::good:
Finally facebook operating at 100 % .
I noticed another problem ( see picture) : during charging the animation is wrong ... how can I solve?
Click to expand...
Click to collapse
You need to change these files from stock rom.
From /system/lib folder
1) libipod.so
2) libshowlogo.so
From /system/bin folder
1) boot_logo_updater
2) ipod
3) logwrapper
Click to expand...
Click to collapse

bravonova said:
Copy sensors.defaults.so from stock rom. Rename it to sensors.mt6592.so and place it in /system/lib/hw folder.
Also add compass/magnetometer permission xml file from /system/etc/permissions to ported rom.
There is streaming issue in some apps.
Use youtube app given in second post of @fire855 CM 13 thread.
Click to expand...
Click to collapse
Google Maps Compass doesn't work yet!?

bravonova said:
stefano91av said:
You need to change these files from stock rom.
From /system/lib folder
1) libipod.so
2) libshowlogo.so
From /system/bin folder
1) boot_logo_updater
2) ipod
3) logwrapper
Click to expand...
Click to collapse
I just tried it, everything solved. Thanks again
Now I still get all rom in dayly use, looking for any bugs.
Click to expand...
Click to collapse

Nice Work Bro ? ..

Thanks guys,
There is, also, another patch fixing potentially BT connection issues with mi wrist smart bands and another one fixing wifi direct issues (both of them tested on cm12.1 from the Greek forum)
Also, in case you face low sound issues, you may try my gionee elife sound patch.
http://www.myphone.gr/forum/showthread.php?p=6549582#post6549582
Fully compatible with atmos, digital plus, audio fx, etc

[GUIDE] How to Change Boot Logo (Splash Screen) of Razer Phone (cheryl)

Note:
This is not bootanimation, this is the splash screen (the boot logo which is displayed when device is switched ON)
This is for Razer Phone Only.. (codename: cheryl)
(For other devices, please send me your splash.img so that I can create a tool for you too..)
Requirements:
1. Rooted Razer Phone (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: Razer_Phone_Cheryl_Splash_Maker.zip
2. Make sure you have a picture with resolution 1440x2560px.
Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
3. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@game_guy who provided the stock splash.img of Razer Phone (cheryl)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..

You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.

RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Splash screen is different from boot animation. The one which appears before boot animation

Oops sorry, brain fart.
I guess I wasn't paying attention all that well.

@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?

linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed

eoghan2t7 said:
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed
Click to expand...
Click to collapse
Nope, the splash screen is just a BMP picture (in RGB24 format) with an empty 16kB header before the picture.
You could see that in the batch file's code.
linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
The warning message actually is from the bootloader itself.
Most probably, it will be present in the 'aboot' partition, but it's not as easy as changing splash screen.
The same issue was also present in Nextbit Robin. (a company acquired by Razer)
Because, the bootloader is just a raw file when dumped, which needs to be checked using hex editor or whatever tool to see if it has an image and find its offset and patch the image accordingly, or even, it might be possible to find the location of where the amount of warning time is present and make it 0.
But the problem is, since it's a raw dump and the bootloader is the code that brings up the kernel, it's highly possible that if we do something wrong, the device might be hard-bricked (even fastboot mode is from bootloader). Also, today's bootloaders might even be signed, so patching the bootloader for warning picture might not necessarily work since the device won't be able to verify the integrity of bootloader partition after its contents change.
So, if there's a tool with which you can flash and recover a hard-bricked phone, and if you're willing to test the modified bootloaders that I create, send me the bootloader partition dump. I'll take a look at it

@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)

linuxct said:
@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)
Click to expand...
Click to collapse
Lol I remember doing stuff with my Droid RAZR and Bionic for dhacker back in the day. It was worth it in the end, but took time for the recover from hard brick processes to come about.

RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Hi, can you please upload and share the default bootanimation here? I have deleted mine and would like to get it back.

[GUIDE] How to Change Boot Logo (Splash Screen) of Redmi Note 5 Pro (whyred)

Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..

GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
Click to expand...
Click to collapse
You are awesome , genius , superb , intelligent , brilliant , excellent , superb:good::good::good::good:
thank You Sooooooo MUCH

How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...

kqixs said:
How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...
Click to expand...
Click to collapse
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.

GokulNC said:
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.
Click to expand...
Click to collapse
The reason wasbunderstood, but i couldn't find the solution...i didn't know much about programming (to edit .bat file) i tried to search it a bit but couldn't succeed so i just used another image for boot logo....
Thnx for you help though....?

Please make a flashable Google pixel logo and boot animation for Redmi note 5 pro

Google G icon splash screen for whyred.
splash.img
raw files

Wow. Thanks its so easy.

This is the flashable zip of my splash screen.
If anyone find it useful.

Thanks for making this guide and sharing this tool, I love it!
I have an issue though, I tried making some 1080x2160/18:9 splash screens but they got vertically squished down into 1080x1920/16:9 , is this meant to happen?
As a workaround I changed my images to 1080x1920/16:9 and made the background pitch black so there wouldn't be black bars at top and bottom.
I'm a loser who loves watching Twitch livestreams, so in lack of creativity I just made these my Splash screens

KuldeepShivankar said:
This is the flashable zip of my splash screen.
If anyone find it useful.
Click to expand...
Click to collapse
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing

sharmasrb said:
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing
Click to expand...
Click to collapse
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.

Can I request this picture for splash image, as my computer is broken..
Thank you

This is a test splash screen...

KuldeepShivankar said:
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.
Click to expand...
Click to collapse
Okay, i want it

@GokulNC I tried to edit the script and make the resolution 1080*2160 because I wanted a white splash without the black bars, and then resized all 3 images to the same resolution, and then made a splash and flashed it. Worked but instead of these images it shows a complete black screen.
You know why?

Rishi2906 said:
@GokulNC I tried to edit the script and make the resolution 1080*2160 [...] Instead of these images it shows a complete black screen.
Click to expand...
Click to collapse
The routine that displays the images is very simple, and just looks for them at certain offsets within the splash partition. When you change the dimensions, file sizes change as well, and the following images are no longer at the offsets they're expected to be, so they can't be found, and nothing is displayed.
If the BMP images are exactly 6,220,854 bytes each, they can just be concatenated together; smaller ones could possibly work with some padding in between them but if you want a larger resolution, the resulting bitmaps would be too large in size.
One way to make the files small enough to fit within their spaces so that the following ones could still start at the right offsets would be to reduce color depth. (Another way would be to find the code that displays the images and edit the offsets it looks for but this isn't trivial). But in the end, the routine might still not be designed to display anything else than 24-bit, 1080x1920 px anyway.

Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip via twrp

irfan.shikarpuri said:
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Is it flash able zip via twrp
Click to expand...
Click to collapse
No.

What is the maximum logo size that I have to make? thanks before
What is the maximum logo size that I have to make? thanks before