Hi. I've been trying for hours to get Helium backup to work with my R1 and it won't work. My G4 works fine with the same USB port and cable. When my G4 is plugged in, if I type adb devices, it shows up. The BLU phone does not show up. I've tried uninstalling and installing Helium in my computer and in the phone. I did a hard reset on the phone. I downloaded and installed the drivers Helium recommends and nothing. I simply can't make the R1 work. I've noticed a few people having the same problem in other forums but I haven't found a fix for it.
Anyone can give me some ideas? Thanks.
Did you enable usb debugging. Not calling you an android dummy but we have all forgot to enable usb debugging one time or uhnutha.
Yeah, I enabled it.
Another day trying to get adb to see my phone and nothing. I installed mtk drivers, etc and I'm still getting a blank when typing "adb devices"...
Are you using the cable from Blu? I noticed that my other devices work fine with any cable, but the R1 only seems to respond with the Blu provided USB cable.
Yeah, I started using the BLU cable just in case and it didn't make a difference.
Sent from my VS986 using Tapatalk
My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.
king200 said:
My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.
Click to expand...
Click to collapse
Don't be so sure it's not driver, because while in recovery and while in system the phone reports different mode to PC, so could be using different driver
Try going into device manager in Windows and updating the driver. Select choose from available drivers, and if there's one that's different than what is currently loaded, try that one.
Sent from my BLU R1 HD using Tapatalk
Vendor ID issue, you need to update the adb_usb.ini to include it.
I got adb to see my R1 under Windows. When you plug it in, change from MTP mode to PTP mode and unplug it, then plug back in. It works in PTP mode but not MTP mode for some odd reason.
Synir said:
Vendor ID issue, you need to update the adb_usb.ini to include it.
Click to expand...
Click to collapse
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1
king200 said:
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1
Click to expand...
Click to collapse
did it work?
Has anyone solved this issue yet?
i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.
pookeye said:
i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.
Click to expand...
Click to collapse
ADB just "works" for so many users, It leaves the dumb question . Did you enable developer options and turn adb debugging?
Also what abd are you using?
Easiest thing to do would be reinstall adb + fastboot with 15 second install.
link to that is in the unlock tool thread. Which will also answer your question what is needed to install new / other rom.
(tool unlocks bootloader, flash twrp, can install superSU,)
Related
I've Google'd the topic and all the comes up are my own post in the Dev sections where I asked how to create/get a logcat. I can "adb logcat" to a text file, then it shows "waiting for device". Now what's the procedure or setup on the S7 end? I've turned On adb debugging options in the S7. Can/ls this done by USB? The "adb devices" command while plugged into the USB shows nothing. I can connect in Fastboot mode and "adb devices" shows nothing also. Or is more of the Android SDK package needed for this?
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
giveen said:
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, since I've never used adb commands in the past, maybe not! Are they installed from a EXE file or in a INF fashion?
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
giveen said:
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
Click to expand...
Click to collapse
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
wptski said:
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
Click to expand...
Click to collapse
Um....no?
http://d-h.st/592
giveen said:
Um....no?
http://d-h.st/592
Click to expand...
Click to collapse
Yep, that's a link to the page but where's a link to actual file download? I think the third comment on the page mentions this.
If I'm not missing the driver files, I wonder if it might be that I NVflashed CM10 again but didn't allow it to reboot before restoring a TWRP backup?
All the old links to files have been changed since the DNS problems but I found a link to the old files at StreakDroid and the DNS issued is fixed. Download, unzipped, nothing looks any different to what I already have. I still tried the package anyway and it still can't find it's driver. Next I'm going to NVflash CM10 again and let it boot up fully and try it then before restoring my TWRP backup.
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
jamezz98 said:
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
Click to expand...
Click to collapse
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
wptski said:
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
Click to expand...
Click to collapse
Its because I was testing some things out in init.streak7.usb.rc
giveen said:
Its because I was testing some things out in init.streak7.usb.rc
Click to expand...
Click to collapse
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
wptski said:
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
Click to expand...
Click to collapse
It works just fine.
I'm stumped!
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
wptski said:
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
Click to expand...
Click to collapse
Restored my ICS-B4 backup, ran into the exact same issue and used the same solution to install the ADB drivers.
Hi
I have 2 Kindle Fire HD 7 inch. The 16GB is rooted and can run ADB commands from the latest FirstAide. The other is a new 32GB (arrived today) and I am trying to root it.
In XPs admin tools/computer management, the Android Composite ADB Interface driver is shown. In Properties/general, the rooted device is shown as working normally, whereas the unrooted device is shown as "Currently, this hardware device is not connected to the computer. (Code 45)"
Obviously, trying to use FirstAide to root the new device won't work if ADB isn't working.
As the PC installation is the same, and even the same USB data is being used, there must be something different with the new device. I can't believe that the storage size plays a part so what should I look at? ADB is turned on in the new device (more/device/ADB).
I do have a factory cable but don't know how that can be used in this instance. The new device seems to work normally, and both device and PC have been rebooted/reset to no avail.
Can anyone help or does it look like the device is faulty?
edit: the new device was v7.2.2 but updated itself soon after to 7.2.3 which is the same as the rooted 16GB device
I just used the factory cable and reset the device which went into fastboot mode but didn't respond to any fastboot commands. Switching off and replacing the factory cable with standard data cable saw it boot normally (I thought the boot mode was persistent until reset?)
Maybe try a factory reset on the new one and then turn off wifi until you root it.
Sent from my KFTT using xda premium
If you connected the 32gb kindle before enabling adb at any point you'll want to UNINSTALL its drivers from device manager on your PC and upon reconnect your PC will install the adb version of these drivers assuming adb is enabled.
Let me know how this works for you.
Sent from my KFTT using xda app-developers app
Thanks for the replies. I'm a little confused.
Eventually, I uninstalled the drivers from the PC. I found I couldn't install the drivers using the new FirstAide, I got an error message, so I used the old FirstAide and the drivers installed no problem. From there I could get to root. :laugh:
However, now I find that the old device isn't seen by ADB whilst the new one is..... it's as if the drivers are device specific.
Can anyone explain this to me? In my mind, the drivers, once installed correctly should work for all devices. At the moment, I'm faced with uninstalling/reinstalling drivers whenever I want to swap devices.
victorlugo do you literally mean that if you charge up the device without enabling ADB then you won't be able to install the drivers? As it is, enabling ADB was one of the first things I did, as it was my intention to root it immediately and transfer data from the 16GB model using Titanium.
well, I now have 5 drivers installed covering the 2 devices:
2 x Android ADB Interface
2 x Android Composite ADB Interface
1 x Tate-PVT-08
anyone have any ideas why this might happen? Each device responds to ADB ok, but they use separate drivers
the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off
RedBlackPellet said:
the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off
Click to expand...
Click to collapse
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
nkk71 said:
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks
RedBlackPellet said:
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks
Click to expand...
Click to collapse
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.
Seanie280672 said:
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.
Click to expand...
Click to collapse
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
im at a loss, sorry I couldn't help any further, but if its doing it with different devices, it has to be a software issue, especially as you say its working in recovery and bootloader, the only thingf I picked out from your picture is it states your adb is out of date, but you say you've tried that too, all I can suggest is you try this one.
http://forum.xda-developers.com/showthread.php?t=2588979
also where did you get the drivers from
RedBlackPellet said:
and sometimes device offline
Click to expand...
Click to collapse
reboot PC and phone, use a USB2 port
RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
why are you using an adb shell to push the file? push the file using adb and then enter the shell to chmod the "ff" file (I suppose you are pushing firewater but your renamed the file to "ff" ?) And btw "adb devices" will not output your device ID from an adb shell.
Code:
adb devices
adb push ff /data/local/tmp
then
Code:
adb shell
su ---> [COLOR="blue"]to get a # prompt[/COLOR]
chmod 775 /data/local/tmp/ff [COLOR="Blue"]--> to give read/write/execute permission[/COLOR]
/data/local/tmp/ff
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks
toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks
joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).
toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.
For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs
?k
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!