Database Develop

Help with Set Up?

Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.

G1BRICKED said:
Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.
Click to expand...
Click to collapse
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
nephron said:
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
Click to expand...
Click to collapse

Also at what point are you having issues with setting this up?

nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
Ok so I have it setup as C:\android-sdk-windows and then all of the files. When I type in the first command it says
Code:
The system cannot find the path specified.
And I have the Droid Explorer Installed and everything but it doesn't have the Emulator and that's all I really want. That and FastBoot.

nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd [B]C:\sdk\tools[/B]
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
If you noticed it extracted it to C:\sdk\tools, you did yours to C:\android-sdk-windows. So you'll need to adapt to the changes..
Code:
cd C:\android-sdk-windows\tools
adb shell

Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.

G1BRICKED said:
Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.
Click to expand...
Click to collapse
A friend of mine had the same problem. Make sure the device is plugged into the back of your computer, reboot the PC and the Phone. See if that helps. And which ROM are you running?

Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging

G1BRICKED said:
Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging
Click to expand...
Click to collapse
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.

nolimit78 said:
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.
Click to expand...
Click to collapse
Well man, I tried it on FastTest and now I have a Custom Splash1 Image and now I'm not afraid of holding the Back button with the Red one. I think I'm going to throw Sense UI off to the side for now until it supports ADB and all. So thanks man, after all these monthes I finally have ADB Access. One more thing though, how can I get Emulator to work?

Now, when I try to go into Emulator through CMD, I se this;
Code:
C:\android-sdk-windows\tools>emulator
emulator: ERROR: You did not specify a virtual device name, and the system
directory could not be found.
If you are an Android SDK user, please use '@<name>' or '-avd <name>'
to start a given virtual device (see -help-avd for details).
Otherwise, follow the instructions in -help-disk-images to start the emulator
Then, I navigate to C:/Windows-SDK-Windows/SDK Setup and I allow it to run. I get two windows, one that says
Code:
Failed to fetch URL https://dl-ssl.google.com/android/repository/repository.xml, reason: HTTPS SSL error. You might want to force download through HTTP in the settings.
I close that window and go to the one that says Choose Package To Install, but the white box on the side is blank. I close that and go to Android SDK And AVD Manager. From there I go to Virtual Devices and it's blank and grey-ed out. I click new and see
Code:
Name - [I]Here I can write[/I]
Target - [I]Here I can't write[/I]
SD Card: Size [I]Here I can write[/I] MiB or KiB
File: [I]Here I can't write[/I] Browse [COLOR="DarkRed"]Dulled out[/COLOR]
Screw skins and Hardware I can do that on my own, but how can I set a Target if it is grey-ed out?

G1BRICKED said:
how can I get Emulator to work?
Click to expand...
Click to collapse
that is something I can't help you with. I am at work and it won't allow me to download what I need for that. But I am glad you got ADB workin!

Lol thanks =D

[Q] Tons of Trouble with ADB and Fastboot

I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...

Did you use the "cd" command to change the directory to where the platform-tools folder is?
That's assuming you have the Android SDK and Java Dev Kit (JDK) installed already..
Sent from my Atrix HD via XDA-Developers application

pianoman102 said:
I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Click to expand...
Click to collapse
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.

devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!

pianoman102 said:
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
Click to expand...
Click to collapse
U're welcome

devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.

skeevydude said:
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
Click to expand...
Click to collapse
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language

devilsking said:
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
Click to expand...
Click to collapse
Thanks.
That's what I thought it did. I was going to do something similar, but I couldn't remember if the correct folder was and I was just too lazy to do the research and find out. I was thinking System32, but its been so long that I couldn't remember.

[Q] PLEASE HELP!! No OS after wipe

Hello!
I have an HTC one developer edition, I did an advance wipe of my phone because it wasn't charging, it said that USB Host mode was on. It only charged when the phone was off. I decided to wipe everything but the pictures (or so I thought) but once it finished the wipe the entire OS systems was erased, know the only thing I can do is enter TWRP.
Please Help I just bought the phone!

santiolaya91 said:
Hello!
I have an HTC one developer edition, I did an advance wipe of my phone because it wasn't charging, it said that USB Host mode was on. It only charged when the phone was off. I decided to wipe everything but the pictures (or so I thought) but once it finished the wipe the entire OS systems was erased, know the only thing I can do is enter TWRP.
Please Help I just bought the phone!
Click to expand...
Click to collapse
You just bought the phone? So why did you tamper with it? go back it store and exchange under warranty.

alray said:
You just bought the phone? So why did you tamper with it? go back it store and exchange under warranty.
Click to expand...
Click to collapse
I cant just change it i bought it on EBay. Plus I'm from Ecuador so its a long way from where I bought the phone...
alistondsouza I'm going to download Android SDK and try to do every step, thanks for helping me Ill keep you updated

alistondsouza said:
Read through...
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
For step 6 which zip should I choose the same one that you have on the picture or a different one?
also what happens if the computer doesn't not read the phone ?

