yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] bethesdaadk:
S2 running EL29 Frimware and Android 2.X "Waiting for Device"

I have an S2 / Epic 4G running the EL29 Firmware. It is rooted and I wanted to install CWM on it so I can install a custom ROM. I downloaded one of the available auto root packages - but it doesn't appear to be able to correctly talk to the device. I get this far. USB Debugging is enabled and to the best of my ability to check, storage mode is not on. KIES is not running, but has been installed in order to install the proper drivers. It seems to be an adb issue. I wait a little then terminate.

Suggestions?

INSTALL BootImg - EL29+CWM-Rogue (requires ROOT)

Please verify ALL of the following:

USB Debugging is ENABLED

USB Storage Mode is DISABLED

Samsung USB/Android drivers are INSTALLED

Phone is connected to USB port and recognized

Press any key to continue . . .

----

Waiting for device to be connected [press CTRL-C to cancel]... ^CTerminate batch

job (Y/N)? y
[Samsung Epic 4G Touch] sfhub:
I think sling already answered your question, but basically everything is automated and Options A-E will each automatically reboot upon completion of the individual tasks.
[Samsung Epic 4G Touch] pasta1234:
I noticed the folder oooroot after using this amazing process, is it necessary to stay there, purpose ?

Thanks,

Pete
[Samsung Epic 4G Touch] sfhub:
The installer keeps some files it uses on your /sdcard/000root directory. You can remove this at any point. It won't affect future operations, though I like to keep it around since you'll be able to do stuff like restore EG30 directly on the phone using Terminal (ie you wouldn't need a PC)

As long as you have the /sdcard/000root directory around you can do the following from the phone (without need for PC)

1) unroot

2) install EG30+CWM

3) install EG30

4) install arbitrary zImage

Even if you remove the directory, next time you run the root installation kit on your PC, the necessary files will get put back, so it won't affect whether you can use those functions later.
[Samsung Epic 4G Touch] maddoggin:
thank you!!
[Samsung Epic 4G Touch] Henri Blanche:
Greetings All!

If I use menu option C or D does that leave me with an Odexed or Deodexed ROM?

Cheers, Henri
[Samsung Epic 4G Touch] sfhub:
It will leave you with exactly the same ROM you had before option C or D. In other words, it doesn't touch your ROM, only the BootImg. In both examples, with the included BootImgs, you'll have the stock EG30 kernel (not recompiled). The difference is Option C includes an initramfs that has been repacked with CWM. This is explained in Reference Section C.
[Samsung Epic 4G Touch] firket2000:
Does this method wipe your phone or are apps and data left intact?
[Samsung Epic 4G Touch] sling:
No but a back up just in case doesn't hurt
[Samsung Epic 4G Touch] firket2000:
Thanks
[Samsung Epic 4G Touch] rde34:
First of all, thanks so much for this. I want to make sure the way I'm doing things is utilizing this method the proper way. So, I start by rooting my device this way and installing stock+cwm5 via eg30auto. Then, what is the correct method to install a custom ROM and maintain the stock kernel? Do I just flash the ROM as usual through cwm5 and then go back to eg30auto and replace that ROM's zImage via option (C) thus reinstalling eg30+cwm5? I mean, I know this way works but is there an intended way to do this that I am missing? Thanks in advance.
[Samsung Epic 4G Touch] sfhub:
It is probably easier if you remove the zImage file from the ROM's zip file. Folks have mentioned doing that to avoid flashing the kernel included with the ROM.

If you install a kernel along with the ROM by mistake, you should be able to use Option C (or Option D) to get back a stock kernel.
[Samsung Epic 4G Touch] rde34:
Thanks so much for the quick reply. Do I simply use 7zip and delete the ROM's zImage? Some have stated that you then re-pack or zip the ROM and then flash. I am not sure I know how to re-pack or zip. Could this be why I removed the zImage from a custom ROM, closed 7zip, flashed that ROM via cwm but got an error message? Thanks again.
[Samsung Epic 4G Touch] sfhub:
This is what other folks suggested.

