Database Info

[Q] Zip Flashing Fail - Multirom TWRP

Hi Guys,
I've never had this problem before but I can't seem to get any zip files I create to flash through TWRP.
I've compressed them with STORE method in 7zip.
I've double checked everything I put in the update-script file.
and I've tried signing them
My directory tree for the zip is as follows:
Code:
-META-INF
CERT.RSA
CERT.SF
MANIFEST.MF
-com
-google
-android
update-binary
updater-script
-system
-priv-app
SystemUI.apk
My updater-script only has a few lines because I'm still trying to just get it successfully run but it is as follows:
Code:
ui_print("Testing if system can be mounted");
ifelse mount("yaffs2", "MTD", "system", "/system") == "system", ui_print("Mounted!"), ui_print("Mount Failed!");
with of course an extra empty line at the end.
This is a screenshot of my failed flash:
http://www.mediafire.com/convkey/bba3/r0eidwl8ito77uhfg.jpg
I noticed it says "updater-binary" rather than "update-binary" so I tried changing the name and signing the zip again.
After attempting to flash the unsigned and the signed zip this is the message I get:
http://www.mediafire.com/convkey/ed01/5oh5mqyt6lv8lwffg.jpg
No longer says updater-binary but still getting MD5 error and flash is failing everytime.
I was able to flash the Omni rom I even switched my signed SystemUI.apk with the one in the rom and flashed it fine.
I have downloaded update.zip(s) and flashed them fine. But whenever I edit the update-script my self it doesn't do anything .. I've even tried a simple
Code:
ui_print("message");
and it failed.
Not sure what I am doing wrong never had this problem when i was theming for my Lg Revolution way back when .
Also I'm using Notepad++ and eol conversion is set to unix.
Thanks to anyone with answers.

hackn101 said:
Hi Guys,
I've never had this problem before but I can't seem to get any zip files I create to flash through TWRP.
I've compressed them with STORE method in 7zip.
I've double checked everything I put in the update-script file.
and I've tried signing them
My directory tree for the zip is as follows:
Code:
-META-INF
CERT.RSA
CERT.SF
MANIFEST.MF
-com
-google
-android
update-binary
updater-script
-system
-priv-app
SystemUI.apk
My updater-script only has a few lines because I'm still trying to just get it successfully run but it is as follows:
Code:
ui_print("Testing if system can be mounted");
ifelse mount("yaffs2", "MTD", "system", "/system") == "system", ui_print("Mounted!"), ui_print("Mount Failed!");
with of course an extra empty line at the end.
This is a screenshot of my failed flash:
http://www.mediafire.com/convkey/bba3/r0eidwl8ito77uhfg.jpg
I noticed it says "updater-binary" rather than "update-binary" so I tried changing the name and signing the zip again.
After attempting to flash the unsigned and the signed zip this is the message I get:
http://www.mediafire.com/convkey/ed01/5oh5mqyt6lv8lwffg.jpg
No longer says updater-binary but still getting MD5 error and flash is failing everytime.
I was able to flash the Omni rom I even switched my signed SystemUI.apk with the one in the rom and flashed it fine.
I have downloaded update.zip(s) and flashed them fine. But whenever I edit the update-script my self it doesn't do anything .. I've even tried a simple
Code:
ui_print("message");
and it failed.
Not sure what I am doing wrong never had this problem when i was theming for my Lg Revolution way back when .
Also I'm using Notepad++ and eol conversion is set to unix.
Thanks to anyone with answers.
Click to expand...
Click to collapse
It's update-binary. Try this one: https://db.tt/MdWU1rZ8
You can mount /system with this: run_program("/sbin/busybox","mount","/system");
You do not need the signature files in /META-INF

Aerowinder said:
It's update-binary. Try this one: https://db.tt/MdWU1rZ8
You can mount /system with this: run_program("/sbin/busybox","mount","/system");
You do not need the signature files in /META-INF
Click to expand...
Click to collapse
Thanks I renamed it back to update-binary I'm not sure what I did differently but I have one working now.
However I noticed in my post I didn't forget any semi colons, But that will keep the whole file from installing so maybe I had the right setup before and just missed a semi colon.
Thanks again

[TOOL] [WIN/LINUX/MAC/ANDROID] [4.4.x] Grouper EXT4 to F2FS ROM Converter

