yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] depechemodegurl:
I am getting this same error message, what do you mean the exe version and where is the reference section?
[Samsung Epic 4G Touch] sfhub:
The e4gtauto-sfx.exe download link is right next to the link to the zip file.

The reference section is in the 2nd post
[Samsung Epic 4G Touch] jeffyv2:
Is there a reasom on why when i try to flash a rom after doing this won't flash? It restarts shows the Samsung screen then the blue notification light shows then goes back to clockwork.
[Samsung Epic 4G Touch] sfhub:
your issue is with cwm and the rom update.zip or your partitions, it isn't specific to auto root. If you are booting into cwm,that is the extent of where auto root gets involved
[Samsung Epic 4G Touch] Karl:
i couldnt get it to work
[Samsung Epic 4G Touch] sfhub:
Care to provide more details? Couldn't get what to work? What was the error?
[Samsung Epic 4G Touch] sfhub:
Updated to include stock FC18, FC22

Updated to include FC18+CWM-Rogue

Added "Lite" version, which includes EG30, EK02, EL26, EL29, and most recent 3 versions of ICS. Most people will only need this. This saves on disk space and download time.

If you have some lesser used versions, then download the Full version.
[Samsung Epic 4G Touch] sfhub:
Updated to include FC22+CWM-Rogue.

Added new feature to "fix" USB Mass Storage Mode for ICS ROMs. Use Option E (Extra Options) then "Enable ICS USB Mass Storage Mode" To get stock behavior, choose "Enable ICS USB MTP Mode"
[Samsung Epic 4G Touch] sfhub:
This is for the FAQ section:

What happened to USB Storage in ICS, how do I get the old GB behavior back?

You may have noticed that ICS ROMs by default will configure the USB port for MTP (Media Transfer Protocol) mode. MTP mode may be more convenient for some people as it can coexist with USB debugging better, but the transfers are much slower and if you don't have the OS driver support (Mac/Linux) the USB drives may not show up.

Most people prefer to have the behavior from GB ROMs where you could drag the notification bar, click on the USB symbol, and manually enable USB Mass Storage mode.

With earlier versions of ICS, you could do this less conveniently using the menu->settings->more->USB Utilities configuration page.

Starting with ICS release FC22, the USB Utilities configuration page is no longer present. This presents the user with a problem as they cannot enable USB Mass Storage using the UI.

The Auto Root package has a solution for you. Under "Extra Options" of the main menu, there are 2 choices that affect ICS mass storage:

1) Enable ICS USB Mass Storage Mode

2) Enable ICS USB MTP Mode

These are mutually exclusive options. If you enable one, you disable the other.

To get GB USB Mass Storage behavior, choose the first option (USB Mass Storage Mode). This option once chosen, will be persistent through reboots and is stored in your Android User Data. It will only get reset if you reset your Android User Data or manually choose a different mode.

This was tested with the FC22 release, but theoretically should work with any of the ICS releases.

Technical Details:

There is a property which controls how the USB storage should behave. You can see the value of this property by typing in "adb shell"

# getprop persist.sys.usb.config
mtp,adb
# setprop persist.sys.usb.config mass_storage,adb
# getprop persist.sys.usb.config
mass_storage,adb

When Android is first installed with a clean reset of the /data partition, this value is retrieved from the default provided in the /default.prop file. The /default.prop file is contained in the kernel's initramfs. Some solutions for the ICS USB Mass Storage annoyance modify the information in this file so the value is set to mass storage mode from the beginning. This does work, but has the side effect of a kernel which is no longer signed by Samsung (ie you'll increase your ODIN flash count and trigger the yellow triangle if you flash in ODIN)

Alternatively, you can set this value after Android is installed and it will be stored persistently in your Android User Data. This is the approach Auto Root takes as I prefer to have packages which do not affect the ODIN flash count nor trigger the yellow triangle.

If you would like to change this value using an App within Android see this entry in Android Market.
[Samsung Epic 4G Touch] Foulwx:
Quick question:

If I enable mass storage mode and later want to go back - will I still be able to run autoroot if mass storage mode is currently enabled?

I may be getting confused about terminology, but I just wanted to make sure before I did this.
[Samsung Epic 4G Touch] sfhub:
I'm kind of overloading the terms. What this does is tell the USB port to BEHAVE as mass storage (meaning it'll show up as drive letters in windows). To actually enable storage mode, you'll still need to drag the notification bar down, press the usb symbol, and turn on storage mode. As long as you haven't enabled storage mode (dragging down notification bar, pressing on USB symbol, turning on storage mode), auto root can still copy the files it needs to the internal sdcard and install stuff from there.
[Samsung Epic 4G Touch] Foulwx:
Thanks for the answer. I really appreciate all the work you've done here.

