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.
Related
Created an Evo Splash Screen that everyone is welcome to use.
Put the file linked below into you're SDK/tools directory.
Reboot phone into bootloader.
Type "fastboot flash splash1 evosplash1.rgb565" (without the quotes) into the adb console.
Reboot and Enjoy.
Here's a link to the file you need:
http://www.megaupload.com/?d=QT6NU66C
Sun
Light
thanks its very nice
Thank you much sir! This is great
Can this be flashed with flash_image from the phone directly?
like this - flash_image splash1 filename ?
I believe it needs to be zipped and signed in order to be flashed.
I just read somewhere in google land that splash1 partition is called misc within android. I bet I'll brick it if I try to flash to misc. Or something...
When in the boot loader I can't get access to the device in adb shell. Any ideas?
eeeeeeeeek said:
When in the boot loader I can't get access to the device in adb shell. Any ideas?
Click to expand...
Click to collapse
1. Use adb to boot into the bootloader ">adb reboot bootloader"
*Once you're in bootloader adb commands don't work
2. Flash the .rgr565 file ">fastboot flash splash1 evosplash1.rgb565"
*Make sure the evosplash1.rgb565 file from the OP is in the SDK/tools directory on your PC
once in the boot loader it doesn't allow me to type anything, I can scroll between bootloader, reboot, reboot bootloader, and power down so I'm not sure if I understand step 2 of your response. Sorry Noobish on the evo, came from the samesung moment, thanks
eeeeeeeeek said:
When in the boot loader I can't get access to the device in adb shell. Any ideas?
Click to expand...
Click to collapse
I'm a noob too, but have had a little luck with ADB. Have you checked to make sure the USB Debugging in the Development menu is activated?
I have it on, I can use adb just fine when not in the bootloader, I'm just understanding how to flash from the boot loader.
Select fastboot from the bootloader. Connect your phone to the computer.
Your phone should say FASTBOOT USB near the top.
Now use a terminal and issue commands like you would with adb, only that the specific command is
Code:
fastboot flash splash1 evosplash1.rgb565
sweet that worked. Thanks!
Very nice. Like this a lot. Thank you
Created 2 more EVO splash screens for anyone to use if they wish:
Sun
Light
OP will be updated.
Jykinturah said:
Select fastboot from the bootloader. Connect your phone to the computer.
Your phone should say FASTBOOT USB near the top.
Now use a terminal and issue commands like you would with adb, only that the specific command is
Code:
fastboot flash splash1 evosplash1.rgb565
Click to expand...
Click to collapse
nevermind i got it
RickBaller said:
Created 2 more EVO splash screens for anyone to use if they wish:
Sun
Light
OP will be updated.
Click to expand...
Click to collapse
any chance you can whip up a version of light in red for my rom?
Yay 4 Juggs said:
any chance you can whip up a version of light in red for my rom?
Click to expand...
Click to collapse
Sure, post a screenshot and ill try and match it.
Yay 4 Juggs said:
any chance you can whip up a version of light in red for my rom?
Click to expand...
Click to collapse
Here you go bro.
http://www.megaupload.com/?d=H9ZGL7W7
ok so the rgb file we have to put it in the sd card directory right?
then either the sun or light file aswell?
last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
New Jer-Z said:
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
Click to expand...
Click to collapse
You skipped right over the "can't seem to able to flash a recovery."
Please explain in detail the instructions you followed AFTER unlocking via HTCdev.com. This includes files you downloaded, where you put them, how you attempted to flash, etc.
These details will be very helpful. Don't worry, sounds like you're not in any serious trouble at all. Just don't go flashing anything you see.
Also, please post this to the Q&A forum or General next time. This development forum is intended for development posts ONLY (ie. ROMs, Kernels, Radio's, etc). Just a heads up. Welcome to the forums
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Moved To Q&A
Please post all questions in the Q&A section
New Jer-Z said:
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Click to expand...
Click to collapse
Ahhh, not to stir up the pot here, but you're getting vague again with what's going on. You say "when I try to reboot into recovery, I don't get very far". What do you mean by this? Details are extremely important in helping you. Sounds like you're saying that recovery was successfully pushed, but then I didn't get any details as to what's going on when you attempt to load recovery. Also, which recovery file did you use? Use this one
I'm not trying to get on to your case here, but you've got to be really specific when you say stuff doesn't work, because that doesn't help us diagnose your issue. When your recovery is done flashing, you should be able to access the bootloader by holding Pwr + Vol-Down for like 5 secs, then choose recovery (that or fastboot>recovery....I cant recall if recovery is a main menu item). What happens after you choose that? Mine shows the htc splash screen, with a development message in red, and then it boots Clockworkmod.
No, no, lol I totally understand, I guess I am being vague.
I was going to go into details, but I was at work. Interestingly enough, my phone died, and when I plugged it and let it charge for a little bit, the phone booted right into CWM touch - so odd! So I was like, ok, i've achieved root - well, no, cuz I opened ROM Manager and it says SU couldn't be found.
BEFORE, when I would do what you said I should do, it would take me to the HTC splash screen where it was in red text, some disclaimer about some proprietary information crap, then it would skip recovery and just boot into Android -___-
Let's see if I can replicate booting into recovery now. (What method are you using to flash your recoveries?)
EDIT: Well it looks like I can't get back into recovery. Same thing as mentioned above. I can get to the fastboot screen, but if I click recovery, it takes me to that HTC disclaimer screen, the little loading bar loads then - poof - screen goes blank and Android boots up.
I have the same problem -_-! Can someone help please
The recovery image was flashed succesfully from Hasoon2000's toolkit. But when i go to the bootloader and select Recovery, I get the red warning for from HTC about how this is for development purpose only... then the phone's screen goes black, then it boots into the stock ROM.
Cant flash recovery
Hello everyone.
I have a similar problem. I successfully proceeded with the bootloader, but now I can't install the recovery. It simply wont flash.
I was following the xda tutorial that's in this very forum, but i got stuck: In my desktop i downloaded the needed files (or so I believe), and so i have in my desktop a folder called "carpeta" (random name) with these files within: adb.exe, adbwinapi.dll, fastboot and 3 different recovery images i have tried to flash.
I use mac, so i open the command prompt for mac (terminal) and go to the "carpeta" folder and after that, I type "cd fastboot flash recovery xxxxx.img" (the xxx are the names of the recovery images that i have in the folder, one at a time) but it simply wont flash anything. I attach a screenshot to ilustrate what happens...
Please help me
http :// img710.imageshack.us/img710/6026/capturadepantalla201205.png
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
I'll give it a shot later tonight on my lunch break.
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
alexjuanes said:
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
Click to expand...
Click to collapse
Make sure that you navigate to the proper folder using the "cd" command.(for example" cd C:\Fastboot ", if your adb and recovery are in that location)
Make sure that the Clockwork Mod recovery file is in the same folder as the adb and make sure that you type the file name correctly
I used these file and put the recovery image inside the folder after unzipping
http://www.mediafire.com/?50baad8rykng2j0
Here is the recovery I used :
http://loadbalancing.modaco.com/download.php?file=r2-modaco-recovery-clockwork-touch-ville.img
But your running Mac so I don't know if the method I used will work for you because I'm on Windows
Doesnt work...
I have the bootloader (when i start in bootloader mode my phone says ***tampered*** and also ***unlocked***.
BUT
I've been 2 days trying to flash my recovery on my htc one s from my macbook, and after i use the command prompt to get to the folder where i have adb, fastboot, my recovery .img file,etc... this is what happens:
-----
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$ fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
-bash: fastboot: command not found
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$
-----
ive already updated all that i could in the sdk manager, or whatever its name is...
please some help?
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
This actually worked for me. I am rooted, and am now running a custom ROM.
Thanks so much for all your help!
Hey everyone
i seem to have made a very tiny bit of progress here since now i can type the commands and make it start, but only that... starting.
my command box is stuck in a "waiting for device" message that will start nothing, and my phone is just there, untouched.
i never thought flashing a recovery would give me this much of a long headache...
help anyone? how do i make my pc stop "waiting for device"?
Have you tried a different USB cable/port? I had a similar problem but moving to a different port worked.
Sent from my HTC VLE_U
I have the same problem i did everything as in the guide posted here http://forum.xda-developers.com/showthread.php?t=1583427
But when i flash recovery through fastboot ( fastboot flash recovery recoveryname.img) everything goes ok but when i want to boot into recovery i get stuck on the HTC screen.
Than i wanted to go to recovery trough fastboot ( fastboot boot recovery ) i get message cannot load recovery.
If you need more info for help i can provide you guys with the screenshots.
Thanks in advance Nikola.
A few days ago I tried getting my phone to s-off using the "[how to] manually achieve s-off,simunlock,supercid for Inspire 4g/DHD" guide on the Android forums. (Sorry, I can't post direct links.)
I got to the part where I was supposed to type in "fastboot flash boot boot.img" to the command line but I accidentally skipped that part and typed in "fastboot boot recovery recovery.img". I stopped everything and tried to start over but when I turned my phone back on I was stuck in a boot loop. Going to hboot and trying to choose Recovery or Factory Reset only results in more boot looping.
I've tried putting PD98IMG.zip on the SD card and booting it, but it only reads it and says "Parsing..." before doing nothing. Attempting to enter recovery mode after this makes it enter the boot loop again.
I've also tried using the HTC Sense and RUU from AT&T on my computer to fix the issue. My phone can connect to my PC after choosing fastboot from the hboot menu. The RUU can see the device and it starts recovering it, as my phone shows a black background with HTC on it. But the RUU stops after trying to update the signature saying "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again." I am 99% positive I am using the correct RUU.
I've searched high and low on the internet for a similar situation, but everyone else seems to have their problems solved using either of these steps. Thanks for any help.
Without knowing what you did (since you haven't given us a step-by-step and can't post links), we don't know how to help.
Sorry about that. I'll try to explain what I did the best I can.
Before using the guide, I managed to root my phone and used it for a few days, so everything was fine then. I later decided to s-off it so I could flash a custom ROM to it. Using the guide I mentioned above, I created a mini-adb directory in my C: drive with the ace-tools.zip that I downloaded. Using the command line I copied my stock boot image, though to where I do not know. (I feel like a fool for doing all this without being sure of what I was doing exactly. I deserve what came to me.) Then, using the command line I made my SD card a gold card. After that I changed the "misc version" (?) to allow installation of the downgrade firmware, and then relocked the boot loader and booted back into fastboot. Then I flashed the downgrade software and unlocked it again. It's here that my phone was supposed to be unable to boot, and I was supposed to flash the boot image but skipped that step.
Now I'm unsure of what I have to do, and I only want to get my device working again.
I wish I could post the link to the exact topic, but since I can't I guess you'd have to search the topic name to see exactly what the directions were trying to get me to do.
Thanks again.
Can you boot the phone into fastboot and flash the boot.img from fastboot?
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
SammichMonster said:
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
Click to expand...
Click to collapse
Wait. What? Not PD98IMG.zip from hboot. Extract the boot.img and flash from fastboot, not adb.
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
SammichMonster said:
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
Click to expand...
Click to collapse
No, the boot.img needs to be on your computer. Your phone needs to be in fastboot mode. From the folder where the boot.img is saved,
Code:
fastboot flash boot boot.img
I can't use the command prompt to connect with the device because it can't see it. I always get an "error: device not found" instead.
Is your phone in fastboot mode?
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
SammichMonster said:
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
Click to expand...
Click to collapse
So you're booting into hboot, navigating to fastboot with the volume buttons, and selecting it with the power button? What does fastboot devices say?
I'm assuming by "fastboot devices" you mean what it says in the command prompt.
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
I'm assuming I have to load the boot.img now?
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
SammichMonster said:
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
Click to expand...
Click to collapse
That's what i figured you were doing, so that's why I clarified.
SammichMonster said:
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
Click to expand...
Click to collapse
You're welcome. You could also have fastboot flashed any custom recovery image, flashed a ROM from recovery, and fastboot flashed that ROM's boot.img. So you weren't too badly off.
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: