Database Info

Splash Screen's For EVO

To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot.
4.Remember that you need to be rooted

awesome I am using it now

The Rubenator said:
To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot
Click to expand...
Click to collapse
What does "fastboot flash splash1 evosplash1.rgb565 mean?"
From a terminal window? Or what? Regular adb push? While the phone is on the fastboot screen?

Run Command, put your phone into bootloader once in there push the file from a terminal window while the phone is on the fastboot screen just like the way I post it.

The Rubenator said:
Run Command, put your phone into bootloader once in there push the file from a terminal window while the phone is on the fastboot screen just like the way I post it.
Click to expand...
Click to collapse
so do you put the zip on the root of your sd card before pushing?

too bad you have to be rooted for this..

BAleR said:
so do you put the zip on the root of your sd card before pushing?
Click to expand...
Click to collapse
No, you put the evosplash1.rgb565 file on the tools folder of your SDK folder

Nice boot screen!
Instructions for users on a mac:
Boot phone into fastboot
Download Green Android Splash.zip and unzip the files into your android sdk tools folder
Load up terminal
CD into the android sdk tools folder
Enter the command: ./fastboot-mac fastboot flash splash1 evosplash1.rgb565
Then once it's completed enter the command: ./fastboot-mac reboot
Your Evo should reboot with the new boot screen.

Did it and still have my previous splash screen.

bunch great splasheds posted today D:

effluent said:
Did it and still have my previous splash screen.
Click to expand...
Click to collapse
Are you rooted effluent?

I am having a bit of a problem flashing this as well... I have unzipped the file, and copied the evosplash1_rgb565 file into the sdk/tools folder on my computer. I reboot the phone into fastboot (Vol down/power, when in HBOOT, verify cursor on fastboot, press power) Phone enters fastboot and shows "FASTBOOT USB" in red letters. I go into my cmd: and type the "fastboot flash splash1 evosplash1.rgb565". I get "error: cannot load 'evosplash1rgb.565'
To verify that I was connected to the phone in fastboot, I have done 2 things. First, I entered "fastboot devices" the cmd: returned HTxxxxxxxx (device name) followed by fastboot. I also typed "fastboot reboot" which rebooted the phone.
Please tell me where I am going wrong.
Thanks, and great work on the recent splash screens you are putting up.

Anybody???? I tried leaving as much detail as possible, to try to rule out "Did you try ______?" replies. I just want to be able to change my boot screen, and the given instructions didn't work for me... Does ANYBODY have any insight into what I did wrong, or what I could do differently to change the bootscreen?
BTW, yes, I am fully Rooted via toasts method, and running Damage Control 3.2.3

1-Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb. If you type the command.
Code: fastboot devices
2-it should show you your phone. Next type the following command
Code: fastboot flash splash1 splash.rwa565
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image.
Sorry if you having any issues, I just took a look at the files and everything seen to be working perfect.

The Rubenator said:
To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot
Click to expand...
Click to collapse
The Rubenator said:
1-Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb. If you type the command.
Code: fastboot devices
2-it should show you your phone. Next type the following command
Code: fastboot flash splash1 splash.rwa565
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image.
Sorry if you having any issues, I just took a look at the files and everything seen to be working perfect.
Click to expand...
Click to collapse
Ok, thanks for chiming in with a fix.... In your first post, you said to use: fastboot flash splash1 evosplash1.rgb565
Now it is: fastboot flash splash1 splash.rwa565 ?
Just verifying, would I need to rename the file (bootscreen image), since in the download, it is evosplash1.rgb565 ?

1-Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb, or do it using "Quick Boot.apk" drop the file into your sdcard and install from there as a normal apk file.
once you run "Quick Boot select "Bootloader"
Remember that you need to put evosplash1.rgb565 into the android-sdk/tools folder.
If you type the command
Code: fastboot devices
2-it should show you your phone. Next type the following command
Code: fastboot flash splash1 splash.rwa565
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image.
I want to give thanks to "RikusHaven" for the help.
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"

