Database Info

[MOD] White On Black Evo Splash Screen

Here is a Splash Screen i wanted to share with the community, It's simple just the original with inverted colors
Please enjoy.
As always please backup before trying, I won't be responsible for anything that may go wrong if this fails
and mods if this is posted in the wrong place please move thanks
{
"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"
}
To apply just unzip the contents of the package below into the tools folder of the android sdk
How-to Enter fastboot mode .... While the phone is off hold down "Volume down key" and then "power button" hold both till you get a white screen with the androids and skateboards
to confirm your device is seen by adb use this command
Code:
fastboot devices
you should see your phone listed under the command you just typed. After that type the next command to flash the splash image
Code:
fastboot flash splash1 splash1.nb
Then you should see that it was successful and rebbot the phone and preview your new image by typing
Code:
fastboot reboot
Please Thank and post comments as needed, if there is any trouble i'll try to help if i can i'm rather busy lately...lol

There was a huge thread on how to change splash with win 7 and I am stuck in osx thanks for a tut on how to to it in fastboot

Thanks! I followed the instructions and applied it no problem. Makes booting up look seamless with Fresh's bootscreen

So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim

Criimson said:
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Click to expand...
Click to collapse
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition

Am I missing something? I do everything step by step and it won't find fastboot command in the terminal (using OS X). I can't do anything.

JSZESZE said:
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Click to expand...
Click to collapse
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Is there a way to flash from the EVO itself? I can copy files with no problem if I connect as a HDD.

add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it

Criimson said:
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Click to expand...
Click to collapse
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone

I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?

JSZESZE said:
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Click to expand...
Click to collapse
Awesome! Thanks man, I appreciate it. Looks great.

beautiful! thank you VERY much for this

JSZESZE said:
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
Click to expand...
Click to collapse
No it is in fastboot
From what I gather a lot of people have this issue with Vista 32bit and HTC Sync. I haven't been able to track down a solution. Even when trying to use Sync..it always just errors and says:
Unable to find HTC Sync on your PC. Please make sure.....
Kind of a pain, but so far I have been able to do everyting I want just doing it from the phone with files copied over. Using the terminal emu or file manager
Criim

imaxreed said:
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
Click to expand...
Click to collapse
sounds like a permission issue... are you rooted and nand unlocked?

JSZESZE said:
sounds like a permission issue... are you rooted and nand unlocked?
Click to expand...
Click to collapse
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?

imaxreed said:
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
Click to expand...
Click to collapse
in adb type
Code:
adb shell
then you should see
Code:
#
A $ prompt is the prompt for normal terminal ...
whereas:
a # prompt is the prompt for root (super user)

i am running osx and can access adb shell
http://imgur.com/t8MKg.jpg

does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues

JSZESZE said:
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
Click to expand...
Click to collapse
yes exactly. I haven't had a problem before this is strange.

Works great for me, no problems. This is a great way to save battery!
haha.

Simple XDA splash, black

7/11: I have posted new versions of each. The white is toned down a bit to match the HTC EVO emblem, and not be overwhelming. And both fonts have been smoothed so it looks much better.
I also changed the file in each zip to contain the correct name so those of you having problems should be able to run the command without changing filenames.
Mirrors also added!
Hey guys, I made this to represent xda when I boot
Thought I would share
The files attached can be flashed through bootloader.
Boot your phone into fastboot (hold vol up key while powering phone on, select fastboot)
Now open command. To verify your computer is recognizing your phone, type
Code:
fastboot devices
This should list your device. After that, you want to unzip the file you downloaded and place it in your android sdk tools folder.
Now, back in command, change to your tools directory and enter
Code:
fastboot flash splash1 splash.raw565
Remember to back up anything you don't wanna lose, and nandroid. Not responsible for anything that happens if you don't
That said I have flashed it and it works.. enjoy
{
"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"
}
Download black and white splash here: DOWNLOAD Mirror ~~> http://www.megaupload.com/?d=DD298CR4
Download color splash here: DOWNLOAD Mirror ~~> http://www.megaupload.com/?d=9PQ2PZ3A

I like that, might just have to flash it.

enragedpaza said:
I like that, might just have to flash it.
Click to expand...
Click to collapse
let me know what you think