Edit: After applying the mass storage mode change, everything works as it did before.

FC22 is the first build I've been able to get GPS working without first locking on in EL29 before updating. Yahoo! I've also been getting good notifications. I did have a couple of apps that would attempt to install to usbstorage/sd card and would hang up Titanium Backup or just would not install from the market. The temp solution to that is to unmount the SD card, install from the market, then remount the SD card. I've been using this build since it was uploaded by sfhub, and it's working well.
[Samsung Epic 4G Touch] sfhub:
Added FAQ #e15 - link to writeup from Oscarthegrouch on running Auto Root, ODIN OneClick, and ODIN on Mac using virtual machines:

e15) How do I run Auto Root, ODIN OneClick, or ODIN on Mac?
[Samsung Epic 4G Touch] wildside84:
more than one device and emulator error when trying to install cwm. suggestions?
[Samsung Epic 4G Touch] sfhub:
Can you be more descriptive about what you tried and what error you received. Cut&past of the error would help. I actually have no idea what you are describing. I've never seen an error with the text you describe, but probably it is some error adb is giving? Do you have more than one phone connected to the PC?
[Samsung Epic 4G Touch] wildside84:
I'm trying to put cwm on my phone and I go through the prompts and select el 29 then I just get errors when its trying to push the files to my phone. I only have one phone connected. I restarted my computer and killed the adb process and tried multiple times and I still get that same error. When I get to a computer I can copy and paste everything.
[Samsung Epic 4G Touch] Docarut:
This may sound silly to ask but are you trying to install the CWM of same software version that is on your phone? You probably are but just checking.
[Samsung Epic 4G Touch] darkfire2024:
Forgive me for asking, but does this autoroot work on AOSP roms? (specifically codename 1.5.6 by T.C.P) I know this method doesn't add to ODIN count, and I want to avoid that and the triangle.
[Samsung Epic 4G Touch] wildside84:
Yes i'm on el29. I've rooted and installed cwm before on this phone but it was bricked and sent it to Samsung and they fixed it. Don't know why i'm getting this error of more than one device and emulator. I'll end up trying on a different computer when I get a chance.
[Samsung Epic 4G Touch] sfhub:
If it is a problem copying files, sometimes that is because usb mass storage is enabled (ie your internal sdcard is accessible from the pc. When mass storage is enabled the sdcard is not visible to adb. If you drag the notification bar and press the usb symbol, the android guy should be green, not orange.
[Samsung Epic 4G Touch] sfhub:
If you are asking whether it would install cwm,the mechanism I use to write the kernel/recovery should work fine, however I adb push the files to /sdcard and if that doesn't exist or is called something else, then copying the files would fail. It would be something easy to address if that was an issue. You could just manually adb push the files to the appropriate location and runthe scripts. None of the scripts on the phone care where they are installed, just the windows menu system assumes they are in /sdcard/000root, so you could follow the manual install instructions in the 2nd post
[Samsung Epic 4G Touch] darkfire2024:
Thank you, I confirmed with ES File Explorer that /sdcard/000root does indeed exist so I think I'm good to go.
[Samsung Epic 4G Touch] agaddis:
I've done some searching through the forums for an answer that I'm curious about but not finding to right leads, so I do apologize if the subject has been covered extensively.

My question: Any way to use Mobile Odin to flash these stock GBw/root ROM's?

Thanks.
[Samsung Epic 4G Touch] sfhub:
Yes, mobile odin can use the oneclick files. See the "android" section of fc22 or el29.

Basically you just need to unpack the 7zip self-extractor and feed the oneclick.exe to mobile odin.

Keep in mind mobile odin will not flash cdma modems, has nothing to do with oneclick, so use cwm to flash the modem
[Samsung Epic 4G Touch] wildside84:
But USB storage wasn't enabled.
[Samsung Epic 4G Touch] sfhub:
I said "if"

As I mentioned before, if you enable the scroll buffer in the main menu and cut/paste the iutput I can tell what is going on, otherwise it is difficult to help you because I haven't seen the error you are describing
[Samsung Epic 4G Touch] wildside84:
Getting ready to

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]... error: protocol f

ault (status read)

Found device

Proceeding with install

----

Asking for root permissions...

Please turn ON phone and EXIT the lock screen

AFTER you press any key to continue, if you are PROPERLY ROOTED, you *MIGHT*