Ummmmm...... You said that last time..... Also, you obviously did NOT read my original question, because you keep feeling the need to tell me how to get into fastboot. I said in my first question, in detail, how I was getting into fastboot, what I was typing, etc. You obviously ALSO didn't read my 2nd question, which asked if I need to rename the image, since in the first post you call it evosplash1.rgb565 and now you call it splash.rwa565. Any time I have ever had to move, copy, delete, etc... a file, I had to tell the computer WHAT file it is I want it to work with. By having a file named one thing, and telling the computer to work with another file, it doesn't make sense to me that the computer will miraculously know what to do. IF a rename is not needed, a simple "No, fastboot will find the file on its own" or something similar would have been enough, but to retype all the steps that I had already said I had taken, and still not providing a definitive answer to the question, shows that you aren't reading what the problems people are having. I tried to be as descriptive as I could, in posting my problem, rather than just saying "It don't work", and It is still taking multiple questions to try to find an answer.
If there is any doubt as to what steps I took, PLEASE scroll up and read Post #12. It tells in detail, What steps I took, What I typed, What error message I received, AND what I did to verify that I was in Fastboot.

thenewguy821 said:
Ummmmm...... You said that last time..... Also, you obviously did NOT read my original question, because you keep feeling the need to tell me how to get into fastboot. I said in my first question, in detail, how I was getting into fastboot, what I was typing, etc. You obviously ALSO didn't read my 2nd question, which asked if I need to rename the image, since in the first post you call it evosplash1.rgb565 and now you call it splash.rwa565. Any time I have ever had to move, copy, delete, etc... a file, I had to tell the computer WHAT file it is I want it to work with. By having a file named one thing, and telling the computer to work with another file, it doesn't make sense to me that the computer will miraculously know what to do. IF a rename is not needed, a simple "No, fastboot will find the file on its own" or something similar would have been enough, but to retype all the steps that I had already said I had taken, and still not providing a definitive answer to the question, shows that you aren't reading what the problems people are having. I tried to be as descriptive as I could, in posting my problem, rather than just saying "It don't work", and It is still taking multiple questions to try to find an answer.
If there is any doubt as to what steps I took, PLEASE scroll up and read Post #12. It tells in detail, What steps I took, What I typed, What error message I received, AND what I did to verify that I was in Fastboot.
Click to expand...
Click to collapse
youll need to replace evosplash1.rgb565 with whatever the correct file name you are flashing is.

I'm having issues as well. I've done this before without problems, but now i get waiting for device. My phone is on the fastboot usr screen. (power off, hold vol down then power on, then power again to get to fastboot screen)

I like that blue one. Good stuff bro.

Help...Bricked

Hey all -
So I followed instructions very specifically for rooting my Xoom on my Mac, and successfully unlocked the Xoom. As soon as I flashed the rootboot.img I rebooted and cannot get past the Motorola logo. I can get into Android Recovery, Fastboot and RSD protocall support but my Mac does not recognize it when I type in ./adb devices....what shall I do? I already performed Factory Reset but this didn't help.
P.S. When I say I followed instructions carefully, that is not to say this is anyone's fault but my own. I obviously did something wrong, and am realizing now that I flashed a 3.0 img file on my 3.1 Honeycomb...this is probably where I went wrong.
Any help would be greatly, greatly appreciated.
Thanks

I had a similar situation using rootboot, don't worry....download the proper boot.img from tiamat's thread, and flash it via fastboot the same way you did the previous one and reboot. That should fix you right up.
And your Xoom is nowhere near bricked, just a little confused. It will be alright.
Sent from my GT-I9000 using XDA Premium App

ah so quick! thank you thank you thank you. how do i flash it if the device won't show up though?

I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?

bloodmut said:
I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?
Click to expand...
Click to collapse
You said you could get into fastboot, yes? Power the Xoom down with power + volume up, reboot into fastboot with power + volume down, plug in the USB, open a prompt in the same folder as you have the new boot image and use the same command that you did before....should have been something like fastboot flash boot boot.img.
That is what worked for me in much the same situation.
Sent from my GT-I9000 using XDA Premium App

It keeps saying unable to create a plugin over and over and over

Ah ok wait. I needed to shut down Parallels. The command ran, but it said failed in terminal. On the Xoom, it says "Boot command is not allowed on consumer devices, Failed to process command error (0x8)"

bloodmut said:
It keeps saying unable to create a plugin over and over and over
Click to expand...
Click to collapse
Unable to create a plugin....hmmm..that one is new to me.
Still don;t panic. If there is a way to get into Fastboot then there is a way to install a new boot image.
Did you type adb remount to start out?

Just unlocked it again using ./fastboot-mac oem unlock...but when i type ./fastboot-mac boot boot.img it says the boot command is not allowed on consumer devices even though I unlocked it...also could you link the .img i'm supposed to use just so I can be sure lol

and no ./adb devices doesn't show my xoom