says "cannot find splash.raw565"

enragedpaza said:
says "cannot find splash.raw565"
Click to expand...
Click to collapse
Are you booted in fastboot? Did you put the raw file into your sdk folder?
If not maybe it needs the original raw file in there too.. I didn't think it should tho. If you wanna try I have attached it. You could try dropping that in tools too and running the same command. Even though thats not the file its looking for.. so it leads me to believe one of previous should fix it

It looks awesome. I think I will leave that one on there for a while. Well at least a couple of days
I flashed mine a little differently though. I changed the name of the file to evosplash1.rgb565 and ran
fastboot flash splash1 evosplash1.rgb565
Click to expand...
Click to collapse
It worked great. Im not sure if your command accomplishes the same thing though (noobness talking)
Edit - Forgot to say thanks!

Love it man! The second I saw it, I HAD to flash it!
Thank You

says cannot load the file..not sure what i'm doing, my sdk tools is on my desktop do i need to cd to it or what.
EDIT: nevermind, sometimes i'm so stupid

Looks great
I have a desaturated theme going on so the orangish color won't work. Might use it in the future... unless you want to make a black/white version <3

kpkimmel said:
says cannot load the file..not sure what i'm doing, my sdk tools is on my desktop do i need to cd to it or what.
Click to expand...
Click to collapse
put the "splash.raw565" in your tools folder
boot phone into fast boot
cd desktoplocation/androidsdk/tools
fastboot flash splash1 splash.raw565

imaxreed said:
Looks great
I have a desaturated theme going on so the orangish color won't work. Might use it in the future... unless you want to make a black/white version <3
Click to expand...
Click to collapse
This should be it.

barnacles10 said:
This should be it.
Click to expand...
Click to collapse
Flashing now thanks brah

Thanks everyone. Glad you all like it.

enragedpaza said:
says "cannot find splash.raw565"
Click to expand...
Click to collapse
I think I figured out your problem. I forgot I changed the names of these files before zipping them so you will need to change them to splash and then run the command. I've added new versions anyway with the correct file names so you can try those too.

your server bombed out, looks like you hit your bandwidth cap. mirror?

iammuze said:
your server bombed out, looks like you hit your bandwidth cap. mirror?
Click to expand...
Click to collapse
Yeah ill be home from work soon and ill post up some mirrors

Thank you for this..Looks great!

iammuze said:
your server bombed out, looks like you hit your bandwidth cap. mirror?
Click to expand...
Click to collapse
Mirrors are up
MrDSL said:
Thank you for this..Looks great!
Click to expand...
Click to collapse
thanks!

made a splash screen, saved as bmp, what do i need to do to make it a splash on my evo. thanks

Black and white for me, worked like a charm. Thanks.

[Q] Trying to Root. Just aint happening

Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers

Bertrum said:
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Click to expand...
Click to collapse
http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I liked this guide. First time rooting.
On command prompt, you have to go to the Android\android-sdk\tools folder then execute those fastboot command.
Your command prompt probably says C:\Users\Your User Name.. [I have Windows 7]
Type 'cd..' (without ' ') until your line says C:\>
Then type the following cd Program Files\Android\android-sdk\tools
It could be Program Files (x86) not Program Files.. depends which bit you have. You can type those fastboot command from there.

Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?

Bertrum said:
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Click to expand...
Click to collapse
Did you download ClockWorkMod img and paste it into android-sdk\tools folder? You can do that my opening My Computer folder -> C:\ -> Program Files -> Android -> android-sdk -> tools folder.
Then open command prompt and type like that. I just did the first line for you.
{
"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"
}
Yours could be Program Files, not Program Files (x86) though. I downloaded 32-bit version accidentally and I didn't wanted to do it over.
After that you use your Nexus S to boot into bootloader [which the instruction says] and continue on.

thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.

Bertrum said:
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Click to expand...
Click to collapse
I'm glad I helped. I had hard time rooting yesterday but it's all good now

I finished everything last night. All unlocked and rooted. Also running CM7 rc2 with the n14 kernel.
Its soo fast compared to my old blackberry and my friends galaxy.
Many thanks to the people who worked on the roms and kernels. Your knowledge astounds me.
Sent from my Nexus S using XDA Premium App

