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
Related
I am stuck with my HTC Hero and I need help to find my way out of the maze.
I was having trouble with my RCMix v2.2 WWE instalation. I decided to flash a new ROM.
What I did:
I tried to boot into recovery but it didn't work. I believe recovery was damaged. I went to installed Rom Manager and tried to reinstall RA Recovery. When it was rebooting, phone got stuck in the first white screen.
Now that's where I am stuck:
Even though I try all the rebooting shortcuts, it doesn't load regular ROM and doesn't load recovery. It keeps showing the white screen with HTC logo and "quietly brilliant" slogan. And it starts it over and over.
If I try to go into recovery with power+home button it freezes in HTC logo on white screen, without looping and without showing "quietly brilliant" slogan.
My two options were:
1) Flash a recovery using ADB. It didn't work. I think that's because phone doesn't really goes to the point where the desktop software can reach it through debug mode. Doesn't know where to go from here. I go to Windows CMD line, in ADB folder and try to run "adb shelll". It shows me "Error: device not found".
2) Install a stock/shipped ROM. My hope was to start from a shipper rom and go from there all the way to rooting and flashing a custom ROM. The installation of a shipped ROM worked until the point where it checks the ID. Since I don't have a goldkey (and there is not way I can create one) it doesn't allow me to finish shipped ROM instalation. Is there an universal shipped ROM file which doesn't demand a specific ID or goldkey?
So... What do I do? Any one can give me a clue?
Thanks!
I've been trying to use ADB + Fastboot to install RA Recovery, as described here:
http://forum.xda-developers.com/showthread.php?t=561124
The problem is that the instructions below don't work:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.7.0.1.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell reboot
Click to expand...
Click to collapse
As you can see here:
{
"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"
}
What am I doing wrong? (I wish I could have asked in the related thread, but I was not allowed).
What's up, guys! I am proud to present you a bundle of one cool boot animation and one splash screen (the image that appears when you turn on your device) for your beloved HTC EVO 3D. Whether it is the GSM or CDMA variant, you will still be able to run them.
What is Maxell Audio?
Maxell Audio, as I want to call it, is a simple, yet inspiring and unique boot animation. Inspired by Maxell's well-known budget headphones, it manages to take your phone to another musical dimension. It carries the distinct green color found on the named headphones and also their outline. Combine them all and you will get something that was never seen before!
What about the splash screen?
The splash screen is the first thing you see when you turn on your phone. The old HTC logo has become quite boring, hasn't it? I'm sure it has, at least for me. To suit the Maxell Audio Boot Animation, I've come up with a custom splash screen, named Maxell Splash. The dominant color is black, with some green gradients. It's minimalistic, simple, elegant and the favorite amongst my testers.
Previews
Maxell Splash
{
"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"
}
Maxell Boot Animation
Installation
HERE, I'M SUPPOSING THAT YOU ARE FAMILIAR WITH FASTBOOT COMMANDS, ROOT AND ALL OTHER RELATED THINGS. IF YOU ARE NOT FAMILIAR WITH SOMETHING, PLEASE LEAVE THE TUTORIAL AND DO A RESEARCH FIRST. OTHERWISE, YOU ARE RISKING BRICKING YOUR DEVICE!!!
The installation is quite simple, actually. Just follow my steps and you should be good:
Extract the downloaded zip archive
Rename the boot animation to bootanimation.zip
Put it on your phone's SD Card
Using a root file manager, copy the animation to the following directory: /system/customize/resource
Overwrite your current boot animation
Reboot and enjoy!
And now for the splash screen
Extract the downloaded zip archive
Reboot your device into fastboot mode (bootloader)
In CMD, type the following fastboot command: fastboot flash splash1 splash1.img
In CMD, type: fastboot reboot
Enjoy!
Download
Feedback
Please share your feedback! I'm committed to improving this bundle in any way possible. Thank you for your patience!
I'll definitely be checking this out, thanks man!
TrashWang
Reply
icon69 said:
I'll definitely be checking this out, thanks man!
TrashWang
Click to expand...
Click to collapse
I am waiting for your feedback!:laugh:
*deleted*
*deleted*
*deleted*
Hi, i can't help you for now, but i have your same smartphone and i want to make a cwm recovery.
I've been rooted succesfully the phone and i made a cwm for this device, does anyone know how put the you25 in fastbootmode?
*deleted*
your help will be apprecciated,
the phone if of my girlfriend and now, after tryng to flash a cwm recovery built by the online builder,the you25 is still in bootloop.
Fortunately, I made a backup of the stock recovery and now i have to reflash it.
I need to know how put the phone in fastboot mode or eventually how reflash all the entire system, (before my girlfriend knows what i did:crying.
If you are interested, i made a cwm porting that works for 50%, you can backup and restore all entire system; then i tried the online builder to make it 100% working but with no success.
*deleted*
*deleted*
No, i can't access adb, i need to put it in fastbootmode by pressing at startup a sequence of buttons. (Es, power+vol down or whatever else for this devise).
Now i see the android logo only plugyng the power cable, it still appears for about 3-4 seconds, then the backlight of the three buttom buttons lights on and then the device reboots.
Initially, I flashed the recovery by adb, after rooted the mobile and mounted the filesystem in r/W mode with:
Code:
dd if=/sdcard/recovery.img of=/dev/blocks/mtdblocks10
.
You can find the right number by typing in adb shell:
Code:
cat /proc/partitions/
I have experience with other device, generally you can flash with adb, fastboot and by download mode, if the device boots you can always fix it, but you need the right tools.
*deleted*
mgbrain said:
what happens when you boot the device by normal start, does it also go into the 3-4 seconds bootloop or does it get stuck on the android logo?
i had my device stuck there already too but i was still able to access adb.
Click to expand...
Click to collapse
The device starts only if i plug the power cable, after 5-6 second the android logo shows up and then after 4 seconds the device reboots.
Adb doesn't work for me, but if you have adb working i think i can help you.
What is the last think you made to the device before beeing stock on the boot?
*deleted*
Thank you, but that doesn't work for me.
What about jtag? i have experience with decoders but nothing about smartphones.
Reading about how restore nexian a850, i founded that is possible to reflash the you25 with the sprocoom tool and the same driver of the nexian a850. Unfortunately I do not have the firmware for the you 25. Has anyone it, please?
I think that it is possible to flash the device using the img files that i created before and a prebootloader.
I have also to edit a file with a list of all partitions with their address in hex format.
Unfortunately i do not know these values, and i cannot see them from my device because it doesn't work. can anyone help me, please?
here is a list of all partitions:
{
"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"
}
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
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.