Here is the boot image...
http://forum.xda-developers.com/showthread.php?t=978013
and shouldn't the command be:
./fastboot-mac flash boot boot.img

Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!

bloodmut said:
Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!
Click to expand...
Click to collapse
No worries...I viewed it the same way. Down the line the knowledge you have been getting with this process will serve you well. Anyone can one-click, but doing it this way we learn how and why things work in Android.

Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch

Ended up flashing stock boot, system, and recovery images and am back to stock with no problems. Again, thank you for your patience and help.

bloodmut said:
Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch
Click to expand...
Click to collapse
Actually I would go in and flash Tiamat's kernel via CWM. That worked for me in restoring my wifi.
Otherwise you can run the following commands to restore wifi (I think...)
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
EDIT....OR you can just go back to stock and start again. Good luck.

Phone Kinda Bricked

I have HTC Panache. I tried to install Ice Cream Sandwitch on my Phone
http://forum.xda-developers.com/showthread.php?t=1341847&page=17
The phone rebooted using ROM manager. it was extracting. I believe I pressed the power button. Anyways, the phone rebooted and now its just showing the MI logo and a sound that indicates that its a new rom but doesnot goes futher..
I tried to reboot using adb . But when I go into the Clockwork mod recovery, it just shows a hat with a yellow round arrow underneath it. My Clock work mod recovery version is 5.0.2.0

Just discovered
My version is as follows. Is it some thing to be worried ?
<6>[ 6.091674] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.

chem.manish said:
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
Click to expand...
Click to collapse
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devices
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.

saranhai said:
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devces
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
Click to expand...
Click to collapse
Correction, first command should be-
fastboot devices

Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command

ahaseeb said:
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium

saranhai said:
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.

He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.

Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !

Tez MyTouch said:
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Click to expand...
Click to collapse
eng bootloader you can use fastboot with, and you can change more stuff.
correct me if i'm wrong...

chem.manish said:
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
Click to expand...
Click to collapse
You mean I should follow all the steps of rooting once again ?
Jack_R1 said:
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Click to expand...
Click to collapse
So you mean, I should install bootloader using adb again ?
What was the command flash ... ?
When I type reboot recovery, it goes into the bootloader and a phone appears.. Thats all

When your phone is booting, run "adb shell" and watch. The "#" sign should appear.
If the shell stays and doesn't drop out when the phone is bootlooping (the sign is still there after 2-3 minutes) - you're good to go.
WARNING: YOU'LL BE FLASHING BOOTLOADER. WRONG MOVE - AND YOUR PHONE IS A BRICK.
Since you're already running a rooted OS, "adb shell" should present you with "#" sign.
The thread below has steps to flash engineering bootloader. Don't use those steps, but download the bootloader and check the md5sum (do me a favor and don't ask how to do it, simple googling will spill you 200000000 answers). Put the bootloader into your ADB directory.
http://forum.xda-developers.com/showthread.php?t=858996
Direct link to the file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
Now, to flash engineering bootloader while you're in the ADB root shell, use these steps:
Open Windows' Command prompt in the ADB directory (DO NOT enter ADB shell yet!).
Type (EXACTLY as below):
adb push hboot_dhd.nb0 /data/local/
adb shell
("#" should appear)
cd /data/local/
dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18
You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah
Now reboot into bootloader, see that you have 0.85.2007 version, enter FASTBOOT mode (select FASTBOOT with volume keys and press power button), and from there you can follow the suggestion above to fastboot flash the recovery, or anything you want.
And on the side note: you won't see any ICS in MIUI that you've attempted flashing. You should have read the thread - it clearly says "all the ICS changes are under the hood, visually it's just a regular MIUI".

I do not see # sign when i type adb shell..
Means I have to root again ?

What do you see? "$"?
In that case, try typing "su" and see if it brings you root.
If it doesn't - you can try to achieve temp root like when downgrading, using fr3vo.
For instructions - section "gain temp root" from the following thread:
http://forum.xda-developers.com/showthread.php?t=1178912
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.

this link returns me error
an error occured while running the exploit <-1> errno 25..
Probbaly because its already exploited may be ?
I am stuck and confused..
Dont know what to do :S

Jack_R1 said:
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
Click to expand...
Click to collapse
This.
Please google up "mt4g return to stock" or "mt4g apply pd15img", I'm sure there are enough guides to find.

Though applying pd15img.zip is pretty simple, there is even a simpler way for you to return to stock - just find the panache ruu executable in dev section, connect your phone to pc and run that exe.

