I am trying to unlock my device and keep having the problem of it not being recognized in fastboot.
I have the latest drivers from the android SDK (4.0), and have trying reinstalling them. It appears to mount fine, and all of the adb commands work. However, when I try fastboot devices, it returns nothing. fastboot oem unlock only gives a "waiting for device".
Any ideas?
Thanks
Device needs to be in the fastboot screen of the bootloader...
Sent from my Nexus One using XDA App
While I feel really stupid for somehow missing that fact in dozens of threads, it doesn't seem to fix the problem. I now have it in fastboot and at the top is says "FASTBOOT USB". Windows recognizes the device when its plugged in, but still no luck with devices.
Nevermind, I figured it out. It downloaded fastboot from another source. I am guessing that I was somehow missing a file. Thanks though.
Related
So it seems to me that trying to read other threads about using fastboot is that it's pretty specific to the phone you're using. None of the other fastboot threads work for me when trying to get fastboot to load up on the comp here. I have it installed, have the path right, and can't get it to stay up. It pops up, runs a ton of script and closes. I never get a chance to type anything in to any line anywhere, muchless actually send a command. I need help and am totally lost
So so lost
I am totally lost and have absolutely no idea which direction to be going to learn this stuff. Any links to useful info for our phone, or anything you can find or tell me or whatever is apprechiated. I believe the problem is in the SDK, since I can never get the command screen open for more then a second. Or I may just be a total idiot. Should I be booting into fast boot on the phone and then plugging in, or plugging in then booting up? Do i have to open fastboot on the computer first or second? Or do I even open fastboot on the computer. Simply put I cannot get the phone and computer to link up, or keep a dialog box open on the computer end to send commands thru.
Ok so Ive gotten as far as knowing that I have fastboot on the computer and ADB. Now I cant figure out how to get the device to register. I uninstalled and reinstalled drivers as all the reading has told me to do. When I boot into fastboot on the phone, and plug in, the google fastboot driver recognizes the phone is there but ADB isn't coming up. In all of the reading I've done in this case it says to uninstall all drivers associated with the phone and plug it in while in fastboot. I did this, twice, to no avail. I then reinstalled all the drivers and am still stuck at not being able to get my device recognized by adb
You have to access those through a command prompt.
Sent from my Zio using XDA App
basically if it was working I may not know. I have no idea what happens or how to use fastboot or adb. but I think it should do something when I plug the phone into the usb in fastboot. it should bring up a command window for telling the phone what to do right? or do I have to do something to get the command window open. as far as i can tell everything is working like it should.
Ok this is where I must be lost. shouldnt there be a window to type the prompt in to?
YEAH NEVERMIND
Black background, no skaterboarders?
Hello.
Slowly learning noob. I have a Zio from Cricket (as yet unmodified), running Android 2.2.1. I'm a Mac user (OS X 10.6, if it makes a difference).
I've downloaded adb, and confirmed it's working by using "adb devices" to identify my phone.
I've downloaded fastboot-for-mac. I've been able to reboot my phone using "fastboot reboot". BUT, the command "fastboot devices" returns "??????????????? fastboot".
I'm wondering if my phone's actually in fastboot mode. I power-off the phone, then simultaneously press-and-hold the Send (green) and End (red) buttons. After a few seconds, I see a black screen with white writing. I do not see the white screen with 3 skateboarders that my reading here, and Google Image search, leads me to expect. I assume I'm doing something wrong. I haven't discovered what, though. Advice would be appreciated.
When you boot up with end/send the Zio boots in to fastboot yes.....
Sent from my M865 using XDA Premium App
Thanks!
That tells me I am in fastboot. Any suggestions about why "fastboot devices" returns only a string of question marks?
I don't want to proceed with rooting, etc., if I can't even get fastboot to identify my device.
You should beable to root without fastboot just dl universal androot from market and run. I personaly would wait til u have a chance to use a windows based pc to run fastboot and install spz0 2.1 rom.
Sent from my Zio using XDA App
Sounds like a environment variables path issue. Running Windows 7?
Sent from my M865 using XDA Premium App
Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html
I have a problem with trying to see the phone in cmd. Fastboot goes fine it connects I have all drivers on still nothing works at all. I can't figure it out cause I need to get rid of this bloatware.
jdwilder23 said:
I have a problem with trying to see the phone in cmd. Fastboot goes fine it connects I have all drivers on still nothing works at all. I can't figure it out cause I need to get rid of this bloatware.
Click to expand...
Click to collapse
I'm sorry but you'll have to elaborate on your problem. Are you having trouble using adb in cmd? As in no devices list when you type adb devices but they do when you type fastboot devices ? You may need to check what you downloaded/installed and make sure that the folder that it downloaded to--that you've cd'ed into to use adb/fastboot--does contain adb.exe. I suggest this installer straight from Google. Also, adb will only display/connect devices when it's not in fastboot mode.
idk
I'm having problems with getting my token code to unlock my boot loader thru HTC but I downloaded the right software and it does recognise the device as adb but when I go into cmd prompt and type fastboot oem get_token_identifier it's not recognized and doesn't do anything. So I'm stuck on getting my token for htc