Hi,
I own a Samsung Galaxy S2/ GT-I9000
Android: 2.3.3
Baseband: I9100XXKDJ
Kernel Version: 2.6.35.7-I9100XWKDD-CL161513
[email protected] #2
I wanted to root the phone and i have followed this thread to the letter: [Guide] And then there was ROOT.
So i did everything;
-I flashed the kernel (XWKDD) succesfully.
-Phone reboots.
-Opening SuperOneClick; pressing ROOT. (phone still connected)
...And then it just does nothing.
It hangs @: Waiting for device.
As soon as I try to click something, like minimize window, it stops responding.
My device is in debugging-mode (as required for ODIN, reboot -> Still debug, so that's not the problem).
I'm really out of answers..
I don't know how to get it working..
Remember, i followed everything by the letter..
Until the root-part with superoneclick... It just won't let me...
Anyone got any answers?
---Bump---
Topic-saver
Sent from my GT-I9100 using XDA App
Bumpin again.
Sent from my GT-I9100 using XDA App
BryanNL said:
Bumpin again.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Why not post this issue on the SuperOneClick thread? Get the latest version of SuperOneClick then try again. I think they just fixed something major.
theo80 said:
Why not post this issue on the SuperOneClick thread? Get the latest version of SuperOneClick then try again. I think they just fixed something major.
Click to expand...
Click to collapse
Will try. Thanks.
Sent from my GT-I9100 using XDA App
Getting latest version of SuperOneClick doesn't change anything. I still can't root my phone
Sent from my GT-I9100 using XDA App
It happen to me the same
open the superoneclick, with the USB debugging off, when the
superoneclick says waiting for device you turn USB debugging on.
and it works
ah, i forgot!!! Install the previous version of superoneclick.
I install the version 1.9.5 i think, and yes its old but it works
Great news. -1Day roots AT&T Motorola Atrix4G!!! YAY!
11/29/2010:
I'm sorry I haven't been updating lately!!! The problem is, I no longer have an Android phone and I can't play around or test anymore. I'm going to see if I can find one on craiglist or ebay.
11/10/2010:
I finally figured out how to root without looping. After rooting 13 phones, this is how I did it on the first try.
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
All BEFORE it says "Waiting for device..." again
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=803682
Related
I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?
What drivers did you install? And yes, I read the "fastboot devices"
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App
yup.. it is in volume up + on mode.
If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.
melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.
Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App
I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App
Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"
I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App
Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.
Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?
I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App
Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)
Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App
melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.
Hi guys. I'm totally new at this rooting and all. I tried rooting my Galaxy S II so heres what happened.
I used Odin v1.85 and that worked out perfectly. But when i used SuperOneClick v2.1.1 to root afterwards, it goes up to "waiting for device" and hangs out and the next thing i see is that the SuperOneClick is not responding. I have all the things required like .NET Framework 2.0/Samsung Kies 2.0
I also had no choice cause i dont have any SD card in my phone to try the other process.
I would really appreciate it if you guys could help me out here. Thanks
Check out your phone specific threads. There should be step by step guides there
jdbeitz said:
Check out your phone specific threads. There should be step by step guides there
Click to expand...
Click to collapse
Well I've tried this guide but sadly, like always, gets stuck in "waiting for device" and then not responding and then I have to force close SuperOneClick
SmR12 said:
Well I've tried this guide but sadly, like always, gets stuck in "waiting for device" and then not responding and then I have to force close SuperOneClick
Click to expand...
Click to collapse
uninstall super one click then try flashing with ODIN.
Ensure you have USB debugging enabled.
Sent from my SCH-I510 using Tapatalk
Make sure:
a. Kies is installed but not running
b. USB debugging is on (Settings>Applications>Development)
Well, Kies is installed and USB Debugging Mode is on. But still it does not work. I have done all things step by step but doesn't work.
Will flashing with Odin do the same thing (I mean like rooting) ?
Maybe your USB drivers need updating. KIES has the option to update drivers - or you can download drive and app from PDAnet.
With your phone plugged in to USB (debugging on), can you -adb devices- and see your phone? If not the you have a driver problem.
With the drivers fixed everything else should work for rooting the device.
Sent from my GT-P1000 using XDA App
Start from the beginning if all else fails...
Flash to stock with Odin, make sure you have the correct drivers installed and debugging mode is active. Then try super one click again... If that fails again, try tonroot manually by reinstalling the update.zip package
what android version is your phone running?
afaik gingerbread cannot be rooted, only froyo
Im sorry guys im a total newbie at this. Can u pls tell me how to "adb devices" to see my phone?
Sent from my GT-I9100 using XDA App
Update: I did the adb devices and they could not find my phone. Any suggestions ?
sweetnsour said:
what android version is your phone running?
afaik gingerbread cannot be rooted, only froyo
Click to expand...
Click to collapse
My phone's running on 2.3.3 gingerbread. If this cannot be rooted then why is there a guide to it ? :S
Sent from my GT-I9100 using XDA App
Im using the revolutionary method i get my beta key.
when i run the program it type in my beta key, and it accepts it and the comes up with ''zerging root. . . this might take a minute or so. . .'' but nothing happens and it stays like this. is it supposed to boot into bootloader or something? i have usb debugging enabled. and im on htc sync mode.
Did you install USB driver on rev site? Happenned to me when I try rooting it.
Sent from my HTC Sensation 4G using XDA Premium App
Shouldn't be in Sync mode, just connect it in charging mode
Ive tried what both of you have suggested but its still the same? is usb debugging supposed to be on or off?
USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300
EddyOS said:
USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
Thats the guide im following and its not working. My galaxy s2 was a piece of cake to install a custom rom on
it works perfectly up to the point when i type in the beta key? which i know im doing it correctly.
it just hangs there? also when i boot into fastboot it has ***LOCKED*** at the top in pink, so does this mean i need to unlock my bootloader first?
No, it gets replaced with 'Revolutionary' once done.
Try a different USB port/PC
Just calm down and take a break, then re read the instruction. You must miss something
Sent from my HTC Sensation 4G using XDA Premium App
still no luck, and i have no idea why accept this sort of thing always happens to me ive managed to root a desire z in the past so this shouldnt be a problem on my laptop because it worked fine before?
This what comes up
We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator
dav08094194 said:
This what comes up
Click to expand...
Click to collapse
Your phone gonna reboot into HBoot a few time to get root. Are you seeing your phone reboots?
Sent from my HTC Sensation 4G using XDA Premium App
EddyOS said:
We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator
Click to expand...
Click to collapse
Yeah windows 7 and ive tried all 3 usb ports. not sure what DOS Prompt is but im running the program as administrator anyway.
Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights
EddyOS said:
Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights
Click to expand...
Click to collapse
got it to work in the end. i had to install windows 7 on my linux ubuntu pc
Hi there,
I was trying to change the splashscreen with use of adb, when i tried to reboot into bootloader the error devices not found poped up, i thought well no worries ill do it myself then. When in fastboot usb mode it still doesn't find it. things u tried:
usb mode by recovery
usb mode by fastboot
normal usb at homescreen
charging mode
htc sync mode
i did check usb debugging and it was checked
i run OrDriod 2.0.1(2.0.2 in a couple of min) FW 3.32 bricked 0.65 kernel
------------------------------------------------------------------------------------------------
i can only check this question again later tonight.. (gst 1+) so ni about 4 to 5 hours.
use this instead. Much easier and friendly
http://forum.xda-developers.com/showthread.php?t=794638
azzledazzle said:
use this instead. Much easier and friendly
http://forum.xda-developers.com/showthread.php?t=794638
Click to expand...
Click to collapse
+1 on you but i need it for other things to like superCID/making superCID undone...
i did try adb that comes with sdk stuff...
Arrrr i see.
Well dowload ADB again, make sure drivers are upto date, Make sure ADB is in the correct location. And always make sure the commands are correct.
azzledazzle said:
Arrrr i see.
Well dowload ADB again, make sure drivers are upto date, Make sure ADB is in the correct location. And always make sure the commands are correct.
Click to expand...
Click to collapse
check,check,check
if adb devices gives nothing and adb reboot bootloader neither then i guess it doesnt lie down to my adb drivers, since i used them before my laptop just randomly blanked itsself and i needed to get everthing up and running again
You got USB Debugging checked ??
azzledazzle said:
You got USB Debugging checked ??
Click to expand...
Click to collapse
myself said:
Hi ...
htc sync mode
i did check usb debugging and it was checked
i run OrDriod 2.0.1(2.0.2 in a couple of min) FW 3.32 bricked 0.65 kernel
Click to expand...
Click to collapse
that must say it?
haha sorry i didnt read that bit lol....
azzledazzle said:
haha sorry i didnt read that bit lol....
Click to expand...
Click to collapse
np i just need it working again since that flash tool for splash screen doesnt work ether
android flasher works perfect , I was using it less than 10 mins ago....
ADB not working - Android flasher not working ... Seems like some issue with your PC / Drivers
azzledazzle said:
android flasher works perfect , I was using it less than 10 mins ago....
ADB not working - Android flasher not working ... Seems like some issue with your PC / Drivers
Click to expand...
Click to collapse
i thought more of the phone
Possibly,, But providing USB debugging is checked, And there seem to be no other faults / problems with the phone, I cant figure out what could be causing this ?? On the phones part i mean.
Damn i really need adb fixed got a kinda ride splash screen and every watches my screen...
Sent from my Sensation using xda premium
ADB is in the right location yeah ?
what error does android flasher give (if any)
Non just cant go further then starting the daemon srrver because there is no phone connected in fastboot usb mode xD
Sent from my Sensation using xda premium
did you uncheck the 'im already in fastboot' box on android flasher ?
Yes as well as check if devices are connected by adb was non
Sent from my Sensation using xda premium
Hmmmmm. Very strange.
What OS do you have on your PC ?
Btw updated to 2.0.2 with 0.7 bricked kernel
Sent from my Sensation using xda premium
Windows 7 64 bit
Sent from my Sensation using xda premium
I posted this before but didn't get much response and I still have this problem. I rooted my phone using the 1.85 method, and am currently rooted, but not unlocked. I've tried to unlock the bootloader, but since device manager does not detect the device I can't unlock it. The phone charges when connected to the PC (IO panel, not front), but the connection type does not appear in the notification pull-down, and device manager does not display the device. This wasn't true before rooting, and now that my PC can't detect the phone I can't unlock and I can't copy over files from my PC to my phone. I have current drivers successfully installed, and I haven't updated any software beyond stock on my phone (1.85, 4.0.3), though AT&T has tried to push an update on my phone this morning.
How can I solve my problem? This is my first Android phone, and I wanted to unlock the bootloader to be able to flash ROMs and develop my own, but at the moment it isn't possible.
Yarok said:
I posted this before but didn't get much response and I still have this problem. I rooted my phone using the 1.85 method, and am currently rooted, but not unlocked. I've tried to unlock the bootloader, but since device manager does not detect the device I can't unlock it. The phone charges when connected to the PC (IO panel, not front), but the connection type does not appear in the notification pull-down, and device manager does not display the device. This wasn't true before rooting, and now that my PC can't detect the phone I can't unlock and I can't copy over files from my PC to my phone. I have current drivers successfully installed, and I haven't updated any software beyond stock on my phone (1.85, 4.0.3), though AT&T has tried to push an update on my phone this morning.
How can I solve my problem? This is my first Android phone, and I wanted to unlock the bootloader to be able to flash ROMs and develop my own, but at the moment it isn't possible.
Click to expand...
Click to collapse
Did you turn on usb debugging? And after you connect ur phone did you try adb to see if your phone is detected
Sent from my HTC One X using xda premium
abhipati said:
Did you turn on usb debugging? And after you connect ur phone did you try adb to see if your phone is detected
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, USB debugging is on. I tried adb using this guide (http :// www . thesuperusersguide . com/adb-backup--restore.html sorry can't post links), but once I paste in “adb backup –apk –shared –all –f /backup/mybackup.ab," I get back adb: unable to connect for backup."
Yarok said:
Yes, USB debugging is on. I tried adb using this guide (http :// www . thesuperusersguide . com/adb-backup--restore.html sorry can't post links), but once I paste in “adb backup –apk –shared –all –f /backup/mybackup.ab," I get back adb: unable to connect for backup."
Click to expand...
Click to collapse
When you type adb devices, what do u get output
Sent from my HTC One X using xda premium
In 1.85, there was the option to default your connection type. It may be set to charge only. Check your settings. This may be the issue.
abhipati said:
When you type adb devices, what do u get output
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
XNine said:
In 1.85, there was the option to default your connection type. It may be set to charge only. Check your settings. This may be the issue.
Click to expand...
Click to collapse
As it seems the USB port I was using wasn't connected properly to the motherboard, so I had to do some tinkering there. It all worked out though*, thanks for the help.
*Except that I accidentally installed the OTA update instead of postponing it and removing notifications... Now begins the wait for a 2.23 root method. Woe is me.