I was thinking that you'd probably have to turn of signature verification and would get some error at the end of the install script by removing the zImage, but folks seem to be saying it works so I didn't look into it any further.

If it was an ODIN tar file, then just removing the file would be good enough for sure.
[Samsung Epic 4G Touch] maddoggin:
hey man this worked awesome, but i have a question i had installed chris41g kernel with cwm and then flashed the stock rom which had another kernel in it. i want to go back to chris kernel since i have root already can i use this to reinstall chris kernel??
[Samsung Epic 4G Touch] kgatlanta:
Hard reset after root?

What happens if I hard reset my phone after rooting it?
[Samsung Epic 4G Touch] sfhub:
Option C is chris41g's stock EG30 kernel repacked with CWM. If that is the one you are talking about, then yes, you can choose that option to reinstall it.

If it is some other kernel, you can place the zImage in the copy2sd\000root directory and choose Option E.
[Samsung Epic 4G Touch] sfhub:
Root stays, phone gets hard reset (ie /data is wiped). Depending on which recovery you are running some Sprint pre-load may or may not get reinstalled.
[Samsung Epic 4G Touch] maddoggin:
why isnt this stickied??
[Samsung Epic 4G Touch] kiwiBeans:
Dude, yes - you just totally schooled me right there. I mean, EXCELLENT explanation, concise and perfectly understood. Thank you so much!

I almost didn't even know this thread existed - I've been meaning to root but wanted to stay stock. I actually had to ask qbking77, who put together the sticked thread of root methods, what I should do to root and stay stock and he pointed me to this thread. WHY IS THIS THREAD NOT STICKIED?!
[Samsung Epic 4G Touch] sling:
It should of been sticky on day two and here we are on day 7 with members stumbling upon.

Rooting is a pretty serious step for many this method should be well known at top of forum.
[Samsung Epic 4G Touch] Henri Blanche:
Here's another vote for thread stickiness!
[Samsung Epic 4G Touch] sfhub:
This post is for the FAQ section:

Why is the install stuck waiting for device to be connected?

Your phone isn't being recognized by your PC as an Android device.

When the drivers are installed and the phone is properly recognized, you should see the following in start->run->devmgmt.msc

Android Phone
SAMSUNG Android ADB Interface

Modem
SAMSUNG Mobile USB Modem

Until you get the SAMSUNG Android ADB Interface to show up, neither ADB nor this script will work.

Here is a debugging checklist:

1) dial ##UPST# (##8778#) in the dialer and verify AP (or ALL) is checked (if CP is checked, phone won't be recognized as an Android device)

2) restart the ADB server (choose Option E followed by Option I to stop the server, it'll get started automatically by the script)

3) verify USB Debugging is ENABLED

4) verify USB drivers are installed (Win7-64bit see below)

5) try a different usb cable (NOT LG branded)

6) try rebooting phone and PC

If you are in Win7-64bit try changing the default install location for the drivers:

If you see an error like this:

Try running the CMD prompt (or e4gtauto-sfx.exe) as Administrator. Right-click on the CMD icon (or e4gtauto-sfx.exe) and select "Run As", then select Administrator.

If that doesn't work, try disabling windows firewall.
[Samsung Epic 4G Touch] zarthan:
I have been modifying my devices for many many years. TiVos to routers to phones and this was just the easiest I have experienced ever. MANY THANKS.
[Samsung Epic 4G Touch] sfhub:
I added an FAQ section (Reference Section E in the 2nd post). If there is anything you'd like to see there let me know and I'll add it if appropriate.

