Database Info

Rooting issues - ADB unable to locate phone in fastboot

Hi everyone,
I have looked everywhere on google and have been at this for over 5 hours now. I have tried rooting my phone from 3 different PCs (XP SP3, SP2 and 7). With all of them i have managed to get the drivers for adb installed (after many problems) and got all the way to the fastboot part of the rooting.
Once i get there, i have the same problem on all 3 PCs. ADB can no longer find my phone! Following the instructions, i checked for the device before i powered it off and found it by doing abd devices in cmd prompt. The moment the device is powered off and then back on, bam! No more device!
I am at my wits end at this point and just don't know what else I could possibly do! I would be immensely grateful for ANY advice.
I did check that my device allowed USB debug so that's not it either.
Also, my phone is a Rogers phone and I have just put through the upgrade they sent this morning.

adb cant find your phone in fastboot mode but fastboot can
Try writing fastboot devices instead of adb devices
All the comands in fastboot mode start with fastboot...e.g fastboot flash xxx xxx.img

I ran into this problem as well on my attempt, I forgot to re-enable (or enable) depending on where I was at "usb debugging" which is in:
settings> applications > development > check the usb debugging box.
After that, when you do abd devices in your shell, it should surely list after that. Good luck!
edit-- woops scratch that.. sorry I just read back that you made sure of that.

Thank you for that!
Now, i see it in fastboot, but when i try typing fastboot boot recovery.img i get a "cannot load recovery.img"
Sorry, apparently i need a lot more hand holding than i though!
(this is where I am getting the instructions from HowardForums. I'd post the link but I can't do that yet on this forum...
Basically, these are the instructions i am following:
If the phone you have is an HTC Magic (no hardware keyboard), the method is pretty much the same. I modified Haykuro's zip with files that were meant for the Magic. You can grab it here:
*link*
Again, open another command prompt as steps 2, and 6-8 are entered in the command prompt.
Quote:
Originally Posted by Haykuro-ish
0. Place update.zip on SD card.
1. power off the phone and boot into fastboot (hold back and power)
2. fastboot boot recovery.img
3 [optional]. make a backup with nandroid
3. apply update. (LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
4. reboot out of recovery mode.
5. power off phone, hold back button and power to boot into fastboot again
6. fastboot flash boot boot.img
7. fastboot flash recovery recovery.img
8. fastboot reboot
enjoy!
These are pretty much the Haykuro instructions for the Dream, which I modified to apply to the Magic. The boot and recovery images were made by Amon_RA. Happy Rooting!
Just like with the Dream, the first part flashes a good SPL, the second flashes a rooted boot and recovery. The easiest way to test if the device is rooted is to open another command prompt in the tools dir and type
Code:
adb root
If it returns that adb is already running in root, then you're all set.
Click to expand...
Click to collapse
Am i doing something wrong?
Thanks so much!

You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...

eyegor said:
You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...
Click to expand...
Click to collapse
Again, thank you so much! It seems I am still having issues as now I'm being told that "remote not allow".... is this a rogers thing?
Again i do apologize for all the hand-holding necessary here

yes, i am getting this <remote:not allow> message too. I was able to fix my other magic (purchased in october) via fastboot boot recovery.img but not this new one i have (purchased in Dec).
Anyone have any ideas how to bypass this block of 'remote, not allowed"?

[Q] Almost fixed!

So I'm in a horrible bootloop, but I got my phone recognizing the PB31IMG file, but when I click update, then select reboot, it enters bootloop again..anyone have an idea?
It's an incredible.

Ryanism said:
So I'm in a horrible bootloop, but I got my phone recognizing the PB31IMG file, but when I click update, then select reboot, it enters bootloop again..anyone have an idea?
It's an incredible.
Click to expand...
Click to collapse
you did it from recoveryy?
in adition you posted it in A&Q of htc incredible?? i´m sure that in that thread can someone help you.. here are a lot of noob people..

did it there..no responses
No, from hboot. I can't get to recovery.

Ryanism said:
did it there..no responses
No, from hboot. I can't get to recovery.
Click to expand...
Click to collapse
if you can enter into bootloader you can enable usb debug yes?
okay you can copy paste another or the same rom to sd card and then flash it via adb.

Never heard of ADB what is it and where can I get it?

And I've added the files with the SD card reader, not sure i'm able to read the phone with it plugged into my comp..

Ryanism said:
And I've added the files with the SD card reader, not sure i'm able to read the phone with it plugged into my comp..
Click to expand...
Click to collapse
try it... put your device in the bootloader (hboot) and conect it to your pc if you have installed the htc sync drivers and the pc recognices your device you are able to do usb debug for run adb parameters.
ADB PARAMETERS are part of the software of "sdk" of android (software development kit)
download from here http://developer.android.com/sdk/index.html
and read about it browsing in google....
sdk runs in a windows CMD
is the only way to restore your device if you can´t enter into recovery menu
later when you read about and how to use adb commands i´ll post here the exact commands that you must to enter for restore your device..
but tomorroww now i´m going to bed here are the 4:08 am

I"m installing it now, thanks so much..hopefully I can figure this out.

So I got to cmd..made it to "adb devices" and it said "list of devices attached", but nothing was listed.

Also, when I type adb devies, I get * daemon started successfully *

Ryanism said:
Also, when I type adb devies, I get * daemon started successfully *
Click to expand...
Click to collapse
okay lets go....
if you write in the CMD (in the sdk folder) this:
"adb" (ENTER)
"adb reboot"(ENTER) for example... your device should to reboot... try it and let´s go to flash a rom
EDIT: remember.. for to run any adb comand you must to stay in adb folder..
if i don´t forgot it it´s in "platform-tools" folder of the "sdk file"
in my case:
c:\users\evodroid}cd..
c:\users}cd..
c:\cd sdk
c:\sdk}cd platform-tools
c:\sdk\platform-tools}adb
c:\sdk\platform-tools}adb reboot
daemon sucesfully.....
..... wait... (the device reboots)

