[Epic 4G Android Development] swp22:
I have read alot of threads with issues in regards to flashing back to stock and odin not working and wandering if people should flash a then b. I did have some trouble when i went from a to b version from hell version and had to odin back to stock. I also had issues with odin some times failing just like people have had. Here is the exzact steps i went through that i hope will help some people who had the same problems that i had cause my phone now is working flawless.

This might help some people who are having problems with odin failing. I have odin back to DK28 stock using the tar file from sdx under the ( update epic from 21. 2.2 forum ) i used the modem and pit that was listed in the beggining of this thread. I also used odin 1.61 to do this...... What i did due to odin failures was i first installed the tar file only and (this is very important... I took the MD5 off the end of fill name and it flashed beautifully) i then went back into download mode and then installed the pit and modem and it ran flawless again.

Now i used this root version (epic.aio.ver2.04 "google it and you will find it") which has the required cwm you need to install all of vipers rom including the newest one which BT gives instructions on how to get to CWM version 2.5.1.0. This root file i listed will automatially put you into that version and then i simply followed his instructions to a T and it worked great.

Now for where i screwed up in the beggining :)

I first saved all my sd stuff to my desktop then did the following

1. i initially tried to go from hell to (a) then straight to (B) without ever rebooting. Yeah that didnt take to well and my phone got stuck at the samsung boot screen.

2. What i did was i did my odin trick up top then loaded vipers hell version after following BT's instructions on how to flash that

3. I then let the phone boot up normally and formatted my SD card through the phone menue and did a normal power down.

4. I then followed BT's flash instructions except for the reboot recovery to get into 2.5.1.0 because the root i used (listed up top) had that version as its default already. Once i got into version (A) I powerd up let it run and once again formatted my SD card through the phone menue and then powered the phone down normally.

Before i continue i would like to mention that before doing these steps ive listed i have had all the same problems that everyone else has posted in this thread as far as ( line errors 3 12 7 you name it ive had it ) and these steps fixed everything and flashed with no problems.

5. I then booted into cwm and followed BT's instructions to a T to get from version (A) to (B) and it flashed flawlessly. Now i will say this as a reminder YOU MUST ALWAYS DOUBLE CHECK YOU TO MAKE SURE YOU DO REBOOT RECOVERY VERSION 2.5.1.2 TO GET THESE FILES TO FLASH. I had several errors that people have posted due to the fact i didnt double check and ssumed once i was in version (B) i would automatically be in CWM 2.5.1.2. That is not the case even running version (B) i still sometimes get version 2.5.1.0 and have to do reboot recovery to get to 2.5.1.2. Not checking this prior to flashing will give you files errors as well as errors pertaining to cannot find file, cahce, program, blah blah basically everything people have posted about.

I have even had an instance where it said CWM 2.5.1.2 i went to install a file and got errors i did the reboot recovery and it CWM said 2.5.1.2 again and installed the same file and it worked the second time. Another thing I have also had to do to not get errors is i will boot up into CWM and would say version 2.5.1.0 even after having version (B) installed. I would then do reboot recovery and it would still say CWM version 2.5.1.0. All i did then is simply flash the (FLASH FIRST) file from the new (B) version only and then do reboot recovery to get the 2.5.1.2 and install any zip file my heart desires with no errors.

I have found and its been said in prior posts that files seems to install very nicely in version (B) when your in the CWM 2.5.1.2. I really hope this will help alot of people cause i know how it felt to get these line errors and have odin not work properly to get back to stock.