yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] sjsharksfan420:
I meant to reply to this before.. I don't feel bad, I just was offering my server if needed.. I understand though. No worries.. but I was planning on keeping up on the file updates and versions for sure..

One thing I found out after I removed my feeds was that my hosting company doesn't allow for file hosting for the type of account/server I am on.. so for that too, its all good.. :)

sj

Sent from my sgs2e4gt on AoKPb32 FD10 aOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] TheGman125:
Has anyone had issue with the auto root not rooting the devices. So what is an alternative?

Sent From NS4G, E4GT, and Mopho all running CM9
[Samsung Epic 4G Touch] sfhub:
It is usually very consistent with rooting, but only EG31/EG31/EK02.

Starting with EL13, they plugged the exploit being used, and the new method is to use the pre-rooted ODIN OneClicks referenced in the first post.
[Samsung Epic 4G Touch] sfhub:
You probably already saw, but these are available here:

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

I'll update Auto Root to include FD16 in a few hours.
[Samsung Epic 4G Touch] sfhub:
Packages updated to include stock FD16 kernel. I'll update the jpgs in the post later.
[Samsung Epic 4G Touch] sjsharksfan420:
Yep, downloaded as soon as I saw you posted.. I always keep a closer eye on the forums after the rdf pages drop cause as most, I know your tools follow very soon after.. :)

Thanks again SF, your tools are excellent!

sj

Sent from my sgs2e4gt on AoKPb32 FD10/16 aOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] sfhub:
Updated to include stock FD19.
[Samsung Epic 4G Touch] sjsharksfan420:
You ROCK SF!

Sent from my sgs2e4gt on AoKPb32.2 FD16/FD19 aOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] sfhub:
Added an Experimental feature to add init.d support to any stock kernel

You need to be rooted.

Choose Option E (extra options), then Option E (Add init.d support)

I've tested it on FD19 and EL29 and stock ROMs.

I have *not* tested in on AOKP. It doesn't modify your kernel, so I don't anticipate anything bad would happen.

I've also tested it in the case where you start with stock kernel, add init.d support, then later install a repacked kernel with builtin init.d support. In that case this will defer to the builtin init.d support in the kernel so the init.d scripts are not run twice. What that means is you don't need to remove this if you should later switch from stock kernel to stock kernel+CWM. If you want to remove it, just choose Option F (Remove init.d support)

If you install a new ROM, then you will need to re-run this option to add init.d support, if the included kernel does not have builtin init.d support.
[Samsung Epic 4G Touch] sfhub:
Added stock FD24 kernel.

Added wipe dalvik-cache option to Option E - Extra Options.

Enhanced init.d support to work with products which may also use install-recovery.sh like link2sd.
[Samsung Epic 4G Touch] sjsharksfan420:
Any access to FD26 yet?

http://device.sprintpcs.com/Samsung/SPH-D710/FD26.rdf

sj

Sent from my sgs2e4gt on AoKPb34 FD24 on TabletUI @ 128 dpi aOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] DataHawg:
Your Auto Root program has really grown up, sfhub. I remember when it was a simple tool to root EG30 and add CWM
[Samsung Epic 4G Touch] sfhub:
Thanks, these are just tools I use myself so I figured I'd make them available for others.

Anyway, added stock FD26 kernel.
[Samsung Epic 4G Touch] sjsharksfan420:
Me too! I still have a copy of that one :) I keep copies cause ya never know when you might need that one.. it takes up a few gigs.. but all good. :)

sj

Sent from my sgs2e4gt on AoKPb34 FD24 on TabletUI @ 128 dpi aOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] sjsharksfan420:
Bro.. these tools are what is making our devices what they are today.. Samsung wouldn't be nearly as close to final with out this community and we wouldn't be where we are with out your tools.. :)

sj

Sent from my sgs2e4gt on AoKPb34 FD24 on TabletUI @ 128 dpi aOS 4.0.4 using Tap@Talk 2 Beta 5
[Samsung Epic 4G Touch] nerdslogic:
I am getting a fail.....all threads completed. (succeed 0 / failed 1)

---------- Post added at 11:40 AM ---------- Previous post was at 11:37 AM ----------

I keep getting the fail after SetupConnection.. then blank line...
[Samsung Epic 4G Touch] sfhub:
If this is regarding ODIN OneClick, please post on the appropriate thread for that version.

As to your question, please post the full log. Just "fail" isn't enough to go on.
[Samsung Epic 4G Touch] nerdslogic:
oops....too many tabs open
[Samsung Epic 4G Touch] sjsharksfan420:
hey SF, with the latest zip file for this tool, I get invalid zip when trying to run the auto-extract tool on my pc. All previous versions worked (except 1 that I can remember that had this same error) but this latest that you added FD26 stock kernel to is the one in reference to here.

sj
[Samsung Epic 4G Touch] sfhub:
I will check it out.

Is it possible your download was not complete?

These are the MD5s for the packages:

55ed466d835306b4ace123cef44526d4 *e4gtauto-lite-sfx.exe
f87bb81ea605a96513d663e00738af52 *e4gtauto-lite.zip
3b8314a1588074be347beab51596bc21 *e4gtauto-sfx.exe
83e305310627dd05c45326b90d92625c *e4gtauto.zip

I will redownload the 2 zips and confirm whether I can reproduce.
[Samsung Epic 4G Touch] sjsharksfan420:
getting zip data error to be exact..

sj
[Samsung Epic 4G Touch] sfhub:
Could you run md5 checksum on the file?

http://www.winmd5.com/

I downloaded both the full and lite versions. I unpacked using 7zip and using native windows zip support. Neither one gave errors.

Is it possible it is a bug in the app that is doing the unpacking for you?
[Samsung Epic 4G Touch] sjsharksfan420:
Hi SF, I haven't made any changes and can still launch previous versions without any issues, just the latest. I redownloaded the file, I checked the md5sum too, it matches. I am rebooting my pc now and I will advise further..

sj

Sent from my sgs2e4gt on AoKPb34 FD24/FD26 on TabletUI @ 128 dpi aOS 4.0.4 using Tap@Talk 2 Beta 6
[Samsung Epic 4G Touch] sjsharksfan420:
I have rebooted SF, I still get the same error, it looks like it doesn't extract all the way and gives zip data error..

sj

Sent from my sgs2e4gt on AoKPb34 FD24/FD26 on TabletUI @ 128 dpi aOS 4.0.4 using Tap@Talk 2 Beta 6
[Samsung Epic 4G Touch] sfhub:
Are you using windows? What does the standard zip support in the OS do? Just click on the .zip in explorer and drag/drop the e4gtauto folder out. Alternatively, what does 7zip do? http://www.7-zip.org/

Is it possible your virus checker is intercepting the file open request and not handing over the file in time to the zip extractor, so while the file you have is complete, the file that gets handed off to the zip extractor is not?

If you have the same md5, you have the exact same file I have and I'm not having problems extracting the contents.
[Samsung Epic 4G Touch] sjsharksfan420:
I am running win7 and using 7zip as well. I'm stumped though cause I'm not doing anything different and haven't made any changes so its confusing. BUT I did download the lite version and it will work so I'm not needing anything further. Thanks for your hard work SF!

Just so you knew what was happening, I dl the file, md5 matches, click the file to run, it starts extracting, gets to about 40% - 50% and then errors out saying zip data error.

sj

Sent from my sgs2e4gt on AoKPb34 FD24/FD26 on TabletUI @ 128 dpi aOS 4.0.4 using Tap@Talk 2 Beta 6
[Samsung Epic 4G Touch] darren.wlsn1:
oh. lol

ty
[Samsung Epic 4G Touch] sfhub:
2&3 are completely unaffected by this rooting method. If it worked before, it'll work afterwards.

1&4 I don't really do and probably wouldn't suggest doing even on stock as it is better to get community feedback on what an update does then update on your own schedule rather than pulling something from Samsung/Sprint that might put you in a situation you might not like.
[Samsung Epic 4G Touch] kgatlanta:
Thanks? Can you point me to the most reliable way to enable wifi tethering after I have gained root?
[Samsung Epic 4G Touch] darren.wlsn1:
dl wifi apk and launch it.
[Samsung Epic 4G Touch] puertoblack2003:
I did that and it didn't work.I'll try again................
[Samsung Epic 4G Touch] sfhub:
Did you have root before you ran Option C?

Did you get any errors when you ran Option C?

How did you verify whether it "worked" or not?

Download the eg30auto.zip again, run Option C, and post the output between "BEGIN LOG" and "END LOG"
[Samsung Epic 4G Touch] jdubdieslo:
Thank you so much. No more los for me. I loved starburst but i had los almost every 1-2 hours. On stock ive never had los. Thanks again.
[Samsung Epic 4G Touch] nebrando:
If I flashed chris41's stock kernel with cwm and subsequently installed su and busybox and I want to unroot, will I be able to use the unroot script to unroot? Has anyone tried this yet?

I'm thinking the only thing that may cause problems is if the version of su and busybox is different from the version that gets installed with this script, but I'm not sure.

Thanks in advance.
[Samsung Epic 4G Touch] darren.wlsn1:
to unroot if your not sure this will work in your case just odin stock EG30 if your sending phone back.
[Samsung Epic 4G Touch] sfhub:
As long as you installed "su" and "busybox" in the ROM (/system/bin or /system/xbin) (rather than in the kernel initramfs) the uninstall script should work fine. It'll remove the symlinks (safely) too. Also Superuser.apk is assumed to be in /system/app.

If you installed them in some other directory, the tne script doesn't check and you might end up with two copies.
[Samsung Epic 4G Touch] darren.wlsn1:
sorry op i read that wrong.
[Samsung Epic 4G Touch] sfhub:
So I looked at chris41g's kernel a little closer. It packages a builtin busybox and when you "install" busybox through installbusybox.zip, it just creates symlinks in /system/xbin to the busybox in /sbin.

The unroot in this package should remove the "symlinks" you created when you "installed" busybox, so yeah it will "uninstall" the busybox that you installed.

However you still have busybox builtin to the kernel/initramfs and that won't be touched.

What are you trying to accomplish?
[Samsung Epic 4G Touch] nebrando:
Basically, I am trying to return to stock without losing my current setup and app data. Ever since flashing this kernel and rooting, my battery life has sucked and I wanted top return to stock, keeping everything the same. At that point, if the battery continued to drain I would know I could look somewhere else for the culprit. Also, I would like to be able to receive OTA update again when the first one comes out. I rooted because I wanted to use tethering over the weekend because I was spending a lot of time in airports this weekend and wanted to use my laptop.
[Samsung Epic 4G Touch] sfhub:
If it were me, I would just, ODIN - crawrj's stock EG30 kernel (pulled) + stock EG30 ROM (pulled)

See reference A4 in the second post.
[Samsung Epic 4G Touch] nebrando:
I was under the impression that ODINing a ROM will wipe all my data, etc.

Is this not true?

Sorry for being a noob about this...
[Samsung Epic 4G Touch] sfhub:
When flashing the stock pulled through ODIN, unless you choose to wipe your data (on your own) through recovery, privacy->reset, or ##786# reset, it shouldn't touch your /data.

You should however wipe cache/dalvik on your own (from recovery) after the flash.
[Samsung Epic 4G Touch] darren.wlsn1:
exactly what i told him, i did it to send back a broken signal epic.
[Samsung Epic 4G Touch] nebrando:
Thank you so much!! You have been very helpful this morning. Just so I understand correctly...

1) ODIN the file referenced in above post. (place in PDA section with only auto reboot checked)

2) Turn off after reboot and boot into stock recovery

3) Wipe cache/dalvik cache

4) reboot

Does this look accurate to you?

