Database Develop

[Tutorial] How to install Android Loliipop+Root

Note:​I'm going to assume you have the Fastboot and ADB Drivers installed and the boot loader is unlocked! ​
Why is this here?
This thread is made to help new users install the developers preview through what I think is the fastest way and safest way too through the command prompt on Windows.
Responsibility!
If your device becomes bricked, makes toast for you, and anything else I did not mention its simply not my fault since you took it upon your self to do this method.​
Credits!​​Thanks Google for this lovely Operating System. Thank you Chain Fire for providing this method to root Android Lollipop and for your app and boot.img too! Thanks to LG for manufacturing this great device to use and enjoy stock Android. Finally, big thanks to TWRP for providing us with this recovery!​​​​​
The Steps!​​​​​Step 1: Download the Lollipop preview HERE, extract it and open the folder with all the image files along with the radio and bootloader image too.
Step 2: Drop all the images to your folder that contains the ADB and Fastboot files
Step 3: Open the folder that contains the ADB and Fastboot files
Step 4: Hold the shift key and right click and click "Open command window here"
Caution! Make sure you back up everything before you begin the process if not its not my fault you forgot to back up.
Step 5: Make sure your device is in fastboot and connected. We are going to replace the boot loader for a newer one. Please make sure the boot loader image name first before we began because i'm just going to use boot loader as a example the real file name will be different. Type the command shown below.
Code:
fastboot flash bootloader bootloader.img
Step 6: Now we are going to flash the Radio as also stated above be sure to check the image name before we flash.
Code:
fastboot flash radio radio.img
Step 7: Now we are going to flash userdata. This part you don't have to worry about the file name you can just copy and paste the command but, I would double check.
Code:
fastboot flash userdata userdata.img
Step 8: Now going to flash boot or the kernel just as step 8 and here from out I will let you know when you have to worry about the file name again.
Code:
fastboot flash boot boot.img
Step 9: Now were flashing the system files.
Code:
fastboot flash system system.img
Step 10: Now were flashing the a custom recovery (twrp for this example) so we can install the SuperSU files later. You can get the recovery image HERE and rename it "Trecovery" and place it to the same folder. After flashing it go to the recovery and from there reboot it.
Code:
fastboot flash recovery Trecovey.img
Yay! We got Android Lollipop now we have to root it.​​​​​Step 1: Let Andriod Lollipop boot up and go download SuperSu on your device by going to Chainfire SuperSU thread and click on his installable zip link and download SuperSU 2.14 or above. On your computer download his modified boot image HERE and rename it Rboot.img and move it your folder where the ADB and Fastboot files are.
Step 2: On your computer go to fastboot again on your phone and type the code in below.
Code:
fastboot flash boot Rboot.img
Step 3: Go to recovery and install the SuperSU zip as usual, reboot, and that's it. Enjoy!

reserved

Trecovery.img

Thanks for your work. Unfortunately, we already have a sticky thread on flashing images and rooting: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
The method to flash and root lollipop is no different than any other version.
Because we don't want multiple threads with the some information I will close this thread
Thanks.