Help... Trying to flash the newest Tiamat kernal and Clockwork Mod

When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
{
"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"
}
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!

Your not actually changing direcotry into the correct directory. so when you call the fastboot command it's looking in the current directory of "c:\Users\Marc" instead.
cd \Program Files(x86)\Android\android-skd\platformtools
adb reboot bootloader
fastboot flash recovory recovory.img

Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App

Thanks guys, Ill try again.

ghoticov said:
When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!
Click to expand...
Click to collapse
*FACEPALM*

jase33 said:
Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Does this work using Vista? I do not see the option to "open command window here".

Duh, nevermind... I figured it all out. I was putting a \ after platform-tools so it wasn't actually opening the folder where the recovery.img file was. Told you I was a novice. But I am getting it!

This is why one-clicks are the root of evil. If you would have done it manually from the start, you would have already known what to do here . Also since you posted this in development, i'm looking forward to the release, although i'm unsure what you are releasing at this point...

Ok people... Let's be mature here and not flame other users. This is supposed to be a community, not a war zone. If something is posted in the wrong section, or there's a post that breaks forum rules, drop me a pm or report the post. Thanks!
And this belongs in q and a... Since this is a question. Thread moved.
Please follow forum rules and post in the correct section.

damn, I must have missed some good flaming post! Lol

dont feel too bad
hehe I was doing the same thing for a 1/2 hour before I realized that the recovery.img wasn't even in the same folder...got that sorted out tho..

Bricked After Trying To Restore Splash Screen

So recently I've been messing around my Sensation, adding custom bootanimations and splash screens.
I've backed up the old one using
Code:
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/splash.img
So to restore it I'd thought I'd do the opposite
Code:
dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p1
Bad news, the phone is dead.
I can't boot into recovery or anything. So... is there a cure?

Matt1408 said:
So recently I've been messing around my Sensation, adding custom bootanimations and splash screens.
I've backed up the old one using
Code:
dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard/splash.img
So to restore it I'd thought I'd do the opposite
Code:
dd if=/mnt/sdcard/splash.img of=/dev/block/mmcblk0p1
Bad news, the phone is dead.
I can't boot into recovery or anything. So... is there a cure?
Click to expand...
Click to collapse
If that second line is the actual one you used, then you pushed the splash screen img file to mmcblk0p1 instead of mmcblk0p19.

Crap, looks like I made a typo and messed it up.
{
"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"
}

have you tried flashing stock RUU to restore?

Forgive me for asking, but where is this RUU.exe?

Oh no! good luck matt.

Matt1408 said:
Forgive me for asking, but where is this RUU.exe?
Click to expand...
Click to collapse
depends on your model, but i can help ya
is it unbranded? or bell/tmobile etc?

It's the Bell version

and you cant get into bootloader at all?
have you tried pulling the battery for 5-10sec, put it back in, then old VOL.DOWN + POWER?

I've tried pulling the battery, and booting into recovery, but to no avail.
However, when I plug in the phone to my computer, I get something about "qhsusb_dload." But thats about all that happens. Adb doesn't work, and such.

thats actually a really good sign!
do you have ADB on your computer? you WILL need that for sure, if not ill get ya a link

Of course I do, what do you think got me in trouble in the first place

hahaha oh yeah, just looked at first page
ok so go into cmd, connect phone via usb and type - adb devices
edit* also, just noticed your name is matt and you live in toronto, as is/am i
also, sorry im doing a million things at once cuz im at work, so some posts might be short 1-2 steps

Code:
C:\Users\Matt\Desktop\New folder>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
No devices show up.

are you running cmd as admin? thats important

Yup. No dice.

can you check battery discharge? i just wanna see what level of control you have.
enter
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
it will say "CHARGING" or "DISCHARGE"

As I said, adb doesn't detect the phone.
But the phone was about 90% when I killed it.

ok well it seems thats its in download/recovery mode from you're earlier post, so lets try fastboot
fastboot reboot
OR
fastboot reboot-bootloader
EDIT* also, are you rooted, superCID or anything special like that?

<waiting for device>
... nothing