yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] pbsst7:
Yeah, unfortunately it looks like I am still stuck on data.img as well. :(

Had such high hopes. Thanks so much though sfhub.
[Samsung Epic 4G Touch] caspersfi:
Damnit.....thanks for your efforts sfhub.
[Samsung Epic 4G Touch] dadoc04:
i cant believe this is happening... im still kinda shocked about the whole thing

good luck to everybody.... and a HUGE thank you to SFHUB
[Samsung Epic 4G Touch] caspersfi:
I know....like I said in the op, I always thought that as long as we can get into odin were good. I learned alot from this for sure.
[Samsung Epic 4G Touch] bleyten:
If I were you I'd make a stink and tell them how you get on the web and tried some things to fix it after their update jacked up your phone!!
[Samsung Epic 4G Touch] sfhub:
I am unsatisfied, because I feel like this is a solvable problem once an understanding of why it is happening is revealed.

If I had a spare phone and insurance I would go ahead and try real hard to duplicate it, but unfortunately I actually need my phone.

I will try and think of more ways to attack this problem, but I'm thinking most people may have gone ahead and got their phones replaced because they need to use them.
[Samsung Epic 4G Touch] pbsst7:
Im kind of stuck with it..... because bonehead me got rid of my insurance a month ago..... damn.
[Samsung Epic 4G Touch] dadoc04:
Just went thru and thanks'd a ton of posts.... sfhub, i cant thank u enough
[Samsung Epic 4G Touch] YoungAceAtlanta:
Whoever recommend flashing CWM Touch shouldn't anymore.. because it screwed my phone up during data wipe and restore.. after that it just stop working.

i had restored my phone without CWM using a .tar and i should of had stuck to my method smh.. my own blame listening to others -_-

---------- Post added at 08:23 PM ---------- Previous post was at 08:13 PM ----------

You shouldn't feel bad.. over 1,000 post probly get posted about others being careless and letting their phone fall into water 5 times or losing it.. i know a friend who return his phone 7x in one year.

But most likely mines came from flashing CWM Touch and wiping with it.. or restoring. i should of had stuck witht he Odin .tar method of restoring
[Samsung Epic 4G Touch] arehm:
Any chance some fashion of repartition with Odin would clean things up? Just a WAG.
[Samsung Epic 4G Touch] pbsst7:
I'm just glad that you guys are still trying. I would love if we could solve this little puzzle. I agree that if FEELS like it should work.

I definitely have some serious donation money for anyone who could do this.

So stumped.
[Samsung Epic 4G Touch] sfhub:
You are welcome to try also and give another data point.

Some people earlier tried and it didn't work.

The last ODIN One-Click I posted forced a repartition and the data.img still failed to flash.
[Samsung Epic 4G Touch] caspersfi:
I've had to move on. Will have my replacement phone in a couple days. I do hope something good comes out of this and sfhub or someone figures out a solution.
[Samsung Epic 4G Touch] arehm:
has anyone stuck tried to load the new tar for ICS?
[Samsung Epic 4G Touch] bleyten:
I tried this morning and couldn't get it to boot either way (zip on card or tar in odin)
[Samsung Epic 4G Touch] arehm:
anyone else with this problem finding the phone won't keep a charge? It's like it's running away, even when it's not. mine's very warm to the touch at the top.
[Samsung Epic 4G Touch] huskerpat:
I'm so flipping screwed. Sprint already replaced my phone yesterday and I'm getting this error today. can't format data. can't wipe data. can't restore a backup. can't odin a stock recovery.
[Samsung Epic 4G Touch] arehm:
Now all i get is a flashing blue light on mine, slow and dim. I can't get it to charge to even get back into Odin mode. I've tried to pull the battery, and when I put it back in i get the regular error message about a failed upgrade, then nada. Suggestions?
[Samsung Epic 4G Touch] pbsst7:
Battery is dead or low? That happened to me last night.
[Samsung Epic 4G Touch] arehm:
Been on the charger all the time.
[Samsung Epic 4G Touch] huskerpat:
I'm trying the one click fb17 you posted last night and I'm still hanging at data.img.
[Samsung Epic 4G Touch] sfhub:
Something is messed up with your /data partition. It isn't a problem with the one-click.

If we can figure out how to fix that, then cwm, odin, and odin one-click will all start working
[Samsung Epic 4G Touch] huskerpat:
At one point last night, I was able to odin the el26 kernal and formatted data. I immediately tried to flash a rom, it went thru, but hung at the boot logo.

I just repeated this. It's bootlooping at the samsung logo. sigh...

Your help so far is greatly appreciated.
[Samsung Epic 4G Touch] pbsst7:
I am very much appreciating all the help in this matter as well. Thank you all so much.
[Samsung Epic 4G Touch] sfhub:
Can someone who has flashed Rogue (or any custom recovery) connect with adb shell and type:

ls -l /dev/block/mmcblk0p10
[Samsung Epic 4G Touch] huskerpat:
I can try, but I'm afraid I'm not sure how to use ADB. is there somewhere we can chat?
[Samsung Epic 4G Touch] arehm:
I'm sure this won't come as a shock (since you're asking about it), but I'm pretty sure I've seen an error in relation to that on my unworking phone at some point in the ordeal. Thank you for your diligence.
[Samsung Epic 4G Touch] K Ron Hubbard:
brw------- 1 0 0 179, 10 Feb 20 20:54 /dev/block/mmcblk0p10
[Samsung Epic 4G Touch] sfhub:
hmm, the major/minor node #s shouldn't be different between phones. Could you list the other device files in that directory (type the underlined commands)

shell@android:/ # [B][U]cd /dev/block[/U][/B]

shell@android:/dev/block # [B][U]uname -a[/U][/B]
Linux localhost 3.0.15-SPH-D710.FB15-CL143880 #3 SMP PREEMPT Wed Feb 15 23:48:01 KST 2012 armv7l GNU/Linux

shell@android:/dev/block # [B][U]ls -l[/U][/B]
brw------- root root 7, 0 2012-02-20 12:02 loop0
brw------- root root 7, 1 2012-02-20 12:02 loop1
brw------- root root 7, 2 2012-02-20 12:02 loop2
brw------- root root 7, 3 2012-02-20 12:02 loop3
brw------- root root 7, 4 2012-02-20 12:02 loop4
brw------- root root 7, 5 2012-02-20 12:02 loop5
brw------- root root 7, 6 2012-02-20 12:02 loop6
brw------- root root 7, 7 2012-02-20 12:02 loop7
brw------- root root 179, 0 2012-02-20 12:02 mmcblk0
brw------- root root 179, 8 2012-02-20 12:02 mmcblk0boot0
brw------- root root 179, 16 2012-02-20 12:02 mmcblk0boot1
brw------- root root 179, 1 2012-02-20 12:02 mmcblk0p1
brw------- root root [B][COLOR="Red"]259, 2[/COLOR][/B] 2012-02-20 12:02 mmcblk0p10
brw------- root root 259, 3 2012-02-20 12:02 mmcblk0p11
brw------- root root 259, 4 2012-02-20 12:02 mmcblk0p12
brw------- root root 179, 2 2012-02-20 12:02 mmcblk0p2
brw------- root root 179, 3 2012-02-20 12:02 mmcblk0p3
brw------- root root 179, 4 2012-02-20 12:02 mmcblk0p4
brw------- root root 179, 5 2012-02-20 12:02 mmcblk0p5
brw------- root root 179, 6 2012-02-20 12:02 mmcblk0p6
brw------- root root 179, 7 2012-02-20 12:02 mmcblk0p7
brw-rw---- system radio 259, 0 2012-02-20 12:02 mmcblk0p8
brw------- root root 259, 1 2012-02-20 12:02 mmcblk0p9
drwxr-xr-x root root 2012-02-20 12:02 platform
brw------- root root 1, 0 2012-02-20 12:02 ram0
brw------- root root 1, 1 2012-02-20 12:02 ram1
brw------- root root 1, 10 2012-02-20 12:02 ram10
brw------- root root 1, 11 2012-02-20 12:02 ram11
brw------- root root 1, 12 2012-02-20 12:02 ram12
brw------- root root 1, 13 2012-02-20 12:02 ram13
brw------- root root 1, 14 2012-02-20 12:02 ram14
brw------- root root 1, 15 2012-02-20 12:02 ram15
brw------- root root 1, 2 2012-02-20 12:02 ram2
brw------- root root 1, 3 2012-02-20 12:02 ram3
brw------- root root 1, 4 2012-02-20 12:02 ram4
brw------- root root 1, 5 2012-02-20 12:02 ram5
brw------- root root 1, 6 2012-02-20 12:02 ram6
brw------- root root 1, 7 2012-02-20 12:02 ram7
brw------- root root 1, 8 2012-02-20 12:02 ram8
brw------- root root 1, 9 2012-02-20 12:02 ram9
drwxr-xr-x root root 2012-02-20 12:02 vold
[Samsung Epic 4G Touch] K Ron Hubbard:
nvmnd... gimme a sec
[Samsung Epic 4G Touch] sfhub:
"ls -l" will provide the extra info.

"uname -a" will tell me which kernel you are running.
[Samsung Epic 4G Touch] K Ron Hubbard:
# cd /dev/block

cd /dev/block

# uname -a

uname -a

Linux localhost 2.6.35.14-rogue_ET-1.5.0+ #1 SMP PREEMPT Sun Feb 5 08:18:39 UTC

2012 armv7l GNU/Linux

#

---------- Post added at 04:20 PM ---------- Previous post was at 04:18 PM ----------

yeah..... I didn't read first and then I made an ass out of me not u

---------- Post added at 04:28 PM ---------- Previous post was at 04:20 PM ----------

lol. looks like i still didn't read the whole thing sorry, here you go.

# cd /dev/block

cd /dev/block

# uname -a

uname -a

Linux localhost 2.6.35.14-rogue_ET-1.5.0+ #1 SMP PREEMPT Sun Feb 5 08:18:39 UTC

2012 armv7l GNU/Linux

# ls -l

ls -l

brw------- 1 0 0 253, 0 Feb 20 20:54 cyasblkdevblk0

brw------- 1 0 0 253, 1 Feb 20 20:54 cyasblkdevblk0p1

brw------- 1 0 0 7, 0 Feb 20 20:54 loop0

brw------- 1 0 0 7, 1 Feb 20 20:54 loop1

brw------- 1 0 0 7, 2 Feb 20 20:54 loop2

brw------- 1 0 0 7, 3 Feb 20 20:54 loop3

brw------- 1 0 0 7, 4 Feb 20 20:54 loop4

brw------- 1 0 0 7, 5 Feb 20 20:54 loop5

brw------- 1 0 0 7, 6 Feb 20 20:54 loop6

brw------- 1 0 0 7, 7 Feb 20 20:54 loop7

brw------- 1 0 0 179, 0 Feb 20 20:54 mmcblk0

brw------- 1 0 0 179, 1 Feb 20 20:54 mmcblk0p1

brw------- 1 0 0 179, 10 Feb 20 20:54 mmcblk0p10

brw------- 1 0 0 179, 11 Feb 20 20:54 mmcblk0p11

brw------- 1 0 0 179, 12 Feb 20 20:54 mmcblk0p12

brw------- 1 0 0 179, 2 Feb 20 20:54 mmcblk0p2

brw------- 1 0 0 179, 3 Feb 20 20:54 mmcblk0p3

brw------- 1 0 0 179, 4 Feb 20 20:54 mmcblk0p4

brw------- 1 0 0 179, 5 Feb 20 20:54 mmcblk0p5

brw------- 1 0 0 179, 6 Feb 20 20:54 mmcblk0p6

brw------- 1 0 0 179, 7 Feb 20 20:54 mmcblk0p7

brw------- 1 0 0 179, 8 Feb 20 20:54 mmcblk0p8

brw------- 1 0 0 179, 9 Feb 20 20:54 mmcblk0p9

drwxr-xr-x 3 0 0 60 Feb 20 20:54 platform

brw------- 1 0 0 1, 0 Feb 20 20:54 ram0

brw------- 1 0 0 1, 1 Feb 20 20:54 ram1

brw------- 1 0 0 1, 10 Feb 20 20:54 ram10

brw------- 1 0 0 1, 11 Feb 20 20:54 ram11

brw------- 1 0 0 1, 12 Feb 20 20:54 ram12

brw------- 1 0 0 1, 13 Feb 20 20:54 ram13

brw------- 1 0 0 1, 14 Feb 20 20:54 ram14

brw------- 1 0 0 1, 15 Feb 20 20:54 ram15

brw------- 1 0 0 1, 2 Feb 20 20:54 ram2

brw------- 1 0 0 1, 3 Feb 20 20:54 ram3

brw------- 1 0 0 1, 4 Feb 20 20:54 ram4

brw------- 1 0 0 1, 5 Feb 20 20:54 ram5

brw------- 1 0 0 1, 6 Feb 20 20:54 ram6

brw------- 1 0 0 1, 7 Feb 20 20:54 ram7

brw------- 1 0 0 1, 8 Feb 20 20:54 ram8

brw------- 1 0 0 1, 9 Feb 20 20:54 ram9

drwxr-xr-x 2 0 0 100 Feb 20 20:54 vold
[Samsung Epic 4G Touch] sfhub:
Also type this:

shell@android:/ # [B][U]cat /proc/partitions[/U][/B]
cat /proc/partitions
major minor #blocks name

179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 307200 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 524288 mmcblk0p9
259 2 2097152 mmcblk0p10
259 3 12066816 mmcblk0p11
259 4 319488 mmcblk0p12
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
[Samsung Epic 4G Touch] K Ron Hubbard:
# cat /proc/partitions

cat /proc/partitions

major minor #blocks name

179 0 15387648 mmcblk0

179 1 20480 mmcblk0p1

179 2 1280 mmcblk0p2

179 3 1280 mmcblk0p3

179 4 8192 mmcblk0p4

179 5 8192 mmcblk0p5

179 6 8192 mmcblk0p6

179 7 307200 mmcblk0p7

179 8 16384 mmcblk0p8

179 9 524288 mmcblk0p9

179 10 2097152 mmcblk0p10

179 11 12066816 mmcblk0p11

179 12 319488 mmcblk0p12

253 0 16186368 cyasblkdevblk0

253 1 16182272 cyasblkdevblk0p1

#
[Samsung Epic 4G Touch] sfhub:
Thanks, I'm going to try some different kernels and see if the major/minor #s change.
[Samsung Epic 4G Touch] dadoc04:
Sfhub.... dude you are an asset to this community. Props for still trying to help even after many of us called it quits
[Samsung Epic 4G Touch] K Ron Hubbard:
Any time man! glad I could be of help after all you've done for the community!
[Samsung Epic 4G Touch] caspersfi:
Awesome to see sfhub hasn't given up on this. Really hope he's able to get this worked out.
[Samsung Epic 4G Touch] sfhub:
Just to confirm, your /data is writable or you are having trouble writing to it?
[Samsung Epic 4G Touch] arehm:
Mine is not, do you need data from me? I should say I get stuck on the data.img with odin.
[Samsung Epic 4G Touch] K Ron Hubbard:
My data is writable. Yes.

---------- Post added at 04:55 PM ---------- Previous post was at 04:52 PM ----------

I hope I wasn't wasting your time...
[Samsung Epic 4G Touch] sfhub:
Yes, it would be best to get information from someone who can NOT write to /data and compare it to my own, which is writable.
[Samsung Epic 4G Touch] arehm:
Let me see if i can get ADB going here. standby
[Samsung Epic 4G Touch] K Ron Hubbard:
sorry :o 10char
[Samsung Epic 4G Touch] arehm:
Can someone point me in a direction for a good ABD install/use guide? I want to make sure I get this correct. I've used it once before, but..... (certified geek, so I'm not worried)
[Samsung Epic 4G Touch] sfhub:
It is probably overkill but if you download the Auto Root package (e4gtauto-sfx.exe), choose Option E in the main menu and then Option E in the sub-menu and you'll have an adb shell.

http://xdaforums.com/showthread.php?t=1342728
[Samsung Epic 4G Touch] K Ron Hubbard:
I believe there's a post in the general section, but google android sdk and install it.
[Samsung Epic 4G Touch] arehm:
OK, have ADB, working on figuring out how to get the phone in ADB mode.
[Samsung Epic 4G Touch] huskerpat:
Yeah, i can get to a recovery or download mode
[Samsung Epic 4G Touch] sfhub:
adb should already be running if you have custom recovery.
[Samsung Epic 4G Touch] arehm:
Then perhaps i can't help. I'm back to stock and all i can get to is odin mode. i get the ever popular firmware upgrade encountered an issue..... when i try and get to recovery.
[Samsung Epic 4G Touch] huskerpat:
I'm in Rogue recovery 1.1.2. Computer says waiting for a device to be connected...but I have it plugged in, and yes i have all the drivers and sdk installed.

did a recovery log. does any of this mean anything?

http://pastebin.com/HYnYHu0p
[Samsung Epic 4G Touch] sfhub:
Assuming you are having issues writing to /data, format /data and then post the log from that.
[Samsung Epic 4G Touch] huskerpat:
I wiped formatted data and here's the log.

http://pastebin.com/RNCP8B7Q
[Samsung Epic 4G Touch] sfhub:
Too bad, looked promising, but it appears this is just the startup log for recovery. It doesn't have logs of actions done after startup.

I actually found a recovery log, but it is in /data/log, which wouldn't help your case, as you can't access /data.
[Samsung Epic 4G Touch] glass330:
Me three. Omg why is this happening. :(

has anyone tried to restore el29 tar to fix it?
[Samsung Epic 4G Touch] arehm:
I've tried a 1/2 dozen different one click odin's. Someone here tried a special made Odin for this issue and it didn't work. Fortunately it's still being researched. Time will tell. I have my fingers crossed.

---------- Post added at 05:13 PM ---------- Previous post was at 04:52 PM ----------

sfhub, is there a particular rom you know will work? I can try and flash it tonight and get into it's recovery and see what I can get you.

---------- Post added at 05:14 PM ---------- Previous post was at 05:13 PM ----------

sfhub, is there a particular rom you know will work? I can try and flash it tonight and get into it's recovery and see what I can get you. (meant this to be a reply, not edit)
[Samsung Epic 4G Touch] huskerpat:
I successfully odined the file HOME_SPH-D710_EK02_CL704398_user.tar.

on reboot, "E:faled to mount /data (unknown error: 0)

E:UPdate logfile dose not esist

e:faild to moun /data (unknown error: 0)

It's now trying to format data...and it finished, restarted and I'm stuck at the the samsung screen.
[Samsung Epic 4G Touch] arehm:
http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/60768-how-factory-restore-fix-bricked-phone.html

1/2 way down is:

5b. IF YOUR PHONE IS BRICKED (like mine was) the field for data needs to use a different file, use the one found here: RapidShare AG, Cham, Switzerland

Any chance there is something in what i assume is a linked file that may help.

Don't run off and use these files, i'm more asking the brains here if this person may be on to anything.

Looks like it's for the international version.
[Samsung Epic 4G Touch] glass330:
I have tried re-formatting the device and restoring the EL29.tar

I used a pit from here

http://xdaforums.com/attachment.php?attachmentid=721784&d=1316200711

Epic_4g_Touch_Pit

Still stuck at boot loop.

If I try and flash FB17 get stuck at data.img, then the firmware update failed notice/boot.

So then I reflash EL29 just cause it finishes, can't boot. Same

I can flash all sorts of kernals in odin, but never get a recovery with UP and PWER. Only a loading bar...

please help. :(

I can wipe this data partition problem out >:(
[Samsung Epic 4G Touch] arehm:
http://www.galaxyforums.net/forum/samsung-fascinate-hacking/2301-simple-step-step-odin-heimdall-recovery-how-unbrick-your-fascinate.html

It almost sounds like Heimdall (which sounds like a cross platform version of Odin) may be of some use here. Again, I do not recommend anyone jump out as this post was clearly from a different Samsung phone, and I have no friggin' clue if this will take things from bad to screwed. I'm just hoping to pass some possible information to those with a better clue to see what they can tell us.
[Samsung Epic 4G Touch] glass330:
okay i gotta mac I can use. Once i set it up what do you want me to do?
[Samsung Epic 4G Touch] stonesaber:
I'm able to get into stock recovery and flash rogue recovery via odin and boot into it as well. I've also been able to get mine to boot to the sprint boot animation but it sticks at the 4g screen. I'm also able to restore a back up in rogue but it hangs at restoring data. Seems to me, if we can get into download mode and recovery there should be a way to fix this. I just have no idea how.
[Samsung Epic 4G Touch] glass330:
nevermind, lolz i didnt know there was a windows version of heimdall either way i got both and a linux box if i need it.
[Samsung Epic 4G Touch] arehm:
Again, no one do anything with my posts. I'm putting them out there for the snowball's chance in the land down under they can help point the brains in the right direction.
[Samsung Epic 4G Touch] glass330:
Okay. I reflashed FB17.tar and got stuck.

So now I have used Heimdall and flashed a data.img from FB17 using the pit from earlier and set it to datafs reaches 100% then

ERROR: Failed to confirm end of file transfer sequence!

DATAFS upload failed!

Ending session...

ERROR: Failed to send end session packet!

Unit still wont boot.

Now im gonna try some recoveries
[Samsung Epic 4G Touch] arehm:
Good luck.
[Samsung Epic 4G Touch] glass330:
stuck at this
[Samsung Epic 4G Touch] oscarthegrouch:
I know my comment isn't any help but gd, something in those fb leaks is royally f'ing up phones lately!
[Samsung Epic 4G Touch] glass330:
No I think its Touch Recovery that jacked everyone up.
[Samsung Epic 4G Touch] iniz94:
I'm stuck at Data.img as well

By the looks of the posts on this thread, has anyone successfully fixed it yet?

Edit: Read through all 17 pages and praying that there is a fix. I wish I had insurance for my phone :/
[Samsung Epic 4G Touch] sfhub:
The current issue appears that the /data partition is hoarked and nothing (CWM, ODIN, ODIN One-Click) can write to it, not even ODIN with explicit repartition, which is surprising. Every other partition is fine, just the /data. However without /data you phone cannot boot into Android.

---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------

I don't think any "ROMs" will work because they all require /data to boot up. Every other partition besides /data seems to be fine, so you can flash and boot up into custom recovery. That is where we might be able to do some diagnosis from.

---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------

Just out of curiosity, did you install CWM Touch and try to do a restore? (I'm not pointing fingers, just trying to gather data)

---------- Post added at 07:12 AM ---------- Previous post was at 07:11 AM ----------

I tried looking on that thread but didn't see the links they were referring to. The RapidShare text seemed like it should be a link but was just text.

---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------

Like glass330 said, the pattern appears to be CWM Touch rather than the ICS release. People just happened to use CWM Touch early on with the FB09 thread.
[Samsung Epic 4G Touch] iniz94:
In response to sfhub: I just recently got this error but I tried restoring from CWM Touch and this happened
[Samsung Epic 4G Touch] sfhub:
So did everyone who has this issue with /data, at some point, use CWM Touch to do some operation, restore or format?
[Samsung Epic 4G Touch] caspersfi:
I did. The touch recovery link is what was givin in the op of the FBO9 thread as a temporary way to restore your backup.

Booted into stock recovery

Flashed touch recovery

Full wipe with touch recovery

Restored backup with touch recovery

Stuck at Samsung logo

Then used odin as a way to get out and stuck at data.img.
[Samsung Epic 4G Touch] dgn_sandibalz:
yes. happened when i tried to format.
[Samsung Epic 4G Touch] pbsst7:
Same thing. Happened when I tried to restore a backup.
[Samsung Epic 4G Touch] MeWarning:
What settings do you use in Odin when flashing this? I've never flashed just a recovery before and this guy needs help, lol:

http://xdaforums.com/showthread.php?t=1508542
[Samsung Epic 4G Touch] dgn_sandibalz:
This is brutal. Last week my handset did a factory restore when I turned it on. It kept doing that every couple hours. Got replacement. Now this.

Got to smug flashing roms like I know what I'm doing.

Thanks to all the help in this three. Really, much respect for the effort you guys put in on your own time.
[Samsung Epic 4G Touch] dadoc04:
It was definitely touch recovery....
[Samsung Epic 4G Touch] arehm:
Touch here as well.....

adb is essentially a shell to the linux os on the phone, correct? could formatting/mounting/dpart or whatever in adb be a possible cure? go even lower level than odin.
[Samsung Epic 4G Touch] dgn_sandibalz:
I was able to get jig to work though....

This worked to do that:

http://xdaforums.com/showthread.php?t=1391624
[Samsung Epic 4G Touch] arehm:
So are you fully working again? Or just reset to a 0 count?
[Samsung Epic 4G Touch] dgn_sandibalz:
Just 0 count. Was important because this is second phone in a week. Will require some begging on my part.

I am still trying today to get it working. I'm lucky to have a backup phone. If I get it working I will post what I did.
[Samsung Epic 4G Touch] arehm:
Here's one link to ADB doing a repatition that sounds promising

and here another I'm using the google cache as the regular link came up with a threat on my system, some malwarething, this cached version from google came up cleaner.

And this one, after reading this part, remove the postcount=24 and see the rest of the thread, may be more useful info.

Of course I now remember I can't get into ADB mode. But if a CWM recovery can get us ADB mode perhaps it's an option....
[Samsung Epic 4G Touch] glass330:
Touch recovery is the problem

funny enough - if i boot into recovery using rouge 1.1.4 I can load the touch recovery zip and it immediately shows me touch recovery. device doesnt even restart.

I can mount everything but /data & /emmc from rogue1.1.4 and touch recovery at this point.

I wish there was something i could do from touch recovery to correct all this junk it caused, then never EVER use it again .
[Samsung Epic 4G Touch] stonesaber:
It's the same for me. Luckily rogue allows you to mount internal storage so we can at least pull some of our stuff off it. I had some pics that was stored on the internal storage I was able to recover. I have no doubt someone smarter than me will figure this out.
[Samsung Epic 4G Touch] arehm:
http://xdaforums.com/showthread.php?t=1390393

The one here? should this be safe to load to try and recover my data?