{
"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.
Related
Well since we have s-off now we can flash our own splash1 screens!
I am using the file i've attatched here in memory of my evo.
{
"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 do it using fastboot I believe there are other methods.
Code:
fastboot flash splash1 splash1.img
fastboot reboot
i didnt search or nothing (i know im a horrible person) but where would one go about creating one of these splash.img's?
Lol ill post a link for howtos in justa minute.
Sent from my PG06100 using XDA App
If anybody is interested, I think I've come up with a process for changing the splash screen on initial boot up.
This is how it will progress:
1. boot phone into bootloader (so it will be ready later)
2. confirm that your 'splash1.bmp' file is located in the 'Tools' folder
3. confirm that there is now a file called 'splash1.bmp.nb'
4. confirm that the 'splash1.bmp.nb' file has been renamed to 'splash1.img'
5. go ahead and connect your phone to the USB cable and your computer then wait 15 seconds
6. check for 2 'OKAY' outputs from the flashing process and wait for 15 seconds again
7. then the batch file will reboot your phone and exit the command window
(waiting to connect the phone to the USB and the two 15 second waits may not be strictly necessary, but I prefer to limit the number of possible things that could corrupt the process)
I've included the bitmap I used for the full process and have had success using [email protected]'s 'splash1.img' in the short process for existing 'splash1.img' files described in the instructions in the zip file.
As always constructive feedback would be helpful if I've missed something.
Darn you! I've been looking for like 2.5 hours trying to get a bmp to convert to img file. Now you come in here flaunting your stupid brain and stuff and now I have a custom splash screen. I HATE YOU.
Sorry...but thats about how long it took me to write out the instructions as concisely as I could AFTER I figured out how to do it!
Any suggestions for clarity in the guide? Any hitches in the process?
I'll check back tomorrow...my head keeps bouncing off my keyboard and I am tired of correcting typos...
I do have a question, is that ability to convert something to an .img file something that has to be done within that directory? or is it just an ability that command line/ terminal have?
The bitmap to img conversion process is the work of the 'nbimg.exe' program I put in the 'Tools' folder of the zip file. It will convert a bitmap into an '.nb' file (which is then renamed '.img') or if you rename the '.img' file back to '.nb' it will convert it back into a bitmap.
Instructions can be found by opening a command prompt where the 'nbimg.exe' file is located and running it without any parameters...you'll get a brief usage explanation and a listing of possible parameters (some of which I have no idea what they are for).
The program was apparently written back in 2008 by a Pau Oliva from XDA. Props to him.
Custom Splash Screen.
Thanks hdmunger the script worked like a champ.
BuddahWolf01 said:
Darn you! I've been looking for like 2.5 hours trying to get a bmp to convert to img file. Now you come in here flaunting your stupid brain and stuff and now I have a custom splash screen. I HATE YOU.
Click to expand...
Click to collapse
straight up flashing this. right now.
Ha yea go ahead.
Sent from my PG06100 using XDA App
MODIFIED TWRP IMAGES FOR TITAN!Yeah, that's it. I was thinking about making twrp images for our device with every single color which you can found in this nice thread. Yes, I know that we can put the theme in /TWRP/theme/. But, why don't get rid of that annoying folder, make the change permanent, and most of all, share knowledge? That's what I'm going to do by making even easier the above guide, plus I'll be uploading modified twrp images (when I got time) ready to flash.
We need:
TWRP Image for titan.
Android Kitchen 2.4 for Windows. It's in the attachments section.
Uncompressed themes. You can choose your fav color there.
Patience and common sense.
1. Uncompress the Android Kitchen zip in your desktop (or any other folder), and download your favorite theme color. Uncompress it too.
2. Put the twrp image which you previously downloaded in the Android Kitchen folder (in the same folder where are the .bat files and so on).
3. Drag the image file to the "unpackimg.bat". There'll be a folder called ramdisk afterwards.
4. Go to ramdisk/twres/, and keep it open in a window. Remember the uncompressed theme folder from the first point? Well, open the uncompressed folder and move this: "images", "portrait.xml", "splash.xml", "ui.xml" to /ramdisk/twres. If windows asks if you want to move and replace these files, hit yes to everything.
5. Go back to the Android Kitchen Folder and click repackimg.bat; wait, and voilá, there'll be a new-image.img. Flash it from fastboot or from twrp itself (remember to check the "recovery" box). Click in "Reboot Recovery" to see how your twrp looks now.
That's all!
Images below are only for titan, not for thea/osprey/falcon. Just click the color, download and flash! They're ready to be flashed.
RED:
{
"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"
}
GREEN:
YELLOW:
BLACK: (This one looks like a darker and dimmed gray though).
(another) RED:
TEAL:
PURPLE:
GRAY:
Disclaimer: I'm not responsible to what could happen to your device. This is generally safe, but there's always people that end up messing their phones in a veeeery strange way. You're warned.
Thanks to: osm0sis, Luk, Luca, fichl and those who made this possible. I don't own anything nor I did any theme. If there's any way to make this better, you're free to post it here. I just share what worked for me.
Works great!
Where i find ramdisk folder
Sent from my XT1068 using Tapatalk
vrkawin said:
Where i find ramdisk folder
Sent from my XT1068 using Tapatalk
Click to expand...
Click to collapse
1. Drag the .img to the unpackimg.bat
2. A new folder (ramdisk) will be created afterwards in the same directory.
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
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
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.