[TOOL][MOD][A12/A13] Unpack & repack OPlus splash image (logo.img) [LINUX][WINDOWS] - OnePlus 8 / 8 Pro & 8T Cross Device Themes, Apps &

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.

Related

[Q]Scatter file To Alcatel OT 918M

Hello, I am trying to rooting my device (ALCATEL OT 918M V2.3.6) by this guide:
http://forum.xda-developers.com/showthread.php?t=1748927
And I keep get the following error:
==========================
EBOOT ERROR: (16008)
[Android] Partition size changed!
[HINT]:
Partial images download error.
The following partitions must be down FULL downloaded all together
===============
After a quick seacrh online I understand that I need the correct Scatter file, but where can I get him?
I tried to work with this software on windows 7 Home Premium 64 bits:
{
"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"
}
http://forum.xda-developers.com/attachment.php?attachmentid=1173969&d=1341315997
Apparently it does not work...
It is important to add that I downloaded the software "One Touch Upgrade S 2.7.0" and upgrade my phone...
My question is how can I discover the Scatter file from my device?...
Thanks for your time
check out this
WH1234e7 said:
Hello, I am trying to rooting my device (ALCATEL OT 918M V2.3.6) by this guide:
http://forum.xda-developers.com/showthread.php?t=1748927
And I keep get the following error:
==========================
EBOOT ERROR: (16008)
[Android] Partition size changed!
[HINT]:
Partial images download error.
The following partitions must be down FULL downloaded all together
===============
After a quick seacrh online I understand that I need the correct Scatter file, but where can I get him?
I tried to work with this software on windows 7 Home Premium 64 bits:
http://forum.xda-developers.com/attachment.php?attachmentid=1173969&d=1341315997
Apparently it does not work...
It is important to add that I downloaded the software "One Touch Upgrade S 2.7.0" and upgrade my phone...
My question is how can I discover the Scatter file from my device?...
Thanks for your time
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2151251
Please help Alcatel OT 918 (without any other character) SP-flash tool files
I need Alcatel OT 918 (without any other character)
scatter file
dsp_bl
preloader
UBOOT
I've tried using some on the net but they result into missing partions like EMMC not found with SP-flash tool.
Also the phone won't boot at all after trying some different scatter files.
But luckily it's still detected with SP-Flash tool.

[GUIDE] How to change the splash screen

After digging around with EDL mode I found out that the splash screen can be very easily changed. As always I'm not responsible for anything that happens to your phone, warranty void and all that.
Requirement:
-One of the below:
1) Rooted ROM
2) TWRP
3) EDL mode setup
-Image editing software, I used GIMP
Making the splash:
1) Using GIMP or any other image editing software make your splash screen in 1440x2560 resolution.
2) Merge the layers and then flip the image horizontally, making it upside down.
3) Export as .bmp format. Turn on compatibility settings if you can any as this needs to be in BMP3 format. This may work with other formats but the stock splash.img is in BMP3. Read more here.
Example in GIMP
{
"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"
}
Click to expand...
Click to collapse
Installing the splash:
A) With rooted ROM or TWRP:
You will need to put the image on your phone. For this guide I'll assume it's on the sdcard named android.bmp.
1)Get into a terminal. You can do this via adb shell or using a terminal emulator on your phone. If you are using TWRP it's under Advanced for a Terminal.
2)
Code:
su
to root yourself. You don't need to do this if it's TWRP as you are already rooted.
3)
Code:
dd if=/sdcard/android.bmp of=/dev/block/bootdevice/by-name/splash
this will write the image to your phone
Click to expand...
Click to collapse
B) With EDL mode. This can be done without root but will void your warranty.
1) Setup EDL mode with MiFlash or the Axon 7 ToolKit.
2) Download the folder below and replace splash.img with your image. I included my splash as well as the stock US one.
3) Flash the folder. WARNING. This folder contains TWRP, Fastboot AND the splash screen. If you don't want TWRP or fastboot you can just edit "rawprogram0.xml and delete the appropriate lines.
Click to expand...
Click to collapse
Downloads and Images:
Example picture: https://imgur.com/Rv098hh.jpg
EDL folder: https://my.mixtape.moe/gkzxwa.zip

Amazfit nexo (Magisk,root)

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

[MOD][TWRP] Change boot-logo

