Database Info

[Splash] Halo Reach Splash Screens

I can't be the only one who likes Halo and can't wait for Reach to come out.
Here's a couple of splash screens I created with that in mind.
They are similar, but the second has one of my favorite quotes from Halo 3 and any one who has read the books knows what it means.
Let me know what you think. (Be gentle though, these are my first ones)
{
"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"
}

They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App

The reason I used that quote was because of the references in the halo: the fall of reach (the book). But if anyone wants a specific quote let me know and I'd be happy to include it.
Sent from my Fresh'd out Evo 4g
using XDA App

blkswanpres said:
They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Here ya go.

Hi, was hoping you could help me with this. I followed instructions on how to flash this and the actual sending of it worked but when it tried to write it, it said FAILED (remote: not allowed). Any ideas on what that would mean? Thanks!

You need to have ADB enabled. Put the evosplash1.rgb into your sdk/tools folder. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
fastboot flash splash1 evosplash1.rgb565
fastboot reboot

FattySparks said:
You need to have ADB enabled. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
adb remount
fastboot flash splash1 evosplash1.rgb565
fastboot reboot
Click to expand...
Click to collapse
First, thank you for replying to my post! You are the first one to state the "adb remount" part. I did that but it is saying device not found now. My phone does show the red fastboot usb so do you any further suggestions because it still failed on the writing part. The sending part went fine but I guess it is failing since it cannot find my phone. Might I have the sdk set up incorrectly?

One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.

eaglenest608 said:
One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.
Click to expand...
Click to collapse
when you're in fastboot it shouldn't show up in adb devices. I also forgot to mention to put the rgb565 file into your sdk/tools folder. Other than that it sounds like your setup properly.
Edit: Also the adb remount code isn't needed. I was so used to using it from messing around with bootscreens, I forgot it isn't needed for fastboot.

Yes, it seems I am setup correctly from what I have read. Maybe I should flash to a different rom and see if that helps me. My wireless tether app is giving me problems as well so not sure what has happened but it may be time to give something else a go. Unless you can think of anything new that is, lol. Thanks a bunch though for you help...really appreciate it.

Well, for those that actually care I have now resolved this issue. It turns out that the HBOOT version that I had did not allow me to perform this flash. I had to actually downgrade it to a different one and it worked perfectly. I wish to thank those that actually took the time to reply to my post...it was greatly appreciated!!

Realize I posted the screen of the new quote, but didn't attach the file... duh

Halo Reach Boot animation
http://forum.xda-developers.com/showthread.php?p=8419483#post8419483

PLEASE
Can you do one that says
"Halo:Reach>MW2"
That would be epic

Sorry for the delay, got married last weekend.
Here ya go.

Ohhh this is Perfect the delay is no problem but seriously thanks alot and congrats on the marriage

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..

Stuck big time. Help requested (Nexus S)

Hi all,
Well my adventure started last night when I went to return my Nexus S to stock. I did so and it worked well. Then I tried to re-root the device.
After doing so, it now will not boot past the google boot screen (with the unlock icon). It just sits there, even after battery pulls and additional attempts to start up. I can reboot into recovery (fastboot) as shown on the attached images. After hours of reading, it seems I need to flash CWM recovery.img to get the phone to boot. Ok, not a problem. So I installed the android sdk, google and samsung phone drivers and my phone is recognized in device manager.
When I go to flash the recovery.img via fastboot, it just sits there on "waiting on device" and ever goes anywhere. I also have a message on the bottom of the Nexus screen that says "FASTBOOT STATUS - FAILInvalid Command"
I'm at a point where googling is doing no good. Please help.
How can I get my phone to boot? How can I successfully flash the recovery image so I can go forward with root and be done with it?
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"
}

First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.

albundy2010 said:
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
Click to expand...
Click to collapse
Ok, how does one go about doing this on Win7x64?
Quides are on the forum? No idea what that means.

The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.

albundy2010 said:
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
Click to expand...
Click to collapse
Believe me, I've done that. Hours and hours worth.
Anyone care to help since apparently this information is so easy to locate? Fastboot simply isn't communicating with my phone and it will not boot past the google boot screen.

After many hours of trying, I figured it out. It had to do with the PDA net drivers. Basically, my phone would not boot up, preventing me from finishing the PDA net install. It kept hanging on "Installing PDA net to your phone" because, well, it couldn't install to my phone (since it was in fast boot mode).
I kept clicking on OK on the dialogue box and it would roll back, uninstalling the PDA net drivers. This was why fast boot could not communicate via cmd.
How I worked around this was by NOT clicking ok, hence not uninstalling the drivers.
It was an epiphany. And a pain in the arse.
So, if you have a similar issue, don't click ok on the dialogue. Leave it in limbo and work your command line magic!

[Q] More than one device and emulator / device offline...Desperate for help

