Related
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
bzowk said:
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
Click to expand...
Click to collapse
First off, this isn't Development.
Secondly, I explained to you how to fix this in the very root thread you linked several times.
Thirdly, there's a newer, official RUU from HTC right on their ROM Downloads website. I'd start by installing that (though I also have a recovery-flashable version of that ROM in my Base ROM thread).
Fourthly, with access to an official RUU, and my ROM decrypt script, you have access to the stock boot.img (which is also in the firmware zip in my Base ROM thread), which you can use as your baseline for restoring the verity key to the ramdisk, thereby allowing you to use adopted storage without any issues. Note however that I was only able to use adopted storage with the "forceencrypt" flag enabled.
Fifthly, you can't just restore the stock boot image (at least not if you want to stay rooted). You can be both rooted and encrypted, but you have to first make sure SuperSU is flashed and set up prior to allowing the device to be encrypted again (adopted storage only works with an encrypted device, and then you won't be able to access your storage with TWRP).
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
bzowk said:
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
Click to expand...
Click to collapse
Re-read my post. If you flash the stock boot.img, you will no longer be rooted.
And as I said in the original thread, you need to pull the rooted boot.img and add the verity key from the stock one to it. Also you'll need to add the forceencrypt and verify flag back.
P.S. You also need to re-read the instructions in the decrypt thread. You don't have to rename anything anymore.
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
bzowk said:
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
Click to expand...
Click to collapse
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Captain_Throwback said:
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Click to expand...
Click to collapse
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
bzowk said:
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
Click to expand...
Click to collapse
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Captain_Throwback said:
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Click to expand...
Click to collapse
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
4. Flash SuperSU 2.76 zip
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
9. Flash newly packed boot.img to phone using fastboot
10. Enjoy
I really appreciate your help and patience with me!
bzowk said:
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
Click to expand...
Click to collapse
Good so far . . .
bzowk said:
4. Flash SuperSU 2.76 zip
Click to expand...
Click to collapse
I'm sure this is just a typo, but that should be 2.67, not 76 (there is no 2.76).
bzowk said:
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
Click to expand...
Click to collapse
Bolded the correct one above (no need to leave TWRP as the necessary modifications have already been made).
bzowk said:
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
Click to expand...
Click to collapse
Looks good . . .
bzowk said:
9. Flash newly packed boot.img to phone using fastboot
Click to expand...
Click to collapse
TWRP can also flash the new image, but fastboot is probably the most reliable way to do it.
bzowk said:
10. Enjoy
Click to expand...
Click to collapse
Hopefully . . . You'll likely get a reboot on the first boot (possible multiple reboots), as SuperSU needs a reboot to install the necessary files. Since your device will also encrypt on that initial boot, I'm not sure whether there will be a conflict or not.
bzowk said:
I really appreciate your help and patience with me!
Click to expand...
Click to collapse
Guess we'll see if it all works out . . .
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
bzowk said:
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
Click to expand...
Click to collapse
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Captain_Throwback said:
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Click to expand...
Click to collapse
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
bzowk said:
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
Click to expand...
Click to collapse
If your adopted storage doesn't show as corrupted, and you're able to open the SuperSU app in your app drawer and not get a message that no su binary is installed, you should be good to go .
bad topic
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 4 Pro/Prime Only (which has 1080x1920 resolution)..
For Redmi 4 or 4A, please send your device's splash.img as given in link below.
(For other devices, please send me your splash.img so that I can create a tool for you too.)
Requirements:
1. Rooted Redmi 4 Pro/Prime (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: Redmi_4_Prime_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920px.
3. Now copy your picture inside "pics" folder and rename your picture as logo.png or logo.jpg (according to its format).
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 @ishehad who provided the stock splash.img of his Redmi 4 Pro
2. This is just a modified copy of the tool for Lenovo Vibe K5 Plus
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Nice. Do I need re-flash everytime I change rom?
And where can I find stock splash.img in my device?
Works great!
(I put a personal picture, so I prefer not upload an example, but it came out great).
I never dreamed that suddenly pop up an official guide for my model,
And certainly i never dreamed that the credit I deserve.
All credit goes to you!
Thank you very much! :good:
nice !
I'm try this guide on my redmi 4 prime… but why the end bootsplash no change…?? Still mi.com…
I followed the steps carefully, i'll say that this works like charm!
um... How do you think it would apply to redmi note4x?
Assuming yes to both, as this is before we get to system startup, but:
1) this will work regardless of rom?
2) this will work on encrypted phone?
Thanks a lot dear! Very useful!
Built custom splash screen and flashed on stock rom, it worked fine. Dirty flashing Epic ROM didn't replaced splash screen, can't say about fastboot flash.
How do I extract the .png/jpg image from stock splash.img ?
pauloecs said:
How do I extract the .png/jpg image from stock splash.img ?
Click to expand...
Click to collapse
You may try Android Image Kitchen. Both pc and Android version are available on XDA.
Thanks for the great tool! It worked great on my device.
I made some Google Logo Spalsh images, the original images were extracted from here, and I made some changes with PS.
Hope you guys would like it
Google-Evolved-Splash.zip
GoogleG-Evolved-Splash-BlackWhite.zip
GoogleG-Evolved-Splash-Coloured.zip
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 A1 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 Mi A1 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
FOR NEW FIRMWARES FOR WHICH THIS TOOL DOESN'T WORK, TRY THIS NEW TOOL here:
https://forum.xda-developers.com/mi-a1/themes/tool-tissot-splash-maker-mod-5-pngs-t3799701/
Also, try these if that didn't work:
https://forum.xda-developers.com/showpost.php?p=76713069&postcount=42
https://forum.xda-developers.com/mi...change-boot-logo-splash-t3681033/post75978168
(I don't know if it works; an user seems to have successfully used it to create splash.img for new bootloader)
I never had the latest splash.img from the latest firmware, so I can't create a proper unless someone sends me
For older firmwares, proceed below:
STEPS to create splash.img:
1. Download & Extract this: Mi_A1_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Mi A1 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & 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 after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:View attachment 4073256 can be edited to something like this: View attachment 4073257
(Hope you understand what I say)
c. Try some other picture.
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.
Credits:
1. Based on my original tool for Redmi Note 4
2. @OtrovX who provided the stock splash.img of Mi A1.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Was searching for this thanks.
@GokulNC
I created splash with your demo logo image... Result: Same boot logo showing when booting
I created splash with Google and iphone pngs taken from rn4 thread... Result: Same boot logo showing when booting
So not working for me
@GokulNC
Splash not working bro in ma1
it create splash image and i flash via fastboot but not working
Kindly look into it asap
ravinder0003 said:
@GokulNC
I created splash with your demo logo image... Result: Same boot logo showing when booting
I created splash with Google and iphone pngs taken from rn4 thread... Result: Same boot logo showing when booting
So not working for me
Click to expand...
Click to collapse
rameshurfrnd1 said:
@GokulNC
Splash not working bro in ma1
it create splash image and i flash via fastboot but not working
Kindly look into it asap
Click to expand...
Click to collapse
Please send your stock splash.img and logo.img
I'll check what the problem is..
GokulNC said:
Please send your stock splash.img and logo.img
I'll check what the problem is..
Click to expand...
Click to collapse
Attached splash.img of stock and logo.img not available check enclosed screenshot
Hey, @GokulNC please add options like change bootloader image, charging animations etc, and give a proper way to unpack or extract decompile splash.img file.
Will this also change the 'your device bootloader has been unlocked' thingy?
Say goodbye to white
If there's enough interest I'll make a matching boot animation (Oreo flavor)
Tested and working through flashing via twrp on latest Oreo OTA
Tested and working through flashing via twrp on latest Nougat OTA
If you find yourself stuck in a twrp bootloop - look at the slot you are in
If in A choose reboot - than select slot B - then boot to system to get out of it
any way to remove bootloader unlock warning in mi a1?
need to find out how to remove or change to black
pedrazadixon said:
any way to remove bootloader unlock warning in mi a1?
Click to expand...
Click to collapse
There's already a couple of us looking into to this but so far no luck
I've combed through system dumps even and nothing to be found
If anyone knows where this screen is located please let us know
Stoutpuppy GFX said:
There's already a couple of us looking into to this but so far no luck
I've combed through system dumps even and nothing to be found
If anyone knows where this screen is located please let us know
Click to expand...
Click to collapse
@Stoutpuppy GFX, I was reading an earlier reply of yours on this thread, did you flash the splash.img in TWRP instead of fastboot flashing it?
Any luck on anyone getting this message removed?
I tried the splash maker, didn't do anything, instead of a white background screen with the text, anytime I made a splash image and installed it, the screen was then black with the bootloader unlocked text. Has anyone unlocked their bootloader and used this Splash Maker and had it work?
fastboot erase splash works, then we get a black screen and Tux... LOL
I've always considered a Splash image what you see on a bootup, running this command removes this message, but the Fastboot image is also removed in the Mi A1.
It would be nice to not erase the splash and someone comes up with a fix for this?
Please let us know...
Thanks
DoR3M3 said:
Any luck on this?
I tried the splash maker, didn't do anything, instead of a white background screen with the text, anytime I made a splash image and installed it, the screen was then black with the bootloader unlocked text.
Removing the splash image does work, then we get a black screen and Tux... LOL
It would be nice to not erase the splash and someone comes up with a fix for this?
Please let us know...
Thanks
Click to expand...
Click to collapse
No luck so far - but I read somewhere the some pixel & nexus devices have the same problem with no solution either
I'm hoping these screens will disappear once we get an official ROM for our device - fingers crossed I hate white screens
And I just flashed the splash screen through adb commands (fastboot splash splash.img) don't use brackets
but unfortunately if you have to leave your device in an unlocked state - all it will do is change the splash screen
to black with message saying your phone can't be checked bla bla - followed by that white unlocked screen shown in previous post
Stoutpuppy GFX said:
No luck so far - but I read somewhere the some pixel & nexus devices have the same problem with no solution either
I'm hoping these screens will disappear once we get an official ROM for our device - fingers crossed I hate white screens
Click to expand...
Click to collapse
@Stoutpuppy GFX
WOW fast reply, LOL...
Please look back and read over, I edited my previous reply...
Thanks
Any news about the splash solution for the tissot? Thanks.
PS: the problem seems to be the new splash format comes with the new bootloader.. Does anybody got luck to guess the format?
Since this tool is based on redmi note 4's tool and the redmi note 4 ones already have splash maker for newer firmware in that thread, can I use that for Mi A1 too?
robby_tan said:
Since this tool is based on redmi note 4's tool and the redmi note 4 ones already have splash maker for newer firmware in that thread, can I use that for Mi A1 too?
Click to expand...
Click to collapse
The new format for RN4 is:
python bin/logo_gen.py pics/logo.png 100864
mv output.img temp/logo.img
python bin/logo_gen.py pics/fastboot.png 613888
mv output.img temp/fastboot.img
python bin/logo_gen.py pics/logo.png 101888
mv output.img temp/logo2.img
cat bin/header.img temp/logo.img temp/fastboot.img temp/logo2.img bin/destroy.img > output/splash.img
rm output\*.raw
So, I'll test it today for Tissot
GokulNC said:
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 A1 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 Mi A1 (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: Mi_A1_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Mi A1 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & 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 after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:View attachment 4073256 can be edited to something like this: View attachment 4073257
(Hope you understand what I say)
c. Try some other picture.
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.
Credits:
1. Based on my original tool for Redmi Note 4
2. @OtrovX who provided the stock splash.img of Mi A1.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Click to expand...
Click to collapse
thanks
novic_dev said:
The new format for RN4 is:
python bin/logo_gen.py pics/logo.png 100864
mv output.img temp/logo.img
python bin/logo_gen.py pics/fastboot.png 613888
mv output.img temp/fastboot.img
python bin/logo_gen.py pics/logo.png 101888
mv output.img temp/logo2.img
cat bin/header.img temp/logo.img temp/fastboot.img temp/logo2.img bin/destroy.img > output/splash.img
rm output\*.raw
So, I'll test it today for Tissot
Click to expand...
Click to collapse
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
---------- Post added at 01:26 PM ---------- Previous post was at 01:11 PM ----------
novic_dev said:
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
Click to expand...
Click to collapse
Just use the correct scripts I've prepared: http://anikos.su/tissot_splash_scripts_new_novicdev.zip
PS:
SPLASH - is a so-called "structured" raw image of the splash device partition.
Each bootloader parses the splash partition as a set of images created in some different media formats and sizes.
So, the new updated bootloader of Tissot is now parses the splash as a set of 4 (four) parts: "header - image - fastboot image - image 2".
novic_dev said:
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
---------- Post added at 01:26 PM ---------- Previous post was at 01:11 PM ----------
Just use the correct scripts I've prepared: http://anikos.su/tissot_splash_scripts_new_novicdev.zip
PS:
SPLASH - is a so-called "structured" raw image of the splash device partition.
Each bootloader parses the splash partition as a set of images created in some different media formats and sizes.
So, the new updated bootloader of Tissot is now parses the splash as a set of 4 (four) parts: "header - image - fastboot image - image 2".
Click to expand...
Click to collapse
what's header image? The 5 second "device can'tbe checked" warning?
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
gian20 said:
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
Click to expand...
Click to collapse
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
gian20 said:
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
Click to expand...
Click to collapse
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
gcrutchr said:
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
Click to expand...
Click to collapse
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Unable to change Boot Logo
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
gcrutchr said:
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
Click to expand...
Click to collapse
SM T285 flash wrong bootlogo.zip
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
hassansys2 said:
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
soaib333 said:
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
gcrutchr said:
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
Click to expand...
Click to collapse
yes sir the jpg file is around 600 kb..... sir please help me..... :crying::crying::crying::crying::crying::crying:... please tell me sir what can i do for recover my device... sir please...... please sir :crying::crying::crying::crying::crying::crying::crying:
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
sir please, can you send me stock boot logo tar.md5 file for SM-T285 ...... beacuase my phone is bricked.. only download mode is working...... if i flash the orignal bootlogo.tar.md5 i hope it will recover please sir help me.... i request you sir please :crying::crying::crying::crying::crying::crying:
I have a huge problem. I made the .jpg file too big and now the tablet won't boot except for DOWNLOAD MODE. I wasn't able to backup so I just downloaded the param.ifs from this reply.
gian20 said:
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Click to expand...
Click to collapse
Now I am using Windows 7 Heimdall to flash this. Except with this I am unable to flash because it's showing "Error: Failed to retrieve config descriptor."
Need help ASAP
Update: After a few tries, now it says
"Initializing Protocol...
Error: Failed to send data!Releasing device interface...
Solution: Used Odin. Basically, using 7zip, packed the param.lfs to a tar file, then packing that to a gzip file, then prooding to flash via ODIN
Any one have stock param.tar file for flashing on sm-t285?? Plz help me? ? ?
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Darksnite said:
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Click to expand...
Click to collapse
How big is the image you are trying to install?
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 150 kb i dont have it now but i can get it again but i did make sure the picture was below 200 kb
And when i factory data reseted the phone it still have the same logo
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Darksnite said:
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Click to expand...
Click to collapse
You need yo rename your image to: logo.jpg
Then use 7zip or winrar to open bootlogochanger. replace the logo.jpg in the zip file with your logo.jpg
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 Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (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: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
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.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
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.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR 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..
GokulNC said:
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 Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (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: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
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.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
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.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR 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..
Click to expand...
Click to collapse
You are awesome , genius , superb , intelligent , brilliant , excellent , superb:good::good::good::good:
thank You Sooooooo MUCH
How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...
kqixs said:
How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...
Click to expand...
Click to collapse
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.
GokulNC said:
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.
Click to expand...
Click to collapse
The reason wasbunderstood, but i couldn't find the solution...i didn't know much about programming (to edit .bat file) i tried to search it a bit but couldn't succeed so i just used another image for boot logo....
Thnx for you help though....?
Please make a flashable Google pixel logo and boot animation for Redmi note 5 pro
Google G icon splash screen for whyred.
splash.img
raw files
Wow. Thanks its so easy.
This is the flashable zip of my splash screen.
If anyone find it useful.
Thanks for making this guide and sharing this tool, I love it!
I have an issue though, I tried making some 1080x2160/18:9 splash screens but they got vertically squished down into 1080x1920/16:9 , is this meant to happen?
As a workaround I changed my images to 1080x1920/16:9 and made the background pitch black so there wouldn't be black bars at top and bottom.
I'm a loser who loves watching Twitch livestreams, so in lack of creativity I just made these my Splash screens
KuldeepShivankar said:
This is the flashable zip of my splash screen.
If anyone find it useful.
Click to expand...
Click to collapse
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing
sharmasrb said:
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing
Click to expand...
Click to collapse
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.
Can I request this picture for splash image, as my computer is broken..
Thank you
This is a test splash screen...
KuldeepShivankar said:
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.
Click to expand...
Click to collapse
Okay, i want it
@GokulNC I tried to edit the script and make the resolution 1080*2160 because I wanted a white splash without the black bars, and then resized all 3 images to the same resolution, and then made a splash and flashed it. Worked but instead of these images it shows a complete black screen.
You know why?
Rishi2906 said:
@GokulNC I tried to edit the script and make the resolution 1080*2160 [...] Instead of these images it shows a complete black screen.
Click to expand...
Click to collapse
The routine that displays the images is very simple, and just looks for them at certain offsets within the splash partition. When you change the dimensions, file sizes change as well, and the following images are no longer at the offsets they're expected to be, so they can't be found, and nothing is displayed.
If the BMP images are exactly 6,220,854 bytes each, they can just be concatenated together; smaller ones could possibly work with some padding in between them but if you want a larger resolution, the resulting bitmaps would be too large in size.
One way to make the files small enough to fit within their spaces so that the following ones could still start at the right offsets would be to reduce color depth. (Another way would be to find the code that displays the images and edit the offsets it looks for but this isn't trivial). But in the end, the routine might still not be designed to display anything else than 24-bit, 1080x1920 px anyway.
Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip via twrp
irfan.shikarpuri said:
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Is it flash able zip via twrp
Click to expand...
Click to collapse
No.
What is the maximum logo size that I have to make? thanks before
What is the maximum logo size that I have to make? thanks before