[DEV] sdat2img 1.1 - img2sdat 1.7 ◦ Unpack/re-pack android DAT files - Android Software/Hacking General [Developers Only]

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

Related

[GUIDE][MOD][KERNEL] Change Bootsplash Image

DISCLAIMER NOTE: I AND XDA IS NOT TO BE HELD RESPONSIBLE FOR ANY DAMAGES THAT YOUR PHONE MIGHT INCUR DURING THIS PROCESS, I HAVE TESTED IT IN MY BEST KNOWLEDGE TO WORK FOR OUR DEVICE BUT JUST TO BE SURE, PLEASE PERFORM ALL NECESSARY BACKUPS FOR THE PHONE TO PREVENT ANY DATA LOSS, IF YOU HAVE THE NEED TO DISAGREE AND/OR FAIL TO COMPLY JUST DON'T FLASH IT AND GET ON WITH YOUR LIVES
Click to expand...
Click to collapse
This is for editing the bootsplash: the image wich is displayed while kernel is loaded.
For example in Samsung devices is the image which comes between Samsung Logo and bootanimation.
This change is made in kernel, so if you want to include this in your ROM you must include the edited kernel with it.
Pre-requisites:
1.-Android Image Kitchen (DOWNOLAD)(THREAD)
2.-edit image on windows Tool modified by me (DOWNLOAD)(thanks to championswimmer for this)
3.-I recommend Photoshop or similar software for image editing (GIMP or Paint are ok)
4.-I recommend to enable the file extension visualization in Windows.
Let's start!
1.-Take the boot.img of the kernel that you want to use
2.-Extract Android Image Kitchen
3.-Extract edit-image-windows.zip
4.-Put boot.img in Android Image Kitchen folder
5.-Now go to cmd and navigate to Android Image Kitchen folder
6.-Type:
Code:
unpackimg boot.img
7.-Now open windows explorer and navigate to *\Android Image Kitchen\ramdisk, look for a *.rle file and copy it. Rebember the name of the .rle file, you'll need it later.
8.-Paste the rle on edit-image-windows folder
9.- Open cmd, navigate to edit-image-windows folder and type:
Code:
rle2png nameoftthrle.rle 000x000
Where I wrote nameoftthrle.rle write the name of your rle and where I wrote 000x000 write your phone's resolution.
Example: for me, I have a GT-S6500D wich has a 320x480 resolution and the name of my rle is GT-S6500.rle so I must write:
Code:
rle2png GT-S6500.rle 320x480
10.- Open the .png file which is now on edit-image-windows folder with your image edition sowtware (I recommend Photoshop) and made the changes you want. In my phone, is only displayed on black and white, so it's useless to enable color mode.
11.-When you finished editing go again to cmd and write:
Code:
png2rle nameofttherle.png
Where I wrote nameoftthrle.rle write the name of your png.
Example:
Code:
png2rle GT-S6500.rle.png
12.-Now you'll have a file called nameofyourrle.rle.png.rle witch is the modified rle
13.-Go to *\Android Image Kitchen\ramdisk and replace the rle with the new one witch is modified.
14.-Now go to cmd, navigate to Android Image Kitchen folder, and type:
Code:
repackimg
15.-Done! rename the image-new.img to boot.img and flash it!
Click to expand...
Click to collapse
PLEASE give me a thanks if you like my work
reserved
last one reserved
manu19thebest said:
This is for editing the bootsplash: the image wich is displayed while kernel is loaded.
For example in Samsung devices is the image which comes between Samsung Logo and bootanimation.
This change is made in kernel, so if you want to include this in your ROM you must include the edited kernel with it.
Pre-requisites:
1.-Android Image Kitchen (DOWNOLAD)(THREAD)
2.-edit image on windows Tool modified by me (DOWNLOAD)(thanks to championswimmer for this)
3.-I recommend Photoshop or similar software for image editing (GIMP or Paint are ok)
4.-I recommend to enable the file extension visualization in Windows.
Let's start!
PLEASE give me a thanks if you like my work
Click to expand...
Click to collapse
Nice work, wonder if it work on window64
You can now edit/split a ramdisk on your phone now. Apktool on android has boot.img/ramdisk editing functionality. And a whole bunch of others....
Download apktool on android from here:
http://code.google.com/p/apktool/downloads/list
Make sure you download the correct zip file for your phone... And the updated apk. Follow the installation guide the developer has posted.
Before you split the boot.img make sure you're running apktool on an ext4 filesystem. Move the boot.img to /cache/subfolder our something like that.... then you shouldn't have a problem.
EDIT:
If your ROM has SElinux integrated, make sure it's set to permissive before splitting the image file or you'll get sh-applet error.
Go into terminal emulator and type:
su
setenforce 0
Happy editing
_kohjun_ said:
Nice work, wonder if it work on window64
Click to expand...
Click to collapse
My Windows is 64 so yes
Enviado desde mi GT-S6500D usando Tapatalk 2
DexedrineXR said:
You can now edit/split a ramdisk on your phone now. Apktool on android has boot.img/ramdisk editing functionality. And a whole bunch of others....
Download apktool on android from here:
http://code.google.com/p/apktool/downloads/list
Make sure you download the correct zip file for your phone... And the updated apk. Follow the installation guide the developer has posted.
Before you split the boot.img make sure you're running apktool on an ext4 filesystem. Move the boot.img to /cache/subfolder our something like that.... then you shouldn't have a problem.
EDIT:
If your ROM has SElinux integrated, make sure it's set to permissive before splitting the image file or you'll get sh-applet error.
Go into terminal emulator and type:
su
setenforce 0
Happy editing
Click to expand...
Click to collapse
I prefer using pc, mobile isn't good for image editing and boot.img is kernel, so just a little pediting will be a brick for sure.
Enviado desde mi GT-S6500D usando Tapatalk 2
manudroid19 said:
My Windows is 64 so yes
Enviado desde mi GT-S6500D usando Tapatalk 2
Click to expand...
Click to collapse
and on x32 sys? it didnt worked for me. bootloop. anyway doing for the 2nd time now
Edit- it did worked. many thanks
So how do you put a modified kernel in a rom zip? I built a rom from source, and want to change the uninstalled kernel to my own. P.S I have a tool that does this and creates a flashable zip for you, if anyone wants it.
Great work!!!
Tried it on my SONY... - perfect! :good:
Thank you very much
Can you use an .elf or .sin file instead of .img?
I'm on cm12.1 and there aren't any rle files
im also on cm12.1 an no rle file
By using these tools Can I able to change my boot splash ( ASUS Boot logo) in my asus zenfone 5 ? If not, then please guide me so that i can change my ASUS BOOT LOGO with custom made boot logo.
Thanks in advance?
I can't help myself but this work looks very similar to @DooMLoRD work - even the script is almost the same. Only resolution variable added....
https://forum.xda-developers.com/showthread.php?t=1140406