see a PROMPT asking for permissions. If so, please ALLOW root access.

Press any key to continue . . .

error: more than one device and emulator

---- BEGIN LOG ----

BOOTIMGNAME = EL29+CWM-Rogue

BOOTIMGFILE1 = zImage-el29

BOOTIMGFILE2 = zImage-el29-cwm-rogue

BOOTIMGSTKREC = no

BOOTIMGSCRIPT = install-boot-el29-cwm-rogue.sh

...Proceeding to copy necessary files...

error: more than one device and emulator

push: copy2sd-img/000root/zImage-el29 /sdcard/000root/zImage-el29

error: more than one device and emulator

push: copy2sd-img/000root/zImage-el29-cwm-rogue /sdcard/000root/zImage-el29-cwm-

rogue

error: more than one device and emulator

----

error: more than one device and emulator

---- END LOG ----

Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.

----

Getting ready to reboot...

This reboot will take slightly LONGER than usual since it will be

recreating Dalvik-Cache.

Your phone MAY be slightly SLOWER for a SHORT TIME after boot is

complete while it performs maintenance.

This is all NORMAL.

Press any key to continue . . .
[Samsung Epic 4G Touch] sfhub:
I think adb is detecting a ghost device.

This can happen if you have other software that opens ports in the 5554, 5555, 5556, ... R

range

To see if that is the case type the command

adb devices

If there is more than one and the other ones aren't your phone, that is probably the problem. You could try and disable the software listening on that port or just try a different computer

ultimately google is the one that wrote adb so the problem lies with them.
[Samsung Epic 4G Touch] :
I don't understand any of what's been posted above. ^^ lol I'm not to smart so I just use this: http://downloadandroidrom.com/file/Epic4GTouch/rooting/e4gtauto.zip

It's an auto script just like this one but the one in the link is the one I used to learn how to flash.

I like this one because it's just pick and choose. I always use the EL29-cwm-rogue recovery at the bottom and I'm flashing everyday like there's no tomorrow. I want to try all of the roms before the disappear or something.
[Samsung Epic 4G Touch] sfhub:
You realize that is just a copy of the tool from this thread right?
[Samsung Epic 4G Touch] :
not really, in fact.

I didn't know that since I've only been doing all of this for 6 days now. ^^ I appreciate the confirmation of it being a duplicate though!

Have a nice day! :D
[Samsung Epic 4G Touch] AreOh:
I am the admin on this laptop, I turned off the antivirus protection and I STILL can not get neither the .exe file or the .rar file to save. I'm out of ideas. I guess I just can not use this method.
[Samsung Epic 4G Touch] sfhub:
Have you tried a different browser?
[Samsung Epic 4G Touch] AreOh:
Chrome and Firefox. What finally did work was that zip two posts up from my last, though. Is that the exact same program?
[Samsung Epic 4G Touch] sfhub:
It is some version of it. They just copied it so i can't vouch for the contents

Btw i just dowloaded both "lite" versions using the stock e4gt phone browser and it was fine.
[Samsung Epic 4G Touch] AreOh:
I don't know why I didn't think of using this browser to save the zip and then copying over to my laptop, smh.
[Samsung Epic 4G Touch] sjsharksfan420:
@sfhub hey bro, I have a question on how to flash a custom kernel with your auto root tool. With the latest CM9a2, I ran a good backup with the EL26/cwr5 and all is good, but when I restore the backup, the rom doesn't boot until I get the correct kernel flashed. So, I have the "kernel" file extracted from the main directory of CM9a2. Do I rename that file to zImage and put on my phone in the copy2sd/000root folder?

How would I flash that kernel with your tool? Is that even possible?

Edit: I just realized that this way will not work for what I was thinking about since this process would require that I am booted and have USB debugging on and in this situation I would need to flash through download mode. So until I get my USB jig, I will hold off on my nandroid that is needing this process for restore..

sj

Sent from my SPH-D710 sgs2e4gt on CM9a2 FC24 AOS 4.0.4 using Tap@Talk 2 Beta 4
[Samsung Epic 4G Touch] TorelliB:
EL29 - Adding CWM Clarification

Flashed the stock EL29 w/root preserve data. Good to go. I just want to make sure what im supposed to install to get cloockwork. The latest on the Menu for the auto is EL13...Flash that?? or is there something else im supposed to flash to get CWM?
[Samsung Epic 4G Touch] sfhub:
You don't need to be booted into android. El26+cwm has adb enabled so you can run auto root while booted into recovery.

place the zImage you want in copy2sd/000root

