Is there a way I can change it to the HTC logo or to something else? Or is it not possible?
Sent from my Droid running UD 6.0 and P3Droid's 1100 GHz kernel
Yes. Credit goes to daikonv for this. It isn't simple though. You need to have an image, convert it to hex, and hex edit part of the rds file. You'll need to re-root your phone too.
http://www.youtube.com/watch?v=LAsryc6mnRk
This is to change the motorola logo that you see when you boot your phone to a custom image. This is separate from the boot animation seen afterwards.
Tools/files you will need:
1) RSD Lite
2) droid sbf
3) SBFCodec
4) Photoshop (or paint, or whatever drawing program)
5) Hex editor (frhed is free and very easy to use)
NOTE: I do not use sbf-recalc because it complains about needing version 1.3, so I use SBFCodec instead.
Steps:
1) Run SBFCodec and open up the sbf file. This will extract all the smg files and header files.
2) Using photoshop, create an image that is 480 pixels wide and 182 pixels tall. Each color should be assigned 8 bits (1 byte), or in paint, just make a 24 bit bmp file. Mirror the image, making the left become the right, and the right becoming the left. Save as a bmp file (photoshop method).
3) Using a hex editor, open up your image and erase the first 54 bytes of data. (and possibly the last 2 bytes of data if you used photoshop. the number of bytes remaining should be exactly 262,080) With the remaining data, reverse the bytes. (using frhed, the option is in the edit menu->Reverse bytes)
4) Using a hex editor, open up the CG42.smg file created in step 1 and erase all data except the last 64 bytes of data (these 64 bytes of data should be FF's in the file). Then paste in the remaining data from step 3 to the beginning of the file and save. Your final file should be exactly 262,144 bytes large.
5) Go back to the SBFCodec window and save (this creates the sbf) the sbf file and name it whatever you want. i.e. boot.sbf
6) Using RSD Lite, flash this sbf to your phone. It may take 5-10 minutes for the flashing to complete. (after the 10 minutes, it might say "failed", just click on the show device button once that happens and you'll have succeeded)
You now have a stock phone with a custom boot image. Go ahead and root your phone and stuff. Sorry for the difficult instructions, this was the only approach I could think of to edit the boot logo.
Click to expand...
Click to collapse
I was hoping there might be something simpler... but thanks anyways!
Sent from my Droid using XDA App
I can create boot logo sbf files for the Droid 1. Post up an image and I'll make it for ya.
esocid said:
Yes. Credit goes to daikonv for this. It isn't simple though. You need to have an image, convert it to hex, and hex edit part of the rds file. You'll need to re-root your phone too.
http://www.youtube.com/watch?v=LAsryc6mnRk
Click to expand...
Click to collapse
That's intense. Can't you guys just flash rgbs through fastboot?
barnacles10 said:
That's intense. Can't you guys just flash rgbs through fastboot?
Click to expand...
Click to collapse
The Droid 1, 2 and X do not have fastboot access. I can however create an sbf that contains only the bootloader image to replace the Moto M logo. It will not require you to reroot. The attached was created for the D1. DO NOT attempt to flash this to your D2 or DX
Contact me if you want your own custom boot logo for your D1 or DX
So when I write the sbf I will have to reflash cw also or can I just do a restore
Sent from my Droid using XDA App
dakoopsta said:
So when I write the sbf I will have to reflash cw also or can I just do a restore
Sent from my Droid using XDA App
Click to expand...
Click to collapse
if you use the sbf in the zip i posted above, you will not have to reflash or restore anything. It only changes the bootloader logo.
jlutz555 said:
The Droid 1, 2 and X do not have fastboot access. I can however create an sbf that contains only the bootloader image to replace the Moto M logo. It will not require you to reroot. The attached was created for the D1. DO NOT attempt to flash this to your D2 or DX
Contact me if you want your own custom boot logo for your D1 or DX
Click to expand...
Click to collapse
Thank you so much for this, I've rerooted my phone a dozen times because I didn't have this!
Vaizard420 said:
Thank you so much for this, I've rerooted my phone a dozen times because I didn't have this!
Click to expand...
Click to collapse
Sent from my Droid using XDA App
Hey, sorry, I tried to edit the cg42 file in your sbf with one of my custom 24 bit bpm's, I did everything that works in other sbf's, but it won't flash right, yet it works if I don't touch the original file. Any thoughts on what I could do?
Vaizard420 said:
Sent from my Droid using XDA App
Hey, sorry, I tried to edit the cg42 file in your sbf with one of my custom 24 bit bpm's, I did everything that works in other sbf's, but it won't flash right, yet it works if I don't touch the original file. Any thoughts on what I could do?
Click to expand...
Click to collapse
Modifying my sbf will not work without editing the checksum after you add your own logo. I'll give you the link when I get home to my computer this weekend... There is also a windows program out there that will take a bmp and convert straight to sbf. Search droidforums.net...
Sent from my Droid using XDA App
jlutz555 said:
I can create boot logo sbf files for the Droid 1. Post up an image and I'll make it for ya.
Click to expand...
Click to collapse
I have been trying to follow these instructions and have failed every time. The error I usually receive is:
Failed flashing process. Failed flashing process. Interface AP-OS: Error verifying Code Group 42 checksums. File: 0xDDF9, Phone: 0x6BEA (0x4007031); phone connected
Could you please convert this bmp file into a flashable sbf ?
jlutz555 said:
Modifying my sbf will not work without editing the checksum after you add your own logo. I'll give you the link when I get home to my computer this weekend... There is also a windows program out there that will take a bmp and convert straight to sbf. Search droidforums.net...
Click to expand...
Click to collapse
After much searching, I was able to find such a program referenced:
Boot Logo Generator v1.10.10.22.exe
For convenience of everyone else, I have attached it here so other don't need to go through that ridiculous download process.
Related
Hi,
I just spent the past 3 hours downloading Rodriguez' MIUI mod on my computer because my connection is so slow. I usually download ROMS straight from my phone.
This time however, about an hour in, I realised that OSX Safari will unzip the ROM as soon as it finishes downloading automatically. I got into Preferences>General and change that setting, but it seems as though it didn't come into effect because I changed the setting whilst the download was in progress.
Anyway, is there any other way I can compress the ROM (which is now a folder) through any terminal commands either on the phone or on the computer?
I've already tried compressing it normally like any other folder with MM's Gingerbread ROM I downloaded yesterday. When I flashed it, I bootlooped so....
Oh and I can't download it again. I'm on the brink of going over my bandwidth allowance.
Thanks!
Well, You can use WinRAR like application for MAC (I Don't use OS X) so cant specify.
Select all the files and compress it to zip! Done!
Donate to me by clicking the Thanks if I helped you!
In theory, it would just be to compress it normally with the use of any archiver program which compresses to a .zip file. Not too familiar with OS X, so I cannot guide you into what program you'll need and how to do.
You need to re-compress the ROM files and sign the ZIP.
Jack_R1 said:
You need to re-compress the ROM files and sign the ZIP.
Click to expand...
Click to collapse
Forge94 said:
I've already tried compressing it normally like any other folder with MM's Gingerbread ROM I downloaded yesterday. When I flashed it, I
bootlooped so....
Click to expand...
Click to collapse
i think the issue is signing... Can someone tell us how to sign a rom on osx?
rassawyer said:
i think the issue is signing... Can someone tell us how to sign a rom on osx?
Click to expand...
Click to collapse
Signapk? But i think signing a rom is not neccesary anymore... Just turn off signature verification in recovery or use 4ext
I have had the same situation. Safari extracted the file automatically.
After waiting for 3 hours until the download completed, because the website is restricting my download speed to 100 kb/s.
I tried zipping and compressing the file both by a Windows system and a Mac. IT DID NOT WORK.
I have to download the file again.
thanks to superchillpil and gadget for i can make custom splash images now if anyone is interested. can take requests will try to make how you like but no promises.(justa rookie). if you post a pic i should be able to make into splash.
here's one from gadget
more to come if there is a need
must have root!
place on root of sd card(not in a folder)
boot to bootloader,
You will see
update splash,
Select yes update splash,
Wait, when done
select reboot
TB ONLY!!
HIT THANKS if u like
Here is how i make my own splash's if you want to make you're own
1.find an image u want.{must be 480x800!!-photoscape and gimp work for resizing and such}
2.use the splash flasher program(do not connect phone just use for conversion) to convert j-peg(whatever ur pic is)into an IMG file,should say custom.img.
3.rename file to splash1,(after should say splash1.img)place splash1.img and android info txt file into a folder and zip.(make sure u zip under store setting)only zip 2 files not folder containing files!
4.rename PG05IMG
ucan change second splash by changing png image in boot ani
thanks to trueblue_drew for his splashflasher!!
also solarpolitiks has an awesome request splash thread, check his out at
http://forum.xda-developers.com/showthread.php?t=1179810
And feel free to post your work here
hmm might try this
Ifu like let me kno
sent from dinc
Is the boot screen animated or is it s static image. Looks pretty boss though.
Replaces first image (the HTC one) not bootanimation
sent from dinc
Ah ok. Going to have to flash this.
Put on sdcard root, go into bootloader, wait u will see update splash, hit yes then hit reboot.
sent from dinc
Got it installed. Love it! Thank you
Sent from my thunder....BOLT!
Thank you very much, however, do you think you can edit the picture a little bit? It seems just a touch grainy, is that because of a size restriction? Either way, thank you very much. Could you make a version without "Rooted" at the bottom?
ryanstfl said:
Thank you very much, however, do you think you can edit the picture a little bit? It seems just a touch grainy, is that because of a size restriction? Either way, thank you very much. Could you make a version without "Rooted" at the bottom?
Click to expand...
Click to collapse
try this ryan-ur pic
how do you install this?
I would like help installing this as well. I have no folder on my sdcard for root. In my sdcard folder I do have a zip file called PG05img.zip. That is the same name as this file I just downloaded. If I put the downloaded file into the same folder as the other one wont it completely erase the other file?
chas1723 said:
how do you install this?
Click to expand...
Click to collapse
chas1723 said:
I would like help installing this as well. I have no folder on my sdcard for root. In my sdcard folder I do have a zip file called PG05img.zip. That is the same name as this file I just downloaded. If I put the downloaded file into the same folder as the other one wont it completely erase the other file?
Click to expand...
Click to collapse
Guys, the root just means not in any folder. Their are instructions in the OP and in another post on page 1.
Btw, chas, you want to remove the original PG05IMG.zip from your SD card. Every time you boot into hboot that will try and update on your phone. Best to remove it asap to avoid problems
named PG05IMG so bootloader sees it. U just put on root of sdcard not in any folder, ifu have another file with same name it won't work.
sent from dinc
heres a plain one i found
please make this a splash thanks
Thunder bolt ?
sent from dinc
Upstreammiami said:
please make this a splash thanks
Click to expand...
Click to collapse
TB ONLY!!
follow instructions on first page
Rom-Addict said:
TB ONLY!!
follow instructions on first page
Click to expand...
Click to collapse
awesome man thanks!!!!
http://forum.androidcentral.com/wal...htc-thunderbolt-wallpapers-cyber-warrior.html
V20B (CIS)
V20O (DEU)
Root on V20B
information deleted
I used google translator and that's the result of the post above:
All items are strictly in the order do not jump over them and keep the sequence!
Spoiler (+ / -) (I advise you to read before flashing)
to the root of drive C:
Two. Download Attachment SmartFlashTool_External.rar (1.18 MB) Number of downloads: 37
and extract the root of drive C:
3. Download Attachment Superuser.zip (611.2 KB) Number of downloads: 51
and put ( no need to unpack ) File on the SD-card phone
4. Turn off the phone.
Five. We hold the Volume Up (+) and insert the USB cable one end into the computer, the other into the phone
6. We will have the text of S / W Upgrade Please wait while upgrading ...
Spoiler (+ / -)
7. Run the file B_SmartFlashTool_Extern.exe
Eight. Go to the tab ROM copy D / L
9. Select the two files that you extracted from the archive [PATCHED] BIN_LGP970AT-00-V20a-CIS-XXX-JAN-06-2012 +0.7 z
10. Check:
Spoiler (+ / -)
11. Click the Start button
12. Go to the process of the firmware, go to drink coffee \ tea shorter depart away from your computer to your phone
13. When you sign Download Comlete! Go to the phone
Spoiler (+ / -)
14. On the phone, we see the regime Recovery (touch it, the management of a finger)
15. Select install zip from sdcard
16. Then choose zip from sdcard
17. Prolistyvayem and choose Superuser.zip
18. Prolistyvayem and select Yes - Install SuperUser.zip
19. Select + + + + Go back + + + +
20. Choose wipe data / factory reset
21. Prolistyvayem and select Yes - delete all user data
22. Then reboot system now
That's it! Phone is loaded, if you do it right!
As a result, we have a firmware with the Root-V20A human touch and Recovery! Thank you all and good luck to you in the firmware!
Click to expand...
Click to collapse
Dont exactly know, what it does, but as far as I get it, it roots the device and installs CWM touch.
Credits go to poster, if it is successful.
Hey, thanks for posting here. Here is v20b : http://www.lgmobiles.com/gsm/download/P970 V20B(Gingerbread Version).rar
We don't have it for N version. I saw the russian forum and wanted to ask you about howvyou managed to root v20a before this method.
Sent from my LG-P970 using XDA App
this method is working just v20a(attachment patched bin file) right?
Where how I convert .kdz to .bin file?
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Thread moved
Unless it's a ROM or kernel you've created yourself, this doesn't belong in Development.
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Kraaz said:
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Click to expand...
Click to collapse
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
SnegovikRZN said:
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Click to expand...
Click to collapse
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
adxgrave said:
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
adxgrave said:
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Since Telcel's v20a is is just out, its going to be pretty good news if it works.
mihaiolimpiu said:
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Click to expand...
Click to collapse
Yes it does.
Redpik said:
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
adxgrave said:
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Redpik said:
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Click to expand...
Click to collapse
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
I bet our rom cooker knew how to unpack and repack. So, anyone?
Sent from my LG-P970 using XDA App
jimakos29 said:
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
Click to expand...
Click to collapse
update: doing some research and it seems to extract the bin files you need lgutils and the .dll file you get from the kdz extraction but I am not at home to look into it any further.
Stable ROOT METHOD found!
You don't need this, disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Here is the proof
http://forum.xda-developers.com/showpost.php?p=22195743&postcount=417
Here are the drivers I used:
http://forum.xda-developers.com/showpost.php?p=22196019&postcount=21
I used Windows 7 32 bit, the original poster used Win7 64 bit...
Need it for a Cricket 626s. It was never officially released by Cricket, so if anyone has a T-Mo or Metro ZIP, that would be wonderful.
The T-Mo/Metro RUU's didn't take.
I flashed the T-Mobile Debloated MM ROM from XDA on my Cricket 626s. I haven't encountered any big issues yet, but make sure you back up Lollipop in the event that you do.
IMPORTANT: Before you first boot up into MM, remove your SIM card. Do not insert it until the setup process is completely over. When you get to Self-Service, wait a while to bypass it.
jakesnot-hereman said:
I flashed the T-Mobile Debloated MM ROM from XDA on my Cricket 626s. I haven't encountered any big issues yet, but make sure you back up Lollipop in the event that you do.
IMPORTANT: Before you first boot up into MM, remove your SIM card. Do not insert it until the setup process is completely over. When you get to Self-Service, wait a while to bypass it.
Click to expand...
Click to collapse
Where can you download this?
technohunter123 said:
Where can you download this?
Click to expand...
Click to collapse
I misspoke; it's actually the Sprint ROM: https://forum.xda-developers.com/de...m-flashable-stock-htc-626s-debloated-t3293602
I forgot one step, though. There's a couple of lines in a single file that prevent this file from flashing.
To fix it:
Open the .zip file from Windows (Without extracting)
Navigate to /META-INF/com/google/android/
Open 'updater-script' with a good text editor
Delete the lines from 'assert' to the next semi-colon
Save, and let Windows recompile the .zip
This new file should flash without problem. If you have trouble doing this, say something, and I'll upload mine when I get home.
jakesnot-hereman said:
I misspoke; it's actually the Sprint ROM: https://forum.xda-developers.com/de...m-flashable-stock-htc-626s-debloated-t3293602
I forgot one step, though. There's a couple of lines in a single file that prevent this file from flashing.
To fix it:
Open the .zip file from Windows (Without extracting)
Navigate to /META-INF/com/google/android/
Open 'updater-script' with a good text editor
Delete the lines from 'assert' to the next semi-colon
Save, and let Windows recompile the .zip
This new file should flash without problem. If you have trouble doing this, say something, and I'll upload mine when I get home.
Click to expand...
Click to collapse
Thanks for helping out here. I just tried your suggestion, and when I flash from TWRP, I get the error:
"Updater process ended with ERROR: 6
Error installing zip file '/sdcard/TWRP/Sprint_Stock_MMDB_2.27.651.6.zip'"
embhorn said:
Thanks for helping out here. I just tried your suggestion, and when I flash from TWRP, I get the error:
"Updater process ended with ERROR: 6
Error installing zip file '/sdcard/TWRP/Sprint_Stock_MMDB_2.27.651.6.zip'"
Click to expand...
Click to collapse
Huh. Try this zip; I just flashed it successfully: https://drive.google.com/file/d/0B9O8izj2yw8iTWFnXzRWS20xaUk/view?usp=sharing
jakesnot-hereman said:
Huh. Try this zip; I just flashed it successfully: https://drive.google.com/file/d/0B9O8izj2yw8iTWFnXzRWS20xaUk/view?usp=sharing
Click to expand...
Click to collapse
That did it! Thanks for your help getting the right ROM.
:good:
After installing the ROM, I followed these instructions for activating / setting up (since I got the error "Cannot contact Google servers" trying activate G account):
https://forum.xda-developers.com/showpost.php?p=69853901&postcount=281
Help
Help please my little brother attempted to root his metro pcs htc desire 626s and some how he accidently wiped the os on it will the file on the thread be a rom i could install to his phone using twrp?
gruiz487 said:
Help please my little brother attempted to root his metro pcs htc desire 626s and some how he accidently wiped the os on it will the file on the thread be a rom i could install to his phone using twrp?
Click to expand...
Click to collapse
You can use the zip that jakesnot-hereman posted in TWRP
I have added a utility to my git repo to change the startup logo. Instructions are below, use at your own risk and all that.
Logo requires a 800x480 image. Any format should work. If the image is not 800x480 it will resized.
This release requires cygwin and my modified firmware to be installed.
1. Install cygwin
2. Extract all the files in logo.zip to your pc.
3. Open a cygwin shell and navigate to the extracted directory.
4. Run ./createXAVlogo.sh and pass the input file. ex ./createXAVlogo.sh input.jpg
5. Copy usbexecute, flash_erase, and newlogo.img to a usb stick.
6. Insert it into radio, flash will auto start.
7. When unit reboots remove usb stick. New logo should now display.
8. Remove copied files form usbtick.
Do we just download the "logo.zip" file? or do we click on the "clone or Download button" from the previous directory and download all the files again? I have already installed your disable files to radio?
Just a little nervous about doing this right so I don't brick a new radio. LOL
Thanks for all you have done with this
wellsjj said:
Do we just download the "logo.zip" file? or do we click on the "clone or Download button" from the previous directory and download all the files again? I have already installed your disable files to radio?
Just a little nervous about doing this right so I don't brick a new radio. LOL
Thanks for all you have done with this
Click to expand...
Click to collapse
I added all the files in one zip to make it a little easier so no need to clone it. This update is fairly safe. On my test unit I completely wiped the logo partition and was still able to boot. There is always a small risk though.
I added a windows batch file version. Cygwin is no longer needed.
Color change
Hey @superdave, I tried this earlier this morning and everything works fine, I just have one problem. I used the same picture I used for the background and even though the bootup picture did change the blue part of the logo turned red for some reason. Your converted_preview.tiff shows the right picture so Idk what's going on. I'm using your firmware for the caution screen disable btw. I'm going to try a different usb and maybe another logo with the color blue in it to see if it does it again.
Orlando1193 said:
Hey @superdave, I tried this earlier this morning and everything works fine, I just have one problem. I used the same picture I used for the background and even though the bootup picture did change the blue part of the logo turned red for some reason. Your converted_preview.tiff shows the right picture so Idk what's going on. I'm using your firmware for the caution screen disable btw. I'm going to try a different usb and maybe another logo with the color blue in it to see if it does it again.
Click to expand...
Click to collapse
I just noticed this as well. In my case the red turned to blue. Pretty sure I know the issue. I'm checking this now.
Ok @superdave so I actually just tried another usb. Same problem, with the first usb I used the cygwin method and it was formatted in ntfs. The second usb I used the windows batch method and it was formatted in FAT32. Same results on both. The custom logo works fine as a background but when I set it as the bootup picture too the bootup one changes the blue part of the logo to like a maroon red. It's weird. I'm going to try another blue logo soon.
Orlando1193 said:
Ok @superdave so I actually just tried another usb. Same problem, with the first usb I used the cygwin method and it was formatted in ntfs. The second usb I used the windows batch method and it was formatted in FAT32. Same results on both. The custom logo works fine as a background but when I set it as the bootup picture too the bootup one changes the blue part of the logo to like a maroon red. It's weird. I'm going to try another blue logo soon.
Click to expand...
Click to collapse
I just pushed and update to the .bat and .sh. it should work now. It wants the format in bgra instead of rgba
superdave said:
I just pushed and update to the .bat and .sh. it should work now. It wants the format in bgra instead of rgba
Click to expand...
Click to collapse
Do I need to edit the picture at all? I just tried it again, and I got the same result. Idk if it'll help but I attached the picture.
No, shouldn't have too. Are you using the . Sh or the. Bat?
superdave said:
I just pushed and update to the .bat and .sh. it should work now. It wants the format in bgra instead of rgba
Click to expand...
Click to collapse
Btw I don't know if this is normal but this is what happens when I input the image.
Enter the 800x480 image input file name: input.jpg
input.jpg JPEG 800x480 800x480+0+0 8-bit sRGB 43507B 0.016u 0:00.010
input.jpg=>tmpoutput.bgra JPEG 800x480 800x480+0+0 8-bit sRGB 1536000B 0.016u 0:00.012
convert: UnableToOpenConfigureFile `colors.xml' @ warning/configure.c/GetConfigureOptions/714.
convert: UnableToOpenConfigureFile `magic.xml' @ warning/configure.c/GetConfigureOptions/714.
1 file(s) copied.
convert: UnableToOpenConfigureFile `magic.xml' @ warning/configure.c/GetConfigureOptions/714.
Image conversion complete.
Enter the drive letter to copy files to:
Orlando1193 said:
Btw I don't know if this is normal but this is what happens when I input the image.
Enter the 800x480 image input file name: input.jpg
input.jpg JPEG 800x480 800x480+0+0 8-bit sRGB 43507B 0.016u 0:00.010
input.jpg=>tmpoutput.bgra JPEG 800x480 800x480+0+0 8-bit sRGB 1536000B 0.016u 0:00.012
convert: UnableToOpenConfigureFile `colors.xml' @ warning/configure.c/GetConfigureOptions/714.
convert: UnableToOpenConfigureFile `magic.xml' @ warning/configure.c/GetConfigureOptions/714.
1 file(s) copied.
convert: UnableToOpenConfigureFile `magic.xml' @ warning/configure.c/GetConfigureOptions/714.
Image conversion complete.
Enter the drive letter to copy files to:
Click to expand...
Click to collapse
Yeah, it's normal. Just warning messages since we're not using any config files.
@superdave, Yea the .sh did the same thing, the blue part of the logo is red. Maybe it just doesn't like my picture lol.
Orlando1193 said:
@superdave, Yea the .sh did the same thing, the blue part of the logo is red. Maybe it just doesn't like my picture lol.
Click to expand...
Click to collapse
I just tried your image and it worked fine. Maybe try deleting the files off the USB first?
Edit: I just posted a new version that deletes the files if they exist first. I also just noticed I did not update the logo.zip before.
superdave said:
I just tried your image and it worked fine. Maybe try deleting the files off the USB first?
Edit: I just posted a new version that deletes the files if they exist first. I also just noticed I did not update the logo.zip before.
Click to expand...
Click to collapse
Works Great! Just downloaded everything again and used the logo.zip. I was only using the logo.zip before you fixed it so it makes sense as to why it wasn't working when you had fixed it already.
Thanks a lot man! I got a 2 year protection on the radio, so if you ever need a guinea pig for any update I'm here lol.
Working well, but I am having trouble trying to get the boot logo background to match the wallaper background of the unit (I want a logo on the boot screen, but logo-less on the desktop).
The luminance of the boot image seems to be massively boosted, and I am having trouble trying to match them. Anyone arty enough to work out what's going on? Or some Paint.NET adjustments to make to get them to match? Attached my image I am using. (Feel free to use it if you want)
I just tried to convert the image but the program just exits after I enter the file name and enter. Tried with different name, with and without file type, still exits without converting it.
EDIT:
damn antivirus! it blocked the operation without notifying me about its actions. it works!
EDIT 2: my radio won't update. I've put everything in its place and it doesn't do anything. tried also with update folder and without, no success
I plugged in my pendrive and the radio did nothing. I have the firmware on the version 1.02.06. Any tips?
Help for a non-Windows user...
I'd love to update the logo at startup, but I don't have a Windows PC. Would anyone be so kind as to convert 2 logos for me?
Greg996 said:
I'd love to update the logo at startup, but I don't have a Windows PC. Would anyone be so kind as to convert 2 logos for me?
Click to expand...
Click to collapse
Sent you a PM on here.