I was wondering if it were possible to change the bootloader logos (not the boot animation, which displays during the Android startup process) for the HD 8.9" (jem). Would we be able to change both the white & orange and white & blue "Kindle Fire" logos, or would we only be able to modify the white & blue logo? I know the second logo must be modifiable somehow, as Hashcode did it when he wrote the 2nd bootloader image for the HD devices.
Using existing bug in bootloader only 2nd one is possible to change. Orange logo is shown by the stock amazon bootloader which is signed and those the device will refuse to boot it if you will modify it. To modify the second bootlogo you should recompile 2nd bootloader and rebuild boot.img
ipipipipip said:
Using existing bug in bootloader only 2nd one is possible to change. Orange logo is shown by the stock amazon bootloader which is signed and those the device will refuse to boot it if you will modify it. To modify the second bootlogo you should recompile 2nd bootloader and rebuild boot.img
Click to expand...
Click to collapse
1) So I would need to modify initlogo.rle and then recompile the u-boot file?
2) After that, would I need to flash that file to the bootloader partition on the Kindle?
3) Finally, would the new u-boot bootloader brick my kindle?
If you flash it in place of second bootloader you are safe (second bootloader is built-in into "boot" partition), if you alter actual "bootloader" partition -- you'll get a brick (it is signed, and its integrity is checked by xloader (also signed xD)) (and I'm not sure if it is possible to recover from this state without disassembling the device and connecting directly to emmc pins).
TL;DR; It's not possible to get rid of orange kf logo, but you can change the blue one.
ipipipipip said:
If you flash it in place of second bootloader you are safe (second bootloader is built-in into "boot" partition), if you alter actual "bootloader" partition -- you'll get a brick (it is signed, and its integrity is checked by xloader (also signed xD)) (and I'm not sure if it is possible to recover from this state without disassembling the device and connecting directly to emmc pins).
TL;DR; It's not possible to get rid of orange kf logo, but you can change the blue one.
Click to expand...
Click to collapse
Sorry for the (really) late reply, but I read the post, and I was planning on building CM for myself. Would I flash the u-boot file directly to the boot partition, or does it need to be wrapped into a ROM boot image somehow? Also, if if needs to be embedded into the boot image (and I'm assuming it does), where would it need to be placed?
There is a prebuilt binary of uboot (in the device specific files) https://github.com/KFire-Android/android_device_amazon_jem/tree/cm-12.0/prebuilt/boot that is attached to the boot.img while building the ROM
ipipipipip said:
There is a prebuilt binary of uboot (in the device specific files) https://github.com/KFire-Android/android_device_amazon_jem/tree/cm-12.0/prebuilt/boot that is attached to the boot.img while building the ROM
Click to expand...
Click to collapse
I figured that out, and I was able to change the 2nd bootloader image successfully.
However, whenever I directly reboot to recovery without pressing and holding the volume up button (i.e.: when choosing to reboot to recovery from within TWRP or Android), the blue and white "Kindle Fire" logo shows up instead of my custom image. I'm thinking that this is because the initlogo.rle is also baked into the custom bootloader partition (which I think uses u-boot as well). Would there be any way to decompile the bootloader (not the u-boot.binary in the device-specific files), replace initlogo.rle, and then recompile into a usable bootloader image?
the initlogo.rle is also baked into the custom RECOVERY partition
Click to expand...
Click to collapse
don't touch the partition called "bootloader" without correct signature you'll get a brick that is quite hard to recover.
recovery partition is built almost the same way as the boot one, and I suppose you may use the same uboot binary (the one with replaced initlogo.rle) for it, just place it with a specific offset into your TWRP (or whatever you use) recovery image.
https://github.com/KFire-Android/android_device_amazon_jem/blob/cm-12.0/boot.mk#L53
ipipipipip said:
don't touch the partition called "bootloader" without correct signature you'll get a brick that is quite hard to recover.
recovery partition is built almost the same way as the boot one, and I suppose you may use the same uboot binary (the one with replaced initlogo.rle) for it, just place it with a specific offset into your TWRP (or whatever you use) recovery image.
https://github.com/KFire-Android/android_device_amazon_jem/blob/cm-12.0/boot.mk#L53
Click to expand...
Click to collapse
I'll try that out. Thanks so much for the help!
To All,
Following the instructions on one of the threads of this forum, I was able to root my Samsung Galaxy S7 Active. The next thing I would like to do is to change the boot splash screen. Right now, I get the Samsung boot splash screen with the unlocked icon. I have tried some of the techniques used for older Samsung Galaxy S Active devices, such as identifying the param partition and uncompressing it but I haven't been successful during the uncompress process. When attempting to uncompress it, I get an error stating that the tar command cannot understand the file header for the param partition. I have searched the forum and some people have stated that the boot splash screen might be embedded in the kernel although this has only been briefly discussed in other threads not directly related with my question. Also, I didn't see any threads addressing this question, which is the reason I decided to start one. Has anybody tried to modify the boot splash screen for this device after rooting it?
Thanks!
- Trucudrulo
I am seeing the mod from @miniminus does change the bootscreen, but not the very initial splash where displaying the "S7 Active" and the "unlocked" padlock. Perhaps you should root the device first, then look into the system directory?
Ok so this is what happened
Device: Samsung Galaxy Note 10.1 2014 edition p607t Lollipop 5.1.1 build LMY47X.P607TUVSBPL1
Attempting to flash to lineage-14.1-20170816-nightly-lt03lte-signed.zip
1)Used TWRP to flash recovery {twrp-3.1.1-0-lt03ltexx.img.tar}
2)Boot to recovery
*recovery fail*
*reboot*
3)reattempted flash same file
4)Used app store app to reboot to recovery
*recovery fail*
*enter [bootloop]
5)Booted to Download
*odin3 fails to recognize*
*ADB Installer version 1.4.2 fails to recognize*
*Samsung Link fails to recognize*
6) Post here as I am now out of ideas...
Twrp 3.1.1 does not work on the note 10.1 I found out the hard way also. The only way I found to stop the loop was to open the back and temporarily disconnect battery, carefully as you can break the connector easily, when you connect the battery the tablet will be off and you use the power button / volume button combination to enter download mode and install older version of twrp which works.
Model: SM-T800
Current ROM: LineageOS 14.1
Current recovery: twrp-3.1.1-0
So I was trying to edit the boot logo on my tablet. I found the logo.jpg in an archive (/dev/block/platform/dw_something0/by-name/PARAM).
I backed up the PARAM archive, extracted it, edited the image slightly, repackaged it and put it back. Then I restarted the tablet and whoops black screen.
I guess some permissions didn't end up as they should have.
I can't get in to recovery by button combination and I can't boot the system. I can however get in to download mode.
Edit: What I ended up doing was flashing a stock bootloader with odin that contained param.bin.
Now I can continue what i was doing. SOLVED
Hi all,
Great work on the SamPWND technique!
I am wondering if there is a way to disable the console text that appears on boot and shutdown? Also can I change the Samsung static splash image that occurs before the qmg boot sequence?
Thanks all!