Boot into el26+cwm, go into mount menu and mount /sdcard (also verify /system is already mounted)

Then choose option C (or D) and install generic zImage)
[Samsung Epic 4G Touch] sfhub:
You probably have an older version. Try redownloading. Lite version is all you need. Full is fine too, just a larger download.
[Samsung Epic 4G Touch] sjsharksfan420:
ok, so say I pulled the kernel from CM9a2, do I have to rename that kernel (cause they labeled it "kernel" I think) to zImage and put that in the copy2sd/000root folder on my phone? Then follow the process above from recovery? Sorry that I sound like a n00b I just havent run your tool with a custom kernel yet, ever since you helped me a few months back, I use your tools every time I flash ics so I can get back to gb safely, so I think your tools are a must for folks that flash anything.. I just have always used your kernels that you put in the tool..

I will feel dumb though if all I needed to do was rename it and I'm good.. cause I just don't want to do it the wrong way..

thanks again for your help sf!

sj
[Samsung Epic 4G Touch] TorelliB:
Thank you sir, figured it out :) You the MAN!
[Samsung Epic 4G Touch] sfhub:
Yes, just rename as zImage , case-sensitive.

There is a video on the first page showing the process when the kernel you want is already named zImage
[Samsung Epic 4G Touch] sjsharksfan420:
thank you SF, much appreciated! :)

sj
[Samsung Epic 4G Touch] sjsharksfan420:
SF, are you planning on releasing a new version with FD02 included as well?

sj

Sent from my SPH-D710 sgs2e4gt on CM9a2 FC24 AOS 4.0.4 using Tap@Talk 2 Beta 4
[Samsung Epic 4G Touch] sfhub:
Yes, will be there in about 2hrs. There is no FD02+CWM though, so it would still use FC24+CWM-Rogue and FD02 would be just to return to stock kernel.
[Samsung Epic 4G Touch] sfhub:
Updated to include stock FD02.
[Samsung Epic 4G Touch] AreOh:
With every leaked rom + kernel we have to re download the lite file?
[Samsung Epic 4G Touch] sjsharksfan420:
yes, or the full version, and that is only if you want to be able to install the latest kernels with sfhubs excellent tool..

if you dont need to flash the newest kernels, then you dont need to redownload.. but it is recommended to always have the latest imo..

sj

---------- Post added at 01:00 AM ---------- Previous post was at 01:00 AM ----------

outstanding, thank you sir!!

sj
[Samsung Epic 4G Touch] reldridge:
Thanks for the info - Been crazy busy haven't had a chance to try this yet, but I am not sure where the Odin one Click noData version is?

Any more help/instructions would be great so i could get the phone updated to the latest release and the ability to re-root the phone.

Thanks.
[Samsung Epic 4G Touch] sfhub:
Updated to include FD02+CWM-Rogue.
[Samsung Epic 4G Touch] sfhub:
Pick which version you want from my signature. Follow the directions in the thread. If you can't see my sig, it is provided here:

http://xdaforums.com/showpost.php?p=23478866&postcount=869
[Samsung Epic 4G Touch] sjsharksfan420:
And thank you sir once again :)

sj

Sent from my SPH-D710 sgs2e4gt on CM9a2 FC24 AOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] Foulwx:
Just tried to update to FD02+rogue with e4gtauto-sfx.exe lite version, but I got FC24. Tried twice.

Anyone else seeing this?
[Samsung Epic 4G Touch] sfhub:
Sorry about that, I messed up the menu system choice on the lite version (the full version was done right). Will reup right away.
[Samsung Epic 4G Touch] Esoteric68:
Since I'm only on my second custom ROM trial ever I'm unsure if it's safe to flash recovery. Will it be okay?
[Samsung Epic 4G Touch] sfhub:
If you are asking whether this tool would work with a custom ROM, from the standpoint of the flashing mechanism it should work fine. In the process of copying files to your phone as a staging area for the flash though, it does assume your internal sdcard is mounted as /sdcard, so if that doesn't exist and/or was renamed for some reason on your custom ROM, then the copying wouldn't work even though technically the flashing of the kernel would have worked. I think most custom ROMs still have internal sd mounted as /sdcard, but can't speak for all of them.

One other thing, if you are going back and forth between ICS and GB ROMs, be aware, that a GB kernel will not boot an ICS ROM and vice versa (though you can still use Power+VolUp to get into CWM recovery to do backup/restores/flashes) Nothing "bad" will really happen, it'll just hang at boot.

