Hi,
I wanna change the splash screen (boot logo) of my sony ericsson xperia active (st17i) , with FXP 152 CM 10 on it, I can't find the original logo.rle, I found the bootanimation but not the boot logo, can someone help me please? Thanks
Sent from my Xperia Active using xda app-developers app
u cant change kernel boot logo with just a simple copy pasting. its in ramdisk.
one has to unpack ramdisk from kernel, change the boot.rle in ramdisk and repack back ramdisk with kernel.
http://forum.xda-developers.com/showthread.php?t=2066539
First, start off by installing any linux distro (preferrably Ubuntu) and download android kernel kitchen - http://forum.xda-developers.com/showthread.php?t=1659584
In the kitchen, you have to first unpack the boot.img. Then you have an option to convert your (the one you want to put) png file to a rle file and replace the stock logo.rle file and then repack the ramdisk and create the boot.img. Flash it to your phone using fastboot and the following command - fastboot -i 0x0fce flash boot boot.img
Press thanks if I helped and good luck
Related
Anyone tried to flash a splash1 image on the xperia play yet?
This method:
http://forum.xda-developers.com/showthread.php?t=753788
I tried long ago to flash a splash, fastboot tells me the play has no splash1 partition, and i know no way to sign the .img with a se signiture, most splash1 converters i found, used the htc signiture..
Sent from my R800i using Tapatalk
u can easily change the splash image / static bootscreen / static bootlogo by changing the initlogo.rle/logo.rle file in the boot.img ramdisk...
DooMLoRD said:
u can easily change the splash image / static bootscreen / static bootlogo by changing the initlogo.rle/logo.rle file in the boot.img ramdisk...
Click to expand...
Click to collapse
I thought it was in the boot.img, we have been discussing it in this thread aswell http://forum.xda-developers.com/showthread.php?t=1064520 .
Doomlord, obviously we dont have the brains you have, if i have a copy of my boot.img, can you give us instructions on how to extract the .img. change the file and repack it??
AndroHero said:
I thought it was in the boot.img, we have been discussing it in this thread aswell http://forum.xda-developers.com/showthread.php?t=1064520 .
Doomlord, obviously we dont have the brains you have, if i have a copy of my boot.img, can you give us instructions on how to extract the .img. change the file and repack it??
Click to expand...
Click to collapse
[How-To] Make custom bootscreen/bootlogo (image to rle)/(rle to image)
aZuZu Small Tools 4 SE - All In One Place
I'm having trouble flashing a kernel. I've compiled the 2.3.4 kernel (faux's kernel, and i'm using ken's 2.3.4 ROM) and i am trying to fastboot the resulting zImage to my device with no luck. i keep getting either an error, or no action at all.
using the below command, the image is sent, bootloader mode, but just sits there forever.
Code:
fastboot boot zimage zImage
and below just gives an error such as FAILED: 0x30003000.
Code:
fastboot flash zimage zImage
i've searched the forum and see talk about needing the ramdisk, but i'm new to that. my nexus one i was able to just flash the zimage directly after compile with no ramdisk with it.
however i did give the ramdisk a shot. i took my nand backup, pulled the boot.img from it. then broke that up with an extract perl script i found from google, got the resulting ramdisk, which actually looked like the same size as the HKTW ramdisk, both at 152kb. but alas, i just get a boot loop when i use the ramdisk with the following command:
Code:
fastboot flash:raw boot zImage ramdisk.gz
so i'm kinda stuck here and hope someone could give me a pointer. thanks!
i had this while trying to flash xoom's kernel
Sent from my MB860 using XDA App
interesting so you think there is no solution and it has something to do with tegra devices? i can't imagine it's impossible else how are we making custom ROMs!
anyone else have hints? i doubt recovery matters, but i'm using CWM. i even tried wiping dalvik cache before the flash. since fastbooting a kernel doesnt use recovery but the bootloader, recovery prob does not matter either way.
anyone have the ramdisk they could send me? i'm using 2.3.4 ken's ROM. maybe i just goofed on extracting the ramdisk myself.
anyone have any additional advice or tips on the kernel zimage and flashing it to the atrix? i'm at my wits end here. i've tried for 5 days everything i could think of and just CANNOT flash the kernel that i compiled.
i also compiled it about 30 times thinking something screwed up. but seems like i just cant flash it to device. thanks.
use cwm? thats how I flashed the kernel. went perfectly.
also, are you unlocked?
Stephen Who said:
use cwm? thats how I flashed the kernel. went perfectly.
also, are you unlocked?
Click to expand...
Click to collapse
Well this is a zimage because I compiled the source and that's what's giving me trouble flashing to the phone.
I'd have to bundle into a flashable zip to use CWM and I need the ramdisk to do that.
Yes I'm unlocked.
Movd to proper section
Here is a (roundabout) way:
Not sure if you found an answer - but here is a roundabout way:
Start with an existing CWM kernel zip file and extract the boot image off it. Then follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=443994
to get the ramdisk from the image.
Now - since you compiled your own kernel, assuming you know your way around Linux - you might need to adapt the command to match your linux installation, paths, etc.
Also - You might want to use moto-fastboot instead of the stock android fastboot:
Code:
sudo moto-fastboot flash:raw boot zImage mynewimage.img-ramdisk.cpio.gz
where zImage is the zImage compiled by you, and the ramdisk.cpio.gz is the ramdisk you extracted. This is how I load my own kernels onto my Atrix - and has worked for me. I just use a standard ramdisk image - makes life easier
Cheers.
Hi,
Because i like to test many different Roms with kernels, i created my own script to flash properly with the recovery.
Often, the Kernels are available for a Rom in particular, in a zip file containing a boot.img with the kernels modules contained in /system/lib/modules
The problem is that to start, Android does not need that kernel, but also the image of a micro file system (zImage) containing startup instructions, but also a list of parameters to pass to the kernel.
The boot.img is the concatenation of the kernel with its startup parameters, and zImage.
To properly replace a kernel, so we need to retrieve the current settings, the current zImage, and reform the boot.img with the new kernel, and of course, replace the modules.
This recovery script make these step:
- Extract the kernel from the boot.img file
- Get the boot parameters of actual kernel.
- Get the actual zImage
- Rebuild the boot.img with new kernel, old boot parameters, old zImage
- Replace the modules in /system/lib/modules
- Flash the new boot.img
Before do that.
Download the kernel from other Rom, you want to flash
Extract from the zip file, boot.img and /system/lib/modules directory
Get my kernel_flash.zip
Extract it.
Replace the system/lib/modules content with the new one.
Replace the boot.img with the new one.
Rebuild you zip file with 7zip (www.7zip.org)
This zip file containing:
META-INF
boot.img
kernel
system
version.txt
And flash it under recovery.
I tested these method with Senses Roms, with AOKP or AOSP Roms. Always in my system started succefully.
You should be able to flash this kernel on any ROM (except the boot stock that has an offset of 256 bytes incompatible with the script)
As is, this kernel_flash.zip file contains a yoda kernel 2.1, overclocked to 1.5 Ghz, you can test with your ROM.
Sorry for my english.
Thank you to Google for translation assistance
Thank you for the kernel to yoda (my kernel_flash.zip contain 3.0.16-yoda_v2.1)
Thank you to all XDA developers who allowed me to further my understanding
looks promising, but does this work also for s-on users ? i dont know if you knew this already, but there is https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui&hl=en this app in playstore, which works for both s-on and s-off users, and also flashes recovery
gav-collins1983 said:
looks promising, but does this work also for s-on users ? i dont know if you knew this already, but there is https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui&hl=en this app in playstore, which works for both s-on and s-off users, and also flashes recovery
Click to expand...
Click to collapse
For s-on:
After flashing kernel under recovery, only /system/lib/modules files are copied
Keep in Recovery,
You need to flash the kernel with fastboot.
Open a terminal
with adb, pull the boot image:
Code:
adb pull /tmp/newboot.img boot.img
Restart in fastboot mode
Code:
adb reboot bootloader
Flash the boot.img file
Code:
fastboot flash boot boot.img
fxjumper said:
For s-on:
After flashing kernel under recovery, only /system/lib/modules files are copied
Keep in Recovery,
You need to flash the kernel with fastboot.
Open a terminal
with adb, pull the boot image:
Code:
adb pull /tmp/newboot.img boot.img
Restart in fastboot mode
Code:
adb reboot bootloader
Flash the boot.img file
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
would it flash the kernel if you are using 4ext recovery ?
Pacattack said:
would it flash the kernel if you are using 4ext recovery ?
Click to expand...
Click to collapse
My phone is S-OFF
4ext recovery flash the kernel.
I know 4ext dispose a S-ON mode to flash the boot.img on the first boot, but i don't know if it works in this case.
Try it
I have compiled a custom Kernel for my HTC Desire 200 unit from htc's source. After my kernel is compiled i get a zImage file. I then use Android Image Kitchen, to take a standard boot.img file and unpack it, replace the original zImage in it, repack and flash it via the fastboot command: "fastboot flash boot boot.img"
Fastboot then flashed the kernel, i reboot the phone and it boots and works to some extend. The changes i make is there (as an example, i can see the name change i have made in the kernel version), however WiFi is not working on the device with this custom kernel, and i believe this is because i need to somehow install the devices needed modules along with the kernel.
And heres my question. How can i create a zip file, that i can flash from Clockwork Mod recovery, that flashes the kernel, along with placing the modules where they belong? OR bundle the modules with a boot.img file that i can flash from fastboot ?
Basicly what i have i a zImage and modules, but i need to bundle it together for easy flash either via recovery (zip) or fastboot (img)
Can you assist me?
Quite surprised that this seems unsolvable yet also seems to be a thing every kernel developer has been dealing with ..
Hi
please let me know the procedure to unpack boot.img edit init.rc & repack boot.img & flash using sp flash tool. The main purpose is to change device id, serial & Android ID.
Pl advise.
Thanks in advance