Database Info

[Q] [n00b]

sorry guys, despite my stupid slow connection i have to open a new thread.
i got my defy few days ago. i still cant get it rooted. can anyone please help me to do it?
i have:
all the drivers needed,
rsd lite 4.3
super one click 1.7 and 2.1
z4root
my defy is from singapore with 2.51 and bootloader 09.10.
seriously can any one help me. super one click got stuck. z4root got FC. god i need help.

have you tried this post ? here

arixal said:
have you tried this post ? here
Click to expand...
Click to collapse
tried, still no use. trying to flash uk stock rom and try again. sigh..

SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
adb server is out of date. killing...
OK
Pushing rageagainstthecage...
adb server is out of date. killing...
OK
chmod rageagainstthecage...
adb server is out of date. killing...
OK
Running rageagainstthecage...
adb server is out of date. killing...
FAILED
============================================
what does it really happened?
already flash uk roms.
almost tried everything. but still the same.

You need to use this version http://forum.xda-developers.com/showthread.php?t=913709
Make sure you have Debugging turned on and on mode "None" or "ChargeOnly" connected to the PC.
Then you must have RSDLite 4.9 that you can get here http://forum.xda-developers.com/showthread.php?t=853674

edition- said:
You need to use this version http://forum.xda-developers.com/showthread.php?t=913709
Make sure you have Debugging turned on and on mode "None" or "ChargeOnly" connected to the PC.
Then you must have RSDLite 4.9 that you can get here http://forum.xda-developers.com/showthread.php?t=853674
Click to expand...
Click to collapse
tried. still the same. been using super one click, z4root, universal androot. all the same
even when i try to connect using adb to do manual root, adb hardly detected my device. anyway i'm on win7 pro.
it keeps reinstalling drivers whenever i change into whichever mode on the usb mode.
seriously bro, whats the matter.
whats the latest universal androot version anyway. i'm using v1.6.2b5.
hope someone encountered this and successfully rooted can help me with this.
originally i'm from SEA rom without blur. now i'm on GB (uk) rom with blur.
i suppose what sbf should i flash for vulnerability the secure for defy?

I think the only way to root it is thru superoneclick 2.21 that we posted

edition- said:
I think the only way to root it is thru superoneclick 2.21 that we posted
Click to expand...
Click to collapse
still cant get it

limkoksoon said:
still cant get it
Click to expand...
Click to collapse
If you want help plz post EXACTLY what you have done yet and where you stuck...
Like this:
- start up phone
- attached USB Cable
- turned debugging on
- ....
and so on