OK..wait, I have an androidsdk folder in my C:/..not adb folder..

I'm getting an error: device not found

I put in my root C:/ an adb folder and i also copied its contents to the tools folder in my androidsdk folder as well..

Ryanism said:
OK..wait, I have an androidsdk folder in my C:/..not adb folder..
Click to expand...
Click to collapse
adb its the parameter, not a folder..

you must put the sdk folder (the general) into the root of c:\
then browse where you have the adb files (nornally in the sdk--platform-tools)
in this folder you can use adb parameters
when you write "adb" (enter) shows you the all the functions that adb has????
if it happens your sdk its installed well

I believe I did what you wrote and it didn't work. at adb reboot, nothing happened. Doesn't recognize my device.

hi mates!i´m new here and i´m reading about your thread and i had the same problem are you doing it from the bootloader or fastboot?
EDIT: ei sergi.3210!!!!!!!!! are u the same person that the developer roms from htcmania.es?¿?¿?¿?¿?¿? ooohh man you are in the all the sites hahahha
i have your hero rom installed and works great,, and your "serkernel12c" my hero its working at 714 mhz!!!!

spike_14 said:
hi mates!i´m new here and i´m reading about your thread and i had the same problem are you doing it from the bootloader or fastboot?
EDIT: ei sergi.3210!!!!!!!!! are u the same person that the developer roms from htcmania.es?¿?¿?¿?¿?¿? ooohh man you are in the all the sites hahahha
i have your hero rom installed and works great,, and your "serkernel12c" my hero its working at 714 mhz!!!!
Click to expand...
Click to collapse
cheers.... yes i am... welcome spike we meet again

Ryanism said:
I believe I did what you wrote and it didn't work. at adb reboot, nothing happened. Doesn't recognize my device.
Click to expand...
Click to collapse
are you doing like spike says? from the bootloader or from fastboot? windoze recognizes your device?

100$ to whoever can help me solve this (NO JOKE)

i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*

Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium

it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed

Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f

Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium

Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command

If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.

Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way

Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.

Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz

OP... check your PM inbox.

Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App

scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file

Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps

mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.

Yes thank you guys i love u all

check your mp , excepted if you found the solution.

$100? Lol
Sent from my Nexus S using XDA App

crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App

Blackstone - Fastboot Problem

Well I am trying to Flash the latest fagyi NAND for Blackstone - http://forum.xda-developers.com/showthread.php?t=1914723
So I did everything, but when I reached the fastboot thingy, I did this:
After ROM flashed, took batter out and restarted device.
Blue screen showed up, forced fastboot, ready USB state, so I connected to PC
Then I opened a command prompt, so now what should I enter in the command prompt! I am using fagyi's fastboot!
Thanks, in advance!

