Database Info

[HOW-TO] Get a rooted version of EE4

I thought I'd collect together instructions from a few threads to help people get from stock EE4 to a rooted version. While the instructions will be consolidated, I will be linking back to the original threads for software downloads, so that people will always be getting the latest versions from those threads.
Assumptions
You are running stock EE4 (I'll address getting to this state in another post if I need to, but the only reason for this is that we're flashing the ROM via Clockwork Mod, which I don't think will update the baseband radio for you if it's not already at EE4).
You are on a Windows system (because that's the drivers and software I'll be pointing you to - the basic concepts will be the same for other operating systems.
Preliminary
Download the Droid Charge Windows drivers here and install them.
Download Odin on to your computer from here or here.
Download the version of Clockwork Mod (CWM) Recovery you want to load and put it somewhere on your computer you can remember. Check nitsuj17's post here for the current choices, but as of June 13th, 2011, imnuts's version here was the only choice for a bug free EE4 experience.
Download the rooted kernel you would like to use to get you root access, and put it somewhere on your phone's SD card. Check nitsuj17's post here for the current choices, but as of June 13th, 2011, imnuts's PeanutButta Jelly Time kernel seems to work without requiring an SD card fix. This recommendation is only slightly influenced by the fact I'm eating honey chipotle peanuts while writing this. Choose either a Voodoo lagfix or non-lagfix version. The Voodoo lagfix should be faster, but will require you to convert back if you want to go back to stock. Here's an explanation of what the Voodoo lagfix is. (though this isn't a Galaxy S phone, it's the same concept).
{Optional} Download the ROM you would like to use (if you want to load one) and put it on your phone's SD card (as well as any other fixed files the ROM author posted). Do this if 1) you want a deodexed ROM that can load custom system-wide themes (as opposed to Launcher themes), and/or 2) you would like a ROM that has the bloatware removed already, and/or 3) you would like whatever other improvements the ROM authors added. Again, check nitsuj17's post here for the current choices, but as of June 13th, 2011, the best options for EE4 are either the stock ROM that has been deodexed, GummyCHARGED 1.5, or imnut's EE4 Debloated 4.2.1 ROM. [These are all ROMs installed with CWM, so the instructions below will apply to that scenario, but you may run across a ROM that is installed via Odin. Just install those the same way you are being instructed to install CWM.]
Potentially, you could install a pre-rooted ROM and be able to skip the kernel instead.
As a safety precaution, download the file in this thread and save to your phone in case you have problems with your SD Card because of your new kernel.
Installing CWM using Odin
Shut down your phone and make sure it is unplugged from your computer.
Pull the battery out of your phone.
Make sure all applications are shut down and Antivirus is disabled, and run Odin on your computer.
Plug your phone in to your computer.
Hold the Down volume button until the large yellow triangle downloading screen appears. The first thin rectangle in the upper left of the ODIN applicate should also turn yellow and identify a com port. You can now release the volume key.
Uncheck the box in Odin that says "Auto Reboot".
*For this next part, make sure you are using the PDA button, NOT the Phone button, or you'll hurt your phone* Check the box next to PDA in Odin, and click the PDA button.
Navigate to the .tar.md5 file for CWM you downloaded (probably something like New_CWM_Recovery.tar.md5) and Open it.
Now you should be showing your phone connected to a Com port, Auto Reboot is unchecked, and you have selected the CWM file you want to load, so click the Start button.
In Odin, it should show the download progress, briefly flash a blue "Restart", then show a green "Pass". If it doesn't, try again, and if it repeatedly fails, try the following:
Mine was seeming to lose power and shut off halfway through, and here's how I fixed it. After Odin was loaded on the PC and the phone was in download mode, but before I started the flash, I inserted the battery. This kept the phone on through the process and it succeeded.
Try a different USB port (some people claim the back USB port works better for them, but that's very computer dependent).
If you're on a laptop, make sure it is plugged in. Try a desktop if it continues to fail.
Try a different USB cable.
Make sure Odin is the only software running, and antivirus is disabled!
Redownload the Odin package, it may be corrupt.
Redownload the ROM/kernel/recovery, it may be corrupt.
Shutdown your phone by disconnecting it (and removing the battery if you had to install it for troubleshooting).
If you need visual instructions for running Odin, there are excellent ones here, just make sure to uncheck the auto-reboot box.
At this point, you should have CWM installed, so now let's install your rooted kernel.
Installing kernel through CWM
Boot in to recovery by holding down the Home key, the Up volume key, and the power button. After you see "SAMSUNG" you can let go of the power button, but continue to hold the home key and up volume until you are in recovery.
In CWM, navigate up and down using the volume keys, select using the power key, and go back a menu using the back key.
Select "install zip from sdcard".
Select "choose zip from sdcard".
Find and select your kernel's .zip file
Repeat the above steps, but this time choose the SD Card fix file you downloaded.
Install your ROM
If you decided to install a new ROM as well, you have a couple of extra steps.
Select "wipe data/factory reset".
Select "Yes -- delete all user data".
Go back using the back key.
Select "install zip from sdcard".
Select "choose zip from sdcard".
Find and select your ROM's .zip file.
If needed, install any other fixes the ROM author posted (for instance, Gummy comes with an Exchange Email fix you need to load).
At this point, reboot and you should be all set. If you chose a lagfix kernel, it will take a while to reboot while it converts your file system. You will hear an electronic female voice detailing what is going on while this is happening.
If you are having problems accessing your SDCard with a custom kernel, please follow the instructions in this post.
Thanks to nitsuj17 for maintaining a list of dev work for the Charge, to imnuts, kejar31, and jt1134 for awesome dev work, and to DroidXcon for dev work and the awesome Odin instructions.

Reserving one post, just in case.

Nice clear and to the point write up. This for sure should help alot of folks out getting themselves to a EE4 build that has root access. Nice job!!!!

Just a FYI, I was on EE4 debloated and went to a stock EE4 deodexed for personal reasons. Needless to say, my sdcard is locked out from CWR because I forgot to install the sdcard fix before rebooting recovery - that step is probably necessary for people going with that ROM (I tried the adb commands in the kernel post, but I'm getting an error "unmount command not found" or something like that). Superuser also was wiped out, but a download from Market takes care of that.
I do have the yellow CWR and PBJT kernel installed before I flashed the stock deodexed ROM. When I get home I'm going to start over with ODIN on stock rooted ED1.

binglejellsx2 said:
Just a FYI, I was on EE4 debloated and went to a stock EE4 deodexed for personal reasons. Needless to say, my sdcard is locked out from CWR because I forgot to install the sdcard fix before rebooting recovery - that step is probably necessary for people going with that ROM (I tried the adb commands in the kernel post, but I'm getting an error "unmount command not found" or something like that). Superuser also was wiped out, but a download from Market takes care of that.
I do have the yellow CWR and PBJT kernel installed before I flashed the stock deodexed ROM. When I get home I'm going to start over with ODIN on stock rooted ED1.
Click to expand...
Click to collapse
Thanks for the info, I hadn't tested that!

So I followed the above instructions to a T on flashing New_CWM_Recovery, which worked fine, and then I installed PBJT's Voodoo kernel, which also worked fine. I rebooted and ran Quadrant, and my score went from 950 on stock EE4 to 1700 with the Voodoo kernel, so it definitely installed. However when I try to go into Titanium Backup it is telling me that I don't have root access. Root Explorer also won't let me mount as R/W anymore. I have Superuser installed. I am relatively new to all of this and could use some help. Any ideas on what is happening?

chadness said:
...for the current choices, but as of June 13th, 2011, imnuts's PeanutButta Jelly Time kernel seems to work without requiring an SD card fix. This recommendation is only slightly influenced by the fact I'm eating honey chipotle peanuts while writing this. ...
Click to expand...
Click to collapse
Just FYI, started with stock EE4 and ended up still having to use the SD Card fix to get around some weird read/write issues. Not sure if it was in read only more, but my mac wasn't recognizing the SD card when in mass storage mode. Installed the fix via CWM and everything worked like a charm. This was immediately after installing PBJTime.
Cheers!

Thanks!
Chadness you are the awesomeness
I've rooted before when I had an Incredible, but was a little leery rooting my charge since I've never used Odin before. Your guide lays out all the steps and was very easy to follow. Thanks a bunch!

underscored said:
Just FYI, started with stock EE4 and ended up still having to use the SD Card fix to get around some weird read/write issues. Not sure if it was in read only more, but my mac wasn't recognizing the SD card when in mass storage mode. Installed the fix via CWM and everything worked like a charm. This was immediately after installing PBJTime.
Cheers!
Click to expand...
Click to collapse
Thanks for the report. I think I'll rewrite to have people install that just in case.

zeuswsu said:
Chadness you are the awesomeness
I've rooted before when I had an Incredible, but was a little leery rooting my charge since I've never used Odin before. Your guide lays out all the steps and was very easy to follow. Thanks a bunch!
Click to expand...
Click to collapse
No problem. I hadn't used a Samsung and hadn't had to use Odin before, either. Not too bad once it's laid out, but that program can be touchy!

I rooted with Odin straight from EE4 stock to imnuts's CWM and then the Peanut Butta kernel and didn't have any trouble with the SD card. Now to just decide what rom to put on it...
Edit: Ok, nevermind...my SD card shows up on my computer as a cd drive...so, now to fix it.

I'm going to close this one as we currently have http://forum.xda-developers.com/showthread.php?t=1121201 in General.

[how-to] alternate ways to get cwm

i have seen a number of 3e and cwm questions and they are reasonable questions and and the community support is good but what many people don't seem to realize is that the whole 3e recovery mod and rom manager method is only one way to get to cwm. and there are other variations on 3e such as truselos batch script for 3e that he wrote for the captivate but i wont get into that because i will explain how to bypass the 3e and rom manager steps altogether.
our goal here is to get cwm recovery as it is the preferred way to flash many things. because voodoo kernels have cwm baked in and many have scripts that root the phone we can flash a voodoo kernel from methods other than cwm.
BEFORE YOU START decide if you want to do the voodoo lagfix conversion[takes a long time], you can put a empty file or folder named "disable-lagfix" in a folder labeled Voodoo(capital V is important) on the sdcard before you start if you don't want to use the lagfix now. the path should look like /sdcard/Voodoo/disable-lagfix
or from windows <insert drive letter here>:\Voodoo\disable-lagfix
option 1
flash a kernel built off of gtg's community kernel sources via odin/heimdall. gtg's kernel and his sources have root built in. no root is required. just install superuser app from the market after the flash if you dont plan to flash a rom or just flash the rooted rom of your choice in red cwm. gtg's kernel can be found here
http://forum.xda-developers.com/showthread.php?t=1119598
to do this you will need a computer with odin or heimdall (heimdall on mac/linux doesnt require drivers) and drivers(installed with samsung kies). you can get odin with the unbrick packages from gtg, it is in the .zip these are good to have ready if you do something stupid.
http://forum.xda-developers.com/showthread.php?t=1116251 (original firmware)
http://forum.xda-developers.com/showthread.php?t=1112555 (ota updated firmware, rooted)
heimdall for all platforms including windows can be found here
http://forum.xda-developers.com/showthread.php?t=758296
kies can be downloaded from samsungs oversees sites as well as random places on the internet, the captivate drivers for kies mini may work as well, that is in the support downloads section of the samsung us website
1 once kies and therefore the drivers are installed make sure it is not running in the system tray.
2 open the odin .exe as administrator and place the voodoo enabled kernel file of your choice(should be .tar or .tar.md5 format) in the pda slot. [for heimdall extract the zimage from the .tar and put it in the kernel slot]
3 put phone in download mode and connect it to the computer [hold vol up+vol dn +plug in the data cable]
4 hit start
it takes about 3 seconds then the phone reboots and voodoo conversion starts(unless you disabled it) and may take 20 minutes, you will here voices
if you have driver trouble that you cant pin down [ugh windows ] with odin this might not be the option for you as i don't plan on remotely diagnosing everyones windows problems in this thread, there are other members that might so ask but don't expect too much from me, good thing there is another option.
option 2
root phone then flash via sgs kernel flasher or other root app with kernel flashing capabilities (galaxy tuner also works, there may be others) i recommend sgs kernel flasher for its backup capability
you will need drivers[windows only-install kies] and a computer with superoneclick or lost1's scripts
http://forum.xda-developers.com/showthread.php?t=1082247
super one click root is cross platform but depends on other 3rd party software to run on certain os's so i recomend lost1's shell scripts for linux/mac users. his batch script works great for windows as well.
http://forum.xda-developers.com/showthread.php?t=1081072
1. [windows users]install drivers if applicable
2. root phone, refer to the thread that contains your root method. [all methods are insanely easy]
3. install sgs kernel flasher from the market. it is free
4. download voodoo kernel of your choice to the phone (can even be in cwm flashable format, infact it can extract the kernel out of the rom .zip you will flash later, only one download is needed if you do this. the app is pretty smart)
5. backup the stock kernel in sgs kernel flasher[optional] then select "choose kernel" and navigate to the location of the download.
keep auto rebooot selected
6. choose "flash kernel" the phone will reboot and start the voodoo conversion(unless you disabled it). it will talk to you during the conversion, you are not crazy. the process takes up to 20 minutes.
i know my instructions are redundant. some people only need the explanation, some get the step by step, i find a few people learn better if they get both. if the wordiness is a distraction for you, i never said i was a writer

Nice job!
Now if we can just get them to look at it. Possibly make sticky?

people are viewing it they just havent left comments.
it's not as complicated as it might sound, when i helped people do the odin method on captivates i always got comments like "wow, easiest rom flash ever" especially if it was after restoring from a brick because you didnt have to log into google to install rom manager(not aplicable on the infuse but people on the captivate had a habit of using master clear in odinoneclick which cleared the update.zip and all files on the sdcard) you can make it even easier with a restore from a brick by replacing the zimage in the .tar file in 7zip.
there is nothing hard about the way people are doing this now individually but it seems quicker to me to 1 flash kernel 2 flash rom
than to 1 root 2 install 3e without sig check 3 install rom manager 4 flash cwm recovery 5 flash rom.

[link][tutorial] heimdall 1.1 how to aka how to get root and cwm the fast way

i still see questions about rom manager cwm popping up but rom manager will shortly be irrelevent once 2.3.5 drops. modded 3e and root via rage against the cage are a thing of the past. exploits that are no longer open.
this is how rooting and cwm will be done from here on out. get used to it. don't be scared it's not hard.
i did not create the how to video only did 12 seconds of searching on google. things that will be different from the video are that you will only flash the kernel. (zimage)
what you will need:
*heimdall, any version will do but this video is heimdall 1.1. 1.3 would need another video but if i find it ill add it to the op.
*an att infuse 4g or infuse 4g galaxy s if you are canaidian
*a computer, any will do
*a micro usb cable
*an archive program
*a custom kernel (community kernel or defuse for 2.2.1 att users) hellraiser or entropy for rogers users or users that in the future get the 2.3.5 update on att
windows specifics:
drivers- these are available through kies. any version should be fine. the drivers are also on the samsung site without kies
visual c++ redistributable 2010 (should be available through the microsoft download center, google it or bing it if you prefer)
mac specifics:
codeless kext (i have zero experience with this but will see if i can find a tutorial explaining that)
instructions:
-take the kernel downloaded from a link in the dev section (search is you friend) and open it with an archive manager like win rar 7zip or other.
-extract the zimage. this is the actual kernel. if it is a flashable .zip file you will find it in the kernel folder or the updates folder.
-review the video, take note of the driver install. this shouldnt be an issue on win7 32 bit but may be a problem on other versions
-put the zimage in the kernel slot, no other slots are relevant.
-connect the phone in download mode via the data cable (volume bar+usb cable)
-flash!
enjoy your rooted phone with custom kernel cwm and voodoo lagfix! that was easy
video: http://www.youtube.com/watch?v=6TgyaUbjcm4&feature=related
heimdall: http://www.glassechidna.com.au/products/heimdall/
drivers: http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT

Perfect timing. I was just researching this on a suggestion from Entropy in another thread. From what I gather once I uncompress one of these roms I can use heimdall to flash without going into recovery? Does that sound right? You will be in download mode instead of clockwork?
You state "enjoy your rooted phone with custom kernel cwm and voodoo lagfix". I assume that all comes as part of the roms? Is clockwork added in case you want to change roms or wipe data? I was taking it to mean heimdall replaced clockwork but you seem to state it will be on the phone after you flash.
Thanks for the links and all.

Not exactly. This was more about it being used as an alternative to rooting and using rom manager.
Heimdall can flash roms as well obviously but they need to either be a rom dump or extracted Odin package. They need to be in special archives in our case rfs. This is not to say a custom rom can't be manipulated into an Odin or heimfall flashable form. An easy way to do this is to take an existing Odin package and open the factoryfs.rfs image in magic iso and over write the contents with the contents of the /system folder from a custom rom. But permissions can be a problem doing these things in windows so I don't recommend this because it is a little more difficult to change the permissions inside the image than a normal archive and flashing the rom without checking the permissions could lead to a brick. The proper way to do it involves terminal and mounting the image to a loop device for editing which I have never tried. Its a bit more advanced than flashing Roms. This is where you get into some command line skills which are not too common today in our world of GUI.

Thanks for the clarification. This is just to get a custom kernel and be rooted since that is going away then? You will still need to flash using cwm or whatever to get the rom on. I guess I kind of jumped the gun because most of the heimdall flashes that i have seen on YouTube seen to be the whole rom. That's too bad. It almost seems easier that way.
Thanks for responding before I screwed up.
Sent from my SAMSUNG-SGH-I997 using XDA App

rxnelson said:
Thanks for the clarification. This is just to get a custom kernel and be rooted since that is going away then? You will still need to flash using cwm or whatever to get the rom on. I guess I kind of jumped the gun because most of the heimdall flashes that i have seen on YouTube seen to be the whole rom. That's too bad. It almost seems easier that way.
Thanks for responding before I screwed up.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
What you use for flashing is up to the rom developer. There have been Odin roms in the pastfor the galaxy s and the bootloader may need to be updated this way for people who don't choose the use the the 2.3.5 update to get the bootloaders. That means some rom developers may choose to package the rom for Odin or heimdall to get the bootloaders.

[TUT] Install Root, CWM, and the FC17 Update on Samsung Conquer 4G

Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.

it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...

I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.

AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.

brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.

AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.

brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.

give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help

sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk

sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.

i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help

brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"

It worked for me.

Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.

roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.

Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.

Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.

I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?

Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium

There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA

[Q] Rooted with SOC without unmounting SD

I performed root of my stock Froyo Infuse using Superoneclick.
I did NOT remove or unmount the SD card prior to doing this (it was not mentioned in the instructions I followed on another site).
The phone was successfully rooted. I see no problems evident in behavior of the phone.
I am contemplating flashing a ROM at some time in the future (after more studying of the qkster's "how-to").
Will this previous error cause me any problems?
Is there anything I should do to fix it before I proceed?
Thanks in advance.

You appear to have done everything correctly so you are safe to continue. When it says not having the sdcard connected it refers to your internal sd card, which cannot be mounted to the pc when running SOC.
What ROM you plan on flashing sir? That way I may be able to make the process simpler for you.
Sent from my sweet & buttery Infuse

Thanks. AEON is my objective.

Very well, then you just only need to install cwm so you can flash the rom.
follow method 1 of this:
http://forum.xda-developers.com/showthread.php?p=14376440
Be sure to first install the 3e modded recovery using an root explorer such as solid explorer or es file explorer, both free.
Sent from my sweet & buttery Infuse

andros11 said:
Very well, then you just only need to install cwm so you can flash the rom.
follow method 1 of this:
http://forum.xda-developers.com/showthread.php?p=14376440
Be sure to first install the 3e modded recovery using an root explorer such as solid explorer or es file explorer, both free.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
Or...since he's rooted download aeon, then download one of entropys DD kernels (any one...its only for cwm and the kernel will be replaced by aeon)
Then go to the playstore and search "sgs kernel flasher"
Flash entropys kernel that you downloaded
After reboot (may boot loop don't worry) boot into recovery by holding both volume keys and power simutaniously until your phone reboots and you see Samsung logo...when you see the Samsung logo release the buttons
Wipe data/factory reset
Wipe cache
Wipe dalvic cache (under advanced)
Install zip from sdcard
Choose aeon
Choose yes
Wait
When done reboot
Sent from my HTC Holiday using Tapatalk 2

promissa reGeneo
mg2195 said:
Or...since he's rooted download aeon, then download one of entropys DD kernels (any one...its only for cwm and the kernel will be replaced by aeon)
Then go to the playstore and search "sgs kernel flasher"
Flash entropys kernel that you downloaded
After reboot (may boot loop don't worry) boot into recovery by holding both volume keys and power simutaniously until your phone reboots and you see Samsung logo...when you see the Samsung logo release the buttons
Wipe data/factory reset
Wipe cache
Wipe dalvic cache (under advanced)
Install zip from sdcard
Choose aeon
Choose yes
Wait
When done reboot
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
I want to follow roughly mg2195’s path suggested above.
I did download SGS.
As a side-trip, I used SGS to install some Froyo-compatible custom Kernels (Infusion 2.0, Infusion 1.8, Defused 1.4).
I now have Defused 1.4 Kernal along with my stock Froyo ROM
I used Root explorer to put the modified recovery file in.
I rebooted several times and used the three-finger press, and now I reach the RED screen:
ClockwordModRecovery v2.5.1.3. But I didn't do anything at that screen yet other than exit.
I have two questions before I proceed;
QUESTION 1 – Can I skip entropy’s DD kernal since I already have CWM red?
QUESTION 2 – I want to verify the modified recovery file that I used is correct:
I use the one suggested in this Infuse video:
http://www.youtube.com/watch?v=Y09p-J_g_Rg
the video links to file
http://llamalord.com/youtube/downloads/3e_recovery_no_sig_check.zip
When I googled that file name 3e_recovery_no_sig_check.zip to double-check, it lead me to this thread for CAPTIVATE:
http://forum.xda-developers.com/showthread.php?t=909213
GTG has a different thread “100% working ClockworkMod Recovery for Infuse 4G” which has a zip file with a different name (recovery-clockwork-2.5.1.2-infuse.zip)
http://forum.xda-developers.com/showthread.php?t=1107881
That 2.5.1.2 is not quite the same version number that I see on my red screen (my red screen says 2.5.1.3) . And on top of that, GTG made some comments on page 1 and 2 of that thread which I didn’t fully understand but lead me to believe Captivate is not a match (so he used i90000 instead). All of this makes me wonder if I have the right CWM red in there.
QUESTION 2 SUMMARY: Do you think my CWM red is good, or do I need to start all over again with GTG’s file?
Additional info found later;
I did find the same file 3e_recovery_no_sig_check.zip that I installed here on xda forums in an Infuse thread by h8rift: http://forum.xda-developers.com/showthread.php?t=1091465 . I downloaded it and verified the zip filename and size is identical to the one I used. That makes me feel a little better about question 2.

Although I've been studying these things, I'm still confused about the next step (trying to figure Q1 answer myself). Maybe if I can understand better, then I can answer myself. The following questions are an attempt to improve my understanding:
Q3 - Does getting the red CWM menu mean my CWM is successfully installed the way it needs to be ready to flash a rom ? (I’d think it does, but not sure).
Q4 - I see the GTG thread was same one linked by andros11. I am totally confused about that thread. Method 1, Step 1 you take a zip (which zip... your ROM or the one linked on the message?) and you rename it update.zip and put it on your sd card (where on your sd card... surely it makes a difference?). And this accomplishes something different than putting the modified file named recovery file into root/system/bin/recovery using root explorer?
Q5 – the only purpose of mg2195’s recommendation to download entropy’s kernal was to get the modified CWM, right?
Thanks for your patience.
========================
I think I will go ahead and flash Entropy's daily driver, should make all my questions irrelevant.
I'll post results, fingers crossed that it'll be a proclamation of victory.
In the meantime, I'm still curious about above, especially question #4.
==================
Edited again - actually I am going to sleep on it for a few days and make sure this is what I want to do.

electricpete1 said:
Although I've been studying these things, I'm still confused about the next step (trying to figure Q1 answer myself). Maybe if I can understand better, then I can answer myself. The following questions are an attempt to improve my understanding:
Q3 - Does getting the red CWM menu mean my CWM is successfully installed the way it needs to be ready to flash a rom ? (I’d think it does, but not sure).
Q4 - I see the GTG thread was same one linked by andros11. I am totally confused about that thread. Method 1, Step 1 you take a zip (which zip... your ROM or the one linked on the message?) and you rename it update.zip and put it on your sd card (where on your sd card... surely it makes a difference?). And this accomplishes something different than putting the modified file named recovery file into root/system/bin/recovery using root explorer?
Q5 – the only purpose of mg2195’s recommendation to download entropy’s kernal was to get the modified CWM, right?
Thanks for your patience.
========================
I think I will go ahead and flash Entropy's daily driver, should make all my questions irrelevant.
I'll post results, fingers crossed that it'll be a proclamation of victory.
In the meantime, I'm still curious about above, especially question #4.
==================
Edited again - actually I am going to sleep on it for a few days and make sure this is what I want to do.
Click to expand...
Click to collapse
Since you already managed to get Cwm red, you have no need of using the 3e modded recovery. That would only allow you to flash the zip linked in the OP of the gtg thread, which should be placed on the root of your /sdcard.
Entropy's dd mg2195 suggested would replace your kernel with a Gingerbread one that included cwm.
I would say to go ahead and flash Aeon since you already have CWM.
Sent from my sweet & buttery Infuse