I am using a sk17i with FXP CM7.2. I want to change my kernel splash screen. Ive tried to split the kernel, make an rle file, and combine it again with various scrips on the internet but i keep getting an error when I try to flash it using fastboot. Can someone please give me a step by step guide on how to create the rle image in the correct method and flash it onto my phone. I have seen that you can change the splash screen on HTC phones using fasboot directly, is there any way I can do it on SE and if not how do I correctly split and modify my kernel?
Related
I've got my Optimus T flashed with the void ROM now and I'm loving it. I've been playing around now with the boot animation and I notice that now there is an animated version of the LG logo that comes after the static logo and before the bootanimation.zip. I've got the bootanimation.zip figured out, but I'd prefer to go straight from the static LG logo to the beautifully simple "void."
Does anyone know where this animated logo is located and how it can be changed or removed? Thanks in advance.
Answering my own question.
The images are in /bootimages named opening_0[1-8].rle. These are rle encoded raw RGB files. See to565.c in the android git tree for some details on that RLE format.
Trying now to see if getting rid of those files gets rid of the boot animation...
Looks like these files are written anew every time from the boot.img. I have found how to unpack the boot image from /dev/mtd/mtd0, but I'm working right now on how to make a new one...
the boot images are in ramdisk you need to unpack boot.img modify ramdisk and repack boot.img
the command to unpack on linux is "./unpack-bootimg.pl boot.img" you need perl libraries installed
Yep, I can unpack the boot image and change the images but once I repack it, how can I flash it to the appropriate place?
take commands what you need from an update-script of a custom rom and flash it trough recovery
Any updates on this? I would also like to know an easy way to remove this animation.
irondevil said:
take commands what you need from an update-script of a custom rom and flash it trough recovery
Click to expand...
Click to collapse
This sounds like the easy answer. Anyone with more knowledge willing to do this for me? I guess we're just talking about a zip to flash to remove boot/shutdown animations and nothing else.
First , i want to completely debrand my phone ..i.e. remove boot-animation as well as that LG logo (which i think comes from /boot partition and can we change that??)
Second, is it possible to have Debian-like kernel log(bootlog) displayed when the phone boots up ??? Is there a workaround for that???
yes you can change bootanimation but you need to extract boot.img and modify ramdisk then repack boot.img
irondevil said:
yes you can change bootanimation but you need to extract boot.img and modify ramdisk then repack boot.img
Click to expand...
Click to collapse
He doesn't want to change the bootanimation, he wants to remove it and have android to boot in "verbose" mode instead, like linux does. To my knowledge, nobody has been able to do it yet.
rotorto said:
He doesn't want to change the bootanimation, he wants to remove it and have android to boot in "verbose" mode instead, like linux does. To my knowledge, nobody has been able to do it yet.
Click to expand...
Click to collapse
To boot in Verbose Mode is needed to enter into the Bootloader. It Lg Optimus One how, we, can enter into bootloader? Maybe it is blocked, as Nexus ONE?
the_best_hacker said:
To boot in Verbose Mode is needed to enter into the Bootloader. It Lg Optimus One how, we, can enter into bootloader? Maybe it is blocked, as Nexus ONE?
Click to expand...
Click to collapse
There is no need to get into bootloader mode: what you need is to compile a new kernel with fbcon enabled.
If anyone is interested, here is explained how to enable verbose booting on the Galaxy S. Adapting those instructions for the LGP500 shouldn't be difficult.
rotorto said:
There is no need to get into bootloader mode: what you need is to compile a new kernel with fbcon enabled.
If anyone is interested, here is explained how to enable verbose booting on the Galaxy S. Adapting those instructions for the LGP500 shouldn't be difficult.
Click to expand...
Click to collapse
thnx..but how do i go about editing the .config of the mik_os's kernel that i m using......Will just editing the .config of the present kernel without the need to recompile it and zip it???
You have to edit the config file, recompile the kernel and flash it on your phone.
I noticed for myself with custom ROMs there is no problem to flash a kernel zip
with Zimage or boot.img inside via recovery.Tried all available kernels and all works.
But if I do a restore to my rooted and S-Off stock ROM with stock kernel,
nothing works.First I flashed kernel zip with Zimage,then I got
Code:
Flashing New boot.img ...
assert failed: write_raw_image ("/tmp/newboot.img". "boot")
(Status 7)
Installation aborted
After this,I tried to flash a kernel zip with boot.img inside.This works,but
phone stuck at HTC splash image.
Also,after flashed the kernel zip with boot.img inside,the kernel zips with
Zimage inside works too,but also stucks at HTC splash image.
Phone details:
EVO 3D GSM, rooted by:
HBOOT 1.49.1107
revolutionary s-off
CWM 5.0.2.0
Any answers/solutions for this from the devs,why custom kernels don`t
work with rooted/S-Off stock ROM and stock kernel?
This should go to Q&A Section...
Stock ROM's have secured Boot Images, custom ROM Dev's unsecure the Boot Image to allow Root ADB commands.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
harpss1ngh said:
This should go to Q&A Section...
Stock ROM's have secured Boot Images, custom ROM Dev's unsecure the Boot Image to allow Root ADB commands.
Click to expand...
Click to collapse
So no solution to get a custom kernel working on rooted/S-Off stock ROM
with stock kernel?
harpss1ngh said:
This should go to Q&A Section...
Stock ROM's have secured Boot Images, custom ROM Dev's unsecure the Boot Image to allow Root ADB commands.
Click to expand...
Click to collapse
I could be wrong, but as far as I know this is partly true, although I might have misread.
I agree, completely 100% stock kernels from the manufacturer have secured kernels (boot images).
Ganii said:
So no solution to get a custom kernel working on rooted/S-Off stock ROM
with stock kernel?
Click to expand...
Click to collapse
The first 256 bytes of the kernel/boot.img are the signature/encryption on 100% stock kernels for this device. Since the first 256 bytes are encrypted, the standard Anykernel (zImage in .zip file with dd, etc.) method does not work. It will successfully dump the kernel from the boot partition but it will fail when parsing out the pieces due to the 256 bytes at the beginning, at least in previous/current state.
The only way I've seen to bypass this is by flashing an unsigned kernel. I've had success removing the first 256 bytes of the dumped/RUU kernel file and flashing. Once the user has an unsigned/unsecured kernel loaded in the boot partition, the Anykernel style (zImage, dd, mkbootimg.sh, etc) type kernel usually works.
These unsigned kernel files can be found in ROMs or separately in kernel .zip files, but they have to always be in the boot.img form the first time.
Some of this is my personal theory but it is based on my experiences. Welcome anybody else with experience to chime in, especially other kernel developers.
Hope my ideas make sense!
I also tried to flash boot.img,but doesn`t work.
http://forum.xda-developers.com/showpost.php?p=18686747&postcount=166
I think you might be typing the commands wrong. Have you tried
fastboot flash zimage??? Also did you unpack/unzip the .img to the correct directory??? Also did you do fastboot reboot boot loader???
Locked & Loaded
""Shooter on Deck""
Ganii said:
I also tried to flash boot.img,but doesn`t work.
http://forum.xda-developers.com/showpost.php?p=18686747&postcount=166
Click to expand...
Click to collapse
If the kernel is compiled and verifed working properly, flashing the boot.img should work as it completely overwrites the stock kernel image.
In comparison to the Anykernel method, where they dump the stock signed kernel and attempt to split out the ramdisk, cmdline and base, which will fail due to the 256 byte signature at the front of the kernel.
As a side note, I'm fairly certain it would be simple to modify the current tools, somebody might have already, to ignore the first 256 bytes of the kernel partition, and then use the rest of the image to split out the correct information. On a mass scale, the only hard part would be determining which kernels had 256 bytes of encryption/signed or which don't. The easiest solution would be to provide a flag to pass to the binary which splits out the imagine ... probably getting off topic.
Hope the extra details help clarify the process as far as I understand it!
Whats the fastest kernel out for the EXT3? And how about EXT4?
Hi there guys,
I am having an issue and was wondering if someone could point me in the right direction, maybe to a tutorial or some decent info on this.
Anyways, I have been tinkering around and teaching myself about building kernels, and roms and just a short while ago finished compiling my first kernel. I have the zImage, and i have tried adding the zImage to Koush's AnyKernel updater.zip but when i try and flash it says failed but is not displaying any errors (Using TWRP recovery) Or I am doing this wrong and need to unpack and repack boot.img with the new zImage?
Any help is greatly appreciated, Thanks!:good:
(edit) I am building on Fedora 17
You answered your own question.
Unpack the boty.img and repack with new zImage
So I was in the right ball park at least.
Sent from my SGH-T989 using Tapatalk 2
Will fastboot boot boot.img work on the galaxy note for testing a kernel? In case I have a borked kernel I want to take precautions so I don't brick my device.
Sent from my SAMSUNG-SGH-T879 using Tapatalk 2
No to fastboot.
With a broken kernel you should still be able to button combo into recovery and just flash a working kernel .zip
Or..at the very least be able to boot download mode and use Odin to flash the kernel.
I have gotten the boot.IMG all packed back up and when I flash it, my phone just hangs up at the white Samsung logo screen and does not go any further. Does something in the ramdisk have to be edited?
Tapa-a-Talkit it... Galaxy Note...4.2.1
Dear specialists on the XDA,
Normally I ask no questions in order to save the precious time of people, however this time I have a problem which I fail to understand and cannot resolve using the documentation available on the internet.
I have committed extensive reading and know how to build software but am simply missing a link here.
Trying to boot a home build kernel on a oneplus7 pro device with no luck so far.
Here is the situation so far: I have after hours of headaches successfully built myself a kernel straight from the stock sources. No alterations just using the msm8150-perf.defconfig file and build successfully with clang 9.0.5. There are only a few warnings nothing serious and the dtb has many warnings but I get what I need. I have done this before for my oneplus 3 and indeed the kernel was working.
Assuming the kernel is in a functional state. I used the latest version of android image kitchen to unpack the boot image which I extracted (from the right active slot) and replaced the kernel file and repacked the boot.img successfully into a new image file.
No luck after trying to boot into the image using fastboot. Screen hangs forever. Bootloader is unlocked btw
So far I have tried:
1. Signing the boot image using boot signer
2. Unpack/repack using android image editor (which signs the image)
3. Repack using different kernel image files from xda which I expect to be good and working
4. Flash signed image straight into active slot.
5. Completely read through the anykernel1, 2 and 3 scripts to find answers.
No matter what I try. Kernel does not boot. Either the fastboot screen hangs forever or the system reboots back into its currently working active slot.
I have to add that this bootimage contains magisk.
I am out of ideas. Please help me out. I hope that you can point me into a good direction.