santiolaya91 said:
For step 6 which zip should I choose the same one that you have on the picture or a different one?
also what happens if the computer doesn't not read the phone ?
Click to expand...
Click to collapse
chose whatever rom you want as long its compatible with your device variant and compatible with your twrp version.
what do you mean by doesn't read the phone? its is not detected as sideload when you type ''adb devices''?

alray said:
chose whatever rom you want as long its compatible with your device variant and compatible with your twrp version.
what do you mean by doesn't read the phone? its is not detected as sideload when you type ''adb devices''?
Click to expand...
Click to collapse
so im on step 4, i dont know how to get the adb.exe file or the .zip on the folder. i cant even find those documents, do they get there automatically or what?
im sorry im new at this (as you can tell)
maybe somemore pictures or descriptions for step 4?

santiolaya91 said:
so im on step 4, i dont know how to get the adb.exe file or the .zip on the folder. i cant even find those documents, do they get there automatically or what?
im sorry im new at this (as you can tell)
maybe somemore pictures or descriptions for step 4?
Click to expand...
Click to collapse
download the android sdk from here http://developer.android.com/sdk/index.html

alray said:
download the android sdk from here http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
Yep, all ready did and also update 4.4 and 4.3

santiolaya91 said:
Yep, all ready did and also update 4.4 and 4.3
Click to expand...
Click to collapse
So adb.exe and fastboot.exe are located in ''platform-tools'' folder of the sdk.(adt-bundle-windows-x86_64-date/sdk/platform-tools/)
move your zip to that folder and open cmd prompt from that folder.

alray said:
So adb.exe and fastboot.exe are located in ''platform-tools'' folder of the sdk.(adt-bundle-windows-x86_64-date/sdk/platform-tools/)
move your zip to that folder and open cmd prompt from that folder.
Click to expand...
Click to collapse
ok im on that folder im currently downloading the .zip but its only adb and fastboot, not .exe.
am I doing something wrong, why wouldn't it appear like you tell me ?

santiolaya91 said:
ok im on that folder im currently downloading the .zip but its only adb and fastboot, not .exe.
am I doing something wrong, why wouldn't it appear like you tell me ?
Click to expand...
Click to collapse
.exe file extension might be hidden depending your windows configuration. Go ahead with the guide it should work.
Open a cmd prompt from that folder. (shift + right click in a blank space) (step 4)
with you device in twrp sideload mode (step 1,2,3 completed)
type in the cmd prompt:
Code:
adb devices
make sure it output your device s/n + sideload
then
Code:
adb sideload <name_of_rom>.zip
what rom did you downloaded?

alray said:
.exe file extension might be hidden depending your windows configuration. Go ahead with the guide it should work.
Open a cmd prompt from that folder. (shift + right click in a blank space) (step 4)
with you device in twrp sideload mode (step 1,2,3 completed)
type in the cmd prompt:
Code:
adb devices
make sure it output your device s/n + sideload
then
Code:
adb sideload <name_of_rom>.zip
what rom did you downloaded?
Click to expand...
Click to collapse
ok so i finally have everything ready, i downloaded http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/ this rom
sense 5.5 with 4.4kitkad.
I do all the command but it says
error: device not found
my HTC is connected and it shows in the usd
when i type adb devices:
list of devices attached.
nothing else

santiolaya91 said:
ok so i finally have everything ready, i downloaded http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/ this rom
sense 5.5 with 4.4kitkad.
I do all the command but it says
error: device not found
my HTC is connected and it shows in the usd
when i type adb devices:
list of devices attached.
nothing else
Click to expand...
Click to collapse
so your drivers aren't properly installed. download latest htc sync from htc website, it will install the drivers for you. then uninstall htc sync as it may interfere with what you are trying to do. (the drivers will remain installed)

santiolaya91 said:
I cant just change it i bought it on EBay. Plus I'm from Ecuador so its a long way from where I bought the phone...
alistondsouza I'm going to download Android SDK and try to do every step, thanks for helping me Ill keep you updated
Click to expand...
Click to collapse
Jus fastboot cwm or twrp...then install Rom of choice

alray said:
so your drivers aren't properly installed. download latest htc sync from htc website, it will install the drivers for you. then uninstall htc sync as it may interfere with what you are trying to do. (the drivers will remain installed)
Click to expand...
Click to collapse
Still nothing
same thing with or with out htc sync manager
i did this before anything else i dont know if it can interfere in any way
http://www.youtube.com/watch?v=CivvxcM1PCY

santiolaya91 said:
Still nothing
same thing with or with out htc sync manager
i did this before anything else i dont know if it can interfere in any way
http://www.youtube.com/watch?v=CivvxcM1PCY
Click to expand...
Click to collapse
did you typed ''adb device'' when the phone was booted in twrp?
Go in windows device manager and tell us how the device is listed.

