Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
bullpen7979 said:
Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
Click to expand...
Click to collapse
you can push adb when the phone is connected as a camera. To connect it via ptp, you just scroll down your notifications bar and click on the usb notification, you can switch to ptp there. But like i said, adb works when connected as a camera device, so you are doing something incorrectly with adb. Possibly the commands you are running. The OS for your computer might be causing the problem (but that would mean oyu have the wrong stuff downloaded to adb with the computer set up you are using). You don't have the correct drivers. You are using a faulty data cable. you are using a usb 3.0 port that isn't compatible. it is an endless list. Also, you can copy stuff to your device in camera mode as well.
also would like to note that whether you phone is rooted or not has nothing to do with your ability to use adb or push files to your phone.
finally, this is a question which should go under q&a not the general discussion subforum.
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
so whats the problem. you have adb working. What do you mean you can't copy things to the phone. What error do you get when you try to push a file to the sdcard on the phone? You see your phone in the list of devices so you can put files on it that way too. Really confused at your dilemma.
you trying to root? you trying to push files to the phone? IDK, but you clearly should be able to push them if you have adb running. Perhaps you aren't running the right commands to push files to your phone.
Don't you have to have USB debugging on?
Sent from my XT1060 using Tapatalk
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Click to expand...
Click to collapse
Unless you have another android device connected to your computer, your X has USB Debugging mode turned on, and Windows & ADB properly sees your phone.
As jayboyyyy posted, in this state you can use ADB to push files from the PC to phone, or pull files from the phone onto the PC, assuming you are using the right commands. But if all you are looking to do is copy files back and forth, this is overkill as you can do it with windows. ADB is usually only need for hacking and flashing your phone.
As I said in the other thread... Please include what you were doing and what the results are. You haven't given us a complete enough of a picture to understand 1. what you are trying to do. 2. Any/all steps you have taken. 3. EXACT error message you are receiving.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader. But your second paragraph starts saying you can't get the thing rooted to save you life.. So which is it? Are you rooted or trying to root? If you are trying to root, what process are you trying to follow? What step in that process are you stuck at? What did you type and what did you get back?
I know you are probably frustrated, but its just as frustrating on this side when you don't give a complete picture that allows us to help you. Look, rooting and hacking isn't easy. It can even result in turning your phone into a paper weight. So these details are important so we don't screw things up and add to the headaches and frustrations.
bullpen7979 said:
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
I'm not sure what you are doing, or trying to do, as you said in the first post that you unlocked the boot loader and rooted.
The Moto X wont show as a drive letter in "My Computer." Even if USB Debugging is on, it should show up as a "Media" device, or Player type device with an icon in a separate section from your hard drives, DVD drive, mapped network drives, or even USB memory sticks/flash drives. It does this because the X supports/uses MTP/PTP, and NOT USB MASS STORAGE MODE.
MTP/PTP wont show a drive letter in My Computer. This is by design. You don't have to "stop" or "eject" the phone from windows when you are done. This mode also allows the phone to access the "storage" or emulated "SD" partition at the same time a connected Computer can.
USB Mass Storage mode will give you a drive letter in My Computer, IF the phone supported it. However the X doesn't, at least not out of the box, and I'm unaware of any app or hack to enable this. In USB Mass Storage mode, the PHONE looses access its storage partition or emulated internal SD card while the PC is connected. You'd need to "stop" or "eject" the device when you want to disconnect form the PC in order to prevent data corruption of the "emulated SD"
So again, its important for us to know exactly what you are trying to do.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader.
Im sorry I was unclear. Bootloader is unlocked, but I am not rooted. What I said was that I had another thread about getting it rooted.
I'm sorry for the mis-speak. And I'm sorry I'm being such a pain, but others in the thread I'm referencing are clearly having the same issue I am. I just need to know what to do to obtain root access if my bootloader is already unlocked. To be clear, I do NOT have root access.
This is my procedure.
Start with this link:
http://forum.xda-developers.com/showthread.php?t=2509676
Download Cydia Impactor. Check.
Download RockMyMoto.zip attachement. Unzip two files to directory x. Check.
Download PuTTYtel file "puttytel.exe" Check.
Step one. I have my ip address. At bottom of wireless config on phone, it is 10.59.1.6. So far so good.
I run adb shell getprop dhcp.wlan0.ipaddress just to be sure. same ip addy. Good.
I start command window. push the two files to the phone. all is well.
Step two i open the puttytel window and proceed to run the exploit
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
and I can't run the damn thing because i get PuTTytel Fatal Error
Network Error: connection timed out.
exactly like this dude: http://dl.xda-developers.com/attach...f04a/5290120c/2/3/8/1/6/0/9/1384014224630.jpg
The end. I read the rest of the thread, and post #22 is the first of about five other posts that mentions the same time out problem, a solution for which is NEVER ADDRESSED, except indirectly as a possibility that the the two devices are not on the same network. My wireless card is on dhcp and the phone is the IP address above.
that's where it stops. I can't run the exploit because i can't type the command fast enough. Several people mention this problem, but I read all SIX pages of the thread and this defect is experienced my many and adressed by nobody.
This is driving me stark raving Bat S#!+ crazy.
And yes I have USB debugging on.
If your boot loader is already unlocked, there is another process.
https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Is the process and while I think that twrp version should work, you might need the older version. Had to take my mom to the hospital so not in a good position to find older if newer doesn't work.
EDIT: this thread -> http://forum.xda-developers.com/showthread.php?t=2536200 has some discussion too
Related
This about as short as I could make it:
I haven't tried to use ADB with my G1 for about a month, so I'm not exactly sure when the problem started, but it's become a royal headache now. For whatever reason when I launched ADB shell today, I got an error saying 'device not found'. The first thing I did was check device manager where I noticed the phone showed as a 'USB composite device' with a yellow exclamation mark over it. I thought to myself "drivers." So I tried pointing it to the driver in the Android SDK folder. That just popped an error saying that Windows couldn't find a better driver match than the one I was already using.
From there I got the googling and came across this insanely long Google Groups thread. Following the advice listed, I started pulling some USB .sys files. I tried using an older copy of the USB driver from a previous SDK. I tried using Haruyko's modified USB driver. None would install.
Same error.
Reading down some more I saw that some people had success with with usinfg HTC Sync. It was worth a shot, right? Well it certainly made things different, but doesn't resolve the issue. Now in device manager I have an 'HTC Remote NDIS' listing under Network Connections. The old 'USB Composite Device' item is now gone. But still, I can't use ADB. "Device not found."
It's driving me nuts.
At this point I figured that it'd be best to try this on a different PC. Maybe my primary one is wonking out. These things happen. Well, that hope was quickly crushed when I discovered that NOT EVEN on a VANILLA XP SP3 setup, will Windows detect the G1. I downloaded a fresh copy of the SDK, plugged it in, pointed it to the USB driver....and nothing. Same error as PC number one:
"Windows can't find a better version of the driver than you're currently using."
Tried switching the USB cable. Same thing.
Back to PC number one, I removed all HTC software from 'Add/Remove Programs, then ran USBDeview. There, I removed the HTC NDIS device, unplugged the G1, and plugged it back in.
The HTC NDIS Remote device returned. **** my life.
SO.....before I throw this phone into traffic, does anyone have any clue as to what's going on here? All I want to be able to do is regain ADB access to my phone. I don't care about USB tethering (and toggling that option does nothing btw) or none of that. Just looking to regain ADB access. The only thing that's changed since the last time I used ADB is the version of Cyanogen's mod. I'm currently using v4.2.3.1. Maybe this broke shell access?
Thoughts?
**EDIT***
-Toggling USB debugging does nothing either.
-Ditto that for Fastboot
device not found has to do with the phone....make sure your cable is not messed up.
B-man007 said:
device not found has to do with the phone....make sure your cable is not messed up.
Click to expand...
Click to collapse
Tried switching the USB cable. Same thing.
Click to expand...
Click to collapse
Tried that already.
the.snks said:
Tried that already.
Click to expand...
Click to collapse
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
B-man007 said:
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
Click to expand...
Click to collapse
As far as I know the USB port is ok. It charges fine. And to update everyone on where I am, I tried the following today:
-Removed all HTC software (Sync and Drivers).
-Used USBDeview to remove all instances of HTC, and Android devices.
-Tried downgrading my test machine (PC #2) to Service Pack 2.
-Tried a third USB cable.
And I'm still getting the same problem. So there's no doubt in my mind that it has to be the phone. Like I said, the only thing I've done lately is update the version of Cyanogen's ROM.
I know it definitely worked before I updated to v4.2.3.1. Also I noticed that I am no longer able to mount the sdcard as storage in Windows. I do not get a prompt on the G1 asking if I wish to mount it. However, the USB debugging notice still pops up (weird).
....and here I'm stuck once again.
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
rp1783 said:
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
Click to expand...
Click to collapse
Yes. Multiple times in fact. It can't be the computer if the same issue is happening across two different PC's, with three different USB cables.
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stuck in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
goldenarmZ said:
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stick in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
Click to expand...
Click to collapse
PROGRESS! I booted into recovery mode and plugged the G1 into the computer. I got the 'new hardware' prompt and was asked to install the driver. I did so using the one from the SDK. Now I have ADB access, and Windows tried to mount the sdcard but that failed. I'm guessing because there's no way for me to 'ok' that in the recovery console.
So what does this tell us? I'm not sure if I understand what's wrong here.
(Sidenote: Man I'm so tempted to try to install the new Google Maps now....)
the.snks said:
So what does this tell us? I'm not sure if I understand what's wrong here.
Click to expand...
Click to collapse
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd for windows when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
goldenarmZ said:
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd as storage when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
Ah....that blows but you do what you gotta. I'll try wiping and report back in case this thread helps anyone else.
Thanks man.
Alright, here's what I did to get working again:
Doing a wipe did NOT resolve the issue. However, updating to v4.2.4 did (remember I was using v4.2.3.1 originally). For clarity, I wiped both before and after the update. And I had to use a sdcard reader to get v4.2.4 onto the phone. I can now ADB and mount the sdcard in Windows without issue. I'm not sure if this was a one off, or possibly a bug in v4.2.3.
Somebody may want to bounce that Cyanogen.
B-man007 and goldenarmZ, the help was much appreciated.
This probably is related to USB tethering Cyan put in his rom.
Also for future reference, if you want to mount your SD card in recovery and you have Cyan 1.3 or greater or RA recovery, you can just type
ums_enable
to mount and
ums_disable
to dismount
saves you from typing that hideously long line lol
Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit
@DigitalDementia--
How is what you said relevant in this thread?
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?
rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.
still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.
rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.
After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.
I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.
Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.
Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.
Hey, everyone, I tried posting about this in the CM7 general discussion thread, but no one seemed apt to respond.
I think this was a problem that popped up in the 60s or 70s in terms of nightlies, but I'm having it again now since around the 155 mark.
I'm on 160 and when I plug my NC into the USB cable, I no longer get any options to connect for file transfers in the notification area. If anyone could help me out with this, I'd really appreciate it. It's just so perplexing and no one seems be having this issue except me. If it's user-side error, that's fine as well, I'd just like to know how to fix it.
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
votinh said:
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
Click to expand...
Click to collapse
1. No, nothing comes up.
2. The notification area remains blank.
3. I'm running it off eMMC.
Thanks for taking the time, by the way!
If so, unplug the usb cable then replug in a few times and see what happens.
If still nothing, try to use other usb cable.
Oh, btw, have you had Nookcolotweaks app installed?
I do have Nook Tweaks installed, yes. I'm using the cable that came with the Nook, but I'm not sure I have any other cables around.
Do make sure you check OFF the USB Host feature (reboot and reconnect)
I gave that a try, too, but still nothing. So confusing!
Don't be so hard on yourself.
Let try it on different computer if you have.
Also try difference usb cable.
Last, if nothing works, update latest nightly build
When you disconnect and reconnect the nook in testing/trying to get it recognized... unplug usb cable from computer... its made a difference at times.
I know this sounds basic but in applications-settings ensure you have usb debugging checked. Sometimes when flashing different nightlies, settings change.
Sent from my NookColor using Tapatalk
Thanks again for all the help, everyone! I made sure USB debugging was checked and tried unplugging/replugging the cable, but there's still no notification coming up.
A new development:
I tried connecting it to my Windows PC instead of my Linux and it brought up this message that said it didn't recognize the device. I also tried to get ADB to see it and it can't. Does this information help or am I in trouble here?
Next time, do clearly indicate that you are using Linux or Windows. I'm sure many members here are Linux but still far less support than Windows world.
When I provided those suggestions in previous posts, I meant in Windows.
Anyway, back to your issue.
1. "it didn't recognize the device" because of missing adb usb driver. You need to get it installed first in order to use ADB, however it has nothing to do with your usb mass storage function. For now, you don't need to worry about it just yet.
2. Back to my question before, have you seen any "removable" on the PC (Windows)
Along with USB Host uncheck, if still having problem, I would suggest you either downgrade to the earlier versions or wait until tomorrow and update with another nightly build.
Good luck
I have the ADB drivers installed in Windows, as far as I know. I've used it before.
I typed "adb devices" into the prompt and it doesn't see the NC at all. Since one of the nightlies seems to be what prompted this sudden change in connectivity, I guess I'll just hope that one of the new ones can fix it. Thanks again.
Also, Windows doesn't show anything "removable" except for my external HD.
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
arda99 said:
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
Click to expand...
Click to collapse
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
junkrobot said:
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
Click to expand...
Click to collapse
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
If you've installed ADB drivers, you might want to remove it as this might mess up usb storage.
arda99 said:
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
Click to expand...
Click to collapse
Alrighty. I have those two. I've connected my NC to ADB both wirelessly and and with the cable in the past, so this should all be straightforward anyhow. It just plain refuses to cooperate.
Go to the Marketplace and download "Nook Color UMS" app. Follow instructions and it will mount properly. I had the same issue used it and it mounts proper through the app.
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
First off, I barely know anything with regards to phones as I still learning. However, last night had a similar issue and ended up having to use cmd prompt to navigate to adb and then used it to see the device.
MrTechie890 said:
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
Click to expand...
Click to collapse
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
BD619 said:
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
Click to expand...
Click to collapse
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
MrTechie890 said:
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
Click to expand...
Click to collapse
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
tdhite said:
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
Click to expand...
Click to collapse
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
MrTechie890 said:
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
Click to expand...
Click to collapse
Then try this:
adb backup
That should create a backup file called: backup.ab
tdhite said:
Then try this:
adb backup
That should create a backup file called: backup.ab
Click to expand...
Click to collapse
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
MrTechie890 said:
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
Click to expand...
Click to collapse
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
tdhite said:
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
Click to expand...
Click to collapse
For me, doing it on Linux wouldn't be a huge issue but since I have a mac as my primary machine I'm trying to make due with it.
I think I just firgured it out actually. I just had to install the android sdk, I was using the abd files provided from a tutorial. anyhow, thanks for trying to help tdhite.
QUESTION: Can someone please explain in simple form how to fix the ADB unauthorized issue that has been present since the update to M? The option for removing any current rsa keys is gone from the developer settings. And when you plug your phone in to a new computer it used to pop up a notification that would let you accept the rsa key. None of this is working any more. I cant believe that it is not a bigger issue and I have spent a few hours over a few days looking for a solution so if I have missed it, I am sorry. I have read a few things that say that google has just removed the ability to use adb and one post even explaining that, what looked to me to be a prop file variable, needed to be changed from 0 to 1, or vise versa, but didnt explain where the variable was. I dont see anything that I am confident with in the build.prop. Thanks. Please explain so that anyone will be able to overcome this issue, or point to a link.
Are you talking about the option to "Revoke USB debugging authorisations" under Developer options? It's there, at least on my N6 running stock 6.0.1 MMB29V... And I just tried to ADB to my device and the popup for the authorisation came up on the phone, just as it should.
I think you have some other problem going on.
Are you running the latest adb/fastboot tools on your PC?
Article showing removal of ADB
stevemw said:
Are you running the latest adb/fastboot tools on your PC?
Click to expand...
Click to collapse
Yes I am, I always use the one directly from the 'platform-tools' directory in the SDK. Another thing is I have read multiple articles that actually state that Google has removed the adb functionality in marshmallow... I don't get it. I even went from stock G.E. to CM an its exact same problem. Not to mention now I am dealing bwith the fact that the nethunter kernel isn't compatible with the CM build for Nexus... What!? Anyone can enlighten me on that subject I would love to know that as well... LoL. Here is link to one of the ADB articles though.
Tekto-kodi.com/kodi-news/marshmallow-android-6-removes-adb/
I looked at your link and the links provided in that article. The only thing I can read from those is that the ability to run ADB from your phone, i.e. from the terminal emulator (not your PC) has been removed. Are you trying to run ADB from your phone or your PC (I was under the impression that you're using your PC, but I have to ask)?
As I stated before, ADB from my PC to my N6 works just fine with Marshmallow (6.0.1 MMB29V).
You say that you use ADB directly from "platform-tools", but you don't say if you've updated the tools from the SDK-manager.