[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

For (WINDOWS) Tool Android Unpack\Repack system.new.dat Nougat 7.х.х

A tool to Repack the firmware image system.new.dat Nougat 7.x.x
the author of the tool by Karan Sangaj thank you :good: on XDA haven't found the original post
The usage is very simple, I hope many will be useful.
thanks for the help ajsmsg78
1) install Python 2.7.13
2) original post File contexts.bin converter thank you
another File context tools thank you
video instruction
https://www.youtube.com/watch?v=OsHWPdIgGjY
https://plus.google.com/u/0/collection/EiQ1NE
sory for my English
cannot convert my_new_system.img.
how to convert it exactly?
Any solution??
Traceback (most recent call last):
File "C:\Users\pc\Desktop\Android Unpack Repack Nougat\tools\img2sdat.py", line 10, in <module>
import common, blockimgdiff, sparse_img
File "C:\Users\pc\Desktop\Android Unpack Repack Nougat\tools\common.py", line 112
print " running: ", " ".join(args)
^
Esakren17 said:
Any solution??
Traceback (most recent call last):
File "C:\Users\pc\Desktop\Android Unpack Repack Nougat\tools\img2sdat.py", line 10, in <module>
import common, blockimgdiff, sparse_img
File "C:\Users\pc\Desktop\Android Unpack Repack Nougat\tools\common.py", line 112
print " running: ", " ".join(args)
^
Click to expand...
Click to collapse
I am getting the same error as this, what should I do to fix it?
Have installed python v2.7.13+3.6.1, latest java jdk and jre and .NET framework v4.7 and running windows 10, it had worked on the first try but started showing this error suddenly.
It works, but after install ROM the battery discharges very quickly and heats up... I think that incorrectly exposed file permissions, because if i flash "system" folder with setting simlinks and set_metadata in updater-script ROM works fine and battery is ok.
ROM work only with system.img, system.new.dat dont flash, error 7 in TWRP...
best tools ，thanks！！
raghuM said:
I am getting the same error as this, what should I do to fix it?
Have installed python v2.7.13+3.6.1, latest java jdk and jre and .NET framework v4.7 and running windows 10, it had worked for the first time but started showing this error suddenly
Click to expand...
Click to collapse
same here
Anyway to repack oreo
Got a problem with this tool.....
it works perfectly to extracting system.new.dat and unpack system.img I modify and remove some files in the system folder (remove some apks and fonts, add some hosts....) so the size of the system folder change and when I type the 04 option got this error message.....
0 [main] make_ext4fs 7236 cygwin_exception:pen_stackdumpfile: Dumping stack trace to make_ext4fs.exe.stackdump
Impossible de trouver C:\Users\RAYMAN95\Desktop\Android Unpack Repack Nougat\temp_size.txt
How is it possible to made some modifications and repack it to system.new.dat????
thank's for the help
This tool is very nice.... But please help me guys... On the last step I'm failed to repack system.img to new.system.dat... SYNTAX ERROR... how to fix it?
By the way it is very great tool... Thx to Dev ^^
Can't Unpack system.img
Ok Bro .. That's awesome Tutorial.
I have the system.img of Note 8 AP file .. I try to unpack it directly but it Ext4Extractor.exe is stopping working.
I don't have system.new.dat file so I'm trying to unpack system.img directly but it doesn't work.
As these images show the error:
https://imgur.com/a/jlZvb
Thank you very much for your tools very easy to use Thank you again
iMenesi said:
Ok Bro .. That's awesome Tutorial.
I have the system.img of Note 8 AP file .. I try to unpack it directly but it Ext4Extractor.exe is stopping working.
I don't have system.new.dat file so I'm trying to unpack system.img directly but it doesn't work.
As these images show the error:
https://imgur.com/a/jlZvb
Click to expand...
Click to collapse
The link is not working.
You need to have a custom ROM, and in it system.transfer.list and system.new.dat.
Use this method:
[DEV] sdat2img 1.0 - img2sdat 1.2 ◦ Unpack/re-pack android DAT files
For a long time I use and have not found Android ROM 5.1.1 - 8.0.0, which can not be unpacked using sdat2img.py.
Thank you authors @xpirt , @luxi78 , @howellzhu !
You dont need a custom rom or the system.transfer.list, or system.new.dat. This unpacks images just fine. It will not unpack factory images tho. I got it to work just fine unpacking nexus 6 system.img by placing the image in the output_converted_dat_to_ext4 folder then telling the bat file what the size is and unpacking it. Do the same thing for oreo and the ext4 exe crashes.
ze7zez said:
The link is not working.
You need to have a custom ROM, and in it system.transfer.list and system.new.dat.
Use this method:
[DEV] sdat2img 1.0 - img2sdat 1.2 ◦ Unpack/re-pack android DAT files
For a long time I use and have not found Android ROM 5.1.1 - 8.0.0, which can not be unpacked using sdat2img.py.
Thank you authors @xpirt , @luxi78 , @howellzhu !
Click to expand...
Click to collapse
iMenesi said:
Ok Bro .. That's awesome Tutorial.
I have the system.img of Note 8 AP file .. I try to unpack it directly but it Ext4Extractor.exe is stopping working.
I don't have system.new.dat file so I'm trying to unpack system.img directly but it doesn't work.
As these images show the error:
https://imgur.com/a/jlZvb
Click to expand...
Click to collapse
greeshan said:
It works, but after install ROM the battery discharges very quickly and heats up... I think that incorrectly exposed file permissions, because if i flash "system" folder with setting simlinks and set_metadata in updater-script ROM works fine and battery is ok.
ROM work only with system.img, system.new.dat dont flash, error 7 in TWRP...
Click to expand...
Click to collapse
flash "system" folder with setting simlinks and set_metadata in updater-script ROM
Click to expand...
Click to collapse
How did you fix the problem?
How did you do that?
master.robot said:
How did you fix the problem?
How did you do that?
Click to expand...
Click to collapse
i use commands set_metdata(xxxx); after block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
Is this tool work with oreo roms ?
wgmmmx said:
Is this tool work with oreo roms ?
Click to expand...
Click to collapse
No i think
link77kz said:
A tool to Repack the firmware image system.new.dat Nougat 7.x.x
the author of the tool by Karan Sangaj thank you :good: on XDA haven't found the original post
The usage is very simple, I hope many will be useful.
thanks for the help ajsmsg78
1) install Python 2.7.13
2) original post File contexts.bin converter thank you
another File context tools thank you
video instruction
https://www.youtube.com/watch?v=OsHWPdIgGjY
https://plus.google.com/u/0/collection/EiQ1NE
sory for my English
Click to expand...
Click to collapse
rom isn't booting after editing system.new.dat. any help ?
For anyone having syntax errors converting systemsparse.img to system.new.dat just download the updated img2sdat files from the link below and extract all files ending in .py to the tools folder of this batch tool. There's also an updated sdat2img.py linked below which goes in the same tools folder. Overwrite all the old files when prompted.
Edit: I've attached a zip that has the tools already updated. Maybe the OP can update the first post?
img2sdate update: https://github.com/xpirt/img2sdat
sdat2img update: https://github.com/xpirt/sdat2img