Also I added Reference Section C to explain what the included scripts do.
[Samsung Epic 4G Touch] dcxgod:
I now official <3 you.
[Samsung Epic 4G Touch] ChodaBoyUSA:
*sniff* I love you man!
[Samsung Epic 4G Touch] DataHawg:
Oh Happy Day. So easy and slick. I love the scripts running in the DOS box during the process, too. Clever. Like a play by play of an alien earth invasion. LOL. In the FAQ, can you post the sequence to boot into CWM Recovery from power off? I'm sure it's in the forum somewhere but I haven't been able to find it. I used Rom Manager to do my first backup after root but would like to know the correct process to get to CWM in case I ever get a boot-loop after flashing a new ROM. Also, this is my first Samsung phone. What is download mode and what would I use it for?
[Samsung Epic 4G Touch] sfhub:
For the FAQ section

How do I boot into Recovery?

Power down phone using [Power]

Press and Hold [Power] [Vol Up] [Home] until Recovery screen is displayed, then release buttons.

This is sometimes confused with the [Power] [Vol Dwn] [Home] key sequence which boots into ODIN download mode. ODIN allows you to flash software to the phone outside of Android. It provides similar functionality to fastboot on other platforms.

Alternate ways to boot into recovery:

From "adb shell" or "terminal" (do not type the $ and # signs)

$ su
# reboot recovery

From DOS Prompt

adb reboot recovery

From Android

Quick Boot
[Samsung Epic 4G Touch] maddoggin:
finally got the respect this deserves, thank you for this makes rooting so much easier man, i got my replacement phone yesterday 10 minutes later i was rooted thanks to this method. just like oneclick!! thanks man!!
[Samsung Epic 4G Touch] DataHawg:
Thanks so much. This is very helpful. I had forgotten about the methods of booting into recovery through adb or DOS. I wasn't familiar with ODIN and your auto method was just too easy not to try. Great!
[Samsung Epic 4G Touch] sfhub:
First post update to reflect new EG31 zImage+initramfs from squshy 7's tarball.

I've done cursory testing with EG30 modem.bin, EG31 zImage, and EG30 ROM. WiFi and 3g work ok.

However, EG31 zImage is mainly there if you ODIN'd squshy 7's factory image tarball, then need to get back to EG31 zImage (to match your EG31 modem.bin) after you installed some ROMs that overwrote zImage.
[Samsung Epic 4G Touch] dette:
So, probably a bit of a noob question here. If I root and then install the stock kernel + cwm will it increase my flash counter?

Thanks
[Samsung Epic 4G Touch] sfhub:
Through this method, no. Through ODIN, yes.
[Samsung Epic 4G Touch] eman3316@optonline.net:
Do we need to use squshy's odin file in order to get EG31 on our phone first before rooting it or will EG31 be pushed to our phone if we use the file in your zip?
[Samsung Epic 4G Touch] sling:
hmm loaded selection (E) but nothing changed , I'm still on Calks 1.1 with EG30 goods after boot.

Update:

Oh and I lost CWM

Update:

I went ahead flashed (C) getting CWM back.

Im going to hold tight till full factory EG31CWM combo is put together then go from there.
[Samsung Epic 4G Touch] michaeljc70:
This worked great. On top of root, I got drive letters when I connect via USB which lets me do a sync for my music which I could not do before because it showed as a device.
[Samsung Epic 4G Touch] sfhub:
EG31 is "stock", so you are supposed to lose CWM. At the moment it is there for folks who install the EG31 tarball from squshy 7 (they'll have EG31 modem.bin, EG31 zImage, and EG31 ROM) and then get there EG31 zImage overwritten at some future point. These folks may want to go back to stock EG31 zImage w/o using ODIN, so I included it here. A little background, squshy 7 graciously provided a factory image ODIN tarball. That included a slightly newer EG31 radio. The kernel was still labeled EG30, but the build date was 1 day later. Also the ROM had some changes. Instead of confusing the issue with qualified names, it is easier to call all of them EG31.

NOTE: EG31 is also known as EG30-Rev5. Based on Samsung naming conventions, the kernel should have been named EG31 since it was built on July 31, but it was released with the EG30-Rev5 name, with an EG31 baseband/modem.

The only "visible" change you will see is the kernel version # should be

EG31: 2.6.35.7-SPH-D710.EG30-CL435

803

-

Sun Jul 31 06:19:52

vs

EG30: 2.6.35.7-SPH-D710.EG30-CL435

734

-

Sat Jul 30 23:56:18
[Samsung Epic 4G Touch] sling:
Well that doesn't matter now I'm bricked way to kick off weekend :(

I restored back-up all was well then I decided to reinstall Calks rom without Zimage which was bad move I'm stuck on Boot screen.

Did battery pull tried to get into CWM and that's a no go boot screen comes back stuck
[Samsung Epic 4G Touch] sfhub:
To help others could you go into more detail as what you "restored" to (zImage, ROM, etc.) and how you restored (CWM?)
[Samsung Epic 4G Touch] sling:
After restored to EG30CWM stock I took apart Calks1.1 removing Zimage packed it back up then dropped into internal storage for flash.

I booted into CWM flashed Calkulin's_FORMAT_ALL_for_E4GT then flashed Calk repack I put together.

Install took place I rebooted getting stuck on GS2 splash with boot to never complete.

BRICK

Well i still can get into Odin mode
[Samsung Epic 4G Touch] sfhub:
Calk's format all, basically formats /cache, /data, and /system

Probably the ROM does some path changes in the init.rc/init.d (via initramfs in the zImage)

I think you can probably just take the zImage you removed from the Calk's ROM, stick in a tar file, and flash via ODIN and it will get you booting into Android again. After his kernel does the setup, you should be able to switch it out to EG30+CWM as the setup is probably persisten. This is all in theory. It is probably easier to flash stock EG30 or EG31 via ODIN and then move forward.
[Samsung Epic 4G Touch] sling:
Yeah I was thinking EG31 Odin install would be safe bet.

I just need to figure out how lol
[Samsung Epic 4G Touch] thephawx:
I've been hesitant to try any ROMs with the LOS problems people have been reporting.

Also because my stock build works perfectly that I don't find it all that necessary to try any.

What is the overall consensus on EG31? Much improved?
[Samsung Epic 4G Touch] sfhub:
It just came out yesterday (via squshy 7's factory image tarball) so there aren't enough experiences to say much. Calk says EG31 modem fixed LoS for the builds he is working with. From past experience though there are sometimes things that break also and you don't hear about them until a week or two after release.

If you are the cautious type and everything is working for you, I wouldn't change anything. EG31 was built 1 day after EG30 (July 31 vs July 30) so I don't think you are missing much if you don't currently have problems and it would be better to wait and read other peoples' experiences. Keep in mind, there is currently no way to get back to EG30 radio/modem.bin, so once you upgrade to EG31 radio/modem.bin you are stuck there, for better or for worse.

The EG31 zImage, on the other hand you can swap out with an EG30 zImage.

If you currently are having problems, then it might be worth it to try it out.
[Samsung Epic 4G Touch] sling:
ODIN saved the day EG31 tar installed device in working order :)

Thanks sfhub
[Samsung Epic 4G Touch] dette:
Thanks! So I can use cwm through this root and stay safe (I may have to return my phone because of a faulty power button), but if I flash a ROM the counter will go up, no matter how I accomplished the root+cwm, is that correct?

Thanks for answering my first question! This is my first Android phone :)
[Samsung Epic 4G Touch] sfhub:
If you don't use ODIN, your flash counter won't go up. If you use ODIN, flash counter won't increase when you flash signed official kernels from Samsung.

If you use this method, you can root, install CWM, and flash a ROM w/o ODIN, therefore flash counter won't increase.
[Samsung Epic 4G Touch] dette:
Fantastic! Thank you!
[Samsung Epic 4G Touch] Just_s:
I already rooted when I got the phone weeks ago, but I have to say this is one of the best put together, best organized and clearest OPs I've ever seen at XDA. No spelling/grammatical errors, slang, shorthand, or chaotic letter/symbol replacement (i.e. J0k3r5 Aw350M3ne$$ fo R34Lz or whatever.) Just clear concise information and direction. It's a very professional setup. Awesome job sfhub!

I will definitely be sending people to this thread when they are ready to root and will use your method on my wife's E4GT.
[Samsung Epic 4G Touch] eman3316@optonline.net:
So what is the feedback from people who were not rooted and never seen an LOS then rooted this way with EG30 and CWM. No Rom change or anything.

Has anyone seen an LOS after rooting this way and not changing anything else?

Just looking for replies from people who never had one before.

I have never seen the LOS symbol in the month and a half I have had it on my unrooted phone until last night. The cool thing is my service came back after about 2 minutes. No reboot or anything needed. Maybe that is why so many unrooted people don't realize it might have happened because service comes back unlike what we have heard with rooted kernels and custom roms where service does not come back...

Just wanted to follow up that I had rooted my phone the evening I had posted this. I am running the ACS Ice Rom and loaded the stock pulled kernel back after flashing the Rom. So far everything has been great and I have not seen an LOS yet. Hopefully it stays that way!
[Samsung Epic 4G Touch] sling:
Never had issue un-rooted for over 2 months of owenrship

After 9 days rooted with this method still no LOS....well kind of.

My local tower took a clunk device jumping between roam and network for an hour then LOS icon appeared.

I regained service by disabling roam setting then enabling , roam signal came back with Sprint network service following an hour later so I'm racking that up as Sprint network LOS which is like yours.

Device didn't lock up requiring throw against like many are experiencing.....that would be true LOS something to worry about
[Samsung Epic 4G Touch] eman3316@optonline.net:
So tempting, think I might jump on it later. I have been going back and forth with myself in deciding if I should do it.
[Samsung Epic 4G Touch] sling:
Been there done that eman.

I had lots of doubt going back & forth making decision for months then going for it.

Chances are you wont experience issue if you haven't had it before.

Some members are having LOS 4 - 5 times a day everyday stock and rooted while others haven't seen any.

Hardware issue maybe?.....Im beginning to think so.

Its a puzzle with missing pieces samsung fails to provide.
[Samsung Epic 4G Touch] sfhub:
The best I can offer is FAQ #E8 in the second post.

Will this cause LoS?
[Samsung Epic 4G Touch] eman3316@optonline.net:
Thanks, does flashing the one with CWM into the mix change anything up that might play into LOS?
[Samsung Epic 4G Touch] sfhub:
The kernel in that is still exactly the same as the stock kernel.

What changes is swapping out the stock recovery executable with the CWM5 recovery executable. These don't get run unless you boot into recovery.

Also there are slight changes in the init scripts which wouldn't change anything if you are running stock ROM (which doesn't have init.d scripts)

Where I'm 99.9% sure the root itself will have no effect on your LoS (ie you'll see or not see it, irrespective of the root), I'm probably 99.5% confident about the EG30+CWM5 only because I didn't put it together myself, not because I have any reason to think it is less safe.
[Samsung Epic 4G Touch] Sam Sung:
Hi,