Is this the file you are referring to ?
http://dl.dropbox.com/u/25823285/RUU...466_signed.exe
I have heard about phones being bricked. So do I need to be extra careful ?

It worked. Great. Now I am on HTC Sense. 2.1 !
Sounds great
Now should i start from zero again ?

ADB Walkthrough

So I got this help in the CM Q&A but while I've rooted man devices (mostly with oDin and one-click utilities) I've never used ADB and now I'm wanting to go from a sense to AOSP ROM and can't find active links to ADB or tutorials other than (type something here), youtube hasn't been help either, can someone help e out? I had a hboot 1.85 XL so I had it easy when I rooted.
LINKS
3.18 RUU Downloaded
S-Off Thread: http://forum.xda-developers.com/show....php?t=2155071 open in tab but the instructions aren't user friendly
Downgrade Touchscreen: http://forum.xda-developers.com/show....php?t=2159863
TWRP Recovery: http://goo.im/devs/OpenRecovery/evita downloaded
***openrecovery-twrp-2.3.3.1-evita.img or 2.3.3.0 are recommended at the time of this post***
OPTIONAL- Remove red text from splash screen: http://forum.xda-developers.com/show....php?t=2156368
INSTRUCTIONS
Thanks to @InflatedTitan for this breakdown.
While waiting for the RUU to download...
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp *SEE NOTE BELOW*. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp. (Instructions below, insert whatever recovery image you're pushing)
Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
*Note as of the 06/26 Nightly, you do NOT need to downgrade your touchscreen. However if you encounter any touch-related problems using TWRP 2.3.3.x, you should flash the downgrade in fastboot to move on. I'd recommend 2.5.0.0 on the latest touchpanel firmware. It works for me but if you run into trouble, downgrade the touchscreen and flash the recommended TWRP recovery.

ADB is a command line shell for accessing your phone remotely using linux commands. So many linux command line commands will work within adb. To become an ADB master, use linux command line.
As for downloading ADB and fastboot...
https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip

I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Edit after hours searching came across helpful info, but after changing the directory and putting int adb reboot bootloader i get "error device not found" when my phone is connected, any clue?

USFguy said:
I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Click to expand...
Click to collapse
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?

exad said:
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?
Click to expand...
Click to collapse
"error: device not found"

USFguy said:
"error: device not found"
Click to expand...
Click to collapse
this is what i got....

USFguy said:
this is what i got....
Click to expand...
Click to collapse
is your phone plugged in with the rom booted and USB debugging turned on?

exad said:
is your phone plugged in with the rom booted and USB debugging turned on?
Click to expand...
Click to collapse
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish

USFguy said:
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish
Click to expand...
Click to collapse
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'

USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.

exad said:
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.
Click to expand...
Click to collapse
i'm actually getting the no devices connected again since the ruu finished running.

Press and hold power until the phone shuts off then press and hold volume down until the bootloader comes on then try again
Sent from my HTC One X using xda app-developers app

USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
Twrp 2.6 works great. No real reason for 2.3.3.1 anymore but nostalgia.
Sent from my HTC One XL using xda premium

fastbootd

Devs and end users:
I need someone out there to show me how to get into fastbootd. this one completely blindsided me. I need a hand here. Can someone draft up a clear and concise tutorial? There's a donation in it for whoever helps me. If the tutorial has screen shots and an essay for a tutorial, even better. Again, donation up for grabs as soon as someone out there helps me achieve my goal.
In addition, since fastbootd is new to me, please tell me if I need to download tools and whatnot to further achieve my goal. I'm honestly resisting the temptation to buy an international oneplus 8 to get the OTA's we love so much.
I'm posting screen shots of what I've been trying to do. I'm reaching the point of saying "the hell with it" and buy an international version.
Screen shots are sequence I've been using for fastbootd.
1. home screen (boring home screen but I could care less)
2. language selection
3. menu right before choosing fastboot or stock recovery
4. fastboot or stock recovery menu
4a. I didn't post the fastboot screen because it's the same as it was (you all know what it looks like)
Damn man. I'm usually so good at these sort of things but again, I got blindsided. <scratching head in frustration and disbelief>
Thanks guys!

sameog said:
Devs and end users:
I need someone out there to show me how to get into fastbootd. this one completely blindsided me. I need a hand here. Can someone draft up a clear and concise tutorial? There's a donation in it for whoever helps me.
Click to expand...
Click to collapse
If you have TWRP it will only reboot to TWRP when trying to get into fastbootd. If you don't have TWRP it's very simple.
Reboot to bootloader, with your phone plugged into a computer and CMD open type "fastboot reboot fastboot" this will bring you to a menu that looks just like stock recovery it is actually fastbootd

Some_Ghost said:
If you have TWRP it will only reboot to TWRP when trying to get into fastbootd. If you don't have TWRP it's very simple.
Reboot to bootloader, with your phone plugged into a computer and CMD open type "fastboot reboot fastboot" this will bring you to a menu that looks just like stock recovery it is actually fastbootd
Click to expand...
Click to collapse
This is what I'm doing:
i'm using the minimal fastboot adb tool.
I type in : fastboot reboot fastboot
the result: unknown reboot target fastboot (nothing happens)
I'm so stuck and confused. not mad here, just confused.

sameog said:
This is what I'm doing:
i'm using the minimal fastboot adb tool.
I type in : fastboot reboot fastboot
the result: unknown reboot target fastboot (nothing happens)
I'm so stuck and confused. not mad here, just confused.
Click to expand...
Click to collapse
Ok it looks like the above was right though kind of vague so let's take it from the top.
1. You are in regular homepage on phone
a. adb devices (This should show your serial # and the word, "device"
b. ADB reboot bootloader
c. Once rebooted to bootloader, "fastboot reboot fastboot" D-U-N, done.
2. Can't get into phone or soft brick
a. Turn off phone and press VOL+ and VOL- plus power button
b. Oncce in bootloader then "fastboot reboot fastboot" D-U-N, done.
Hope this helps and happy moding!

Nathan.7118391 said:
Ok it looks like the above was right though kind of vague so let's take it from the top.
1. You are in regular homepage on phone
a. adb devices (This should show your serial # and the word, "device"
b. ADB reboot bootloader
c. Once rebooted to bootloader, "fastboot reboot fastboot" D-U-N, done.
2. Can't get into phone or soft brick
a. Turn off phone and press VOL+ and VOL- plus power button
b. Oncce in bootloader then "fastboot reboot fastboot" D-U-N, done.
Hope this helps and happy moding!
Click to expand...
Click to collapse
Damn man, still getting nothing. I went to youtube as well -- only one guy upload a video and it's hella hard to follow.

Nathan.7118391 said:
Ok it looks like the above was right though kind of vague so let's take it from the top.
1. You are in regular homepage on phone
a. adb devices (This should show your serial # and the word, "device"
b. ADB reboot bootloader
c. Once rebooted to bootloader, "fastboot reboot fastboot" D-U-N, done.
2. Can't get into phone or soft brick
a. Turn off phone and press VOL+ and VOL- plus power button
b. Oncce in bootloader then "fastboot reboot fastboot" D-U-N, done.
Hope this helps and happy moding!
Click to expand...
Click to collapse
You need the latest adb and fastboot tools for this and the minimal install from xda isn't the latest it is quite a bit older so it doesn't have access to fastbootd you need to uninstall the minimal tools and get a copy of the latest ones

I don't want the donation.
Let me know if you can reboot into the bootloader by entering 'adb reboot bootloader'? If so, what happens when you enter 'fastboot reboot fastboot'?
If you can't reboot into the bootloader, what's happening there with the adb command?

sufoalmighty said:
I don't want the donation.
Let me know if you can reboot into the bootloader by entering 'adb reboot bootloader'? If so, what happens when you enter 'fastboot reboot fastboot'?
If you can't reboot into the bootloader, what's happening there with the adb command?
Click to expand...
Click to collapse
I just downloaded adb fastboot v.29.0.2.
I launched fastboot v29.0.2 (phone was in fastboot mode already) and typed in fastboot reboot fastboot.
Phone rebooted into fastboot but no fastbootd (I heard fastbootd has the fastbootd on the top of the screen)
Progress....I suppose but still swinging at home plate with nothing but foul balls.

sameog said:
I just downloaded adb fastboot v.29.0.2.
I launched fastboot v29.0.2 (phone was in fastboot mode already) and typed in fastboot reboot fastboot.
Phone rebooted into fastboot but no fastbootd (I heard fastbootd has the fastbootd on the top of the screen)
Progress....I suppose but still swinging at home plate with nothing but foul balls.
Click to expand...
Click to collapse
No, you may not see fastbootd at the top.
After fastboot reboot bootloader, enter 'getvar is-userspace' if the reply is Yes, then you're in fastbootd. Let me know if the reply is no

sufoalmighty said:
No, you may not see fastbootd at the top.
After fastboot reboot bootloader, enter 'getvar is-userspace' if the reply is Yes, then you're in fastbootd. Let me know if the reply is no
Click to expand...
Click to collapse
Here's what I've done:
I'm using minimal adb fastboot v1.43. using command prompt, I've entered: fastboot reboot bootloader
entered: getvar is-userspace
result: 'getvar' is not recognized as in internal or external command, operable program, or batch file. (I copied this verbatim from the command prompt screen)
NOTE: My phone is the tmobile variant. Bootloader is unlocked and sim is also unlocked. Could these be factors that's hindering my goal?
Thanks.

sameog said:
Here's what I've done:
I'm using minimal adb fastboot v1.43. using command prompt, I've entered: fastboot reboot bootloader
entered: getvar is-userspace
result: 'getvar' is not recognized as in internal or external command, operable program, or batch file. (I copied this verbatim from the command prompt screen)
NOTE: My phone is the tmobile variant. Bootloader is unlocked and sim is also unlocked. Could these be factors that's hindering my goal?
Thanks.
Click to expand...
Click to collapse
That shouldn't factor in. Do this:
1. adb reboot bootloader
2. Once in bootloader 'fastboot reboot fastboot'
3. once rebooted 'getvar is-userspace'

sufoalmighty said:
That shouldn't factor in. Do this:
1. adb reboot bootloader
2. Once in bootloader 'fastboot reboot fastboot'
3. once rebooted 'getvar is-userspace'
Click to expand...
Click to collapse
1. adb reboot bootloader (I did this while on my home screen with the phone all booted and loaded)
2. now, the phone is on this part -- please see screen shots.
Man, this fastbootd process is the hardest. Question is now: is it really worth it?

I probably can't help here, but did you download adb/fastboot directly from Google?

BeardKing said:
I probably can't help here, but did you download adb/fastboot directly from Google?
Click to expand...
Click to collapse
I accept any and all help I can get at this point. I thank you for jumping in. I just downloaded platform 30.0.3. I've unzipped the package. What's next?

sameog said:
I accept any and all help I can get at this point. I thank you for jumping in. I just downloaded platform 30.0.3. I've unzipped the package. What's next?
Click to expand...
Click to collapse
Well now we know you have a legit copy of adb/fastboot. Try the instructions posted by @sufoalmighty in post 11 again.

sameog said:
I just downloaded adb fastboot v.29.0.2.
I launched fastboot v29.0.2 (phone was in fastboot mode already) and typed in fastboot reboot fastboot.
Phone rebooted into fastboot but no fastbootd (I heard fastbootd has the fastbootd on the top of the screen)
Progress....I suppose but still swinging at home plate with nothing but foul balls.
Click to expand...
Click to collapse
download the latest platform tools from Google and unzip it into a folder and open a CMD from the folder and that way your ADB will be up to date. also fastbootd is basically stock recovery menu that's how it will appear Chinese writing options and then English on the bottom.
https://developer.android.com/studio/releases/platform-tools

Some_Ghost said:
download the latest platform tools from Google and unzip it into a folder and open a CMD from the folder and that way your ADB will be up to date. also fastbootd is basically stock recovery menu that's how it will appear Chinese writing options and then English on the bottom.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
downloading android studio now -- yes, the whole suite.

sameog said:
downloading android studio now -- yes, the whole suite.
Click to expand...
Click to collapse
android studio didn't do me any good at this point. Still stuck on this: getvar is-userspace
I really need an essay with screen shots to "see" what I should be doing and what I should be looking for. Gonna step away from this before I pound a keg to clear this headache called "fastbootd."

sameog said:
android studio didn't do me any good at this point. Still stuck on this: getvar is-userspace
I really need an essay with screen shots to "see" what I should be doing and what I should be looking for. Gonna step away from this before I pound a keg to clear this headache called "fastbootd."
Click to expand...
Click to collapse
You are probably doing it wrong. You should be typing
Code:
fastboot getvar is-userspace
NOT just `getvar is-userspace` as @sufoalmighty said. (There is no executable `getvar.exe`. `fastboot.exe` is the program and `getvar is-userspace` is an option to it.)

octalkey said:
You are probably doing it wrong. You should be typing
Code:
fastboot getvar is-userspace
NOT just `getvar is-userspace` as @sufoalmighty said. (There is no executable `getvar.exe`. `fastboot.exe` is the program and `getvar is-userspace` is an option to it.)
Click to expand...
Click to collapse
All good here! I got it figured out. 2 devs helped me out on telegram. XDA rules!:good: