{
"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"
}
Black Version of the logo
https://1drv.ms/u/s!Av6RWY-zSfSekyWGQi5mupY_9jvn
White Version of logo
https://1drv.ms/u/s!Av6RWY-zSfSekyaKccB9UqFgCU6U
This bin file will replace the "Bootloader unlocked" warning message with stock splash screens.
To use:
1: open adb CMD
2: type 'adb reboot bootloader'
3: type 'Fastboot flash logo logo_fix_*****.bin'
NOTE:::::: Replace ***** with White or Black as appropriate for your chosen logo download.
4: Restart and enjoy
Thank you for the mod, Added to Master index for more visibility.
I flashed the logo bin from the other stock files and I still have the unlocked warning.
sent via op5 and xda-app
byt3b0mb said:
I flashed the logo bin from the other stock files and I still have the unlocked warning.
sent via op5 and xda-app
Click to expand...
Click to collapse
Yes, this mod is cosmetic. It won't magically lock your bootloader. That warning is hard coded. These bin files are too just mock the locked state for those who are annoyed by it
I wonder if we can hex edit copy/paste an alternate png--as long as you used the correct start address? It is a png, right?
Uzephi said:
Yes, this mod is cosmetic. It won't magically lock your bootloader. That warning is hard coded. These bin files are too just mock the locked state for those who are annoyed by it
Click to expand...
Click to collapse
ya i know it wont re-lock it this actually does remove the warning, i stand corrected. flashing the logo.bin from the retail zip in the other thread only took away the t-mobile logo splash...
execute logo replacement in Android terminal
to execute logo replacement in root Android terminal (if downloaded to Download folder, otherwise change downloaded file location in flash section), type or copy/paste:
su
grep -q system_b /proc/mounts || echo "using slot a"
(or type to detect)
grep -q system_a /proc/mounts || echo "using slot b"
dd if=/dev/block/bootdevice/by-name/logo_a of=/sdcard/logo_a_backup.img
(or type to backup)
dd if=/dev/block/bootdevice/by-name/logo_b of=/sdcard/logo_b_backup.img
dd if=/dev/zero of=/dev/block/bootdevice/by-name/logo_a
(or type to zero)
dd if=/dev/zero of=/dev/block/bootdevice/by-name/logo_b
dd if=/sdcard/Download/logo_fix_black.bin of=/dev/block/bootdevice/by-name/logo_a
(or type to flash)
dd if=/sdcard/Download/logo_fix_white.bin of=/dev/block/bootdevice/by-name/logo_a
(or type to flash)
dd if=/sdcard/Download/logo_fix_black.bin of=/dev/block/bootdevice/by-name/logo_b
(or type to flash)
dd if=/sdcard/Download/logo_fix_white.bin of=/dev/block/bootdevice/by-name/logo_b
Veeery nice! I was waiting for it...! :silly:
Only one question... both version of the logo have no "warning message transparency" issue?
On my old Griffin only some colours were able to fully hidden the msg...
Fantastic job. Love the blacked out version.
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
TheKnux said:
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
Click to expand...
Click to collapse
Definitely has to be flashed to logo.bin
As Joemoss states: it is on a separate partition than system
Amd4life said:
Fantastic job. Love the blacked out version.
Click to expand...
Click to collapse
Really. I can confirm black one is *fantastic* with Amoled and it doesn't have any "transparency" issue...
This bin file will replace the "Bootloader unlocked" warning message with stock splash screens.
To use:
Click to expand...
Click to collapse
THANKS! That warning screen has always annoyed me I flashed the black one. I love it. Looks "Oldskool" Like my Droid X back in the day
TheKnux said:
Can't we just push this to system files and grant proper permissions or does it have to be flashed?
Click to expand...
Click to collapse
Well... If TWRP can access /dev/block/bootdevice/by-name/logo_b(a) then someone can make a flash able zip quite easily.
I remember on all my HTC phones TWRP could flash to that partition when s-off to remove their Dev splash warning and on some others it required to manually flash a hex edited bootloader, so it just depends
Fabulous! Replaced the T-Mobile image and removed the warning! Many thanks! This is the first device I've ever rooted. So glad I did and wouldn't be able too without all of you developing and teaching
Will this work with Flashfire/Flashify /etc? I don't have a pc, just a chromebook so don't have access to fastboot.
I'm about to release a new twrp with flashable boot logos
joemossjr said:
I'm about to release a new twrp with flashable boot logos
Click to expand...
Click to collapse
Sweet!
joemossjr said:
I'm about to release a new twrp with flashable boot logos
Click to expand...
Click to collapse
Any preview?
Don't forget a version for unbranded Z2s pal..!
Related
BIG LOGO
{
"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"
}
DOWNLOAD: http://www.megaupload.com/?d=7RXNL18L
DOWNLOAD: http://www.mediafire.com/?3nymonjmmuj
LITTLE LOGO
DOWNLOAD: http://www.megaupload.com/?d=GHAP5YFE
DOWNLOAD: http://www.mediafire.com/?1an13t2yqta
How to flash:
fastboot flash splash1 <filename>
fastboot reboot
Nice.
Thanks !!
rgb556?
hey maxisma, whats the file type opened with ?
I was hoping that someone would make this, thanks!
Yeah, I also just get a .txt file downloaded. Should it be renamed to .zip and flashed from recovery?...or ...?
bert269 said:
Yeah, I also just get a .txt file downloaded. Should it be renamed to .zip and flashed from recovery?...or ...?
Click to expand...
Click to collapse
don't change the filename. he has instructions at the bottom of the post. boot into fastboot and type in the commands. everything is how it should be. rgb565 is the correct file type.
Is this animated or not?
idbl_fanatic said:
Is this animated or not?
Click to expand...
Click to collapse
it's a splash screen. it replaces the tmobile g1 screen when you first boot up your device.
grandomegabosses said:
it's a splash screen. it replaces the tmobile g1 screen when you first boot up your device.
Click to expand...
Click to collapse
Oh ok, so it's not the 2nd screen that comes up, darn it! Oh well.
is it possible to use console or terminal?
s0mep00p said:
is it possible to use console or terminal?
Click to expand...
Click to collapse
not from anything i've read. fastboot is your friend.
why the hell is it keep on saying cannot find <file name> when i try to do fastboot for splash screens!!! i made a folder on the desktop with the name "fastboot" and even made a folder with the same name on the root of the sd card. fastboot works and it recognizes my device. if you can help send me a email at [email protected]
Thankyou so much Maxis!
Thanks for the image
AndroidNoobie said:
why the hell is it keep on saying cannot find <file name> when i try to do fastboot for splash screens!!! i made a folder on the desktop with the name "fastboot" and even made a folder with the same name on the root of the sd card. fastboot works and it recognizes my device. if you can help send me a email at [email protected]
Click to expand...
Click to collapse
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.
david1171 said:
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.
Click to expand...
Click to collapse
And fastboot has to be in the same folder as the .rgb565 file
david1171 said:
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.
Click to expand...
Click to collapse
thanks man. I love you (no homo)
Somebody backed this up perhaps? Download links aren't working..
Is there a way to view the raw boot process in text mode instead of the boot animation?
Hoping there is a setting in a config file somewhere....
Edit: ([Solved/Workaround])
One easy solution is to install the paid app mentioned here. It shows you the logcat log as your phone boots.
A free kernel mod to accomplish this is still elusive.
For linux/grub this is accomplished by removing the 'quiet' and 'splash' options in /boot/grub/menu.lst
Also found a possible setting in /init.rc
export ANDROID_BOOTLOGO 1
Click to expand...
Click to collapse
However I cannot chmod this file to edit it even as root. / is mounted read-only
su
chmod u+w init.rc
chmod: init.rc: Read-only file system
Click to expand...
Click to collapse
Do I need to unpack + edit the file + repack boot.img and then flash(boot) it to achieve this?
britoso said:
For linux/grub this is accomplished by removing the 'quiet' and 'splash' options in /boot/grub/menu.lst
Also found a possible setting in /init.rc
However I cannot chmod this file to edit it even as root. / is mounted read-only
Do I need to unpack + edit the file + repack boot.img and then flash(boot) it to achieve this?
Click to expand...
Click to collapse
you need to mount /system as rw before you can chmod anything. SU file manager works well for this, and you can do it all on the phone, even the edits. Just don't forget to make a nandroid before you do any tweaks.
I know there is a way to disable the boot animation in the boot.img-kernel, i've seen it done before.
So you want a verbose boot mode?
uansari1 said:
So you want a verbose boot mode?
Click to expand...
Click to collapse
Yes.
SU file manager is not free.
followinginsanity said:
you need to mount /system as rw before you can chmod anything. SU file manager works well for this, and you can do it all on the phone, even the edits.
Click to expand...
Click to collapse
SU file manager can only mount /data and /system as RW, afaik / is a ramdisk image that is only modifiable if the change is made in a boot.img and flashed.
heh Just depends on where you need to make the changes Its what I used to do the build.prop mods to get navi working on the G1 back before they did the official update. Either way I do hope we can figure out how to disable the boot animation. Like I said I know its been done, and where the guy said he did the mod to do it. But thats only a start. Also I know the emulator has a command so that you can boot it without the animation but thats the emu, not the actual device.
Heres where I am now:
The first X comes from initlogo.rle in the root directory of the bootimage.
The next image is the boot logo. This is a set of two images in framework-res.apk/assets/images.
{
"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"
}
If a bootanimation.zip is found in /data/local or system/media, it is shown next. This is the nexus boot animation.
I tried renaming bootanimation.zip...the boot logo images were shown instead.
I removed the boot logo images from framework-res.apk...got a blank black screen until the lock screen appeared.
Also tried editing pushing a modified init.rc with these commands, didnt help the original init.rc was restored on reboot.
Code:
adb shell mount -o remount,rw rootfs /
adb pull init.rc .
#edit the file.
adb push init.rc /
adb shell sync
adb reboot
Found some instructions on how to edit the boot image:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Thinking of setting up ubuntu in a virtualbox to try this. (Goal is to turn set ANDROID_BOOTLOGO 0 in init.rc). Dont know if this will let us see the verbose boot log or not...
Update:
Tried this. the 2.5MB boot.img splits up into two pieces (ramdisk and kernel), totaling 2MB (?), flashing an updated 2MB boot.img gets the phone stuck on the initial x. ... Something is missing.
heh this is what I want (not the phone)
http://www.youtube.com/watch?v=5yO2KQHkt4A#t=1m44s
Re: Boot with no boot screen? (console)
I noticed there is a /system/bin/bootanimation. I ran it from terminal and the animation played. I couldn't exit it and had to take the battery out to reboot. It took over my screen and disabled all the buttons.
If you removed the images and still had a black screen, I wonder if this program was running but was black because the images were gone. Maybe renaming it would keep it from running and do what you want?
I tried to "cat" it but it's a binary. There was some garbled text toward the end which said "boot animation disabled" and gave some file locations etc. May be some clues there.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
fubaya said:
I noticed there is a /system/bin/bootanimation. Maybe renaming it would keep it from running and do what you want?
Click to expand...
Click to collapse
Tried this.
adb -d shell mv /system/bin/bootanimation /system/bin/bootanimation1
It booted ok and I got a black screen in place of the boot animation, went straight to the lock screen.
Didnt get the console text though
sorry, cant contribute. but id love to have this as well.
Well where are all the Kernel hackers when you need em
Told by someone pretty intelligent that the Kernel will basically need to be compiled to enable the console framebuffer option and maybe remove references to the boot animations etc. I'd love something like this though, wish I knew more about implementing it.
I can contribute a little bit.
Go over to the Dev section, see the "update.zip creation" thread. There are instructions for creating a boot image:
http://forum.xda-developers.com/showthread.php?t=667923
In these instructions, you'll notice an interesting switch for kernel to execute with:
--cmdline 'no_console_suspend=1 console=null'
I believe that might lead you to where you're trying to get
Jack_R1 said:
I can contribute a little bit.
Go over to the Dev section, see the "update.zip creation" thread. There are instructions for creating a boot image:
http://forum.xda-developers.com/showthread.php?t=667923
In these instructions, you'll notice an interesting switch for kernel to execute with:
--cmdline 'no_console_suspend=1 console=null'
I believe that might lead you to where you're trying to get
Click to expand...
Click to collapse
I tried that, the new boot.img I create does not work, see post #8
what did you define as console?
Jack_R1 said:
what did you define as console?
Click to expand...
Click to collapse
What you posted, and also tried the command that was in my boot.img (cyanogenmod)
Re: Boot with no boot screen? (console)
i would love this!
unfortunately i did the same things eg move bootanimation.zip bootanimation script etc.
only got a black screen.
we could build a bootanimation.zip with text images... lol
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
leonnib4 said:
we could build a bootanimation.zip with text images... lol
Click to expand...
Click to collapse
There is one out there, but I prefer the real thing.
We need help from one of the kernel masters!
britoso said:
What you posted, and also tried the command that was in my boot.img (cyanogenmod)
Click to expand...
Click to collapse
But I posted the default command, and marked it in red to say - if you're making a boot image with default command line, you're actually redirecting the console to null, so what do you expect to see?!
First, try eliminating redirection, the default might work. Remove the "console=null" from the line and rebuild the boot image.
In case it still won't work - try to change it to "console=tty", "console=ttyS0" or something like that.
DISCLAIMER:
1) You are doing this at your own risk.
2) Educate yourself first and try this ONLY if you feel comfortable with modifying with your phone.
3) If you break your phone it is not my fault nor is it my responsibility to fix your phone.
Things could go wrong but they shouldn't if you follow the directions and have some general knowledge of Android.
##############################
Go from this:-------------------------------------------------To This:
{
"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"
}
----------
##############################
Things needed:
ADB/Fastboot knowledge - HERE and HERE
RGB565Converter v0.3c - Thanks to DeToX-cz!
UPDATE: You must have the engineering bootloader flashed for access to splash1. Follow the steps here to flash the S=OFF bootloader. -Thanks to jcase
Instructions:
Find an or create an image (.png, .bmp, .jpg, or .gif -- 320x480 is preferrable)
Open RGB565 Converter
Ensure that "To RGB565 (binary)" tab is selected
Click "Open Image", select your image
Click "Convert to RGB565" (RGB565 Converter will make your image 320x480 if it is not already)
CLOSE RGB565 CONVERTER
Reboot phone into Fastboot using this command: adb reboot bootloader
OR Button combo: SEND/CALL + END/POWER
Flash image using this command: fastboot flash splash1 <your_image_name>.rgb565
Reboot phone using this command: fastboot reboot
OR fastboot oem powerdown if not then remove your battery
View the results of your hard work.
Enjoy!
As of right now there is no way to read the splash1 partition to back it up short of some kind of kernel mod to partition splash1 from NAND as a new MTD. At least that's how I understand it, please correct me if I'm wrong.
You must flash the S-OFF BOOTLOADER for this to work.
You can use the RGB565Converter tool to flash your image successfully without needing to type commands.
Below is another method used to keep your phone from rebooting unexpectedly during the process:
joshw0000 said:
I tried using the "Flash Splash1" button that someone had posted earlier and I almost **** myself. I think my phone tried to load the file I originally used to root it. I was getting really nervous so I pulled the battery and, to my relief, it powered on and it booted normally. I'm sure that method works but I'm scared of it now.
I tried the original instructions and it rebooted my phone before I was ready so I did this in the command prompt (this was mentioned on the first page of posts):
cd C:\android-sdk-windows\tools
adb shell
su
reboot bootloader
fastboot flash splash1 <copy and paste file name here>
fastboot reboot
Of course this will only work if you've downloaded the program, converted your picture and placed it in the tools directory of SDK.
Worked great for me. I couldn't be happier!
Click to expand...
Click to collapse
didnt seem to work for me, but im not rooted, ill try this with my brothers rooted phone in a bit and repioret back
Wow that worked great! Thanks
Reboot phone into Fastboot (Power down, hold Send press and hold Power)
Click to expand...
Click to collapse
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
ch4sethe5un said:
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
Click to expand...
Click to collapse
no, Hold Call button and end button to get into fastboot
and this is ONLY FOR ROOTED PHONES
thanks
thanks i will try it out. Im using ivan's 0.7
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
ch4sethe5un said:
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
Click to expand...
Click to collapse
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
there should be an option to go to HBOOT menu and then into recovery and reboot from there.
I used this one:
Great tutorial. Thanks!
Here's mine if someone likes it they are free to use it.
+1 rep (if only we could do that). I was looking for something like this. Thanks!
t2noob said:
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
Click to expand...
Click to collapse
I did a battery pull myself too lazy to go into recovery from hboot. My phone did not explode after doing a battery pull so it "should" be safe however do so with caution.
moved thread by request of OP.
Best regards,
Flar
Ive learned that battery pull is the easyiest way,
As a fan of FFXIII, I could not pass up the opportunity to do this.
[Taking Requests also ]
Maybe we should come up with a thread so people can post all boot images and animations in one place, no?
Just remember to convert it like mentioned in the first post
Here is one(as a fan =] ):
Was just thinking about changing and found this. Thanks.
Awesome!!!
Thanks for the tutorial.
Worked great!
Not having custom recovery sure is frustrating, but we can still have all the fun other phones have!
{
"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"
}
Thanks to Android-Police for posting the flashable for me to grab the files from for this.
What is this?
It's a Windows script for flashing the 4.2 Camera+Gallery files through adb.
What are the requirements?
Be unlocked bootloader, with the insecured boot.img installed
You can find the unsecured boot.img to flash in my root thread, in the zip labeled as "razr_i_boot_insecured.img"
Code:
fastboot flash boot razr_i_boot_insecured.img
What works?
Taking pictures. Taking 720p and 1080p video.
Gallery*
What doesn't work?
Panorama.
Photosphere.
*Some functions in gallery force close.
Physical camera button for booting to camera from locked.
Will this remove my normal Camera+Gallery?
No, just adds another set.
Note: I removed the original Camera+Gallery (renamed to .bak the MotGallery2 and MotCamera apks in /system/app/ and see this as lockscreen, but the camera button doesn't launch it anymore, just takes pictures:
How do I go back to normal?
My Homemade fastboot thread, or an official FXZ from The Firmware Team.
Instructions:
Have unsecured boot.img installed (see above requirements).
Enable USB Debugging in Settings > Developer Options.
Plug in USB cable if you haven't already.
Double-click 'Install.bat' and let 'er rip!
Download:
Batakang
Enjoy!
Didn't work for me.
Device unlocked
Flashed 81.5.39002.Retail.en.EU - 4.0.4
Unsecure boot flashed (after a first try, in case off)
Running the script is unsuccessfull (hard to read but had the time to read "permission denied").
When I try manually "adb wait-for-device remount" give me "remount failed: operation not permitted".
Any idea ?
Le_Poilu said:
Didn't work for me.
Device unlocked
Flashed 81.5.39002.Retail.en.EU - 4.0.4
Unsecure boot flashed (after a first try, in case off)
Running the script is unsuccessfull (hard to read but had the time to read "permission denied").
When I try manually "adb wait-for-device remount" give me "remount failed: operation not permitted".
Any idea ?
Click to expand...
Click to collapse
You are using the secure boot.img. My Home-made flasher replaces the unsecure boot.img when its done rooting, as it says in my thread
Remount works only on the unsecured boot.img.
I PM u with a version that have photosphere working. There's any chance that, with this one, the photosphere starts working?
Another question: after upload the files, can I back the secure boot img?
ReeSilva said:
I PM u with a version that have photosphere working. There's any chance that, with this one, the photosphere starts working?
Another question: after upload the files, can I back the secure boot img?
Click to expand...
Click to collapse
That's the one I used, and it is indeed not fixed. You can flash the secure boot.img back after, the only reason for the unsecure is so we can use
Code:
adb remount
mattlgroff said:
You are using the secure boot.img. My Home-made flasher replaces the unsecure boot.img when its done rooting, as it says in my thread
Remount works only on the unsecured boot.img.
Click to expand...
Click to collapse
Ok, my bad, did miss the point
ReeSilva said:
I PM u with a version that have photosphere working. There's any chance that, with this one, the photosphere starts working?
Another question: after upload the files, can I back the secure boot img?
Click to expand...
Click to collapse
Photoshphere can be funny on this phone as theres no gyroscope
BOOTLOADER MUST BE UNLOCKED
DON'T TRY AND FAIL/BREAK YOU LOCKED DEVICE
Splash screens for Nokia 6.1 Plus
New screens will be added and updated by the contributors
{
"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"
}
More Previews
Download Splash
Instructions:
METHOD 1
via adb
unzip and place image file into platform-tools folder
reboot to fastboot
fastboot flash splash_a splash.img (replace splash.img with the respective img file name)
fastboot flash splash_b splash.img (replace splash.img with the respective img file name)
fastboot reboot
METHOD 2
via TWRP
Download zip
Unpack zip
1. boot to TWRP
2. Copy splash img
3. Select install
4. Select install image
5. Select splash.img
6. Select splash ( in partition box )
7. Swipe to flash
press home select reboot change slot repeat step 3-7
finally reboot system
tool used to work with img files by @GEEKiDoS
Contributors:
@D-Mi
@Sanju0205
@iamy7j
@joshclaudio
Amazing, Thanks
Is there a tutorial on how to make custom splash.img files for a given device? I want to modify the splash screen on my Nokia 7 Plus but can't find any tutorials or splash files.
thebob97x said:
Is there a tutorial on how to make custom splash.img files for a given device? I want to modify the splash screen on my Nokia 7 Plus but can't find any tutorials or splash files.
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/no...ol-splash2boot-logo-partition-editor-t3946992
Where splash screen image is stored?
Volski_ said:
Where splash screen image is stored?
Click to expand...
Click to collapse
It's located here - root/dev/block/by-name
But in case you need to extract run this commands in terminal emulator
su
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
@D-Mi The link for the tool is broken. Can you upload the tool or DM for me. Thanks in advance!
The25thMe said:
@D-Mi The link for the tool is broken. Can you upload the tool or DM for me. Thanks in advance!
Click to expand...
Click to collapse
Download tool here
can i also use a gif
D-Mi said:
Download tool here
Click to expand...
Click to collapse
Amazing work, can I use this to extract files from my splash.IMG of realme5 snapdragon chipset sir?
{Mod edit: Quotation fixed}
rockh3x said:
can i also use a gif
Click to expand...
Click to collapse
No splash.img is static part if you want to edit animation part of your phone's boot sequence you should change/edit bootanimation. Basically you can use any 30second video and turn it into a bootanimation.
Adamant12 said:
Amazing work, can I use this to extract files from my splash.IMG of realme5 snapdragon chipset sir?
{Mod edit: Quotation fixed}
Click to expand...
Click to collapse
I guess not these two phones have different resolution.