Just for fun I changed the boot logo of my phone. Since it was such an easy a thing to do, here are some logos you can use.
Just boot in to TWRP and flash.
This is how I did it (in linux):
1. extract an original miui-rom. As long as it has the logo.img, it will do.
2. download the wonderful logo-xiaomi.py-script that penn5 has created.
(Link: https://github.com/penn5/logo-xiaomi)
3. extract the logos from logo.img
$ python3.9 logo-xiaomi.py extract -i logo.img -o output
4. edit (using what ever editor or tool you prefer) the images logo-0.bmp (boot logo for locked phone) and logo-2.bmp (boot logo for unlocked phone). Don't edit either of the other two. They're familiar for people, so they know their phone is either in fastboot mode or has been soft bricked. If you do edit logo-1.bmp and/or logo-3.bmp people will be confused if either something soft bricks the phone, or they try to enter fastboot mode. Yes, if you haven't done so in a while this might confuse you. Leave logo-1.bmp and logo-3.bmp alone.
logo-0.bmp and logo-2.bmp is what you want to edit.
IMPORTANT - remember to save as bmp and in the correct resolution. If you save it in the wrong format and/or the wrong resolution, your phone might not show any boot logo on boot.
5. repack the logo.img-file.
$ python3.9 logo-xiaomi.py -i logo.img -o logo.new.img -a logo-0.bmp -a logo-1.bmp -a logo-2.bmp -a logo-3.bmp
Yes, in that order. The logo-xiaomi-script creates the new image of the files in that order. If you change the order of the logo-files, they'll end up in the wrong order on the new logo.img.
6. either create a flashable zip, using one of my zips, adb push the logo and adb dd it on the logo-partition, or fastboot flash the logo.
fastboot flash logo logo.new.img
OR
adb push logo.new.img /tmp
adb shell dd if=/tmp/logo.new.img of=/dev/block/bootdevice/by-name/logo
This is what the bootlogos I've made look like:
AOSCP
{
"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"
}
G-BLACK
GOOGLE-BLACK
HAVOC
SNAPDRAGON
XIAOMI-EU
Standard is just the standard boot logo, in case you wish to revert back to the normal one.
This is great As soon as I get a little free time I am going to change my boot logo to something personal. Even if it's just for showing off to some friends
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
langithitam said:
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
View attachment 5752805
Click to expand...
Click to collapse
No, it's in logo.img. I did all this in linux (Arch). You might get this to work in WSL. But I'm not guaranteeing anything other than I had no problems under linux (others might not have the same luck).
@Verbato
Sir, can you please make this logo?
device unlocked
twrp and magisk installed

MDZ-16-AB bootloader unlocked

I unlock the bootloader of mdz-16-ab by disassembling uboot and write the cracked instructions back to the box using 'mw' command in uboot.
I've only cracked r454 firmware virsion(android 6.0). And I'm looking for someone who have a UART cable to do more tests on this work. My final purpose is to crack the final firmware release (android pie).
Though my work, I can decrypt the boot image and recovery image and boot decrypted images.
If you want to boot any image: mw 77eff124 14000007
If you want to decrypt the boot image and copy it out from RAM: mw 77eff120 d280ccc0; mw 77eff124 aa0003f4
(this is different for different firmware versions, this one is for r454)
You can add 'mw 77eff124 14000007' to the beginning of uboot env 'preboot' and 'saveenv' to autocrack during boot. After that, you can replace the encrypted boot images with decrypted boot images and use twrp and magisk.
If you have upgraded to oreo or pie, don't worry. I need you to do some tests too. I will soon crack these new versions.
{
"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 flash r454 firmware (once r454 update.zip) into my mdz19aa, cant power on, only show MI.
intel_outside said:
I unlock the bootloader of mdz-16-ab by disassembling uboot and write the cracked instructions back to the box using 'mw' command in uboot.
I've only cracked r454 firmware virsion(android 6.0). And I'm looking for someone who have a UART cable to do more tests on this work. My final purpose is to crack the final firmware release (android pie).
Though my work, I can decrypt the boot image and recovery image and boot decrypted images.
If you want to boot any image: mw 77eff124 14000007
If you want to decrypt the boot image and copy it out from RAM: mw 77eff120 d280ccc0; mw 77eff124 aa0003f4
(this is different for different firmware versions, this one is for r454)
You can add 'mw 77eff124 14000007' to the beginning of uboot env 'preboot' and 'saveenv' to autocrack during boot. After that, you can replace the encrypted boot images with decrypted boot images and use twrp and magisk.
If you have upgraded to oreo or pie, don't worry. I need you to do some tests too. I will soon crack these new versions.
Click to expand...
Click to collapse
Could you please make a guide that how to found the address(77eff124) ? Thank you.

Categories

Resources