A couple of days ago I flashed Eclipse v2.0, wanting to change my phone up a bit I had been on shift3r for a few weeks. Anyways, just now I was trying to copy some modules into my /system/lib/modules to overclock my device and was having issues copying within my phone. So I tried to use an adb shell to do so, but I keep getting the output of the device being offline, this is what I'm getting:
-NV57H:~$ adb devices
List of devices attached
0A3BAF200C014015 offline
And I have done a search, where some people were having trouble using certain cords, mainly with Samsung devices, and switched cords with success. This does not apply in this situation as I have used adb many times with the cord I'm using, and also I did try to switch cords anyways. Also the only other thing I saw was a situation involving driver installation and re-installation creating problems. As I am on Lubuntu, and not Windows, this does not apply to the situation because I have neither installed or re-installed drivers. My adb is setup properly because I have been using this computer for a couple weeks now and it was working previously. Any ideas on anything that could have happened? or maybe I should switch ROMs?
additionally: on my file manager, in the address bar for my device when it is plugged up, it is seeming odd to me, this is now what the address is showing for my device's sdcard:
gphoto2://[usb:002,007]/
I think I might have messed something up on my Bionic. If you read the first post I was saying how I tried adb on the same computer I've been using, AFTER flashing Liberty. Well I've gotten rid of Liberty and went back to SHIFT3R to try to fix the problem, and my problem is still looming. I have tried on Lubuntu and Windows, and my girlfriend's Incredible 2 works on both of the OS's with the same cables I'm using as well. I remember the other day when I was flashing Liberty, I had to mount my USB while in recovery to move the file onto my SDCARD because it had vanished once I tried looking for it to flash it. I remember when I tried to eject my phone from my computer (lubuntu), it said that it was busy and could not unmount the phone, after the file transfer screen went away as well. And then I waited a few minutes and tried again, it said the same thing, but I unplugged the cable anyways and unmounted USB in recovery. The file flashed fine so I know it was not still transferring the zip file. If anyone knows what I may have done or what I may be able to do to fix this let me know. I just wanted to update the thread with my most recent trials and errors in fixing it. Thanks to anyone who can guide me. I have never had issues with adb before.
O man i really hope someone can help us with this issue.
I have the same problem..
I am trying to use the path saver, and it keeps telling me device offline.
RSD lite won't even recognize it.
HELP!!!
Me too
I had the same problem... I wanted to upgrade the radio on my Bionic to the .901 load... I could not get adb to see my device.
Using Windows 7 64 bit (Ultimate).
RSD Lite would not recognize device either.
Decided "Screw it", I'll just go back to my nandroid backup... which didn't work either.... soooo... here I am.... stuck.
Off to google I went... I don't know which of these fixed it, but it is working now... here is what I did.
Found a thread that stated "run your commands from the 'C:\platform-tools' directory... so I took all of the files from the "Bionic Path Saver 1" and copied and pasted them into this directory.
Secondly, instead of just double clicking the upgrade batch file (runmebbb.bat) like I was before, I opened a DOS command shell -IN ADMINISTRATOR MODE- and ran the batch file from there.
It immediately kicked off and I was off and running.
For those of you that don't know what I am talking about, I was upgrading... using instructions from this thread:
http://forum.xda-developers.com/showthread.php?t=1433783
I hope this helps... it bugged the crap out of me... but the feeling of relief certainly makes up for it.
Well the thing is it doesn't work on windows or Linux with my bionic. I've tried various Android devices that I own and all of them work on both of my operating systems except for my bionic
Sent from my DROID BIONIC using Tapatalk
Same issu
I just installed Eclipse 2.2 on my Bionic and now i am getting the same issue. Has anyone found an answer or a fix for this? Also, does the .902 patch have anything to do with it? Any help is greatly appreciated.
Once i had this problem the only way i fixed this was by using RSDLite to flash a FXZ. Changing ROMs didnt work, nothing worked but that. It wont affect RSD reading the phone in AP Fastboot mode. Just make sure you install moto drivers and have the newest version of RSD Lite. That worked for me, now I have my adb back
Sent from my Transformer TF101 using xda premium
Are you using Safestrap recovery? If so I think that may be the issue.
Try downloading "ADB Over Wifi" from the market.
Then "adb connect iport"
The widget should show you ip/port when you activate it.
Bionic 2.2 Eclipse adb device offline
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
s.wyckoff1 said:
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
Click to expand...
Click to collapse
First of all, it automatically adds 5555 into your address so instead use
Adb connect 10.0.2.2 or whatever your ip is. And as far as not showing your device with a USB cord, try various other cables. I have over ten cables and maybe two work with my bionic. I urge you to use as many as possible before my next recommendation. This problem screwed with me for a couple months and finally i booted into fastboot mode and FXZd my phone. I booted my phone up after that and adb worked perfect. I don't know what causes this.
Sent from my DROID BIONIC using xda premium
Eventually I discovered why adb wasn't working. Apparently there was no adb daemon running. I came across this in a different thread awhile back. Once I copied it to my phone's /sbin/ directory (there was a link to the file in this post http://forum.xda-developers.com/showthread.php?t=974824) and ran adbd from a terminal I could use logcat. However it was removed everytime the phone cycles power so only a temporary fix. I was considering trying another rom instead of eclipse 2.2. It was also buggy in that when I tried to do an adb install it broke terminated the daemon.
If you're using linux I always do "sudo adb start-server"
Sent from my DROID BIONIC using Tapatalk 2
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
For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud
Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080
anyone have problems in ubuntu 10.04 can't get it :'(
I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk
I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.
[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.
If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs
I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps
Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.
Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave
I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.
so, stupid question time.
i've used ADB in the past and its worked great so not sure whats going on this time around.
I get the following errors when trying to start adb:
"daemon still not runningerror: cannot connect to daemon"
I have installed moto drivers for droid 3 (32bit), im on win7 32bit. I have my phone on dev mode, and charge only. I have run CMD with admin rights. and still ADB wont turn on.
I have also tried using the new one click method:
http://rootzwiki.com/showthread.php?t=3714&p=75934
anyone have some direction? I did kill adb from my running processes (all instances) and tried all over, no go, same error.
help?
Did you put the phone is PC Mode as opposed to USB Mass Storage?
its supposed to be done in Charing only mode, the issue isn't on my phone setup, it got to do with my darn computer, I can even do an adb devices command... may have to remove the sdk completely and start over.
Put in charge only, use one click method
Sent from my DROID3 using xda premium
did you change directory in cmd to the folder that adb is in?
...I had to change to the folder like this cd\program files (x86)\android\android-sdk\platform-tools
The one-click root method is bundled with adb.exe. Except for the driver and a USB cable, it contains everything needed to root.
I've been reading all day and I'm confused and looking for some direction.
I have a mostly stock Droid Bionic that had been rooted using the motofail method. All was fine, and then I attempted to make the edit to my mount_ext3.sh file, but must have done something wrong.
At reboot, phone is stuck at the red Moto splash screen.
I thought I could use adb to pull / push the mount_ext3.sh script to edit out my error and put the file back. For some reason I am not able to do this. I believe I have the correct drivers installed, and I am able to see the adb device in my device manager. RSD lite also sees the device when in fastboot mode. But adb devices shows no device.
Can someone tell me if it's possible to use adb to restore this mount_ext3.sh file? I'd prefer to not factory wipe if possible.
Also, I notice that a lot of links and files referenced in rsd restore methods are gone or invalid. Although I have found them elsewhere (such as bionic_minimal_fxz.tar.gz) .. but I'm not sure my best course from here. Seems like the small edit should be easier to un-do. Can I boot from an SD card or mount the /system/ partition some other way?
Thanks, and if this belongs elsewhere, please let me know and I'll move it.
Thanks,
Chris
Are you using the factory cable from Motorola? Also are you using the latest drivers from Motorola? Make sure you using the correct drivers for 32 or 64 bit OSs.
Gosh .. factory cable. I'm not sure .. I have so many cables laying around.
The cable has several sticky labels that say:
Model: DICMUSB / DC1012 ..
Hmm .. this might be from my old Incredible - It has the following model numbers on the cable:
adr6300vw
adr6225vw
adr6226vw
mwp6985
Jimmeny Crickets. Now I can't seem to be able to get the phone to do much of anything. Sheesh .. indicator light on the front is steady white when usb connected. Did I read somewhere that you basically need a full battery for a lot of this stuff? Swell. Guess I'll home and get the wife's battery.
Majority of people's problem's i've noticed was people not using the factory cable. Motorola's cable are different from other manufacture cables as I've found out recently. I've had issues in the past using other cables and usually using the factory cable resolves my issue.
Link to post about motorola cable:
http://forum.xda-developers.com/showthread.php?t=1077414&highlight=motorola+factory+cable
adb
So I am using the correct cable, I believe I have the correct drivers. I've installed the SDK and am using the ADB from the Android platform_tools.
RSD Lite 5.6 recognizes the device as:
Fastboot CDMA_TARGA S
Does that confirm anything (like that I have the correct ADB driver installed) ..
I've tried all the usual adb commands like adb shell, wait-for-device, kill-server/start-server, etc.
I always get
error: device not found
or in the case of adb devices:
I just get an empty set. ARGG! Really frustrated. I can't believe I started all this with a fatfinger on a forever root script edit. I really thought I would be able to adb pull/push the /system/bin/mount_ext3.sh file in a case like this.
Thanks,
Chris
bionic minimal
Does anyone have any recent experience with this bionic_minimal fxz file:
http://forum.xda-developers.com/showthread.php?p=17560174
I wonder if I can flash that and get back?
Thanks,
Chris
I am going to assume you were previously on 902 or 905. You could do SamuraiHL's no dataloss fxz script to 902. Should prevent any data from your internal memory from being wiped: http://www.droidforums.net/forum/mot...ml#post2173723. I believe there used to be a link in there to the original fxz 902 file that prevented your memory from being wiped. Since you can see your phone via RSDLite and not adb.
Btw...i never mentioned to ask but are you booting into AP Fastboot or staying at the splash screen when trying to adb?
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Xenther said:
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Click to expand...
Click to collapse
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
dray_jr said:
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
Click to expand...
Click to collapse
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Xenther said:
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Click to expand...
Click to collapse
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
Thanks again, so much, for all this! I'll go through all of these in about... two hours or so. I'll report back regardless of the outcome. You're awesome for this! :highfive:
No problem man hope it fixes your problem
Sent from my XT1056 using xda app-developers app
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
So, I've done everything in this list, and also added trying forums.motorola.com/posts/caa12135bd?commentId=725256#725256 out. I'm pretty much out of ideas, because everything I've searched showed pretty much everything you've suggested (and that I tried!) as suggestions
I appreciate the help, but so far (at this rate), I think I might just not have to root. This is super frustrating to me!
EDIT: Actually, I think I finally have something here! After hooking it up to another computer, installing the adk and everything, making sure all the drivers showed up as installed correctly and getting nothing I pretty much resided to giving up. I, for whatever reason, decided to try and run adb. After I did, and ran the start-server command, it gave me the window to accept my laptop's fingerprint! Finally on to follow the rest of the guides!
Thanks!!!
Second edit: So, proceeding to step 3 or so in RockMyMoto, I'm encountering another issue. When running Impactor and trying to run telnet on port 2222 or whatever that is, I get an error that says Signature Bugs unavailable. If I'm understanding correctly, I have to do everything in this guide to downgrade to 4.2.2 or whatever the version with the camera update is, because there isn't a root available for 4.4 without downgrading. But now I'm seeing that I somehow need to downgrade from 4.4 to the previous version in order to get Impactor/telnet working correctly?
I'm super lost now :C
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
dray_jr said:
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
Click to expand...
Click to collapse
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Xenther said:
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Click to expand...
Click to collapse
i wouldn't see why not but i am not sure
26344422579
dray_jr said:
i wouldn't see why not but i am not sure
Click to expand...
Click to collapse
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Xenther said:
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Click to expand...
Click to collapse
correct
dray_jr said:
correct
Click to expand...
Click to collapse
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Xenther said:
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Click to expand...
Click to collapse
everything looks fine bro just finish the last command and then run root checker you should be fine.
i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
i might downgrade just to run back threw it to see if i can figure it out and maybe put together a package for you that i know works. but i am on the sprint X
dray_jr said:
everything looks fine bro just finish the last command and then run root checker you should be fine. i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
Click to expand...
Click to collapse
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Xenther said:
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Click to expand...
Click to collapse
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Alright, I tossed the adb stuff on my flash drive, and I'm going to see if I can try this at work. I'll report back. You are going above and beyond to help me out, and it's just amazing. After my last community being the League of Legends community, I'm not used to this! :highfive:
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Running each of the commands works, until the last one. I get "can't create /sys/kernel/uevent_helper: Permission denied" error message
EDIT: I got it! Yeah!! :highfive: I found someone suggesting to take the phone back to 4.2.2 with this error message and redo SMM, and it stuck! Downloaded root checker, and I got a congrats result! Thanks so much, mate! You've been such a huge help; I was going to give up the first night before I even decided to post here!
I'm glad to hear you got it rooted finally if you have any other questions or need any ideas on what to do please feel free to pm me anytime
Sent from my XT1056 using xda app-developers app
i've got one for you... running windows 7, 32 bit. Eset AV-disabled.. have 4.2.2 rooted, but can't get moto-wp-nomo to successfully run...any ideas?