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"?

GUIDE - How to flash radio.img OS X

I couldn't find a guide for this anywhere, so after a lot of trial and error, I worked out this method from various write ups on the web.
Preq's:
Make sure your battery is fully charged (I have no idea why, but it seems to be a must do thing)
You'll need the Android SDK, so make sure you have this and you'll be needing Fastboot for Mac, which you can find here Fastboot
And you need to boot your phone in fastboot mode.
Drop the Fastboot file into to the tools directory of the SDK.
Download your desired radio image and put it in the same same folder.
To make sure Fastboot is working, open Terminal and type "fastboot devices"
(without the speech marks) and hit return. You should see:
List of devices attached
HXXXXXXXXXX device
Click to expand...
Click to collapse
XXXXXXXXXX = the unique number of your phone.
If it doesn't display anything, you need to re-check SDK and Fastboot are installed properly.
If you do, carry on.
Now, the nervous part.
1. Open the tools directory of the SDK in a Finder window and the open a Terminal window.
2. Now, drag the 'fastboot-mac' file in to the Terminal window.
3. Type this (make sure you hit the space bar after typing) :
flash radio
Click to expand...
Click to collapse
4. Now, drag the radio.img to the Terminal window
(It should read something like this)
/Users/Liam/SDK/tools/fastboot flash radio /Users/Liam/SDK/tools/radio.img
Click to expand...
Click to collapse
5. Hit the return key and wait. Make sure you touch nothing.
6. When terminal has given you the "Okay" message twice, check you phone screen and make sure there isn't a red loading bar on the top left hand side of your phones screen. When this is done, type:
fastboot reboot
Click to expand...
Click to collapse
And hit return.
7. Your phone will reboot and you're done.
If I've missed anything, let me know and I'll add it.

been trying for a few days now heads gone all i get it adbwinapi.dll is missing tried several reinstalls now need help please guys system is win 7 ultimate

steve36 said:
been trying for a few days now heads gone all i get it adbwinapi.dll is missing tried several reinstalls now need help please guys system is win 7 ultimate
Click to expand...
Click to collapse
Wrong thread. But the thread you want, and the answer, is here: http://forum.xda-developers.com/showpost.php?p=10113370&postcount=91
Do some searching first..
Anyways, yeah, now I can use my MacBook.

This seems to be an odd way of doing it.
Just download the fastboot-mac binary from the htc developer page. Drop it in the platform-tools folder of the androd SDK.
Start a Terminal and run:
/path/to/platform-tools/fastboot-mac flash radio radio.img
make sure you have radio.img in the current directory where you invoke the script.

I found it easier to drag and drop the files. Saves lots of typing and does the same job.

liam08 said:
I couldn't find a guide for this anywhere, so after a lot of trial and error, I worked out this method from various write ups on the web.
Preq's:
Make sure your battery is fully charged (I have no idea why, but it seems to be a must do thing)
You'll need the Android SDK, so make sure you have this and you'll be needing Fastboot for Mac, which you can find here Fastboot
And you need to boot your phone in fastboot mode.
Drop the Fastboot file into to the tools directory of the SDK.
Download your desired radio image and put it in the same same folder.
To make sure Fastboot is working, open Terminal and type "fastboot devices"
(without the speech marks) and hit return. You should see:
XXXXXXXXXX = the unique number of your phone.
If it doesn't display anything, you need to re-check SDK and Fastboot are installed properly.
If you do, carry on.
Now, the nervous part.
1. Open the tools directory of the SDK in a Finder window and the open a Terminal window.
2. Now, drag the 'fastboot-mac' file in to the Terminal window.
3. Type this (make sure you hit the space bar after typing) :
4. Now, drag the radio.img to the Terminal window
(It should read something like this)
5. Hit the return key and wait. Make sure you touch nothing.
6. When terminal has given you the "Okay" message twice, check you phone screen and make sure there isn't a red loading bar on the top left hand side of your phones screen. When this is done, type:
And hit return.
7. Your phone will reboot and you're done.
If I've missed anything, let me know and I'll add it.
Click to expand...
Click to collapse
Hi i did not notice your guide so i created one last night >>>>here<<<<

I use this:
http://qtadb.wordpress.com/

I cannot get terminal to respond to "fastboot devices"
I think i've installed it all ? I've run the adk with android in the tools folder, and I have the platform tools folder. i've run fastboot-mac, i don't know what else to do?

