yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] sfhub:
Most of this post was already covered by earlier posts from helpful users.

As clarification, this *root* DOES use your existing kernel+initramfs/ROM/UserData. You won't lose your existing data.

With the EG30+CWM and EG31+CWM BootImg/zImage, it doesn't touch your ROM or UserData, so you won't lose your existing data.

As to repacking CWM, you are really talking about semantics. With respect to "stock" kernels, whether you use your existing stock linux kernel, or someone elses stock linux kernel, to repack CWM is not really relevant. Both linux kernels have the same md5sum so behave exactly the same.

All the kernels from Samsung (for a particular version) will be the same for every phone. It isn't like Samsung delivered different EG30 or EG31 kernels to different people. What is changing (with the repacked kernels) for CWM is the initramfs. Whether someone uses your existing linux kernel or someone elses, for this repack, will make no functional difference.

Though I'm not aware of a tool on Samsung to do this repack with your existing kernel, theoretically it would be possible, but IMO it is more dangerous to try and repack arbitrary live kernels than it is to have someone repack it offline, test it, then deliver only the final product.

The only downside to the way it is being done now is you need to choose which base linux kernel you want, EG30+CWM or EG31+CWM, (rather than say "add CWM to my kernel") but that is really minor IMO.
[Samsung Epic 4G Touch] sfhub:
This is partially covered in FAQ #E6 in the second post:

What is the EG31 BootImg?

When the phones first shipped, every retail phone had EG30 modem.bin, kernel+initramfs, and ROM.

About a week ago a "factory" restore became available. We found that this "factory" restore actually restored your phone to a build that was 1 day newer than what the retail phones shipped with.

The modem.bin version was EG31. The kernel+initramfs, and ROM were listed as EG30-Rev5 when according to Samsung naming convention should have been EG31. Both to remain consistent with the modem.bin naming and to follow Samsung naming conventions we have been referring to what has been labeled EG30-Rev5 as EG31.

So to answer your question, EG31 is a kernel+initramfs that matches what was delivered in the Factory restore tar and matches the EG31 modem.bin.

If you haven't used that Factory restore tar, I would just suggest you stick with EG30.
[Samsung Epic 4G Touch] sfhub:
This is covered in FAQ #E8 in the second post.

Will this cause LoS?
[Samsung Epic 4G Touch] sfhub:
The zergrush exploit is failing for you. I've only ever seen it fail once, never after a fresh reboot.

There have been a lot of people who have rooted this way and you are the first to report it failing 4 times in a row, so my guess is it is something specific to your phone's setup.

Try letting the phone finish the media scans if you haven't already. Other than that, I would look for things you might have installed that other might not and try disabling those.
[Samsung Epic 4G Touch] sfhub:
So to clarify, EG30 and EG31 could refer to the radio (modem.bin), the kernel+initramfs (zImage) or the ROM.

In the case of the automated rooting kit in this post, we are only referring to the kernel+initramfs (zImage).

The automated rooting kit does not touch your modem.bin and it works with whatever ROM version you have installed, so doesn't change the ROM version.

When you say there is no way to go back to EG30, you are actually referring to the radio (modem.bin). With the kernel+initramfs (zImage) and ROM, you can go back between EG30 and EG31. Also EG12 only exists as a radio (modem.bin) version. There is no matching kernel+initramfs (zImage) and ROM released to the public as far as we know.

Other than that clarification, what you said is accurate.
[Samsung Epic 4G Touch] xlGmanlx:
Thanks for the clarification as you are correct as it bears clarifying modem versus kernel
[Samsung Epic 4G Touch] ogeretla:
Thank you Sir! :)
[Samsung Epic 4G Touch] Heelfan71:
I used this method to root and do not want to run any custom rom, but I do want to use some themes. Is that possible or do I need to have a custom rom to theme?
[Samsung Epic 4G Touch] sfhub:
Many themes are implemented in framework.jar and since the stock ROM is odexed, changes in framework.jar require re-odexing many other files, effectively forcing you to get a custom ROM. If you start with a de-odexed base, then you can probably just get themes, but some would consider a de-odexed stock ROM to be a custom ROM.
[Samsung Epic 4G Touch] Heelfan71:
Thanks, I might try Strong Steve's Odexed rom as I had good results with it before I rooted with this method. Will that rom cause any issues since I rooted with this method?
[Samsung Epic 4G Touch] sfhub:
I can't really envision every possible scenario, but there shouldn't be any "issues". Obviously once you install StrongSteve's ROM, if it includes a different kernel, you'd get the kernel (or kernel+CWM) that comes with that ROM and the unroot in this script only undoes what it put in place to start with. It won't undo a ROM install that you did subsequently. It should all "work" though, your phone shouldn't brick or anything like that.

