Related
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
First things first:
You are doing this on your own risk, I will not be responsible for any damages!!
Requirements:
->An image in .jpg format.
(Note: It is best if the image size is in 720x1280px)
->Bootlogomaker- https://www.google.com/url?q=http://forum.xda-developers.com/moto-g-2014/themes-apps/app-motorola-boot-logo-maker-source-t2874732&sa=U&ved=0ahUKEwiytOTGi5LQAhWKq48KHYgCD3gQFggJMAI&client=internal-uds-cse&usg=AFQjCNHSZisyc5uNTRBqu3UZT0IX-i9hVQ
Making an logo.bin
Steps:
->Open boot logomaker and select your phone!
->Click on logo_boot in the logos and then replace.
->Now browse and choose your image.
->Do the same for all of them.
(For best results use the logo.bin file in the zip attached. You can open it by going to file open.....)
->Now save this by clicking on file and then save as.
Flashing an bootlogo
Method1:
Using ADB:
->Boot your phone to fastboot mode by turning off and then pressing vol.down and power button simultaniously.
->Connect it to your PC and start adb command line by holding shift key and right clicking on an empty place in your adb directory(folder).
->Now type
Code:
fastboot devices
->If you see your phone listed there and it says fastboot, then you are good to go!
->Now type
Code:
fastboot flash logo <location of your logo.bin>
->Then
Code:
fastboot reboot
Now you have custom logo on your phone!
Method2:
(You should have an unlocked bootloader and custom recovery)
->Download the atached zip and replace your logo.bin instead of logo.bin in the zip file.
->Reboot to recovery.
->Flash the zip file!
Thats it!
This is only for motorolla devices. I don't know if it will work on any other device!
good job with the tutorial, only one thing:
you mind changing "custom boot image" to "custom boot logo" in the title?
a boot.img (<-- called boot image) is something different than a logo.bin
just wanted to point that out
thanks!
I thought it was a tutorial on how to build a kernel
Sent from my MotoG3 using Tapatalk
Can we do it for a non rooted phone just flashing the zip file through recovey mode of moto g 3gen
Hiteshpandit said:
Can we do it for a non rooted phone just flashing the zip file through recovey mode of moto g 3gen
Click to expand...
Click to collapse
Yes, but with TWRP
In that software there is no Moto G3 in the list. And my logo created as custom or as for Moto G2 didn't work
Hi, the file works fine on motoG3 XT1540? I have CyanogenMod 14.1 and the twrp. Thanks and sorry for my English
Hiteshpandit said:
Can we do it for a non rooted phone just flashing the zip file through recovey mode of moto g 3gen
Click to expand...
Click to collapse
Yup, you don't need have root access but you must have unlocked bootloader and TWRP(If you go for flashing the zip). Unlocked bootloader is compulsory!!
nahuelt1 said:
Hi, the file works fine on motoG3 XT1540? I have CyanogenMod 14.1 and the twrp. Thanks and sorry for my English
Click to expand...
Click to collapse
It does!
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
DaGoo_Balls said:
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
Click to expand...
Click to collapse
It apparently is.
https://forum.xda-developers.com/r1-hd/development/unofficial-lineageos-14-1-t3689435/post75020813
Thanks. Looks like I have plans for NYE
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
You would be better off to patch my boot image and fastboot boot it.
Then backup your boot image, patch it with magisk, and flash that one back to the device.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/blur2-boot.img"
This keeps things clean, just incase you are using a boot image that is different from your own device. Plus you have a "stock" boot image backup if you ever need it.
Not a bad idea to grab recovery also.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/blur2-recovery.img"
Sent from my ford using XDA Labs
BLU R2 LTE files. Link
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
bobsmithy said:
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
Click to expand...
Click to collapse
The size of memory "shouldn't" matter.
Braunish said:
Hi there, am trying to root this phone also. Stumbled upon your thread and had a question. If I take the 3 image files (recovery, boot, system) that are included at mediafire site (that you included in your post) and replace the same 3 image files in stock rom, would that work to root the phone? Thank you for any help, I've tried kingoroot, kingroot, and framaroot to no avail.
Click to expand...
Click to collapse
Read back few post on this thread. They discuss successful root method.
Basically unlock bootloader and use majisk manager to patch boot.img and flash patched image with fastboot.
Root R2 Plus w/ BLU R0190WW V7.0.04.01 GENERIC 11-02-2018
DaGoo_Balls said:
Thanks. Looks like I have plans for NYE
Click to expand...
Click to collapse
Hi there, I recently got a Blu R2 Plus and am aiming to root. I used the boot-sign.img that came with that ROM version in title (9447 KB) when patching with Majisk Manager and came up with a patched file of 9.57 MB size. Is there a way to test this ROM, or can you verify that is the same sizes you dealt with when you went through this process. Thank you for any information. It took me a while and a factory reset before I could get majisk manager installed to patch the correct boot-sign.img file.
Hi There copy img file to where on phone
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Braunish said:
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
Click to expand...
Click to collapse
If I understand correctly.
You have adb and fastboot installed.
You have a boot image that works for your device and tested it by using fastboot to boot it. let's call it working_boot.img
You have MagiskManager installed.
The next steps:
adb push working_boot.img /sdcard Doesn't really matter where you put it.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on working_boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
adb pull /sdcard/magiskmanager/patched_boot.img
Reboot to bootloader and fastboot boot patched_boot.img
Open MagiskManager. You should see that Magisk is installed and active.
Now that you have temporary root, you have some options.
The easiest way would be to open MagiskManager and use the Direct install option. This will pull, patch and install a patched boot.img to the device.
Unless the the original working_boot.img used is the correct one for your device.
The safer way, pull the stock_boot.img I normally grab recovery also from the device.
For BLU R2 LTE
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/BLUR2-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/BLUR2-recovery.img"
adb pull /sdcard/BLUR2-boot.img
adb pull /sdcard/BLUR2-recovery.img
Then patch it and fastboot boot it to make sure it works.
After that you can either use MagiskManager Direct install or fastboot to flash the new patched_boot.img.
Bricked my device, used SP Flash Tool to update - Now no OTA?
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
8milerd said:
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
Click to expand...
Click to collapse
These links do not work? Link Direct download links are from MediaFire. Click on the name of the file.
I try to use direct download links from MediaFire. There servers can normally handle it. You do not have to navigate ads and redirects with direct download links.
---------- Post added at 04:58 AM ---------- Previous post was at 04:35 AM ----------
HornyOryx said:
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Click to expand...
Click to collapse
A while back , I had to do a factory reset to get an OTA. Then I had to un-root it to get the OTA to flash.
I've been looking for a way to change my A2's splash screen for a while. Tried using tools available for other Mi devices such as GokulNC's Redmi Note 5 toolkit (https://forum.xda-developers.com/re...guide-how-to-change-boot-logo-splash-t3787820) and they worked for replacing the splash screen, but the fastboot image (Xiaomi bunny) was broken in the process, leaving fastboot mode only with a black screen. So I decided to take matters into my own hands and voilà, managed to change both splash images. In this guide I'll explain how.
Edit: since posting this I've made a simple cmd script for automatically generating the splash.img. For the old tutorial check out this post's edit history.
Prerequisites:
Mi A2 with unlocked bootloader
Windows machine with working fastboot executable
Tutorial:
Download a2 splash generator.zip from this post and extract it to its own folder
Replace the .bmp files with the desired images
1.bmp is the default splash logo that shows up when you boot your device
2.bmp is the image for fastboot mode
3.bmp can be left alone as its probably unused (the unlocked warning is now baked into the bootloader itself)
4.bmp is the splash logo with unlocked padlock. You probably should make it a duplicate of 1.bmp
Run generate_splash.cmd. It will make newsplash.img in the same folder
Put your phone in fastboot mode and run the command
Code:
fastboot flash splash newsplash.img
You may now reboot the phone and check the your all new splash and fastboot screens!
If it doesn't work, make sure the resolution of your BMPs is 1080x2160 and save them in Paint as 24 bit bitmap files. Then run generate_splash.cmd and flash the image again.
with this guide you can remove the message that the bootloader is unlocked?
Julio_MotoMod said:
with this guide you can remove the message that the bootloader is unlocked?
Click to expand...
Click to collapse
Na u can not. Unlocked bootloader message is shown from boot loader itself.
To anyone is using a UNIX or UNIX like OS, to generate the image just run
Code:
cat header.img 1.bmp empty.img 2.bmp 3.bmp 4.bmp empty.img > splash.img
Awesome! I was just looking for that. After swaping roms from MIUI to AO I lost my fastboot logo and it was only showing a black screen, Thanks!
In case someone wants to grab the original image files:
Code:
dd skip=16384 count=6998454 ibs=1 if=splash.img of=1.bmp
dd skip=7014840 count=6220854 ibs=1 if=splash.img of=2.bmp
dd skip=13235694 count=6998454 ibs=1 if=splash.img of=3.bmp
dd skip=20234148 count=6998454 ibs=1 if=splash.img of=4.bmp
The generated image matches with 10.0.2.0 stock's splash.img (MD5: EE57036E7626DA5DEFC276F428D7FBE9).
Files are attached.
EDIT: The unlocked bootloader warning is not stored in splash.img (run fastboot erase splash and see yourself), modifying this will not change that
I was waiting for this to create my own bootanimation. I want to share that with you guys if possible.
should i post a reply here or create an other thread(m not familiar with rules). Before this all i have done is explore xda
The bootanimation is of goku (complete UI) though!
@prokaryotic cell This tool break Xiaomi Bunny in the process
YouTube ban guy said:
@prokaryotic cell This tool break Xiaomi Bunny in the process
Click to expand...
Click to collapse
Delete 3.bmp and 4.bmp, run the tool, and it works. Even the stock splash, the one I backup from my device, break xiaomi bunny.
EDIT: lmao i know why mine wont work, because i do the steps incorrectly. you don't have to delete 3 and 4 bmp. but if this post helps you anyway then okay
ARNOB XENON said:
Na u can not. Unlocked bootloader message is shown from boot loader itself.
Click to expand...
Click to collapse
Do you know since when it changed this way? Is it possible to use an older bootloader to avoid the unlocked warning?
Embeeweezer said:
Do you know since when it changed this way? Is it possible to use an older bootloader to avoid the unlocked warning?
Click to expand...
Click to collapse
Yeah, it will be really amazing if someone can make a mod to "hide" the unlocked bootlader thing.
Hey op do you know how to do it for wayne?
fchrkbr said:
Hey op do you know how to do it for wayne?
Click to expand...
Click to collapse
Sooo after few hours playing with hex editor (and actually figuring how to read those hex), I figured out how to do it for 6x! Turns out the composition of the 6x splash is header+logo+fastboot+corrupt+logo-unlocked, rather different than a2 which has 2 bytes of empty file in between logos. Oh, AND for 6x it uses 1080x1920 24bit bmp instead of 1080x2160, idk why
I edited the generator script from op, you can download it below, and how to do it is exactly the same except it has to be 1080x1920 24bit bmp
If OP would take the file to the first page so it's easier to find, it'd be delightful
View attachment 6x_splash_generator.zip
I tried in mi6x(converted mia2) but even if I change 4 files with different images only 1.bmp shows in booting and fastboot is black
fchrkbr said:
Sooo after few hours playing with hex editor (and actually figuring how to read those hex), I figured out how to do it for 6x! Turns out the composition of the 6x splash is header+logo+fastboot+corrupt+logo-unlocked, rather different than a2 which has 2 bytes of empty file in between logos. Oh, AND for 6x it uses 1080x1920 24bit bmp instead of 1080x2160, idk why
I edited the generator script from op, you can download it below, and how to do it is exactly the same except it has to be 1080x1920 24bit bmp
If OP would take the file to the first page so it's easier to find, it'd be delightful
View attachment 4698907
Click to expand...
Click to collapse
Fastboot is broken. Stays black. Rest works.
ktlk21 said:
I tried in mi6x(converted mia2) but even if I change 4 files with different images only 1.bmp shows in booting and fastboot is black
Click to expand...
Click to collapse
Letzen said:
Fastboot is broken. Stays black. Rest works.
Click to expand...
Click to collapse
Huh, weird, you guys on relocked bootloader? I'm sure when it boots it shows 4.bmp, not 1.bmp. Or is your device native 6x (not a2 converted)? It works on my converted a2, but I'll look to it. Maybe it does need empty file.
fchrkbr said:
Huh, weird, you guys on relocked bootloader? I'm sure when it boots it shows 4.bmp, not 1.bmp. Or is your device native 6x (not a2 converted)? It works on my converted a2, but I'll look to it. Maybe it does need empty file.
Click to expand...
Click to collapse
Yes, it is native 6X.
DELETED
pretty awesome tool, thanks for making it. there is not way to replace too the boot animation?
prokaryotic cell said:
I've been looking for a way to change my A2's splash screen for a while. Tried using tools available for other Mi devices such as GokulNC's Redmi Note 5 toolkit (https://forum.xda-developers.com/re...guide-how-to-change-boot-logo-splash-t3787820) and they worked for replacing the splash screen, but the fastboot image (Xiaomi bunny) was broken in the process, leaving fastboot mode only with a black screen. So I decided to take matters into my own hands and voilà, managed to change both splash images. In this guide I'll explain how.
Edit: since posting this I've made a simple cmd script for automatically generating the splash.img. For the old tutorial check out this post's edit history.
Prerequisites:
Mi A2 with unlocked bootloader.
Click to expand...
Click to collapse
I have locked bootloader, and fastboot screen is black.What will i do?
I couldn't find any guide for rooting the V40, so I thought I'd write down the steps I took to root my new EUR V40 - LMV405EBW. Maybe it will help others. Sorry if this is somewhat confusing, I didn't have time to make a polished version. It's basically made from my notes during the process with the commands copied from bash history.
-First, unlock the bootloader following LG's instructions here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
There's no TWRP for the V40 and the one made for G7 doesn't work. I don't have the time and knowledge to even attempt to compile TWRP for the V40, so I proceeded with just patching an original boot image with Magisk.
You can get the patched boot images that I used from here:
Oreo 10e: boot_a_magisk_patched_10e.img
Oreo 20f: boot_a_magisk_patched_10f.img
Pie 20a: boot_a_magisk_patched_20a.img
Pie 20b: boot_a_magisk_patched_20b.img
Pie 20f: boot_a_magisk_patched_20f.img
Pie 20g: boot_a_magisk_patched_20g.img
Q 30b: boot_a_magisk_patched_30b.img (this requires flashing to the active boot partition).
Q 30c: boot_a_magisk_patched_30c.img (this requires flashing to the active boot partition)
Q 30d: boot_a_magisk_patched_30d.image (this may or may not work with "fastboot boot" and could require flashing to the active boot partition. I haven't tested if live boot still works. I just did fastboot flash boot_x img_file).
You can try to boot it with with fastboot if you have a LNV405EBW and skip the KDZ extraction part.
Installing Magisk:
Flashing this image isn't necessary, just straight boot should be sufficient and safe.
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
Code:
adb reboot bootloader
fastboot boot boot_a_magisk_patched_10e.img
After the phone boots the OS with the external boot image, open Magisk Manager and tap on Install. Select the option to Direct install to the active slot. I played it safe and decided to NOT flash also on the inactive slot. I've left it alone so I can use it in case of need of recovery.
You'll probably notice that you don't have a connection to the carrier. Just ignore it, it will back once the phone is booted normally.
Reboot and you will have permanent root until you switch the A/B slots.
In case my patched boot image doesn't work, you can just make your own.
Tools needed:
Magisk Manager 7.0.0 installed on the phone
LG Bridge installed on a Windows machine.
a Linux machine or VM (I used the latest ubuntu desktop), python3 with the zstandard module installed and kdztools from steadfasterX's repo. Maybe kdztools would work on Windows too, I haven't tried it.
adb, fastboot
You need to procure an original ROM file for your phone model. It can be downloaded easily with LG Bridge. Just connect the phone to a Windows PC, start LG bridge, go to the Software update tab and click on Update error recovery. Wait for the download to start and disconnect the phone. Ignore LG Bridge complains about not being able to flash after the downloading stage is completed. Don't click anything in Bridge and before closing it go to C:\Users\<your_username>\AppData\Local\LG Electronics\LG Bridge\SWUpgrade and copy your KDZ somewhere else. Preferably send it to the Linux VM to the LG work folder, it'll be needed there.
On Linux open a terminal:
Code:
cd ~/Documents
mkdir LG
cd LG
git clone https://github.com/steadfasterX/kdztools.git
cd kdztools
nano undz.py -c
For kdztools to be able to extract the V40 images, I needed to edit undz.py and comment the lines 88-90. So, this block should all be commented or undz will fail to extract the boot partitions.
Code:
#if len(dz_item['pad']) != 0:
# print("[!] Error: pad is not empty", file=sys.stderr)
# sys.exit(1)
To extract, with the KDZ copied to ~/Documents/LG/
Code:
cd ~/Documents/LG/kdztools
./unkdz.py -f ../V405EBW10e_00_OPEN_EU_DS_OP_0109.kdz -x
cd kdzextracted/
List the partitions contents and look for the IDs of boot_a and/or boot_b. In my case they were 44 for boot_a and 63 for boot_b
Code:
../undz.py -f V40510e_00.dz -l
Extract boot_a or boot_b or both, they're identical:
Code:
../undz.py -f V40510e_00.dz -s 44
../undz.py -f V40510e_00.dz -s 63
You can find the extracted boot images in the dzextracted subfolder. Get boot_a.image or boot_b.image or both from there and send them to the phone in a location accessible by Magisk Manager. The Download folder should do fine.
Open Magisk Manager and tap Install, select Patch Boot Image file and patch the image file(s) you extracted. Get the patched_boot.img that Magisk Manager saves in the Download folder and send it to a PC where you have adb and fastboot.
Go to the beginning of the post to the Installing Magisk section.
Damned tempting, but I'll wait until after Pie drops.
Sent from my LM-V405 using Tapatalk
Glad to see this, hopefully it's a start for all of us.
If anything, at least a way to unlock the bootloader via legitimate channels! Gonna be generating that string, next chance I get, to be ready.
Sent from my LM-V405 using Tapatalk
Once runningnak3d gets a hold of this, we should be good with the v40. Cool beans.
Hey do the unlock codes online work for $ 12-15 on sprint? I used to flash phones back in the day and got a great deal on a bad IMEI sprint lg v40, but so far I can see there isn’t a way yet. On top off all that I m in Europe and don’t want to get the error message that I m out of the Region. I would have to go to USA just to unlock the phone.
@runningnak3d
Can't I install the firmware on a different device?
V version can not unlock BL, so envious
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
LameMonster82 said:
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
Click to expand...
Click to collapse
Or I could find you stupid for not noticing the patched image is in my first post.
DLS123 said:
I find you stupid for not noticing the patched images are in my first post.
Click to expand...
Click to collapse
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
LameMonster82 said:
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
Click to expand...
Click to collapse
I mentioned in the description 1 line below the link that it's for 10e. There was no other update in a long time. I don't think there can be any confusion for now. I can edit and label the file when there's will be another fw update.
It looks like unlocking the bootloader breaks Widevine L1 on the V40 and downgrades is to L3. No more HD or UHD Netflix.
I couldn't find any other solution than to re-lock the bootloader to restore L1.
This doesn't happen on the V30.
@DLS123
Thank you for all!
I ask you for more details; i'm stuck at flashing first image in adb; it returns an error; have LMV405EBW with 10f. unlocked bootloader of course
Thx again for your support!
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
i suppose is something wrong in this instructions.
daphix said:
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
Anyway; understand now what to do;
Steps are below:
- first install magisk manager
- download magisk zip from magisk site or from magisk manager himself on phone
- download patched_boot_a.img to phone from our good contributor
- use magisk manager and select inslall image of patched_boot_a.img from phone
- magisk manager will generate a magisk patched image
- transfer this magisk patched image (not patched_boot_a.img) to pc in ADB folder
- flash with Adb this magisk patched image from pc to phone.
Thx to our friend!
---------- Post added at 09:53 AM ---------- Previous post was at 09:21 AM ----------
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Hi;
using Magisk mamanger and your file was generated a file: magisk_patched.img
pls support; trying to flash that image from PC with adb not work:
fastboot flash partition_a magisk_patched.img
Click to expand...
Click to collapse
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
DLS123 said:
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
Click to expand...
Click to collapse
Hi , thank you for reply;
I tried many combinations of your commands;
maybe due that am noob, but succesion below simply is not working:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img