[Guide] Change Boot Logo - MTCB Software Development

Please note that this has only been testing on MTCB Head units.
As with all mods, do so at your own risk. I take no responsibility if you brick your unit.
The instructions set out below work for me and I have done been successfully using this method for over a year now.
The unit I testing it on was an Xtrons TD696a RK3188 800x480.
I have determined that this process works on Malaysk 4.4.4 roms up to about March, the same with booroondook roms. As far as I can make out it works with all 5.1 custom roms
I haven't testing much on stock firmwares but I see no reason why it won't work with all of them.
If you follow the steps correctly the worst that can happen is that it will load with your custom boot logo once then revert back to the original without causing any harm to your unit.
Tool required
gimp - https://www.gimp.org/
HxD - https://mh-nexus.de/en/programs.php
RK3xxx firmware tools by SergioPoverony - http://vondroid.com/threads/rk3xxx-firmware-tools-by-sergiopoverony.14718/#post-44489
Terminal Emulator - http://www.apkmirror.com/apk/jack-palevich/terminal-emulator/terminal-emulator-1-0-70-release/terminal-emulator-1-0-70-android-apk-download/
The guide is split into 4 sections.
1. Modifying kernel to determine image size
2. Making the image
3. Importing image to kernel
4. Installing kernel to system
5. Modifying kernel.img inside backup.img
I think I have covered everything but no doubt as time goes on things will be changed or added.
I stress again As with all mods, do so at your own risk. I take no responsibility if you brick your unit.

