Related
Hello,
The reason why anyone would do this is for example - I installed the Rogers WM6 but preferred the HTC BOOTSCREEN Image - hence why i personally did it. I did not like Rogers BootScreen Images as they take too long to boot as well as the bootscreen image in the Rogers WM6 used to load after the Green Windows Mobile Screen and on power-up, it used to have a black screen instead of the bootscreen image which to me did not seem practical as I rather see that the phones turned on right away than wait till the Windows Mobile screen loads. I've successfully flashed HTC Bootscreen image using the following steps. I had a member ask me how to flash .nbh files to phone. I'm talking specifically about the bootscreen .nbh images. In order to flash .nbh boot screen images - you have to flash through USPL. Here's how to do it -
1) Firstly, Download all required files that is
a) USPL CID -BYPASS
b) RUU
c) SDA APPLICATION UNLOCK
d) BOOTSCREEN IMAGES(IT CONTAINS HTC, ROGERS AND TMO BOOTSCREEN IMAGES)
2) Copy/Paste RUU File that is ExcaIMG_USPL_1110000unsigned.nbh to the desktop.
3) Copy/Paste ANY of the preferred BOOTSCREEN IMAGE (i.e. for example HTC.nbh) to RUU directory
4) Right Click ExcaIMG_USPL_1110000unsigned.nbh and Select Rename - Press Ctrl + C to copy file name
5) Head over to RUU and Right-Click HTC.nbh, Select Rename - Press Ctrl + V to copy over existing file name.
6) Once you're done this, REMOVE SD CARD AND REBOOT PHONE
7) Once done, APPLICATION UNLOCK YOUR PHONE IF IT HASN'T ALREADY BEEN APPLICATION UNLOCKED - YOU HAVE TO RUN SDA APPLICATION UNLOCK.
8) Now, Run USPL, Make sure you follow proper instructions as this is the main thing - if everything done right, you'll see screen goes into dim black with penguin and green messages, wait until you see the screen turns white then go to active sync and disable usb connections.
9) After this, run RUU and it'll use the re-named file which is the boot screen image to update the boot screen image. It will take max. a minute or two.
10) Once done, I think you see the tri-color screen but there won't be a cold boot - It'll reboot i think and go directly to the main screen.
11) Reboot and see if you see the preferred boot screen image.
For now, I'll post HTC, TMO and Rogers Boot Screen Images. We should still try as a group to create Custom Boot Screen .nbh files. If someone who know's how to make it, please share in this discussion.
Also, Does anyone know how to bring back the "Vibrate" mode during startup and shutdown?
Good Luck ! Post any concerns or any questions
NOTE: Please follow proper instructions, otherwise it won't work. If i'm missing anything, please let me know as I did this flash yesterday and I'm writing the guide today. Also, YOU HAVE TO FLASH THROUGH USPL - IT DOESN'T MATTER IF YOUR PHONES CID UNLOCKED OR NOT.
Credits go to da_mayhem for uploading the images.
sweet, thanks... I'll try this later tonight after i get home from work... or tomorrow
woohoo, sweet... thanks for the guide lukybandit.
On step #2, you'll want to "Cut/Paste" if you copy, it leaves the original file in the folder, so renaming the HTC.nbh isn't possible unless you delete the original file.
also, step #8... DEFINATELY make sure you disable USB connections, i tried without and it didn't work...
However you're supposed to do that for WM6 rom updates also, but i never have, and haven't had a problem... until now that is.
Change HTC Splash Screen
Hello,
How to change the HTC splach screen which appears just after powering on the device?
I tried a lot of tools but I did'nt found one which works. Is it because the Excalibur screen is 320x240 instead of 240x320?
Does someone knows how to do?
StefanSki
StefanSki said:
Hello,
How to change the HTC splach screen which appears just after powering on the device?
I tried a lot of tools but I did'nt found one which works. Is it because the Excalibur screen is 320x240 instead of 240x320?
Does someone knows how to do?
StefanSki
Click to expand...
Click to collapse
replace Shutdown.png in windows folder,with 320x240
i tried this i created a .png file but when i try to place it there access denied lol it wont let me touch anything in the windows folder
This is not this splash screen I mean.
I am talking about the first one, which is in the NBH file as a NB file. I don't manage to make a good NB file in the right format to flash it using RUU.
nbh file wat folder wuld that b in because i jus changed my shutdown screen and i want my turn on screen to b da same as that one
blahzay_blah said:
i tried this i created a .png file but when i try to place it there access denied lol it wont let me touch anything in the windows folder
Click to expand...
Click to collapse
you need total commander to overwrite
No one knows how to make a NB file that contains the splash screen? The default HTC NB file begins with "this is smartphone signature".
i changed my shutdown screed with resci explorer but to change the start up screen the htc screen and the freen windows mobile screen i want to get rid of those ugly screens
any1? a little help lol just want to change the start up splash screen any1 know how
You can use nbimg, to convert from NB to BMP.
For excalibur you'll need to use the following syntax:
Code:
nbimg.exe -F MainSplash.[nb|.bmp] -w 320 -h 240 -n
Also you'll need to add the "this is smartphone signature" manually to the generated NB file (using an hex editor). Maybe I'll add support for doing this automatically if there's a need. PM me as I'm not following the thread.
just saw on another thread how to create a .nb file from a .bmp .... i placed this here because apparently luky got the tmo and rogers .nbh files which have the mainsplash.nb files in them. need to know how to take the .nbh files he included and replace the mainslpash.nb and mainsplash.bmp files with the ones i created
heck i'll even upload the images here if someone wants to show me what to do
i was able to get the .nbh file created but when i flashed the phone with that file the first screen now looks like a green gradient image and not the image i put in the .nbh file
thanks for this man much appreciated.
First of all, thanks to lukybandit and pof for their help and threads which made this possible.
This tutorial will allow you to change your initial splash screen to any 320 X 240 customized splash screen of your choice.
You will need to download 3 items below:
The nbimg 1.1.zip file made by pof
the 2 .zip files (1.) Excalibur-USPL-RUU.zip (2.) Excalibur USPL - CID BYPASS.zip
Unzip all 3 files and place the contents into "local disc C:" root directory.
first thing to do is to create a bitmap file ".bmp" with a 320 x 240 screen resolution. I recommend taking any image you make and using photoshop or gimp or even MS Paint to make the resolution 320 X 240 and then save it into "local disc C:" root directory. To make it easy to follow with this tutorial, save it with the file name of "MainSplash.bmp".
UPDATE 6/4/09: Additional instruction if you are not creating using MS Paint. Thanks to TheExpertNoob
If your "Designing" your 320x240 boot screen in Photoshop, save it, then flatten the image (discard hidden layers as well).
Once that is done, CTRL+A, CTRL+C (to copy whole flatten image from photoshop) open MS Paint and set the dimensions of a new file as 320x240 in MS Paint, CTRL+V, then save it as a 24-bit bitmap in MSPaint. (this seems to remove any "Information" Photoshop puts into the BMP file if you were save as in photoshop, which seems to cause the messed up boot screens. reopening a photoshop saved BMP in MSPaint won't work either.)
Then back in photoshop undo your "flatten image" to modify to your liking later.
If your still not having any luck, download one of the premade bootscreens found in these forums ex. HTC, flash it and start over with the above steps (so your overwriting your custome over a clean boot screen)
After you've created your .bmp file, the next thing you're going to do is to open up a command prompt and type: "cd c:\" . press enter. this should take you to a c:\ prompt.
Next you're going to type this:
Code:
nbimg -p 108514 -n -s -w 320 -h 240 -F MainSplash.bmp -T 0x600 -S 1024 -D EXCA10000
press enter.
{{{Keeping mind of the upper or lower case of the letters (this is important!)
if it is a upper case "S" then it has to be a upper case "S" (not "s") and lower case "n" then use a lower case "n" (not "N").}}}
If you do it right, it should look 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"
}
you will end up getting two output files:
MainSplash.bmp.nb &
MainSplash.bmp.nbh
(you can delete the MainSplash.bmp.nb)
Next step is to rename the output file. (MainSplash.bmp.nbh)
Open the folder "Excalibur-USPL-RUU" and locate the file "ExcaIMG_USPL_1110000unsigned.nbh" use this exact file name to rename the file you just created. Once renamed you're going to cut and paste that file into the "Excalibur-USPL-RUU" folder and overwrite the original.
UPDATE 6/4/09: Alternate Instructions if doing this with Energy Based ROM: thanks killa-mckilla!
(Rename the file to EXCAIMG.bmb.nbh , not ExcaIMG_USPL_1110000unsigned.nbh)
Next, you need to prepare your phone for this flash of the splash screen.
( if your phone is not app unlocked this procedure WILL NOT WORK! If your phone is not app unlocked, please download and run the SDA_Application Unlock.zip file from your PC below)
You will need to power your phone off and remove your micro-SD card ( if you have it installed, if not just reboot it) now power your phone back on.
(this seems to work better when a non-sliding panel (chome) homescreen is active, so you may want to change this at this time if you are using a sliding panel homescreen.) ))
Connect your phone to your PC via activesync.
Open the folder named "Excalibur USPL- CID BYPASS" and run the file "Uspl.bat" follow the instructions on the screen and after abour the 3rd or fourth enter press your phones screen should turn white. You should hear the audible sound from your PC indicating that something was just disconnected. ( don't worry it should reconnect immediately ) Activesync will not detect your phone. this is normal.
Now you will open the folder "Excalibur-USPL-RUU" and you're going to run "ROMUpdateUtility.exe". follow the on-screen instructions. If done successfully, the RUU will give you a success screen and your phone will reboot. You should now see your newly created boot splash screen that you just created!.....I am currently pursuing how to also change the second splash screen (the windows mobile screen) and will update this tutorial when that happens. Let me know if any part of this is confusing or if you have any difficulty with the results.
Good post man, hopefully this will help a lot of people out with similar questions regarding this.
Hey Pudgedaddy, good post. I know this want work for me, but is there any way to change it without flashing? I would like to change but didn't know where to start.
showaco said:
Hey Pudgedaddy, good post. I know this want work for me, but is there any way to change it without flashing? I would like to change but didn't know where to start.
Click to expand...
Click to collapse
I don't think so. The initial splash screen is part of the the ROM so you have to flash a .nbh file in order to change it.... as far as i know.
pudgedaddy said:
I don't think so. The initial splash screen is part of the the ROM so you have to flash a .nbh file in order to change it.... as far as i know.
Click to expand...
Click to collapse
So this is the first splash? Not the second one, right?
showaco said:
So this is the first splash? Not the second one, right?
Click to expand...
Click to collapse
Yes. In the case of excalibur users, it's either the HTC first boot screen, the t-mobile first boot screen, or the rogers first boot screen that they see as soon as they turn on the phone.
pudgedaddy said:
Yes. In the case of excalibur users, it's either the HTC first boot screen, the t-mobile first boot screen, or the rogers first boot screen that they see as soon as they turn on the phone.
Click to expand...
Click to collapse
ok, 'cause on mine , I have a blue windows screen for a couple of seconds and then it changes to a green windows screen with the custom rom's name that stays on thru rest of boot process. I found a reg hack to change the second boot screen, thats why I was asking.
showaco said:
ok, 'cause on mine , I have a blue windows screen for a couple of seconds and then it changes to a green windows screen with the custom rom's name that stays on thru rest of boot process. I found a reg hack to change the second boot screen, thats why I was asking.
Click to expand...
Click to collapse
what's the reghack that you use....? maybe i can change my second boot screen too.
The reg entries are at HKLM\System\Startup\1. In there you will only want two keys, one called Duration and the other Splash. If there is ay others, remove them. I have Duration set as dword and is 9000. Splash is image location. It should be in windows folder and word is jpg doesn't work but that gif does. I think png does also. You can do the same for HKLM\System\Shutdown\1. Image size is 320X240.
showaco said:
The reg entries are at HKLM\System\Startup\1. In there you will only want two keys, one called Duration and the other Splash. If there is ay others, remove them. I have Duration set as dword and is 9000. Splash is image location. It should be in windows folder and word is jpg doesn't work but that gif does. I think png does also. You can do the same for HKLM\System\Shutdown\1. Image size is 320X240.
Click to expand...
Click to collapse
oh ok.... i have a variation of this same hack adapted from thw WM6 t-mo ROM for my phone. ( I actually have a thread that talks about how to do this with screens and sounds) anyway, with this hack i end up having 3 screens...... 1 my custom first boot screen, 2. the standard windows mobile screen, 3, my other custom boot screen using the reg hacks.
So i guess there's still something in the ROM that needs to be flashed to change the 2nd boot screen for the DASH
Im New Here And I Tried Doing This Step By Step But
I Just Cant Seem To Get It Right. My Command Promp Tells
Me That What I Wrote Down Cant Be Recognized As A Command. What Am I Doing Wrong???
CHEKO15 said:
Im New Here And I Tried Doing This Step By Step But
I Just Cant Seem To Get It Right. My Command Promp Tells
Me That What I Wrote Down Cant Be Recognized As A Command. What Am I Doing Wrong???
Click to expand...
Click to collapse
you have to tell me SPECIFICALLY what step in this process you are in and what SPECIFIC error message came up. Then i can help
WELL IM DONE WITH THE FIRST 2 STEPS BUT
WHEN I TYPE DOWN THIS "nbimg -p 108514 -n -s -w 320 -h 240 -F MainSplash.bmp -T 0x600 -S 1024 -D EXCA10000" THE COMMAND PROMPT
TELLS ME "nbimg is not recognized as internal or external command" what do i do wrong???
CHEKO15 said:
WELL IM DONE WITH THE FIRST 2 STEPS BUT
WHEN I TYPE DOWN THIS "nbimg -p 108514 -n -s -w 320 -h 240 -F MainSplash.bmp -T 0x600 -S 1024 -D EXCA10000" THE COMMAND PROMPT
TELLS ME "nbimg is not recognized as internal or external command" what do i do wrong???
Click to expand...
Click to collapse
the nbimg.exe file and whatever .bmp file both have to be in the root C:\ directory.
basically, if you're starting out as "c:\ nbimg -p **********" the c:\ part if this assumes that anything you are running is in the c:\ root diretory. so when you type after that "nbimg" it is searcing got the program in c:\ only. it will not search your entire hard drive(s) for this app. secondly the .bmp has to be also in c:\ because nbimg.exe also only looks in whatever directory it is currenty in. Now technically this doesnt have to be in c:\ it can be anywhere you want.... say your desktop. but if you have it somewhere else, you'd have to change the active directory you're in before you start. Some people don't know how to get to the active desktop directory in a command prompt. I only listed the instructions to be placed in the C:\ root directory because it makes it a whole lot easier not having to type out the entire direcotry name. (so you type in " cd c:\ " instead of "cd c:\documents and settings\*username*\desktop\" to get to the active directory) which makes this less error prone with noobs running command prompt.
well i done these steps but now
it tells me " file:MainSplash.bmp..
could not open MainSplash.bmp"
CHEKO15 said:
well i done these steps but now
it tells me " file:MainSplash.bmp..
could not open MainSplash.bmp"
Click to expand...
Click to collapse
is the .bmp you are trying to convert named "Mainsplash.bmp" ???
basically the mainsplash.bmp refernces the .bmp file you are converting. if your .bmp file is named something different, you need to either insert that filename.bmp in place of mainsplash.bmp or rename your file to mainsplash.bmp
edit: secondly if the file is named "MainSplash.bmp", do you have it in the same directory as nbimg.exe? if not it needs to be in the SAME DIRECTORY!
(ex: if nbimg.exe is in C: <root directory> then MainSplash.bmp need to also be in C: <root directory> )
Thanks Man I Finally Got It..
Thanks For The Steps And Keep On
Helping People.
help
Okey I have changed my second load screen and eveything works but when I look in eg edit for hklm/system/startup I cannot find it. I'm using a tilt. anythoughts
Hi, I tried this method step by step and got my splash to change, but the actual picture is really distorted compared to the original bmp pic. Not sure what happened there. I tried it using different bmp files and every time the splash screen is distorted. I am using Rickywatt v24 vanilla rom.
pcdo said:
Hi, I tried this method step by step and got my splash to change, but the actual picture is really distorted compared to the original bmp pic. Not sure what happened there. I tried it using different bmp files and every time the splash screen is distorted. I am using Rickywatt v24 vanilla rom.
Click to expand...
Click to collapse
was the original image a 320X240 resolution? it HAS to be an original 320X240 ( and not a 240X320 ) resolution in order for the output to match the input.
I have attached all the files needed to do this on windows, mac, and linux at the end of this post. The creation of these apps, goes to the respective people, including Koush, JF, Infernix, and alansj.
Want to get rid of that t-mobile boot image?
Disconnect, over at Gotontheinter.net, has figured out how to do it using the new unlocked bootloader from the g1 dev phone. Below is a quote from the source. ( http://www.gotontheinter.net/node/9 )
"So you want to join the party and flash your own boot image, but its a weird undocumented format and you don't want to spend all year researching it in the source. Well, I'm here to help.
It is actually very simple. Start with an image you want to use, make sure it is 320x480 with 8bpp color. (In my examples, I'll use splash.png: PNG image data, 320 x 480, 8-bit/color RGBA, non-interlaced
Just make sure you have ImageMagick installed, and the utilities from the source build. (Specifically, rgb2565.)
$ convert -depth 8 splash.png rgb:splash.raw
# Make sure it is 460800 bytes long!
$ rgb2565 < splash.raw > splash.raw565
# Triple-check size before flashing! 307200 bytes
$ fastboot flash splash1 splash.raw565
$ fastboot reboot
Lets break it down. the convert turns it from a png (or any supported image format) into a raw 8-bits-per-color no-alpha data file. This file should be 460800 bytes - no more, no less.
Next, rgb2565 converts that file to a raw 565 16bit file (for the framebuffer on the G1.) This file is exactly 307200 bytes long - if its not, you messed up somewhere.
Finally, you use fastboot to flash the splash image and reboot. Instead of the B&W T-mobile logo, now you will see your custom splash screen. Congrats! "
Thanks to Infernix for the following extended how to:
1. find an image you like
2. edit it with your favourite editing suite and scale it to 320x480
3. after scaling it, convert the colorspace to 256 colors (8-bit)
4. Save it as a PNG without alpha channel/transparency.
5. Use the convert tool from the ImageMagick toolkit (use cygwin, or a linux box): convert -depth 8 splash.png rgb:splash.raw
6. Check that the splash.raw file is exactly 460800 bytes!
7. Compile the android tool called rgb2565 (gcc -O2 -Wall -Wno-unused-parameter -o rgb2565 to565.c)
8. Run the conversion command: rgb2565 < splash.raw > splash.raw565
9. Check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE. double-check your steps, something went wrong.
10. Boot your phone in SPL mode (hold camera +power).
11. After SPL shows, plug in USB connector/cord/whateva and push trackball or hit back. SPL restarts and now shows FASTBOOT.
12. If on windows, you need to install http://dl.google.com/android/android_usb_windows.zip
13. Compile android (see http://source.android.com/download) and make sure the fastboot binary (mydroid/out/host/*/bin/fastboot) is compiled (* being your OS)
14. use fastboot devices to check whether if your phone is showing up. if it isn't, try it as root (user might not have permission to access the usb device).
15. Double check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE.
16. Flash the splash image: fastboot flash splash1 splash.raw565
17. Reboot your phone to check: fastboot reboot
The instructions below are for users trying to flash their own boot image using windows.
The instructions below are also JF's work and not my own:
Instructions:
(note: you have to check the USB device in Computer Manager when the phone is in fastboot mode. The computer sees the phone in fastboot mode as a different device than the phone in normal mode)
Download the file and extract it in the same folder as adb. (if you don't have adb yet, it's included in the android SDK for windows. go download it!)
Take out the usb cable and boot up your phone into the SPL (back + power). You have to have the dev bootloader for this to work (white background with 3 skateboarding androids).
Plug in the usb cable, and make sure the display on the phone changes from "Serial0" to "FASTBOOT". If it doesn't, try pressing the back button.
If it asks you to install drivers, then go ahead and use the same usb drivers that you used to get adb working. You can skip the rest of the instructions. Fastboot should be working for you now.
If it doesn't ask you to install a driver, you need to figure out if the correct driver is loaded already.
Right click on My Computer, and click Manage, then go to the device manager
If you see an "ADB Interface" category at/near the top, with "HTC Dream" under it, then you're good to go. Fastboot should be working for you.
If you don't see an "ADB Interface" category, then it's likely that windows loaded the USB Mass Storage driver for it automatically. In the device manager, go down to "Universal Serial Bus Controllers", and see if you have at least one "USB Mass Storage device". If you have multiple ones, you'll need to go through each to find the correct one.
To find the correct one, right click on the USB Mass Storage device and click Properties. Go to the Details tab. In the combo box at the top that says "Device Instance Id", bring up the pull down and choose "Compatible Ids". If that is the correct device, then you will see 3 entries:
* USB\Class_ff&SubClass_42&Prot_03
* USB\Class_ff&SubClass_42
* USB\Class_ff
Once you find the correct device, go to the driver tab, and click "Update Driver". Choose "No, not this time", then "Install from a list or specific location", then "Don't search, I will choose the driver to install", and then choose the same usb driver that you used to get adb to work.
After that's done, you should be good to go. Open a command prompt and type fastboot devices and it should list the phone.
Here is a very good set of instructions for applying this to your phone if you haven't gotten it already: http://forum.xda-developers.com/showthread.php?t=467064
Additional Information
-
-
another way to convert to 565 raw, but from ANY format, is to use ffmpeg like so:
ffmpeg -i input.png -f rawvideo -pix_fmt rgb565 output.565
where input.png could be jpg, gif, tiff, etc. whatever you want.
-
-
credits for this goes to
Clone137
Heres some info about FFmpeg and where you can download it: FFmpeg
Stericson
“It won't work,” droned Marvin, “I have an exceptionally large mind.”
It's possible to modify the code to show a different startup animation: for example, the cylon strobing eye animation that was present up till Android V0.9.
Check out \frameworks\base\libs\surfaceflinger\BootAnimation.cpp. Just need to redeploy the one surfaceflinger file to see the changes.
Stericson, You ROCK!
I'm getting hung up at this line
fastboot flash splash1 g1-splash.rle
it says g1-splash.rle not found. what'd i miss? everything else has worked like a charm thus far.
Correction in instructions:
$ rgb2565 < splash.raw > splash.raw565
# Triple-check size before flashing! 307200 bytes
$ fastboot flash splash1 splash.raw565
$ fastboot reboot
Stericson said:
This file should be 460800 bytes - no more, no less.
Click to expand...
Click to collapse
460800 shall be the size of the file, and the number of bytes in the file shall be 460800. 460801 shalt not the size of the file be, neither shall the size be 460799, excepting that thou then append a byte to 460800.
460802... is right out.
Once the file size 460800, being the 460800th byte be reached, flasheth thou thy boot image onto the G1, who, being naughty in my sight, shall display it.
(note: please read the instructions, and don't actually flash a file that's 460800 bytes long. I had to take some artistic liberties here )
Ok, now the terminal just hangs on
< waiting for device >
Is the phone supposed to be in recovery? I've tried that, but have had the same results. I have the /system mounted and the phone is on a jailbroken RC30 (1.2). And it also is running the Dev 1 bootloader. Any helpful hints?
[edit]
when i do an 'adb devices', the phone is listed...
can I do this using windows? I made an image, with paint shop pro, and used convert to convert it to the raw format and it turned out to be 403,200 bytes, is that wrong? What did I do? Also, can I use rgb2565 on Windows? or do I have to run this in linux? Lastly, when using fastboot, do I boot my phone into the dev bootloader and connect to it via adb shell and then type that command?
Any help would be great!
OK let me extend the howto:
1. find an image you like
2. edit it with your favourite editing suite and scale it to 320x480
3. after scaling it, convert the colorspace to 256 colors (8-bit)
4. Save it as a PNG without alpha channel/transparency.
5. Use the convert tool from the ImageMagick toolkit (use cygwin, or a linux box): convert -depth 8 splash.png rgb:splash.raw
6. Check that the splash.raw file is exactly 460800 bytes!
7. Compile the android tool called rgb2565 (gcc -O2 -Wall -Wno-unused-parameter -o rgb2565 to565.c)
8. Run the conversion command: rgb2565 < splash.raw > splash.raw565
9. Check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE. double-check your steps, something went wrong.
10. Boot your phone in SPL mode (hold camera +power).
11. After SPL shows, plug in USB connector/cord/whateva and push trackball or hit back. SPL restarts and now shows FASTBOOT.
12. If on windows, you need to install http://dl.google.com/android/android_usb_windows.zip
13. Compile android (see http://source.android.com/download) and make sure the fastboot binary (mydroid/out/host/*/bin/fastboot) is compiled (* being your OS)
14. use fastboot devices to check whether if your phone is showing up. if it isn't, try it as root (user might not have permission to access the usb device).
15. Double check that splash.raw565 is 307200 bytes. if it isn't, DO NOT FLASH IT ON YOUR PHONE.
16. Flash the splash image: fastboot flash splash1 splash.raw565
17. Reboot your phone to check: fastboot reboot
This list together with instructions at http://www.gotontheinter.net/node/9 should get you going.
The tools mentioned here are commandline tools.
I have attached static versions of the tools mentioned for linux x86 to this thread. However I can't guarantee that they will work for you. they should, though.
A quick note: you can save directly to raw format from gimp or photoshop (allowing you to skip the imagemagick step). It just has to be 8-bit (which has been the default when I tried it).
Also, I attached rgb20565 and fastboot compiled for OS X 10.5.
Could someone upload the compiled binaries for Windows for those lazy people out there (me included)?
Here is the compiled binary for rgb2565
I don't have the compiled binary for fastboot, hopefully someone else will post it for you guys...I found it easier, way easier, to do this on a linux box.
After a bit of tinkering, i finally got it. The biggest problem i was having was that after i booted into the SPL, THEN i was supposed to connect the USB cable... i had it plugged in and then tried to boot SPL and nothing happened. Everything is great now. Big thanks
Thanks Stericson for the compiled rgb2565 file(for windows)
Can someone please upload the fastboot binary? I don't know how to compile it myself....Thanks a lot in advance for everyones previous hardwork on this and forthcoming.
to build the file yourself go to the root android source directory (mine is linux, but it looks like this "/home/ryan/android_source"), your's might look something like "C:/Source Codes/android/" or whatever. Once you navigate to that directory (via the command prompt... just go to start > run > and type in 'cmd' and hit enter, then use the 'cd' command to get there... e.g., "cd C:/Source Codes/android/"), once there, simply type 'make' and hit enter and it will start building everything, it might take a few minutes to complete. Then just go into the 'out' directory, then it's under "host/windows-x86/bin" (i'm not sure about the windows-x86 part, it might just be windows or something like it, i'm just assuming based on mine), once in that folder you'll have the fastboot as well as all of the other binary files ready to go. Then you can just type fastboot w/e w/e and it'll work just fine.
Here's my updated bootloader logo:
It's kind of difficult to see, my camera sucks... it's my fraternity letters with the crest in the background. Here's the image i used for it:
big head white robot guy
Id like to have the big head robot one in the first of this post, mind sharing the properly pressed,flipped,shook,stirred and what not, Id just like to dump the tmob splash, really anybody who has tried tested images attach them here, if you don't mind sharing...
just figured I'd ask as I didnt see any posted anywhere I don't always do so well at looking for stuff, at least thats what my wife is always b1tchen in my ear...
bhang
Ok, I'm sure I can do that, but now how do I get the android source onto my windows installation? Do I use cygwin? How, if so?
Thanks so much....
BTW, I've tried googling this, and still am, with no luck, thusfar.
Here's what I finally settled on.
Take 2...
Awesome, thanks for the help!
You mentioned that disconnect figured out how to do it with a dev bootloader - does this mean my rooted rc30 phone should be upgraded to a dev phone bootloader for it to work? Or will I be able to perform it on my modified rc30 v1.2 setup?
thanks
edit: nm, figured it out thanks! here's a pic:
Hi, since this is my wife's HTC hero from Orange UK, I'm being particularly careful with it. I'm new to xda-developers/HTC platforms (but not new to doing horrible things to embedded platforms) :>
I've been messing about with the phone all evening - downloaded that ROM image from the other thread and pulled it apart to look at the OS files etc - the standard break-a-new-embedded-linux-platform routine.
Anyway, if you hold down BACK when powering on, it enters the bootloader mode with a "FASTBOOT USB" prompt, which sounded interesting. I got a copy of the fastboot binary, and extracted the kernel and the ramdisk images from "boot.img" in the "HEROIMG_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed.zip" (using split_bootimg.pl).
Just as a quick test, I tried booting them with:
fastboot boot kernel.img boot.img
since the above just boots a kernel from RAM, and not actually flash it. Anyway, fastboot claims it downloaded and booted it ok, and the phone shows the "HERO" logo. Unfortunately that is as far as it gets. However, if I reset the phone, it boots perfectly fine from the kernel/ramdisk in flash (phew!)
Since it doesn't actually boot into android proper (and doesn't show up as a USB device), I don't know if (a) its showing the HERO logo, but failing the signature check, or (b) actually booting, but crashing 'cos the kernel/ramdisk aren't quite right. I'd guess (a) myself, but I'm new to messing with HTC bootloaders.
Anyway, in case they're useful, the details of the phone from the fastboot mode are:
HERO CVT SHIP S-ON
HBOOT-1.76.0004 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.04.25
Jul 3 2009,15:22:21
That method of entering fastboot is the same as the magic. Check the magic / sapphire wiki and have a read as I suspect the magic is its closest relative and a lot of the magic stuff will work...
daisy xx
Aha, thank you very much, that gives me more information!
Anyway, I just tried booting the boot.img itself instead of splitting it up with:
fastboot boot boot.img
This time, it booted right into the full android! Checking /proc/config.gz:
On the phone booting normally, it says:
# Linux kernel version: 2.6.27
# Fri Jul 3 07:52:06 2009
On the phone booted with boot.img extracted from that zip, it starts:
# Linux kernel version: 2.6.27
# Thu Jun 25 14:16:01 2009
So it seems as though it can boot the boot.img: AFAIK config.gz is hardcoded into the kernel binary. Now: is there a signature in the boot.img file?
Erm, I'm either hallucinating from lack of sleep, or I appear to have a root shell on it now. e.g. I can see the contents of /data from "adb shell":
ps reports: [snip]
root 43 1 3332 164 ffffffff 0000e8f4 S /sbin/adbd
root 619 43 748 340 c005ef5c afe0d08c S /system/bin/sh
# ls /data/app
org.oep.pong.apk
com.google.android.stardroid.apk
se.illusionlabs.labyrinth.lite.apk
com.google.zxing.client.android.apk
com.innovativelanguage.wordpowerlite.jp.apk
com.funambol.android.apk
com.massorbit.sword.apk
com.soundroid2012.piano.apk
jg.entertainment.abook.four.apk
com.maplekeycompany.apps.shake.apk
net.peterd.zombierun.apk
All I did was
1) pull the boot.img apart with split_bootimg
2) gunzip the ramdisk
3) hexedit the ramdisk to set ro.secure=0 (couldn't be bothered faffing about with cpio)
4) gzip the ramdisk
5) rebuild the image with mkbootimg. Oh you need to specify a different base address. Example command line:
/tmp/mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.insecure.gz --cmdline 'no_console_suspend=1 console=null' -o test-insecure.img --base 0x19200000
Then I just booted it with "fastboot boot test-insecure.img"
adq said:
Erm, I'm either hallucinating from lack of sleep, or I appear to have a root shell on it now. e.g. I can see the contents of /data from "adb shell":
ps reports: [snip]
root 43 1 3332 164 ffffffff 0000e8f4 S /sbin/adbd
root 619 43 748 340 c005ef5c afe0d08c S /system/bin/sh
# ls /data/app
org.oep.pong.apk
com.google.android.stardroid.apk
se.illusionlabs.labyrinth.lite.apk
com.google.zxing.client.android.apk
com.innovativelanguage.wordpowerlite.jp.apk
com.funambol.android.apk
com.massorbit.sword.apk
com.soundroid2012.piano.apk
jg.entertainment.abook.four.apk
com.maplekeycompany.apps.shake.apk
net.peterd.zombierun.apk
All I did was
1) pull the boot.img apart with split_bootimg
2) gunzip the ramdisk
3) hexedit the ramdisk to set ro.secure=0 (couldn't be bothered faffing about with cpio)
4) gzip the ramdisk
5) rebuild the image with mkbootimg. Oh you need to specify a different base address. Example command line:
/tmp/mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.insecure.gz --cmdline 'no_console_suspend=1 console=null' -o test-insecure.img --base 0x19200000
Then I just booted it with "fastboot boot test-insecure.img"
Click to expand...
Click to collapse
You're ready to build your own rom images ;-)
You could start by preparing your own rooted recovery with nandroid.
For a quick and dirty basic recovery image, just download one from sapphire development forum, replace the boot.img-kernel with a working copy for your hero.
Then rename init.sapphire.rc in init.hero.rc in ramdisk image.
You can simply extract ramdisk image with:
mkdir boot.img-ramdisk
cd boot.img-ramdisk
zcat ../boot.img-ramdisk.gz | cpio -idv
make your changes to ramdisk files
search internet for a script named repack-bootimg.pl
add the new base parameter to mkbootimg line in the script
cd to directory where you unpacked your boot.img
repack-bootimg.pl boot.img-kernel boot.img-ramdisk newboot.img
fastboot your recovery
then you can use nandroid in the recovery image to make a full dump of your rom and use the newer version of boot.img you have in your device to rebuild an up-to-date recovery or any kind of rom (you could start by preparing a copy of your original rom by changing ro.secure=0 in both boot.img and recovery.img).
By the way, I noticed that kernel in HERO uses sapphire fixup. The currently available version on the net is not booting on sapphire (magic) 32A, but it resets after a few minutes.
Maybe the kernel version in your orange hero introduces compatibility with sapphire boards. Well, really I suppose it won't, but if you get a nandrod backup and post your current original boot.img, magic 32A board owners could give it a try while we are waiting for HTC to release updated kernel sources for Magic and Hero.
Bye
daldroid
adq said:
[...]
So it seems as though it can boot the boot.img: AFAIK config.gz is hardcoded into the kernel binary. Now: is there a signature in the boot.img file?
Click to expand...
Click to collapse
No, no signature in standard boot.img, you have to zip it and sign the resulting zip. But no signing keys except for test-keys are available to the public, so I suppose your spl (S-ON) wil not allow you to directly flash rom images from fastboot command line.
However it seems your SPL allows you to fastboot a repacked boot image, so it should not be a problem to use a recovery image to flash whichever rom mod you like.
I suggest you not to flash any SPL you can find on the net, I suppose you have the newest ad no image of your original SPL is available (there is one from a leaked hero image, but yours seems to be newer)
Bye
Yeah, my thoughts exactly, I'd rather not flash the SPL if I can help it: I don't fancy explaining to my wife why I have to rip her phone apart to find the JTAG contacts I'll upload the boot.img later though.
Thats odd about the reset after a few minutes thing: hardware watchdog timer of some sort?
adq said:
Yeah, my thoughts exactly, I'd rather not flash the SPL if I can help it: I don't fancy explaining to my wife why I have to rip her phone apart to find the JTAG contacts I'll upload the boot.img later though.
Thats odd about the reset after a few minutes thing: hardware watchdog timer of some sort?
Click to expand...
Click to collapse
Well, really it's a little bit mor than a minute or so.
I suppose it's not an hardware watchdog, I don't have access to console debug messages.
Really the reset is a good sign, if you try booting dream or sapphire 32b kernel on 32A boards, it hangs forever.
If you extract piggy.gz from the kernel and hexedit it,you can find hero kerel initializes the hardware using the sapphire fixup.
It could only be that htc reused the same source and fixed hardware details and forgot to change the fixup routine name or that they are prepare to build a kernel able to boot on both hero and magic 32A boards.
32A and hero use the same new base address for kernel and ramdisk loading 0x19200000.
our boards have more memory than dream and 32b boards.
I suspect htc is using a stacked ram configuration and they changed the init code for the number of banks in memory.
In 32A they changed ram location for fb, ram console and maybe gpu1. It was a real mess to guess every change, so I stopped recompiling and rebooting the kernel after a dozen of times ;-) Waiting for htc to release the patched source code ;-)
The radio rom on hero seems to be is newer than 32a's latest available but I don't want to try a flash, you know what I mean ;-)
The available hero SPL shoud work on sapphire (and on blackstone and topaz too) and maybe the newer radio rom requires it, but... I prefer not to brick my Magic.
Have a nice rom rooting time. You could want to give superuser.apk a try.
People on this forum is asking for rooting status on hero, I suppose you'll be able to announce them your succes in a short time.
Wow! That was Fast! Lol..... even thought there is still some work to do.
i feel honoured to have been one of the first to read this i still dont have a hero yet =[ gotta wait till august when i get my ema might start scrounging and saving what i can get so i can get it sooner
Well done to you sir what a fine job uve done, gz =]
I'm waiting for my Hero as well and I'm completely new to android.
But like you I develop for and work with embedded Linux systems so tearing ROMs apart was pretty much on top of my list when my device should arrive .
I don't know what the 'recovery' image does on Android systems, but as I read it like this: You can temporary boot a rom (or at least a kernel and it will get the rest of the system from the rom area) through the fastboot method.
So yes, then you have temporary booted into a rooted ROM. But how to make it permanent? Because if you modify the ROM and flash it back it will probably not work because it detects its modified, right?
Trying to make a "dirty recovery image" to dump full roms using Nandroid Backup
Hello Dalroid,
I read your post and was able to do the following:
1. Using split_bootimg, extract the ramdisk files from the Stock HTC HERO Rom found in the XDA forums.
2. I downloaded the cm-recovery 1.4 image from Sapphire and used split_bootimg on it as well.
3. I copied the extracted kernel from the HTC Hero ROM and replaced the one from the cm-recovery of sapphire.
4. I renamed init.sapphire.rc to init.hero.rc in the extracted recovery image folder.
5. This is where i have trouble. I am using the repack-bootimg.pl, but I am unable to repackage the image.
I did note that you stated that some base parameters needed to be changed in the script for this to work. Could you please shed some light on what I need completed in order to repackage. Thank you in advance.
EDIT: I found one problem so far, I do not have mkbootimg or mkbootfs on my computer. How do I get these on my computer?
JWallstreet said:
Hello Dalroid,
I read your post and was able to do the following:
1. Using split_bootimg, extract the ramdisk files from the Stock HTC HERO Rom found in the XDA forums.
2. I downloaded the cm-recovery 1.4 image from Sapphire and used split_bootimg on it as well.
3. I copied the extracted kernel from the HTC Hero ROM and replaced the one from the cm-recovery of sapphire.
4. I renamed init.sapphire.rc to init.hero.rc in the extracted recovery image folder.
5. This is where i have trouble. I am using the repack-bootimg.pl, but I am unable to repackage the image.
I did note that you stated that some base parameters needed to be changed in the script for this to work. Could you please shed some light on what I need completed in order to repackage. Thank you in advance.
EDIT: I found one problem so far, I do not have mkbootimg or mkbootfs on my computer. How do I get these on my computer?
Click to expand...
Click to collapse
I built my mkbootimg from android source code (android.git.kernel.org), but if you prefer you can find a prebuilt binary from http://rapidshare.com/files/249629878/PortTools.rar. I'm not the author neither I tested it, just searched for mkbootimg in forums and pasted the link for you.
If you use the standard mkbootimg, just add --base 0x19200000 the the mkbootimg line, otherwise the boot.img will be generated with standard load address which won't work for hero (or for my 32A Magic).
This is pretty exciting stuff
I really want to remove the SIM lock from the Hero - is this something you can do now you've got su access?
Is it going to be possible to have a 'how to' guide for the Hero to tell us what to do to get the phone unlocked?
I want to see someone install the Magic image on the Hero - it should fly with the extra RAM
Just out of curiosity, what would happen if I booted the original cm-recovery-1.4.img on the Hero?
My phone will hopefully arrive tomorrow, and the first thing I'd like to do is create a backup with the nandroid script.
wossName said:
Just out of curiosity, what would happen if I booted the original cm-recovery-1.4.img on the Hero?
My phone will hopefully arrive tomorrow, and the first thing I'd like to do is create a backup with the nandroid script.
Click to expand...
Click to collapse
It wont boot. You can instead use the modified(only trackball press event and kernel) cyanogen's recovery here: http://forum.xda-developers.com/showthread.php?t=541807&page=2
enlightener said:
It wont boot. You can instead use the modified cyanogen's recovery here: http://forum.xda-developers.com/showthread.php?t=541807&page=2
Click to expand...
Click to collapse
I'm new to all this, so I'd be grateful for some more information: is the Dream and Hero hardware too different to boot the same image? Or would it be possible to create multi-platform images?
I already downloaded the modified image from that thread and have extracted the same kernel, so I should be all set.
Hey guys, I have flashed a couple roms throughout the past 2 months, and i usually use Task 29 to wipe anything remaining but for some reason I get the Splash Screen from the Core Cell Evo roms, although im using the Energy GTX July 4 rom. Anyone know how to make this go away? or somehow I could change that? thanks
Not sure if this will help, but still trying to post something that may help you...
My phone was using the original HTC rom that came with T-mobile settings. Today I flashed its ROM with the following version :
ROM Name : WWE RHODIUM Cookie Energy style
ROM Version : 03.Jul.2010 WWE
ROM date: 03/15/10
RADIO Version : 3.45.25.14
and it removed the original T-mobile splash screen and also allows me to control the splash screen as follows :
Start -> Tools -> Advanced Config -> Splash
Hopefully it helps..
khoyifish said:
Hey guys, I have flashed a couple roms throughout the past 2 months, and i usually use Task 29 to wipe anything remaining but for some reason I get the Splash Screen from the Core Cell Evo roms, although im using the Energy GTX July 4 rom. Anyone know how to make this go away? or somehow I could change that? thanks
Click to expand...
Click to collapse
Yes, many of the custom ROMs will overwrite the initial splash screen. You generally have to manually install the screen you want - but depending on the ROM (some chefs don't change it), you may have to manually change the settings. There are several threads on the APPS forums dealing with changing the startup screens.
Note that there are two startup screens. The first one comes up right after power on / reset. This one has to be flashed. Then there is an (optionally) animated one that can be easily changed.
[How-To] Custom Boot Screen
stevedebi said:
Note that there are two startup screens. The first one comes up right after power on / reset. This one has to be flashed. Then there is an (optionally) animated one that can be easily changed.
Click to expand...
Click to collapse
There are actually three boot/splash/startup screens. The first one comes on after the little vibration when it turns on. The second one is the screen that contains the "R.G.D." info (in red) at the bottom left of the screen. The third is the one that can be changed easily. The first two are changed by flashing an .nbh file, and the third can be changed via reg tweak or cab.
.....
You can change the first two boot screens by flashing a stock ROM.
OR, to really customize the first two boot screens, you can do this:
**This will not affect your ROM, radio, and SPL (so don't worry). It will simply flash the first and second level boot screens. But you do need HardSPL.**
***This has only been tested (by me) on a T-Mobile USA Touch Pro2 (Rhodium 210 model; hence the RHOD210 in the code). I am not responsible for bricks!***
EDIT: I think it works for all GSM Rhodium variants; if it doesn't flash, it'll just say "Invalid Model ID" so it shouldn't brick (as long as you have Hard SPL). HOWEVER, I don't know about CDMA (Sprint/Verizon/Telus) models.
1. Download the nbimg tool.
2. Get a 24-bit, .bmp photo that is 480x800. You can resize and save the photo (as a .bmp) by using Microsoft Paint.
3. Unzip the nbimg tool. Put your photo in the same unzipped folder.
4. When you're in the unzipped folder, run a command (SHIFT + Right Click. Open Command)
5. In the command write this:
Code:
nbimg -p 18400 -w 480 -h 800 -F [U]insertnameofphotohere[/U].bmp -T 0x600 -S 64 -D RHOD210
6. Get the Rhodium RUU here (download the "Flashing Tools").
7. Put the .nbh you created in the same folder as the RUU.
8. FLASH -- it should have flashed the first boot screen.
9. To change the second boot screen, go back to step 5 and enter this (you can also change the picture, if you want! Just make sure it's in the same folder as the nbimg tool.):
Code:
nbimg -p 18400 -w 480 -h 800 -F [U]insertnameofphotohere[/U].bmp -T 0x60[B]1[/B] -S 64 -D RHOD210
10. Repeat steps 7-8. You should now have your custom first- and second-level boot screens.
I attached 2 of my boot screen pictures -- one from my TP2 and one from my HD2. I actually don't like the one from my TP2 because the scale of the phone in the picture is bad -- it was a resizing issue.
sumflipnol said:
There are actually three boot/splash/startup screens. The first one comes on after the little vibration when it turns on. The second one is the screen that contains the "R.G.D." info (in red) at the bottom left of the screen. The third is the one that can be changed easily. The first two are changed by flashing an .nbh file, and the third can be changed via reg tweak or cab.
.....
You can change the first two boot screens by flashing a stock ROM.
OR, to really customize the first two boot screens, you can do this:
**This will not affect your ROM, radio, and SPL (so don't worry). It will simply flash the first and second level boot screens.**
***This has only been tested (by me) on a T-Mobile USA Touch Pro2 (Rhodium 210 model; hence the RHOD210 in the code). I am not responsible for bricks!***
1. Download the nbimg tool.
2. Get a 24-bit, .bmp photo that is 480x800. You can resize and save the photo (as a .bmp) by using Microsoft Paint.
3. Unzip the nbimg tool. Put your photo in the same unzipped folder.
4. When you're in the unzipped folder, run a command (SHIFT + Right Click. Open Command)
5. In the command write this:
Code:
nbimg -p 18400 -w 480 -h 800 -F [U]insertnameofphotohere[/U].bmp -T 0x600 -S 64 -D RHOD210
6. Get the Rhodium RUU here (download the "Flashing Tools").
7. Put the .nbh you created in the same folder as the RUU.
8. FLASH -- it should have flashed the first boot screen.
9. To change the second boot screen, go back to step 5 and enter this (you can also change the picture, if you want! Just make sure it's in the same folder as the nbimg tool.):
Code:
nbimg -p 18400 -w 480 -h 800 -F [U]insertnameofphotohere[/U].bmp -T 0x60[B]1[/B] -S 64 -D RHOD210
10. Repeat steps 7-8. You should now have your custom first- and second-level boot screens.
I attached 2 of my boot screen pictures -- one from my TP2 and one from my HD2. I actually don't like the one from my TP2 because the scale of the phone in the picture is bad -- it was a resizing issue.
Click to expand...
Click to collapse
I used that on my old Magician, I didn't realize the same technique worked on the TP2.
OK, that was easy
I have attached the image I used, and the nbh files that I used.
hd_480_1.bmp - source picture
hd_480_1.bmp_1.nbh - Initial boot screen
hd_480_1.bmp_2.nbh - 2nd boot screen
I didn't put the "TP2" logo on the screen, because I figure I know what device I'm using!
EDIT: I don't mind anyone using them freely, but the picture may NOT be used for commercial purposes.
Question:
I made my bmp file, converted it to .nbh, but now I am not sure which "Rhodium RUU" to get and that link ( post 4 under 6. ) gives many files but nothing clear to what I am looking for.
Line 6 is this one:
6. Get the Rhodium RUU here (download the "Flashing Tools").
I thought I might be able to use "Rhodium_CustomRUU_v1.1" found at this thread:
http://forum.xda-developers.com/showthread.php?t=492930
but I need a confirmation from someone who knows this as I sure dont know will this do damage or help me make my new splash screen.
I will be using as my 1st splash this picture I found using google: