Related
i successfully got into adb in recovery mode fairly easily on my ubuntu 10.4 laptop using the following method-
this should also work for a linux live boot from a usb flash drive
in one terminal tail and follow log messages
~$ tail -f /var/log/messages
in another terminal run the loop
then
1. plugin usb and keep it plugged in
2. remove battery, eject sd card.
3. put battery in
4. press vol- and power
5. after around 6 seconds, your terminal with the log will show something like "new high speed USB..."
6. press vol- to select recovery
7. press the power button
8. IMPORTANT- as soon as you see a new log entry (something like "USB disconnect"), pop in the sd card
check your loop terminal for adb. if it doesn't work, repeat at step 2
hope this may be helpful to some
blaksplash said:
i successfully got into adb in recovery mode fairly easily on my ubuntu 10.4 laptop using the following method-
in one terminal tail and follow log messages
~$ tail -f /var/log/messages
in another terminal run the loop
then
1. plugin usb and keep it plugged in
2. remove battery, eject sd card.
3. put battery in
4. press vol- and power
5. after around 6 seconds, your terminal with the log will show something like "new high speed USB..."
6. press vol- to select recovery
7. press the power button
8. IMPORTANT- as soon as you see a new log entry (something like "USB disconnect"), pop in the sd card
check your loop terminal for adb. if it doesn't work, repeat at step 2
hope this may be helpful to some
Click to expand...
Click to collapse
Awesome Post! you win the most helpful post of root!!... well over exaggerated but you get the point. Thank you.
blaksplash said:
in one terminal tail and follow log messages
~$ tail -f /var/log/messages
Click to expand...
Click to collapse
Great tip, thanks for knowing bash much better than I do
This ought to be quite a bit more useful than my previous method of running an lsusb loop, and definitely more useful than waiting for Win7's boo-boops, which like all Windows notifications is prob ~1s after the bus event is completed--I NEED MORE TIME(ING), so thanks!
Kulaa said:
Awesome Post! you win the most helpful post of root!!... well over exaggerated but you get the point. Thank you.
Click to expand...
Click to collapse
rynosaur said:
Great tip, thanks for knowing bash much better than I do
This ought to be quite a bit more useful than my previous method of running an lsusb loop, and definitely more useful than waiting for Win7's boo-boops, which like all Windows notifications is prob ~1s after the bus event is completed--I NEED MORE TIME(ING), so thanks!
Click to expand...
Click to collapse
Thanks guys
I also forgot to add that Windows users could easily try ubuntu or a Linux distro by booting a live session from usb disk.
blaksplash said:
Thanks guys
I also forgot to add that Windows users could easily try ubuntu or a Linux distro by booting a live session from usb disk.
Click to expand...
Click to collapse
I'm not sure a livecd on usb will work unless persistence is enabled, if one's concerned about setting up a 51-android.rules in /etc, but I have my doubts that a dedicated driver is necessary for work in adb with linux.
rynosaur said:
I'm not sure a livecd on usb will work unless persistence is enabled, if one's concerned about setting up a 51-android.rules in /etc, but I have my doubts that a dedicated driver is necessary for work in adb with linux.
Click to expand...
Click to collapse
i just tried it on a live boot of mythbuntu 10.4 and it worked on my first try. i think if you sudo ./adb shell you shouldn't have add the usb rule. no drivers, no path changes
open a terminal-
[email protected]:~/Downloads$ wget http(colon)//dl.google.com/android/android-sdk_r06-linux_86.tgz
[email protected]:~/Downloads$ tar -zxf android-sdk_r06-linux_86.tgz
[email protected]:~/Downloads$ cd android-sdk-linux_86/tools/
[email protected]:~/Downloads/android-sdk-linux_86/tools$ sudo ./adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can windows show the log of USB connection?
Cool! I tried to do it but didn't quite get it on my first try (although I don't even want to root right now).
Thanks for the share!
Booker-T said:
Can windows show the log of USB connection?
Click to expand...
Click to collapse
i'm not sure. here is link for tail for windows. you might be able to open C:\WINDOWS\system32\config\SysEvent.Evt or some other log file the might keep track of hardware events
sourceforge.net/projects/tailforwin32/
x.v_ said:
Cool! I tried to do it but didn't quite get it on my first try (although I don't even want to root right now).
Thanks for the share!
Click to expand...
Click to collapse
so did you get it in another try?
I for the life of me can not get adb to run on this phone. I know adb and used it back when I had windows and use it currently on Ubuntu 10.04 with my Nexus One without any problems. I keep getting the device not found... How do I loop "adb shell"?
i got it on the first try with ubuntu live usb, once i got the error and i was in recovery, i went to go do the update.zip and i press power too fast and it ended up going to system reboot and i havent been able to get in since then
InsightGoalie said:
I for the life of me can not get adb to run on this phone. I know adb and used it back when I had windows and use it currently on Ubuntu 10.04 with my Nexus One without any problems. I keep getting the device not found... How do I loop "adb shell"?
Click to expand...
Click to collapse
are you able to get into adb normally with the phone set to "HTC Sync"?
here's how to make the loop
echo 'while true; do /ADB_DIRECTORY/tools/adb shell; done' > script_name
chmod +x script_name
./script_name
if you need root privileges to adb-
sudo ./script_name
socalracer said:
i got it on the first try with ubuntu live usb, once i got the error and i was in recovery, i went to go do the update.zip and i press power too fast and it ended up going to system reboot and i havent been able to get in since then
Click to expand...
Click to collapse
i've had the same thing happen to me. i left the battery out a little longer before my next attempt and that helped- maybe for a minute or 2.
i got it first time 2 times yesterday, my trick i think format sd card as ubuntu live
usb
Any idea if there is a USB log for OS X? Looking through var/log now and I cant seem to find much.
I've had a MT3G for awhile and just upgraded to a Nexus One. I still have my old phone and can use adb with the MT3G without any issues. When I try using adb with the Nexus one i receive an error insufficient permissions on the device. Here's some more info about my setup:
Nexus One:
Clockwork Mod Recovery
CM6.0.0RC1
USB debugging is enabled
Computer:
Ubuntu 10.04
I have the rules set up for adb
I have tried remounting and restarted adb with root permissions and have still receiving the same error. I've tried connecting to another Ubuntu box and a windows xp box with the same error.
Any help?
What response (if any) do you get to the "adb devices" command?
What exact command are you trying to execute when you get that error?
When i run adb devices i receive this:
List of devices attached
???????????? no permissions
adb shell gives this:
error: insufficient permissions for device
I receive the same output running the commands as user or superuser. I've also killed and started the server as user and root. Remember I'm running the udev rules so I can run these commands as user.
Today I went ahead and reflashed my phone. I downloaded cm6 from xda and frf91 from the same post. Checked the md5sum for the update and then wiped and flashed.
Even after the wipe I'm in the same spot.
Can you access the device via fastboot?
When I first got the device I used fastboot to unlock the bootloader.
now the command
Code:
fastboot reboot
hangs at
Code:
< waiting for device >
I can still reboot the device into recovery and fastboot.
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
last thoughts, as it's been a while since I've used adb on Ubuntu...
Code:
./adb kill-server
./adb start-server
./adb devices
???
./PROFIT
It seems to be somehow an issue with your local adb set up, not anything phone-related. Could even perhaps be a driver issue.
raim1312 said:
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
Click to expand...
Click to collapse
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
i get the same results after killing and starting adb either as user or root. i'll pull out the drivers and android sdk and reinstall. i'll let you know how it goes once its done
codesplice said:
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
Click to expand...
Click to collapse
Yeah sorry about that one. i'm still a newb but willing to learn
i just reinstalled the android sdk and removed the udev rules. gave my pc a reboot and killed then started the adb server.
same issue.
to verify adb was working i plugged my gf's mt3g in and adb found it.
i've never need to reinstall usb drivers in anything but windows so honestly I don't know how to do it in ubuntu. can you point me in the right place?
I'm afraid I'm out of ideas then. I've only had very limited experience using adb on my Ubuntu install
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
raim1312 said:
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
Click to expand...
Click to collapse
Please do. Everything that I was able to find on google relates to a screwy adb server... but being able to adb on another device complicates things. Very interested to see what you figure out on this.
I installed the rom froyou frf50 with radio from here:
http://android.modaco.com/content/g...ed-update-zip-no-radio-option-online-kitchen/
didn't work.
while looking into returning the phone to stock i received an ota update. so i ran it.
the update failed during a signature check.
i tried to follow the instructions here to return to stock: http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
only issue is fastboot will not find my device.
performed a nandroid restore to go back to cm6 frf91.
fastboot still will not find my device.
i'm at a loss here. the device is usable for everything but adb. and adb is the main thing i need. i dont' want to keep whacking at this and cause more issues.
any ideas are welcome. all my data is backed up and the bootloader is already unlocked.
its... working??? i finally got adb to recognize my device.
first i restored the phone back to stock using this: http://forum.xda-developers.com/showthread.php?t=717870
then i replaced the cable i was using for one from a Motorola droid. (since the mt3g has a different usb port i had to use a different cable).
then i ran the adb kill and start server commands as root. and voila. it works.
i remove the cable and go back to the one that came with the phone and it still works. not sure what happened but adt is working as well. so im back up and running. i wish i knew the cause of this frustration but i fear i will never know. anyway thanks for all your help!
Yikes.... take your boat back!!!
Perhaps you ran chmod u+s on adb?
Edit: Yep, that was the problem for me..
I don't know the commands to well, so i just right clicked adb and went to permissions and removed set uid.
seems adb needs started from root, but making the file always run as root doesn't work so well.. I thought it would fix my annoyances with eclipse starting adb with not enough permissions. Perhaps ill chmod u+s eclipse instead.
Oh and btw... nexus one can kiss my a$#. HTC Hero!!
Solution for permission problems:
http://wiki.cyanogenmod.com/index.php?title=Udev
Hi everyone i think i messed up in the process of flashing a new rom on to my captivate the way i did this was i used 1 click root to root the phone and then used rom manager to boot into clockwork and from there installed from sd the zip of the rom i wanted wich was Cognition v2.2 BETA9 it apeared everything went well up untill the phone rebooted i then was greeted with a looping recovery boot ive tried the button combos to get into download mode but none seem to work is there anything anyone thinks i should try? thank you anyone with help
did you really need to start a new topic in the wrong section for this?
http://forum.xda-developers.com/showthread.php?t=786532
http://cognition.theidiotshideout.net/phpmyfaq/index.php?action=show&cat=1
http://webchat.freenode.net/?channels=Cognition
there is already plenty of info on this. read the last 5-10 pages of the thread and you will see that you installed the rom WRONG
you need to find a way to get into download mode and restore it to stock......then before you flash something, read.
Sorry for posting in the wrong section if there is a mod feel free to move this I have previously read everything you gave me and i am unable to get into download mode but i am a little confused on the adb process can you help me through this i open a cmd promp and type in adb shell and it just says something about it being an unknown command am i missing a step?
hellhound911 said:
Sorry for posting in the wrong section if there is a mod feel free to move this I have previously read everything you gave me and i am unable to get into download mode but i am a little confused on the adb process can you help me through this i open a cmd promp and type in adb shell and it just says something about it being an unknown command am i missing a step?
Click to expand...
Click to collapse
did you download the SDK? ADB is part of the SDK and is not something found natively in windows.
i do have sdk in my Cdrive yes
hellhound911 said:
i do have sdk in my Cdrive yes
Click to expand...
Click to collapse
did you unzip it?
is the filepath C:\android-sdk or something similar?
i think you need to have a look at this:
http://forum.xda-developers.com/showthread.php?t=819105
hellhound911 said:
i do have sdk in my Cdrive yes
Click to expand...
Click to collapse
Pirateghost said:
did you unzip it?
is the filepath C:\android-sdk or something similar?
i think you need to have a look at this:
http://forum.xda-developers.com/showthread.php?t=819105
Click to expand...
Click to collapse
Yeah that thread has everything you need to know. It's important to check and make sure you can enter download mode via the button combo method before you start flashing away.
Also, you really must do a backup of your current rom before you flash a new one. Had you done that, you wouldn't be sitting where you are right now.
Having said that, you will read in the thread that Pirateghost linked that, assuming you have the sdk and have installed the proper drivers, you need to navigate to the \tools directory within the sdk in order to run adb. Once you are in the proper directory, just type:
adb shell
(dollar sign should appear here)
adb reboot download
and it should reboot into download mode.
There really should be a warning not to flash Cog b9 from 2.1 with clockwork. I don't think I've heard of a single report of that working.
There after two "modes" your phone can be put into...
1. Download mode:
Done by having your phone off and then quickly turning it on and holding down JUST the up and down volume controls while having the usb already plugged in (easist I've found is stated above regarding taking the battery out, plug in usb, hold both volume buttons, then while holding them put battery back in)
2. Recovery mode:
Done by holding both up and down volume buttons AND the power button.
I had the same problem as well.
I could use the help of you gurus trying to get some data off my phone since I sat on it yesterday and horribly mangled the screen. The screen wont come on but it sounds like the phone is still working. The screen also doesnt respond to touching it not surprisingly
Really all I want to do is get my texts off of the thing, but with the screen not working, and ADB seeming to be disabled, im not sure how to go about that.
Is there any way for me to:
A) Remotely enable ADB(im guessing no)
B) Remotely enable Wifi(so I can use an app that is already on my phone to control it from my computer)
Any help is appreciated!
BB
If you had a custom kernel on the phone before it broke there is an option in clockwork to restart adb you would just use up down vol buttons and power buttons. I will give you a Button sequence in a minute. Just gotta reboot my phone
[Edit ]
I just rebooted my phone and the dark core kernel does not have the option to restart but I do know some kernels do post what you are tuning and maybe someone else knows. Also there is the TV OUT option just plug into your tv and see if you don't get a picture maybe its on by default. Good luck(;~}
Sent from my phone on vacation
Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB
Baconbreath said:
Thanks for the reply! I was unaware you could restart ADB from CWM. I am running Serendipity VII with the most up to date Serendipity kernel I will try to find out if they support it(if anyone reading this can look in CWM and give me the key sequence that would be so awesome)
http://forum.xda-developers.com/showthread.php?t=1107894
I thought about the TV out option but I would still be unable to input anything from the touchscreen so would be a bit limited with what I can do
Thanks for the assist!
BB
Click to expand...
Click to collapse
The only thing I can think of, if find out where the texts live, ADB into the phone and pull them to your PC.
I use SMS Backup app, but if you don't already have it, it won't do you any good at this point.
You know, Maybe what you can try is a nandroid backup from ADB. You may be able to save the entire ROM and contents, then pull it from your device to your PC.
Also the key sequence for mount usb in recovery might be useful but you don't get access to system only the sd card.
Sent from my phone on vacation
That would be really helpful key combo too to get some photos off of it..and maybe Tibu backed up apps. Mental note: use google+ cloud storage for photos and video in the future
BB
I gave up on this for a while....but tonight I decided to give it a go again with results! Posting steps here in case someone else runs into this...
I took the phone full apart to see if there was any damage internally besides the mashed screen and I couldnt find any. Put it back together and oddly ADB started working!
After much searching...I was able to find this solution:
http://androidcommunity.com/forums/...s-storage-through-the-recovery-console-19999/
for a step by step, all I did was :
Adb root
Adb reboot recovery
Running:
ADb devices
Showed:
List of devices attached
32326B102E3E00EC recovery
then run:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
and the SD card became mountable and I was able to rescue my stranded data
BB
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?