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 Xiaomi Mi 5(, 5s, 5s Plus) & Mi Max/Mix Only (Snapdragon Variants)..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Mi 5 or Mi 5s / 5s Plus or Mi Max or Mi Mix (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
Seems this tool won't work anymore for the latest updated firmware.
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: Splash_Logo_Maker.zip
2. Make sure you have a picture with resolution equal to your device resolution (for example, 1080x1920px for Mi5) or lesser.
Note:
In fact, you don't need 1080x1920 picture, you can even have a picture with any resolution lower than device resolution, which will automatically be centered while booting.
For example, here's the stock splash with resolution 161x321: Click Here
3. Now rename your picture as logo.png or logo.jpg (according to the format) & replace it inside "pics" folder of the extracted folder.
(Or you can also directly edit the picture inside)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , 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 to install:
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.
Note:
For Mi 5 upgraded to Android 7 (Nougat) firmware, if this tool doesn't work, try this tool here by @Cynob:
Mi 5 (Nougat) Logo Maker
Credits:
1. @GokulNC (myself ) who wrote this script
2. Based on logo_gen.py script
Hit the Thanks :good: button if it worked for you
You're welcome to share here the custom splash screens that you made, since others may find it useful
Thanks, was looking for this, trying to figure it out from the similar instructions from Redmi.
Thank you for this beatiful script!
I've made a custom splash screen which looks in my opinion really nice, so I would like to share it. You can find it in my attachements, Thanks!
Thank you man, this is my boot splash image
Thank you so much!! :good:
This is my splash image
Can someone create a Splash Screen with the image attached? The Script does not work on my Computer
33bca said:
Can someone create a Splash Screen with the image attached? The Script does not work on my Computer
Click to expand...
Click to collapse
Wow man it looks very awesome i will create the splash screen in some hour for you if nobody help you.But Can you create an image that makes more sense with xiaomi for me? Please, if you have time obviously
Argenis_jbc said:
Wow man it looks very awesome i will create the splash screen in some hour for you if nobody help you.But Can you create an image that makes more sense with xiaomi for me? Please, if you have time obviously
Click to expand...
Click to collapse
i can do one tomorrow, if i have the time for it.
there you go!
Argenis_jbc said:
there you go!
Click to expand...
Click to collapse
Thanks mate :highfive:
In the attachements you can see another logo, i just used the Unity 5 logo, so basicly no big work behind it. On the Second Splash Screen, i've created a mosaic like five ans placed it instead of the 5 logo.
I hope you like it.
Note: @ work, I only have paint.net...
Didn't worked for me unfortunately
Unlocked and rooted on latest global stable miui 8.
dd in terminal emulator went just fine.
After reboot, stock splash screen is still displayed.
Any idea what am I doing wrong?
Here is one I did for the Mi 4c http://forum.xda-developers.com/showpost.php?p=68648359&postcount=14
Seems cool, but RIP warranty
Thank you for your work.
just a few hours ago: ... searching the net for "convert rgb565 to rgb888" and trying to figure out a way to open the .img file with the boot logo image and do some personal tuning.
and then, Taà Daà! one pensiero* hit me, go check the friends at the XDA community!
* pensiero (italiano) = thought (english)
Borbingo Boy said:
Seems cool, but RIP warranty
Click to expand...
Click to collapse
What do you intend?
Fantastic. Thank you!
Will keep having a look here, interested in seeing what you guys come up with!
ain_gt said:
Thank you so much!! :good:
This is my splash image
Click to expand...
Click to collapse
nice sir, can you please provide it in .img format also?
Creepy splash screen (homage to H. R. Giger)
This is my first attempt at this "game".
The title of the image used for this splash screen is Bio-Mechanical Landscape I by Hans Rudolf "Ruedi" Giger.
Burs said:
Didn't worked for me unfortunately
Unlocked and rooted on latest global stable miui 8.
dd in terminal emulator went just fine.
After reboot, stock splash screen is still displayed.
Any idea what am I doing wrong?
Click to expand...
Click to collapse
Same for me, dont work, flash its Ok but still stock boot splash screen.
Small Image to try & trial & test
@fabioplata @Burs
Sometimes the script does not work depending on the specific environment where it is operating (the user computer), mainly is Python related.
Do you have it installed? wich version? Your Python is mission critical for your workflow / lifeflow? ...do you want to hunt down the problem?
My suggestion is: go with a virtual machine, a small one; bring it up for the work and then puff! close it when done. A fresh virtual machine is a blank slate so no mismatches between different/similia pieces of code.
If the problem is in the outcome and the delivery/deployment...
Did you try the 3 methods to accomplish this task?
Personally my preferenza goes to the flashable zip via twrp. ... and a "Dalvik" if there is time
For your testing in attach is available a small image: both versions, all 3 methods. Hope helps.
glogal said:
Sometimes the script does not work depending on the specific environment where it is operating (the user computer), mainly is Python related.
Click to expand...
Click to collapse
I don't think my issue is Python related, because I'm just flashing the same img file others flashed too (I don't even have that tool installed). My ultimate question is why other people can flash img file and everything works fine, but I still have the same logo image? Note that I have my Mi5 unlocked and rooted with latest twrp, and personally am very confident in what I'm doing. I tried it multiple times in many different ways (using Terminal, fastboot, and twrp), and damn thing just won't work for me.
Related
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Note:
This is not bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when device is switched ON)
This is for Lenovo A6000 & A6000 Plus Only..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Lenovo A6000 or A6000 Plus (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: Lenovo_A6000_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
2. @mshoaib7 who provided the stock splash.img of A6000
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Or check this thread for a huge collection of A6000 splash screens!!
Having problems flashing splash it says in the fastboot flashing okey but when i boot its my old splash img
JovanSijacki said:
Having problems:
On flashing splash, it says in the fastboot "flashing okey", but when i boot its my old splash img
Click to expand...
Click to collapse
Which one you changed?
splash.png or splash2.png ?
If splash.png, try changing both..
I don't know which splash is used where, since I don't own a Lenovo A6000..
I just created this.. Not even tested by anyone else..
@GokulNC
The_A6000_Splash_Maker works, but the splash screen image has incorrect colors.
I did it it works fine for me no color distortion
You just have to find a nice jpg to png coverter
sasukay said:
@GokulNC
The_A6000_Splash_Maker works, but the splash screen image has incorrect colors.
Click to expand...
Click to collapse
Try the updated zip file, and report if there are issues...
I guess you downloaded the old zip file..
I updated it like after an hour after creating this thread..
(Or was it the old one that worked right?
It's actually a confusion between bgr24 & rgb24 color formats.
I couldn't find which one, because the stock logo was black & white and there was no way I could decipher from that)
So I'm waiting for your reply
GokulNC said:
Try the updated zip file, and report if there are issues...
I guess you downloaded the old zip file..
I updated it like after an hour after creating this thread..
(Or was it the old one that worked right?
It's actually a confusion between bgr24 & rgb24 color formats.
I couldn't find which one, because the stock logo was black & white and there was no way I could decipher from that)
So I'm waiting for your reply
Click to expand...
Click to collapse
I used the new one. You could've figured that out with the time stamp in my post.
And btw, I think its due to some kind of problem in converting jpg to png. I just opened the 720x1280 jpg image in Paint and saved it as png
sasukay said:
I used the new one. You could've figured that out with the time stamp in my post.
And btw, I think its due to some kind of problem in converting jpg to png. I just opened the 720x1280 jpg image in Paint and saved it as png
Click to expand...
Click to collapse
And is it working now correctly??
BTW, your pic exactly has to be 720x1280.
Yours wasn't (Anyway, that doesn't have anything to do with color)
GokulNC said:
And is it working now correctly?? BTW, your pic exactly has to be 720x1280. Yours wasn't (Anyway, that doesn't have anything to do with color)
Click to expand...
Click to collapse
I used only the new one, which doesn't work for me. And, my image was in 720x1280 only
sasukay said:
I used only the new one, which doesn't work for me. And, my image was in 720x1280 only
Click to expand...
Click to collapse
Okay, I've updated the zip again (to the old one, ie, bgr24 color format)
Download & try it now..
It should work...
The latest one is working perfectly. Thanks again brother for making this tool
Sent from my Lenovo A6000 using XDA-Developers mobile app
One more thing splash.png is the boot logo and splash2.png is the bootloader image
Sent from my Lenovo A6000 using XDA-Developers mobile app
is there any to change logos using this for redmi note 3
Works perfectly using "bgr" format. I made a thread to share your custom splash screens HERE.
Please, share yours. Cuz, Sharing is Caring..
Here's mine -
mdnaveedb4u said:
is there any to change logos using this for redmi note 3
Click to expand...
Click to collapse
This is only for Lenovo A6000.
If you want a tool for Redmi Note 3, send me the splash.img (or boot logo wherever it's present) and I'll try to make a tool for your device if possible..
Use this command to dump the splash.img to your Internal Storage & send that to me:
Code:
su
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
GokulNC said:
This is only for Lenovo A6000.
If you want a tool for Redmi Note 3, send me the splash.img (or boot logo wherever it's present) and I'll try to make a tool for your device if possible..
Use this command to dump the splash.img to your Internal Storage & send that to me:
Code:
su
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
Click to expand...
Click to collapse
Many Many thanks for your effor dear here is my splash.img which i have dumped using your command
Hope you post a tool as soon as possible thanks bro for all your effort this will help many redmi note 3 pro users
link
http://www.mediafire.com/download/e9cdlfwfkb0e9ru/splash.img
mdnaveedb4u said:
Many Many thanks for your effor dear here is my splash.img which i have dumped using your command
Hope you post a tool as soon as possible thanks bro for all your effort this will help many redmi note 3 pro users
link
http://www.mediafire.com/download/e9cdlfwfkb0e9ru/splash.img
Click to expand...
Click to collapse
Okay..... I just tried something for Redmi Note 3, seems it'll work..
This is the picture I temporarily used: http://androidwalls.org/wp-content/...pers-for-android-1080x1920-jack-o-lantern.jpg
Download these two files:
test1.img
test2.img
Before proceeding, make sure fastboot is setup & working properly in computer..
Now flash test1.img by:
Code:
dd if=/sdcard/test1.img of=/dev/block/bootdevice/by-name/splash
Now reboot & see if it has changed....
(If device doesn't boot, just flash the original splash.img you sent me from fastboot by: 'fastboot flash splash splash.img')
Then flash test2.img by:
Code:
dd if=/sdcard/test2.img of=/dev/block/bootdevice/by-name/splash
Again reboot & see if it has changed....
(If device doesn't boot, just flash the original splash.img you sent me from fastboot by: 'fastboot flash splash splash.img')
If they're working, try the below one:
test3.img
Flash it similarly.. I guess this one won't work & you'll have to flash the original splash.img
Sorry for this many test images, I just want to ensure how it's processed in your device for safety..
MANY MANY of the effort i have tested all three images all are same cynogenmod no new logo.. all are booting properly but logos are not changed please i highly appreciate your effort thanks once again hope you find a solution soon
mdnaveedb4u said:
MANY MANY of the effort i have tested all three images all are same cynogenmod no new logo.. all are booting properly but logos are not changed.
Click to expand...
Click to collapse
Thanks.. It seems that one was fastboot or download mode image which I changed (maybe)..
OK, here's a new try.. This one should definitely work..
Download Link
Try all the test1, test2 & test3 .img files as I said above & tell me which .img are working...
(Make sure fastboot is setup & if device doesn't bootup, do as I said above)
If an .img file is working, before proceeding to flash next test#.img, boot into fastboot mode in device & see if the picture there is displayed properly..
If fastboot doesn't work in device, don't proceed further.. Just flash the original splash.img you provided me, & send a reply about what happened..
Can i flas it via flashify or via custom recovery
Sent from my Lenovo A6000s using XDA Free mobile app
Note:
This is not bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when device is switched ON)
This is for ZTE Axon 7 Only..
(For Axon 7 Mini or other devices, send me your splash.img so that I can see if this tool can work in your devices)
Requirements:
1. Rooted ZTE Axon 7 (any ROM)
2. Terminal Emulator app
STEPS to create splash.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
1. Make sure you have a 1440x2560 picture in PNG format.
(If it's not exactly 1440x2560, there might arise problems with fastboot mode. So double check the resolution)
2. Download & Extract this: Axon7_Splash_Maker.zip
3. Now rename your picture as logo.png & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder.
STEPS to flash splash.img:
0. First, backup your original stock splash.img by the command:
Code:
su
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash_backup.img
(And transfer to computer, might be needed in future)
1. Transfer the splash.img that you created to your device's Internal Storage.
2. Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
(You can also flash from fastboot as given below)
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from fastboot like:
Code:
fastboot flash splash splash.img
This is created based on A2017G's firmware, but should work with all variants..
Please report if any issues..
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
This is awesome , i was wondering about this when I came across that particular image file.
is this static only? or can be animated? (At least 15 frames hehehe).
DrakenFX said:
This is awesome , i was wondering about this when I came across that particular image file.
is this static only? or can be animated? (At least 15 frames hehehe).
Click to expand...
Click to collapse
Lol, just one image..
The one that can be animated and have multiple framee is known as "bootanimation"
Just kidding
GokulNC said:
Lol, just one image..
The one that can be animated and have multiple framee is known as "bootanimation"
Click to expand...
Click to collapse
Yeah, i know i have my own collection...for some reason i thought splash screens can be animated too.
This are my animations for Axon 7 and working in few more.
http://forum.xda-developers.com/axon-7/themes/bootanimation-t3442646
Zte axon Bootlogo
flash in TWRP
Unlock Bootloader and custom rom
Here's mine.
Flashable zip.
Picture found in the official ZTE forum.
Thanx for your information :good:
hi I would like to know if this procedure can be applied to a ZTE axon mini
Thank you so much for this. Made my own
https://ibb.co/kQAfvV
Made a basic AOKP one. Thanks for the guide GokulNC!
the splash.img does not work on A2017G Oreo B02. On Nougat no problems. gives a chance to change this?
Sagit Logo Generator for Xiaomi Mi Pad 4 (clover)
Download: here
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 4 image files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 4 image files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM.
Source: https://github.com/moonheart/sagit-logo-gen/tree/MIPAD4_clover
Thanks @huhu2207 for advice (binwalker).
Thumb up.
Which image should I change if I want to change only the splash screen?
I am still confuse with this mod. Why do I have to change 4 images?
This mod is for splash screen right? Or maybe I am wrong?
I want to know someone successfully using TWRP flash? Because it supports IMG files!
addro said:
I want to know someone successfully using TWRP flash? Because it supports IMG files!
Click to expand...
Click to collapse
Do you know which image to change? There are 4 images.
I want to change only the splash screen. So I only need to change 1 picture, but which one? Is it picture number 3?
dyingbread said:
Do you know which image to change? There are 4 images.
I want to change only the splash screen. So I only need to change 1 picture, but which one? Is it picture number 3?
Click to expand...
Click to collapse
Please be careful that I have failed! I have lost the splash screen.:crying:
addro said:
Please be careful that I have failed! I have lost the splash screen.:crying:
Click to expand...
Click to collapse
What? How did that happen?
Btw you could easly fix that by flashing default logo.img
What picture did you change?
dyingbread said:
What? How did that happen?
Btw you could easly fix that by flashing default logo.img
What picture did you change?
Click to expand...
Click to collapse
I just changed the 03 picture,size 1080X1920.BMP, No other changes to the picture!
addro said:
I just changed the 03 picture,size 1080X1920.BMP, No other changes to the picture!
Click to expand...
Click to collapse
How did you flash the new logo.img? Via twrp or fastboot?
dyingbread said:
How did you flash the new logo.img? Via twrp or fastboot?
Click to expand...
Click to collapse
I use fastboot.
The first time I used this program --> ( https://forum.xda-developers.com/mi-max/themes/guide-to-change-mi-boot-logo-unlocked-t3662117 ) did not change! But it works in my Xiaomi Mi Max!
The second time I used (moonheartmoon) this method was unsuccessful and lost the boot logo! I don't know if it is just a matter of replacing the 03 picture?
I don't know what to do now, can return to the boot logo.
addro said:
I use fastboot.
The first time I used this program --> ( https://forum.xda-developers.com/mi-max/themes/guide-to-change-mi-boot-logo-unlocked-t3662117 ) did not change! But it works in my Xiaomi Mi Max!
The second time I used (moonheartmoon) this method was unsuccessful and lost the boot logo! I don't know if it is just a matter of replacing the 03 picture?
I don't know what to do now, can return to the boot logo.
Click to expand...
Click to collapse
Your device can boot normally right? Just don't have a splash screen. Flash stock logo.img and and your splash screen should be back. You can get stock logo.img from official fastboot rom. Or if you want I can send you the logo img. It's just 3 MB.
dyingbread said:
Your device can boot normally right? Just don't have a splash screen. Flash stock logo.img and and your splash screen should be back. You can get stock logo.img from official fastboot rom. Or if you want I can send you the logo img. It's just 3 MB.
Click to expand...
Click to collapse
Don't give it to me, my stock MIUI ROM everything goes back to normal! You also don't want stock splash screen! Maybe this is only MIUI10 Flash stock!
I have a link, you can refer to it! --> https://xiaomi.eu/community/threads...-image-and-fastboot-image-for-mi-pad-4.47466/
addro said:
Don't give it to me, my stock MIUI ROM everything goes back to normal! You also don't want stock splash screen! Maybe this is only MIUI10 Flash stock!
I have a link, you can refer to it! --> https://xiaomi.eu/community/threads...-image-and-fastboot-image-for-mi-pad-4.47466/
Click to expand...
Click to collapse
I tried with that tool you gave me but still splash screen is gone. Someone who shared that tool in xiaomi.eu forum said that it works but not for me.
Splash screen doesn't have anything to do with ROM. If it works with MIUI it should works with any ROMs.
Have you tried this tool? It works for me on my Mi Pad 4 Plus.
meiser said:
Have you tried this tool? It works for me on my Mi Pad 4 Plus.
Click to expand...
Click to collapse
Do you use miui recovery fastboot?
What do you mean? I use the official fastboot binary.
So I just tried again with moonheartmoon's tool from OP without changing anything. It works, the splash screen is changed to picture no 3 (mi logo with scribble on it).
But when I change picture no 3 with my desired logo it's not working. My picture file type is bmp but it's not working. Is there any special method to make this bmp file?
EDIT: The problem is my picture file size, it's too big. Max picture file size is 2 MB. Bigger than that your splash screen will be gone and shows some warning about bootloader unlocked when booting up.
moonheartmoon's tool is working good for clover. There should be a warning about file size in OP though. Well whatever this tool works, just make sure picture file size is not to big. Thanks
meiser said:
What do you mean? I use the official fastboot binary.
Click to expand...
Click to collapse
You are using MIUI ROM ?
Hi everyone. I recently bought an Alcatel 1t 7 (8067) tablet, 1Gb ram, 16Gb rom, just wifi (no 4G), mt6580 processor, android oreo go edition; a very simple and cheap tablet, but it seemed me a very nice one, because is slim and lightweight; worhty of root access, but also a custom recovery. I prefer TWRP recovery because it's more organized... ¡Anyway!... So I got down to work, but at first, as I didn't know how to backup all firmware, and when I learned how to do it and did it (esentially I could "tame" sp flash tools, hehe), I had already lost my original recovery file. Is needless to say that TWRP recovery, as far as I know, isn't available for this model, so I needed to port it, but as at first, I didn't know how to back it up, I overwritten it with other recoveries that didn't work. I mean, at this time, the tablet is working but is without recovery tool. I'm not going to talk about root access, because I already could get it, by using magisk manager, but I need my recovery image file, back; both to reinstall it and port it to TWRP.
So finally, if anyone has this stock recovery file, the full stock rom for it, or even better the ported TWRP for this tablet, please share it to me.
Thanks in advance for your attention.
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
aIecxs said:
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
Click to expand...
Click to collapse
Thank you for reply. Ok, I booted android. I have enabled usb debugging so, when android booted, I connected it to adb, and opened "adb reboot recovery" command, to be sure that android would reboot into that mode; but it didn't, it just rebooted several times on boot screen, and when it "got tired" of rebooting, it booted into android. Didn't boot into recovery, so I guess, It didn't repair it.
PS: I was looking for that file "recovery-from-boot.p" on that path, and there isn't such file, i can't find it.
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
you can port TWRP with kernel from boot. you can use this TWRP as base
aIecxs said:
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
Click to expand...
Click to collapse
¿Must that file have the same size that the original recovery image? Because the only file named recovery that i can find on that path is named "recovery-resource.dat" and its size is 807kb, and as I have seen before, is that recovery images have several Mb of size.
aIecxs said:
you can port TWRP with kernel from boot. you can use this TWRP as base
Click to expand...
Click to collapse
Two questions about it; as far as I can remember twrp image must be compatible not only for the same chipset, but the same screen resolution ¿Am I right? Also, this tablet is 600x1024 px, or 1024x 600 on landscape mode. All TWRP that I have installed on former machines, worked on portrait mode, so I wonder miself ¿Could TWRP also work on landscape mode?
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
aIecxs said:
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
Click to expand...
Click to collapse
Ok... I can find that file on my tablet, but I'm not so skilled android user, as for rebuild recovery from that file or even port TRWP from that file, so ¿Is there an easy way to do it ( or at least, comprehensible for middle skilled android users) ? ¿How? (and supposedly this machine is easy to port and root, they say on internet. I also have a huawei y7 2018 for rooting, that seems harder to root. But that's a another (my next) struggle in here, hehe)
aIecxs said:
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
Click to expand...
Click to collapse
Another question. ¿Are those programs who claim to help to port TWRP with just some clicks, reliable? (for instance TWRP porter for mediatek)
aIecxs said:
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
All the TWRP recoveries that i have ported before, have had a working touchscreen, but as I understand, resolution requirement is not only for touch calibration, but for correct displaying of TWRP GUI (that all buttons and options fit on the screen), Now I've read that new versions of TWRP adjust automatically to any screen resolution, ¿Is that right?
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
HCU-client needs 4 credits for Huawei.
I may reply in new thread.
aIecxs said:
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
Click to expand...
Click to collapse
¡No, man! If TWRP porting is kinda hard having the stock recovery image, without it, is a brain smashing task (or at least for me). I mean, I really don't understand well, how to port twrp starting only with boot.img, I mean, without recovery img. I've saw tutorials about the use of carliv kitchen (windows version), and seems easy, but all tutorials are made with stock recovery.img available, not with boot.img. So, what can I do there?
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
aIecxs said:
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
Click to expand...
Click to collapse
I saw a tutorial about. It said that I must to unpack stock recovery and twrp recovery, and replace some files of unpacked twrp recovery, with respective unpacked stock recovery files, and edit some files on twrp unpacked folder, and finally repack it.
Until that point, I assume that it should work, I mean, having stock recovery. But I did that, but using boot.img, I renamed all boot resources, to recovery, for instance, boot.imgkernel to recovery.imgkernel; and replaced it, repacked it, and reflashed it, but nothing happened, I mean, it didn`t want to boot into recovery. It`s interesting to "experiment", but I`m gonna try to find its original stock recovery, to at least get it back.
Hello!
I would like some help, alcatel 1T7" 8086 no4g I likely bricked it. There's nothing else than a black screen. The tablet doesn't react to anything. The computer finds it as unknown USB tool. No visibilty is shown. What can i do with it,for it to work? Or should i just put it in the trash?
Thank you for the reply.