Oreo Contexts Converter

THIS TOOL IS FOR TESTING PURPOSE ONLY.
THIS MAY WORK ON SOME DEVICES OR MAY NOT WORK AT ALL.
IF THIS TOOL MAKES THE ROM UNBOOTABLE PLEASE COMMENT BELOW.
NO BUG FIXING not until i get an oreo supported phone for me to test.
TREBLE ROMS ARE NOT SUPPORTED!
FEATURES:
CAN DETECT OREO BOOT.IMG (YOU CANT MESS UP THIS TOOL. HAHA!!)
CAN DETECT WHETHER THERES A BOOT.IMG INSIDE THE MAIN FOLDER
CONVERTS BINARY INTO PLAIN CONTEXTS (MAIN FEATURE)
DECOMPRESS .BR IMAGES INTO .DAT (COOL RIGHT?)
USAGE:
GRAB A BEER AND RELAX
WHILE ON YOUR WINDOWS COMPUTER, UNPACK THE ARCHIVE AND GRAB THE OREO BOOT.IMG INTO oreo_contexts_tool FOLDER
RUN OFC.EXE AS ADMIN (NO NEED ADMIN RIGHTS FOR V2.0.0.1 AND V2.0.0.2)
FOLLOW INSTRUCTIONS AFTERWARDS..
IF YOU NEED THE CONTEXTS CONVERTER FOR NOUGAT THEN USE MY TOOL HERE TO CONVERT PLAIN CONTEXTS INTO BINARY AND VICE VERSA.
tested only on x32bit windows 7 ultimate
ofc v2.0.0.1
ofc v2.0.0.2
!!VERY IMPORTANT TO READ NOTES!!
Code:
v2.0.0.1
can decompress .br image into .dat
can compress .dat image into .br
NO NEED to run the application with admin rights, just run normally.
I added x64 bit application but havent tested it yet on 64bit machine
(my laptop cant run x64 os :p) if it wont work pls use the other application.
v2.0.0.2
file contexts output is current directory
added reset tool if experiencing errors
added clean current directory
less popup of cmd (only when unpacking boot.img)
x64bit tool is not included yet.
note:
choosing "clean current directory" option will delete EVERYTHING
inside the current directory except for the tool. so i advise to run this tool
inside a folder/directory to avoid deleting all your important files on your pc.
e.g you run ofc.exe in drive C:\ (C:\OFC.EXE) ...then you chose
"clean current directory" option, this will delete EVERYTHING in
C: drive so BE CAREFUL!! I wont be responsible if this happens..
if your anti virus detects malware, trojan, etc just ignore.. my script is very simple and basic that any highschool student can laugh at it. :silly: :laugh:
AIK LINK
CREDITS
@osm0sis <-- also thank him
@munjeni <-- and him
DONT JUST SAY THANKS!! HIT THE BUTTON BELOW..
last update:
06/08/18
Thank You.oreo unpacked.
tool
Zipper31 said:
Thank You.oreo unpacked.
Click to expand...
Click to collapse
can you give oreo extract tool
new test update..
there is a trojan in the executable??
Friend, link is broken, please, upload again.
JamFlux said:
Friend, link is broken, please, upload again.
Click to expand...
Click to collapse
Yes! Update link please
greeshan said:
Yes! Update link please
Click to expand...
Click to collapse
I MANAGE MY OWN TOOL FOR THIS:
https://forum.xda-developers.com/ch...l-extract-repack-dat-img-android-5-8-t3670763
JamFlux said:
I MANAGE MY OWN TOOL FOR THIS:
https://forum.xda-developers.com/ch...l-extract-repack-dat-img-android-5-8-t3670763
Click to expand...
Click to collapse
Thanks, i'll try
link works on my slow internet..
reupload please?
0ther said:
reupload please?
Click to expand...
Click to collapse
link is working fine.. maybe use another browser?
Got 404, reupload please ?