P1xelVandal said:
I cannot get terminal to respond to "fastboot devices"
I think i've installed it all ? I've run the adk with android in the tools folder, and I have the platform tools folder. i've run fastboot-mac, i don't know what else to do?
Click to expand...
Click to collapse
Use my guide downloaded the zip file read all of first post sorted
E=Mc2

leith51 said:
Use my guide downloaded the zip file read all of first post sorted
E=Mc2
Click to expand...
Click to collapse
it's a shame all the files are .exe and .bat *sigh* thanks anyway.

P1xelVandal said:
it's a shame all the files are .exe and .bat *sigh* thanks anyway.
Click to expand...
Click to collapse
localhost:~ Mac$ /fastboot/fastboot-mac flash radio /fastboot/radio.img
sending 'radio' (24832 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed)
localhost:~ Mac$
what am i doing wrong? (no i will not switch to PC))
This guy used my thread his problem was he didn't have eng s-off
E=Mc2

Error: can not load recovery-Tiamat-R4c-100611-1150-cwm

So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.

I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798

supenova3000 said:
I have had the same issue for the past few days I have also tried the steps here no luck.... http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.

williamthegoat said:
I used the same guide. It just makes no sense that I can control the Xoom and unlock it, but I can't flash the darn recovery.
Click to expand...
Click to collapse
I tried moving the files from the tools folder to platform tools still no luck.. all of this for the I C S flash I'm going to keep working on a solution I will let you know if I have any luck!

So I have the android sdk in c:\ , and in the sdk folder I have everything, and in the platform tools I have my fastboot and recovery. I then use cmd to get into adb, then I put the xoom in fastboot. From there I try to flash the recovery, which always fails. I must be doing something wrong here.

Try downloading the IMG again. Or try out the rogue recovery. I actually like rogue better.
Sent from my MB860 using xda premium

I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys

Think you have to be stock to flash to ICS, at least that was the word yesterday.
I gave up trying to root just as I found out about the ICS update.

williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys
Click to expand...
Click to collapse
Two simple errors:
1) not opening the command window from the folder where you have fastboot and the image files you're trying to flash; and
2) not realizing that you have hidden file extensions in Windows, and typing ...recovery.img.img

williamthegoat said:
So I have my Xoom unlocked and I am trying to flash the recovery in order to root. I have the recovery in the platform tools folder along with fastboot and all that, and I'm able to get the Xoom into fastboot from adb, but I can't get the recovery to flash. I'm typing the name correct. And I'm putting in 'fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img' without the quotes. Honestly I'm a little bit stumped at this point.
Click to expand...
Click to collapse
I assume that you've set up a path in environment variables to run adb and fastboot from ay directory... and are running the flash command from a folder other than where your .IMG file is located. In order for fastboot to find the file you're trying to flash, you actually have to run your flash command from the folder your file is located...
So, cd\...\platform-tools and then flash

The simplest way I perform all of my operations for this:
I leave everything installed into it's default locations. I download tiamat's CWM image and place it into the platform-tools folder.
For Windows 7, I use Windows PowerShell.
For example: Open Start Menu > Type "power" to search, "Windows PowerShell" should show up. (For me, its default at the top - so I press enter to open it)
Once opened: I type this configuration EXACTLY as is: (Keys in <>)
Code:
cd C:\Pr <TAB><TAB> An <TAB> An <TAB> Pl <TAB><TAB> <ENTER>
This above brings me directly to:
C:\Program Files (x86)\Android\Android-sdk\Platform-tools\
Of course, this will be different depending upon your computer setup. I've nailed this routine to get to the path the quickest.
to use FASTBOOT (XOOM already in fastboot mode):
Code:
./fastboot flash recovery rec<TAB><ENTER>
This auto completes the filename as ./recovery-tiamat-r4c-xxxx.img
Of course, depending on how many files/folders you have, you may have to hit <TAB> multiple times. I have to do it 3 or 4 times to select the recovery image I want.
Auto-complete is a nice thing. "./" is added to command from the working directory.

