Hi All
Im trying to change the very first splash screen that comes up on my MX Android TV box.
I know its found in the logo.img file which is in the update.zip but have been unsuccesful in unpacking/extracting rle/packing this file.
Ive managed to change the second splash screen (which is within the boot.img) using the dsixdas kitchen, but dont have a clue how to unpack the logo.img - any help/ideas would be much appreciated.
Cheers
GS
gunshot69 said:
Hi All
Im trying to change the very first splash screen that comes up on my MX Android TV box.
I know its found in the logo.img file which is in the update.zip but have been unsuccesful in unpacking/extracting rle/packing this file.
Ive managed to change the second splash screen (which is within the boot.img) using the dsixdas kitchen, but dont have a clue how to unpack the logo.img - any help/ideas would be much appreciated.
Cheers
GS
Click to expand...
Click to collapse
Hi, have you found a solution on how to do this? I'm looking for the same thing
logo.img (or logo.bin) is generally a RLE compressed image. There are many tools to unpack/repack, many of them allowing to load your own image, for example this (I've not checked that, just copying the link to you).
You can find all these tools by simply visiting this useful website
To flash new logo.img you can insert into update.zip or dd from recovery into correct partition. Just google it, is very simple to accomplish.
WARNING: be sure to flash the logo.img format which is expected by your phone, or you may end with a brick! I think this is a standard format (same for all devices) but I'm not sure about that.
Related
I tried to use splash flasher to flash some screens but on boot the image is scrambled?
{LCD}Stelios said:
I tried to use splash flasher to flash some screens but on boot the image is scrambled?
Click to expand...
Click to collapse
Are you use a right 24 bit bmp format?
Tried ones that I had on my DHD.
Had the same problem; Here's a quick how to:
Make sure your image is sized as 540x960 (so you'll lose a bit off of the sides, since the aspect ratio is different vs. the usual 480x800 that many HTC devices have been).
Use the 2nd option of SplashFlasher 1.0 to convert the PNG you have to custom.img. Ignore the warning that says the file should be a certain resolution.
Take the custom.img file and copy it into your fastboot directory. Rename it to new_splash.img
do this:
adb reboot bootloader
fastboot flash splash1 new_splash.img
fastboot reboot
(credit to jbrew78 at http://forum.xda-developers.com/showthread.php?t=1171290)
You should be all set! For some reason, the splashing from splashflasher doesn't work with our devices, but it's converting tool is the easiest for me.
This is my first attempt at a how to, so please let me know if there's anything I could help clarify, or if it doesn't work/what step you get stuck on.
Hope it helps!
Cheers for that bud, yeah the tool is handy it is a shame that it doesn't work with the Sensation. Just need to find out what I have messed up with the bootanimation now.
I put a new one in and now I can't work out how to do it again lol?
And that was really easy to follow and helpful thanks.
i use this way and it works
http://forum.xda-developers.com/showthread.php?t=1194690
Hello guys,
I'm new here, and I don't know if I'm posting on the right section, but I cannot find a "Mediacom Tablet" section of the forum.
I'm trying to alter the boot logo of my android tablet rom, I've extracted the boot.img file with a tool called "wendal" , and then I've extracted it with a tool called "extractboot" ... then I've swapped the "initlogo.rle" with my own logo (I've renamed it initlogo.rle of course), and then I've rebuilt the boot.img again (with "packboot").
Now, I've a "boot_new.img" ready to flash on my Mediacom Smartpad 720i .. So I've open RKAndroidTool, and I've selected my new boot image.. But my tablet fail to boot (of course I can still flash it back with stock fw)
I'm pretty sure that the problem is the offset in RKAndroidTool I don't know what to write exactly in the offset field :/
I've tryied with "0x00008000" , but since my modified Boot.img is bigger than the original one, I think that it fail for that reason
Any help please ? Thank you very much and sorry for my bad english
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
rhodesbauer said:
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
Click to expand...
Click to collapse
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
qwertyu123 said:
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
Click to expand...
Click to collapse
I used Root Explorer to look for both, recovery.img and *.img.
No result.
try this http://forum.xda-developers.com/showthread.php?t=2450045
Hello everyone,
I'm new to low-level Android hacking, so I guess I need some help.
What I am trying to do is getting the stock files from an LG E400, and modify 1-2 things, repack, flash, and see if it works for me.
My first step:
1) Rooting the LG E400
2) Flash CWM Recovery
3) Create a backup
4) Get boot.img from the backup.
So I have a boot.img (which I think is stock, because rooting does not modify the contents of the boot image as far as I know.)
After that, I followed this tutorial to extract the kernel and the ramdisk.
I used a hex editor for this. I saved the kernel and the ramdisk as separate files, and I tried to gunzip the ramdisk. That seemed to work. However, after that, when I try to run cpio on the file, I get a lot of "Malformed number" errors, and only two empty folders are extracted.
And that is where I'm stuck at.
Are the LG phone boot.img-s encrypted somehow? Am I doing something wrong?
If anyone can help me, I would be really grateful.
Thanks in advance
I was always kinda annoyed by the not matching boot logo. After the loader I could change the logo to the car manufacturer but the first seconds still showed "On vehicle navigation system". After installing the Malasyk 8.0 ROM I recognized a different boot logo. So a change was possible. After some playing around with various ROM tools I was able to change the logo (sorry, I don't remember the exact steps). After switching to the HAL9k ROM, the changed logo was gone. The old method didn't work with HAL as the boot loader with the logo was part of the signed update.zip and changing the logo of course breaks the signature.
So I played round with dumping various partitions and check for the logo. There is a way to change it:
NOTE: The slightest mistake in one of the steps WILL brick your device!!!
1. Dump the bootloader partition
2. Find the logo in the dump
3. Replace the logo in the dump
4. Write the new bootloader parition
In general it is a good idea to connect to the device using adb on your PC as typing on the on-screen-keyboard is error prone. dd commands have to be executed as root.
1a. dd if=/dev/block/mmcblk2p4 of=/storage/ext_sd/mmcblk2p4.bin
Note: Depending on your ROM or device the partition might be different. So if you don't find the logo there, try other partitions. Also adapt the of argument. I wrote the file to the "Music" SD card.
1b. Write down the file size. In my case it was exactly 16MB.
2a. Search the dump file for the string "BM6". I used HxD and found it atoffset F800.
2b. Dump everything starting as this offset to a new file and name it with the extension BMP.
2c. Open it with your favorite viewer (I use IrfanView) and check if it is the correct logo.
2d. Check the resolution. In case of the HAL9k 3.1 ROM it should be 800x480x24, for Malasky it was 1024x600x24
2e. Save the file there to a different name.
2f. Check the new file size. In case of the HAL9k 3.1 ROM it should be 1152054 bytes
3a. Create a logo of your choice with exact the same resolution.
3b. Check the file size. It must be identical to the one of the dumped BMP
3c. Replace the data in the compete dump. Make sure, you use the correct offset and use replace, not insert.
3d. Save the new dump and compare the file size. It must not be changed!
4a. Copy the file back on the SD card
4b. Write it back: dd of=/dev/block/mmcblk2p4 if=/storage/ext_sd/mmcblk2p4.bin
Note: if and of is now switched!
4c. Reboot
Just did mine in Hal9k rom.Thank you
Sent from my iPad using Tapatalk
NOTE: The slightest mistake in one of the steps WILL brick your device!!!
Hi,
just a thought of safety..
is it not better that you change that -boot- logo for all cars so that "everybody" can choose his car logo, instead or to prevent that men would make some a mistake which wouldl brick his headunit?
https://www.google.com/search?q=and...KHQHTDu8QsAR6BAgEEAE&biw=1280&bih=726&dpr=1.5
Thanks for this!
In my case, it was mmcblk2p7.
At first, I had a black screen, but file size and resolution was correct.
Somehow, I managed to boot the device again and then I tried another picture and it worked.
I don't know the difference between my first and second try...but I'm lucky that my device isn't bricked.
Maybe we find a safer way for this...
rezi09 said:
Thanks for this!
In my case, it was mmcblk2p7.
At first, I had a black screen, but file size and resolution was correct.
Somehow, I managed to boot the device again and then I tried another picture and it worked.
I don't know the difference between my first and second try...but I'm lucky that my device isn't bricked.
Maybe we find a safer way for this...
Click to expand...
Click to collapse
Great example of New member joining, reading articles, giving it a go and reporting back.
Wonderful but rare.
marchnz said:
Great example of New member joining, reading articles, giving it a go and reporting back.
Wonderful but rare.
Click to expand...
Click to collapse
Well, I'm new since 2009
Thx...it's a great forum with great people!
Pls support