This is a simple script that will convert any grouper EXT4 ROM to F2FS. The script will simply swap out boot.img (i.e. the kernel) and edit the updater-script to replace EXT4-specific lines with F2FS-specific lines. The included boot.img may be replaced with any grouper F2FS boot.img.
NOTE: If you have not reformatted your device for F2FS, you're not ready to use this tool yet. This tool will make a ROM F2FS-compatible, it will not convert your device to F2FS. To reformat your device to F2FS, start here: http://forum.xda-developers.com/showthread.php?t=2678140
Windows instructions:
1) Unzip the windows zip to any empty folder.
2) Place your EXT4 ROM zip in the same folder, make sure there are no other zips in this folder.
3) Run EXT4_to_F2FS_grouper.bat.
Linux / Mac instructions:
1) Ensure you have sed, zip, and unzip installed. And note that this is a bash script.
2) Unzip the linux_mac zip to any empty folder.
3) Place your EXT4 ROM zip in the same folder, make sure there are no other zips in this folder.
4) cd into your converter folder.
5) Run "chmod +x EXT4_to_F2FS_grouper.sh". This only needs to be done once.
6) Run "./EXT4_to_F2FS_grouper.sh".
Android instructions:
1) Ensure you have a zip binary, likely located at /system/xbin. If not, flash zip_binary_flashable.zip from recovery.
2) Ensure you have busybox. Stericson's 1.22.1 definitely works: https://play.google.com/store/apps/details?id=stericson.busybox. Others may not, try Stericson's before reporting problems.
3) Unzip the android zip to any empty folder on the SD card.
4) Place your EXT4 ROM zip in the same folder, make sure there are no other zips in this folder.
5) Open an Android terminal
6) Run "su" (there's problems with unzipping when not root for some reason)
7) cd into your converter folder
8) Run "sh f2fs.sh"
Mediafire Downloads: https://www.mediafire.com/folder/k70lnuoqldzxr/EXT4_to_F2FS_grouper
Google Drive mirror: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhcWZLS0p1T2lWeUU&usp=sharing
Changelog:
7/11/14: Very minor change to Linux tool to make it compatible with the Mac terminal.
7/8/14: Windows, Linux, & Android tools handle /data mounting (for SlimKat).
7/1/14: Initial release, included boot.img is stock LiquidSmooth 06-27-2014 recompiled for F2FS.
Credits:
@NABENDU1 for the original grouper F2FS ROM conversion tool that inspired this: http://forum.xda-developers.com/showthread.php?t=2731666
@johansenmo for the assistance in making the Linux tool Mac compatible.
@legolas93 for the F2FS work: http://forum.xda-developers.com/showthread.php?t=2678140
My other projects:
LiquidSmooth-OFFICIAL for maguro: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2667078
LiquidSmooth-OFFICIAL for toro: http://forum.xda-developers.com/gal...m-liquidsmooth-v3-1-kitkat4-4-3-toro-t2575560
LiquidSmooth-OFFICIAL for toroplus: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2672510
LiquidSmooth-UNOFFICIAL for maguro: http://forum.xda-developers.com/gal...aguro-toro-t2793275/post53641446#post53641446
LiquidSmooth-UNOFFICIAL for toro: http://forum.xda-developers.com/galaxy-nexus/verizon-develop/rom-liquidsmooth-v3-1-toro-t2793284
LiquidSmooth-UNOFFICIAL for toroplus: http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-liquidsmooth-v3-1-toroplus-t2793281
LiquidSmooth-UNOFFICIAL for grouper: http://forum.xda-developers.com/showthread.php?t=2709385
F2FS Converter tools for Galaxy Nexus ROMs: http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
Ting APNs to fix LTE: http://forum.xda-developers.com/galaxy-nexus/general/ting-flashable-zip-fixed-lte-android-4-t2428999
Verizon APNs to fix MMS: http://forum.xda-developers.com/android/software/tool-verizon-mms-apn-patch-t2833914
Click to expand...
Click to collapse
[poo]

Has anyone tried this yet? Away from pc so can't give insight but looks promising
Sent from my HTC One XL using XDA Premium 4 mobile app

pjcanales said:
Has anyone tried this yet? Away from pc so can't give insight but looks promising
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lots of people have been using my Galaxy Nexus version and the code is practically identical. http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
[poo]

