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?
Related
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!
Let me explain:
First I hard-bricked my 16gb i747 phone by accidentally flashing an old bootloader with twrp, then I debricked it using a debrick image I found online.
One day I left my phone charging over night and I woke up in the morning and found it overheated and soft-bricked again for some reason, at the time I could get into bootloader, but I couldn't flash anything, it kept giving me writing errors and pit write failure. I didn't have time to deal with it at the time so I just picked another phone.
Now --today-- my other phone --Note 3-- got bricked the same way when I tried to install linux on it, but I fixed it using a full 32gb debrick image I prepared before.
I remembered that my old phone -- The i747 -- is still bricked, so I tried to boot it up but this time the phone wasn't booting at all then after listing my usb devices I figured out that it was hard-bricked when It said qulacomm 9008, so I flashed the debrick image I found online and it booted up to bootloader but in a strange way. It says:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS.
COPY FROM T-FLASH.
BOOT RECOVERY.
WRITE 159488 sectors.
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWERV: 3
And when I list it, it says 'I9100 (samsung galaxy s II) download mode'.
I tried various pit files for various roms and versions of the device, I tried editing the image before booting up the device, and I tried booting using every possible way, but nothing worked. I've been searching all over the internet for a full debrick image, in hope I could boot from sd card and try to fix it after that, or leave it as it is.
The phone is still overheating at the bottom --around the sdcard slot-- and I'm starting to think that this is a physical damage thing, but I really want to fix this one, please help!
Hope this can help
I personally used these files
It's just my Backup
Search for the files and verify they are what you need
https://mega.nz/#F!o5QQ2AjZ!DkFZP4K7AluKjgeeMFEkIA
Sent from my SM-N950U using Tapatalk
chowming said:
Hope this can help
I personally used these files
It's just my Backup
Search for the files and verify they are what you need
https://mega.nz/#F!o5QQ2AjZ!DkFZP4K7AluKjgeeMFEkIA
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Thanks and all, I'm definitely gonna use those files in the future, but...I discovered that my phone was toasted and the problem is with the qualcomm chip, I think that some transistor next to the chip was deformed.
My Note 10+ shut down earlier today and has been stuck on a blue downloading screen but it hasn't changed and won't boot into any other screens to give me options. I've read about others having similar problems on other Samsung devices after flashing but as far as I know I did nothing to trigger it and I am not knowledgeable in sideloading so I don't really know where to start on fixing the issue.
The screen reads:
partition boot
Reason boot: Hash of data does not match digest in descriptor.[2nd] (3)
Calculated Hash of (boot) : D45EF024EE, (VMETA) : 594C218D84
SAMSUNG boot, N975USQS4CTF3, 32618795R
VBMETA N975USQS4CTF3, 32618795R
lux.aestiva said:
My Note 10+ shut down earlier today and has been stuck on a blue downloading screen but it hasn't changed and won't boot into any other screens to give me options. I've read about others having similar problems on other Samsung devices after flashing but as far as I know I did nothing to trigger it and I am not knowledgeable in sideloading so I don't really know where to start on fixing the issue.
The screen reads:
partition boot
Reason boot: Hash of data does not match digest in descriptor.[2nd] (3)
Calculated Hash of (boot) : D45EF024EE, (VMETA) : 594C218D84
SAMSUNG boot, N975USQS4CTF3, 32618795R
VBMETA N975USQS4CTF3, 32618795R
Click to expand...
Click to collapse
It seems your device has a corrupted firmware. This could have been while trying to update and getting a bad download with some data absent.
Either ways, you have to find the latest firmware for your model, download and unzip it, and then flash it properly with Odin 3.14, and you will be fine
Best of luck
I tried using the XDA Discord server to get a quick response, but apparently, some people just ignore me or don't even know how to help me. So I will try here...
I was following that tutorial so that I can use Joycon Droid on my phone. I installed TWRP Recovery and gone in his recovery mode. I wiped what the tutorial asked to wipe and began the flash process. Unfortunately, I mistakenly downloaded the flash files on the computer. I tried removing my SD Card and putting inside it the files I need, but TWRP was not able to read any data for the SD Card. So I tried to find a way to cancel the recovery menu, and I did by clicking Reboot System. Since then, my phone was locked in the logo screen. After many attempts, I've gone from the charging screen and finished by the "An error occurred while updating the device software.". I can enter the download mode, but nothing else. My phone is an A520W and I think the root was not properly installed. I researched everywhere without any solution, so I came to this discord server, hoping someone would save my phone. I tried flashing the official A520W OS, but Odin always does a FAIL message or freezes. I later tried to use another firmware file, reinstalled the Samsung USB driver and Odin, and know it says on the Download Mode screen:
SV REV. CHECK FAIL(BOOTLOADER) DEVICE: 9, BINARY 7. (it failed)
Can someone help me? I really need help!
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
matkali said:
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
Click to expand...
Click to collapse
Kay I'll try the easy-jtag, but if it doesn't work, who is an expert at emmc programming stuff?
Is there a way to fix the crushed partition table without buying stuff?
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
better than the error screen right? the program name is fonepaw
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
It is dangerous for your phone, because every phone have different partition table and different architecture!
Pit file in a520w stock firmware have partition table structures information. (use PIT_Magic.exe to see)
In old architecture of Samsung(e.g. s3) when partition table cleaned from emmc (phone internal storage), they use micro sdcard to boot from it! (to identity correct info for Odin) (same boot from USB when you are installing windows.) then by going to download mode they flash stock Rom!
But I suggest to you find one knows enough information and requirements stuffs.
Heya, I wasn't sure whether to put this under Theming, it is half a question and half a list of my discoveries
I'll be putting em here in hopes of better code nerds figuring out the language this thing speaks for custom boot logos
Tl;Dr is I'm trying to get custom boot logos to work on my F4, everything I could gather is below.
Compared to the normal process of there existing a file like splash.img or boot.img as you would find in a F2 Pro or F3, the F4 has neither
To be more specific, there exists a device partition in /dev/block/bootdevice/by-name/splash, which is a few symlinks to the actual device /dev/block/sda20
However, trying to dd sda20 results a 34MB file of naught but zeroes, viewed in a hex editor it is completely empty.
My guess is this stems from the Virtual A/B partitioning and whatever new boot scheme the peeps what enginerded this thing came up with, making /dev/block/ obsolete.
Side note, I did attempt flashing a logo.img made with the K30 Util (download below) with:
Code:
fastboot flash splash logo.img
Also tried flashing a splash.img made with a barebones Splash util (again, download below), ran:
Code:
fastboot flash splash splash.img
Both cases succeeded in flashing but the logo didn't change, completely ignored it and booted normally. Didn't even brick the device. The nerve.
Half question, half Theme, can anyone help me figure this out?
Links:
K30 Logo Utility (GDrive, 7z, credits to Pzqqt and Gokul NC)
Splash Logo Maker (Generic)
chihirofujo said:
Heya, I wasn't sure whether to put this under Theming, it is half a question and half a list of my discoveries
I'll be putting em here in hopes of better code nerds figuring out the language this thing speaks for custom boot logos
Click to expand...
Click to collapse
I also tried on my Xiaomi 12 pro without success while on the F2 pro no problem.
This is probably due to partitions A / b but especially that the partitions at the level of this sector is write protected.
.\fastboot flash logo_ab logo.img not working.
helo im chiense,
i belicve this is cause by xiaomi protectoing the splash image partitont on a/b phone z
hope this help!!
What about flashing from fastbootD? Will it works?
Hello guys, does any of you have a stock boot splash/logo mod without unlocked logo/text, which is working for poco f4 ? (I need this to hide my bootloader unlock status from bootsplash screen, so that in case of device brick, service center guys will not know its unlocked by just looking at it )
sachin karinki said:
Hello guys, does any of you have a stock boot splash/logo mod without unlocked logo/text, which is working for poco f4 ? (I need this to hide my bootloader unlock status from bootsplash screen, so that in case of device brick, service center guys will not know its unlocked by just looking at it )
Click to expand...
Click to collapse
Unlocking the bootloader does not void warranty.