I suggest you do a nandroid backup from CWM before you go playing with ROMs so you can get back to where you started.
[Samsung Epic 4G Touch] Heelfan71:
That is what I ended up doing. It installed fine. I went back to my nandroid bckup though as I got a LOS this morning after flashing his rom, which I never had before on that rom with the old root method.

I have noticed after rooting with this method that I keep getting a "lost data connection" in the pull down menu everytime it switches to roaming. My connection is fine, just get that message.
[Samsung Epic 4G Touch] sfhub:
I get that on stock unrooted. It has nothing to do with this root method.
[Samsung Epic 4G Touch] frog_dude:
So this works with the Sprint SPH-D710? If I unroot my phone with this app...its like it never happened?
[Samsung Epic 4G Touch] sfhub:
If you root, then unroot, everything will get undone.

After rooting, if you install EG30+CWM then before you unroot, install EG30.

You are responsible for uninstalling anything you install after rooting though. For example, if you install a custom ROM, this isn't going to undo that.
[Samsung Epic 4G Touch] frog_dude:
I am just looking to be able to wifi tether with my Sprint phone. This will work with opition A only?
[Samsung Epic 4G Touch] sfhub:
Yes, you can run Android WiFi Tether 3.1 Beta 7. Keep in mind e4gt has a newer wireless chipset and Harald hasn't gotten around to adding infrastructure support yet, so it is ad-hoc only.
[Samsung Epic 4G Touch] kiwiBeans:
sfhub, I'm hoping you can help me with a little problem I've got. I rooted using the method from this thread, and that was it. I never installed anything else, never performed a Nandroid, etc.

Well just a little while ago I was disturbed enough by this Carrier IQ fiasco that I installed the removal tool and "removed" it... when I rebooted I'm stuck on the Samsung splash screen.

Ideally, I'd love for a way to just get my phone back to the way it was but that's probably asking too much. In light of this realization, my next order or business is to get my files off the internal SD card - that was the primary location I was using and, due to the "GPS doesn't work if the phone is encrypted bug", it's not encrypted (thank god?). Is there some way I can get access to those files? Since the phone won't boot I can't get the phone to be recognized in USB mode to pull the files off... Thanks for any help anyone can offer...
[Samsung Epic 4G Touch] sfhub:
If you can boot into ODIN mode, I would suggest you flash stock pulled EG30 kernel and ROM. Theoretically it'll get your phone back and running, preserving your data.

Here is the ODIN tar file for EG30 pulled:

http://xdaforums.com/showthread.php?t=1282420

Also to get into ODIN mode, turn off phone (or pull/reinsert battery). Then press and hold [Power][Vol Dwn]. There's a video on how to use ODIN in the stickies.
[Samsung Epic 4G Touch] SantinoInc:
Can someone advise if using this root method will remove that CIQ crap? If not what is the best way to do it w/o flashing a custom rom
[Samsung Epic 4G Touch] sfhub:
It will not remove CIQ. This meant to only root with as few changes as possible. It gives you the ability to make further changes to your system but does not force you to.

The best way to remove CIQ is with a custom ROM that removes it. It can get complex to remove it because it is embedded in several apps and libraries used by several apps. Due to odexing, once you start changing some base libraries many files need to get re-odexed.
[Samsung Epic 4G Touch] kiwiBeans:
Thank. You. So. Freakin'. Much. That did the trick. Did just as the reference thread said and used the Youtube video posted as I went along. Phone booted up fine, then I turned it off, put my encrypted SD card back in it and rebooted. THe media scanning of both internal and external drives took a bit longer but in the end I could see everything and all was in tact.

Without having to make you go into too much detail, what the heck did I just do? My guess is that I essentially flashed the stock ROM and returned the phone to "stock" state, but it didn't touch (at least from what I can initially see in these first few minutes after having done it) anything in the phone. My apps, screen set up, files, (options and settings, even?) are all still there. I didn't know that was possible.

Clearly, I've lost root, as SU app is gone and the only 'mod' thing I can remember doing (replacing the camera app and camera sound files w/ a modded ones for no audible camera clicks or focus beeps) are gone - as in they make the noises again when I snap photos.