ok, this might light things up..
what version of motorola driver are you currently using?
because yesterday I tried to root my defy using super1click with moto driver 4.7 in my win xp laptop.. always failed becaused it always waiting for ADB server (my defy won't install adb driver in the xp laptop.. )
than I downloaded the motorola driver ver. 5.0 at motodev here you have to register, but it's free anyway..
and then I tried to root it using the new driver in a different laptop using win 7 32bit.. and it works..
should also be working in windows xp since I assume the main problem is the motorola driver

32-bit driver:
http://ifile.it/zfct95b/Motorola_End_User_Driver_Installation_5.0.0_32bit.msi
64-bit driver:
http://ifile.it/lzx8hmf/Motorola_End_User_Driver_Installation_5.0.0_64bit.msi

No Root

Hello All: I am heping my daughter put a custom ROM on her sidekick but I am really stuck in step 1. Shemessed it up and I did the ODIN recovery method to restore it back to usable. Now I am trying to use superoneclick to root it...I put the drivers on like 4 times and I have triple checked that there is USB debugging turned on. Plugged in the phone, launched surperoneclick 2.2 and click root. The program gives me " killing ADB server" then "starting ADB server" and then nothing...
Its not rooted, but nothing else is happening. Any guesses as to what I did wrong. Thanks in advance!

What your going to want to do is ODIN to KG2 , there are thread's in this section to help you . Once you do that reboot your PC & phone then enable usb-debugging then open up superOneClick & select psneutar exploit then it'l do it for you .
Sent from my SGH-T839 using XDA App

kj2 no longer exists
Anyone have kj2 odin tar file that I can use. The link on the dev page takes you to a dead link.

http://www.multiupload.com/0JGFMKW8CQ
enjoy , just uploaded it , it include's updated superoneclick for root also .

Sorry to be a pest
except the file I really need is kj2.tar.md5 or kj2.tar I have all the other compoenents.

Go get Kies from Samsung and update your device yourself. After that, root your phone.
Use Google to solve the where and how questions.
That saves us all time and trouble.

GPM Odin to KG2 then root & cwm then flash a rom .
Sent from my SGH-T839 using XDA App

good

Downgrade SuperOneClick
I had the same problem, and I fixed it by using an older version of SuperOneClick, It also made it so that clockwork recovery couldn't recognize the file system, and to fix that I just booted into the forced (red) mode of clockwork and it all worked from there.

[Q] I can't root my phone with ANY TOOLs..

First, this problem is not common question..
My phone is TAKE(EV-S100), I think there's no one who has this phone if there is no Korean who is reading this thread..(?)
I could root my phone when it was froyo, but when I upgraded my phone to gingerbread(2.3.4), it doesn't root with any tools.
I tried SuperOneClick all versions, zergRush, update.zip and boot.img.
Result is:
SuperOneClick : Step #7 : waiting for device
with adb.exe of phones upgrade folder : Step #7, but not responding..
zergRush : There's no progress after *daemon started successfully*
update.zip : There's no information for my phone but I tried droid's root-update.zip, but eocd error and signature error.
boot.img : when I enter bootloader mode (I could do adb reboot bootloader), then the driver what named 'kroid' but not installed, can't find driver.. so when I enter "fastboot boot boot.img", prompt says "waiting for device"
If someone can resolve this problem, please answer..
I believe my phone can be rooted someday..
Please understand if I wrote wrong grammer.
I'm not American and I studying English but I'm clumsy English yet..(?)

Same problem to me any one can us.............
Thanks ..................
Masud-GSM

This might help
Masud-GSM said:
Same problem to me any one can us.............
Thanks ..................
Masud-GSM
Click to expand...
Click to collapse
After reading through some of the development forums I found that I did not have my phone in internet connection mode with the usb attached. It needs to be on this mode in order to run anything. If you have that running not sure what else it might be. I have been able to troubleshoot alot by looking through the devo forums for my phone.

root GT-P5100 4.0.4 with heimdall

confirmed root wit heimdall and P5100 with stock 4.0.4 ! i
( used arch linux and heimdall 1.3.2 )
I am not to be held responsible for any damage this may do to your device
*not for newbies*
1. install heimdall http://forum.xda-developers.com/showthread.php?t=755265
2.download cwm-root-gtab2.zip http://goo.gl/WkRQy ,Galaxy Tab 2 GT-P5100.tar http://goo.gl/pwBvp
3.coppy cwm-root-gtab2.zip on externalSD
4.unzip Galaxy Tab 2 GT-P5100.tar (recovery.img) , cd to extracted tar
5.turn off tab ,push power+volume-up to get download mode , connect usb to tab
6.open konsole and run " heimdall flash --recovery recovery.img --no-reboot " (--no-reboot very important)
7.when finnished dont reboot ,straight from the "download" screen press volume down and power hold and wait to samsung logo shows then release only power button ,hold volume down until CWM6 loaded .
8.go to install zip from externalsd find cwm-root-gtab2.zip and flash
9.when finnished reboot device and when asked for "stock reboot fix" press yes.
you are rooted !
for windows you can try unchek reboot option !?
i tryed kang rom and cm10 both worked fine !

Sounds nice. Should give it a try. Any preferences for installing under windows

dehein said:
Sounds nice. Should give it a try. Any preferences for installing under windows
Click to expand...
Click to collapse
i dont run windows , cant say nothing about it ? if you run win. then use odin , but i dont have experience with it ?
and didn try gui for heimdall i prefer konsole,

Can you assist? I keep getting one of two errors:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to receive response!
or
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file "recovery.img"
Any advice?

xavier2k3 said:
Can you assist? I keep getting one of two errors:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to receive response!
or
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file "recovery.img"
Any advice?
Click to expand...
Click to collapse
Check md5sum and what version of heimdall you use ? Strange i roted 4 p5100 without errors .
Sent from my GT-I9100 using xda premium

I keep getting this error.
please help
Failed to detect compatible download-mode device.
Also, this is a new device running 4.0.4
I run linux mint on an imac

Michael61182 said:
I keep getting this error.
please help
Failed to detect compatible download-mode device.
Also, this is a new device running 4.0.4
I run linux mint on an imac
Click to expand...
Click to collapse
I'm not sure, but maybe you need android udev rules -> https://github.com/M0Rf30/android-udev-rules

it's working perfectly

i get this.. and i don't know what this error is?
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12

BrownGhost said:
i get this.. and i don't know what this error is?
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Click to expand...
Click to collapse
from Driver->zadig install samsung driver when connected

raressh said:
from Driver->zadig install samsung driver when connected
Click to expand...
Click to collapse
I uninstall samsung drivers.
then i use zadig, then i see it found the tablet, but before i can do anything ****ty samsung drivers update and installs them self again, and its gone and im back to, not seeing the tablet GRRRRR
I try to uninstall samsung drivers, with delete, and no internet, dissablet wifi.. but its still they always tak over the zadig drivers stay only 10-15 secounds.. im on windowws 7...
man what a nightmare, 3 days ive been trying every single gude i can find, himedal, odin, this and that, nothing works, simply cannot connect to the tablet in download mode...

BrownGhost said:
I uninstall samsung drivers.
then i use zadig, then i see it found the tablet, but before i can do anything ****ty samsung drivers update and installs them self again, and its gone and im back to, not seeing the tablet GRRRRR
I try to uninstall samsung drivers, with delete, and no internet, dissablet wifi.. but its still they always tak over the zadig drivers stay only 10-15 secounds.. im on windowws 7...
man what a nightmare, 3 days ive been trying every single gude i can find, himedal, odin, this and that, nothing works, simply cannot connect to the tablet in download mode...
Click to expand...
Click to collapse
ddon't uninstall the samsung drivers. only install the one from zadig over it. you should exit keis before and it should work

heimdall dont work, but after ive done the install of the other drivers ODIN works.. Cool now i finally can root the thing..
Done, and now running [ROM][GT-P51XX][JB][4.1.2] CyanogenMod 10 official nightly builds )
Thanks

[Q] LG G2 Root

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/