Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
I am current and up to date with the sdk and drivers. I have fastboot installed. I know how to use it, please skip the referrals/how-to because that isn't the issue.
Spawn The Dark Ages
JediNinjafication said:
Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
Spawn The Dark Ages
Click to expand...
Click to collapse
As for fastboot, sounds like you need to get the proper driver. It's a different interface than adb. Try the naked driver efrant links to in his 101 FAQ post.
As for the other issue, I'm not sure I follow. Using a file manager on the device, you see files/folder that "aren't there" and via adb shell you don't see them? Please elaborate.
Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed. since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Spawn The Dark Ages
I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages
JediNinjafication said:
Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
Click to expand...
Click to collapse
What do you mean by external? The gnex doesn't have an external SD. Forget browsing the /sdcard with Window explorer at this moment, let's try more robust ways first. What do you see using a file manager on your device? What do you see using adb shell? (type ls -l)
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed.
Click to expand...
Click to collapse
Yes, the adb interface device and mtp device are gone because when you are booted in bootloader the phone uses another interface (fasboot). I'm sure it says best driver installed, but if 'fastboot devices' doesn't list your device I beg to differ that's true. Manually update the driver using the naked driver version 0.7: http://forum.xda-developers.com/showthread.php?t=1379875
since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Click to expand...
Click to collapse
Fastboot won't work if you're booted into Android OS. Again, it's an interface of the bootloader.
Oh..i just remembered..when i did have root, i had a program that would tell me system info and it listed internal memory and sdmemory. This was just before i restored.
Spawn The Dark Ages
My external harddrive for my computer. I know all this you just said hence i posted the thread
Spawn The Dark Ages
JediNinjafication said:
I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages
Click to expand...
Click to collapse
Afaik, stick mount is an app that allows you to mount USB thumb drives with your gnex. If you don't have one of those attached and you never used this program, I doubt it's the cause or your problem.
This is not my first Android. each time i post everyone immediately refers me to a toolkit or how to on the sdk. Let's skip all that, assume I'm current and up to date and know how to use it. Now, read the post and continue from there. Not trying to be *****y, but this check drivers and fastboot banter will continue three pages.
Spawn The Dark Ages
And that's why I'm asking because that's how my phone is mounting.
Spawn The Dark Ages
I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.
Petrovski80 said:
I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.
Click to expand...
Click to collapse
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages
Nor was there any command issued. It was a request to skip the usual fastboot/adb and get down to the issue...saving each one if us typing and time.
The time spent explaining i am current and up to date with everything is horrible. Only reason i did the fastboot is because i have never seen it say Android debug interface while my phone is powered on...only when it's in fastboot. Nor have i ever had it sharing files with my external hard drive...like it were stick mounted.
Spawn The Dark Ages
Spawn The Dark Ages
JediNinjafication said:
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages
Click to expand...
Click to collapse
You obviously think you understand what you are doing, but it us clear to everyone but you that you do not. I'm not trying to be mean here, but you are not listen to everyone who has tried to help you. I have tried in your other thread, petrovski80 tried in this one, and others in your other threads that you keep creating. One: you do not have the fastboot driver installed. Period. Two: to answer your question in your other thread, once you do install the fastboot driver, you can follow any one of the multiple guides on how to get root. Three: do not trust what you see in mtp on windows - it is not refreshed properly often. Four: no matter how many android devices you have had and have rooted and no matter how many drivers you have installed in the past, you still have not done the things you need for the GNex.
Sent from my Galaxy Nexus using Tapatalk 2
http://forum.xda-developers.com/showthread.php?p=30778314#post30778314
JediNinjafication said:
http://forum.xda-developers.com/showthread.php?p=30778314#post30778314
Click to expand...
Click to collapse
Funny, because no one suggested you use the driver that came with the SDK. If you look up to post #5, you would have seen that the driver that was linked to was the one that you should have used, and you would not have had to make any changes to any setup.inf files, and your issue would have been solved a while ago.
Funny because I had multiple different ones put in my dropboxthat didn't work either. Point being the drivers were there.
And I learned something new. Win/win
Related
Sorry, i know you must get this all the time guys, but i'm really struggling with rooting and such.
I'm on 1.72 and have no idea how to downgrade. I know you might say "read the guide" blah blah, but i don't understand it "Moron" i hear you saying. Anyway, Is there a complete noob guide for it anywhere? Like literally one that talks you through every step?
Also, my screen cracked, so i opened it up and replaced the screen myself, didn't have insurance or the £170 to have them fix it. Before the screen cracked it was doing this thing where it looked all psychedelic, Whites have blue coming off them, blacks have reds coming off them, that kind of thing. and its doing it again. This made me think it was a software issue, it happen to anybody else? I was thinking if i put a different rom on it, it'd stop, but i dunno. Anyway, thanks for any help anyone gives.
Does the screen replacement involve the flat ribbon cable between the screen part of the phone and the keyboard? I'm thinking it doesn't, but I'm certainly no expert. A damaged ribbon cable can cause colors to display improperly.
Nah, its attached to the screen so it was a new one.
The screen only comes with a small ribbon cable that connects to the pcb in the front half of the phone.
There is a larger ribbon cable that connects the two halves of the phone together, you can see it if you hold the phone halfway between open and closed. If this cable gets damaged, which happens easier than you may think then it can causes all sorts of things to mess up, including the colours on your display.
Unfortunately this cable is attached to the screen pcb so needs to be replaced as one unit.
So i'd need to replace my main pcb? Damn. Thanks for the help though! Could anyone help me with rooting?!
Sent from my HTC Vision using XDA App
at which point are you getting lost? sussed downgrading yet?
emdaftrave;14529179.Could anyone help me with rooting?! :D
.
Sent from my HTC Vision using XDA App[/QUOTE said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
Just have a search and there are numerous step by step guides, I was a total amateur and managed to do it, I think the hardest part to try learn would be using ABD (command prompt) and how to navigate to directories and push files but there are numerous guides on this forum so just pick your simplest and go for it!
elliott2705 said:
at which point are you getting lost? sussed downgrading yet?
Click to expand...
Click to collapse
Pretty much trying to install the sdk, i think im gonna reinstall it because its being a bit dodgy for me. But thanks for all the help guys!
Sent from my HTC Vision using XDA App
silverwind said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
can you use the SD card already in there as a gold card, or do you need a separate one?
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
emdaftrave said:
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
Click to expand...
Click to collapse
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
pmcqueen said:
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
Click to expand...
Click to collapse
ok, i've done it, thank you very much! now to just downgrade and root!
Ok so i'm using the XDA wiki guide on rooting, and i've got to the part where you move all the files onto the phone. Specifically, the files that aren't moving are:
$ adb push flash_image /data/local/tmp/
$ adb push su /sdcard/,
I'm getting a "Permission denied" error in command prompt. I also don't have an /sdcard directory on my phone, maybe thats why i'm getting an error?
EDIT: Never mind, i had the phone in Disk Drive mode when it wasn't supposed to be. Sorry for the double post.
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.
Have you added the environment variable for the sdk directory? It won't work if you don't.
Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try
I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.
vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.
bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.
If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App
It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
JT-on said:
Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
Click to expand...
Click to collapse
To use ABD you need to be connected in recovery or a booted device.
nlooooo said:
To use ABD you need to be connected in recovery or a booted device.
Click to expand...
Click to collapse
Brilliant. Like you said, ADB recognized my device in both booted OS and recovery. However, I needed to be in recovery to push files to the system directory. Thanks.
You're welcome. You can push in booted device you just need to enable superuser rights in adb shell.
Sent from my HTC Desire using Flashes and Thunders
JT-on said:
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
Click to expand...
Click to collapse
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
rmp5s said:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
Click to expand...
Click to collapse
You can't. Both the n4 and the n7 have their memorys formatted as ext4, partition type that windows can't access normally. MTP was the only sollution google had.
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Bump - anyone? Bueller? Bueller?
B
finnfather said:
Bump - anyone? Bueller? Bueller?
B
Click to expand...
Click to collapse
If you're trying to root then see the method I added to the end of the ROOT thread (can't post link, new account).
In short, you can get directly into the flashed recovery without it going back to normal and getting over written first without needing to use ADB to send it back to recovery mode.
Just take the back off, then once you have flashed the crackling recovery: pull the battery.
Plug it back in with the volume down held and power the device on, holding volume down.
You'll get into the recovery and can install superSU.
Hope that helps.
finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
I had the same problem on my Windows 10 that was upgraded from 8.1.
To fix it, I removed completely Android SDK and reinstalled it. For some reason this was the solution for me.
I tried the same things as you before that (except factory restore as it is a pain) and got the same results - no device listed.
As for Linux and OSX, the Swift got recognized without a problem.
finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
Hi everyone,
@finnfather I think I have solved the issue. Today, I decided to manualy install (cm-12.1-YOG7DAS2FI) the latest cyanogen update as my phone didn't recive it as an OTA. I downloaded the zip package here and installed it through the atock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,
Jev
Hi
Windows 10, android sdk installed and google drivers.
Fastboot shows 8bce440 fastboot when fastboot devices is tried in cmd (admin priv) and "waiting for any devices"
ADB list devices is also empty.
Any help appreciated.
Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?
Pak0St said:
Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?
Click to expand...
Click to collapse
Hi Cheers for replying.
I have now tried it on Win 10 (clean install) win 8.1 (clean install) and windows 7 (clean install)
Reinstalled sdk on 8.1 and 10 twice but no joy. I cant see anything under device manager for it (in fastboot)
Under devices and printers it shows Android
Any help appreciated.
---------- Post added at 06:31 PM ---------- Previous post was at 06:25 PM ----------
adb_usb.ini could this help? I have tried creating a file manually. But no joy
In fastboot mode, it should come up as Marshall London Bootloader Interface under Device Manager. From Devices and Printers you can check what driver is currently installed when it's displaying "Android".
Windows 8/10 is very insistent on using verified drivers. You could try to uninstall the current driver and re-connect the device so that Windows can try to find the verified ones.
For me it automatically installed the fastboot drivers, although it wasn't fast enough and the Swift rebooted before the drivers were finished with installation.
Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb
jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.