Simple default splash without annoying useless note about unlocked bootloader.
Also Pie firmware include splash with incorrect proportions, it's vertically stretched. But this is with normal dimensions. Made by this utility.
UPD: reulploaded, fixed missing fastboot logo (mi-bunny).
Just flash attached ZIP via custom recovery. Remember, that installing MIUI update or new firmware may overwrite bootlogo.
Also attached default logo if you want to revert.
BTW check stylised "Redmi Note 5" logo
thx for sharing
Related
This isn't a double post; other resolved posts are too specific.
I have an IdeaUSA CT702, commonly referred to as an A777. It's rooted and I think the bootloader is unlocked (can't tell because one of my last posts wasn't answered: Fastboot Devices = ?).
The problem:
I recently modified my build.prop and replaced it with some corrupted one that I found online to allow for more compatibility (ie. Gameloft Apps). After restarting my tablet, the splash showed, finished loading, but didn't continue on to show the "android" boot logo. I then restarts after some point in time. The black screen that it stops on is fastboot mode (my fastboot is just a black screen for some reason. It always was. What should I flash? My original build.prop is attached in a zip file.
I also ripped my boot.img and recovery.img (I don't have CWM rocovery, there is no compatible one) earlier just for no reason. I don't have a nandroid backup, and I didn't rip the system.img. I can boot into recovery and fastboot, just not normal boot, so perhaps we could flash an update.zip? I also tried using UniFlash 1.2 and the build.prop editor but for some reason it always reverts back to the corrupted version when I restart the program. Why is this?
I unlocked bootloader of my MOTO G Dual sim India version 1st gen today. It was showing me annoying warning whenever I boot. So, I decided to follow this thread - http://forum.xda-developers.com/showpost.php?p=47971145&postcount=1 and flashed the zip.
But, However it made the conditiong worse. Now whenever I boot It shows me some really courrpted image. I want to get my original BOOT logo back. Please guide me. If that's not possible, then I would like something nice as Boot logo instead of a corrupt image.
maxviwe said:
I unlocked bootloader of my MOTO G Dual sim India version 1st gen today. It was showing me annoying warning whenever I boot. So, I decided to follow this thread - http://forum.xda-developers.com/showpost.php?p=47971145&postcount=1 and flashed the zip.
But, However it made the conditiong worse. Now whenever I boot It shows me some really courrpted image. I want to get my original BOOT logo back. Please guide me. If that's not possible, then I would like something nice as Boot logo instead of a corrupt image.
Click to expand...
Click to collapse
Unzip the .zip file and flash the logo.bin file, this will fix it.
Hi Everyone,
Im using XT1550 and installed CM-12.1 from the official snapshot type ( download.cyanogenmod.org/?device=osprey) and its been working okay.
I wanted to build my own and so followed steps at Build_for_osprey wiki page to build a ROM (No changes, just copied steps from there) and tried to install it. Once I get into TWRP and flash the zip file, it comes back to the "Warning Bootloader unlocked" motorola white screen, vibrates for sometime and then is stuck at that screen. It then switches off and loops again to the same screen after about 30 secs. The same thing continues. I can meanwhile boot into recovery and install the official ROM and get back to a working phone, but not sure why the loop is happening.
Here are the differences from the official one and the one I built.
1. The system.new.dat from official CM website is of size 492412928 whereas the one I built is of size 427536384. But funnily, when I use sdat2img.py to extract the dat file as an image, the file sizes of the image file are the same (2432696320). I'm not sure why the sizes of the 2 ROM are so different.
2. Everything else is the same.
The one thing I changed during building was to use Oracle JDK instead of OpenJDK by changing the build/core/main.mk from requires_openjdk := true to false so that I can get past that stage.
Are there any pointers on how to debug this? Is there any way of looking at logs to find out why the one I built may result in a loop?
Thanks in advance
Raja
I have installed a custom theme onto my twrp which blocked my 3.10 twrp so that its stuck on the splash screen , I downgraded to 2.8.7.0 but the theme is there but its missing the slider buttons so doing anything is impossible, also switching themes is impossible since the slider isnt rendering for some odd reason.
Is this possible to recover from, if so how lol? i can enter download mode but when it boots up "normally" it doesn't display the splash screen and boot loops.
(i changed the splash screen and i'm assuming i did something wrong and now it breaks when loading it?)
Also i am unable to boot into recovery, just ignores it and continues bootlooping
nvm fixed it, just reflashed with stock firmware