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
Related
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.
Hey guys. I am running ubuntu 10.10 and i have successfully installed android sdk and the eclipse in their proper places and added the neccessary coding to make everything work. One problem though. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL. i know others have achieved to being able to flash it without a problem.. I have tried to troubleshoot this myself with the help of the internet and xda... but still the same problem keeps re occuring. and to tell you the truth, it is really pissing me off. I have downloaded fastboot drivers and placed them in the sdk/tools folder and moved adb to that folder as well for easier access. I dont know what else to do. If any one has any solutions or would be a help please. Thank you for reading.
bosna110 said:
. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL
Click to expand...
Click to collapse
The question is: can linux see the phone (plug in the phone while in fastboot mode and check dmesg)
If linux sees it and fastboot can't.. make sure its not permission issues [read is fastboot running as root? if not can your user read the USB device?] The phone identifies its self differently in fastboot mode vs. adb/mass storage mode. So don't assume the fact adb works from your normal login means fastboot will also.
linux sees it no problem.. but when im in fastboot mode, its not wanting to list the device.
Try executing fastboot as root.
Sent from my Gingerbread on Dream using XDA App
ok give me 1 sec.. ill go try it our right now. i am trying to flash terry's spl and radio so i can have the extra 14 or 15 megs of ram extra because my g1 is so sluggish right now i can barely use it for anything.
Strange thing with me is that it loads a different driver in fastboot. If I have it turned on normally, in my Device Manager it shows as "ADB interface -> HTC Dream Composite ADB Interface". (I think it used to show as just "HTC Dream"). I had to switch to HTC Bootloader. :/
Edit: only skimmed. Missed anything about Linux.
He's on linux ... the drivers should load automatically.
Sent from my Gingerbread on Dream using XDA App
ok i must be doing something wrong its either me or the laptop.. im doing "su" on the terminal and then when i enter in my password, it says auth failed.... this is friggen bee ess
Try
sudo fastboot devices
And when asking for the password you enter your user's password.
Sent from my Gingerbread on Dream using XDA App
still doing the same thing.
ok, what i did was
1. open terminal
2. cd sdk/tools
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
4. then when i look at the listed devices, my phone isnt listed..
5. then i try doing sudo fastboot devices and entering my password and its still not working.
let me try restarting my laptop.. perhaps that is going to fix it..
ok, just to make my self look dumber lol.. when my phone is shut off
i pressed back and the power buttons at the same time until the white screen with the android skateboards come up.. am i supposed to then press the trackball button to get into fastboot mode?
cause maybe i am not pressing something correctly to get it to work right. ill keep refreshing this page every minute for a reply..
bosna110 said:
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
Click to expand...
Click to collapse
adb will never work if you are in fastboot mode... and fastboot will only work when in fastboot mode.
so Dont run './adb devices' run './fastboot devices' or as we mentioned to run it as root 'sudo ./fastboot devices'
ok, gotcha. when i did the ./fastboot devices, it told me the Permission denied.
im sorry, i must be really brain dead right now.. i totally forgot to checkmark fastboot as an exectuable on its properties.. now its recognizing my G1 no problem. now its the flashing that is giving me some trouble
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
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!