[Root] Samsung Epic 4G Official Froyo EB13 w/Optional EXT4

[Paul627g]

I NEED HELP!

my phone is stuck on the Galaxy S screen and it has a Android going through it blinking and it vibrates 1 time then 3 times fast

what do I do!


edit the galaxy s screen went away but it still has the android name and it vibrates the same

its been 10 min since this started

EDIT: I pulled the battery and tried the restore but it didnt work - I tried the reset factory settings or whatever and now every time I press the bottons at the bottom of the screen it crashes

Which method of root and cwm were you trying to obtain? Under normal conditions rooting/cwm 2.5.1.0 rfs system wouldn't do this. If you were trying to convert to CWM 3.0.0.6 EXT4, did you finish the conversion by flashing a EXT4 ROM before rebooting?

 

[leftkidney]

I followed the directions on the first page of this thread

I was on EB13 stock that I installed using the samsung software that wipes everything on my phone - I had DK28 before so no OTA and I didnt need anything on my phone so I wiped it


then I rooted then confirmed this with titanium backup

I moved on to part 2

I hold buttons it reboots and does its thing, so I follow directions at step 6&7 and I dont reboot I do the kernel flash so I do that and it does its thing

the phone rebooted and there was an "Android" icon/word in landscape mode that was blinking all funny - then the Galaxy S logo came up and it stayed like that for about 7 min then when I pressed the power button for a second it went away and it was just a black screen with that "Android" icon/word blinking and the 1 normal vibe pause 3 fast vibe that I know happens when something force quits or whatever - but this would never stop

after about 15 min of this I pulled the battery and turned it back on having the same thing happen again

so I did the 3 finger boot and tried the restore option and it said it worked and when I reboot the phone that "Android" icon/word was still there but the phone booted up and things worked until I pressed any of the 4 buttons at the bottom and then it would lock up and the screen wouldnt work or power button and it would go to a black screen with that "Android" icon/word blinking again only to start back up and do the same thing again if I pressed one of those buttons


so I did the samsung software flashing thingie that I did before and it worked fine except for I am back at a fresh phone again

I have now just rooted and am leaving it at that for now until I figure this out

thinking about trying this one and using odin - http://forum.androidcentral.com/epi...-pre-rooted-deodexed-clockwork-rfs-ext4.html- what do you think, I will probably be going with the midnight rom unles someone can say otherwise

 

[Paul627g]

I followed the directions on the first page of this thread

I was on EB13 stock that I installed using the samsung software that wipes everything on my phone - I had DK28 before so no OTA and I didnt need anything on my phone so I wiped it


then I rooted then confirmed this with titanium backup

I moved on to part 2

I hold buttons it reboots and does its thing, so I follow directions at step 6&7 and I dont reboot I do the kernel flash so I do that and it does its thing

the phone rebooted and there was an "Android" icon/word in landscape mode that was blinking all funny - then the Galaxy S logo came up and it stayed like that for about 7 min then when I pressed the power button for a second it went away and it was just a black screen with that "Android" icon/word blinking and the 1 normal vibe pause 3 fast vibe that I know happens when something force quits or whatever - but this would never stop

after about 15 min of this I pulled the battery and turned it back on having the same thing happen again

so I did the 3 finger boot and tried the restore option and it said it worked and when I reboot the phone that "Android" icon/word was still there but the phone booted up and things worked until I pressed any of the 4 buttons at the bottom and then it would lock up and the screen wouldnt work or power button and it would go to a black screen with that "Android" icon/word blinking again only to start back up and do the same thing again if I pressed one of those buttons


so I did the samsung software flashing thingie that I did before and it worked fine except for I am back at a fresh phone again

I have now just rooted and am leaving it at that for now until I figure this out

thinking about trying this one and using odin - http://forum.androidcentral.com/epi...-pre-rooted-deodexed-clockwork-rfs-ext4.html- what do you think, I will probably be going with the midnight rom unles someone can say otherwise

Yes I would recommend the all in one Odin package, Froyo EB13/prerooted/CWM3.0.0.6/EXT4.

The procedure you did above could of just "screwed up" for whatever reason. It does happen from time to time, there are alot of system changes going on and one little glitch in the conversion to EXT4 is all is takes to blow the whole thing.

 

[MikeMc890]

Instead of doing Part 2 step 3, can't I just use a new rom that comes includes an ext4 kernel such as the ACE rom?

 

[zerzat]

That was unbelievably easy. I spent hours rooting my old moto backflip and all of 3 seconds on step 1 to root my epic. Great job guys

 

[zerzat]

Step 2 just as easy as the first. awesome work

 

[Sirus213]

I tried to search the thread before asking, couldn't find an answer so heres my concern:

I followed the steps and during the final installation of the EB13-DUALFS-KERNEL.zip my phone keeps restarting and vibrating for the last 5 mins is this normal?

 

[leftkidney]

I tried to search the thread before asking, couldn't find an answer so heres my concern:

I followed the steps and during the final installation of the EB13-DUALFS-KERNEL.zip my phone keeps restarting and vibrating for the last 5 mins is this normal?

