Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
splituapp is similar to splitupdate.pl and split_updata.pl for unpacking/splitting/extracting img files from an UPDATE.APP file. The main difference being this one is written for Python2/3 instead of Perl. Additionally, splituapp allows you to extract specified img files where the others will only extract all img files at once. This saves a lot of time if you know which img files you want.
Assuming splituapp and UPDATE.APP are in the same directory and you have a command prompt open in that directory, here are some examples.
To extract all img files:
Code:
splituapp -f UPDATE.APP
To extract only system.img and boot.img:
Code:
splituapp -f UPDATE.APP -l system boot
You can run "./splituapp -h" (Linux) or "python splituapp -h" (Windows) to get usage instructions.
Like splitupdate.pl and split_updata.pl, splituapp will do crc checksum verification on the img files after extraction if the crc binary is in the same directory the script is run from. Unfortunately I do not have the source for the binary so it is only available for Linux at this time. As a result, the crc verification will be disabled in Windows for now.
This program does not extract the images it splits from UPDATE.APP. Once the img files are split from UPDATE.APP the job is complete. If you are looking for a tool to handle system.img extraction you can check out SuperR's Kitchen.
splituapp Download/Source
Enjoy
Credits:
I am not sure who did what, but thanks
McSpoon, JoeyJiao, ZeBadger - for the data_structure file in splitupdate.pl and the crc binary for Linux
reserved
Updated.
Changes:
Improved argument parsing by adding -f and -l switches.
Improved the help output.
NOTE: Make sure you check the command syntax, it has changed.
CRC errors
Hi,
when extracting the UPDATE.APP of BKL-L09C432-9.0.0.178(C432E4R1P12) I have CRC errors like:
Code:
$ ./splituapp -f UPDATE.APP -l recovery_ramdisk
Extracting recovery_ramdisk.img ...
Calculating crc value for recovery_ramdisk.img ...
ERROR: crc value for recovery_ramdisk.img does not match
Doing all this on Ubuntu 18.04.2 (Kernel 4.20).
Can I trust the extracted images?
Update: After a crosscheck with the use of "split_updata" and hashing both extracted recovery_ramdisk and following use of the extracted .img with Magisk to root my Honor V10, I can confirm that the image was correct even with the CRC-error.
Updated.
Changes:
Check for files with duplicate names in UPDATE.APP and append file names with _2 to avoid overwriting the first.
Do not read entire file into ram before writing it. This will help PCs with less ram to extract large files.
General code cleanup.
Hello
You are talking about the new encryption EROFS I updated my huawei p10 EMUI 9.1 to latest version i unlocked the bootloader trying to flash Chinese firmware on it then it bricked no sign of power but my pc recognise it in Fastboot I downloaded a file from xda named p10 revive which includ the flashing firmware. but the partitions are not flashing even if I flash it individually please can some one help and show me how to RW the partition from RO please
SuperR. said:
Updated.
Changes:
Check for files with duplicate names in UPDATE.APP and append file names with _2 to avoid overwriting the first.
Do not read entire file into ram before writing it. This will help PCs with less ram to extract large files.
General code cleanup.
Click to expand...
Click to collapse
Can you please help with how to bypass EROFS because my phone bricked and it's not sending the cust, system, vendor ....etc when I flashed please enligh me on how to RW the EMUI 9.1 partitions
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wrote a web converter that takes a properly sized image (1080x1920) converts it into a IMG file and packages it up into a zip file which you download. Unziping the file will provide you with a splash.img file which you would place into your ADB directory and then use fastboot to load onto your phone.
YOU MUST HAVE S-OFF for this to work!
This is ONLY for the HTC Droid DNA
Prerequisites:
ENG HBOOT
S-OFF
How it works.
o You create an image.
o Image must be 1080x1920 in size
o Image must be in png, jpg or gif format
o Go to the converter website: http://droid.tnet.com/dnasplashgen and upload your image
What the converter does
o checks that the image uploaded is the right type
o checks that the image is the correct dimensions
o converts the image to a splash.img file
o creates a zip file with this image file in a unique id zip file
o Presents you with the ability to download the file.
What you need to then
o After you download the zip file onto your hard drive. Extract the included splash.img file contained in it.
o Move it to your ADB directory
o Boot phone into fastboot mode.
o Open command prompt in ADB directory and type in:
Code:
fastboot flash splash1 splash.img
o When complete use the next command to reboot your phone
Code:
fastboot reboot
Web Generator
o http://droid.tnet.com/dnasplashgen
Other Splash Generators:
HTC Rezond
HTC EVO 4G LTE
So you just upload a picture and it provides you with the .img? If not, what exactly is it?
Sent from my HTC6435LVW using xda app-developers app
You create a picture that is 1080x1920 in jpg, png or gif format... upload it.
The generator converts it into the proper img format (something like: ffmpeg -i uploaded.png -f rawvideo -pix_fmt rgb565 splash1.img ), creates a Zip file with the necessary files (android-info.txt) and lets you download it.
I believe (as I don't have the DNA to test) but you rename the file as PL83IMG.zip, stick it in the root of your SDcard and flash it.
I already have a few samples in the gallery, but I've not yet had anyone try one. http://droid.tnet.com/dnasplashgen/gallery
krelvinaz said:
I believe (as I don't have the DNA to test) but you rename the file as PL83IMG.zip, stick it in the root of your SDcard and flash it. http://droid.tnet.com/dnasplashgen/gallery
Click to expand...
Click to collapse
Nope the DNA doesn't have a removable sd card so you have to flash it via fastboot
Sent from my HTC6435LVW using xda premium
I generated one, and flashed the IMG via fastboot
fastboot flash splash1 image.img
worked fine for me. thanks
DELETED
I've updated the first post and activated the pages on my site.
I am still using a zip file due to the size of the generated img file which is 4gb in size. The zip file makes this significantly smaller for storage and transfer.
ADB is needed along with S-OFF and the ENG Hboot.
It worked perfectly for me. Thanks for this. Now if only there was one for the boot animation.
Modification utilities FindleeDEODEXING NOTE-3 ; S4 for UBUNTU, Linux MINT
System Requirements:
OS << Ubuntu; Linux MiNT >>
Installed Java
Application:
Download the archive, unzip it to the home directory, go to the folder and apply the script deodex Start
After completion of the process to pick up from my deodexsing ready folders app and folder framework
You can just throw extracted from the image folder and app framework in a folder and apply a script deodex aot
Features:
Automatically unpacks the firmware from the zip or tar.md5.
Automatically mounts the image and extracts the app folder and framework.
Deodex, zipaling, optimizes image inside apk.
Installed version 2.0.2 baksmali
Download: View attachment Deodexsing.tar.gz
Modification utilities FindleeDEODEXING NOTE-3 for UBUNTU, Linux MINTOnly for 4.4.2!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
System Requirements:
OS << Ubuntu; Linux MiNT >>
Installed Java
Application:
Download the archive, unzip it to the home directory, go to the folder and apply the script deodex Start
After completion of the process to pick up from my deodexsing ready folders app and folder framework and priv-app.
Features:
Automatically unpacks the firmware from the zip or tar.md5.
Automatically mounts the image and extracts the app folder and framework and priv-app
Deodex, zipaling.
Installed version 2.0.3 baksmali
Downloads: View attachment DEO_KIT_KAT.tar.gz
Thankyou, this is very easy.
Also the attatchment in tapatalk says it is 1 byte in size, is this a common problem? Downloaded and it is 1.92mb.
Sent from my SM-N9005 using Tapatalk
does not work, it asks me root password when putting and accept unmounted partition closes and returns to the main menu.
rogerscrack said:
does not work, it asks me root password when putting and accept unmounted partition closes and returns to the main menu.
Click to expand...
Click to collapse
Do you have problems in OS
I try to kali and does not work, format and install mint 16 and not working ... are my OS?
Enviado desde mi SM-N900 mediante Tapatalk
hello @alexyuh. I tried with ubuntu 12.04 lts, and does not work ... I have the same problem with Kali and Mint.
also try compressing the zip/system.img.tar.md5. zip/system.img.tar. only zip/sistem.img. and every combination you can think of.
also, thanks.
Thanks, I am using your script to deodex kitkat for ZTE Open C.
How about in Windows OS?
I am not the author, the author is a Chinese user, just a simple translation, the original post will be placed in the back.
-----------------------------------------------------------------------------------------------------------------------------------------------------
Amazfit nexo (Magisk,root,wearable)
Why not use fastboot because the command is disabled.
You need: adb tool, QFIL (in QPST), MagiskManager.
1 .Install QPST on your computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.Open QFIL and adb, enter adb reboot edl in the command window to enter 9008 mode
3.Extract boot
3.1)Download firehose and configure it according to the figure below
3.2)After entering Partition Manager, right-click the partition and click Manage Partition
3.3)Read partition: read as below
==============================================================================================
Note: Please backup each partition according to the above method, otherwise you will not be able to boot after failure. You can't use other people's recovery package to recover.
And at the same time rename to the partition name (without changing the suffix)
==============================================================================================
4.Convert boot.bin to boot.img (use IMg2simg)
5.Import to watch
Put boot.img into the watch, and cancel the hook of keeping avb2.0 in the installation option of MagiskManager.
6.Flash into boot
There is a magisk_patched.img file in the Download folder of your watch, put it on the computer, the watch restarts into 9008 mode, also use Partition Manger, right-click the boot partition (not aboot partition, don't
make a mistake), also click on the first One item, but to flash it in, we click Load Image and select this magisk_patched.img for flashing, twrp is the same.
7.Flash into wearable
Install ROOT Explorer,Unzip the wearable.zip and put it in the watch, copy it into the corresponding path one by one (for example, system/framework corresponds to /system/framework)
8.Then you can try to install some modules or wearos applications
File:
https://drive.google.com/drive/folders/1BHlxNqKZ3QoRv3PSULn1AwGadowSA_nQ?usp=sharing
Link:
https://www.coolapk.com/feed/176069...d=1096145&shareFrom=com.coolapk.market_10.2.1
https://www.coolapk.com/feed/175621...d=1096145&shareFrom=com.coolapk.market_10.2.1
https://www.coolapk.com/feed/173257...d=1096145&shareFrom=com.coolapk.market_10.2.1
https://www.lanzous.com/b015anw7e 密码:5ty2
can you point us to the direction of this chinese guy?
xicko said:
can you point us to the direction of this chinese guy?
Click to expand...
Click to collapse
This is the CoolMarket homepage of Chinese authors. Http://www.coolapk.com/u/1415080
The author also asked a programmer to compile it TWRP,https://wwu.lanzouv.com/i1L9Y0a61q3c
Password: 69zz
My Old Computer is slow down when changes to WSL2Note: May be there are someone wants to modify GSI suitably for their device.
Modified sub-partition of super.imgStep by StepCREATE CustomAP for Odin Flashing with Patching Dynamic Partitions.
*** the continue part of Step by Step CREATE CustomAP framework file for GSI Flashing with Odin.
(Required Win10 with wsl2 or Ubuntu or VirtualBox)
What are we doing now ?1) unpacking super.raw with imjtool. ( super.img.lz4 -->super.img-->super.raw)
2) resizing system.img (in order to insert our modifications to the rom)
3) mounting system.img
4) do our modifications
5) umounting system
6) shrink edited system.img to the minimal size
7) generating new super.img
8) Create customAP file ( for flashing it to our device with odin.)
>>>>Part 1 (update to used win10 + WSL2) is here. https://forum.xda-developers.com/t/...s-a12-a13-installation.4473159/#post-87204333
Steps ( Essencial tools)Extract Sub-Partition inside super.img.lz4 tool## Download Samsung framework file. (Stock Firmware) with
Bifrost.
## Extract "super.img.lz4" from (AP framework file) with (unzip FILE.zip) command. or uses utility from win 10
## Decompress "super.img" from "super.img.lz4" with LZ4 command
## sparse format ""super.raw" from "super.img" with simg2img command
## Use imjtool to extract the partitions of super.raw. Notice that partitions in a super image are split into several groups.
(The exact grouping varies across devices/OS versions, so one should always use imjtool to check first.)
Code:
wget http://newandroidbook.com/tools/imjtool.tgz && tar xzvf imjtool.tgz
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
imjtool v2.0 beta1
*You may also use the official lpunpack for extraction but it can’t display the group schema.
Code:
./imjtool.ELF64 super.raw extract
output:
MMapped: 0x7f5f4a89d000, imgMeta 0x7f5f4a89e000
liblp dynamic partition (super.img) - Blocksize 0x1000, 2 slots
LP MD Header @0x3000, version 10.0, with 4 logical partitions on block device of 5812 GB, at partition super, first sector: 0x800
Partitions @0x3080 in 2 groups:
Group 0: default
Group 1: main
Name: system (read-only, Linux Ext2/3/4/? Filesystem Image, @0x100000 spanning 1 extents of 3 GB) - extracted
Name: product (read-only, Linux Ext2/3/4/? Filesystem Image, @0xe6700000 spanning 1 extents of 1 GB) - extracted
Name: vendor (read-only, Linux Ext2/3/4/? Filesystem Image, @0x12d500000 spanning 1 extents of 685 MB) - extracted
Name: odm (read-only, Linux Ext2/3/4/? Filesystem Image, @0x158300000 spanning 1 extents of 4 MB) - extracted
Note: Notice file size of "system.img" =3GB
Full contents here: https://forum.xda-developers.com/t/...s-a12-a13-installation.4473159/#post-87204293
While researching about Run-length-encoding (RLE) and modifying the source code of the splash image tool for the OnePlus 6 series to be compatible with 8 series (which was starting to look promising), I ended up stumbling upon this GitHub repository for a tool that already accomplishes the unpacking and repacking process of logo.img for various OPlus (Oppo + OnePlus = OPlus) devices.
This has been tested on both OOS12 and OOS13 firmware. Compatibility with older versions of the logo.img from previous OOS versions (OOS11 and below) is unknown at the time of writing this.
Usage
Unpack oplus splash image:
./opsplash unpack -i orig-logo.img -o pic
Editing:
You'll want to make your edits to the output file named "boot". I noticed that if "boot" exceeds the default size it will not show up during power on and will instead display a black screen. It is advised to keep the bitmap file the same size or less to work properly.
Repack oplus splash image:
./opsplash repack -i orig-logo.img -o new-logo.img
Only read image info:
./opsplash readinfo -i orig-logo.img
Flashing
This will need to be done in fastbootd rather than fastboot (bootloader), since regular fastboot (bootloader) prevents flashing critical partitions.
Original logo:
fastboot flash --slot=all logo orig-logo.img
New logo:
fastboot flash --slot=all logo new-logo.img
Side note:
I seem to have found some rather unusual images in the logo.img for instantnoodlep. You'll just have to unpack it and see for yourself -_-
Reserved
made this one, looks good. logo.img in attachment, plus original bmp, remove the *.pdf extension (xda impose upload rules)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
why do i keep getting this error my stock boot.bmp is 7.41 MB
the one i want to replace is 6.67 mb
but i keep running to this error
whould you know why?
halloweenm925 said:
why do i keep getting this error my stock boot.bmp is 7.41 MB
the one i want to replace is 6.67 mb
but i keep running to this error
whould you know why?
Click to expand...
Click to collapse
Your bmp file does not pass checks:
1. You bmp file header is doesn't equal to 0x36.
2. BMP file itself seems to be wrong or corrypted.
Also try to rename it to contain no spaces in filename.