• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Guide] Root for Official 2.3.5 With Guide

Edit1: Yes, and Yes. Edit 2: I did look in the downloads folder too, lol! I got worried and was like "what the heck?"

I think I may have figured out what happened though, and I apologize for omitting this information: Basically, the phone is on Simple Mobile. Not sure if that has to do with anything.

But the real omitted comment is that when I first booted into recovery, I selected Wipe* (Factory Reset) and let it sit for like 5 minutes....nothing was happening, and I thought the process got stuck, so I pulled the battery (I never had a wipe ever take that long on any other device I've owned)....afterwords, when it rebooted, some app icons said "SD" but when I went to click them, they said "not installed on device", so basically I just went to the market and reinstalled them all (after I reinstalled the market)

I even had to reenter my data settings for Simple Mobile. Otherwise, everything remained the same.

After that, THEN I tried to flash a ROM, and CWM did not see them. Maybe the partial wipe had something to do with it? I didn't even know the phone was still wiping.......5 minutes later?


It can take that long and That could definitely play a factor in your issue. I would try to start all over again once you get it back up and see what happens.

Geeve
 
It can take that long and That could definitely play a factor in your issue. I would try to start all over again once you get it back up and see what happens.

Geeve

So you mean redo the root process? That won't break the device? I never ran a root twice...is that safe?
 
So you mean redo the root process? That won't break the device? I never ran a root twice...is that safe?

What I am saying is do the factory reset and let it finish and if once that is done see if you still have root, if so cool if not reroot. And reflash the corn kernel. There is really no telling what was wiped and what wasn't. That is the only thing I can think to do and it's what I would do. In fact if I could get it all the way back to when I bought it and let it reformat and all that good time consuming crap. I'd go that route. Tha's just me though, a clean slate sometimes is the best way, But I don't mind taking it to 2.1, then to 2.2 then 2.35 if need be. May not be your cup of tea though.

When I made this guide, I was rooted already and took the screen shots as I basically rooted again. Had no ill effects.

Geeve
 
Awesome, I should have been more patient, I just got freaked when I noticed the wiping taking forever :(

Okay, now I know. Thank you for all of your help, I appreciate it!

What I am saying is do the factory reset and let it finish and if once that is done see if you still have root, if so cool if not reroot. And reflash the corn kernel. There is really no telling what was wiped and what wasn't. That is the only thing I can think to do and it's what I would do. In fact if I could get it all the way back to when I bought it and let it reformat and all that good time consuming crap. I'd go that route. Tha's just me though, a clean slate sometimes is the best way, But I don't mind taking it to 2.1, then to 2.2 then 2.35 if need be. May not be your cup of tea though.

When I made this guide, I was rooted already and took the screen shots as I basically rooted again. Had no ill effects.

Geeve
 
updated and rooted. easy to do. However, went into sgs tools to test root and simply changed startup and shutdown sound to off. got superuser granted permission however it does not mute sounds.
 
thanks geeve420 -
your step by step instructions r great.
i lost root on my captivate when i upgraded from froyo to gingerbread.
read a lot of forums before i found ur posting.
was a bit apprehensive since i would have to flash uckk4 - had never done any roms previously. worked great though. thanks for your great instructions.
 
updated and rooted. easy to do. However, went into sgs tools to test root and simply changed startup and shutdown sound to off. got superuser granted permission however it does not mute sounds.

Did you go to the market and update Superuser and install busybox?

Geeve
 
Ok, i followed this guide and did the first step, and now it wont load,, it will show samsung... then a very looks like pixelized screen and tries to load the galaxy s screen but freezes then resets and goes back to samsung screen..

Help!!
 
I followed the procedure, but at the end, no su binary was present.

Went through it again - same result.

Next I did the first step (AutoRoot) and at that point, su is there, and works.
Then loaded the KK4 kernel again - no su binary.

I did notice that as it booted the KK$ kernel there is a (yellow) set of messages about applying updates. Don't know if it is supposed to do this or not? Looked at /sdcard, there was an old update.zip there, so removed it and tried again.

After AutoRoot - su works.

After loading KK4 kernel, no su is present.

Anyone have any ideas what is going on?
 
I followed the procedure, but at the end, no su binary was present.

Went through it again - same result.

Next I did the first step (AutoRoot) and at that point, su is there, and works.
Then loaded the KK4 kernel again - no su binary.

I did notice that as it booted the KK$ kernel there is a (yellow) set of messages about applying updates. Don't know if it is supposed to do this or not? Looked at /sdcard, there was an old update.zip there, so removed it and tried again.

After AutoRoot - su works.

After loading KK4 kernel, no su is present.

Anyone have any ideas what is going on?


After you flash back you have to go to the market and update superuser and install busybox. That may solve some of your issue. If not let us know and we will go from there.

Geeve
 
Tried - complains that the phone is not rooted...

After AutoRoot there is an su binary in /system/xbin.

After loading KK4, there is no su binary.
You can't install busybox without su.

SuperUser shows as installed.
Uninstall, reinstall.

No su present (still) - not surprising, because /system is mounted ro.

Run the Superuser app, and click "Su binary vnull" to check for updates.
It finds a "legacy" version.

Click "Update"

Looks for busybox and fails to find it, so uses custom busybox, looks for current install path - of course, there isn't one, and no installed binary, so update fails.

How do people end up with an su binary after loading KK4???
It obviously overwrites whatever is in /system...

------

After loading AutoRoot, re-installed busybox -- all the links to busybox and su binary are in /system/xbin.

Flash KK4 and all that we have is:

$ ls -l /system/xbin
-rwxr-xr-x root shell 13936 2011-11-17 11:58 iqbridged
-rwxr-xr-x root shell 60276 2011-11-17 11:58 dexdump

I don't understand how others get things left in xbin and I don't ...
 
After AutoRoot there is an su binary in /system/xbin.

After loading KK4, there is no su binary.
You can't install busybox without su.

SuperUser shows as installed.
Uninstall, reinstall.

No su present (still) - not surprising, because /system is mounted ro.

Run the Superuser app, and click "Su binary vnull" to check for updates.
It finds a "legacy" version.

Click "Update"

Looks for busybox and fails to find it, so uses custom busybox, looks for current install path - of course, there isn't one, and no installed binary, so update fails.

How do people end up with an su binary after loading KK4???
It obviously overwrites whatever is in /system...

------

After loading AutoRoot, re-installed busybox -- all the links to busybox and su binary are in /system/xbin.

Flash KK4 and all that we have is:

$ ls -l /system/xbin
-rwxr-xr-x root shell 13936 2011-11-17 11:58 iqbridged
-rwxr-xr-x root shell 60276 2011-11-17 11:58 dexdump

I don't understand how others get things left in xbin and I don't ...


Very interesting, you can check my other guide as well. You may have better luck using corn kernel. Let me do some digging. Got me curious now.

Geeve
 
Got it!

The problem was that the links for KK4 are to THE ENTIRE AT&T DISTRIBUTION.

Loading that (obviously) overwrites everything.

You need to load JUST THE KERNEL. I found a download which was just the kernel -- hint, if the KK4 load takes more than a few seconds, you have the complete distro, not just the kernel!
 
Got it!

The problem was that the links for KK4 are to THE ENTIRE AT&T DISTRIBUTION.

Loading that (obviously) overwrites everything.

You need to load JUST THE KERNEL. I found a download which was just the kernel -- hint, if the KK4 load takes more than a few seconds, you have the complete distro, not just the kernel!


Weird, I just went back to complete stock and used the downloads from the first post (LIKE THE GUIDE SAYS TO DO) and had no issues what so ever rooting. The kk4 zip In the first post is in fact just the kernel. Not real sure where the disconnect is.

Geeve
 
Just wanted to say thanks for the easy to follow instructions. Captivate now once again rooted! My only hiccup was getting in the Download mode correctly. Method 3 definitely was more consistent for me as well. Thanks!
 
Here are my details:
I have a Samsung Captivate i897. I recently used mini-Kies to maunually update to Gingerbread 2.3.5. I first used your guide here to root it using the kk4 kernel, which CWM doesn't recognize. I went through the steps listed in the guide again and used the Corn Kernel found at "http://forum.xda-developers.com/showthread.php?t=1294477", (version: CornKernel_UCKK4_v705.tar), in place of the KK4 stock kernel and flashed it to the phone using Odin.

I see the Corn kernel loading page when the phone starts up. Going to Settings > About Phone I've confirmed:
Firmware version: 2.3.5
Baseband version: I897UCKK4
Kernel version: 2.6.35.7-I897UCKK4-CORNv705
Build number: GINGERBREAD.UCKK4

Mornin' Geeve,

So a quick thanks once more for all of the root and back up data. I had a quick question though, are you or anyone else who is using the Corn kernel 7.05 seeing their device randomly lock? Now that I've got the Captivate rooted, it runs really well, but about once or twice a day, it will lock up and I have to cycle the power to clear the problem. It almost always happens when I am texting someone.

Any recommendations on possible fixes?


Thanks!

Allen.
 
Mornin' Geeve,

So a quick thanks once more for all of the root and back up data. I had a quick question though, are you or anyone else who is using the Corn kernel 7.05 seeing their device randomly lock? Now that I've got the Captivate rooted, it runs really well, but about once or twice a day, it will lock up and I have to cycle the power to clear the problem. It almost always happens when I am texting someone.

Any recommendations on possible fixes?


Thanks!

Allen.

Personally I have not had any lock ups at all, but then again I was getting random reboots with 7.06 and some folks weren't. You can try a different version and see if it clears ups for you. Here is the link to the Corn Kernel page at XDA:

[KERNEL][KK4][1/28/11] Corn Kernel v7.06 from Source (OC, BLN, Voodoo Sound, etc.)! - xda-developers

May have a poke around over there and see what others are saying :)

Geeve
 
Personally I have not had any lock ups at all, but then again I was getting random reboots with 7.06 and some folks weren't. You can try a different version and see if it clears ups for you. Here is the link to the Corn Kernel page at XDA:

[KERNEL][KK4][1/28/11] Corn Kernel v7.06 from Source (OC, BLN, Voodoo Sound, etc.)! - xda-developers

May have a poke around over there and see what others are saying :)

Geeve

I'll give 7.06 a go and let you know how it works out for me. Everything else has been great and the phone seems snappier, though that may just be a placebo effect; so to speak.

Much thanks for the help and your responsiveness. It is much appreciated!

Allen.
 
I'll give 7.06 a go and let you know how it works out for me. Everything else has been great and the phone seems snappier, though that may just be a placebo effect; so to speak.

Much thanks for the help and your responsiveness. It is much appreciated!

Allen.

My pleasure anytime and let us know!

Geeve
 
This was awesome. It works perfectly if you just follow the instructions. I extracted the downloads to the desktop for easy access.
 
Back
Top Bottom