williamthegoat said:
I finally got it. In command I needed to direct it to the platform tools folder and then it flashed just fine. I am now rooted. Now to learn about flashing ICS
Thanks for the responses and help guys[/QUOTE
Worked for me too!!! Thanks!!!
Click to expand...
Click to collapse

[Q] Recovery Mode inexistant

Okay, so I posted about a week ago re: my softkey issue and fortunately that was fixed by returning my phone to stock, however, I followed nexushacks method and when it told to do this:
Step 12. Once you get the Android guy with exclamation mark, hit Volume Up and Power button at the same time until you get blue menus.
Nothing bloody happens. Please don't tell me I have to hold it for something like 60 seconds because I. Will. Rage. Lol.
When I try to go into recovery I get that symbol and can't do anything but batt pull. I'm still unlocked and rooted, to my knowledge.
I downloaded ROM Manager because I wanted to flash a recovery on it but it told me that "An error occurred while attempting to run privileged commands"
It also says this when I open Rom Manager "You must root your phone for ROM Manager to function. Superuser was not found at "/xbin/su" or "/system/xbin/su". Use google blabla"
I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a responce from device" whatever that message is...
Trying to give as info as possible so someone can help a brother out.
I can't deal with this Stock OEM crap anymore *twitch*
Thanks!

Herp Derp
Okay, I didn't realize it was Press the Power button, then the volume up button.
Silly noobs.
So my question, is there a way to get Clockwork Recovery back on now or do I have to go through the whole "Rooting" process again?

I assume you see a lock symbol while booting. This means you're unlocked. Now you'll just need to use fastboot to flash a custom recovery (namely, CWM). NexusShacks details how to setup and use fastboot and i think they provide TWRP now, feel free to use this or just download CWM from here and flash that .img file instead.
After this, download the latest Superuser-3.0.7-efghi-signed.zip and flash that. Note that on a stock ROM it will flash stock recovery on every boot. To change this, rename /system/etc/install-recovery.sh to something else.

But how do I flash a .img file when I don't have Recovery mode?
Or can I use do that through the OEM Recovery (blue screen)?

You flash it with fastboot. Fastboot is a command line tool to flash various images through the bootloader screen. To enter the bootloader, turn off the device and hold Vol. Up + Power. This is the same place you would've typed "fastboot oem unlock", except to flash the new recovery you'll be typing something along the lines of "fastboot flash recovery recovery.img". NexusSHacks teaches you how to do all of this.

Ah sorry, I still get Fastboot and Bootloader mixed up.
Only problem is that I don't know if my computer is recognizing my device when I plug it in through Bootloader.
As mentioned in my original post
"I'm also in the process of trying a command prompt on windows but it keeps giving me the "waiting for device" or awaiting a response from device" whatever that message is..."

I'm at work now and trying to figure out how to do this using Terminal on my mac.
When I type in "cd /nexussrootICS" it keeps on telling me "no such file or directory"
Do I need to put this file in a specific folder? I got this step working on my PC at home but it told me "Waiting for device" the whole time.
Any thoughts?

I'm not particularly familiar with OS X so forgive anything i say that might be off target.
You need to direct the terminal to the relative OR absolute directory of that folder. A relative directory can be done by "cd ./blah", while an absolute will be done by "cd /blah". This is quite confusing for people who aren't used to command line, but very simple once you've done it a few times.
Easiest way aside from magical OS X shortcuts i don't know about is:
-Unzip the files to a "nexus" folder on the desktop, making sure the adb files are in this nexus folder and not a sub folder
-open terminal
-"cd /user/artist/desktop/nexus" or whatever the FULL PATH to the folder is. You should be able to see this through the folders properties or in the file explorer.
-Now you are in the folder, you can use adb and fastboot by just typing those words
I believe OS X can recognise the device straight away so you shouldn't need to install any drivers - at least my linux distros were like that. Installing drivers on Windows is detailed in the video, too.

Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"

TheArtist8 said:
Ah!!!! I feel like I'm so bloody close...
Okay that part worked perfectly, I found out how to at least direct Terminal to the right location but now I'm lost again...
It's giving me this
"
USER-iMac:nexus user$ ./fastboot-mac flash recovery-clockwork-5.0.2.0-crespo.img
unknown partition 'recovery-clockwork-5.0.2.0-crespo.img'
error: cannot determine image filename for 'recovery-clockwork-5.0.2.0-crespo.img'
USER-iMac:nexus user$
"
Click to expand...
Click to collapse
The command should be
./fastboot-mac flash recovery recovery-clockwork-5.0.2.0-crespo.img
You were missing the recovery flag in the command.
Sent from my Nexus S 4G using Tapatalk 2

Also do "man fastboot-mac" in terminal to show all its options.
Sent from my Nexus S 4G using Tapatalk 2

Son of a... alright ill try after my lunch.
Sent from my Nexus S using XDA

Omfg I love you guys.
Thanks so much
I just got into Recovery mode, now on to Cyber-GR

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