My first order of business is to backup everything before I do another thing, but getting root again is just as simple as following the OP of this thread, I assume. However, seeing as how I'd like to avoid anything this catastrophic I'll want to use/make Nandroid backups. As you mentioned in the other thread, do I need to choose option A to root and then option C to get CWM? (I'm assuming the Nandroid capability is part of CWM?). Thanks for being so helpful and patient, and for bailing my ass out. I owe you big time.
[Samsung Epic 4G Touch] sfhub:
You replaced your kernel and ROM with the ones that came with the phone. The app you ran to remove CIQ probably played with the ROM to try and scrub it but didn't leave things consistent, so Android wouldn't boot. There was a remote chance it tried to scrub the kernel too, so I just suggested you restore both back to the original.

The kernel has it's own partition. The ROM is mounted as /system (which is also its own partition) Your user data is mounted as /data (which is also its own partition).

You restored the kernel and /system to their original state, leaving /data in place. That is why your data is still there. Some custom ROM and factory restore methods will erase your /data because they make significant changes that would cause things to break if you kept your original /data, however you were going from stock EG30 to stock EG30, so nothing would likely break.

As to root, yes, you can choose Option A to re-root. Then choose option C and then EG30+CWM in the submenu. Then reboot into recovery (power down, press-and-hold [Power][Vol *Up*] until recovery shows up)

There will be a menu entry to "backup", choose that and follow the directions. Also, store your nandroid backup one other place other than your phone, in case your phone gets corrupted.
[Samsung Epic 4G Touch] SantinoInc:
Thanks for your reply and thank you SOOOOO much for making a retard proof rooting method. Based on your reply I suppose it is safe to say that using k0nane's MOD will jack up a stock phone? All I really want and need is a stock kernel, stock rom but with CIQ removed. I seriously don't need my info tracked...that's retarded. Any suggestions to reach this goal?
[Samsung Epic 4G Touch] sfhub:
Can't say from personal experience, but it says it works so I assume if it didn't there would be people complaining on the thread. I would just read through the thread or ask your questions there. It'll probably work fine.
[Samsung Epic 4G Touch] SantinoInc:
Yes sir, that is exactly what I did. I figured I would ask the question in both threads to see if the answers matched. I will post my findings back here in case anyone else needs the info. Thanks
[Samsung Epic 4G Touch] sfhub:
I read through that thread and it seems the odex version is no longer there and the folks that got it from other users had some problems.

Personally I think it is easier to get some rom with minimal changes like StrongSteve's odexed AIO that has the changes. I think he bundles a stock repacked kernel so it should be the same as you currently experience w/r/t LoS (ie if you don't see it now, you shouldn't see it with that ROM)
[Samsung Epic 4G Touch] pasta1234:
If i have Rooted my phone using this method and want to update to EK02/2.3.6 whats the easiest way ?

Pete
[Samsung Epic 4G Touch] Sam Sung:
Yes, the odex version is mia. Here is a link to the rom/kernel you mention:

http://xdaforums.com/showthread.php?t=1323763

It is, however, recommended that one wipes the phone. It was recommended to me to use Calkulin's_FORMAT_ALL_for_E4GT.zip, which can be found by searching the term in the Epic 4G Touch Android Development forum.

I was able to restore most apps and system settings with a Titanium backup. I played around with it a bit, then 'nandroided' back to where I was with this root. I intend to check it out later, but I just love my setup with the rooted stock (Thanks again, sfhub!)

I can't recommend strongly enough that those who move on to other roms and/or kernels or even just mods have both nandroids and titanium backups (or the like). Nothing like trying new things with the assurance that you can be back to where you were in minutes. Even moreso if something gets hosed.
[Samsung Epic 4G Touch] sfhub:
Assuming you haven't made any changes to /system after rooting, you can just run the rooted EK02 update.zip from here (this will update your modem/radio to EK02, after which there is no going back to EG30, people seem to be happy with EK02):

http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Roms/

If you have made changes, then choose a full ODIN update like this:

http://xdaforums.com/showthread.php?t=1368117
[Samsung Epic 4G Touch] sfhub:
For the FAQ section:

How can I get manually go to STOCK EK02 ROM and EK02 Kernel+CWM5(repack) w/o waiting for the OTA update?

There are many ways you can accomplish this. Here I'm just listing minimal instructions to get you to your final goal efficiently with fewer chances for mistakes.

Except for step 4, this will work regardless of whether you currently have EG30 or EG31 on the phone.

This will NOT give you the yellow triangle nor will it up your ODIN flash count.
[Samsung Epic 4G Touch] ejlmd:
Broken link

The mediafire download link for the egauto.zip script from first post seems to be broken.
[Samsung Epic 4G Touch] sfhub:
I think all of mediafire is having problems. Here's an alternate link: [mirror - eg30auto.zip]
[Samsung Epic 4G Touch] ejlmd:
rooted with your script, no system changes, signature verification fails when I try to install the update.zip from stock recovery
[Samsung Epic 4G Touch] musclehead84:
Sfhub do u known if this will root ek02? I'm just curious if the exploit was blocked or not in 2.3.6. Thanks.

Sent From My Evo Killer!!!
[Samsung Epic 4G Touch] DaEXfactoR:
this worked flawlessly and required little effort of me. Thanks for this root method.
[Samsung Epic 4G Touch] sfhub:
You need to run the EK02 update.zip (the "full" one from calkulin/chris41g) from CWM. Choose Option C and install the appropriate repacked CWM.
[Samsung Epic 4G Touch] pasta1234:
Why must we use the full EK02 build when we are upgrading from EG30 ?

Shouldn't it just take a update.zip on the memory ?

Pete
[Samsung Epic 4G Touch] sfhub:
You can take the OTA update.zip, but it is shipped as patches, so it needs every file in your ROM to be exactly as it expects it. If you made any modifications to or deleted any file it depends on, then it will fail the assert checks. For example, if you "factory" restored to EG31/EG30-Rev5 or if you installed a custom ROM, it will fail. Installing the full EK02 doesn't suffer from any of these issues, but you have to download a little more.

In either case, if successful, the end result should be the same /system. In either case, your /data is preserved.

IMO given the different states folks phones may be in, using the full EK02 update.zip is less work and less chance for mistakes. You are welcome to use the patch OTA version if you like.
[Samsung Epic 4G Touch] Sam Sung:
Would a nandroid 'bring you back', or are the 'permanent' files unaffected by a nandroid restoral?
[Samsung Epic 4G Touch] sfhub:
That statement was only referring to the EK02 modem.bin. Everything else can be restored via nandroid, odin, etc.

Once you change from EG30 modem.bin you can't go back. Once you change from EG30, you can't go to EK02. Once you change from EK02, you can't go back to EG30 nor can you go back to EK02.

This is all because we don't have an EG30 modem.bin to flash.
[Samsung Epic 4G Touch] chucky_93:
Waiting for device to be connected?

I chose option A and then confirmed that everything was ready, then I pressed any key to continue. Now it says "Waiting for device to be connected, press CTRL C to cancel" For how long should that be displayed? It's been about 5 minutes with me.
[Samsung Epic 4G Touch] Joe Smithereens:
I updated stock unrooted EG30 everything to stock unrooted EK02. How can I now root my phone?
[Samsung Epic 4G Touch] ejlmd:
That did it, thank you.

Also, along the way I discovered that the first time I ran your rooting script, it didn't fully "take", since I had run it from the desktop, rather than top level C drive.
[Samsung Epic 4G Touch] sfhub:
Troubleshooting checklist is in FAQ #E3

Why is the install stuck waiting for device to be connected?
[Samsung Epic 4G Touch] xlGmanlx:
..................
[Samsung Epic 4G Touch] syed239:
Does this include CWM?
[Samsung Epic 4G Touch] xlGmanlx:
Option C allows for installation of stock kernel and cwm
[Samsung Epic 4G Touch] 321321:
nociq

please, how could i nociq this automated root stock rom

i have cwm

thank you
[Samsung Epic 4G Touch] xlGmanlx:
Check out this thread

http://xdaforums.com/showthread.php?t=1373394
[Samsung Epic 4G Touch] sfhub:
directory and filename changed to e4gtauto (from eg30auto) to fit better with multiple version support

Added EK02 root support

Added EK02 and EK02+CWM BootImg/zImage support

Added No-CIQ support (EXPERIMENTAL)

Updated to su 3.07 (due to a DB change the list apps already granted root is reset during the process of installing root, just re-grant permissions)
[Samsung Epic 4G Touch] limeaid:
awesome. thanks!
[Samsung Epic 4G Touch] sfhub:
For FAQ section

How can I tell if CIQ is running?

You can use a Carrier IQ detector in market like:

Voodoo Carrier IQ detector

Please note that it is NORMAL to see Carrier IQ elements found:

as what was done was to disable CIQ rather than delete all remnants. The reason all remnants were not removed is because doing so might prevent you from getting OTA updates in the future. OTA updates check for the presence of the files that need to be patched and if not present, will cause the OTA update to fail. The important thing is the CIQ processes have been disabled.

You can also manually verify:

In adb shell you should see something similar to the following before disabling CIQ (do not type the $ signs)

After disabling CIQ it should look like this: (do not type the $ signs)
[Samsung Epic 4G Touch] jrock32:
I just want to make sure i'm understanding this method. This will allow me root access and CWM, if i choose, w/o using odin? Is the benefit so the odin count wont go up? I currently use Caulks 2.0 rom and love it, but i flashed EG12 and want to go back to EG30. If im correct i will need to find my nandroid backup before i changed modems (hope I can find it) or get a new phone?...

Ultimately i want to be able to tether, have Ti and delete unused apps. Would this method work for me? Sorry for the multiple questions, i just want to be sure.
[Samsung Epic 4G Touch] sfhub:
Option A gives you root access with the existing ROM on your phone.

Option C will let you install a stock kernel with CWM repacked. Option C requires you root first.

No yellow triangle and no increase in flash count are some benefits. Other benefits are it uses your existing stock ROM, so if everything is otherwise working great, but you just want the addition of root access, this will get you there using your existing setup, instead of asking you to flash a new custom ROM. Some people like to run on stock, but just add root access. It is also easier in the sense that you can't really mess up your phone choosing the wrong options and you can also swap kernels later on, from the phone, without need for PC. (mobile ODIN helps with that too)

You cannot go back to EG30 modem. You can go back to EG30 ROM and EG30 kernel, but not the modem. You can go to EG31 modem. However, the OTA update that was available earlier could only be applied to EG30, but that doesn't really matter for you since you are on EG12 and wouldn't be "losing" EG30 by going to EG31.

If you are talking about Android WiFi Tether, then installing root access using this package will allow you to use that. It will also allow you to remove unused system apps.
[Samsung Epic 4G Touch] DataHawg:
Fantastic. This is what I was looking for. I rooted with your script before the EG31 option was added so I'm still on EG30 with the stock ROM. When the OTA update gets pushed to my phone do I need to unroot first to install it or will I just lose root and then root again with the new script? I'm debating whether I even want the update because my phone is working great and I've never had LOS.
[Samsung Epic 4G Touch] sfhub:
You shouldn't need to unroot. None of the root files installed by this package are on the "verification" list of the OTA update. Now if you modified your /system by changing or removing binaries, then those might be checked by the OTA update.

So assuming all you did was root EG30, you should be able to apply the OTA EK02 update, it'll remove the root permissions for su (but leave the Superuser.apk app), so you'll still see Superuser in the app drawer, but su won't work.

Then just re-run Option A from the package (after redownloading it) The directory name change to e4gtauto (from eg30auto)

Also the su version got upgraded to 3.07 and there was a DB incompatibility with previous versions, so after re-rooting, the *first* time your root apps run, you'll need to "accept" the prompt that comes up to grant root permissions.

I wrote it a little wordy to be complete, but it is relatively simple.

As always, when doing system updates, have make a current backup, just to be safe.
[Samsung Epic 4G Touch] DataHawg:
That explains it very well. I already downloaded the new script and I'm anxious to try the nociq option but didn't want to flash a custom Rom to get it. BTW. It appears an official EG30 modembin has been leaked and it's being tested as we speak. I read about it on another thread about an hour ago.
[Samsung Epic 4G Touch] puertoblack2003:
Hey, i tried that ciq disable and it worked, to confirm that it did.I used voodoo carrier iq detector. good job !! One thing tho i had to update the adb package.It was asking me to update so i pulled it from my sdk folder
[Samsung Epic 4G Touch] sfhub:
Good to hear ciq disable worked. Thanks go to JoshMiers for putting it together.

What exactly was asking you to update adb? I don't think I included anything that would check for updated adb so was it something you had on your PC already?
[Samsung Epic 4G Touch] puertoblack2003:
when i ran the runfirst.bat file, i selected option D then i went through the intro and that's when it popped up with outdated adb.exe.No big deal just a heads up just in case anyone else runs into the same issue .I always resolve my own issues ;)