SEE, thats the same problem I had

I just had to restore to before EXT4 and then use the samsung software to reflash back to 2.2 EB13 - I then just rooted and am waiting on an answer to as why this happened

maybe I will just try the other method that I mentioned in my earlier post

 

[The Harrington]

im currently running oneclickcwm3 and while running run.bat it is hung up at push: recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/icon_installing.png

any ideas? Its been sitting for a while now

I am having the sane problem that dsalman was having. Have rerun the run.bat file at least 5 times and I keep getting stuck at recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/icon_installing.png". Should I just keep trying again and again? When ragnatokx says to stop and try again should I reboot the phone each time or just exit the cmd.exe screen and just rerun the run.bat file? Or should I start from stp 1. Any advice would be appreciated.

TH

*** But of course it works the very next time after I posted this message***

 

[EpicTornado4g]

Ok. Did step 1 and 2 with no problems. Absolutely the easiest root job since Universal Androot. I do have a question about the deodexed version of eb13. After step 1, i had around 398mb free on my phone memory. After step 2 and removing all aps to reflect what i had after step 1, i was at around 317mb free. I did a wipe cache partition and wiped dalvich cache and ended up with around 339. My question is this: Is the extra usage due to the deodexed rom? Or, is there a temp installation file somewhere that i can remove to free up some memory?

 

[Paul627g]

Ok. Did step 1 and 2 with no problems. Absolutely the easiest root job since Universal Androot. I do have a question about the deodexed version of eb13. After step 1, i had around 398mb free on my phone memory. After step 2 and removing all aps to reflect what i had after step 1, i was at around 317mb free. I did a wipe cache partition and wiped dalvich cache and ended up with around 339. My question is this: Is the extra usage due to the deodexed rom? Or, is there a temp installation file somewhere that i can remove to free up some memory?

For one, when your running stock Froyo EB13 or Eclair, whatever OS then you add root and CWM, you have to take into account for those two new things. Root has some files that were added to your phone taking up additional space and CWM also has its own set of files. So that is where your extra file space is probably coming into play.

 

[anon(67968)]

I just wanted to say thanks to Ragnarokx, Paul627g, and all the other people that made rooting so simple and easy. I've only been on Android for 6 months or so and was tentative to mess around with rooting for a long time. I decided to wait until Froyo came out because I didn't want to have to mess with getting back to stock. I got the OTA update the day before it was pulled and had no problems with it, so I decided to go ahead and start tinkering. After many failed USB cords, I finally found one that worked, and using these instructions was a breeze. I soon found myself messing around with ROMs(thanks Paul and Ace 1.7) ad removals, getting rid of bloatware, and so much more. Just making my device so much more enjoyable and fun than I had ever thought possible, and I had already been plenty happy with my Epic. Big thanks to everyone that contributes here, your hard work and efforts are very much appreciated!

 

[5111]

I got the

abd connection will be reset. restart abd server on desktop and re-login.
Wait for phone to reconnect...


It has been that way for about 5 minutes. Now what?

 

[5111]

Mount system as r/w, cleanup old files, do some basic configuration
99KB/s (0 bytes in 4793.000s)
_


Now it is stuck there. Any help?

 

[Paul627g]

If I remember correctly your device should reboot automatically on its own when the rooting process is done. Your computer I think finishes up by saying something to the effect of "Press any key to continue" or something when its finished the installation.

I do it so blindly now because I've done it so many times I don't pay attention anymore, anyone who has done it recently please correct me if I'm wrong.

 

[5111]

I finally got it finished up, downloaded Titanium backup, and it said that I was not rooted. So I am in the process of trying it again.

Do I turn off USB Debugging before running Titanium backup (Free)?

 

[Paul627g]

Debugging will not effect anything while running apps. I forget to shut my off from time to time and it will not effect anything.

Sometimes the Root process does fail as Ragnarokx mentions I think in the thread or one of our other rooting threads. It may take a few tries before your computer gets it right.

Some troubleshoots.

- Try a different USB port. Back of computer/laptop are usually the best.
- Different USB cable if available.
- Shutdown and Reboot both your computer and device if root fails to have a clean start.
- Disable any anti virus/spyware detection programs while rooting.

 

[5111]

I think that it actually worked this time. I got an error code, but Titanium Backup doesn't say that I am not rooted.

I'll try the next step.

Thanks again for all your help. I'm sure that I will need more of it.

Now I'm just trying to decide if I want to do the EXT4 part so i can try some of these ROMS everyone keeps ranting about!

 

[leftkidney]

I tried to use an app that was a light meter of some sort, needed root access and it said it couldnt get it, my phone wasnt rooted

but titanium backup works fine so I must be

 

[Khoi Nguyen]

Thank you, I rooted my phone and install EXT4, and ClockworkMod Recovery v3.0.0.6. Everything went very smooth except now I am no longer able to connect to my wifi network. Do you have any clues to what happened?

Nor Bluetooth connectivity when I checked this morning.