sdat2img & img2sdat: Unpack Android .dat images - Andrei ...
sdat2img by xpirt
Is March-Security-Patch for Android 7.1 real?
My father has a "Motorola Moto G4" (athene) and I'm currently building the OS for his smartphone on my Linux VM. But I'm suprised that my current build has the Patch-Level 2020-03-05 (I checked it by creating an image with sdat2img, mounting the image, looking into /build.prop and searching for ro.build.version.security_patch) How is that possible? Android 7.1 is not longer supported by Google (Android 7.1 is on https://de.wikipedia.org/wiki/Liste_von_Android-Versionen marked red as "older version, not supported anymore" [the english wikipedia page sadly doesn't have this information] and the recent Android Security Bulletin https://source.android.com/security/bulletin/2020-03-01 has no entry for 7.1) Is the LineageOS-Team backporting the security fixes?
E:\HIS Documents\Computer guides\LG G7\Softwares\lineage\lineage zip extract>C:\ ProgramData\Python\python sdat2img.py system.transfer.list system.new.dat system .img sdat2img binary - version: 1.2
Same result: https://i.imgur.com/32tYXnL.png Update: I had to manually specify the file extension, i.e. system.new.dat.br, instead of, system.new.dat The system.img file is 1.29GB. How would I go about extracting vendovbmeta/dtbo? Update: QFIL tool let me extract the different vendor files it seems, but ideally, I'd like to do so through LG's KDZ file on my PC.
Can't connect to Mi-Band/too many devices? Read this!
CyanogenMod 13 broke Bluetooth LE on the 9th/10th of January and people have been having trouble pairing with their band since. I posted this as a reply in another thread but since I fixed it I thought I'd share. You will need root/custom recovery and access to an older ROM. It doesn't have to be exactly the same ROM (for example I used files from the Resurrection Remix ROM from December but I'm now running CM13 nightlies), as long as it's based on CM13 and built prior to the 9th of January. To fix it I replaced the bluetooth files in /system with files from an older build prior to the 9th. You will lose the a2dp fixes that broke the BLE functionality - I personally haven't noticed a difference. If you can find an old build, you need to:
Guide: Enabling built-in superuser (using official files only)
Note: This is for CM12S. For those who are a bit paranoid and/or conscious of the risk in using magical "root my phone" programs... (note: there's a .zip here that will do this for you; I've checked that the files used are the same you'd get by following this guide) The first step is enabling a "debuggable" kernel. This will allow you to use root from ADB. To do so, download the boot-debuggable image (link in post), put the device in fastboot mode (adb reboot bootloader or hold volume-up while booting) and run fastboot flash boot cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img Now boot the phone normally, go to Settings -> About Phone. Tap a bunch on Build Number until it tells you that developer settings are active. Go back, enter "Developer options". Turn "Android debugging" on and set "Root access" to "Apps and ADB". Make sure adb is working (device needs to show as "device" under adb devices). Restart adb with root privileges: adb root and make sure /system is mounted for write: adb remount Now, download a CM12 (not 12.1) nightly for the device. You'll need to convert the system.new.dat file (sparse filesystem image) to a mountable, standard filesystem. I used https://github.com/xpirt/sdat2img (python script). Run it like so: sdat2img.py cm-12-20150414-NIGHTLY-bacon/system.transfer.list cm-12-20150414-NIGHTLY-bacon/system.new.dat system.img Now the system image needs to be mounted; the right way to do this depends on your OS. On Linux, this is trivial; mount it as any other device. (sudo mount system.img /mnt) On Mac OS, install ext4-fuse (brew cask install osxfuse; brew install ext4-fuse) and run ext4fuse system.img /some/directory. On Windows...well, find a way to do this. You might be better off with a Linux VM here. Once it's mounted, navigate to the root of the image and copy xbin/su somewhere. cp /mnt/xbin/su ~ Now, we just need to drop this su binary on the device. adb push su /system/xbin/su Now, you have to tell SELinux that this binary can act as su. To do so, open a shell: adb shell and set the context... chcon u:object_r:su_exec:s0 /system/xbin/su and set the right owner and permissions... chown 0:0 /system/xbin/su chmod 06755 /system/xbin/su Close the shell. Reboot the device, and root should now be working (though do note - it's managed in Privacy Guard now, there is no preference pane for it). Unlike CM11, you do not need to arrange for the su daemon to be run. /init.superuser.rc will do this for you.
Convert sparse Android data image to filesystem image Using sdat2img and img2sdat binaries you can unpack and decompress Android sparse data image files (.dat) sdat2img.py system.transfer.list system.new.dat system.imgby 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) 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 (optional) Example. This is a simple example on a Linux system: ~$ ./sdat2img.py system.transfer.list system.new.dat system.img OTAs ~$ ./sdat2img.py system.transfer.list system.new.dat system.img 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. Info.
Rekaman saat Install brolti sdat2img Tapi ujicoba QEMU untuk menjalankan IMG masih gagal OnnoCenter Auto Tool Unpack Repack .DAT & .IMG For Windows v2.0 (Marshmallow Supported) Tool by: MTK THAI ROM MODDER (Thailand) Create tool by : Kritsada Chaitan Thank ... herramientas a usar http://adf.ly/1aAWIu pagina para descargar pyphon http://adf.ly/1aAWKH comandos por si no quieres escribirlo en el cmd sdat2img.py system...