OP updated with 7/8 release of Windows, Linux, and Android tools.
[poo]

F2fs really makes the difference...should be the default partition for everyone
Sent from my Nexus 7 using XDA Free mobile app

I can't get the converted CM11 nightly for 7 July to boot on my Nexus 7, it stuck on CM boot animation looping.
This is what I did:
1. flash TWRP 2.7.1.1 with F2FS support
2. change file system for /system, /cache and /data to f2fs
3. reboot into recovery again
4. flash the converted ROM and reboot system
Did I do something wrong?

thedesp said:
I can't get the converted CM11 nightly for 7 July to boot on my Nexus 7, it stuck on CM boot animation looping.
This is what I did:
1. flash TWRP 2.7.1.1 with F2FS support
2. change file system for /system, /cache and /data to f2fs
3. reboot into recovery again
4. flash the converted ROM and reboot system
Did I do something wrong?
Click to expand...
Click to collapse
Looks like you did everything right to me. Normally any issues with the ROM expecting EXT4 and getting F2FS (or vice versa) or the boot.img result in getting stuck at the Google logo. Since you've actually progressed to the CM boot animation, something else is going on. I ran CM11 7/7 through my Windows tool and everything looks like it should. Have you tried installing a different F2FS kernel immediately after flashing the converted CM11? Have you tried installing any other F2FS ROM?
[poo]

just tried OmniROM and it stuck at boot animation also.
Same result when flashing another kernel (M-Kernel)

thedesp said:
just tried OmniROM and it stuck at boot animation also.
Same result when flashing another kernel (M-Kernel)
Click to expand...
Click to collapse
Are you all f2fs, cache, system, and data?
[poo]

Yes
/system /cache /data are all f2fs
Tried again with CM11 M8 + M-Kernel and it worked!!
Still don't know why...

thedesp said:
Yes
/system /cache /data are all f2fs
Tried again with CM11 M8 + M-Kernel and it worked!!
Still don't know why...
Click to expand...
Click to collapse
That's odd. But ok, I'll take it.
[poo]

OP updated. The Linux tool is now Mac compatible.
[poo]

Working for Stock Rom?
I have the stock rom from Google, it should work on it too right?
(nakasi-lrx21p-factory-93daa4d3.zip)
I'm trying this as I type. Will report results soon.
EDIT: I tried the windows version according to the instructions and it gives the error: boot.img is not supported archive. Incorrect function and cannot find archive.
EDIT2: Okay. I realize it won't work with the factory image.

[HELP] Error executing update binary in zip

Hey,
I'm trying to update my One Plus One from CM11 44S(rooted) to CM12 Nightly, I have downloaded the CM12 Nightly file( cm-12-20150124-NIGHTLY-bacon.zip) from the official cyanogenmod page. I have TWRP [v2.8.4.1] recovery installed on my One Plus.
The issue:
I transferred the .zip file and gapps to my root folder and booted my phone into recovery. I performed a Backup of my ROM with the tools available with TWRP, then I wiped Cache,Dalvik Cache,System and Data. Now when I try to flash the .zip file from the Install section I get the following error.
E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....​Another statement that looks like an error.
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
assert failed : oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"​Things I have tried :
1) repeated the above procedure two to three times
2) checked md5 checksum of the .zip file ==> it matched the one on the website
Can someone please help me sove this issue? Am I doing something wrong?

It only happened when youre coming from a KK ROM i dont know why. Flash an earlier nightly build e.g. 20150123 build, then flash 20150124 build. This worked for me.

redundant
I have not tried it yet, but don't you think it would be redundant since 20150123 would itself require a previous build.
Thanks for the support though.

sgovindN said:
I have not tried it yet, but don't you think it would be redundant since 20150123 would itself require a previous build.
Thanks for the support though.
Click to expand...
Click to collapse
Tried it didn't work.

Guys please help
Guys please help. I am too facing the same problem. I also even tried installing the previouds update of 23rd but it didn't help. Please help us...

Me too. I'm having the same problem in the same circumstances as @sgovindN. I've already tried CM12 from 23.01, 22.01, 13.01. The same error

Have all you guys updated your firmware?
Transmitted via Bacon