Hello forums, I am new to xda, and to the motorola section so if I misplaced this post please forgive me. I have check all over the place trying to figure out my problem. I just got the Atrix 2 and tried running a one-click root program only to get the error "more than one device and emulator" I have read online, and from what I can understand that it may be an "adb" error, and that I need to locate the adb devices by using the command prompt (as seen here in the comments of another website cant post cause I'm a new user)
Not being very tech savvy I'm not quite sure how to control cmd, and if this is even the right thing to be looking for. If there is anyone who could walk me through this I would be infinitely grateful. Through these forums, or perhaps email, or skype. I don't want to bog down anyone, but I have been looking forward to getting and rooting this phone for quite a while now.
Thanks

piggies55 said:
Hello forums, I am new to xda, and to the motorola section so if I misplaced this post please forgive me. I have check all over the place trying to figure out my problem. I just got the Atrix 2 and tried running a one-click root program only to get the error "more than one device and emulator" I have read online, and from what I can understand that it may be an "adb" error, and that I need to locate the adb devices by using the command prompt (as seen here in the comments of another website cant post cause I'm a new user)
Not being very tech savvy I'm not quite sure how to control cmd, and if this is even the right thing to be looking for. If there is anyone who could walk me through this I would be infinitely grateful. Through these forums, or perhaps email, or skype. I don't want to bog down anyone, but I have been looking forward to getting and rooting this phone for quite a while now.
Thanks
Click to expand...
Click to collapse
Not sure about the error message, but have you made sure before you try to run the root exploit that your device (in settings/applications) you have the "Unknown Sources" and "USB Debugging" boxes checked?
{
"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"
}
Sent from my MB865 using xda premium

Yea, I made sure to enable both of those settings, since then I have tried messing around with the usb settings. When I set the phone to "charge only" get past the first phase and the phone reboots. However, upon rebooting I get the same error of having more than one device and emulator. I have also tried starting the root with Mass Storage on. Does anyone the source of this error, or some key words I could start researching?

Are you getting that error only when connected to your PC?
Have you seen these?
http://forum.xda-developers.com/showthread.php?t=1639199
http://androidforums.com/droid-all-...hell-error-more-than-one-device-emulator.html

I'm not quite sure what you mean, I dont get error when the phone is disconnected or connected via usb except when running the root program. Thank you for the article on the "bluestacks" problem. I'm not running that program, but I guess it's possible that something else on the computer could be conflicting. I checked task manager, nothing there. The other message talking about killing the adb server, how would I go about doing that? Like I said I'm not super tech savvy, so when it comes to command prompt stuff I have problems. Any suggestions?

Are you running Android 2.3.6. and which one click rooting method are you trying? You may want to download THIS ROOT EXPLOIT FILE, save to your C: drive, and plug in your device, set to "charge only". Then navigate to the C: drive, open the folder, and click the "click to root" option within the folder.

Apex_Strider said:
Are you running Android 2.3.6. and which one click rooting method are you trying? You may want to download THIS ROOT EXPLOIT FILE, save to your C: drive, and plug in your device, set to "charge only". Then navigate to the C: drive, open the folder, and click the "click to root" option within the folder.
Click to expand...
Click to collapse
I know this is a old thread. I faced the same issue and it complained this.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb.exe shell
error: more than one device and emulator
Click to expand...
Click to collapse
Disconnecting and Reconnected did the trick.

[SOLVED] Soft-Brick BOOT.IMG Recovery with CM10 and All-In-One Toolkit [NOOB-FRIENDLY

Right, I'm sure there is similar here, but I had loads of difficulty finding it, so I thought I'd create my own version.
I'm a complete noob at this, so I'll make it easier on you, and put it as plainly as possible. EVERY step is listed as if you're in the same [or similar] situation.
I only recently tried to get CM10 onto my phone, and on first try, I soft-bricked it. I unlocked the Bootloader, Rooted, Installed TWRP and a version of CWM when it didn't work, and CM10 seemed to work fine, but upon booting for the first time, and leaving it for about 15 minutes, I realised something went wrong. Tried going back to the most recent RUU [the EU OTA version], and that didn't work [after relocking the bootloader, yes]. Started freaking out a small bit, as it stopped letting me mount the storage in Recovery, even though ADB could still see the phone.
Asked a friend to help, and we found this over on the One X sub-forum.
BEING AWARE THIS IS RELATIVE TO hasoon2000's All-In-One Toolkit
[nice work btw! Might wanna look into this btw - it may be a small bug with your software. No offense ]
Turned out it was the boot.img that installed incorrectly, so making sure the .zip MD5 is correct is first step.
If that's not the issue, the 2nd step is to just open the .zip and take the boot.img out of the root of the container, and pushing that to the phone using ADB [the one that come's with the AIO is perfect]. If you're not sure how to get into ADB, and get it to stay open, here's what you do:
1. Copy the directory of "adb.exe" within your AIO's "data" folder [for example, mine is D:\Administrator.Sheol\HTC\All-In-One\Data\]
Click to expand...
Click to collapse
2. Open Command Prompt [in Vista onwards, type "cmd" into the Start menu Search Bar, in XP, open the "run" dialog in type cmd. Alternatively, find it in Start > Accessories, in all recent versions of Windows]
Click to expand...
Click to collapse
3. Type the following into Command Prompt:
cd D:\Administrator.Sheol\HTC\All-In-One\Data\
{
"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"
}
Remembering your directory WILL be different, so adjust accordingly!
Click to expand...
Click to collapse
4. It'll list all ADB's command's. Don't worry, it's meant to. If you want to, skim through them to familiarise yourself with it. At this point you may want to maximise the window, to fill the screen height [makes every thing much easier]
Click to expand...
Click to collapse
5. Follow this thread to the tee > [Tutorial] How to flash a new boot.img via Fastboot
Click to expand...
Click to collapse
Doing exactly this, worked a charm, and now I have a flawless CM10 HTC One S! After the GApps install of course [which can be done in your Recovery after downloading it/pushing it to your phone, by using the "Install from .zip" option]