alray said:
did you typed ''adb device'' when the phone was booted in twrp?
Go in windows device manager and tell us how the device is listed.
Click to expand...
Click to collapse
yes and it doesn't appear
this is what appears on device manager
when its on the bootloader-fastboot: Android usb device - my HTC
when its on twrp: portable devices WPD file system volume driver, (for like 20 seconds and then disappears)
When its off: under USB controllers as Unknown device
when its on htc screen: USB composite device ( another window opens saying drivers were not installed)

santiolaya91 said:
yes and it doesn't appear
this is what appears on device manager
when its on the bootloader-fastboot: Android usb device - my HTC
when its on twrp: portable devices WPD file system volume driver, (for like 20 seconds and then disappears)
When its off: under USB controllers as Unknown device
when its on htc screen: USB composite device ( another window opens saying drivers were not installed)
Click to expand...
Click to collapse
check my guide under faq #2

nkk71 said:
check my guide under faq #2
Click to expand...
Click to collapse
I don't have any option that says Other devices - ONE
just the ones i listed before.
I don't know if this helps in any way but i when to fastboot and the on CMD typed fastboot devices and it showed up, but if i go to twrp ADB sideload and type adb devices it doesn't show my device.

santiolaya91 said:
I don't have any option that says Other devices - ONE
just the ones i listed before.
I don't know if this helps in any way but i when to fastboot and the on CMD typed fastboot devices and it showed up, but if i go to twrp ADB sideload and type adb devices it doesn't show my device.
Click to expand...
Click to collapse
When its off: under USB controllers as Unknown device
Click to expand...
Click to collapse
have you disabled "Settings -> Power -> Fast boot"?
in either case it should show up as "Android ... -> My HTC"

using osx to unlock bootloader???

first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter

If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.

I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.

You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237

geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter

geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter

pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike

Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter

sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!

Windows 10 Razer phone 2 driver problem.

Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5

raver445 said:
Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5
Click to expand...
Click to collapse
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?

Yes usb debug mode is on...

Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
I have even tried updating the drivers and it keeps saying it can't update it even if I use the manual update settings

Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
How can I get the drivers installed then? It's driving me crazy.

raver445 said:
How can I get the drivers installed then? It's driving me crazy.
Click to expand...
Click to collapse
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.

Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.

th3cavalry said:
Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.
Click to expand...
Click to collapse
I have just rebooted my computer I'll see how it works in just a moment but I don't know if it's going to see it or not. it is still not seeing it.

Gamesoul Master said:
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.
Click to expand...
Click to collapse
So what can I do to fix this? It's driving me insane.

raver445 said:
So what can I do to fix this? It's driving me insane.
Click to expand...
Click to collapse
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?

celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
After I update it the software drivers for the computer it says Razer phone 2 but it doesn't work right. I tried doing one of those scripts to reflash to stock software and it doesn't do Jack squat it sits there waiting for device.

use samsungs usb driver installer and change adb driver to Samsung's version in device manager. should see fastboot device now .

celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
i got it to work for the fastboot devices ...but still unable to relock it

has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period

ghost9640 said:
has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period
Click to expand...
Click to collapse
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well ?
https://forum.xda-developers.com/and...ndows-t3999445

got it
JDBarlow said:
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well
https://forum.xda-developers.com/and...ndows-t3999445
Click to expand...
Click to collapse
my laptop was not seeing the device my pc is, now im trying to flash arter97 kinda stuck but thx bud

The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved

decode2533 said:
The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved
Click to expand...
Click to collapse
Lol okay..that's about as random as "hey anybody reading this thinking about getting an S20 Ultra or one of the others"
I am....

I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.

Hi All,
Thought I would post this on here for you all, might help someone else like it did me.
What ImperialMe said is correct and I was able to do both my Razor 1 and 2 using it.
imperialme said:
I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.
Click to expand...
Click to collapse
The easy method is to download the Ubuntu Image for Windows (ubuntu.com/download/desktop)
Once you have it, burn it to USB using Rufus (rufus.ie)
Boot into the USB on your PC and when prompted just run as is, no need to install.
Once running, open a terminal window and with internet access and run the following:
Code:
sudo add-apt-repository universe && sudo apt-get update
Now run:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
When promoted press Y and enter
Now run:
Code:
sudo adb start-server
Connect your phone, turned on and on the home screen for example. Run the following
Code:
sudo adb devices
You should see your device listed as unauthorised and get a prompt for ADB access on the mobile phone.
run it again to confirm its authorised and then enter:
Code:
adb reboot bootloader
Once rebooted, use the menu to select boot into fastboot on the phone
Now back to the terminal window, enter:
Code:
Fastboot devices
You should now see your device listed and commands should work as expected.
If you need to copy anything over to the temporary USB OS then use another USB drive and copy them to it before you boot the OS.
I tried this in a VM and VMWare and HyperV both failed as the drivers they use are still Windows based and failed. Only a full OS worked.
Hope this helps someone else!