I must say that you are the ****ing man geeve420! Just updated my phone today to 2.3.5 from a rooted 2.2 AT&T Captivate. I was so pissed to see I no longer had root access. Honestly dude, your directions were, for me at least, easier to follow than using OneClickRoot! Hahaha... smoke on my brother and keep up the awesome work!
I can"t tell you how paranoid I was to do this with such a new release from AT&T. Very simple to do, just follow the instructions. I am an old non techie sort, THANKS a lot !!!!!
Holy Crap. I tried other root methods for about 4 hours today. Including a super "one click" option. Approximately 1,000 clicks later, I was ready to throw my computer down the stairs. Thanks for such an easy root option.
Geeve I just want to thank you a ton! I am a total noob. I don't even have my captivate yet (it will arrive tomorrow) but I have probably put in about 40 hours reading up on all this stuff. I was about ready to completely give up if it weren't for you and a few posters over at xda. This is by far the best guide I have come across. After I went through this thread a few times everything else started clicking. I am really confident now. Already sent a thanks your way!
Last edited by hapifrapicapi; February 13th, 2012 at 12:27 AM.
CWM from the market will not work with 2.3.5 captivate, it won't recognize your device, and it is way behind in version. You need to flash a kernal that has it infused. I use corn kernel which has CWM 5 already in it. I will post link when I get back to a PC
I use V7.05 because 7.06 was giving me random reboots. Flash this using Odin like the root guide tells you (put it in the PDA slot) only replace my downloads with the Corn Kernel, once you flash it on there, there is no need to flash back to stock Kernel. So just one flash of the Corn Kernel and you will have CWM Recovery installed.
Geeve
Edit 2: You can root as well with this Kernel once flashed, it is in the advanced options, I won't get in to that here though.
Geeve, I'm a little confused, sorry like I said i'm a noob.
In your instructions above did you mean that one should use the corn kernel in place of the other custom kernel (the one in the download you provided) if you want to get CWM - OR- did you mean that we should follow the guide to achieve root then after getting root use the same method from above to flash the Corn Kernel to get CWM? Just want to make sure I get this right. Thanks!
Last edited by hapifrapicapi; February 13th, 2012 at 01:45 AM.
Geeve, I'm a little confused, sorry like I said i'm a noob.
In your instructions above did you mean that one should use the corn kernel in place of the other custom kernel (the one in the download you provided) if you want to get CWM - OR- did you mean that we should follow the guide to achieve root then after getting root use the same method from above to flash the Corn Kernel to get CWM? Just want to make sure I get this right. Thanks!
If you want CWM flash the corn kernel. Open up Odin, put the corn kernal tar file in the PDA slot and flash away. If you flash the corn kernel there is no need to flash back to the stock kernel. Corn kernel can run your phone.
There is another guide to do this in the root section. You can just skip the root part of that guide, if you do this root method first.
If you want CWM flash the corn kernel. Open up Odin, put the corn kernal tar file in the PDA slot and flash away. If you flash the corn kernel there is no need to flash back to the stock kernel. Corn kernel can run your phone.
There is another guide to do this in the root section. You can just skip the root part of that guide.
I tried to root using ur instructions but instead i got the dreaded "phone-triangle-computer" thing. After sum fixing, i tried again figuring it was a bad flash.... Same thing. So i tried 8 more times and kept getting the same "phone-triangle-computer" sign on my phone! Please help...
I tried to root using ur instructions but instead i got the dreaded "phone-triangle-computer" thing. After sum fixing, i tried again figuring it was a bad flash.... Same thing. So i tried 8 more times and kept getting the same "phone-triangle-computer" sign on my phone! Please help...
Quote:
Originally Posted by Jonathansk
I have a problem, did what your instructions say....the flash went well, but its not rooted. What am i doing wrong?
1) Dizzle: looking into it, I have not had the problem and can't reproduce it. You are on 2.3.5 correct?
2) Jonathan: After the flashes you downloaded busybox and updated superuser? May try to reflash as well.
Geeve
Last edited by geeve420; February 16th, 2012 at 10:19 AM.
Thanks to Geeves for the great instructions! I'm a newbie. I still can't get the hotspot to work. AT&T still blocking it from enabling wifi. What apps do I need to make this work?
man this worked flawless im not the most phone savvy person out there and i did it first time without any kinks i do own a rooted custom rom'd phone but i had someone else do it and it looked easy so i tried it and it was so super easy thnx a bunch
Very cool! I am not real familar with the Heimdall set up. If you can make a step by step for this I will add it to the orignal guide, just in case we have some Linux Folks out there or just folks that prefer Heimdall That would be really helpful.
Geeve
I'm pretty much uncomfortable with anything that isn't a command line. I like to know every command that is being run. So, I used the Heimdall CLI 1.3.1 tool on my Mac to root my Captivate.
The paths below assume you put the contents of the zip files into directories named accordingly, and that your android SDK was expanded right in your Downloads directory...
Downloads/android-sdk-macosx/platform-tools/adb reboot download
sudo heimdall flash --pit Downloads/flashing/captivate.pit --kernel Downloads/flashing/I897UCKF1-AutoRoot-DesignGears/zImage
Downloads/android-sdk-macosx/platform-tools/adb reboot download
sudo heimdall flash --pit Downloads/flashing/captivate.pit --kernel Downloads/flashing/KK4_stock_kernel/zImage
I'm pretty much uncomfortable with anything that isn't a command line. I like to know every command that is being run. So, I used the Heimdall CLI 1.3.1 tool on my Mac to root my Captivate.
The paths below assume you put the contents of the zip files into directories named accordingly, and that your android SDK was expanded right in your Downloads directory...
Downloads/android-sdk-macosx/platform-tools/adb reboot download
sudo heimdall flash --pit Downloads/flashing/captivate.pit --kernel Downloads/flashing/I897UCKF1-AutoRoot-DesignGears/zImage
Downloads/android-sdk-macosx/platform-tools/adb reboot download
sudo heimdall flash --pit Downloads/flashing/captivate.pit --kernel Downloads/flashing/KK4_stock_kernel/zImage
This worked for me and rooted my phone. After rooting my wifi would not search for networks. I would turn on wifi and it would say scanning for about 15 seconds then turn itself off. I unrooted the phone did a factory data reset and wiped my phones internal sd. Wifi still wont work. HELP?
yes, i have 2.3.5 on my cappy, kk4 as well. im thinking it might b the odin im using... i had previously had another version on my pc. would there be conflict if both were installed on my pc?
1) Dizzle: looking into it, I have not had the problem and can't reproduce it. You are on 2.3.5 correct?
Geeve
ok, think i may have found sumthing... odin isnt able to c my phone when i connect it. Its in dl mode and even makes the auditory sound when it is connected but it wont recognize it. It doesnt seem to b able to see it at all!!!
ok, think i may have found sumthing... odin isnt able to c my phone when i connect it. Its in dl mode and even makes the auditory sound when it is connected but it wont recognize it. It doesnt seem to b able to see it at all!!!
Sounds like drivers to me. I would uninstall and reinstall any samsung drivers (kiess is easy way to get the drivers). remove Odin for the time being to, just till you get the PC to see your phone.
Thanks man. I flashed (anyone else sort of feel like Chuck when saying that?) the gears kernel and it rooted but it no longer detected wifi networks. So I flashed the K4 kernel instead, that seems to have fixed the issue.
Now what's the best way to get rid of bloatware?
Thanks to anyone that helps me out.
Thanks man. I flashed (anyone else sort of feel like Chuck when saying that?) the gears kernel and it rooted but it no longer detected wifi networks. So I flashed the K4 kernel instead, that seems to have fixed the issue.
Now what's the best way to get rid of bloatware?
Thanks to anyone that helps me out.
Yeah the gears kernel was not built to run the phone, just push the root files. That's why in the guide I have you flash the stock kernel again.
Titanium backup is your friend for uninstalling bloatware
Geeve
The Following User Says Thank You to geeve420 For This Useful Post:
I am running Windows 7 Ultimate x64 and the process fails everytime on the first step with the PDA process. The write fails. Is this a Windows 64 bit issue? I installed the 64 bit usb drivers prior so I have those correct.
Thanks in advance
I resolved my own question. I am a Systems Administrator and have more computers than sense! I grabbed another laptop, loaded the same OS (Windows 7 Ultimate) but this time the 32bit (x86) version and the process worked without even a hiccup! So..... there we have it. This process does not seem to like 64bit Windows OS.
Last edited by jperry58; February 20th, 2012 at 11:30 PM.
Reason: Resolved
I am running Windows 7 Ultimate x64 and the process fails everytime on the first step with the PDA process. The write fails. Is this a Windows 64 bit issue? I installed the 64 bit usb drivers prior so I have those correct.
Thanks in advance
I resolved my own question. I am a Systems Administrator and have more computers than sense! I grabbed another laptop, loaded the same OS (Windows 7 Ultimate) but this time the 32bit (x86) version and the process worked without even a hiccup! So..... there we have it. This process does not seem to like 64bit Windows OS.
I must be an exception, All I have is W7 64bit home editions at home and I have never had a problem. I know there are some folks who have trouble with 64 bit though.
I've noticed that since I rooted I've gotten the tethering manager error somewhat more frequently, is there a way to fix this? I recall seeing somewhere that once rooted you could delete the tethering manager; would that remove my ability to tether?
I've noticed that since I rooted I've gotten the tethering manager error somewhat more frequently, is there a way to fix this? I recall seeing somewhere that once rooted you could delete the tethering manager; would that remove my ability to tether?
I don't tether but maybe someone can answer that, to get rid of it though you can freeze it or uninstall it with Titanium backup.
you can try a factory reset to get rid of the error as well. back your stuff up first and you will not lose root.
Back on the first or second page there was a person with with issues as well. I gave some tips on things to try.
***What worked for them was to actually follow the guide again. Could have just been a bad flash. *****
Go back to the first page and read, I don't really remember what I had them do and I am not at a PC. Let us know.
We will get ya going though, one way or another
Geeve
Mornin' folks,
Here are my current device details:
Firmware version: 2.3.5
Baseband version: I897UCKK4
Kernel version: 2.6.35.7-I897UCKK4-CORNv706
Build number: GINGERBREAD.UCKK4
I did have a locking problem, back on page 2 with Corn Kernel v7.05. Specifically the phone would randomly and completely freeze up on me. I'd have to pop the battery out and cold boot it to clear the error. On v7.05 it was happening 1 to 2 times a day.
I tried to reflash it with Odin, but that didn't work, so I flashed it up to v7.06. That helped to mitigate the issue a bit. It still locks up on me, but it only happens once every 2 or 3 days. Given the way it is acting I'm beginning to suspect that a memory leak is involved. I'm currently considering backing up the precious stuff and loading Cyanogen on it to see what happens.
I'll let you know how it goes.
Cannot begin to thank you enough for the effort that went into creating this guide. Excellent job, and it worked perfectly. Now if I could find the same step by step clear instructions to move from 2.3.5 to ICS I'd be in heaven. :-)
Cannot begin to thank you enough for the effort that went into creating this guide. Excellent job, and it worked perfectly. Now if I could find the same step by step clear instructions to move from 2.3.5 to ICS I'd be in heaven. :-)
DCM
I concur it would be awesome if you could show us how to put ICS on it.
Sounds like drivers to me. I would uninstall and reinstall any samsung drivers (kiess is easy way to get the drivers). remove Odin for the time being to, just till you get the PC to see your phone.
Geeve
reinstalled all drivers on pc from samsung website. the problem isnt with my pc not seeing my phone... it sees it just fine. its just odin that wont pick it up... AT ALL! n e suggestions? i really, REALLY want this damn thing rooted again... please help!
ps i used one click heimdall to fix the phone the first time, when it first failed and went to the famous "phone-triangle-pc" screen. it was the only way i could revive it. did that bout 7 times cuz i kept trying n trying...
Cannot begin to thank you enough for the effort that went into creating this guide. Excellent job, and it worked perfectly. Now if I could find the same step by step clear instructions to move from 2.3.5 to ICS I'd be in heaven. :-)
DCM
Quote:
Originally Posted by greatnessinc
I concur it would be awesome if you could show us how to put ICS on it.
I have the files downloaded, may try to make a guide this weekend.
Geeve
The Following 2 Users Say Thank You to geeve420 For This Useful Post:
reinstalled all drivers on pc from samsung website. the problem isnt with my pc not seeing my phone... it sees it just fine. its just odin that wont pick it up... AT ALL! n e suggestions? i really, REALLY want this damn thing rooted again... please help!
ps i used one click heimdall to fix the phone the first time, when it first failed and went to the famous "phone-triangle-pc" screen. it was the only way i could revive it. did that bout 7 times cuz i kept trying n trying...
That is some weird stuff! I am at a loss. You could try to redownload Odin, maybe a bad DL. Try a different USB port, or another PC. That is about all I can come up with for this.
reinstalled all drivers on pc from samsung website. the problem isnt with my pc not seeing my phone... it sees it just fine. its just odin that wont pick it up... AT ALL! n e suggestions? i really, REALLY want this damn thing rooted again... please help!
ps i used one click heimdall to fix the phone the first time, when it first failed and went to the famous "phone-triangle-pc" screen. it was the only way i could revive it. did that bout 7 times cuz i kept trying n trying...
I was wondering if you had ODIN running first before you put your phone into "download mode". I remember being caught by this pretty bad.
The Following User Says Thank You to typicalnuser For This Useful Post:
Cannot begin to thank you enough for the effort that went into creating this guide. Excellent job, and it worked perfectly. Now if I could find the same step by step clear instructions to move from 2.3.5 to ICS I'd be in heaven. :-)
DCM
Quote:
Originally Posted by greatnessinc
I concur it would be awesome if you could show us how to put ICS on it.
First time post i got the files and it doesnt show them as .tar files. Odin will not accept them and gives and "Check images" error when i try to start with them. please help!!!!
First time post i got the files and it doesnt show them as .tar files. Odin will not accept them and gives and "Check images" error when i try to start with them. please help!!!!
When you unzip them the .tar files should be there.
Download the files, unzip them, inside the unzipped file is the .tar file you need for Odin.
Geeve
Last edited by geeve420; February 24th, 2012 at 07:35 PM.
The Samsung Captivate is AT&T's version of the Samsung Galaxy S, marking Samsung's first strong push into high-end Android territory. The manufacturer simultaneously launched the Galaxy S on every major American carrier, each reta... Read More