please i want to ask some few questions.
How can i root my samsung galaxy s and be free of complications? i have tried the z4root once and it wasnt able
to root my device........is there anythin i did wrong? i just copied the apk file to the internal memory of the
phone and clicked on root n it started but along the way the phone hanged and i had to put it off and on and
the device was still the same unrooted
Is there any one click method that i can use like the application
z4root and how exactly can i use it cos i have read conflicting guides on how to use some of these one click apps
If i successfully root my samsung galaxy s can i still be eligible for updates? presently i have 2.1 eclair
installed and my kies tells me that i can update the firmware but my internet connection is very very slow and
i have tried like 4 times and cant update thru kies cos the network always times out. please is there any other
safe method of upgrading? i have actually read about odin but dont really get the guidelines straight.
from what I have heard z4 has a habit to hang. At least on the SGS model I have *Samsung Mesmerize*
It will hang once. Pull Battery to reboot and run again. It should take 2nd time.
No clue why .. just seems to be the case.
You know for sure its rooted if afterwards there is a APP called Superuser in your app drawer.
SuperoneClick seems to hang for me also .. Z4 has been the most surefire way I have seen.
Not sure of eligibility or Kies .. Probably have to unroot at least for update then root again. As for Kies I am in the States and not available here.
thanks for the reply
well, am so glad for ur reply. I have tried twice and it hanged ...........i also saw in a post that debugging has to be on. is it necessary to do it with or without a sim card and please how long did it take u to root urs cos mine stays almost 2 hours b4 hanging and i leave it another two hours before putting it off. I havent tried pulling the battery and rebooting and when it hangs i just leave it and dont even try it that same day again.
I will try it out the way u said n see if it will work out. Thanks again for ur reply
As mentioned before z4 will hang, sometimes it needs to be done a few times. It will definitely work on Galaxy S using Android 2.1 but it apparently won't root it successfully on Android 2.2 (Rogers at least, I'm not sure about AT&T).
Click to root and if it doesn't complete within 15 minutes then pull the battery, restart and try again. Do it until it roots, it will work. Don't wait 2 hours, there's no point and there's no harm in pulling the battery.
If you have Android 2.2 you'll probably need SuperOneClick.
EDIT: You have to be using USB Debugging and you can have a SIM card in there.
thanks a lot again i will continue doing it until it roots ...................glad i have someone that can help...........will still get back to u
SuperOneClick will work and i highly recommend it. It can also hang but if you follow these steps you will be fine.
Enable USB Debugging on your device.
Connect device to PC (do not mount USB)
Make sure drivers have installed. (check device manager)
Turn device off
Run SuperOneClick and select 'Root'
When you see 'waiting for device..' , turn device on and wait.
The program should run through until the end now without any further intervention. Congrats, you are rooted!
In this state, (rooted with stock ROM), you will still be able to receive OTA updates. If you want to go furthur, perhaps try a custom ROM or two, i suggest installing Rom Manager from the market. With that you can flash a custom recovery, back-up your entire device (nandroid), and then proceed to flashing a custom ROM. (In that order!)
Just remember that once you have a custom recovery in place you will no longer be able to receive OTA updates. If you have gone ahead and tried it you can always roll back by re-installing your nandroid backup. (Once you are back to your stock ROM a restart will put you back to stock recovery again too).
Hope this helps.
please DirkGently1, i really appreciate ur reply to my post but i am confused on some certain areas
1 Connect devive to PC (do not mount USB)
please what do u mean by do not mounth usb ? do u mean do not mount memory card or something am not getting
2 for the drivers, i already have kies and use it with my galaxy s and i believe the drivers should already be installed ..........else i need to install them again
3 does turn device off device mean the galaxy s should be turned off after it has been already connected to the pc cos ur 2nd step said connect device to pc
please am sorry for asking more questions .............just that am still not very clear on the super one root method. Thanks for your cooperation
Hi mate,
When you connect to PC you will see a new icon in the notification bar. When you pull the bar down you will see the notification 'USB connected' or something similar. Click on the notification and it will give you the option to 'mount USB'. Just ignore it!
I'm not sure what kies is? As long as your PC recognises your phone when it is plugged in you are ok.
Connect the phone to the PC via USB cable with USB Debugging enabled on the phone so that the PC 'sees' it. Then turn it off. Only turn it back on once SuperOneClick is running, 'root' selected and 'waiting for device..' comes up on the PC.
It's easier than it sounds. Good luck my friend.
thanks again for the clearification ...................will give it a try if zroot cant root my galaxy s
ok i have tried it but finally succeded after a lot of unplugging and plugging usb and clicking on debugging but i was asked if i wanted to test and i clicked yes and it stuck on the testing
this is what i got
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
9 KB/s (5392 bytes in 0.584s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/stl9
OK
Remounting system with read-write access...
OK
Pushing su...
231 KB/s (26264 bytes in 0.111s)
OK
chmod su...
OK
Pushing Superuser.apk...
376 KB/s (196521 bytes in 0.510s)
OK
Remounting system with read-only access...
OK
Running a SU test...
it seems not to finish running the SU test, am i rooted?
I'm not sure I haven't used this method, but check your app drawer for the superuser app, if it's there you're rooted
With z4 when the phone reboots, you tried to reopen it? the phone should ask you to give permission to Superuser you click "accept"
yes there is super user ap in my drawer. so how do i speed up my device now that am rooted
First get titanium backup to backup all your stuff then I guess you could go check out oclf (one click lag fix) to speed up the phone. Check out the captivate forum though, there's plenty of suggestions and help in there too. Congrats on the root.
thanks again on the tip i already have titanium backup and its saying my phone isnt rooted............its the only app saying that i wouldnt know why
You have to make sure you allow it root access when you first start the application. If you don't it will tell you that it's not being given root access. Also if you did z4 root did you temp or permanent root it? If you only temp rooted that will go away when you restart your phone. We'll need some more details here.
This is what you're looking for, I have done this myself (Captivate) and it worked perfectly
i didnt get the zroot 2 work 4 me so i used superoneclick and have rebooted a lot of times and still have root access to other apps its still the titanuim backup that is still different
Try opening your superuser app and check if titanium backup was denied root access or not. What does it say in there?
From my captivate to you.
Rooting
Hi Mate, Im not 100% sure, but I think Rageinthecage is a virus. Kasperskys says it is. be careful!
Hi there,
I have a problem and seems all the threads i found are not helpful....
I have a asus transformer (B50), stock Android 3.2, I've unrootet it from
prime 1.7 using ADB for copy blob file, while tablet was turned on in normal mode.
Here is what makes me sick: I see my device in ADB as long as it's not in APX mode. When i boot my device in APX mode (I use System-Profiler to check if it's really there) then the list of devices is empty.
alex$ sudo ./adb kill-server
alex$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
alex$
The same at my Vista PC... device is in APX but not visible for adb...
I used CWM to unroot and install prime, but I don't want to use it again...
Any more ideas? Would be great if someone could help me on that.
thx.
so my tf300 is rooted and unlocked bootloader, im trying to do the disabling journaling
im already at twrp and my tablet is connected to my pc
but everytime im trying the adb shell it says:
daemon could not start, starting at port 5037
daemon started succesfully
error: device not found
what seems to be the problem here? i tried to install my sdk, still no luck.
Using USBDeview (suggested here - comment 7 : http://code.google.com/p/android/issues/detail?id=2676 ) helped me get my TF300 to appear under 'adb devices'.
Still can't seem to access the device via localhost though.
(I'm trying to get access for web-dev purposes - see here : http://forum.xda-developers.com/showthread.php?t=1966358 )
Hello
I'm trying to run a shell session but getting this error message
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Ok, it seems obvious what the problem is but I can't find a solution
The phone is plugged, Fastboot seems to recognise the connexion as says fastboot USB
HBOOT version 1.14
Not sure what to do
Any idea?
Many thanks
EDIT Problem Solved - should launch from Recovery - Thank you
I don't image the adb command is able to access that sector of the device but for the record, when I connect, I can see the device but
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb kill-server
C:\Users\Brad2\Downloads\adbUnzip2Cdrive\adb>adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully *
List of devices attached
51cfe754 offline
I can connect to the device with Odin in download mode, but I do not see a 'pull' or extract feature on Odin, only push.
What is the trick to extracting the boot files from the device? All drivers and sdks are installed and using the current adb.