[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2 & Redmi 3

Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi 2/2S Prime or Redmi 3/3S/3X/Pro Only..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Redmi 2/2S Prime or Redmi 3/3S/3X/Pro (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
1. Download & Extract this in computer: Redmi_2,3_Splash_Maker.zip
2. Make sure you have a 720x1280 resolution picture.
3. Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
(Similarly you can also change fastboot.png if you wish to change the picture of fastboot)
4. Finally, run the 'Create_Logo.bat' to create splash.img , which you can find inside the "output" folder.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. @GokulNC (myself ) who wrote this script
(This one is just a copy from my thread here: [GUIDE] How to Create Custom Splash Screen for Lenovo A6000)
2. @kumajaya for the stock splash.img of Redmi 2
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..

very nice you came up with some output. i tried lots of things but zero success.
BTW I made something here for myself in ms paint
Get those images from attachments below. Believe me, it looks awesome.
Also, it will be good if you add adb shell guide too for flashing with dd

Wow, I was really looking forward to this thing!!!
Guys, I have a request if this has been tested by you to be working, can you please port the awesome batman bootlogo here, over at http://forum.xda-developers.com/android/themes/bootlogo-awesome-batman-bootlogo-t3264750
.
Maybe you can also edit the image to contain a small MI logo (only for people who want it, not me xD) .
.
Hope this can be achieved - I'd be dammed

shanx_verma said:
Wow, I was really looking forward to this thing!!!
Guys, I have a request if this has been tested by you to be working, can you please port the awesome batman bootlogo here, over at http://forum.xda-developers.com/android/themes/bootlogo-awesome-batman-bootlogo-t3264750
.
Maybe you can also edit the image to contain a small MI logo (only for people who want it, not me xD) .
.
Hope this can be achieved - I'd be dammed [emoji14]
Click to expand...
Click to collapse
I'll try tommorow.
Sent from my 2014818 using Tapatalk

#NoobPremium
noobpremium said:
I'll try tommorow.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Thank You !!!
*thanks button not working somehow :? *
EDIT -
In the same splash (set), maybe you can choose one of these to make the fastboot splash -
.
http://androidwalls.org/wp-content/...0-batman_the_dark_knight_black_background.jpg
.
http://m.androidwallpapercentral.com/downloads/BatmanSilhouetteAndroidLogo.jpg
.
http://wallpapersonthe.net/11662-the-dark-knight-joker-batman-anime-dark/
.
http://www.hdgalaxyalphawallpaper.com/wp-content/uploads/Movie/Batman Galaxy Alpha Wallpapers.jpg
.
http://www.hdgalaxyalphawallpaper.c...Movie/Batman Dark Galaxy Alpha Wallpapers.jpg
*I know, too many choices* *batman love *

Here are some minimal superhero logos for you all!
Thank you @GokulNC for this guide.

Can you please also include in the OP the terminal command to backup stock one while in the OS?

shanx_verma said:
Can you please also include in the OP the terminal command to backup stock one while in the OS?
Click to expand...
Click to collapse
He has given stock images with the tool itself. Have a look at it.
Otherwise if you want some thrill (xD)
Here's command for you:
Run as superuser.*(I assume you know it)
Code:
dd if=/dev/block/bootdevice/splash of=/sdcard/splash.img
Sent from my 2014818 using Tapatalk

- DELETED -

New BatBootLogo
This is what I created... How you like it.
Fully compatible with 2014818.

Gonna make a "Theft chance reducer" splash
Thanks
Maybe a Self-destruction message on the fastboot wold be nice :v

!
Lennoard said:
Gonna make a "Theft chance reducer" splash
Thanks
Maybe a Self-destruction message on the fastboot wold be nice :v
Click to expand...
Click to collapse
Perfectt!!!
Do share here!

@shanx_verma
This is my antitheft image :v
I hope it is useful to avoid stock firmware reset in case of a theft (Yeah, this happens a lot here, thieves are getting smart)
So it is basically a super joke
The first picture tells who owns it, address, email and phone (in case of a simple loss), it indicates that the GPS is on and working (fake :v) and displays a warning that the device is monitored.
Second one is the best

I get an error in terminal part.
Its says :
dd: unknown operand to
Anyone got this error too ?

MRAT47 said:
I get an error in terminal part.
Its says :
dd: unknown operand to
Anyone got this error too ?
Click to expand...
Click to collapse
What device is it?
Redmi 2 or 3?
It's not yet tested in Redmi 3, but working perfectly in Redmi 2..

GokulNC said:
What device is it?
Redmi 2 or 3?
It's not yet tested in Redmi 3, but working perfectly in Redmi 2
Click to expand...
Click to collapse
Redmi 2

Thanks, it works great!! How do we change the charging animation when switched off and plugged in to a charger?

MRAT47 said:
Redmi 2
Click to expand...
Click to collapse
Enter the command properly with proper file name & path..
It's working cool with other users..
Name_Hidden said:
Thanks, it works great!! How do we change the charging animation when switched off and plugged in to a charger?
Click to expand...
Click to collapse
It's in the kernel I guess.
Nothing to do with splash.img ..
That might also be cached in /res/images as a read-only file, just for you to see what it is

Sir, how to flash fastboot splash? Is it has the same way with "how to flash boot splash"? Or not.! Please show me the code!!

Dyt199412syam said:
Sir, how to flash fastboot splash? Is it has the same way with "how to flash boot splash"? Or not.! Please show me the code!!
Click to expand...
Click to collapse
Code:
fastboot flash splash splash.img
Sent from my 2014818 using Tapatalk

axon7tool: Flash and backup boot/recovery using EDL mode

Note: This is an inherently dangerous tool. I have made every effort to make it as safe as possible. But there is always a risk of bricking your device. You assume all responsibility for the consequences. Proceed with caution.
Warning: To avoid bricking your device, NEVER write both boot and recovery in one session. ALWAYS write one partition, test, then write the other. This is why the tool will only write one partition at a time.
Warning: There are versions of TWRP for the Axon 7 that are known to erase your IMEI when doing a restore. Do NOT do a TWRP restore unless your are SURE that you have a good version of TWRP!
This tool will allow you to:
Backup your boot and recovery partitions.
Flash a boot or recovery image (including the signed TWRP image).
See following posts for operating system specific setup instructions.
Once your setup is complete, enter EDL mode:
1. Power off phone.
2. Hold both volume buttons.
3. Plug phone into computer.
4. For G models, you must "adb reboot edl" (see other threads).
Usage:
axon7tool <mode> <partition(s)>
Note: The tool name will vary depending on your operating system.
<mode> is -r for read, -w for write.
For read mode, <partition> is one or more of gpt, boot, recovery. Files will be created as <partition>-backup.bin
For write mode, <partition> is boot or recovery. File will be read from <partition>.bin
Examples:
To backup everything on Linux:
./axon7tool-1.5-linux -r gpt boot recovery
To write recovery on Win64:
Place file as recovery.bin
axon7tool-1.5-win64 -w recovery
Links to axon7tool:
axon7tool-1.5-linux (main)
axon7tool-1.5-linux (alternate)
axon7tool-1.5-win64.exe (main)
axon7tool-1.5-win64.exe (alternate)
Link to signed TWRP removed.
FAQ:
Q: Can you provide a signed boot image with root?
A: No. I do not have the ZTE signing key, and tenfar's images are not current.
Q: Can I have the source code for the tool?
A: No.
Q: Can you provide the programmer?
A: No.
Q: Do you accept donations?
A: No, all work is provided freely for community use.

Setup instructions for Linux:
1. Ensure your login user is in the "plugdev" group.
$ id
You should see plugdev in the list. If not, add yourself to the group and logout/login to take effect.
2. Ensure your udev rules are setup.
Create a file eg. /etc/udev/rules.d/qcom.rules that contains:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev"
3. All done!

Setup instructions for Win64:
1. Download zadig from http://zadig.akeo.ie/
2. Put device in EDL mode.
3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.
4. All done!

Reserved for Mac instructions.

Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?

kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1- No this doesn't work like backing up with TWRP, This tool is more powerful than Custom Recovery (TWRP), and you should be very careful on how to use it.
Like @tennear mention about try first by using -r (read) then just flash the sign TWRP.
I personally recommend just flash TWRP and DON'T mess with Boot image.
2- the Sign TWRP is not provided by ZTE, ZTE will NEVER release a Custom Recovery for us users.

kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1. The tool writes the raw partitions to your PC. Whatever you have in the partition is written out, whether it is stock recovery or TWRP or whatever.
2. The signed TWRP image is copied from the zip that tenfar provided in his post. I did not create it, and I cannot create signed images.

Forgive me my noobiness, but here’s a step-by-step-instruction list. Am I thinking right? I want to minimise the risk when I try your tool tomorrow.
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan

@Controllerboy close, but not quite. I'll attempt to provide detailed feedback on your step by step list tomorrow. Time for sleep now.

Controllerboy said:
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Click to expand...
Click to collapse
None of these steps should be necessary.
Controllerboy said:
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Click to expand...
Click to collapse
I believe you just run zadig, I don't remember an installer.
Controllerboy said:
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Click to expand...
Click to collapse
Renaming the tool is optional.
Controllerboy said:
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Click to expand...
Click to collapse
The tool is "one shot". You can read any combination of gpt, boot, and recovery in one session, then the tool will restart the phone.
Controllerboy said:
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Click to expand...
Click to collapse
Yes, this is correct.
Controllerboy said:
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Click to expand...
Click to collapse
Yes, this is correct. Writing boot or recovery takes about 30 seconds. Then the tool will reboot your phone. Be sure to hold the Vol+Up button to reboot into recovery.
Controllerboy said:
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Click to expand...
Click to collapse
Everything past step 20 is up to you.
Controllerboy said:
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
Click to expand...
Click to collapse
You cannot unzip an img file.
The TWRP image provided is just as tenfar provided for 2017u users. You only need to rename it to recovery.img for using the tool.
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.

Folks who are able to use this new tool/method successfully, please report back with your variant. I can't test this myself, so I'm relying on some verification before I update the newbie guide to point here instead of tenfar's thread (which is outdated and no longer updated as tenfar is now inactive).

tennear said:
<-- SNIP -->
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Click to expand...
Click to collapse
I found this on the 65th page of Tenfar's thread (http://forum.xda-developers.com/showpost.php?p=69215285&postcount=642)
khaino said:
Step 1: Download the zip file and extract to your local disk. a2017 for Chinese model,and a2017u for US model,a2017g for HK & EU model
a2017u :B20_blunlockedhttp://d-h.st/KaaQ
a2017u B20 http://d-h.st/LqR5 (modified from @rczrider�s backup real stock b20 boot.img)
a2017u B27 http://d-h.st/kRgq
a2017 B06:http://d-h.st/ztXw
a2017 B07:http://d-h.st/VVlf
a2017 B08: http://d-h.st/bT6r
a2017 B09:http://d-h.st/sBjo
a2017 B10:http://d-h.st/cBOE(wifi not working) http://d-h.st/aceq (from official update.zip)
a2017g B02 :http://d-h.st/aPiC
a2017g B03:http://d-h.st/r3Z4
TWRP recovery 3.0.2-2 : http://d-h.st/dgWW
latest tools:http://d-h.st/Ienb with dump function
Click to expand...
Click to collapse
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...

Controllerboy said:
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Click to expand...
Click to collapse
That is correct.
d-h.st seems to be down for the past few days. I guess it will come back at some point, and you can download the zip file to extract the recovery image. Or maybe someone else has a copy of it...

@tennear
As far as u know TWRP is the same for every A7, sign or not.

DrakenFX said:
@tennear
As far as u know TWRP is the same for every A7, sign or not.
Click to expand...
Click to collapse
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.

tennear said:
Reserved for Mac instructions.
Click to expand...
Click to collapse
So can the Linux tool be used on Mac?

nuserame said:
So can the Linux tool be used on Mac?
Click to expand...
Click to collapse
No. I have not built the tool on Mac yet. I will try to do that soon.

I wouldnt say I was a newbie but how do you get the file to run. Even with Antivrus off, the computer just wont run it.
Thank you for the time and support.

The .exe file isn't meant to be ran on it's own. Double-clicking it won't do a thing. You need to use cmd (command) to execute commands to the file. If you look at my post on the first page of this thread, you'll get an idea of how the process works. But please don't follow my post as of now, since it's not detailed nor 100% correct yet.
It's my intention to try my luck tomorrow and I'll post a detailed and 100% correct step-by-step-process.

Excuse me for my ignorance, but how does this tool differ from tenfars tool? Beside not being able to write two partitions at the same time that is.
TIA,
Cheerz,
/Cacti

[GUIDE] How to Change Boot Logo (Splash Screen) of LeEco Le 2 / Le S3

Note:
This is not bootanimation, this is the splash screen (the 'LeEco' boot logo which is displayed when device is switched ON)
This is for LeEco Le 2 / S3 Snapdragon variants Only, like X522/S3 (USA), X520 (Chinese), X526 (Indian), and X527 (International)..
For Mediatek variants, check Post #2..
For other devices, please send me your splash.img so that I can create a tool for you too..
Requirements:
1. Rooted LeEco Le 2 / S3 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: LeEco_Le2_Splash_Maker.zip
2. Make sure you have 4 pictures (same or different) in 1080x1920 px resolution in PNG format.
(It seems Le2 displays any 1 picture from the 4 pictures randomly while switching ON, so I think you'll have to use 4 pictures)
3. Now rename your 4 pictures as logo1.png, logo2.png, logo3.png, logo4.png & replace it inside "pics" folder of the extracted folder.
(Similarly you can replace other pictures in it carefully if you wish)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
If some pictures are jumbled or do not appear, check this trick here: https://forum.xda-developers.com/showpost.php?p=71454608&postcount=18
(Or send me your stock splash.img)
Thanks to @Achyuth Reddy who provided the stock splash.img of Le 2 X526 ..
Hit the Thanks :good: button if it worked for you
You're welcome to share the splash images that you created

For Le 2 Mediatek Variants
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..

Thanks.. Gone try it.. :laugh:

worked fine for me, but couldn't flash it in bootloader mode (had to flash the zip file in twrp). Thanks!

it didn't work properly for me.... the images were not centered and also it got jumbled.... any fix?

Is there any known limitation in image size (not resolution)?
Samples are about 200kb at maximum, what about 500 kb?
update: ok it works with files up to 500kb.
update2: just for demo, btw it's a x527...

JamBax said:
update2: just for demo, btw it's a x527...
Click to expand...
Click to collapse
Hi, can you share this splash Image ?
I have x527 and i like it. :good:
Thanks.

marco-ko said:
Hi, can you share this splash Image ?
I have x527 and i like it. :good:
Thanks.
Click to expand...
Click to collapse
I can and I will do
But I'll have to recreate that one, because I made another one already.
Guess it will be online tomorrow, not to say 'soon'
btw. if anyone knows where to find that android font, that would be great :good:

marco-ko said:
Hi, can you share this splash Image ?
I have x527 and i like it. :good:
Thanks.
Click to expand...
Click to collapse
I uploaded the files to mega (this is first version). (link removed)
sometimes the images seem to be out of order, for example fastboot and recovery are exchanged
Maybe @GokulNC knows why this happens??

JamBax said:
I uploaded the files to mega (this is first version).
sometimes the images seem to be out of order, for example fastboot and recovery are exchanged
Maybe @GokulNC knows why this happens??
Click to expand...
Click to collapse
Thanks JamBax but when i try to open the link to Mega it asks to enter the "Decryption key"
Please verify it.
Can You share also the newest splash You made (if they are for X527)?

marco-ko said:
Thanks JamBax but when i try to open the link to Mega it asks to enter the "Decryption key"
Please verify it.
Can You share also the newest splash You made (if they are for X527)?
Click to expand...
Click to collapse
Sorry for that, try this link
the other one will be in the same folder (V2 of course).

JamBax said:
Sorry for that, try this link
the other one will be in the same folder (V2 of course).
Click to expand...
Click to collapse
Ok i downloads it.
In the folder there is V1 and V1a.....Not V2
Is V1a that You mean V2?

marco-ko said:
Ok i downloads it.
In the folder there is V1 and V1a.....Not V2
Is V1a that You mean V2?
Click to expand...
Click to collapse
V1 is original order which is mixed up at my device,
V1a is mixed up, but shows correct on my device
V2 will be there when it's ready, I'm working on it... :angel:
btw, V2 will be named V2

@marco-ko V2 is online

JamBax said:
@marco-ko V2 is online
Click to expand...
Click to collapse
Thanks :good: :good:

Have anyone tried this X526 splash.img on X520?
Because I have X520 (Chinese version) and I want to see only english text when my phone is booting.

umarbest said:
Because I have X520 (Chinese version) and I want to see only english text when my phone is booting.
Click to expand...
Click to collapse
You can try it yourself :good: the original splash.img is inside the stock rocm archive.
Size should be equal.
Only the cpu (snapdragon) is important.

For all those having issues with the incorrect images appearing.
What worked for me was changing the order the images are processed in CREATE_LOGO.bat, I simply moved logo4 to the bottom of the list.
How to:
Using a text editor to modify CREATE_LOGO.bat
Change:
Code:
set pic4_path="not_found"
if exist "pics\logo4.png" set pic4_path="pics\logo4.png"
if exist "pics\logo4.jpg" set pic4_path="pics\logo4.jpg"
if exist "pics\logo4.jpeg" set pic4_path="pics\logo4.jpeg"
if exist "pics\logo4.bmp" set pic4_path="pics\logo4.bmp"
if exist "pics\logo4.gif" set pic4_path="pics\logo4.gif"
if %pic4_path%=="not_found" echo.logo4.png or logo4.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic5_path="not_found"
if exist "pics\fastboot.png" set pic5_path="pics\fastboot.png"
if exist "pics\fastboot.jpg" set pic5_path="pics\fastboot.jpg"
if exist "pics\fastboot.jpeg" set pic5_path="pics\fastboot.jpeg"
if exist "pics\fastboot.bmp" set pic5_path="pics\fastboot.bmp"
if exist "pics\fastboot.gif" set pic5_path="pics\fastboot.gif"
if %pic5_path%=="not_found" echo.fastboot.png or fastboot.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic6_path="not_found"
if exist "pics\recovery.png" set pic6_path="pics\recovery.png"
if exist "pics\recovery.jpg" set pic6_path="pics\recovery.jpg"
if exist "pics\recovery.jpeg" set pic6_path="pics\recovery.jpeg"
if exist "pics\recovery.bmp" set pic6_path="pics\recovery.bmp"
if exist "pics\recovery.gif" set pic6_path="pics\recovery.gif"
if %pic6_path%=="not_found" echo.recovery.png or recovery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic7_path="not_found"
if exist "pics\battery.png" set pic7_path="pics\battery.png"
if exist "pics\battery.jpg" set pic7_path="pics\battery.jpg"
if exist "pics\battery.jpeg" set pic7_path="pics\battery.jpeg"
if exist "pics\battery.bmp" set pic7_path="pics\battery.bmp"
if exist "pics\battery.gif" set pic7_path="pics\battery.gif"
if %pic7_path%=="not_found" echo.battery.png or battery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
To:
Code:
set pic4_path="not_found"
if exist "pics\fastboot.png" set pic4_path="pics\fastboot.png"
if exist "pics\fastboot.jpg" set pic4_path="pics\fastboot.jpg"
if exist "pics\fastboot.jpeg" set pic4_path="pics\fastboot.jpeg"
if exist "pics\fastboot.bmp" set pic4_path="pics\fastboot.bmp"
if exist "pics\fastboot.gif" set pic4_path="pics\fastboot.gif"
if %pic4_path%=="not_found" echo.fastboot.png or fastboot.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic5_path="not_found"
if exist "pics\recovery.png" set pic5_path="pics\recovery.png"
if exist "pics\recovery.jpg" set pic5_path="pics\recovery.jpg"
if exist "pics\recovery.jpeg" set pic5_path="pics\recovery.jpeg"
if exist "pics\recovery.bmp" set pic5_path="pics\recovery.bmp"
if exist "pics\recovery.gif" set pic5_path="pics\recovery.gif"
if %pic5_path%=="not_found" echo.recovery.png or recovery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic6_path="not_found"
if exist "pics\battery.png" set pic6_path="pics\battery.png"
if exist "pics\battery.jpg" set pic6_path="pics\battery.jpg"
if exist "pics\battery.jpeg" set pic6_path="pics\battery.jpeg"
if exist "pics\battery.bmp" set pic6_path="pics\battery.bmp"
if exist "pics\battery.gif" set pic6_path="pics\battery.gif"
if %pic6_path%=="not_found" echo.battery.png or battery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic7_path="not_found"
if exist "pics\logo4.png" set pic7_path="pics\logo4.png"
if exist "pics\logo4.jpg" set pic7_path="pics\logo4.jpg"
if exist "pics\logo4.jpeg" set pic7_path="pics\logo4.jpeg"
if exist "pics\logo4.bmp" set pic7_path="pics\logo4.bmp"
if exist "pics\logo4.gif" set pic7_path="pics\logo4.gif"
if %pic7_path%=="not_found" echo.logo4.png or logo4.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
On my Le x522 I can verify logo1-3, recovery, fastboot, and battery were displayed correctly while logo4 never made an appearance..

JamBax said:
You can try it yourself :good: the original splash.img is inside the stock rocm archive.
Size should be equal.
Only the cpu (snapdragon) is important.
Click to expand...
Click to collapse
Hi guys,
Link was removed ?
where I can to download IMG for X527_english_SplashScreen ?

Which link, which img?
This thread is about how to create your own img (or zip if you like better).

[GUIDE][Coolpad Cool1 Dual] How to Change Boot Logo (Splash Screen)

Note:
This is not bootanimation, this is the splash screen (the 'Coolpad' boot logo which is displayed when device is switched ON)
This is for Coolpad Cool1 Dual Snapdragon variants Only..
For other devices, please send me your splash.img so that I can create a tool for you too..
Requirements:
1. Rooted Coolpad Cool1 Dual (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: Coolpad_Cool1_Dual_Splash_Maker.zip
2. Make sure you have 4 pictures (same or different) in 1080x1920 px resolution in PNG format.
(It seems Coolpad displays any 1 picture from the 4 pictures randomly while switching ON, so I think you'll have to use 4 pictures)
3. Now rename your 4 pictures as logo1.png, logo2.png, logo3.png, logo4.png & replace it inside "pics" folder of the extracted folder.
(Similarly you can replace other pictures in it carefully if you wish)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Thanks to @Vikasspattel who provided the stock splash.img of Coolpad Cool 1 Dual ..
2. This is just a modified version of my tool here: [GUIDE] How to Change Boot Logo (Splash Screen) of LeEco Le 2 / Le S3
Hit the Thanks :good: button if it worked for you
You're welcome to share the splash images that you created

Thank You sir for reading my comment and helped by your quick effort ,
well i had no hope but thank you so much

hi
i installed custom recovery to cool 1 c 103
after it finished model number changed to 106
what i have to do?????