What do mean by updated firware. I am running on cynogenmod 11.0 44s version.

Pady200550 said:
What do mean by updated firware. I am running on cynogenmod 11.0 44s version.
Click to expand...
Click to collapse
In order to run the latest CM12 nightlies you need updated firmware, it's been mentioned countless times in both of the CM12 threads here on XDA.
Transmitted via Bacon

[Fixed]
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.

sgovindN said:
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
Click to expand...
Click to collapse
I'm pretty sure that isn't actually fixing the issue, that's just sidestepping the safeguard that's built into the updater script.
Transmitted via Bacon

sgovindN said:
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
Click to expand...
Click to collapse
Thanks for your help. i have now successfully installed CynaodenMod 12 on to my Oneplus One.

Not able to update new rom by cyandelta. Guys help.

Pady200550 said:
Not able to update new rom by cyandelta. Guys help.
Click to expand...
Click to collapse
Which brings me back to my previous question earlier in the thread; have you updated your firmware?
Transmitted via Bacon

Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley

Pady200550 said:
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Click to expand...
Click to collapse
That's right, that'd what you needed to do in the first place. The method posted by @sgovindN is not a solution at all, it just sidesteps the safeguard that's there to ensure that you're on the right firmware.
Transmitted via Bacon

LMAO I can't believe what @sgovindN did there.... TZ assert is there for a reason, and your "fix" is just a bs work around, @Pady200550 recent posts prove that. It would have taken far less effort to do it the proper way instead of coming up with that
If anyone ever find this thread in the future, DO NOT do what @sgovindN posted. Do it the proper way as @timmaaa posted with the updated firmware
Sent From Lollipopified Bacon Goodness!

Firmware Update?/
Pady200550 said:
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Click to expand...
Click to collapse
I am on 4.4.4 custom rom PACman but unable to intall CM12/resurrection remix/Liquidsmooth/Blisspop (All 5.0 based) it gives me error : E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....
please explain how did you mange to install CM12 ?

sagar0592 said:
I am on 4.4.4 custom rom PACman but unable to intall CM12/resurrection remix/Liquidsmooth/Blisspop (All 5.0 based) it gives me error : E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....
please explain how did you mange to install CM12 ?
Click to expand...
Click to collapse
Are you using multirom? If yes, update to latest it will install blisspop for sure as secondary, I dunno about the rest
Since you're still on KitKat you need to install the cm12 firmware first though. You can find it in blisspop thread
Sent From Lollipopified Bacon Goodness!

I'm with cm11s as a primary in multirom and managed to install Liquidsmooth lollipop. Also managed to install CM12 but it crashes on load, and I get the "E:Error executing updater binary in zip '/tmp/mr_update.zip'" when trying to install Blisspop or tugapower.
From what you guys say, I shouldn't be able to run liquidsmooth as my "basis" is the CM11S firmware, but fact is I can xD
Isn't there a way to flash the updated firmware only over the secondary (lollipop) rom? Or is it possible to run CM11S as a secondary, with CM12 as primary?
I really want to try CM12 (to see the "future" for my OpO), but don't want to lose my fully customized CM11 just yet

[Q] OTA modifier

Thank's to this forum I have phone with 16gb memory, fastboot , TWRP and rooted - this is really great, thank you!
There is new update for 6039H - - 010 07p ~55Mb the of size, waiting for installation.
1st - where is this the file? Where "System updates" app is hiding it?
2nd - should we check update.zip somehow before flashing or just modify, flash and see results.?
Thank you.
Sent from my 6039H using Tapatalk

Just found where is ota hidden : /data/data/com.tcl.fota/.fotadownload
You need to have "Show hidden files" enabled in file manager to see/find it.
I tried use ota_modifier.sh get error:
ota_modifier.sh update.zip
The provided file is not a zip file!
then:
file update.zip
update.zip: Java Jar file data (zip)
In my system LXLE 14 witch is actually Ubuntu there is "zip" not a "Zip" witch is expected from script. I had to change this - editing script. One letter - big difference for linux.
Flashing update_modified.zip filed...
"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip .... [path to my modified zip]
Error flasing zip [path]
[edit]
If you see this error reason is - root. Need to be fully unrooted!
Now everything went fine. Flashed thru TWRP, rerooted. Whole process takes quiet of time be patient.

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