So if you want something that boots into Android, then stick with ICS kernel/ICS ROM or GB kernel/GB ROM. If you just need to get into recovery and don't care about it booting, then any kernel will do.
[Samsung Epic 4G Touch] Esoteric68:
Whew, just checked and I should be fine.

Thank you for your quick response. :)
[Samsung Epic 4G Touch] sfhub:
I might have made it sound more dire than it is. Nothing "bad" would have happened if your internal sdcard wasn't mounted as /sdcard, the tool would just give a bunch of error messages that it couldn't copy the files. Anyway, doesn't sound like it will be a problem for you.
[Samsung Epic 4G Touch] Esoteric68:
I'd much rather you err on the side of caution (making it sound more dire than it is) than play it off as no big deal. I'm still learning and need those bumper guards (bowling anyone?) to keep me out of the brick gutter.
[Samsung Epic 4G Touch] sfhub:
> Sorry about that, I messed up the menu system choice on the lite version (the full version was done right). Will reup right away.

Ok, both e4gtauto-lite-sfx.exe and e4gtauto-lite.zip have been fixed and reuploaded.

Apologize for the inconvenience.
[Samsung Epic 4G Touch] Foulwx:
Thanks! Getting repetitious, but I really appreciate your work. Makes things very easy and quick.
[Samsung Epic 4G Touch] sfhub:
Updated to include stock FD05.
[Samsung Epic 4G Touch] billykent1972:
I bricked mine doing the FD02 update on 32% battery..i know..lol... so I ran this "[ODIN][TAR] SPH-D710.FD05_CL355991 (FD05 Modem/Kernel/ROM - Full Restore - Rooted)" got it going fine...then ran this app..the exe version. the whole thing ran fine, found my phone..did everything perfect, rebooted my phone and I still have stock, no CWM??? Ideas please?
[Samsung Epic 4G Touch] Docarut:
I also cannot figure out how to add CWM other that downgrading FD02+CWM using Auto Root.
[Samsung Epic 4G Touch] sfhub:
There is no FD05+CWM-Rogue from Steady, so if you installed FD05, that is the stock kernel. If you want CWM, install FD02+CWM-Rogue. It will work fine.
[Samsung Epic 4G Touch] billykent1972:
Ok, was guessing that was what it was, just read it wrong, Thanks Docarut and Sfhub!
[Samsung Epic 4G Touch] sjsharksfan420:
Hey SF, here's a mirror link for your latest version of your autoroot tool.. (removed)

I know we don't really need it.. but its there just in case.. (decent speeds too)

sj

since most devs dont want random mirrors no matter how quick the dl speed is, I will avoid any issues and take my mirror site down..

Sent from my SPH-D710 sgs2e4gt on AoKPb31 FD02 AOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] RainMotorsports:
Main problem with mirroring the auto root tool is it gets updated every couple of days and goes out of date quick. If there was a serious bug and all copies can't be taken down or fixed quickly then the developer has an issue on their hands. While he doesn't host it on my mirror at this point if he did he has full access to delete the file when needed etc. Just pointing out the real issues dont feel bad.
[Samsung Epic 4G Touch] sfhub:
Updated to include stock FD10 kernel.
[Samsung Epic 4G Touch] Wacky2bakky:
Question Everyone???

I am currently on the FD05 Kernel in which I don't have CWM on in order to flash any zips. I am wanting to switch themes on the Anakonda ROM. I understand I can get the FD02 Kernel w/ CWM through the autoroot.exe program but I'm currently at work and can't use that on my work PC. Is there any other way for me maybe to use Mobile ODIN or something to get CWM back on my phone? Even If i have to switch Kernels, thats ok. any help would be awesome :-)
[Samsung Epic 4G Touch] sfhub:
Just download the zip package on your phone and look in the copy2sd-img/000root directory. It has the FD02+CWM-Rogue zImage. Flash that in Mobile ODIN. Also unpack stock F05 zImage if you want to go back to that.
[Samsung Epic 4G Touch] sjsharksfan420:
That downloadandroid site is terrible! Very outdated already.. if ppl are going to take the time to create a mirror site.. the least they could do is keep it up to date. Its a shame though cause most if not all developers do not give their permission to post their files. I was going to do this too, but I quickly found that its not worth it to do cause if its not complete, then its not very useful. If all devs don't give their OK to post their files, then it won't be complete. Just m2c...

sj

Sent from my sgs2e4gt on AoKPb32 FD10 aOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] sjsharksfan420:
SF, do you have access to the FD16 modem or kernel yet?

sj

Sent from my sgs2e4gt on AoKPb32 FD10 aOS 4.0.4 using Tap@Talk 2 Beta 5