Samsung Epic 4G Lag Fix: RFS to EXT4 for Froyo DK28

[Paul627g]

Did you download the Samsung drivers, and after installing the drivers plug in your phone and allow the computer to recognize and fully install the drivers?

If you completed those steps did you place your phone in De Bug mode then connect your phone?

I can see what is happening your phone is not being connected/recognized. Check the drivers/install as I stated above. Try a different USB port, cable, if your using 64 bit drivers then try 32 bit.. You get to recognize your phone and you will be in business.

 

[jpeepers]

Did you download the Samsung drivers, and after installing the drivers plug in your phone and allow the computer to recognize and fully install the drivers?

If you completed those steps did you place your phone in De Bug mode then connect your phone?

I can see what is happening your phone is not being connected/recognized. Check the drivers/install as I stated above. Try a different USB port, cable, if your using 64 bit drivers then try 32 bit.. You get to recognize your phone and you will be in business.

Yes, did all of the above. I have already had the phone connect and I pretty sure it recognizes it. I can connect via adb shell right now?

.

 

[Paul627g]

Just keep playing around until you get that run.bat file to successfully work. Might take some playing around like I mentioned.

Try restarting your phone and computer and redo the run.bat file again. Sounds dumb but stranger things have happened.

 

[jpeepers]

Just keep playing around until you get that run.bat file to successfully work. Might take some playing around like I mentioned.

Will do. I have already unplugged it several times, rebooted, tried a different USB port etc. Argh.

Man these Samsungs are a pain in the butt to root etc! Hahaha. My last phone was HTC Hero and everything was really simple to root and flash.

Thanks.

.

 

[Paul627g]

If you read back in previous posts, people have tried everything we talked about already and end up buying a new USB cable and bingo! I know its stupid, cable works fine for mass storage/charging but sometimes doesn't work for Odin/ADB.

Also you may want to uninstall the drivers and try again. Normally it will take a few minutes for the drivers to fully install once its recognized by the phone.

 

[jpeepers]

If you read back in previous posts, people have tried everything we talked about already and end up buying a new USB cable and bingo! I know its stupid, cable works fine for mass storage/charging but sometimes doesn't work for Odin/ADB.

Also you may want to uninstall the drivers and try again. Normally it will take a few minutes for the drivers to fully install once its recognized by the phone.

Yeah, when I rooted the first time (2.5.1.0) I had issue, turns out it was the cable. I am using a good one now (at least it worked before?)

Whats weird is I can open a cmd prompt and do a adb reboot, adb shell etc. and it all works fine? That leads me to believe I am connected and talking to the phone just fine?

.

 

[jpeepers]

Here is the whole first part of the script running.

Original one click made by joeykrim and one click installer made by noobnl and f
iron
busybox by skeeterslint
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
168 KB/s (0 bytes in 5392.000s)
2 KB/s (0 bytes in 43.000s)

[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2382, 2382}
[*] Searching for adb ...
[+] Found adb as PID 2363
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
Root was not obtained after 60 seconds. Make sure the phone is connected and tha
t adb is working. If adb shell isn't root, reboot the phone and try the script a
gain.
Press any key to continue . . .

It looks like it is not even pushing these file to the phone..
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb push root.sh /data/local/tmp/root.sh
?


.

 

[Paul627g]

Do you have access to a different computer? I remember some people having issues being older computer, how old I'm not sure. Just remember someone had troubles, couldn't get it to work and tried a different computer and first attempt it worked.

 

[jpeepers]

Do you have access to a different computer? I remember some people having issues being older computer, how old I'm not sure. Just remember someone had troubles, couldn't get it to work and tried a different computer and first attempt it worked.

No, don't have another computer here at home.

Getting really frustrated now. Using the adb.exe that is in my android SDK tools folder I can push files to the phone, change permissions etc. But using the script or adb version in the oneclickrootcwm3 folder I can't do anything. Won't push files, won't change file permissions, nothing. I even tried coping the adb.exe version from the sdk over to the CWM3 folder and no go.
I've rebooted everything, changed USB and nothing.

Think I'm going to give up for now. Maybe later I'll Odin back to stock and try again but it's becoming too much work right now.

Thanks for the help!

.

 

[GSXRdude]

I am curious as to the meaning of a particular error message I m getting in CWM 3.0.0.5, hopefully somebody can help... A few days ago i used the one click root method w/CWM 3.0.0.5 to go to ext4 then flashed Viperrom 4.0.2c. Everything worked fine and have been flashing different roms to try them out. When I 3 finger solute, I wipe data 3x, cache, but when I select adcanced then wipe dalvik, a line pops up below saying "e:unknown volume for path[/sd-ext]". Note, this appears before I even scroll down to select "yes" to confirm the wipe. Wierdly, whether I back out at this point or select yes to confirm, "dalvik cache wiped" appears. Anyone know about this error message and if I am even wiping it even though it says "dalvik cache wiped" afterwards? Thank you.....

 

[Paul627g]

I am curious as to the meaning of a particular error message I m getting in CWM 3.0.0.5, hopefully somebody can help... A few days ago i used the one click root method w/CWM 3.0.0.5 to go to ext4 then flashed Viperrom 4.0.2c. Everything worked fine and have been flashing different roms to try them out. When I 3 finger solute, I wipe data 3x, cache, but when I select adcanced then wipe dalvik, a line pops up below saying "e:unknown volume for path[/sd-ext]". Note, this appears before I even scroll down to select "yes" to confirm the wipe. Wierdly, whether I back out at this point or select yes to confirm, "dalvik cache wiped" appears. Anyone know about this error message and if I am even wiping it even though it says "dalvik cache wiped" afterwards? Thank you.....

I'm not positive about the error, but judging from the /sd-ext command its pointing towards your SD Card. This could be just a fluke error or possibly a sign of a problem with your SD card.

Anyone feel free to correct me if I'm wrong.

 

[durrett syndrome]

2.2 DK28 DONE!...now curious about other ROMs

I used ODIN to do put FROYO on my Epic. My phone has the following...2.2.1, DK28, Kernel Verison: 2.6.32.9. I want to try a custom ROM that I can just put on my SD card and update and be done. I see many ROMs talking about different Kernels, some require EXT4, SDT??? etc and I dont want to run into any issues.

I think I want to to the Truly Epic bc everyone seems to enjoy is but like I said I dont want to do get an updated ROM and not have everything I need and be stuck with a non-working phone.

 

[Paul627g]

I used ODIN to do put FROYO on my Epic. My phone has the following...2.2.1, DK28, Kernel Verison: 2.6.32.9. I want to try a custom ROM that I can just put on my SD card and update and be done. I see many ROMs talking about different Kernels, some require EXT4, SDT??? etc and I dont want to run into any issues.

I think I want to to the Truly Epic bc everyone seems to enjoy is but like I said I dont want to do get an updated ROM and not have everything I need and be stuck with a non-working phone.

Your best bet is to read the various ROMs we have listed here. Check the first post, the feature list and change logs so you can see what has been added or removed during the phases of different builds on the ROM.

Concerning TrulyEpic Rebirth it is a very simple ROM but also runs very well. Ragnarokx has provided all the links required to download and flash any Sprint apps or Samsung apps that were removed from the ROM. Along with those are many of the most common add ons/themes/apps that people use on a day to day basis provided in the first post also.

Any further comments, feel free to ask.

 

[ragnarokx]

I'm not positive about the error, but judging from the /sd-ext command its pointing towards your SD Card. This could be just a fluke error or possibly a sign of a problem with your SD card.

Anyone feel free to correct me if I'm wrong.

This sounds plausible to me.

Formatting the SD could fix this (make sure to backup its contents first on your computer)

I used ODIN to do put FROYO on my Epic. My phone has the following...2.2.1, DK28, Kernel Verison: 2.6.32.9. I want to try a custom ROM that I can just put on my SD card and update and be done. I see many ROMs talking about different Kernels, some require EXT4, SDT??? etc and I dont want to run into any issues.

I think I want to to the Truly Epic bc everyone seems to enjoy is but like I said I dont want to do get an updated ROM and not have everything I need and be stuck with a non-working phone.

Follow post #1 - it has everything you need.

 

[harismahesh]

When I download OneClickRootCWM3.zip and try to extract it iam getting an error "unexpected end of archeive." Please help.

 

[Paul627g]

OneClickRootCWM3.zip has been downloaded dozen and dozens of times. The file has been verified as working.

Try using WinRAR/WinZip/7zip to open the file..

 

[stormglove]

I'm confused I am trying to get the truly epic ROM you created and from that thread was sent here as I am still running the stock eclair 2.1. This thread says I need to have the DK28 ROM to continue though? Sorry I'm a noob and just trying to figure this out.

 

[Paul627g]

@stormglove, yes first you need to upgrade to Froyo. After you have made that upgrade then you can use the OneClickRootCWM3.zip in the first post of this thread to complete the upgrades needed to be able to run TrulyEpic Rebirth.

Go to the link I provided below.

[How to] Factory Restore (or Fix a Bricked Phone)

Look for the section I have listed below at the link I provided and follow the installation instructions for Froyo.

New: Restore to Froyo DK28

 

[narf]

Do not use CW3 with stock DK28 ROM

I keep seeing the same messages over and over here, with people thinking they've bricked their phones because they get stuck at the Samsung screen. Each time it is because they have installed Stock Froyo TK28, then unlocked it using CW3. The problem is that CW3 will convert your file system to EXT4, and Stock Froyo WILL NOT BOOT on an EXT4 file system. Guess how I know :-*

To root Stock Froyo DK28, use CW2.5 which will not mess with the file system.

If you screwed up and used CW3 with Stock Froyo DK28, use Odin to reflash Stock Froyo DK28 and all will be well. Use the instructions on this link:

http://forum.androidcentral.com/epi...12-how-factory-restore-fix-bricked-phone.html

Someone make this a sticky before every newbie thinks they've bricked their phones.

 

[Kikoshi]

I keep seeing the same messages over and over here, with people thinking they've bricked their phones because they get stuck at the Samsung screen. Each time it is because they have installed Stock Froyo TK28, then unlocked it using CW3. The problem is that CW3 will convert your file system to EXT4, and Stock Froyo WILL NOT BOOT on an EXT4 file system. Guess how I know :-*

To root Stock Froyo DK28, use CW2.5 which will not mess with the file system.

If you screwed up and used CW3 with Stock Froyo DK28, use Odin to reflash Stock Froyo DK28 and all will be well. Use the instructions on this link:

http://forum.androidcentral.com/epi...12-how-factory-restore-fix-bricked-phone.html

Someone make this a sticky before every newbie thinks they've bricked their phones.

The thing is that people should already know by now that CW3 turns your file system to ext4...I don't really see how that is hard to miss, when it states it right on the intructions, and im a n00b to this.
Btw edit your header abit because it will give off the wrong aspect.