I tried to follow the steps from androidandme to set up my phone for screen shots. I got java, got the android sdk and unzipped everything (nothing was installed?), changed the path under advanced settings, dowloaded eclipse (why not) and all that jazz - full 9 yards.
However, when I run ddms.bat in the tools folder and Dalvik comes up it never recognizes my phone. I have tried with the g1 mounted, unmounted, usb debugging on/off (which I also do not know what this means).
Anyone have any thoughts? I did not get any prompts about drivers and I am mounted to my computer.
Read the guides on how to install ADB.
for some reason when i ever i use ddms to take screen shots, i can't just go to take a screenshot, i have to run a logcat first, it will bring up a popup that says "failed!" i then close that and it runs a logcat, after i do that, then i can use it to take a screen shot.
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
Sorry if this is not relevant, but I had a ton of trouble until I had the newest jave runtime installed. I never had trouble, got a new laptop at work and had no clue why it would not run. the newest JRE fixed it right up. Maybe not your problem but...
Also I like the program "droid explorer". It has screenshot built in.
EDIT.
I have one more thought...I (always have one more thought) try starting your phone in fastboot (camera and power) then back button when the skaters come up) and see if it asks for drivers then.
s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
adb.exe is a command line application, it doesn't have a GUI. To use an command line app you have to 'cd' to the directory where it's located and enter valid commands. I think you can type 'adb help' for a full list of commands.
Try reinstalling the drivers, it took me a few tries to get it working right on Vista (interestingly no drivers are needed for OS X )
Let me start very basic. Is there any "installing" of the SPK? Or, do I just extract the files? I extracted them and created a directory in PATH like the site said to do.
If there is no installation... are you saying for me to get in dos and just start keying commands, and not using any of the files from the zip?
There is no installation, but EVERYTHING for the sdk is ran in command prompt. Meaning click start, click run, type in cmd, then type cd path/to/your/toolsfolder/ then type adb remount see if it does, if not you NEED TO FOLLOW THE ADB INSTRUCTIONS FOR INSTALLING DRIVERS.
Related
im trying to set up a adb so i can use my g1 as a webcam:
http://forum.xda-developers.com/showpost.php?p=4975656&postcount=17
however when i plug in my g1 it says everything was installed except the adb.
Do you have ADB setup on your computer in the first place? If not, http://forum.xda-developers.com/showthread.php?t=532719.
I installed the adb with the sdk as it was mentioned and my computer still doesnt show my phone as an adb device
Did you install the drivers for adb?
i cant find out how!
85Mario85 said:
i cant find out how!
Click to expand...
Click to collapse
a little search and VOILA!!!
http://forum.xda-developers.com/showthread.php?t=446274&highlight=64bit+usb
this works if you are running windoze 7 x64
i dont get how im supposed to put windows 7 on test mode =S
im getting this aswel "When running the command prompt adb install I receive an error dialog stating:
"This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.""
im getting so frustrrated with thiss
bump! i dont get this =[
Search for pdanet and install it. That's how I set up adb for Windows. (Btw - get rid of Windows. Finally did my switch to ubuntu today - ahahahahahahaha I'm sad I ever even used Windows.)
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
evilkorn said:
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
Click to expand...
Click to collapse
adding it to the path just saves time. instead of having to cd all the time you can just run adb. i highly suggest it. and i agree - ubuntu is a ***** about permissions all the time. i love it, but i have to learn to use it. however, i'll probably always have a copy of windows in case i can't find out how to do something and have to have it done. better safe than sorry. =]
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.
trying to root 2.1 sprint hero, had the patched .6 version but redownloaded the .5 version on my phone, now says 2.27.651.5! Good right? Then I'm trying the regaw method for rooting. Downloaded the sdk, downloaded HTC Sync 2.0.33, downloaded hero-root. Renamed them to C:\android-sdk-windows\tools, went to the command prompt and typed it in. Then I type in adb devices and I get an error: adb not recognized as an internal or external command, operable program or batch file. I've checked debugging, and still get same error. Deleted files and redownloaded everything again and STILL get same error. Any help would be much appreciated
make sure you cd to that directory, or you can click-n-drag adb.exe (adb-windows.exe in some cases) into your CMD promt and type your command after... Little work around for odd computer setups
EDIT - you could also try to append the ".exe" at the end, i.e. >adb.exe devices
Thanks, I gave it a try! Still nothing,
Did you run the setup or did you just download, extract, and then run straight to CMD? try running the setup, don't download anything if you don't want to, and then try again.
I must be an idiot, the folder size is 54.2 mb. I'm at a loss. I will continue trying!!!!
Ok, total noob here! I've been at this for a while now and still can not get adb devices to recognize my phone. Device manager says everything working properly, drivers installed properly. I have searched and searched for an answer and still I can"t find one. Is there something I am doing wrong or have I not set up. All I want to do is root my phone, any answers would be a godsend.
I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it
TaeKwonDonkey said:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
Click to expand...
Click to collapse
Do you have the right drivers installed?
When your phone is on, plugged in, SD not mounted, and USB turned on, you should see "Android Phone" and "Android Composite ADB Interface" underneath that.
If you don't want to root (it's so easy and painless if you can follow instructions) then I don't know what to tell you other than:
1. Install "USB Deview" and remove all HTC/Google/Android related drivers.
2. Completely uninstall and wipe out the SDK stuff.
3. Rebooted, and reinstall Android SDK, and make sure that Windows7 installs the right drivers.
Installing the SDK is no more difficult than installing any other piece of software. If you've got Java installed, and you've plugged your phone in, and debugging is turned on, what *should* happen when you double-click ddms.bat is, the command prompt window opens, but then the Debug utility should open.
I had the screenshots stuff working before I ever rooted.
I followed the steps here: http://www.knowyourcell.com/google/...take_screenshots_on_the_google_nexus_one.html
Rooting is easy and painless. If you root, you don't have to flash a custom ROM or anything, but then you can install an app that you simply open, enable, then whenever you're doing something that you want to take a screenshot of, you shake the phone, and there it is.
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?