I changed my kernel image from the source code available from HTC. Now, I see a different kernel splash screen:
http://www.flickr.com/photos/[email protected]/7642048282/in/photostream
However, I want to remove the text "This build is for development purposes......"
Or, If I can replace the kernel splash image with a splash image of my own, that would be really gr8
Can anyone point a solution to me? Is it possible by changing something in kernel code or ramdisk etc?
Any help is much appreciated!! :good:
Hi
You will get this "text" as soon as you flash an "unsigned" boot image
so anything different to stock boot_signed.img
I also dont know where this is "handled" but I guess this
is "deep down" in the bootloader or the firmware.
So this suspect this is something that needs to be done when
building the boot.ing not in the kernel itsself.
But I would also like to know if and how this can be changed too
Regards
max
Related
I was wondering if anyone else has run into this problem and perhaps could help me out...
Kernel source compiles fine, without errors, using the defconfig (actually inspire4g, but no real differences)
whenever I try to boot with it (first tried a cwm zip and now just using fastboot), The first HTC splash screen appears but it never gets to the second one. It is obviously hanging, but it is before adb ever comes up so I can't really troubleshoot it, and have been basically trial and error up till now.
Any suggestions would be greatly appreciated,
Chris
Hey, I've done some reading up around here, and I'm looking to change my boot logo (Boot logo. Not the animation). So far, it doesn't look like anyone other than the developer of Logo Me has any method to do so.
From what I understand, "fastboot flash logo.bin logo.bin" doesn't work as it does on most other devices.
Now, I'm no professional, but I've got some of what many don't have: time and dedication.
It boils down to this: To change the boot logo, I'd need (1) a way to get the boot.img off of the phone, (2) a way to reliably edit the boot.img without corrupting it or messing with the format, (3) a way to figure out which file is the boot logo, and (4) a way to get the modified boot.img back onto the phone (again without messing it up in the process).
I'm fairly sure (4) is solved with "fastboot flash boot.img boot.img", but the others, not so easily dismissed.
When I make a nandroid backup in TWRP, the boot backup is an 8MB "boot.emmc.win". I'm fairly sure that this might be of some use, even if it's only for opening and exploring the contents of the partition.
I'm not sure if anybody has any remarkable leads that they've kept to themselves, but I'd figure this would be a good place to start.
Boot.img = ramdisk+kernel
Nothing to do with boot splash
sent from my i9250
the image that youre looking for is somehow connected to the bootloader. so far only ezekeel has figured out a way to do it safely. key word is safely. it appears as its very easy to brick the device if a mistake is made. now, that said, ezekeel isnt your ordinary app developer. hes also one of the smartest, most creative kernel developers that the android has(that doesnt work for google). youve probably even used one of his many kernel mods in one or more custom roms/kernels that youve tried, across varying devices.
Re: Custom boot splash?
Deleted
Re: Custom boot splash?
Deleted
Hello there,
So recently Ive been doing lots of crazy/funny stuff with my phone like testing different ROM and boot images. I'm trying to do things as secure as possible, reading lots of threads before attempting things and trying to make sanity checks on procedures I read here on XDA. Despite of that, Im still unsecure about some principles:
For what I got, on the process of phone booting from power ON, it all starts at boot ROM. Boot ROM then calls the bootloader. At this point I have the first question: These custom boot images we use to upload to phone are the bootloader, right? So, considering we are not touching boot ROM (at least its what I supose as I never saw any reference on how to change boot ROM), if I use fastboot and upload a wrong or bad boot image I will be able to restore another boot image. I mean, theres no danger of definetely bricking my phone while playing with boot images as boot ROM remains untouched?
When I use flashtool to upload ftf images it will flash everything, including the bootloader, right? Again, if I use a wrong/bad ftf file the Boot ROM remains untouched, so no danger of definetely bricking my phone?
Im tempted to test some Cyanogem fork for Xperia M (among other stuff) but need/want to have this sort of questions sorted out first.
Should I post such newb questionsl ike this in here or in the development section of forum?
Any clues?
Thanks
Sorry to be of no help(mostly because I dislike theory and like practice), but changing the bootloader using flash isn't possible because, at least I, have flashed 4.3 without unlocking bootloader.
About what part of XDA this should go on, it's probably the general discussion of XDA.
DanDare_77 said:
Hello there,
So recently Ive been doing lots of crazy/funny stuff with my phone like testing different ROM and boot images. I'm trying to do things as secure as possible, reading lots of threads before attempting things and trying to make sanity checks on procedures I read here on XDA. Despite of that, Im still unsecure about some principles:
For what I got, on the process of phone booting from power ON, it all starts at boot ROM. Boot ROM then calls the bootloader. At this point I have the first question: These custom boot images we use to upload to phone are the bootloader, right? So, considering we are not touching boot ROM (at least its what I supose as I never saw any reference on how to change boot ROM), if I use fastboot and upload a wrong or bad boot image I will be able to restore another boot image. I mean, theres no danger of definetely bricking my phone while playing with boot images as boot ROM remains untouched?
When I use flashtool to upload ftf images it will flash everything, including the bootloader, right? Again, if I use a wrong/bad ftf file the Boot ROM remains untouched, so no danger of definetely bricking my phone?
Im tempted to test some Cyanogem fork for Xperia M (among other stuff) but need/want to have this sort of questions sorted out first.
Should I post such newb questionsl ike this in here or in the development section of forum?
Any clues?
Thanks
Click to expand...
Click to collapse
if u mean kernel as boot img....and rom as boot rom...
then answer is...u will get hardbrick....
kernel is most important to run a device...it should have correct hardware files or else urs will be gone[more than 80% to end up on hardbrick...]...
and in boot rom[rom or system files] only libs,etc are important ...libs has ur hardware related files to make work correctly and etc has some permissions,bluetooth files,ur partition info,etc[all only for ur phones for hardware]...if u place other device libs,etc u may get hardbrick or hardware wont work as usual....app,fonts,framework can be placed from any but it wont let you boot unless u know how to port...
So I recently unlocked my bootloader and have been having tons of fun installing custom ROMs, recoveries, and doing other fun stuff. Currently, I have a dual-boot situation with hsbadr's CM13 port and Dr. Ketan's ROM. I've changed the boot animation on CM to the default Marshmallow animation, and I'm enjoying it immensely.
The only problem I have with my phone at the moment is the splash screen: the image that shows up before the boot animation, saying something like "GALAXY NOTE 4 -- powered by Android." It's also got the "Custom" overlay on it. I absolutely hate this screen. It's ugly and I kind of want something of my own in its place.
I've researched on how to change the splash screen, learning that it's called the splash screen and not a bootlogo, but I can't seem to find any guides that work for me. There are some very old guides, with non-existent files, and there's a new guide for the Note 4 here, but it doesn't work. The 0p8 file isn't a tarball, and the 0p12 file recommended later in the thread is empty when extracted.
Is there a way to change that screen on the 910V? If so, how? I can't seem to find anything, but it's probably right in front of my face.
Sorry if this is the wrong place to ask this.
I've been trying to figure it out with no avail. Not located in /dev/block/bootdevice/by-name/ and is not /dev/logo
I have a feeling that it might be located in aboot. I am stuck and I need help modding my boot logo so I can have it seamlessly transition into my boot animation (pixel boot animation). I do use h811, but I don't think that is going to make a massive difference from h815 (unless we are going to modify aboot, but I hope it doesn't come to that). Any help is appreciated!
seijinshu said:
I've been trying to figure it out with no avail. Not located in /dev/block/bootdevice/by-name/ and is not /dev/logo
I have a feeling that it might be located in aboot. I am stuck and I need help modding my boot logo so I can have it seamlessly transition into my boot animation (pixel boot animation). I do use h811, but I don't think that is going to make a massive difference from h815 (unless we are going to modify aboot, but I hope it doesn't come to that). Any help is appreciated!
Click to expand...
Click to collapse
if its the boot ani just root if its the actual lg logo it is in the kernal somewhere which unlocked bootloader is required
TheMadScientist420 said:
if its the boot ani just root if its the actual lg logo it is in the kernal somewhere which unlocked bootloader is required
Click to expand...
Click to collapse
The boot logo, not boot animation. The LG logo. I already have bootloader unlocked and I am already rooted.
TheMadScientist420 said:
if its the boot ani just root if its the actual lg logo it is in the kernal somewhere which unlocked bootloader is required
Click to expand...
Click to collapse
Ok, so I can't find the boot logo (lg logo) within the kernel. I also don't get why it would be in the kernel, as the kernel is not loaded when the phone displays the LG logo.
seijinshu said:
Ok, so I can't find the boot logo (lg logo) within the kernel. I also don't get why it would be in the kernel, as the kernel is not loaded when the phone displays the LG logo.
Click to expand...
Click to collapse
it is in kernel, kernel is one of first things that have to be loaded, without kernel and modules it could not even display anything...
btw: cust/VDF_COM/poweron
https://forum.xda-developers.com/g4/help/stock-lg-g4-boot-animation-shutdown-t3168785
Flashing_Expert said:
it is in kernel, kernel is one of first things that have to be loaded, without kernel and modules it could not even display anything...
Click to expand...
Click to collapse
K. Now it is a matter of finding it in the kernel. Does anyone have an extracted kernel I can look at? After a while, I realized I have only looked inside the boot image. I also cannot extract the kernel for the life of me.
I thought it was in the kernel. I flashed a new kernel on my note 5 with note 7 port. But after flashin n7 port kernel. Now my initial boot says note 7. Lol i love it.
Flashing_Expert said:
it is in kernel, kernel is one of first things that have to be loaded, without kernel and modules it could not even display anything...
btw: cust/VDF_COM/poweron
https://forum.xda-developers.com/g4/help/stock-lg-g4-boot-animation-shutdown-t3168785
Click to expand...
Click to collapse
Yeah. It would not be in kernel as bootloader inits the display. Just note that download mode is not actually running on the kernel and yet it still displays. And I run lineage and that directory does not exist.
TheMadScientist420 said:
I thought it was in the kernel. I flashed a new kernel on my note 5 with note 7 port. But after flashin n7 port kernel. Now my initial boot says note 7. Lol i love it.
Click to expand...
Click to collapse
Exactly. I have a custom lineage os and I also have a custom kernel, which does not change anything.