I am a n00b and trying to use the AutoRoot v2.5 and I get to this point every time:
"Rooting...
Looking for Root...
Restarting ADB Server...
*daemon not running. starting it now on port 5037*
*daemon started successfully*
Failed to get a root shell, please restart your phone and try again
Press any key to exit"
If anyone could help me figure out what I am doing wrong I would greatly appreciate it.
Related
Hi all,
My phone was previously rooted, and I was following the guide from the dev forums about how to upgrade to GB, but the KD1 rom that was ODIN'd wasn't rooted. Now when I try to use SuperOneClick to root, I'm getting a message right at the top that says that Check Drivers...FAILED. At the bottom of the output from SuperOneClick I get a message that rooting failed.
I've tried using multiple different versions of SuperOneClick, from 1.7 up to 2.2.1. I've tried uninstalling and reinstalling the USB drivers for the Galaxy S 4G, but these are the same drivers that I had before. Has anyone else had this problem?
It's pretty frustrating, since now I'm stuck with a non-rooted phone and I can't find any other way to root it.
Thanks for any help!
total output from super one click
here's the total output from superoneclick...there's a ton of "invalid argument" messages in there
SuperOneClick v2.1.1.0
Checking drivers...
Failed
Killing ADB Server...
* server not running *
OK 0.04s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.08s
Waiting for device...
OK 0.04s
Checking if rooted...
False
OK 0.13s
Getting manufacturer...
turer
/system/bin/getprop: line 1: ?????toolbox???????: Invalid argument
OK 0.03s
Getting model...
odel
/system/bin/getprop: line 1: ?????toolbox???????: Invalid argument
OK 0.02s
Getting version...
ental
/system/bin/getprop: line 1: ?????toolbox???????: Invalid argument
OK 0.03s
Rooting device... - Step #1
1883 KB/s (585731 bytes in 0.303s)
OK 0.38s
Rooting device... - Step #2
euter
/system/bin/chmod: line 1: ?????toolbox???????: Invalid argument
OK 0.04s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
/bin/sh: ./psneuter: Permission denied
FAILED
Once you Odin the Kc1 that's in FB's GB starter you'll have exerting you need
Sent from my SGH-T959V using xda premium
Yeah, try to get into download mode and see if ODIN recognizes your device, if it does, something could be wrong with superoneclick, but a quick work-around would be just flashing another stock rom like the kc1 which comes pre-rooted. If it doesn't recognize your device, try a new usb cord.
How to get into download mode without root?
The problem is how to get into download mode without root? My understanding is that I have to be in download mode to use ODIN. Apparently the KC1 image that I ODIN'd as part of the GB Starter Pack guide wasn't rooted, and now I can't get root. I've tried going into download mode through using the 3 button trick, through using quick boot, and through using CWM, but no love.
You dont need root to get into download mofe. To get into download mode you turn the phone off then hold down the volume up and volume down at the same time and while doing that plug in your USB cable.
Sent from my SGH-T959V using xda premium
THANK YOU
YAY! Thanks, that's exactly what I needed. Thanks for taking mercy on a noob.
Like the title says I need help rooting this phone. It's a 2.3.5 Gingerbread Android version.
I tried SuperOneClick but the program stops responding after:
"Killing ADB Server"
"Starting ADB Server"
*daemon not running. starting now on port 5037*
*daemon started successfully*
After that...nothing. Just freezes.
I also tried DoomLord's ZergRush Root but I get the same "Daemon started successfully* and nothing after that.
USB debugging is turned on.
Any help would be appreciated. Thanks in advance.
Hi man, have you succeeded in the meantime to root this phone. I've got the same issue and need the help!
Hey everyone, i know this is kind of a newbie question. but after looking on the internet and i cant seem to find the solution to a problem i have been working on for a few days now
I downloaded the Motochopper to root my device and when i press enter it says:
Daemon not started. Daemon started using port 507
Daemon run sucessfully.
Then it just sits there.
I know my usb debugging is on im not sure why it gets stuck here.
Any help would be greatly appreciated! thank you so much!
I would try installing the drivers again.
attkstrpure said:
Hey everyone, i know this is kind of a newbie question. but after looking on the internet and i cant seem to find the solution to a problem i have been working on for a few days now
I downloaded the Motochopper to root my device and when i press enter it says:
Daemon not started. Daemon started using port 507
Daemon run sucessfully.
Then it just sits there.
I know my usb debugging is on im not sure why it gets stuck here.
Any help would be greatly appreciated! thank you so much!
Click to expand...
Click to collapse
Looks like you need the proper ADB drivers. You can find them on Motorola's site or I think you can now use Koush's new Universal ADB drivers for all android devices. Report back after installing the drivers
Sent from my XT925 using xda app-developers app
Hello hello! Just looking for some help rooting my LG G2 (Verizon edition).
I'm trying to use the method posted by thecubed, which can be found here http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
I have all of the drivers installed and the phone is recognized in the adb but whenever I run the root.bat file in adb I get the following errors:
Looking for device...
Error: protocol fault (status read)
Determining carrier...
Error: more than one device and emulator
GOTO was unexpected at this time
I've rebooted both my PC and phone, only have my phone plugged in via usb and am still getting these errors. Other posts have talked about these problems, but the solutions either didn't work or didn't seem to apply to this case. Any suggestions or pointers would be appreciated, hopefully this isn't the worst question in the world...
Cheers,
Rich
Hello
rcdurand said:
Hello hello! Just looking for some help rooting my LG G2 (Verizon edition).
I'm trying to use the method posted by thecubed, which can be found here http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
I have all of the drivers installed and the phone is recognized in the adb but whenever I run the root.bat file in adb I get the following errors:
Looking for device...
Error: protocol fault (status read)
Determining carrier...
Error: more than one device and emulator
GOTO was unexpected at this time
I've rebooted both my PC and phone, only have my phone plugged in via usb and am still getting these errors. Other posts have talked about these problems, but the solutions either didn't work or didn't seem to apply to this case. Any suggestions or pointers would be appreciated, hopefully this isn't the worst question in the world...
Cheers,
Rich
Click to expand...
Click to collapse
Try this..... http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/ ..... Just remember to follow all the instructions to the letter. Good luck!
Thanks for that, I'll give it a shot in the morning! Really getting frustrated with having the verizon update notification flashing in my face all the time, scared I might actually hit it one of these times!
Well the one click method didn't work either, continually gets stuck at starting server :/
rcdurand said:
Well the one click method didn't work either, continually gets stuck at starting server :/
Click to expand...
Click to collapse
What's the output of "adb devices"? For what it's worth, I had done the OTA first and was still able to root using this method.
I'm having the exact same issue with my AT&T G2. Did you ever get yours working?
rcdurand said:
Hello hello! Just looking for some help rooting my LG G2 (Verizon edition).
I'm trying to use the method posted by thecubed, which can be found here http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
I have all of the drivers installed and the phone is recognized in the adb but whenever I run the root.bat file in adb I get the following errors:
Looking for device...
Error: protocol fault (status read)
Determining carrier...
Error: more than one device and emulator
GOTO was unexpected at this time
I've rebooted both my PC and phone, only have my phone plugged in via usb and am still getting these errors. Other posts have talked about these problems, but the solutions either didn't work or didn't seem to apply to this case. Any suggestions or pointers would be appreciated, hopefully this isn't the worst question in the world...
Cheers,
Rich
Click to expand...
Click to collapse
Issue with root file stuck
I follow the directions to root to the letter. I have repeated issue multiple times so I know there is some issue preventing this on PC or device.
I get to step of running the root batch file. CMD opens, press key to continue.
I get:
Looking for device...
* daemon not running. starting it now on port 5037*
* daemon started successfully*
_ --- then next line just blinks indefinitely.
This through standard driver software installation that pops up when device connected.
When phone was connected I selected "for internet" --> "Ethernet" as it is a Verizon LG G2 and I noticed someone had made that distinction in one set of instructions. When doing so, phone notes that "entering into USB Debugging" so I would be led to believe that is correct.
Any suggestions or thoughts on this? Have looked around and found nothing in terms of this issue on forums, nothing specific to this issue or similar to this. I have seen issues with those driver installations for other devices but the fix usually consisted of a toolkit for that devices root with the fix built in so little help there...HELP
you could try this, it's worked
http://theunlockr.com/2013/10/25/root-lg-g2-versions-video/
Hello XDADevs,
I had previously experienced boot issues after installing the ARHD 21 ROM on my wife's phone, only to find out that I was flashing the wrong ROM. I switched to ARHD 11.2 and was making better progress, when I started getting errors after hitting the 'HTC One Powered by Android' splash screen. The errors being "Unfortunately, the process com.android.systemui has stopped" popping up every time I tapped OK. The screen would then go blank and would not turn on again, though I could tell the phone was running when I pressed the volume buttons.
Using CWM recovery, I cleared all the caches I could find and re-installed the ROM. This time, phone boots to a blank screen, no responses. Was told by @Captain_Throwback that I needed to be using the TWRP recovery image, so while in CWM(because that was the only way I could interact with my phone via adb) I loaded the TWRP image.
Now, I cannot open Recovery, and cannot interact with my phone. Tried different methods of trying to connect, with no positive results.
C:\Minimal ADB and Fastboot>adb kill-server
C:\Minimal ADB and Fastboot>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Minimal ADB and Fastboot>
This was my first time unlocking, rooting, and flashing a ROM on any device. I used SunShine to unlock and S-Off, loaded SuperSU(everything was fine), then after that I tried loading ARHD 21, which is when all the trouble started.
All I wanted to do was to make my wife's phone work better after porting this phone from Verizon to T-Mobile by changing the band frequencies from CDMA to GSM.
So now that my recovery is not working, how can I connect my phone to the computer again to get this to work?
Hi,
I see you've already been in discussions about this in the rom thread. And that is exactly the thread you should be asking for help in.
Please note the sticky from the top of this section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
XDA Assist is here to help members navigate the site, not for support.
Thank you for understanding. Thread closed.