Image 2 Image [ magisk module ] system, vendor image converter

Android system, vendor image converter tool
############## IMAGE 2 IMAGE ##############
Module Image Converter tools & setup v1.1
## MMT-EX .v 20.4 -Zackptg5
## Python .v 2.7.9 -Python.org
## Python .v 3.4.2 -Python.org
## Bash .v 4.3.4.2 -Bash GNU
## BusyBox .v 1.31.1 -topjohnwu
## Brotli .v 1.0.7-2 -brotli.org
Info:
For unpacking, repacking an creating system.new.dat.br, system.new.dat, system.img an vendor.new.dat.br vendor.new.dat vendor.img on android devices.
# STEPS:
Use a good android terminal emulator app , like Nethunter terminal app. (highly Recommended)
Download :
https://store.nethunter.com/repo/com.offsec.nhterm_2020030100.apk
-Grant your terminal app root: in Nethunter you would choose, android su
** You can also type " sudo " then press enter for root access **
Type without quotes " bash " then press enter
Type without quotes " ziona " then press enter
First time setup !
# INTERNAL STORAGE USAGE:
.You will be asked about which storage your using were the files to convert are located
if using internal storage then leave terminal an locate the folder named internal in that storage
place system.new.dat or dat.br an system.transfer.list here !!
use this location for your dat, dat.br an system|vendor image files
# EXTERNAL STORAGE USAGE:
.You will be asked about which storage your using were the files to convert are located
if using external storage then leave terminal an locate the folder named external in that storage
place system.new.dat or dat.br an system.transfer.list here !!
use this location for your dat, dat.br an system|vendor image files
Once your files are in one of the storage locations ,
Now go back to terminal app menu an press Enter .
# FIRST MENU:
Choose which storage you placed the files to convert
# SECOND MENU AND THIRD MENU:
Choose which convert action to do unpacking or repacking of the image file
Options:
1. unpack system.new.dat.br -------(to) system.new.dat
2. repack system.new.dat.br ------ (from) system.new.dat
3. unpack vendor.new.dat.br -------(to) vendor.new.dat
4. repack vendor.new.dat.br -------(from) vendor.new.dat
5. unpack system.new.dat ----------(to) {raw} system.img
6. repack system.new.dat ----------(from) {sparse} system.img
7. unpack vendor.new.dat ---------(to) {raw} vendor.img
8. repack vendor.new.dat ---------(from) {sparse} vendor.img
9. unpack sparse system.img -----(to) {raw} system.img
10. repack sparse system.img -----(from) {raw} system.img
11. unpack sparse vendor.img -----(to) {raw} system.img
12. repack sparse vendor.img -----(from) {raw} vendor.img
13. mount system.img
14. mount vendor.img
15. umount system.img
16. umount vendor.img
17. makefs raw system.img --------(from) {raw} system.img mounted
18. makefs raw vendor.img --------(from) {raw} vendor.img mounted
Mounting of raw system.img images made after unpacking are done automatically
Mounting of raw vendor.img images made after unpacking are done automatically
.You can also Manually mount system.img an umount system.img in internal|external
.You can also Manually mount vendor.img an umount vendor.img in internal|external
.You can type in terminal m1 to mount a system|vendor image in internal|external
.You can type in terminal u1 to unmount a system|vendor image in internal|external
Usage for storage internal|external folder convertions:
-Copy an Place your images files here for everything -- Unpacking & Repacking Also Mounting Images
system.transfer.list & system.new.dat -- needed for converting
system.transfer.list & system.new.dat.br -- needed for converting
vendor.transfer.list & vendor.new.dat -- optional for converting
file_contexts.bin & system.img -- optional to create a modified new image
.When image is converted from .dat to system.img (raw) it will be mounted
within the same external/internal storage folder look inside /system1 or 2 & /vendor1 or 2
.You can do whatever modifications there before making new image or just repacking after umount.
# NOTE CONVERTIONS:
Examples for image processing:
From; {raw} system.img > {sparse} system.img > system.new.dat & optional finally > system.new.dat.br
From; system.new.dat.br > system.new.dat > {raw} system.img
From; {sparse} system.img > {raw} system.img
~ You can repack raw system.img to sparse system.img
used this to flash images in twrp recovery to system or vendor partitions.
Remember on sparse images:
~ To unpack a sparse image to raw system.img or vendor.img you can sparse unpack,
you can also covert it to system|vendor.new.dat then to raw system|vendor.img.
(You can call help in menu by typing 4 an then enter . At main screen first menu only)
All info will display if successful or errors occur .
General logs are found in folders internal|external/logs .
Android 6 to 11 images:
.Both system an vendor images tested. Works on custom roms Lineage, CM, RR, Mokee rom images an more .
Terminal support for:
busybox, dash, bash, python2 & python3 - Shell Commands that are standalone in terminal.
For best results:
•Have 4GB or more of free internal or external storage available on device
•Operating convertions in internal storage is 3xxx faster than using external storage (sdcards)
•ALWAYS have a backup of your original images before converting an using delete old image option when preserving device storage space.
•Remember normally yellow text in the terminal when converting anything is successful and red is a error happened.
•If a image won't automatically or manually mount its more than likely because it's a bad system|vendor image.
TroubleShooting:
--Error logs are made within system*.logs in external or internal logs folder to report.
--Scroll up to view full menu options they are over 18 to choose from in terminal menu1-2 options, internal|external storage.
--If using Nethunter Terminal app if display freezes or weird behavior occurs restart app or start a new window.
--Always have just system.transfer.list with system image files in folder for convertions.
--Always have just vendor.transfer.list with vendor image files in folder for convertions.
--Always remove system.transfer.list an system image files from folder before convertions if using vendor files.
--Always have file_context.bin when creating new images from a mounted system|vendor image
--Have a image that wont convert even with the necessary files present it can mean a bad image or just incompatible with this module.
--If Nethunter Terminal app enter key stops working press the three dots in upper right corner,
and tap Preferences, now tap Function keys, then untick the (tab) option and go back to first terminal window,
now on top of keyboard theirs special functions a new (enter) tab should be on the end right corner.
--Full support for use on arm devices only
# Credits: For Tools & ideas
Kali NetHunter
@andii_nr
@Zackptg5
@topjohnwu
Python.org
Brotli.org
Bash GNU
Creator:
@Ziona
Created:
13/10/2020
Disclaimer :
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this feature included
* in the product you find here before flashing it!
* YOU are choosing to make these modifications.
This should be safe to use when properly install.
Click to expand...
Click to collapse
For arm devices only !
Download backup link:
image2image_v1.1 -
https://www.androidfilehost.com/?fid=10763459528675564171
.
Reserved
@Ziona
Nice work!
If you're looking for some more up to date binaries like bash and brotli, you can grab them from here: https://github.com/Zackptg5/Cross-Compiled-Binaries-Android
Zackptg5 said:
@Ziona
Nice work!
If you're looking for some more up to date binaries like bash and brotli, you can grab them from here: https://github.com/Zackptg5/Cross-Compiled-Binaries-Androidy
Click to expand...
Click to collapse
Thanks
Cool no prob, will be sure to add what i can for next release. With credits to you again also.
file seems to be corrupt, tried downloading many times but it always stops at 4.5mb
dead0 said:
file seems to be corrupt, tried downloading many times but it always stops at 4.5mb
Click to expand...
Click to collapse
Thanks for pointing that out, xda server seems to be experiencing difficulties.
Theirs a new working link above.
Ziona said:
Thanks for pointing that out, xda server seems to be experiencing difficulties.
Theirs a new working link above.
Click to expand...
Click to collapse
thanks
been trying to unpack the vendor image from miui 12 for poco f2 global. unfortunately the furthest i get is the creation of vendor.img which i am unable to mount - seems to be an error on header magi which im not sure what it means
dead0 said:
thanks
been trying to unpack the vendor image from miui 12 for poco f2 global. unfortunately the furthest i get is the creation of vendor.img which i am unable to mount - seems to be an error on header magi which im not sure what it means
Click to expand...
Click to collapse
What is the default vendor image type before converting? .bin .img .dat or .dat.br . (sparse or raw format)
Ziona said:
What is the default vendor image type before converting? .bin .img .dat or .dat.br . (sparse or raw format)
Click to expand...
Click to collapse
its dat.br in raw format from here: http://airtel.bigota.d.miui.com/V12...IGlobal_V12.0.4.0.QJKMIXM_72b1da9230_10.0.zip
dead0 said:
its dat.br in raw format from here: http://airtel.bigota.d.miui.com/V12...IGlobal_V12.0.4.0.QJKMIXM_72b1da9230_10.0.zip
Click to expand...
Click to collapse
Generally you know it would go like this: vendor.img (raw) > vendor.img (sparse) > vendor.new.dat (data sparse format) > finally compressed again using brotli > vendor.new.dat.br (data sparse format) .
Things to consider
You get header errors also when unpacking images that are bad or when using the wrong decompression tool on it.
Is the .dat.br image for 32 or 64 bit device.
Using google drive, mega or android host create a link here to only the vendor.new.dat.br for me to try
Ziona said:
Generally you know it would go like this: vendor.img (raw) > vendor.img (sparse) > vendor.new.dat (data sparse format) > finally compressed again using brotli > vendor.new.dat.br (data sparse format) .
Things to consider
You get header errors also when unpacking images that are bad or when using the wrong decompression tool on it.
Is the .dat.br image for 32 or 64 bit device.
Using google drive, mega or android host create a link here to only the vendor.new.dat.br for me to try
Click to expand...
Click to collapse
i'll upload it after work. the dat.br is for 64bit. I can extract on the pc using CRB from xda chef central but cant compress it back again
dead0 said:
i'll upload it after work. the dat.br is for 64bit. I can extract on the pc using CRB from xda chef central but cant compress it back again
Click to expand...
Click to collapse
Ok send it then, btw did you try the options in the module on your device an followed the steps to unpack an repack dat.br.
Am not clear on if you did or not
Ziona said:
Ok send it then, btw did you try the options in the module on your device an followed the steps to unpack an repack dat.br.
Am not clear on if you did or not
Click to expand...
Click to collapse
i have tried the steps but only gone as far as creating the vendor.img, after that i get a mounting error
dead0 said:
i have tried the steps but only gone as far as creating the vendor.img, after that i get a mounting error
Click to expand...
Click to collapse
I'll have to check that vendor file, you have busybox installed in your system
Ziona said:
I'll have to check that vendor file, you have busybox installed in your system
Click to expand...
Click to collapse
yes busybox installed. heres the link for the vendor image: https://mega.nz/file/UdEHSCjB#XVgUjFMd2KEfoiaH53z_AyDIB_TGhYWRwyQYRap-2uI
dead0 said:
yes busybox installed. heres the link for the vendor image: https://mega.nz/file/UdEHSCjB#XVgUjFMd2KEfoiaH53z_AyDIB_TGhYWRwyQYRap-2uI
Click to expand...
Click to collapse
Ok
Is this the vendor.new.dat.br image unconverted? If so its really large for a compressed vendor image file
Ziona said:
Ok
Is this the vendor.new.dat.br image unconverted? If so its really large for a compressed vendor image file
Click to expand...
Click to collapse
yes. this is from stock
dead0 said:
yes. this is from stock
Click to expand...
Click to collapse
The vendor image is good .
Android 10
Redmi K30
Xiaomi
It unpacks fine.
It mounts fine.
It repacks fine.
So your sure it was mounted , prop files from the image !
Ziona said:
The vendor image is good .
Android 10
Redmi K30
Xiaomi
It unpacks fine.
It mounts fine.
It repacks fine.
So your sure it was mounted , prop files from the image !
Click to expand...
Click to collapse
Strange. I'll try it again 2moro but using stock ROM as base os. I was testing it with a custom ROM. Any chance u can upload the repacked image?
dead0 said:
Strange. I'll try it again 2moro but using stock ROM as base os. I was testing it with a custom ROM. Any chance u can upload the repacked image?
Click to expand...
Click to collapse
I'll upload it.
You may have to tell me step process your doing to unpack an repack so can point out anything wrong

Categories

Resources