Modifying Kernel to determine image size.
1. Using RK3xxx decompile the update.img you are using or going to use. Click "Select Img" then browse for your update.img.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1a. Then Click Extract.
2. Click on "Logo tools" then "Run logo Changer" (A new window will open).
3. Click on "File" then "Select kernel.ing" and browse for the kernel (it will be in temp/Android/Image).
4. If the kernel boot logo loads you should see an image in the right hand box
And in the box below you should see something like:
Code:
KernelPass:rkdroid
Kernel image size: 800 * 480
Supported Image Size: 800 * 480
If you see an image you are sooooooo lucky and can skip to Making the image section.
If the kernel boot logo doesn't load you will see no image and also in the box below something like this:
Code:
KernelPass:rkdroid
ÃÜÂë´íÎó!
ÔØÈëkernelʧ°Ü
5. Open Hxd and open kernel.img (click "File" then "Open" and browse for the kernel.img).
5a. Click "Search" then "Find" and search for "rk logo password" (don't include the quotation marks "") and make sure Datatype is set to "Text-string".
5b. In the last column (furthest right) highlight between the 1st character
after "password" and before the 1st character of "rk29_backlight" (you will see that the middle section has now been highlighted as well, a total of 44 pairs of characters).
Here's where it gets a bit complicated.
5c. In the middle section take a note of the 1st set of characters and last set. In the above picture they are 93 and C0.
Left click somewhere above to clear all the highlighted code.
5d. Now in the middle section highlight everything from the 1st pair and last pair. (the 2 pairs you took a note of above). You should have 44 pairs of characters highlighted now.
5e. Right mouse click and copy then left click somewhere above again to clear any highlighted characters.
5f. Click on "Search" then "Replace", change Datatype to "Hex-values" and in the 1st box (search for) right mouse click and paste. It should have pasted the 44 pairs of characters.
5g. Copy the below set of codes and paste into the 2nd box (Replace with).
Code:
31 57 8D EB 18 4B A9 41 D9 47 EA 2F 7E 60 B1 67 6C 6F 67 6F 2E 6E 6F 6C 6F 67 6F 00 00 00 00 00 FC F3 AC C0 60 BD AB C0 C8 42 AD C0
Then click "OK".
If the changes were successful the values in the centre and right hand columns will have changed to red.
Double check that the values in the centre column match:
Code:
31 57 8D EB 18 4B A9 41 D9 47 EA 2F 7E 60 B1 67 6C 6F 67 6F 2E 6E 6F 6C 6F 67 6F 00 00 00 00 00 FC F3 AC C0 60 BD AB C0 C8 42 AD C0
5h. Save and exit HxD. (A backup of the original kernel.img has been made if you balls it up at any point).
6. Open RK3xxx again. Click on "Logo tools" then "Run Logo Changer" (a new window will open).
7. Select "File" then "Select kernel.img". Locate the kernel you have just modified.
If you did everything correct in HxD your image should load in the right hand box.
You should also see:
Code:
KernelPass:rkdroid
Kernel image size: 800 * 480
Supported Image Size: 800 * 480
or
Code:
KernelPass:rkdroid
Kernel image size: 1024 * 600
Supported Image Size: 1024 * 600
Image size is very important before you can continue. I have found that some kernels although from a 1024x600 unit have a 800x480 boot logo and visa versa.
If after doing the steps above you find that is the case. You MUST use the image size stated (Supported Image Size even though it doesn't match your unit resolution.
You have been warned.
That is pretty much the hardest section. You can now go to Making the image.

Making the image
1. Now that you have established the image size make sure the image you intend to use for a boot logo is the exact same resolution.
2. Open Gimp and open the image you want to use as a boot logo.
2b. Click on "Image", "Mode", "Indexed".
2c. Set Maximum number of colours to 224 (very important). Then click "Convert".
If you find that the quality of the image isn't as good play around with the colour dithering settings
but never change the Maximum number of colours from 224.
2d. Click on "File" then "Export as".
2e. Click on "Select File Type (By Extension).
2f. Scroll down and select "PPM Image" then "Export"
2g. Data formatting select "ASCII" (Very Important), then "Export"
Getting easier, isn't it . Off to Importing image to kernel.

Importing image to kernel
1. Using RK3xxx click on "Logo tools", then "Run Logo Changer"
2. Click "File" then "Select kernel.img" and load the kernel.img you modified earlier.
3. Click on "File" then select "PNM logo image" and load the PPM image you created in Gimp.
4. If both loaded ok
Simply click on "Replace" and the image in the right side box should change to your custom logo. Click "Exit"
Forgot to take a screenshot of it but it will move the image in the left box over to the right.
And that my pedigree chums is your kernel.img ready to be installed on your unit.
Last but not least . Installing kernel to system.

Installing kernel to system
There is a difference between kitkat and lollipop so please make sure you follow the correct instructions.
1. Copy kernel.img to external_sd.
2. Open terminal emulator.
3a. If you are using Kitkat Android 4.4.4.
Type the following. Make sure to press enter between each line:
Code:
su
cd /mnt/external_sd
dd if=kernel.img of=/dev/block/mtd/by-name/kernel
3b. If you are using Lollipop Android 5.1.
Type the following. Making sure to hit enter between each line:
Code:
su
cd /mnt/external_sd
dd if=kernel.img of=/dev/block/platform/emmc/by-name/kernel
Regardless of which one you use, you should get a few lines of confirmation. Forgot to take another screenshot but it should look something like this:
Code:
12345+1 records in
12345+1 records out
12345 bytes transferred in 0.198 secs
If it failed then it will look something like this:
Code:
12345+0 records in
12345+0 records out
12345 bytes transferred in 0.198 secs
Fingers crossed that you have the 1st output result.
You can simply type "Reboot" in terminal emulator and it will reboot the system and again, fingers crossed you will see your nice new boot logo.
I have taken a lot of time and effort to put this guide together. I know it's not perfect but I hope it helps :good:

GREAT

Example Boot Logos for Head Units
New Boot Logos on Request! Be sure, that you use the correct resolution! All files are optimized to PPM format. So you can skip Step 2 "making the image"! All downloads are direct downloads from my server!
TOYOTA
DOWNLOAD 1024x600
VAUXHALL
DOWNLOAD 1024x600
VAUXHALL ASTRA
DOWNLOAD 1024x600

Will this work with "Update_4_4_4_FUSE_800X480_RK3066_40_MAL_12_06_2016_FIX_RADIO_MTCB" - Last modified 26-Jun-2016?
Thanks

cat2115 said:
Will this work with "Update_4_4_4_FUSE_800X480_RK3066_40_MAL_12_06_2016_FIX_RADIO_MTCB" - Last modified 26-Jun-2016?
Thanks
Click to expand...
Click to collapse
Read the OP
I have determined that this process works on Malaysk 4.4.4 roms up to about March, the same with booroondook roms. As far as I can make out it works with all 5.1 custom roms
I haven't testing much on stock firmwares but I see no reason why it won't work with all of them.
Click to expand...
Click to collapse

MTCD not MTCB work ?
Hello and thank you for your work.
I can use them on bootlogo MTCD not MTCB?
If so how to do it please? The basic procedure does not.
Thanks a lot.
Goodbye

zoxenrbg said:
Hello and thank you for your work.
I can use them on bootlogo MTCD not MTCB?
If so how to do it please? The basic procedure does not.
Thanks a lot.
Goodbye
Click to expand...
Click to collapse
I think I did say in the OP that it was only tested on MTCB units. I don't know what the differences are between the 2 so I really can't comment or give you advice on MTCD units.

I use an 5.1.1 RK3188 China directly.
MCU GS 1.6...
MTCD. I help you ?
Tell me what I have to tell you please do and how to put the logo annimé (I can not find procedure).
Thanks for your help !

Jaihoidundso said:
Example Boot Logos for Head Units
New Boot Logos on Request! Be sure, that you use the correct resolution! All files are optimized to PPM format. So you can skip Step 2 "making the image"! All downloads are direct downloads from my server!
VAUXHALL
DOWNLOAD 1024x600
VAUXHALL ASTRA
DOWNLOAD 1024x600
Click to expand...
Click to collapse
Hey man! I would really appreciate it if you could make a Toyota boot logo for me please? Thank you so mcuh!

jacobreed222 said:
Hey man! I would really appreciate it if you could make a Toyota boot logo for me please? Thank you so mcuh!
Click to expand...
Click to collapse
I believe this was meant so anyone could change the 1st boot logo. It is very simple as I have finished mine a couple hours ago. This post is not a request for logo but for a user make his/her own. Follow the OP procedures and you will not have any issues. This is my first time to extract anything from a ROM and change something and make it work.

bsavoir22 said:
I believe this was meant so anyone could change the 1st boot logo. It is very simple as I have finished mine a couple hours ago. This post is not a request for logo but for a user make his/her own. Follow the OP procedures and you will not have any issues. This is my first time to extract anything from a ROM and change something and make it work.
Click to expand...
Click to collapse
It's the 1st time I've written a guide so how did it go for you following the procedure?

Goose247 said:
It's the 1st time I've written a guide so how did it go for you following the procedure?
Click to expand...
Click to collapse
It was pretty straight forward. The steps were easy to follow and I had no issues with the guide. The only issue i had was with GIMP and resizing my image, for some reason i only got it to 800x500, but after playing around with it i found that I had already created and save a 800x480 resolution copy.

jacobreed222 said:
Hey man! I would really appreciate it if you could make a Toyota boot logo for me please? Thank you so mcuh!
Click to expand...
Click to collapse
Which resolution do you have?

Jaihoidundso said:
Which resolution do you have?
Click to expand...
Click to collapse
I have the JOYING 1024x600

jacobreed222 said:
I have the JOYING 1024x600
Click to expand...
Click to collapse
You can find your image here: http://forum.xda-developers.com/showpost.php?p=68535050&postcount=7 #7

Jaihoidundso said:
You can find your image here: http://forum.xda-developers.com/showpost.php?p=68535050&postcount=7 #7
Click to expand...
Click to collapse
Thank you so much man!

Related

Pagepool Changing , How to do it?

I found out many info after reading other threads about pagepool editing.
Jiggs open my ideas to read and have an info about pagepool editing.
With this site, he discussed it in a simple way:
http://buzzdev.net/read.php?71,31876
How To: Adjust PagePool for the XDA Atom
byJiggs
Tools:
1. Image file of the atom diskimage_Ver.nb0
2. Hex Editor
Instructions:
1. locate the first occurrence of the following hex values:
FF FF FF FF FF FF FF FF 9B 4F FF FF 64 B0 00 00
2. You will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4MB = 00 00 40 00
6MB = 00 00 60 00
8MB = 00 00 80 00
Our Atom comes with 8MB pagepool, after experimenting though, 4MB is okay, 2MB still works though... It's your choice.
3. Of course, you need to flash back the new ROM to your device.
Very simple instructions and straight forward.
Because of this I thought pagepool editing can be done only by editing NBO FILE and we really need to flash back our atom. Like discussed also in other forum device.
xda-developers > Elf > Elf upgrading etc.
PagePool Smart Changer
http://forum.xda-developers.com/showthread.php?t=326006
xda-developers > Hermes > Hermes upgrading etc.
PagePool Changer
http://forum.xda-developers.com/showthread.php?t=323269.
Now I Found out something, They tried to change pagepool on their device without flashing their ROM & they are succesfull.
xda-developers > Elf > Elf upgrading etc.
Change pagepool size! The EASY way!
http://forum.xda-developers.com/showthread.php?t=324594
vippie said:
Fist of all! All credits go to paradis_pal because he came with this solution for the prophet. I've just edited the offset to make it work for the touch (should work for the wing too as they share the offset)!
Also thanks to Paul from Modaco for his guide to do it manually!
It's now possible to change the pagepool size of a rom (4, 6, 8 and 12 mb) with this tool and just a soft reset afterwards!
I strongly recommend flashing USPL before doing this. It isn't necessary, but if you're device fails to start you want to be able to flash a rom from bootloader!
Steps to take:
- Download and Unpack "Change pagepool size TOUCH.zip"
- Connect your device with activesync!
- Copy EnableRapi.cab to your device and run it
- Make a safety backup using "backup.bat" (takes only a few seconds) and check if there's a file called "backup.nb" afterwards!
- run the bat (takes only a few seconds) with the pagepool size of your choice! (ex: 4mb = 4mb pool.bat)
- Soft reset and enjoy your new pagepool size!
If anything goes wrong you can flash back the old value with restore.bat!
Use at your own risk!
Click to expand...
Click to collapse
xda-developers > Prophet > Prophet mobile 6 >
Change PagePool for WM6 ROM 4.0.0.0 using ActiveSync
http://forum.xda-developers.com/showthread.php?p=1442907#post1442907
paradis_pal said:
if you want to test it then please backup first using backup.bat and restore by restore.bat if you have errors, then softreset
no need to hard reset or install new Rom, just soft rest
please use this at your own risk, don't do it unless you know what it is
first install EnableRapi.cab I'll attach it
in shortcut, this will change the memory for youlike this:
4mb pool.bat will make the total memory 52mb
6mb pool.bat will make the total memory 50mb
8mb pool.bat will make the total memory 48mb
12mb pool.bat will make the total memory 44mb the official.
it will take only few seconds, 1 or 2 seconds
only now softreset no need to hardrest or format
you may backup the old byte by backup.bat and restore by restore.bat
please don't blame me if you do anything wrong
and just wish me best of luck if this works for you as I
copyright to me
Click to expand...
Click to collapse
Im trying now to figure out if we can do this easy way to our ATOM. Im already trying to communicate to the thread and see their opinion.
Jiggs, can we do this in our atom? Just asking bro...thanks a lot
...if we manage to pull this off, COOL! It would save tons of time on testing and reflashing. I hope it can be done.
Also, if there was a way to simply flash a small part of the ROM without forcing a hard reset, I think we'd all love that too. The one thing I miss from the O2 Mini is that I could easily throw in a bootload screen without junking my entire install base.
generalriden said:
I found out many info after reading other threads about pagepool editing.
Jiggs open my ideas to read and have an info about pagepool editing.
With this site, he discussed it in a simple way:
http://buzzdev.net/read.php?71,31876
How To: Adjust PagePool for the XDA Atom
byJiggs
Tools:
1. Image file of the atom diskimage_Ver.nb0
2. Hex Editor
Hi Generalriden,
Did you get my pm re Resco Explorer 2007?
I've read all these, that's why I was asking about the procedure of changing the page pool without re flashing the rom, hoping that we can use it in our atom..It would be taxing to reflash..
Best Regards,
Click to expand...
Click to collapse
I have requested already the developer of the Smart Pagepool Changer. SharkinDark. Unfortunately, it doesn't work on our device yet. Although he said that the device info is already included in his program and should work.
When I use his program, it simply says its CID Locked. I'm not sure how to go about it. CID is new to me. All the while I thought we were CID unlocked because we can flash any ROM anytime.
You can follow the thread I requested from him since September 11, 2007.
http://forum.xda-developers.com/showthread.php?t=326006
I always update using SD Card (256mb) method. So, updating for me only takes 10min max especially when I do a lot of testing. BUT THIS REQUIRES THE EXACT FORMAT FOR SD CARD FLASHING. Renaming diskimage_ver.nb0 to diskimg.nbo IS NOT ENOUGH!
jiggs said:
I have requested already the developer of the Smart Pagepool Changer. SharkinDark. Unfortunately, it doesn't work on our device yet. Although he said that the device info is already included in his program and should work.
When I use his program, it simply says its CID Locked. I'm not sure how to go about it. CID is new to me. All the while I thought we were CID unlocked because we can flash any ROM anytime.
You can follow the thread I requested from him since September 11, 2007.
http://forum.xda-developers.com/showthread.php?t=326006
I always update using SD Card (256mb) method. So, updating for me only takes 10min max especially when I do a lot of testing. BUT THIS REQUIRES THE EXACT FORMAT FOR SD CARD FLASHING. Renaming diskimage_ver.nb0 to diskimg.nbo IS NOT ENOUGH!
Click to expand...
Click to collapse
thanks jiggs...
Hi,
Used hex editor and changed the pagepool frm 4mb to 8mb and flashed . No problem .Though program memory is increased In Setting---> system info shows 4mb pagepool , Can this be changed though it does not matter?
hope sharkindark in the forum mentioned by jiggs help us so we can do the easy way...
chaksu said:
Hi,
Used hex editor and changed the pagepool frm 4mb to 8mb and flashed . No problem .Though program memory is increased In Setting---> system info shows 4mb pagepool , Can this be changed though it does not matter?
Click to expand...
Click to collapse
info found in version.txt. you need to dump it and rebuild rom using mamaich tools.
jiggs said:
I have requested already the developer of the Smart Pagepool Changer. SharkinDark. Unfortunately, it doesn't work on our device yet. Although he said that the device info is already included in his program and should work.
When I use his program, it simply says its CID Locked. I'm not sure how to go about it. CID is new to me. All the while I thought we were CID unlocked because we can flash any ROM anytime.
You can follow the thread I requested from him since September 11, 2007.
http://forum.xda-developers.com/showthread.php?t=326006
I always update using SD Card (256mb) method. So, updating for me only takes 10min max especially when I do a lot of testing. BUT THIS REQUIRES THE EXACT FORMAT FOR SD CARD FLASHING. Renaming diskimage_ver.nb0 to diskimg.nbo IS NOT ENOUGH!
Click to expand...
Click to collapse
i f we can only find out how to unlocked, we can do this...even sharkindark cannot say something regarding this :-(
I cant do it with my exec, hic hic (
OMG i didn't understand anything
scounter said:
I cant do it with my exec, hic hic (
Click to expand...
Click to collapse
you really cant, even us in our atom

[HOWTO] GT-I9100 Free SIM Unlock via nv_data.bin by Odia

Free SIM Unlock for SGS2 by Odia. (ONLY for HW Version MP 1.200)
1. Root your phone.
2. Extract your nv_data.bin
3. Look at the file with an hex-editor and goto offset 0x181460 (Ultra Edit, HxD, Hex-Workshop etc)
4. Take the hashes from 0x18146e (20 bytes), 0x18148e, 0x1814ae, 0x1814ce, 0x1814ee
5. If the hash is 7D 3E 17 CF CD 81 6C AC D4 E0 25 FA A6 50 04 FD D1 7D 51 F8 ignore it since that is 00000000
6. Put the hash into the BF exe for example:-
ighashgpu.exe /h:EF63BF26E2382917D96850CCF9632458EE6E6C77 /t:sha1 /c:d /max:8 /min:8 /salt:0000000000000000
and wait for it to finish, do that for each hash which is not zeros, the Found password: [50681318] is the code.
7. Put unaccepted simcard in the phone and when it asks for the unlock code enter them in order
8. Job done, phone is now unlocked for free.
If you cannot find a block which looks like hashes @ 0x181460, then search for SSNV and add 5216, but from the files which I have seen the block appears to be fixed @ 0x181460.
If it will not accept the code which you believe to be correct, it means the attempts have been used up, so you need to use the MCK code to unfreeze your phone, note it will not request unfreeze code, just say network lock unsucessful even your code is valid. (MCK HASH is @ offset 0x180049)
Added an example for what you need to look for.
Mastercode
Dynamic located PERSO section, holds the mastercode (MCK / unfreeze), search for PERSO and look for a hash, can be multiple old sections, added screendump with an example.
MCK HASH is also in the SSNV section @ offset 0x180049
Direct Offsets
GT-I9100
NET 0x18146e -
SUB 0x18148e -
SP 0x1814ae -
CP 0x1814ce -
MCK 0x180049 -
GT-I9000
NET 0x18154b -
SUB 0x18155f -
SP 0x181573 -
CP 0x181587 -
MCK 0x1815af -
If this saved you a few quid, maybe you would like to buy me a beer
View attachment 602403
View attachment 602464
I could not have made this solution and proved my theory without the special help from pulser_g2 and Fall Guy.
I have been advised by pulser_g2 that Chainfire will make a software solution next week using this information.
(APK is here http://forum.xda-developers.com/showthread.php?t=1092451)
Im happy to test for you. Mine is locked, tried tmobile earlier today, and it required a code, im rooted so i can provide anything.
nintendolinky said:
Im happy to test for you. Mine is locked, tried tmobile earlier today, and it required a code, im rooted so i can provide anything.
Click to expand...
Click to collapse
Grab that file from the device and pop me a PM. I presume you know how to get ADB up and running?
OK. Sorta bad news. I can't see a way to retrieve the code itself from the file...
On another note, I DO notice that at address 0x181468, we see the semi-familiar pattern of FF 01 00 00 00 00 ...
On an unlocked phone, that was FF 00 00 00 00 00 (I checked earlier)
This fits in with the information at http://forum.xda-developers.com/showthread.php?t=761045, namely "Change any 0x01 to 0x00 (or 0x00 to 0x01 to lock for warranty)"
That suggests there is a possibility a free unlock could be gained by editing this file. But there would likely be consequences. As such I'm not going to recommend that, nor give instructions for it... If anyone chooses to, they do it 100% at their own risk, and should bear in mind that they NEED a backup of that and the corresponding md5sum first.
But I can't see an unlock code in plaintext
Anyway, that should be food for thought for someone who has a desire to mess about with their device. I won't be trying it for now, and I recommend you don't unless you know what to do to fix this, and are aware you are messing with stuff I don't know much about...
P
pulser_g2 said:
OK. Sorta bad news. I can't see a way to retrieve the code itself from the file...
On another note, I DO notice that at address 0x181468, we see the semi-familiar pattern of FF 01 00 00 00 00 ...
On an unlocked phone, that was FF 00 00 00 00 00 (I checked earlier)
This fits in with the information at http://forum.xda-developers.com/showthread.php?t=761045, namely "Change any 0x01 to 0x00 (or 0x00 to 0x01 to lock for warranty)"
That suggests there is a possibility a free unlock could be gained by editing this file. But there would likely be consequences. As such I'm not going to recommend that, nor give instructions for it... If anyone chooses to, they do it 100% at their own risk, and should bear in mind that they NEED a backup of that and the corresponding md5sum first.
But I can't see an unlock code in plaintext
Anyway, that should be food for thought for someone who has a desire to mess about with their device. I won't be trying it for now, and I recommend you don't unless you know what to do to fix this, and are aware you are messing with stuff I don't know much about...
P
Click to expand...
Click to collapse
Scared are we?
Pretty understandable tbh, I was kinda hoping it was as easy to unlock as the SGS but maybe there is still a way...let's hope so.
Just want to say, hex editing doesnt work. Doesn't detect sim and you get no signal, just put old file back and all works. Looks like we're gonna need another fix.
Quick question, can anyone who has an unlocked device please send me there nv_data.bin.
I want to see if there are any other differences that could be keeping it locked.
dh2311 said:
Just want to say, hex editing doesnt work. Doesn't detect sim and you get no signal, just put old file back and all works. Looks like we're gonna need another fix.
Quick question, can anyone who has an unlocked device please send me there nv_data.bin.
I want to see if there are any other differences that could be keeping it locked.
Click to expand...
Click to collapse
I diffed an unlocked and locked one, and there's a lot of differences at binary level
I would need to ask the guy whose unlocked nv_data I borrowed if he was OK with that, or see if someone else has one...
Also, I did think. Perhaps it "rejects" the file if the MD5 thing doesn't match. If it's a salted MD5, then it could check the md5 of the bin file salted against a "secret" string, and then compare to the contents of the md5sum file...
When I tried putting the old file back i used all the same commands, and it said there was no md5 sum. Which would be expected to be honest. But maybe it requires one. Ill try again this time leave the md5. Doubt it'll work, but its worth ago
EDIT: Faliure again!
Also as a note, cannot be anything to do with the md5 sum, just removed and it still works, so it cannot be checking values against it.
dh2311 said:
Also as a note, cannot be anything to do with the md5 sum, just removed and it still works, so it cannot be checking values against it.
Click to expand...
Click to collapse
OK. So it seems to be checking this file is "valid" somehow then...
pulser_g2 said:
OK. So it seems to be checking this file is "valid" somehow then...
Click to expand...
Click to collapse
is the file size identical? That's a usual standard check for validation.
risq said:
is the file size identical? That's a usual standard check for validation.
Click to expand...
Click to collapse
Should be. We are switching a bit from 0 to 1 - not adding anything
You can have my nv_data.bin if you want... my handset used to be locked to O2 but has been unlocked.
(and I've manually changed the ProductCode by editing nv_data.bin as well, not that that should make a difference)
Let me know, and I'll PM it to you
stuclark said:
You can have my nv_data.bin if you want... my handset used to be locked to O2 but has been unlocked.
(and I've manually changed the ProductCode by editing nv_data.bin as well, not that that should make a difference)
Let me know, and I'll PM it to you
Click to expand...
Click to collapse
Yeah it's worth a shot. Do you have your original file as well? This suggests you managed to edit it fine, and it still worked...
We have tried switching the flag for locked to 0x00, from 0x01, but it didn't work. Would be interesting to see the file though after using a code, to see if the flag is now at 0x00
Really what we might need is a BEFORE and AFTER from an unlock.
ie. anyone getting a code, could you get a dump of this file BEFORE the unlock, then enter the code, and then RE-dump to another file. Call them before and after perhaps? Then we can see what actually happened after the unlock - perhaps a checksum gets re-calculated, or a second "backup" bit was flipped that we missed?
My email, for anyone wanting to send their file (it's only 2 MB so goes fine as an attachment) is (the lines stop OCR gathering it for spam =D)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Email on its way
Something tells me it wont be as easy as on the previous Galaxy S. Remember, the Exynos sports an in die crypto engine.
stuclark said:
Email on its way
Click to expand...
Click to collapse
Will look at yours shortly
mathieulh said:
Something tells me it wont be as easy as on the previous Galaxy S. Remember, the Exynos sports an in die crypto engine.
Click to expand...
Click to collapse
Per http://forum.xda-developers.com/showpost.php?p=13526163&postcount=13 it is evidently possible to edit nv_data.bin and have the phone still work...
stuclark said:
Email on its way
Click to expand...
Click to collapse
any chance of emailing me the nv_data aswell?
mathieulh said:
Something tells me it wont be as easy as on the previous Galaxy S. Remember, the Exynos sports an in die crypto engine.
Click to expand...
Click to collapse
Hey Math,
there are I9103-devices with tegra2-chipsets out there. Not sure how different the firmware would be for those but I guess samsung had to find a way to make the one mechanism work for both sgs2-devices...

[Tutorial] New Motorola Logo by Fabio PAB

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Requirements]
1. Motorola drivers installed
2. Uncompressed file.
[Downloads]
Motorola drivers
New Motorola Logo by Fabio PAB
[Instructions]
1. Download files LOGO
2. Extract to a location easily accessible
3. Start the device in fastboot mode
(With the unit off, press VOL UP + POWER
Select AP Fastboot (Volume - Volume + moves and selects))
4. Open the file VAI.bat
5. Follow the installation steps ('s only 3 Enter)
Bonus:
Logo Moto X by Fabio PAB
Download:
http://www.mediafire.com/?lf05xcl7ey38h3e
Only replace the logo.bin mod topic and have applied.
Credits: Fabio PAB Forum Portal Android Brazil
If copy, cite CREDITS.
Hey Fabio, you think you could please make a logo bin file based on an image that has the correct motorola mobility colors in the logo, like these ones do, please? Thank you so much. ,)
ajape said:
Hey Fabio, you think you could please make a logo bin file based on an image that has the correct motorola mobility colors in the logo, like these ones do, please? Thank you so much. ,)
Click to expand...
Click to collapse
Id kill to see someone make a bootanimation out of this. Maube with the ring spinning? I like my bootloader unlocked warning bootlogo though, dont really wanna change it. is it possible to make a single, stationary image into a bootanimation?
ajape said:
Hey Fabio, you think you could please make a logo bin file based on an image that has the correct motorola mobility colors in the logo, like these ones do, please? Thank you so much. ,)
Click to expand...
Click to collapse
Thanks friend
fabiobatera said:
Thanks friend
Click to expand...
Click to collapse
Err... Well of course, you´re more than welcome my friend, but... can you do it, please, or is it not possible for some reason? Thank you...
ajape said:
Err... Well of course, you´re more than welcome my friend, but... can you do it, please, or is it not possible for some reason? Thank you...
Click to expand...
Click to collapse
Posted the mod. already with the corrected image.
Thanks
fabiobatera said:
Posted the mod. already with the corrected image.
Thanks
Click to expand...
Click to collapse
Wow, mighty fast... lol thanks buddy! Oh! And it looks really good, thanks again! ;D
ajape said:
Wow, mighty fast... lol thanks buddy!
Click to expand...
Click to collapse
I thank you.
Hey Fabio, would you perhaps happen to know why there is an interruption between the appereance of the boot screen and the start of the animation? I distinctly remember that while using the original red motorola logo, the transition to the animation was completely seamless, to the point that the logo itself appeared to dissolve and convert into the first part of the animation. Now, there are three seconds of black empty screen between one and the other, which is strange? I remember in the old HD2 there were actually two stages for the boot screen, and if you only loaded one of the graphics there would be a black gap between the bootscreen and the animation as well, Could something similar be the issue here, perhaps?
ajape said:
Hey Fabio, would you perhaps happen to know why there is an interruption between the appereance of the boot screen and the start of the animation? I distinctly remember that while using the original red motorola logo, the transition to the animation was completely seamless, to the point that the logo itself appeared to dissolve and convert into the first part of the animation. Now, there are three seconds of black empty screen between one and the other, which is strange? I remember in the old HD2 there were actually two stages for the boot screen, and if you only loaded one of the graphics there would be a black gap between the bootscreen and the animation as well, Could something similar be the issue here, perhaps?
Click to expand...
Click to collapse
friend, since this time difference may be due to the bootanimation, now when I see the difference in 3 segungos not imply anything, at least not bothering me.
Test with another bootanimation and check that decreases this time, because I am currently using the google.
hug.
It's the boot animation, I see practically no delay from my Atrix HD...
Oh, and thanks for making this awesome logo for us to use :3
53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
That's really strange, because when I use the original Motorola red logo there is no such delay in place, it seems to melt seamlessly into the red color of the first frames of the boot animation. Anyways, you should be thanking Fabio, because all I did was get the graphics correctly but Fabio was the one that actually made it into a usable boot screen
Sent from my XT925 using xda app-developers app
This is great! Thanks!
Sent from my XT926 using Tapatalk 4 Beta
@fabiobatera Could you please put together a guide showing how to do this so we can make our own? Thanks.
Everything work, thanks a lot!
ajape said:
Hey Fabio, would you perhaps happen to know why there is an interruption between the appereance of the boot screen and the start of the animation? I distinctly remember that while using the original red motorola logo, the transition to the animation was completely seamless, to the point that the logo itself appeared to dissolve and convert into the first part of the animation. Now, there are three seconds of black empty screen between one and the other, which is strange? I remember in the old HD2 there were actually two stages for the boot screen, and if you only loaded one of the graphics there would be a black gap between the bootscreen and the animation as well, Could something similar be the issue here, perhaps?
Click to expand...
Click to collapse
like fabio said i would think this is due to your bootanimation.
im on carbon rom and i done see any interruption between motorola logo and the bootanimation
hugodefcon said:
like fabio said i would think this is due to your bootanimation.
im on carbon rom and i done see any interruption between motorola logo and the bootanimation
Click to expand...
Click to collapse
I'm not too sure, unless it's something related to my Rom that is. I mean, lately I've tried many boot animations, and I have the same delay in ALL of them so far Here, take a look:
Add new logo Moto X by FabioBatera
Hug.
Must, flash... Thank you!
53 65 6e 74 20 66 72 6f 6d 20 6d 79 20 41 74 72 69 78 20 48 44 20 75 73 69 6e 67 20 74 61 70 61 74 61 6c 6b 2e 2e 2e
So Sweet!!!
fabiobatera said:
[Requirements]
1. Motorola drivers installed
2. Uncompressed file.
[Downloads]
Motorola drivers
New Motorola Logo by Fabio PAB
[Instructions]
1. Download files LOGO
2. Extract to a location easily accessible
3. Start the device in fastboot mode
(With the unit off, press VOL UP + POWER
Select AP Fastboot (Volume - Volume + moves and selects))
4. Open the file VAI.bat
5. Follow the installation steps ('s only 3 Enter)
Bonus:
Logo Moto X by Fabio PAB
Download:
http://www.mediafire.com/?lf05xcl7ey38h3e
Only replace the logo.bin mod topic and have applied.
Credits: Fabio PAB Forum Portal Android Brazil
If copy, cite CREDITS.
Click to expand...
Click to collapse
I absolutely love this logo! Thanks a bunch!!!

[WIP]LOGO.bin File Format and Modding

I haven't had enough to get a One now, but I'm pretty interested in the phone. Yesterday I saw a thread on Chinese forum, saying that LOGO.bin contains the image shown in fastboot mode, and thus everyone can choose his preferred image (like CM's) even if he uses ColorOS. So I tried to extract the bitmap from LOGO.bin and replace it with my own picture.
Now I've succeed PARTIALLY in identifying the BIN file format and extracting the images. There's no enough time to dig into replacing the pictures though, but I think it won't be hard.
Here is what I find, for those "aggressive" themers and ROM devs who want custom boot splash screen:
The BIN file starts with the following structure:
C:
struct SPLASHHEADERINDEX {
char magic_code[8]; // = { 'S', 'P', 'L', 'A', 'S', 'H', '!', '!' };
int img_width;
int img_height;
int reserved; // What's this? I haven't figured that out.
int img_offset[6];
char padding[468]; // The header is 512 bytes. Thanks [user=5757424]@chillstep1998[/user] !
};
Right after this structure, the raw data of boot splash image begins. Every pixel is described by 3 bytes in B-G-R order. The pixels begin at the upper left corner and then stored in the order of left to right & up to down. You can read (img_width * img_height * 3) bytes and write them into a BMP file. NOTE that BMP files require 4-pixel alignment for every horizontal row (Google that for details, otherwise you will get a "Broken image" info in image viewers) In order to avoid this problem, I wrote a simple program in VB.NET and used Bitmap.SetPixel and Bitmap.Save to solve it.
This is the VB code for this procedure. (I can't do GUI programs in C++...)
Code:
Dim bmp As New Bitmap(img_width, img_height)
Dim color As Color
For y = 0 To img_height - 1
For x = 0 To img_width - 1
b = fs.ReadByte 'fs is the FileStream of BIN file. Already sought to correct offset.
g = fs.ReadByte
r = fs.ReadByte
If b = -1 Then b = 0
If g = -1 Then g = 0
If r = -1 Then r = 0
color = color.FromArgb(r, g, b)
bmp.SetPixel(x, y, color)
Next
Next
There are some zeros after (img_width * img_height * 3) bytes. I don't know what's for...
Then let's look at the other images. Their offsets are in the img_offset array of SPLASHHEADERINDEX. They have headers like this:
C:
struct SPLASHHEADERNONINDEX {
char magic_code[8]; // "SPLASH!!" without \0
int img_width;
int img_height;
int reserved; //Still don't know
char padding[492];
};
Right after the structure is the raw data. Process that as mentioned above.
The image at img_offset[0] is the one shown in fastboot mode
[1] is AT current test (original Chinese: AT电流测试. What's AT?)
[2] is RF test
[3] is WLAN test
[4] is charging
[5] is low battery warning
Previews for new images are coming soon...
However: there is one bug: the images extracted are "mis-placed". You need to move 0x0 to 164xHEIGHT (163xHEIGHT maybe) area to the right side of the image to get the correct pic. The images extracted from ColorOS' LOGO.bin are listed as follows:
SPOILER:
[0]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[1]
[2]
[3]
[4]
[5]
Boot splash
Does anyone know the cause of this mis-place problem? Although that can be solved easily in the code, but it's not very reliable. Maybe it's related to the "reserved" member?
Since the format is rather simple, modding and repacking will be easy. When I get some free time I'll make a tool for this...
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
dlhxr said:
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
Click to expand...
Click to collapse
Can't come up with any reason why there should be signature check for logo, especially when we can use home-made modem fimwares and kernels without any problem... But it's worth considering since there's "reserved" member. ColorOS gets 0x00 0x00 0x00 0x00 and CM 0x00 0x00 0x00 0x01 in boot splash's "reserved" int. Haven't checked other 6 images though.
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
treChoy said:
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
Click to expand...
Click to collapse
Wow I didn't notice it before... This thread is revealing secrets of the magic and pushing it further
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
updateing said:
Wow I didn't notice it before... This thread is revealing secrets of the magic.
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
Click to expand...
Click to collapse
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
treChoy said:
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
Click to expand...
Click to collapse
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
updateing said:
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
Click to expand...
Click to collapse
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
treChoy said:
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
Click to expand...
Click to collapse
I have once seen somewhere that you can find specific .hex file (e.g. MPRG8960.hex for MSM8960) to download into the phone by QPST Service Programming. Then the phone will boot into mass storage mode, where computer will recognize the phone as a removable disk drive. Now the whole internal storage is "mounted" on the computer and you can use dd to restore then.
(Google'd and it says only QHSUSB_DLOAD need the hex file. QHSUSB_BULK should be mounting the internal storage to computer automatically and dd will be available. Not sure about that. Example: http://forum.xda-developers.com/showthread.php?t=2582142&page=1)
yeah the header is 512 bytes. Now the images are all correct :victory:
Flashing a bad LOGO.bin did send me to the QHSUB_DLOAD mode and I tired rebooting holding down all three buttons. It did seem to work but after a bit it seemed to just boot on its own. Then I just used an adb shell to run dd commands to flash the proper .bin and all has been well since then
Still have been to busy with our newborn to look into anything deeper but between this thread and the one by @chillstep1998 and treChoy and other it looks to be all good!
Glad all is coming together on this end, keep up the great work all
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
m9j_cfALt said:
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
Click to expand...
Click to collapse
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
updateing said:
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
Click to expand...
Click to collapse
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Reive said:
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Click to expand...
Click to collapse
I don't have a OPO to test, all these analysis are theoretical. So I may not be able to help. Sorry...

modified splash.img dont work? try logo.img_Maker for Mi5

Hello everybody
First i dont own a Mi5 but in the newer version of the MIUI V8 Android 7 there is the problem that
a modified splash.img does not change the bootlogo which is shown on boot.
A friend of me (**@[email protected]**) asked if i could try my luck to get a new bootlogo on his phone. So i screwed around build a kernel and tried and tested... till i opened the logo.img file from the rom with a hex editor and tried to understand its header data.
With help from **GokulNC** i figured out how the file is build ( Thank you for that Goku! )
So i was able to rebuild the file with a modified script.
It seems to work!
But i could only test it at Hoschis phone so please feel free to write if something do not work or if there are errors or bugs.
For Windows i edited Gokus tool that it reads 5 pictures from its "pics" folder. ( put your pictures there and name them logo1.png till logo5.png )
I am not familiar with the windows powershell ( ok i wasnt with python either... ) so if somebody could write it better please tell me.
I tested it in a virtual machine with windows7 and was logged in as admin ( if somebody want to know ).
Instead i wrote a tool with a gui for linux. You can use one picture for all or set every single one.
You can adjust the resolution of each picture if you like.
I tested it on Mint and on a nacked virtualized Ubuntu.
Both tools can build a update.zip to easily install your new bootlogo.
How to use Logo_img_Maker for Linux
download the Logo_img_Maker_Linux.tar and untar it to your homefolder.
In the Logo_img_Maker_Linux folder check that the makeLogo.sh script is marked executeable.
Now start the Script with a double click ( run in terminal ) or start it with "./makeLogo.sh"
On start the script check if all necessary additional software is installed and if not try to install it with the apt-get tool.
To run the script succesful following programms are needed:
python; python-imaging; python-pit; imagemagick; zenity; zip
If a error occur the script shows it in the terminal window and maybe ask for your superuser password to install the missing things.
You can also run: "sudo apt-get install python python-imaging python-pit imagemagick zenity zip -y" first to set up your system.
How it works:
At first you see a Welcome screen. Click ok to get to a file selection dialog where you can select the .png file which will get your new bootlogo.
After that you can adjust the resolution if you like. Your original picture dont get edited (the script copy it first to a temporary folder).
If you dont want to let the "keep_size" radiobutton active and only press ok then.
So now you can decide if you want to use the selected picture for all slots in the logo.img file or to put a different for every single slot.
If you want more to know about it read "logo.img explained" in this readme
If you select
one4all:
your before selected picture get used for logo Nr.1
The Script resizes the other 4 to 161x321 to save space on disc
add more:
you have to select the other 4 pictures one after another and set its size like you did with the first one. Of course the sizes can differ
for each picture.
When you are done with one of the two options the logo.img get build.
If that was successful you will get asked if you want to generate a update.zip for your custom recovery.
If you dont want to the logo.img can be found in the output folder.
If you click yes the flashable zip get generated in the output folder too.
How to use Logo_img_Maker for Windows
I only have Windows in a virtual machine to test it but it should work.
I have had it running with the administrator account and it build well... some others had proplems.
Download the Logo_img_Maker_Windows.rar and unrar it
then put your 5 .png pictures in the pic folder and rename them to logo1.png logo2.png logo.3png logo4.png logo5.png
start the CREATE_LOGO.bat to build your logo.img / update.zip after that
Ok i have took this script directly from **GokuINC**s work. the only difference is
that the batchscript estimates logo1.png till logo5.png directly and dont ask if there is a file.
The direct link to **GokuINC**s work:
https://forum.xda-developers.com/mi-5/how-to/guide-how-to-create-custom-splash-t3425054
logo.img explained:
the original logo.img header got explained by **GokulNC** from xda-developers.com - big thanks
- without him this all could not have been possible!
The header from ori file is:
SPLASH!!
Width (of 5 pictures)
Height (of 5 pictures)
SUPPORT_RLE24_COMPRESSIONT (of 5 pictures) (1 means it is RLE encoded, 0 means RGB24)
Payload size/4096 (of 5 pictures)
(Offset/4096)-1 (of 5 pictures)
And the funny thing my script do:
SPLASH!!
Width (of 5 pictures)
Height (of 5 pictures)
SUPPORT_RLE24_COMPRESSIONT (of 5 pictures) (1 means it is RLE encoded, 0 means RGB24)
(Offset/4096)-1 (of 5 pictures)
and it works on "MIUI V8 Android 7" with a Mi5 (gemini)
I first tried to rebuild it like Gokus example ( and of course - in the hex editor it was clear the same as in the original logo.img ..
ok different sizes but all was calculatebale and logical)
but it didnt work....
So i poked around and got this working solution - tested on **@[email protected]**s Mi5
There are many things that arent clear as they should - but it works somehow
It shows the bootlogo equal if you boot to your system or your recovery.
I dont know really if the 5 pictures are all the same but different sizes or if they are different.
The original resolutions are:
logo picture 1 = 161x321
logo picture 2 = 558x992
logo picture 3 = 178x350
logo picture 4 = 1080x1920
logo picture 5 = 1080x1920
Update 04.06.2017 :
Windows tool now v0.2 = fixed installer script
XDA:DevDB Information
Mi5_logo_img_Maker, Tool/Utility for the Xiaomi Mi 5
Contributors
Cynob, GokulNC, @[email protected]
Version Information
Status: Testing
Created 2017-05-09
Last Updated 2017-05-09
logo2 to logo5 seems useless
Only shows logo1 which doesn't show as 1080x1920 (if provided image), instead it shows as 1080x100
This is the logo i made for it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem MI 5 mit Tapatalk
---------- Post added at 08:27 PM ---------- Previous post was at 08:23 PM ----------
@[email protected] said:
Gesendet von meinem MI 5 mit Tapatalk
Click to expand...
Click to collapse
Thies is my Logo 1080x1920
Gesendet von meinem MI 5 mit Tapatalk
duxishere said:
logo2 to logo5 seems useless
Only shows logo1 which doesn't show as 1080x1920 (if provided image), instead it shows as 1080x100
This is the logo i made for it
Click to expand...
Click to collapse
Strange thing... i would understand if nothing is working but your pic 1080x100 sized? ok ... i have took your pic and build the logo.img - can you give it a try if it behave the same?
Where do the logo2.png till logo5.png got shown?
öhm i need more posts to upload files - i have saved your logo.img in the first contribution as update.zip
Cynob said:
Strange thing... i would understand if nothing is working but your pic 1080x100 sized? ok ... i have took your pic and build the logo.img - can you give it a try if it behave the same?
Where do the logo2.png till logo5.png got shown?
öhm i need more posts to upload files - i have saved your logo.img in the first contribution as update.zip
Click to expand...
Click to collapse
Well it is estimated to be about 1080x100 by eye, i will try to take a shot of it. It was built with Windows tool and i will try to test your one, will inform asap
logo2 to logo5 no where to be seen, cant check with stock recovery logo
---------- Post added at 09:30 AM ---------- Previous post was at 09:12 AM ----------
Here is the picture of the boot logo, sorry for potato webcam picture
As you can see it is trimmed to 1080x something about 100-200 px
The proplem is: the original logo.img has 5 pictures in it. I dont know where the other 4 pics get shown. They are there in the file but dont know where they are used.
Here a link to logos i build with Linux!
https://drive.google.com/open?id=0B78p1EKw_mzra1lLd00xVlBfalk
Google
Can someone upload the logo.img which contains Google Pixel Splash Screen? Thanks so much
emanuel.caesar said:
Can someone upload the logo.img which contains Google Pixel Splash Screen? Thanks so much
Click to expand...
Click to collapse
Senden meine a picture
Gesendet von meinem MI 5 mit Tapatalk
if its that google logo: try the update.zip
ok there was a error ... i investigate xD
News:
I rewrote the logo_gen.py to make a file with only one picture inside and deactivated the RLE compression = wont work.
Ok but i think i found out why some png images work and some others not.
Its because some information in the png header itself.
If you have a picture which wont work try:
Open Gimp image editor (https://www.gimp.org/)
Now open your existing png file.
Then use the "export as" function from dropdown menu
give it a "newname".png and click on export
Now you will get to a screen showing the export properties
deactivate every option and set the compression rate to 0
after that click "export" to generate a new picture which can be used for generating a logo.img
best result i got was when i used the same picture and copied it to logo2.png....>>logo5.png
Next step will be to edit the tools that they do it on their own
for testing which filesettings for the png will do it i have uploaded some test objects to github: https://github.com/Cynob/Mi5_logo_image_Maker/tree/master/logo_img_testing
feel free to download and test which one will work or not - if you want to help
Any update/progress on this?
duxishere said:
Any update/progress on this?
Click to expand...
Click to collapse
yes i wait for someone who test my uploaded files on github. If someone would say which works and which not i could finish my work... but till now nobody answered
I could try it tomorrow
Windows Logo maker works perfect!!
Gesendet von meinem MI 5 mit Tapatalk
duxishere said:
I could try it tomorrow
Click to expand...
Click to collapse
and have you tried some of the files?
The proplem is: not every picture gives a working logo.img. i want to know if its the pictures header fault or if it relay on the alpha channel and so on.
Cynob said:
and have you tried some of the files?
The proplem is: not every picture gives a working logo.img. i want to know if its the pictures header fault or if it relay on the alpha channel and so on.
Click to expand...
Click to collapse
None of those working on
firmware_miui_7.5.4_dev.zip
Click to expand...
Click to collapse
None of these working because i was flashing it into splash instead of logo, will try again in a sec
Okay so only glogo03 (one with something like inverted gradient of colors background) seems to be scaled down, something like scaled down to size of others glogo if you know what i mean...
Only one image in the logo.img file right? There was no fastboot image, was same as boot logo
No difference between logos so i suppose fastboot flash logo logo.img worked for every one as returned in CMD prompt
duxishere said:
None of those working on
None of these working because i was flashing it into splash instead of logo, will try again in a sec
Okay so only glogo03 (one with something like inverted gradient of colors background) seems to be scaled down, something like scaled down to size of others glogo if you know what i mean...
Only one image in the logo.img file right? There was no fastboot image, was same as boot logo
No difference between logos so i suppose fastboot flash logo logo.img worked for every one as returned in CMD prompt
Click to expand...
Click to collapse
Ok good - so the tool works if i understand you
only with picture glogo3 there was it shown wrong.
and yes the command "fastboot flash logo logo.img" is the right one.
Is in original logo.img a other logo for fastboot than at normal system boot?
In your logo images same pic for fastboot, but in stock, mi 5 unlocked on bootloader, fastboot text with android figure
duxishere said:
In your logo images same pic for fastboot, but in stock, mi 5 unlocked on bootloader, fastboot text with android figure
Click to expand...
Click to collapse
Did you try to put 5 different pictures in the logo gen tool?

Categories

Resources