yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] sfhub:
So this is different that what it was doing before? Perhaps you are making progress.

Try ODIN flashing just the rooted ROM (section #B4)

Sorry it is taking so long. I'm kind of using you to debug the actual issue.
[Samsung Epic 4G Touch] dadoc04:
no problem... your help is appreciated... gimme a minute download #B4 and ODIN... ill post results

---------- Post added at 02:40 AM ---------- Previous post was at 02:38 AM ----------

I dont see a B4... maybe im looking in the wrong thread... u mind linking me?

---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------

NEVERMIND>.. i was using the wrong link.. i found it

---------- Post added at 02:46 AM ---------- Previous post was at 02:42 AM ----------

do you want me to select anything in odin? or just the auto reboot?
[Samsung Epic 4G Touch] sfhub:
It is a self-extractor so remember to double-click on it to extract the tar.md5 before using in ODIN.

Just auto-reboot is fine.

You've already flashed the kernel and reformated /data. The only thing needed to boot that might not be correct is the ROM, so hopefully this works.
[Samsung Epic 4G Touch] dadoc04:
alright... ill let you know in a few minutes what happens
[Samsung Epic 4G Touch] sfhub:
It will probably take a little bit of time. The ROM is the largest image.
[Samsung Epic 4G Touch] dadoc04:
^ yea...

its going now... currently in FACTORYFS...

---------- Post added at 02:59 AM ---------- Previous post was at 02:55 AM ----------

it says PAss..... not sure where it did data though....

factoryfs

NAND Write Start

RQT CLose

RES OK

REmoved

Completed

All threads completed (succeed 1/ failed 0)
[Samsung Epic 4G Touch] sfhub:
It didn't do /data (data.img). You already formatted that using stock recovery, so it shouldn't be necessary to flash it.

Factoryfs.img is the ROM.

You previously already flash the kernel and verified it was working because you were able to boot into stock recovery.

So that takes care of kernel, ROM, and /data. I doubt anything is wrong with the modem. So everything that is needed to boot should be in place.
[Samsung Epic 4G Touch] dadoc04:
its just flashing the "samsung galaxy s II" screen again

it goes to a grey battery image screen
[Samsung Epic 4G Touch] sfhub:
That is usually what it does when you power down your phone. What happens when you press and hold power until something happens?
[Samsung Epic 4G Touch] dadoc04:
press and hold power = gray battery screen....

edit... the battery went away and "samsung galaxy s2" is back
[Samsung Epic 4G Touch] sfhub:
If it is looping again, try booting into recovery and wipe data/factory reset one more time.
[Samsung Epic 4G Touch] atharchian:
I wonder if you can run adb logcat as the phone goes from off state to stuck on samsung logo. You might be able to see whats going on if adb picks it up.
[Samsung Epic 4G Touch] sfhub:
^ That's a good idea ^ Might provide some clues.
[Samsung Epic 4G Touch] dadoc04:
wiping data/factory reset now... ill let ya know how it goes. It took a while last time as i think it was hung up

---------- Post added at 03:17 AM ---------- Previous post was at 03:14 AM ----------

im comfortable with ADB...

tell me how/when to do it and ill give it a shot....

---------- Post added at 03:18 AM ---------- Previous post was at 03:17 AM ----------

wipe is complete...

still shows the E:file is written: not updated
[Samsung Epic 4G Touch] atharchian:
in command prompt, type

adb logcat

it will more than likely say "waiting for device" . thats fine, just plug in your phone to the pc and boot up the phone as usual. if the phone is booting far enough, adb should pick up the device and start displaying the logcat.
[Samsung Epic 4G Touch] dgn_sandibalz:
I have hit the wall trying to get this thing to repartition correctly.

I did get the stock EL29 Modem, Kernel and Rom odin'd fully ( http://xdaforums.com/showthread.php?t=1433101 ). But, when the phone reboots it stalls at the black screen. When I go into the stock recovery it gives me all of the "can't mount E: to do anything" error messages.

Called tech support to go through trouble shooting. It failed. They put in a note for the store to replace phone. I used the calk's EG30 tar file I linked earlier to get the jig reset working again in case store decides to take a peek.

Sorry I couldn't be any help.
[Samsung Epic 4G Touch] huskerpat:
attempted to make a usb jig. ended up destroying 2 usb cables...sigh. ordered jib off amazon and it'll be here tomorrow. If I don't get it fixed, my wife is going to go all "angry wife" at the sprint store to try and get it fixed.
[Samsung Epic 4G Touch] barnacles10:
So i attempted again today to flash rogue kernel with touch recovery, as i did when going back from the fb09 leak. This has me confused.

Booted into download mode and loaded rogues touch recovery into odin and started the update. Zimage applied successfully as intended. I then powered off and booted into recovery and wiped everything before flashig miui (all i happened to have on my sd card at the time). Flashed successfully and booted successfully.

Im not sure what the variable difference is between what I did and what everyone else is experiencing as I understand this is the same route many took? Or are these touch recoveries coming from the quick flash in rom manager only ?

If thats the case it migt be worth looking into the script injecting this quick recovery to see exactly what its doing.
[Samsung Epic 4G Touch] glass330:
go into touch recovery and try to restore a nand. I believe this will kill your data and emmc partitions.

If anything you may even try just to mount the data partition, then wipe it. should fail.

---------- Post added at 12:21 PM ---------- Previous post was at 12:12 PM ----------

Hey Barnacles10 - check out this thread to re-create the issue.

http://xdaforums.com/showthread.php?p=22794885#post22794885
[Samsung Epic 4G Touch] dgn_sandibalz:
I think most of our issues began with using the touch recovery to format data, or use restore. Those two particular steps seemed to wipe out the partition structure. Without being able to repartition (which gets us our spot for data to be built) all the flashes we do are not going to work because there's nowhere for data to go.

In my case I may have been able to get farther along than some, being able to flash a rom completely with odin. But, on every reboot the device would hang on the Samsung SII screen. I would do a battery pull and reboot into the stock recovery. This is where I think it's clear that the issue is partition related, because every time (without fail), it would state that there were no E: logs (whatever those logs are) and then it would say that it updated the application. Then it would install apk's. Then it would try and create the data part and fail. Every time.

Here are other things that I tried (so I don't have to repeat, in cases where I installed a rogue recovery I tried every build version):

- Install rogue recovery, tried restore from nand

-result...super fail. seriously, this had the worst result of the bunch. it wouldn't even start.

- Odin the stock EL29 pieces from sfhub's one-click thread. figured this one gave me the best shot.

- Install rogue recovery,install temp rogue touch recovery, install FB15 modem, FB17 Rom (odex and deodex) from calk's thread

- Odin the FB15 pieces from sfhub's one-click thread.

-results of the three above...black screen boot loop.

- Use sfhub's one-click EL29

-result...failed at the data.img

I apologize for being so long winded, but wanted to be thorough. I am not an expert at all, so I don't have the lingo down and may not have explained myself very well, or included enough information.

Before going to store I did odin the EG30 bootloader, reset counter with jig, and then odin'd all the EL29 pieces from sfhub's thread (kept the count at zero, huge thanks for that). Store looked at it for about 20 minutes and then ordered replacement.

---------- Post added at 02:05 PM ---------- Previous post was at 02:04 PM ----------

I did email www.mobiletechvideos.som to see if they could fix this specific issue, and they responded that they could. I linked to both thread in my email to them.
[Samsung Epic 4G Touch] glass330:
I dont understand why the pit file isnt just wiping everything and building the partitions correctly. No matter how screwed up they are it should be wipe out the tabled and partition the device correctly, and its not!
[Samsung Epic 4G Touch] dgn_sandibalz:
Maybe I missed it, but I couldn't find just a PIT file from any of the builds. I thought it would be as easy as popping that in the PIT box in odin, check the repartition box and be done with it.

Seems like the PIT file is buried in the tar files, and odin doesn't seem to like repartitioning that way.
[Samsung Epic 4G Touch] blackroseMD1:
I did everything I could think of to fix this, and was never able to. I ended up having to take my phone into the Sprint Repair Center and they couldn't fix it either, so they swapped me out a new phone. My custom binary count was 7 when I took it in, so if you've been denied, you might just want to try a different store.

As an aside, I did use Touch Recovery as well, so that definitely seems to be the common denominator here.
[Samsung Epic 4G Touch] s9amme:
FYI, CWM Touch recovery has also caused some problems with BlazerROM. I don't know if this information would help figure out the issue, but i'll bring it up just in case.

A few people were on the 'Hitman' kernel (comes with Touch recovery) and tried to flash BlazerROM v3.8 (latest at the time) and got stuck at boot loops or would just hang at the Samsung logo. People were able to restore back to a nandroid of v3.7 though. Some people used the one-click ODIN'd back to EL29 stock without issue as well. If you look at the BlazerROM thread in the dev section, it starts around page 417. PhantomHacker also suggests not using hitman (read: touch recovery) to flash his ROMs.

So it seems CMW Touch Recovery is the common denominator, but folks in the BlazerROM thread were able to restore successfully, either through nandroid backups or odin. I'm wondering if its the combination of touch recovery and the FBxx leaks that's causing the /data corruptions.
[Samsung Epic 4G Touch] caspersfi:
Damn, just seen a new thread titled "maybe bricked". Think he said he was on FB17.......went the same route we all did and is stuck. The list just keeps growin.

Just got my phone back and my wife said "your not gonna put that Ice Cream thing back on your phone are ya?"

Think I'll be sitting back and reading and watching these ICS threads for a while. If its ICS or Touch Recovery don't matter, back to playin it safe.

Seen sfhub hasn't checked in here lately.....hopefully thats not a bad sign.
[Samsung Epic 4G Touch] pbsst7:
I agree, Casper. I hope he hasn't left us. He has been so helpful with all of this.
[Samsung Epic 4G Touch] iniz94:
I never got the paid insurance so would I still be eligible to get a new one from sprint? Also, can someone explain what a jig is? I'm told it will reset the Odin count. Is it needed to be eligible for the non-insured warranty?
[Samsung Epic 4G Touch] Dalmus:
Yes, stay away from the touch recovery.

After I flashed ICS, I used Mobile Odin to slash a rogue EK02 kernel with cwm, let Odin reboot to recovery, and then restored my backup from there.
[Samsung Epic 4G Touch] dadoc04:
i think he was heading out of town on a trip or something... i think i saw that somewhere
[Samsung Epic 4G Touch] dgn_sandibalz:
It's gonna be tough just sitting back and waiting after using it for a day.
[Samsung Epic 4G Touch] stonesaber:
Well, I just emailed Josh at mobiletechvideos.com and he thinks they can fix it. It took them about ten minutes to reply to my email. Already impressed. I'll be shipping mine out tomorrow and hopefully by next week it'll be back and fully functional. I'm fortunate that I have a Photon as a backup. I'll post back when I get it back and let everyone know how it went. If this works, they may get a lot of business in the next week or so.

Of course, as soon as I ship mine out, somebody will find a really simple fix and I'll have to give myself a swift kick for not being patient...
[Samsung Epic 4G Touch] iniz94:
Not sure that it'll get fixed any time soon lol since sfhub is going out of town. But please let us know how it goes... I'm like 1 click away from sending mine as well but I might try going to the Sprint store first.
[Samsung Epic 4G Touch] sfhub:
I am still around, but had to travel at the last minute.

It is hard to do any debugging without my dev setup, so i wouldn't expect any updates from me until the end of the week.

Before i left i think i at least figured out why cwm touch was causing issues for some but not others. As mentioned earlier cwm touch already behaves funky on gingerbread roms.

What tipped the scale appears to be if you used the cwm touch update.zip to "fake flash" using the stock ics fb09/fb15/fb17 recovery. When you "fake flash" cwm touch, you end up combining a cwm touch recovery, that was already behaving funny with a linux 2.6 kernel, with the ics linux 3.0 linux kernel. This was just too much and when cwm touch went to format or restore it hoarked some meta data making it impossible for utilities to access, format, or repartition /data.

The people who did not have fatal situations with cwm touch didn't the fake flash on top of the 3.0 linux kernel. They odin flashed a 2.6 gb kernel with cwm touch packed into the initramfs.

So the moral of the story is don't go fake flashing recoveries with arbitrary kernels, you might not like what you get.

Btw both update.zip and rom manager do fake flashes.

Sorry for the typos, i am using swype.
[Samsung Epic 4G Touch] huskerpat:
So, I have a new phone. I've been told that they won't replace the phone again if I brick it...
[Samsung Epic 4G Touch] musclehead84:
Im getting my new one on Friday and have to send back my old one. is there any logcats that anyone wants me to get? I can still keep this phone for like the next two weeks.
[Samsung Epic 4G Touch] caspersfi:
Damn .... well hopefully you have insurance and never have to use it. I just got my new(refurbished)phone yesterday. I went the way of insurance. Figured I'm the one that effed it up so I'll pay.

Been reading and keeping an eye on the ICS threads. So BADLY want to flash one but trying to go the cautious route.

Not easy..........
[Samsung Epic 4G Touch] caspersfi:
Just a suggestion but maybe pm sfhub. I think he's out of town till the end of the week and can't do much till then but I bet he would love to get those.
[Samsung Epic 4G Touch] imfamouzz:
Still Stuck :(

Was Using CM9 Alpha 3.1 with CWM Touch. Tried To restore stock el29 backup through recovery and accidentally wiped with CWM Touch.

tried all sfhub's suggestions including "EL29 v1"

still stuck on Data.img in odin

yes, im a noob, can't you tell?

HELP! :(
[Samsung Epic 4G Touch] iniz94:
Same problem as all of us :/ Go to Sprint and make up a BS excuse to see what they do. I'm gonna do that once my Jig comes in
[Samsung Epic 4G Touch] MeWarning:
Here's a guy you can send it to to get fixed. Hard bricked my phone the other day and it's in the mail to him right now. Mine was bricked a different way but I've heard him say he can fix this too.

http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/

And it's only 50 bucks which is not bad at all.
[Samsung Epic 4G Touch] caspersfi:
Just did some reading, looks promising. Let us know how it goes. This could help alot of ppl.
[Samsung Epic 4G Touch] musclehead84:
Its cool man. It happens to alot of people. I did the same thing and so did a developer so it doesn't have anything tto do with being a noob. Its just that this stuff is new and no one knows how its gonna go until phones become bricked. Good luck.
[Samsung Epic 4G Touch] playya:
I agree stuff does happen but whether here or back in the OG Evo forum at least for me it seems the constant was leave Rom Manager alone. Hey to tell you the truth I wish Amon had a recovery for our phones because I have never trusted Clockwork. Only thing is, at least Steady Hawkins makes it look so purtttty.....lol
[Samsung Epic 4G Touch] imfamouzz:
Sfhub, where are you?

Come back. Help us.
[Samsung Epic 4G Touch] dadoc04:
^ im sure he will be back... he's on a trip/vacay right now. He checks in every once in a while.

Good luck with your phone man...
[Samsung Epic 4G Touch] iniz94:
I've been corresponding with him for awhile now and he said not to send it yet. He wants to see if he's able to fix one before he is open for more orders. I'm assuming yours is the "one" he is referencing.
[Samsung Epic 4G Touch] kingsway8605:
This thread is no different than complaining about having an std after having unprotected sex. You knew the risks, but did it anyway.
[Samsung Epic 4G Touch] arehm:
I'm not usually one to respond to posts like that, but wow. That post will take the cake today for the most unhelpful post I've read. Thanks.

On topic. Still hoping we can get some resolution here. My old android phone's not quite what the SGS2 is. Can anyone with CWM get into ADB mode?
[Samsung Epic 4G Touch] stonesaber:
He had no problem taking my order today. I'm shipping it tomorrow and will let everyone know how it goes.
[Samsung Epic 4G Touch] iniz94:
Well he said that I could send it, but it would be more advantageous to me if I waited to see if he was successful.
[Samsung Epic 4G Touch] stonesaber:
I guess we'll find out in a few days. Hopefully I'll have good news to report.
[Samsung Epic 4G Touch] kingsway8605:
There really isn't anything you can ethically do. This is why there is a disclaimer on every rom that nobody ever reads. It annoys me. Odin is the last line of defense though. If that failed, you are pretty.much screwed. Your best bet is going to your local sprint store and being really friendly with the manager.
[Samsung Epic 4G Touch] iniz94:
We obviously knew the risks and we did it anyways. No one is complaining...we are simply asking for help and advice. And there is hope, since Josh from MobileTechVideos thinks he can fix it (we will find out soon) and several people have successfully gotten their phones replaced from Sprint.
[Samsung Epic 4G Touch] shiftr182:
I imagine that if you did a complete format of the /dev/block/mmcblk0p10 partition (I think that is what data is), then the phone should be able to boot. Im talking about complete formating, like formating ext4, everything, because it would completely wipe everything in the partition. There was something I ran across talking about formating the partitions using "parted" or something, but I believe it only works on ext2 partitions. Anyway, its an idea.
[Samsung Epic 4G Touch] arehm:
That's what I'm thinking too, but to do that we need to be able to get in via ADB. That's why I was wondering if anyone with CWM could get into ADB. Time will tell.
[Samsung Epic 4G Touch] shiftr182:
If you can connect to odin, flash a kernel with cwm, then go to recovery. In recovery you will be able to get in via adb. I have a bricked one sitting in front of me, it sticks at the boot screen, but it has adb.
[Samsung Epic 4G Touch] imfamouzz:
so i used qbking's method..see link

h_t_t_p_:_/_/_www_._youtube.com_/_watch?v=_vmEmheJnyg

remove underscores before "watch"

used that method with "HOME_SPH-D710_CL852097_user.tar.md5". three things are happening

1.) Power on: "Samsung Galaxy S II" screen loop.

2.) Vol down + Power: Odin Working Fine.

3.) Vol Up + Power: E:Update Logfile does Not Exist

Deleting Cryption Meta Data

# MANUAL MODE #

-- Updating Application...

(then goes back to behavior in step 1)

this is certainly an issue with vol E. which im assuming has to do with partition. should be a soft brick. anyone have a fix???
[Samsung Epic 4G Touch] mpnieland:
Also hosed by Touch Recovery

Guys, I've read through the whole thread and I have the exact same problem. Updated to ICS leak, then found the radio wasn't working and tried to revert to my backup with touch recovery. Hung on data and now can't get it recreated using all the same steps everyone else has.

Does anyone know how to re-build the /data partition using adb? A previous poster said something like if we could flash Rogue and get into it with adb, we might be able to do this to get back to square one. Problem is I don't know about linux or adb very well.

I have a company E4GT and would rather not have to deal with returning it as they'll probably ask me if I rooted it. I've used the jig and right now it just looks like it got hosed by an OTA update perhaps. But still, I'd like to fix the phone I have rather than start over.

Any help you can give would be greatly appreciated!
[Samsung Epic 4G Touch] musclehead84:
I can get into recovery on my bricked data partition phone. What commands can I do in adb to repartition? I'd love tto getting his resolved.
[Samsung Epic 4G Touch] shiftr182:
you could try "format DATA:" but it will probably get stuck. One of the devs will have to help as far as redoing the partition. Might try "mkfs.ext4 /dev/block/mmcblk0p10"

You will have to make sure mkfs.ext4 is in /sbin, otherwise you will need to download it and abd push to /sbin. I dont have the bricked on with me anymore, so I cant test.
[Samsung Epic 4G Touch] sfhub:
I assume your phone is busted and you don't care what happens to it because you are getting a replacement?

It isn't repartitioning, but you could try this to see if it helps.

dd if=/dev/zero of=/dev/block/mmcblk0p10

Try it AFTER ODIN flashing a GB-based CWM like EL29 repacked with Rogue CWM, then try the EL29 ODIN One-Click.

If that doesn't work, try it AFTER ODIN flashing an ICS-based CWM like FB17+CWM, then try the FB17 ODIN One-Click.
[Samsung Epic 4G Touch] mpnieland:
Where can I get mkfs.ext4 to push it to sbin? I would like to try this command.

---------- Post added 27th February 2012 at 12:11 AM ---------- Previous post was 26th February 2012 at 11:57 PM ----------

sfhub: Can you explain what this command does? I flashed the EL29 with rogue cwm, adb shell in, and did this command. Then I did the one click and still broken. But I see I do have a /data when I adb in again.
[Samsung Epic 4G Touch] sfhub:
It writes all zeros to the /data partition.

When you say you "have a /data", is that just a directory, or is it a partition mounted to it?
[Samsung Epic 4G Touch] mpnieland:
I just have a /data. No partition. How do I do that?
[Samsung Epic 4G Touch] sfhub:
mount ext4 /dev/block/mmcblk0p10 /data
[Samsung Epic 4G Touch] phelps88ap:
can you move data partition?

i ended up doing the same thing to my epic yesterday and after being on here til 4am and trying everything my limited knowledge could allow, i finally gave up but had a new idea when i woke up. what if we could move or make a new data partition. i'm not sure this is even possible, i'm a complete noob when it comes to developing but i had this idea after i saw you can run multiple roms on one phone. its just a shot in the dark, but maybe sfhub can do something with this when he's back. or if anyone else knows what can be done.

also on a side note, how can i get adb to find my phone? its been said booting into recovery should make adb be able to find your device but i've had no luck. any help with this would be great. thanks in advance.
[Samsung Epic 4G Touch] sfhub:
That's what ODIN with the re-partition tick is supposed to do. People tried it, but it didn't work.

You need to ODIN flash a custom recovery like CWM-Rogue. On stock kernels adb is disabled. On kernels with custom recovery packed in, they usually re-enable it.
[Samsung Epic 4G Touch] Epix4G:
Did anyone try the new pit file that was posted the other day
[Samsung Epic 4G Touch] phelps88ap:
i guessed as much that was what it was supposed to do.

so i flashed cwm-rogue and adb still says

error: device not found

maybe i'm just not doing it right, i'm a real noob with adb, only had to use it once before when i rooted my evo 4g

---------- Post added at 10:12 AM ---------- Previous post was at 10:06 AM ----------

i used the one titled epic 4g touch pit.pit last night again today to no avail.

if there's another one whould you direct me to the thread to download it?