After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
diver47591 said:
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
Click to expand...
Click to collapse
If you do a manual factory reset , never gonna lose the root.
diver47591 said:
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
Click to expand...
Click to collapse
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.
If that fails, try a different cable.
alaneddy said:
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.
If that fails, try a different cable.
Click to expand...
Click to collapse
I was way off! I found a suggestion on another site that recommended updating sdk. Determined my sdk was version 1.0.29, updated to 1.0.30, and voila returned "device name device" good to go. Thanks so much for the help.
Related
Hey, I'm trying to root my AT&T GS4 and obviously need usb debugging to do it, but whenever I connect the chord to my computer it says it's still "Connected as a media device" in the notification bar.
Yes I have:
1) Enabled developer mode
2) Downloaded and installed the usb driver from Samsung (however I'm not sure it went correctly, will explain farther down) also have successfully connected phone with Kies and backed it up.
3) Tap the checkbox to enable usb debugging
The same process I took when rooting my Nexus 7. Only this time usb debugging isn't actually turned on or isn't being detected.
The reason I said I think something went wrong with the install of the drivers is because after I ran the .exe I got off of Samsung's support site it did that icon for driver installation, I opened it and after a while it showed this (replace DOT with . because of XDA's anti-spam thing): i.imgurDOTcom/M6pewok.png
As it shows there were multiple drivers that were installed, but one unidentified device that failed.
I'm really wanting to root my phone but need usb debugging, can anyone help?
re: USB Debugging -Root
T4yB4cK said:
Hey, I'm trying to root my AT&T GS4 and obviously need usb debugging to do it, but whenever I connect the chord to my computer it says it's still "Connected as a media device" in the notification bar.
Yes I have:
1) Enabled developer mode
2) Downloaded and installed the usb driver from Samsung (however I'm not sure it went correctly, will explain farther down) also have successfully connected phone with Kies and backed it up.
3) Tap the checkbox to enable usb debugging
The same process I took when rooting my Nexus 7. Only this time usb debugging isn't actually turned on or isn't being detected.
The reason I said I think something went wrong with the install of the drivers is because after I ran the .exe I got off of Samsung's support site it did that icon for driver installation, I opened it and after a while it showed this (replace DOT with . because of XDA's anti-spam thing): i.imgurDOTcom/M6pewok.png
As it shows there were multiple drivers that were installed, but one unidentified device that failed.
I'm really wanting to root my phone but need usb debugging, can anyone help?
Click to expand...
Click to collapse
If it says "Connected as a media device" that is NORMAL and the way it should be.
If you have check marked "USB Debugging" in your phone settings and the checkbox remains "checked"
then there is nothing wrong with your phone. If the USB debugging does not stay "check marked" after
you "check mark" it then there is something wrong with your phone.
Most likely there is NOTHING wrong with the phone itself and the rooting issue you are having has
nothing to do with usb debugging.
If that's the case then your problem most likely is the usb drivers in your computer or the usb cable
itself and possibly you need to plug the cable into a different usb port on your computer.
First thing I would do if this is the case is to un-install all samsung drivers and applications
from your computer including kies if it's installed. Then reboot the computer and only install
the Samsung USB Drivers and nothing else.
After the samsung usb drivers are installed reboot your computer.
Then you should be able to root the phone with no problem.
The very best and easiest way to root your phone is to download either the cwm or twrp
recovery Odin flash TAR file and download ODIN if you don't already have it.
After doing that download one of the cwm/twrp flashable custom rom zips file and copy it to
your internal sdcard.
Then use Odin to flash the TAR recovery file in the PDA slot of Odin.
After that's done reboot into recovery and select "install" or "install zip" and navigate to your
internal sdcard and find the cwm/twrp flashable custom rom which you copied to the sdcard
and flash it.
After it's flashed you will be rooted, all the cwm/twrp flashable custom roms are pre-rooted
so you will not need to worry about having to root.
Good luck!
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus. Not exactly obvious why, but I you select the second option "Camera (PTP)" the device is available for debugging. This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise
Click to expand...
Click to collapse
Basically, This is my problem. I need to change my Nexus usb configuration from MTP to PTP so that it'll show up on adb devices, but unfortunately I'm softbricked; I cannot get my Nexus to do anything because I can't get it pass the googlescreen.
So my question is; is there anyway to change it from MTP to PTP without having the option to enable it via the tablet?
Bump, can I configure usb through the nexus toolkit? Please help.
What do you mean?
EDIT: Saw the OP now. If you can get into bootloader mode, try flashing a factory image. If that's not the answer you were looking for, please specify your requirements and why you need them.
I don't know what you mean, and I don't understand why you recommended flashing a factory image but I'll try to elaborate.
At the moment, my Tablet doesn't allow for USB Debugging.
It is Soft Bricked, so I can't get into system to enable USB Debugging, as I have accidentally deleted my OS.
I cannot disable MTP either because I cannot access my tablet setting.
WHAT I NEED:
An alternative to accessing these such settings.
To activate usb debug you have to go in "developer options".
To repair "softbrick" you have to flash factory image in "adb sideload" or adb in linux or windows pc.
Yeah since you dleted the OS itself, your only optioons are to either flash a ROM from recovery or flash the factory image.
ivn888 said:
To activate usb debug you have to go in "developer options".
To repair "softbrick" you have to flash factory image in "adb sideload" or adb in linux or windows pc.
Click to expand...
Click to collapse
Not necessarily correct, since it depends on having a working custom recovery that can start an ADB instance. Fastboot flashing is much more reliable.
You DO NOT need USB debugging in recovery or fastboot modes.
USB debugging ONLY applies to a booted OS.
Sent from my Galaxy Nexus
Stop trying to use ADB, use FASTBOOT. There is a sticky at the top of the forum How to flash a factory image using fastboot/return to stock. It has all the information you need to return to a working device. ADB is only useful if you have a working OS, which currently you do not.
Hi,
I kind of "bricked" my nexus. Kind of, because recovery is working, and I can even start the device in android. Problem is error windows pops up and I can't control a thing.
No big deal you say, but I deleted by accident the .zip of the rom I had on the device. AND USB DEBUGGING WAS OFF...
I can't transfer any file to the device, I can't start usb debugging, and every tutorial on the internet says to put the device in usb debugging -> it's bricked, that's the whole point, so WTF!
sorry, I didn't respect the unwritten rule stating you should'nt ask for help on a forum while angry furious
Hope any of you can help me...
I should add I'm really not a poweruser. I've been flashing roms for a long time following carefully the rules, but really I have no idea what I'm doing <insert meme>, so adb and stuff like that I've never used (directly).
Thanks!
Use fastboot, see the sticky that says flashing a factory image using fastboot/return to stock.
Sent from my Nexus 7(2012) that has zero issues.
Thanks for you answer.
Still, I have to turn on USB debugging
Enable usb debugging on your device (found under Settings > Developer Options)
Click to expand...
Click to collapse
I can't do that because I can't use my nexus in android.
Bipo said:
Still, I have to turn on USB debugging
I can't do that because I can't use my nexus in android.
Click to expand...
Click to collapse
USB debugging is system feature. If you cannot load system you don't need to bother about it. You can only use fastboot as writen before.
Bipo said:
Thanks for you answer.
Still, I have to turn on USB debugging
I can't do that because I can't use my nexus in android.
Click to expand...
Click to collapse
Incorrect.
Fastboot works even when there is nothing on the device save the bootloader. Follow the instructions in the flash factory thread linked above and don't apply and personal prejudices-- it does work, and is the "right" way to do things. If you use a Windows computer, then you may also need the naked fastboot drivers (which can also be found by searching).
Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
ant78 said:
Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
Click to expand...
Click to collapse
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
chichu_9 said:
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
Click to expand...
Click to collapse
I'm using windows 10 and I already have oem unlock ticked .
Thanks
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
Most likely this problem. If you don't see the option to touch OK, restart the phone and/or replug the USB cable.
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
My ADB device in Device manager has a warning sign next to it, i click and ask windows to fix this but it says "Windows was unable to install your ADB device"
I have this on my new laptop and new desktop PC, all have usb 3 connections
Just followed this guide and fingers crossed it seems ok, http://visualgdb.com/KB/usbdebug-manual/
Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!