Another new guy here. Thanks for your efforts, and as stated in a recent post, very well spoken and clearly explained. I've read through this entire thread (over the course of a week as time permitted). After doing so, I returned to the OP, followed the instruction and ran runfirst.

Everything seemed to go well, however, I'm not sure how to verify that the phone is rooted (did I miss this in the thread?).

I also have the sdcard/000root directory, but nothing to indicate that I'm indeed rooted. Thanks for your patience :) .

Oh, and I ran only option A.
[Samsung Epic 4G Touch] eman3316@optonline.net:
You should have superuser app in your app drawer.
[Samsung Epic 4G Touch] sfhub:
For FAQ section

How do I know if I'm rooted?

The first sign that you have root is you'll have the Superuser icon in your app drawer, but that is not definitive as it is just a database keeping track of root permissions.

There are multiple ways to know for sure. These are just a few:

1) If you download an app from the market the requires ROOT, like Titanium Backup, it will ask for root permissions the first time it starts. If you are properly rooted, you will see prompts on your screen asking you to grant root permissions.

2) Make sure your screen is turned on and you EXIT the lock screen. In "adb shell" or "terminal" type "su". If you are properly rooted, you will either see prompts on your screen asking you to grant root permissions or you will see notifications that root permissions are being granted. After typing "su" your prompt should change from "$" to "#" A "#" prompt is historically a quick way to indicate you have root permissions in Unix.