Sorry for double posting, but please someone answer me, or atleast give me a tip/advice!

Do you mean this part?
13. Now connect the Blackstone to your Windows OS and open a CLi/Command prompt
14. Within CLi go to the directory where you place the 'adb files & fastboot.exe' files (from step 2)
15. Type: fastboot flash recovery recovery.img (this will flash install the custom CWR)
16. Then type: fastboot boot recovery.img (this will reboot your Blackstone into CWR)
Click to expand...
Click to collapse

post-mortem said:
Do you mean this part?
Click to expand...
Click to collapse
Yeah that exactly!

Step 2 says
2. Extract the 'adb files & fastboot.exe' files to a folder
Click to expand...
Click to collapse
so the 1st question is, do you know what folder you put those files in? Note that we're talking about your computer, not your phone. On your computer, open a command prompt by doing Start -> Run... -> cmd (This is Step 13). Navigate to the folder from Step 2 This is Step 14). Then, type the appropriate commands from Steps 15 & 16.
Still don't get it? Ask away!

Um the files are placed in C:
And when I enter the commands, it says 'File too big to fit in memory"? What do I do now?

So your step 14 should be to type cd c:\, then 15 fastboot flash recovery recovery.img
Is that when you get the error?

Yes, exactly then!

Ok, try redownloading the fastboot program, or install the Android SDK to get the newest version directly from Google.

I've redowloaded it alot of times! And I already have the Android SDK and am using the latest one!

Are you sure that you're using the correct version of all relevant programs? By that, I mean 32 vs 64-bit.

I am not sure about that, how should I know?

Do you get the same error if you type fastboot devices ?

I havent typed that yet!
EDIT: No I get this - "RH104393397 fastboot"

Please Admin/Moderator, lock this thread, my problem is now fixed!

Angat said:
Please Admin/Moderator, lock this thread, my problem is now fixed!
Click to expand...
Click to collapse
Can you tell me how do you fix the problem ? I have the same problem

[Q] I need help with my Nexus 5 with no OS on it.

I screwed up trying to restore and now it says the phone is not rooted and has no OS installed on it. I still have access to the custom recovery if that helps. I have tried using ADB and Fastboot but it does not seem to be working. I need to know asap because it is for my dad and he travels a lot. He needs a phone. Please any help is appreciated.

1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work

First of al: It's best to not use Windows 8 since there have been some driver incompatibilities and I'm not sure if they have been completely fixed yet.
Install 'Universal Naked Driver' and 'Minimal ADB and fastboot'. Both can be found here on xda.
Download the latest factory image for hammerhead from Google website. Extract the downloaded file twice and copy over everything to your 'Minimal ADB and fastboot' install dir.
Double click the flash-all.bat while your phone is in bootloader mode.
This will COMPLETELY reset your phone (all personalbdata will be wiped). Only the bootloader will stay unlocked.

awsumatt said:
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
Click to expand...
Click to collapse
When trying step 3, it says cannot read sideload.

The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?

What does the terminal say as an error? And are you running Linux, Mac, or windows?

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
Yes that is exactly how i entered it but with the file name of course. Although I did try your method but i don't see any file called flash-all.bat.

So just gonna ask again, what message did you get in the terminal?

Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)

experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
okay nevermind my last comment. Now it says fastboot is not recognizable internal or external command. Press any key to exit

After you copied all the files into the Minimal ADB and fastboot folder the flash-all.bat should be in the same directory as fastboot.exe. Is this the case?

Try adb kill-server then (I'm a little rusty with windows) su adb start-server

experience7 said:
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
Click to expand...
Click to collapse
Okay after I run the flash-all.bat, it just hangs at waiting for device

Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)

experience7 said:
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
Click to expand...
Click to collapse
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.

sbecerra407 said:
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
Click to expand...
Click to collapse
Install this(fastboot + adb): http://forum.xda-developers.com/showthread.php?t=2588979
Download the file for Nexus 5: https://developers.google.com/android/nexus/images
Extract the file
Connect phone to pc in bootloader mode
Double click in flash all script
Wait for it to finish

sbecerra407 said:
When trying step 3, it says cannot read sideload.
Click to expand...
Click to collapse
ofc... you need to ENABLE sideload on twrp itself..

Thread cleaned.
Let's keep it on topic guys,