Hi: I'm a long time lurker here on xda-dev, but I'm a first time rooter and this is my first time posting here.
I appreciate any help that I can get, and I will try to be as descriptive as possible so that I don't waste anyone's time. You should know that I am running OS X 10.6.7 (which is 64 bit if that makes a difference). I know that it's possible to root from OS X because I've been in contact with a fellow xda'er about his success with it and my subsequent problems. You will notice from the screenshots that I have a bootcamp partition because I plan on installing Windows 7 at some later time. I think that this may be a driver issue, but really dunno why I would have this driver problem if the person who I know has had success with OS X 10.6.7 didn't have any problems. Not sure if this matters, but I am using this sdcard: http://amzn.com/B003WGJYCY
Things that I've done that you might ask me if I've done:
-Debugging is on (I've toggled it a few times too)
-temprooted with Visionary
-Extracted the Shift file to the root of my sd card
-Checked the md5 of the file in Shift using Terminal emulator (it matches what the guide says it should be)
-Reinstalled the SDK
-Reinstalled Visionary
-Re-Extracted the 'Shift' file to my sdcard.
I am trying to root my shift following this guide : http://forum.xda-developers.com/showthread.php?t=932153
I have installed Android SDK and for have installed the packages that you can see in this screen shot: http://oi55.tinypic.com/2dvimb6.jpg
I then temprooted using Visionary: After a few failed temproots, I did get a successful temproot, which I am verified by gaining SU with the app Terminal Emulator.
I open up command prompt and do the commands that you can see in this screenshot and as you can see after ./adb shell I get "error: device not found" : http://oi51.tinypic.com/2ztcymt.jpg
As you can see, I can open adb, but the adb shell command returns an error that no device is found. I've also done this: http://oi51.tinypic.com/264t6o5.jpg
So, what do you think?
i forgot to mention that my phone is in charge only mode when I execute ./adb shell
is it connected to a 2.0 USB port?
Also have you tried restarting your phone and mac?
I also saw on another forum that Superuser had to be uninstalled then try temp rooting again.
Also are you keeping an eye on your phone while trying to gain su access? You have to click yes when it asks if you wanna give permission.
You could always try rooting via terminal on the phone. That's what I did, no PC involved.
^ Shift Faced
Thanks for your responses.
I assume these are USB 2.0 ports on my 2010 MacBook Pro. I've uninstalled superuser a couple of times, but when I use terminal emulator to check if I'm temprooted, it shows back up in my apps list.
I have never had the option of giving adb superuser permissions, but yes I have kept my eye on the phone to make sure that the phone wasn't requesting this.
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
dubs.law said:
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
Click to expand...
Click to collapse
That's what I did. Had been waiting for perm root so long and was so excited I couldn't stand to wait until I got home and just put the commands into terminal on the phone. Just make sure that you input all commands EXACTLY. It was recommended by others to do it from desktop so you can be sure and copy and paste the commands so as to cutdown on errors but I'm not sure why... I can copy and paste from the phone It's just kinda a pita.
^ Shift Faced
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
dubs.law said:
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
Click to expand...
Click to collapse
Nope.
^ Shift Faced
So, there is no adb commands, you just flash the "eng spl" , correct?
I rooted without a computer. Thanks!
dubs.law said:
I rooted without a computer. Thanks!
Click to expand...
Click to collapse
Awesome! I was coming on to tell you I don't really remember all the details as it was a long time ago and that I couldn't help any
Exciting doing it from the phone, right? The fear of bricking is fun
^ Shift Faced
Related
Hey guys I an having the darnest time root this guy should be easy with these one clickers programs.
Pretty sure its a driver thing, note I can see the device when in cmd and doing the adb devices that shows up. just gets hung up at the end there.
attached a pic of what the cmd line looks like
anybody have the current drivers, googling for them just yields me to forum posts asking where the drivers are
thirty views and nothing
ok its not a driver issue if your loading root.sh (the big block of text) the issue is that the adb server isnt starting back up in time in order for your device to be recognized. solution? open up the bat file and copy and paste the commands one at a time; or if you have a linux/osx computer try doing it there with my scripts in my sig
couple ideas..
1.open up the run.bat file in notepad or similar and go through all the commands manually, that way you have control on speed of commands and allow enough time for adb to startup again.
2. open up the run.bat file and increase the wait time in the script.. -w 3000 or something like that..
i would suggest you do commands manually. The one-click root did not work for me but doing things manually worked right away.
How to do it
Hey man this is how I got it to work. I was having all the problems device not found etc etc. Have been trying since Sunday. What I finally did after installing the drivers was restart the computer and Phone. After that i tried to run the program it failed with device not found again so i unplugged the usb cable from the phone and closed the cmd window. And also brought up Task manager and killed the adb.exe process. then i reran the run.bat file and this time when it gets to the adb restart relogin apart i killed the SMALLEST ADB.EXE IN THE PROCESS TAB OF TASK MANAGER and that is when it finally got it to work. Had to do the same when I tested it with the uninstaller. So that seems to work. If anyone has any questions feel free to pm me.
But thank god it finally worked.
David
other people have done this and it worked for them also.
I tried all kinds of stuff ultimately I ended up using an xp machine. I later remembered the whole xp mode in windows 7 but didn't actually try it ... win7 just gave me a hard time although the post about changing the amount of time to restart adb makes sense
Sent from my SPH-D700 using XDA App
will try all of that thankyou gents
im trying to root my phone but its not working the one click program says phone not connected i already installed drivers... a problem when i try to put phone to usb it says connect but i cant c the drive ....? its not working
What one click program are you trying to use? I gave up on the one click programs after the DL09 update.
Also with DL09 the drive likes to auto mount after a reboot make sure it isn't doing that.
I would recommend following the post here:
http://forum.androidcentral.com/ver...s-hacks/54659-how-rooting-your-fascinate.html
and use post 3.
You can copy paste into the command prompt (one line at a time) making this method easier if you are apprehensive with the command lines.
im trying one click it sayed permission denied
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!
Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.
You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G
ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
tried your directions again
I have tried them again and they do not work.
Try the usb cable for the droid x. Its a really good one.
if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.
mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G
thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.
I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk
Thanks to vbrtrmn's post about his problem on the Q&A forum, I realized I lost the use of SU with todays update. I don't know why (maybe someone else can shed light on this or if this), but it did more than just that, it also broke ADB!
I don't know much about ADB so I am approaching this with limited knowledge, but I hope it helps. I do not take responsibility for any problems you may have!
Also please note that these are not instructions on getting adb and su working from scratch (although they could easily be adapted to do so)
OK! So after some messing around, I was able to get ADB and, in turn, SU working again.
First thing you'll have to do is plug the OUYA into your computer via USB and delete all the OUYA drivers from your Device manager. From what I could tell, the OUYA stopped showing up as an Android Phone ADB Composite device (hence the ADB problem). After you delete the drivers, unplug the OUYA and then follow steps 5-12 (windows) on this website: https://devs.ouya.tv/developers/docs/setup .
Once you get to step 13, you don't actually have to hit the Have Disk button, just select ADB Composite Device from that screen (it appeared for me, may not for you, you might have to follow their directions). This will take you to step 14 and 15 on that webpage.
After that is done, then head over to the original instructions on this forum, found at: http://forum.xda-developers.com/showthread.php?t=2272266
The only thing you should have to do is step 4 under HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES, assuming you already have the files in place.
This SHOULD give you access to SU and any apps that require it once again. To check, go to Make on your OUYA and open the Superuser app. If it asks for root permission, it worked.
The only problem I ran into is that the OUYA is now only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know) on my computer. Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
Again, I know very little about the drivers, adb, and/or su so if I got anything wrong, please let me know!
EDIT: Make sure to try hard resetting the OUYA before trying this. While it didn't work for me, that's what fixed vbrtrmn, but he was not on Windows.
JLCollier2005 said:
EDIT: Make sure to try hard resetting the OUYA before trying this. While it didn't work for me, that's what fixed vbrtrmn, but he was not on Windows.
Click to expand...
Click to collapse
I was using a Mac .. Hard boot both the OUYA and Mac, seemed to fix my issue. Not sure why exactly, killing adb should have done it, oh well.
The OTA update did wipe out my settings in build.prop for wireless adb.
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Same Problem
I am having same exact issue..windows 7 would love some help on this! Just need root for adblock and I am set this device rocks! +rid bloatware but thats a given.
eadred said:
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Click to expand...
Click to collapse
Well, glad to not be the only one. Let's find what we have in common, maybe we'll find where it comes from. Do you also have windows xp? Have you by any chance windowblinds installed? Have you run as administrator? Anything particular otherwise?
Same Problem
I have Windows 7 and no windows blinds...I have tried different ports and also ran as administrator. I have successfully rooted OG Droid, Droid Bionic , and Galaxy Nexus. I think I got spoiled by how easy the Nexus was to root and change roms. Love the G2 just need to get the root to stick. Every time I hit a key to continue from root bat the command window closes. I was able to read quickly a line that says unknown error has occured. Not sure why this is happening. I have tried two different drivers LG VZW_United_WHQL_v2.11.1.exe and LGUnitedMobileDriver.exe with no luck.
Using the application usbdeview, I can't see the lg driver even though I have installed it. Is it the same for you?
Actually a lg driver is indeed listed
LGE Android Phone AndroidNet Sooner Single ADB Interface Vendor Specific No Yes No No 02231cddcf4eb680 19.10.2013 19:25:05 19.10.2013 23:37:42 1004 631f 2.32 ff 42 01 andnetadb ADB Interface DriverNet lgandnetadb.sys USB Google, Inc AndroidNet Sooner Single ADB Interface 3.10.0.0 USB\Vid_1004&Pid_631f\02231cddcf4eb680
Same Problem
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
maclv said:
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
Click to expand...
Click to collapse
Not sure what you mean. On my side, if I write adb devices in a command prompt, I only get one line of numbers and beside it: 'device'. And that's it. Do you get additonal infos?
When I run the root.bat, I can hardly read the text before it closes, but from what I saw and completing with the text that you can get by editing the root.bat, I tend to think that the following is written before it closes:
Looking for device...
.\adb.exe wait-for-device
Determining carrier...
On a chat before, someone suggested me to right click the root.bat and clic edit to view the content of the bat. And then manualy reproduce in adb by pushing the necessary files and such... But I haven't yet given hope that it works with the bat. But maybe you feel like giving it a shot.
I have ESET as antivirus
Same Problem
No luck manual editing the root bat. When I type adb device it list VS980_4G - and a set of numbers
I was wondering if I should try another root method. I have seen on an italian forum someone who rooted with a chinese method. I have no time right now, but I might test it in a few days.
http://translate.google.com/transla...&hl=en&langpair=auto|en&tbb=1&ie=windows-1252
Btw in which country are you? I bought my mobile phone from digitec in switzerland.
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
maclv said:
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
please let me know if you get through. I'm stuck and willing to return the device. it's killing me
Tried on another computer. Was done within second. It will remain a mystery why it didn't work on mine. But hey, done is done! :good:
I will try on another cpu hmmmm
Sent from my VS980 4G using Tapatalk
hit windows key+r,enter cmd then hit run.
then navigate via cd c:\folder\folderthatcontainsroot.bat
then open root.bat by typing it in cmd.
that should stop tje autoclosing of cmd when opening via windows Explorer.
Sent from my LG-D802
Thank you for the tip. I was able to get root switching to a different cpu. .but glad I will be able to use my main cpu in the future. Thank you both for the help.
Sent from my VS980 4G using Tapatalk