Thanks again for your help
[Samsung Epic 4G Touch] sfhub:
Looks fine to me.
[Samsung Epic 4G Touch] sfhub:
Pretty much the same thing, but I think he got sidetracked by the "sending the phone back" qualification and his own incorrect impression that flashing EG30 would wipe his data, something that would be unimportant for someone sending the phone back, but important to him, since he isn't sending it back. Once the impression got corrected he became amenable to the suggestion.
[Samsung Epic 4G Touch] sfhub:
Apologize, for some reason my brain kept thinking you were talking about the .zip file. I realize now you were talking about the -sfx.exe file. I duplicated the problem and will get it fixed.

Sorry again.
[Samsung Epic 4G Touch] sfhub:
This should be fixed now.
[Samsung Epic 4G Touch] sjsharksfan420:
thanks bro, I was hoping i wasent loosin it! ;)

sj
[Samsung Epic 4G Touch] Kikoshi:
Question -

Is it possible to Install EL29 * OTA * Then install the EL29+CWM Kernel from here, then through the kernel flash su-3.05.efgh-signed.zip file? to enable root instead of having to use Odin to flash a nodata EL29 rom ?
[Samsung Epic 4G Touch] sfhub:
No.

1) Installing EL29+CWM-Rogue using this tool requires root, which you won't have after installing the OTA

2) The stock recovery will check if the su-3.05.efgh-signed.zip file is signed by Samsung, find it isn't, then fail.

You can ODIN EL29+CWM-Rogue and do what you want. However you will trigger the yellow triangle and increase the odin flash count. If you don't care or will reset using USB jig or upgrade to ICS and use Triangle Away, then it can do what you want. However, it seems ODIN was what you were trying to avoid in the first place.
[Samsung Epic 4G Touch] Kikoshi:
Thank you for the reply ,

Well i don't mind using Odin since i have a Jig. The only thing i want to evade is having to reinstall everything fresh, if the NoData Rom failed.

But then, the way you mention is that if i Odin EL29_CMW-Rogue, and after i odined this kernel, i can go ahead and Flash the su signed.zip file, and it will work?

Also is EL29 Rogue kernel, the only one i can use with el29?

thanks once again man, keep up the great work!
[Samsung Epic 4G Touch] sfhub:
If you want EL29 with CWM then EL29-CWM-Rogue is the only published one. I think some folks might have private builds of EL29+CWM.

BTW if EL29 NoData fails, very likely, so would the EL29 OTA. They are essentially doing the same upgrade, but EL29 NoData will work in more cases because it doesn't care if you have modified or deleted files/apps from /system as it is going write a full copy of the EL29 /system
[Samsung Epic 4G Touch] Kikoshi:
I feel like an idiw,I didn't even see it on your first sentence lol,sorry for being a pain with my question, and thank you loads for the answer!

So basically I just flash the el29rogue kernel and I can flash su . Zip and it will work,since the modded kernel will accept the zip,and ill have root! Awesome, thank you again :)
[Samsung Epic 4G Touch] sfhub:
In case it wasn't clear, ODIN of EL29+CWM-Rogue will only give you the EL29 kernel and a recovery that will flash the su zip. To get the EL29 ROM you would have needed to flash the EL29 OTA. It is actually far fewer steps to flash the NoData ODIN OneClick and the net results are the same.
[Samsung Epic 4G Touch] Kikoshi:
hah, I just went ahead, and did how you mentioned, and it went wonders without errors :).

Thank you! and sorry for the miss understanding.
[Samsung Epic 4G Touch] sfhub:
First post updated to include FE07 stock kernel and also FE07 Plus repack. FE07 Plus comes with unlocked recovery so you can flash using stock recovery as well as init.d and adb-root support. adb-root allows you to connect to your phone using adb while in recovery and have a root prompt. This allows you to repair things like bootloops while on the stock kernel.

I'll update the pictures and description later.
[Samsung Epic 4G Touch] wraith404:
When I flashed the CWM Repack for ICS (FD02+CWM I think) after the full FE07 ODIN, My phone stopped recognizing any apps that I had moved to SD, and I started getting the somewhat infamous market error "cannot install to USB/Sd" on installs. Flashing back to the stock FE07 kernel corrected the problem.

