Related
I am preparing to root my beloved new Nexus S, but am just wanting to make sure everything is set before I venture off.
I'm a previous nexus one owner, and used fastboot and adb in the past following guides from on here.
Following another guide from here, i've managed to get "fastboot devices" to show my Nexus S connected, however, when I try adb devices, nothing is listed.
I run windows 7, in order to get the fastboot devices to work, I downloaded some drivers and installed them, and then an "unknown Android 1.0 device (as shown in Device manager) was recognised as an ADB device - so I assume i'm all good on the driver front.
Is there any specific mode I need the phone connected in to get adb to recognise it? I cant remember from when I last did it on my N1?
dannstarr said:
I am preparing to root my beloved new Nexus S, but am just wanting to make sure everything is set before I venture off.
I'm a previous nexus one owner, and used fastboot and adb in the past following guides from on here.
Following another guide from here, i've managed to get "fastboot devices" to show my Nexus S connected, however, when I try adb devices, nothing is listed.
I run windows 7, in order to get the fastboot devices to work, I downloaded some drivers and installed them, and then an "unknown Android 1.0 device (as shown in Device manager) was recognised as an ADB device - so I assume i'm all good on the driver front.
Is there any specific mode I need the phone connected in to get adb to recognise it? I cant remember from when I last did it on my N1?
Click to expand...
Click to collapse
to be safe you should uninstall the unknown device and reinstall ur NS
dannstarr said:
I am preparing to root my beloved new Nexus S, but am just wanting to make sure everything is set before I venture off.
I'm a previous nexus one owner, and used fastboot and adb in the past following guides from on here.
Following another guide from here, i've managed to get "fastboot devices" to show my Nexus S connected, however, when I try adb devices, nothing is listed.
I run windows 7, in order to get the fastboot devices to work, I downloaded some drivers and installed them, and then an "unknown Android 1.0 device (as shown in Device manager) was recognised as an ADB device - so I assume i'm all good on the driver front.
Is there any specific mode I need the phone connected in to get adb to recognise it? I cant remember from when I last did it on my N1?
Click to expand...
Click to collapse
Do you have USB Debugging on under Menu > Settings > Application > Development?
slowz3r said:
to be safe you should uninstall the unknown device and reinstall ur NS
Click to expand...
Click to collapse
?? huh?
unremarked - thanks very much, this is the step I had forgotten - usb debugging. Now turned on, computer auto installed some drivers, adb devices now works.
Thanks a whole bunch
dannstarr said:
?? huh?
unremarked - thanks very much, this is the step I had forgotten - usb debugging. Now turned on, computer auto installed some drivers, adb devices now works.
Thanks a whole bunch
Click to expand...
Click to collapse
glad to see you got it working but it shouldnt say unknown android device
slowz3r said:
glad to see you got it working but it shouldnt say unknown android device
Click to expand...
Click to collapse
Sorry - my bad explanation. Before I got "fastboot devices" working, it was shown as an unknown android device. I downloaded and installed drivers and that then turned in to a recognised android adb device
I got that bit done, thats why I was still confused over why in cmd "adb devices" did not show anything listed - but yeah, all sorted now, thanks
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Stryder5 said:
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
Yes, that's where I got the drivers (and that's how I got fastboot working).
I've taken the drastic step now of uninstalling the entire SDK thing and am currently re-installing it. We'll see how that goes.
EDIT: yeah, "adb devices" still gives nothing at all.
You need to turn it on first but Developer Options are hidden in Settings. Go into About phone and tap the build version. After 7 times you will have access and you can turn on USB Debugging
chinly43 said:
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
Click to expand...
Click to collapse
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
0.0 said:
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
Click to expand...
Click to collapse
While this was, admittedly, once my problem back in the early days of android, it's not the problem this time. USB debugging is on.
EDIT: I've also reconfirmed that fastboot is still working after the whole re-installation thing.
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
chinly43 said:
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
Click to expand...
Click to collapse
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
0.0 said:
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
Click to expand...
Click to collapse
That's all I can suggest as well, although I can't see what the issue could be
Yer try installing the SDK and downloading the "Google USB Drivers" from there to see if it helps.
Sent from my Nexus 4 using Tapatalk 2
Here try this. It's from the sdk. I just zipped it. https://www.box.com/shared/7sutkummukh4pup0rwoi
Sent from my Nexus 7 using Tapatalk 2
You can just get the windows executable from Google, r21
http://dl.google.com/android/installer_r21-windows.exe
Thanks, everyone who's been reading/trying to help. Unfortunately, it's still not working.
People suggesting the .exe installer - that's how I've installed it each time. Twice now I've uninstalled/reinstalled the SDK. When installing, I choose the SDK tools, SDK platform tools, the 4.2 API (which is probably unnecessary, right?), and the Google USB driver. Each time, ADB has worked *in general*, but will not recognize this device (via the "adb devices" command).
Here's how things are going right now. When I first plug the phone in (with debugging on), if it's not currently installed as a device then it automatically self-installs and shows up as an "mtp" device. I try ADB, doesn't work. I then go in and manually install the drivers found in various places around this board. When I do this, it no longer appears as MTP. This is weird, though, and I didn't notice this last night - when I look at the list of devices in Device Manager in Windows, the category it falls into is "ASUS Android Devices", under which it's listed as "Android Composite ADB Interface", and it still doesn't work.
Something seems wrong about it being listed as ASUS, though. I wonder if all these current difficulties are a result of the problems I had getting my Transformer Prime to work with ADB? If anyone sees anything above that looks like I'm doing something wrong, let me know; I think the next thing I'm going to try is doing this whole process on a fresh computer here at work that's never been exposed to android at all, see how that goes. I'll check back in after I do that.
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
EddyOS said:
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
I have, and it still doesn't work on my laptop. However...
It's working! On a shared computed at work that had never had *anything* android-related installed before. Went through the same procedure I did on my own computer, so the problem is with my laptop, I guess. Which I'm more okay with than it being a problem with the phone. I guess I need to more thoroughly remove everything from the laptop, maybe?
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
chinly43 said:
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
Click to expand...
Click to collapse
I have to do that to my Nexus 7 before ADB will recognize it, so you're not alone there.
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
I had the same problem, here's what you need to do. When you plug it in, change the settings from MTP to Camera for USB settings. I don't know why, but you need to do it.
dcarpenter85 said:
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
Click to expand...
Click to collapse
I've got four other android devices that all worked (simultaneously, at that): T-Mobile/HTC G1, Nook Color, T-Mobile/HTC G2, and an Asus Transformer Prime.
So I am installing the Nexus 7 in my car as the head unit, but am now stuck with this issue.
I unlocked, and rooted the device, and used the fastboot oem off-mode-charge 0 command and it worked.
Anytime the Nexus 7 receives power it turns on.
However the device battery died completely and now when I plug it in to charge, the screen stays black, buttons do nothing, and eventually it boots up, but immediatley powers off as the battery is at 0 % and has the red ! mark.
I can't even use the fastboot command to reverse it since the device can't stay on.
What the heck can I do?
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Username invalid said:
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Click to expand...
Click to collapse
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
@Username invalid
Yes, but will the command be executed before the device dies again?
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
When you're in bootloader, you don't need debugging enabled since the fastboot protocol comes into play, not ADB (which requires debugging to be enabled). Root is also unnecessary. At least that's what I have learnt in the past 5 months I have had this.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
sgt. meow said:
@Username invalid
Yes, but will the command be executed before the device dies again?
Click to expand...
Click to collapse
There is not enough time for me to set debugging on before the device dies. It stays on for maybe 5 seconds at the home screen then powers off.
Is there a way I could charge the battery a little bit bypassing the Nexus?
Can I splice in the pos and neg of the usb charger to the pos and neg of the battery?
I'd highly discourage the battery direct charging bit.
Username invalid said:
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
Click to expand...
Click to collapse
I'm not sure at all.
I used the R3 Nexus 7 Superboot to push the original command. I had downloaded fastboot from somewhere else, and put it in the Superboot folder to get it to push the command.
By the way sorry for taking so long to reply in between. Since I am a new user, I have to wait the 5 minutes in between posts.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Username invalid said:
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Click to expand...
Click to collapse
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Jeremi1023 said:
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Click to expand...
Click to collapse
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I will do that and let you know what I see.
Just gotta wait for the thing to turn on. It's very random right now.
Okay, I was able to get into bootloader, and I I did "fastboot devices" and nothing came up.
Also checked device manager and no Android or anything like it in there.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Jeremi1023 said:
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Click to expand...
Click to collapse
http://d-h.st/kDu
Username invalid said:
http://d-h.st/kDu
Click to expand...
Click to collapse
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Jeremi1023 said:
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Click to expand...
Click to collapse
Uninstall your current one first.
Username invalid said:
Uninstall your current one first.
Click to expand...
Click to collapse
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Jeremi1023 said:
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Click to expand...
Click to collapse
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Username invalid said:
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Click to expand...
Click to collapse
Yeah I have a desktop I could try it on.
I've never plugged the Nexus in to the desktop, so it should be a complete clean install of drivers.
If Windows recognizes the nexus on the desktop, what should I do?
Do I need to uninstall anything it may install on its own?
I figure I will end up installing the drivers you previously provided.
Hi,
I tried a lot of other rooting applications and have had no luck with any of them. Then I found Wug's Nexus Root Toolkit. It works for my Nexus 4 (Jelly Bean 4.3) - until I came to the "Full Driver Configuration Guide" - where it gives a message: "ADB device was not found".
I have tried it over several times to no avail. Can anyone offer any clues as to what may be causing this?
btw, I am running the Wug's Nexus Root Toolkit v1.7.2 on Windows 8.
Thank you,
David
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
I am having the same problem. Where/how does the phone ask you to confirm USB debugging? It asks me when I turn it on, but not again later.
I have tried 3 or 4 different drivers, but, although the device is recognised by Windows 8, it is not recognised by Root Toolkit.
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
studacris said:
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
Click to expand...
Click to collapse
I'm not quite sure how this was supposed to help. My problem is that the ADB drivers do not seem to work on my computer. I have just tried installing the Android SDK (which comes with its own ADB drivers), having first uninstalled all the existing drivers. It did not help.
Not entirely sure where to go from here.
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
studacris said:
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
I had installed PDANet from within Root Toolkit, and it didn't work. Just now, I uninstalled everything again, and installed PDANet from their web site. Still get no ADB device in Root Toolkit. [NB I didn't have PDANet on the phone, but it seems to be there now]
I tried running adb from the android SDK, and it says "error: device not found".
However, I noted there was an adb prompt on the phone when I first plugged it in, this time (which I told to always accept).
[Later]
Wierd - it is now a bit further on. This is what I did:
Started PDANet on the phone, and enabled USB tethering.
Started PDANet on the computer, and it connected to the phone. At this point the USB debugging permission thing came up again, and I accepted it (also ticking the box to always accept).
Unticked USB tethering on the phone again.
Stopped PDANet on the computer (right click on icon, exit).
Tried the Root Toolkit again (pressed Root button), it connected to the device, and put it into fastboot mode.
The boot loader appeared on the phone, and the computer said "Checking Fastboot Status".
It seemed to stay like that for ever.
Killed the root toolkit. and tried again.
Left the computer for a while, and when I came back, it had completed.
So, it seems to be working now.
And when you try using fastboot directly instead of the toolkit....... what happens?
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
studacris said:
And when you try using fastboot directly instead of the toolkit....... what happens?
Click to expand...
Click to collapse
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Best idea i didnt notice too
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
Thanx !!!!!!!
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Thank you so much! This solved it for me :good:
nikkilocke said:
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Click to expand...
Click to collapse
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Click to expand...
Click to collapse
I found the same solution, changing over from MTP to CAMERA suddenly had the toolkit recognise the phone and could boot it to unlock then root it... Previously, I had installed PDA drivers...
I am astonished how PATHETIC nexus phones/tablets are at simply connecting to a PC. I am baffled at the attempt by google to make their devices as UN-plug & play friendly as possible... bizarre! I have a N10, N7 and have had two N5's and all have the same PITA random disability....
grrr...
Mark.
So the Nexus toolkit is able to see the Nexus 7 as a media device but not Windows ?
marcelin99 said:
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
Click to expand...
Click to collapse
So the Nexus 7 toolkit is able to see the Nexus 7 as media device with this method, but not Windows ? That's strange because Windows is supposed to see your files within the Nexus via Mtp mode. Is it that google removed the ability for Windows to be able to see Nexus 7 files in Android kit kat 4.4.2. What should I do then if I simply want to view files inside Nexus as a non root user ? B.T.W I'm currently on stock kitkat 4.4.2 build KOT49H. Therefore, I'd gladly appreciate it if anyone out there would answer this question and thanks in advance. Feel free to PM me on this so we can "talk" about this. : )
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Success.
Well, mtp connection works perfectly fine in my Windows 7 machine. But on my xp machine I could never get it to work no matter what driver combination I used.
I can see the reason they changed to mtp but I found mass storage to be much more user friendly.
Sent from my Nexus 4 using XDA Free mobile app
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Stuck on fastboot screen
GranPaSmurf said:
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Click to expand...
Click to collapse
Hi
Happy New Year to all! unfortunately I am left with the unusable nexus 7 that happened last night.
I was going crazy with the lags with lollipop and was waiting for the 5.0.5 update OTA but the delay was making me go crazy so I decided to take the risk of manually flashing the image using ADB and SDK.
Like many others pointed, I knew how to enable my computer to see my device by switching from MTP to PTP mode from my earlier rooting experience with Samsung, HTC and others. So that was not an issue for me.
I was following a tutorial from androidcentral and half way through I went to check a tutorial on youtube which I think caused the disaster. After I executed the adb devices no devices were detected and like I said I went and changed the MTP mode to off and bingo now my device was detected.
I executed device unlock and currently my device is in unlocked bootloaded state which is displayed in the fastboot screen where I am stuck now. Following the youtube instead of flashing each separately bootloader first and then the factory image I jumped to 'flash-all.bat' command...I saw something say on my command prompt on pc that completed in so many seconds or minutes which led me to get anxious and since no rebooting happened on the device I went and manually tried to press the power button.
From that time I am stuck on the fastboot screen. I can cycle through 'power off', restart booloader, recovery mode and start. But when I select 'restart bootloader' it comes to 'start' in the same mode and when I select that I can see a tiny 'Booting failed' in white letters in tiny fonts on the top left side of the 'Start'. I cannot go past this state.
Since I know the last time I had enabled 'usb debugging' and MTP off before everything went wrong I am presuming those states are still intact. I can see status on 'reboot bootloader' screen that my bootloader is unlocked.
Now, when I try to go through the process again my device is seen in device manager but when I send 'adb devices' command it cannot detect any devices. If my device is usable I can atleast go into settings to see if my MTP state and usb debugging status. Now I don't have that option. I even tried the Nexus Root Toolkit - everything is fine but until it tests the driver to finally say 'ADB device not found'.
After browsing so many posts I spotted there were some posts that said there is some discrepancy between the device id as listed by the driver to what actually is usb.inf, which all is too technical and overboard for me. And finally left me thinking that it is some issue of Windows PC as someone pointed that the ADB device was detected on a MAC. So I am now thinking to give it a shot in a mac machine as a final attempt to recover my device.
Anyone please suggest a solution, apologies if this is covered by someone elsewhere in the forum if so please point me there. I will make sure that from next time I will never do a manual flash of factory image.
please help!
It sounds like you are on top of it, but haven't hit the right combination yet. Thanks for the quote and I am sorry I am unable to offer any help. As mentioned in my post, I have switched to the Galaxy Mega and was pleasantly surprised by the OTA upgrade to 4.4. Now I am trying to figure out how to root it.
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.
chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.