3) Download a "Root Checker" app from market
[LG Optimus 3D] bolinao:
Somehow after my daughter was playing with my phone one of the 4 permanent buttons on the desktop at the bottom has been replaced with a game icon,how can i change it back to the icon it suppose to be...thanks
[LG Optimus 3D] Trekfan422991:
Its just a launcher setting.. usually a ling hold of the icon allows you to change it... depends on the launcher u are using

Sent from my LG Thrill 4G...
[LG Optimus 3D] bolinao:
No that does not work with the LG Launcher.
[LG Optimus 3D] Barracuda77777:
create a shorcut of the contacts, messages and phone on one of the screens, then long press and drag and drop on the menu in the order to replace the game icons.
[LG Optimus 3D] bolinao:
No when you long press the shortcut the "remove" icon appears at the bottom,so it cant be dragged onto the menu,you can only remove the message icon on the desktop.
[LG Optimus 3D] Barracuda77777:
Hi.

1 make shortcut of applications on desktop

2 go to applications long press from applications and drop on menu bar. Just tried it, it works :-)
[LG Optimus 3D] bolinao:
Step 1 i dont understand ??,but step 2 worked,i can only change the icon from the applications menu,not the desktop... thanks
[Vibrant Q&A, Help & Troubleshooting] Closfig1:
Since I am not allowed to post to the thread. (I don't have enough post) Quick question....I love the rom so far. However, the only issue I have so far is I CANNOT surf the web when I take myself off WIFI. Is there any way to fix that? Please let me know... thanx

I have tried to reflash a few times....still doesn't fix the issue..
[Vibrant Q&A, Help & Troubleshooting] Closfig1:
Nevermind! I am a RETARD! The answer was right there in the OP....
[Fascinate Android Development] weblexa:
MIUI Fascinate 1.11.11

Everything works except the reboot menu only has the normal reboot option. To reboot into recovery, open Terminal Emulator and type:

su <enter>

reboot recovery <enter>

Download: http://goo.gl/Q3euL

md5: 95808984e905906fd1ce7f093ac2448d
[Fascinate Android Development] millwood:
Which Kernel did u use for this port?
[Fascinate Android Development] shag_on_e:
I can't get the link to open...:-(

~~~~There is no spoon~~~~
[Fascinate Android Development] Vinnie981:
Same here......going to try from a PC
[Fascinate Android Development] PhoenixPath:
I don't see how this can possibly be legit. A quick glance at MIUI.US shows us *none* of the devices are running 11.11.11 yet.

Has anyone been able to follow this link?
[Fascinate Android Development] weblexa:
I used JT's latest kernel.
[Fascinate Android Development] weblexa:
Sorry. The server that is hosting my port became overloaded. I'm working on uploading the file to another service and will have the link updated shortly.
[Fascinate Android Development] weblexa:
A quick glance at the miuiandroid.com downloads page shows MIUI 1.11.11 ported to plenty of devices. This port is a miuiandroid port and is completely legit. As stated in my previous post, I'll have a working link up shortly.
[Fascinate Android Development] Vinnie981:
Its real
[Fascinate Android Development] The_Tech_Ninja:
Link is down.