Is this a random occurrence, or does it indicate we will need a new CWM repack?

Thanks
[Samsung Epic 4G Touch] sfhub:
It seems some people are having issues with apps installed to sd with any repack. Trying to figure what the cause is on the FE07 thread.
[Samsung Epic 4G Touch] RainMotorsports:
oops nvm
[Samsung Epic 4G Touch] zarthan:
Whenever I have had trouble installing I have found that if I umount the SD card that I can install apps. Once the app is installed i mount the SD card and everything works.
[Samsung Epic 4G Touch] wraith404:
I did try that first this time, to no effect.. I went down the rabbit hole of stunts to clear the triangle (though I didn't have one), but in the end reverting to the stock FE07 recovery did the trick.
[Samsung Epic 4G Touch] sjsharksfan420:
FE10 rdf posted..

http://xdaforums.com/showthread.php?p=25938803

sj

Sent from my SGS2 Epic 4G Touch on AoKPm5 FE07 OS4.0.4 with dpi @ 128 using Tap@Talk 2.1 Pro
[Samsung Epic 4G Touch] sfhub:
OP modified to include stock FE10, and FE10 Unlocked and Plus repacks.
[Samsung Epic 4G Touch] sjsharksfan420:
SF, I have a qq, I needed to use mobile Odin to flash EL26/cwr5 kernel and I have one that is "StockCWM-EL26.tar.md5" and is 8.01mb. I also have one that is " update-kernel-EL26.zip" and that file is only 5.08mb. Can I flash either one as is with mOdin? Or should I rename the files to ".tar"

Also, I just use the kernel slot and click flash firmware?

sj

Sent from my SGS2 Epic 4G Touch on AoKPm5 FE10 OS4.0.4 with dpi @ 128 using Tap@Talk 2.1 Pro
[Samsung Epic 4G Touch] Razorwindmo46:
I know what rooting is but don't understand anything about flashing. Wish someone would write these in laymans/noob terms
[Samsung Epic 4G Touch] sfhub:
Tar.md5 is larger because it is not compressed. Use open file in mobile odin. Update.zip is cimpressed and meant to be flashed in cwm or unlocked recovery. However you can also flash in mobile odin, just open the zip archive and pull out the zImage file. You can flash that as a kernel in mobile odin.
[Samsung Epic 4G Touch] zarthan:
The original post has a link to a QBKing video partway down the page.

Videos by qbking77 [Install Root / Install CWM] thespotlite [Install ANY User-Provided zImage/Recovery]

Search on youtube for QBKing77 and look for the Epic Touch for more / other rooting videos.

I would do as much reading as you can before you start rooting and when you have specific questions post them before you get started.
[Samsung Epic 4G Touch] sjsharksfan420:
FE16 rdf info:

http://device.sprintpcs.com/Samsung/SPH-D710/FE16.rdf

Hey SF, do you plan on including both FE14 & FE16 in the latest auto root tool?

sj

Sent from my SGS2 Epic 4G Touch on AoKPm5 FE10 OS4.0.4 with dpi @ 128 using Tap@Talk 2.1 Pro
[Samsung Epic 4G Touch] texas83:
If I am on CM9 Alpha 3 - Can I use Option D to install FE10 kernel with CWM built in? I hate using odin to flash stock kernel every time i want to flash an update!
[Samsung Epic 4G Touch] sfhub:
FE10 kernel does not have CWM. It has unlocked recovery.

If you are flashing ROMs, especially CM9, AOSP, AOKP, you are safest going back to GB-based kernel with CWM, for example EL26+CWM. This is available in the GB kernel section (Option C). Once you install the GB kernel, your ICS ROM will no longer boot, but you can still boot into recovery Power+VolUp. From there you can do your CWM operations.
[Samsung Epic 4G Touch] sjsharksfan420:
I felt the same way until I used mobile odin. Now I just do my flashing on device when I'm not at the pc.. i still use the pc for special stuff that you can't use mOdin for, like sfhub's killer tools. ;).. you should check it out, well worth the $5

It also seems to be quicker too.. EL26/cwr kernel flashes very quick

sj

Sent from my SGS2 Epic 4G Touch on AoKPm5 FE16 OS4.0.4 with dpi @ 128 using Tap@Talk 2.1.1 Pro
[Samsung Epic 4G Touch] sfhub:
Updated to include stock FE14, FE16

FE16-Plus, FE16-Unlocked
[Samsung Epic 4G Touch] wraith404:
Thanks yet again.

---------- Post added at 08:09 PM ---------- Previous post was at 07:15 PM ----------

It seems the full normal (non sfx) is still the old version. All the other links are on staging 21, vs staging 20.. I tried full non first, then full sfx.

What is the difference between lite and full by the way? I've always been afraid lite won't have what I need.

---------- Post added at 08:11 PM ---------- Previous post was at 08:09 PM ----------

I've compiled a short list of apps that have problems with custom kernels, just to help people identify what not to move to SD for now, I hope this is more useful than spam... These are just those castaway by my own couple hundred base.. :)

Air control

Angry birds rio

angry birds space

bejeweled

captain america

currents

fruit ninja

GLWG

gravity burst

HDR Camera +

NFS Hot Persuit

Kids Connect the dots

msecure

navigon

sentinel3

Shine Runner

Simplz Zoo

Talking Tom 2

Temple Run
[Samsung Epic 4G Touch] sfhub:
Thanks, I fixed that link. Lite versions have select kernels, EG30, EK02, EL26, EL29 plus roughly the last 3-4 versions of ICS. Also it includes their CWM counterparts if available. The full versions include EVERY stock kernel ever released and their CWM counterparts.

You can use this as a repository of kernels to flash in Mobile ODIN if you like. One download gets you all the kernels to try, instead of multiple downloads.
[Samsung Epic 4G Touch] sfhub:
I've actually determined what is causing the error, but not what is causing the condition that brings about the error.

The reason the error is happening is for some people the repack kernels are not mounting .android_secure from the internal SD. However they are still telling the apps that external storage is available. When you install an app that checks if internal "move to SD" space is available, the system says yes, but since .android_secure isn't mounted by Vold, there is no space on it. Often in this situation, if you insert an external SD, then it will allow you to install new apps, but your old apps that were installed to internal SD are not accessible.

For other people, the reason it isn't happening, is their phones always mount .android_secure from the external SD (regardless of whether they use the stock or repack). So if you have an external SD installed, than installing those apps works (as does Move to SD), but if you remove the external SD then those apps installed to external SD are no longer available.

I happen to be in the latter category, which complicates me figuring out what is producing the scenario where .android_secure is mounted from external SD. It all works the same for me whether using stock or repack. I don't dispute the issue is happening as I have mount tables from folks that show me what is happening. I just can't reproduce the behavior where the phone mounts .android_secure from internal SD, even using the stock untouched kernel.
[Samsung Epic 4G Touch] The Root:
I've thought about this lots. Can it have to do with people moving an sd card from an old phone where .androidsecure has been created before? I've had this issue and the workaround of unmounting has worked, leading me to believe that it's having a hard time choosing where to go,
[Samsung Epic 4G Touch] sfhub:
If you look at the mount table you can usually tell if that is the issue.

Just type

mount

in adb shell
[Samsung Epic 4G Touch] wraith404:
My son is one without an external SD, and I had him back up his SD (USB Storage), format USB storage, reboot, restore vital files, the reinstall affected apps. It seems to have worked for him, he was able to move apps to SD and update them, so the theories about prior version format / mount definitions might be on track. I use both internal and a 16GB external card, It's going to take me a bit longer to backup / reformat / recover both of them, but I'm working on it now.. will post later with my results. Backing up a little, my son's issues were while using the stock el16 recovery.. not sure if that is meaningful, just data for the pot.

Formatting both of my SDs made no effect.. oh well.