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

[ragnarokx]

Hey all,

I am surprised this has not been addressed yet. I am on stock 2.2 now, and am used to Z4 one click rooting.

If I root using the .bat file in the OP, is there a similarly easy way to unroot if I choose?

Thanks in advance,

Matt!

What version of z4root did you use?

And to unroot, you can use Odin. The advantage of this root method is that is gives you ClockworkMod Recovery.

 

[KillerQ]

What version of z4root did you use?

And to unroot, you can use Odin. The advantage of this root method is that is gives you ClockworkMod Recovery.

Rag,

It was one of the newer versions of Z4 - and I only used it to root my Epic when it was on 2.1 stock.

If I root using the .bat file here, and I use odin to unroot, is it just as simple to UNROOT it as it was? I have never dabbled with odin, and I am not sure if it will force me to reinstall something new over my current install, or if odin simply removes the root.

 

[mlauren]

Ragnarokx, you are the man!

Once I saw EXT4 support on EB13, I knew it was time to get off DK28. 24 hours later, I haven't looked back yet. Rotation lag is gone, wifi stays connected, battery life improvement and the phone is just generally snappier! I know it will only get better from here, but I just wanted to say thanks for getting us all started on EB13/EXT4 and so fast to boot!

I'm having some problems getting rid of the boot animation glitch, though. I tried flashing a few CWM3 compatible boot animations from A454nova's mods thread, but I always end up with a boot animation that flashes between the new animation and the stock one. Rebooted tonight in my car and I swear the damn thing almost gave me an epileptic seizure o_0

At the end of your OP you mention that flashing a new boot animation should resolve the boot animation glitch. Would you mind linking me to one that will work as expected?

By the way, TER mini theme 1.8 works great on EB13/EXT4 so far!

 

[Paul627g]

Ragnarokx, you are the man!

Once I saw EXT4 support on EB13, I knew it was time to get off DK28. 24 hours later, I haven't looked back yet. Rotation lag is gone, wifi stays connected, battery life improvement and the phone is just generally snappier! I know it will only get better from here, but I just wanted to say thanks for getting us all started on EB13/EXT4 and so fast to boot!

I'm having some problems getting rid of the boot animation glitch, though. I tried flashing a few CWM3 compatible boot animations from A454nova's mods thread, but I always end up with a boot animation that flashes between the new animation and the stock one. Rebooted tonight in my car and I swear the damn thing almost gave me an epileptic seizure o_0

At the end of your OP you mention that flashing a new boot animation should resolve the boot animation glitch. Would you mind linking me to one that will work as expected?

By the way, TER mini theme 1.8 works great on EB13/EXT4 so far!

I think I know the fix to this. I can't post the fix right now I'm mobile.

@ Ragnarokx, if your watching I think we just tackled this with the shutdown animations deleting out the old overlapping files.... delete_recursive, etc.. ?

 

[ragnarokx]

Rag,

It was one of the newer versions of Z4 - and I only used it to root my Epic when it was on 2.1 stock.

If I root using the .bat file here, and I use odin to unroot, is it just as simple to UNROOT it as it was? I have never dabbled with odin, and I am not sure if it will force me to reinstall something new over my current install, or if odin simply removes the root.

Odin returns you to a completely blank, stock state. You'll have to reinstall anything you need.

Ragnarokx, you are the man!

Once I saw EXT4 support on EB13, I knew it was time to get off DK28. 24 hours later, I haven't looked back yet. Rotation lag is gone, wifi stays connected, battery life improvement and the phone is just generally snappier! I know it will only get better from here, but I just wanted to say thanks for getting us all started on EB13/EXT4 and so fast to boot!

I'm having some problems getting rid of the boot animation glitch, though. I tried flashing a few CWM3 compatible boot animations from A454nova's mods thread, but I always end up with a boot animation that flashes between the new animation and the stock one. Rebooted tonight in my car and I swear the damn thing almost gave me an epileptic seizure o_0

At the end of your OP you mention that flashing a new boot animation should resolve the boot animation glitch. Would you mind linking me to one that will work as expected?

By the way, TER mini theme 1.8 works great on EB13/EXT4 so far!

Interesting. That was a bit of an assumption on my part about the boot animations. I thought the DK28 ones would work on EB13. I'll change that part of the post. Keep an eye on this thread for boot animations as they become available.

I think I know the fix to this. I can't post the fix right now I'm mobile.

@ Ragnarokx, if your watching I think we just tackled this with the shutdown animations deleting out the old overlapping files.... delete_recursive, etc.. ?

But the boot animations are contained in a single zip file, so the same theory wouldn't apply like it would with the shutdown animation and its loose picture files. Perhaps I'll poke around in EB13 and see if I can't find some fix.

 

[Omniren]

Quick question (sorry kinda new). I want to keep the stock Samsung Rom. If I switch over from RFS to ext4, will my stock Samsung Rom still work? Thanks in advance.

Assuming that I DO NOT do anything to the stock rom (in other words, I just follow your directions and then after it is all done, reboot the phone and start it up normally).

 

[ragnarokx]

Your stock ROM will remain, but you'll gain the ability to flash themes (it will "deodex" your system).

 

[Omniren]

Thank you!! Ragnarokx!

 

[gitit20]

Your stock ROM will remain, but you'll gain the ability to flash themes (it will "deodex" your system).

Ok i think i got this understood haha So i just want to be sure this will not nuke my phone to like new condition? I will still have all my setting apps and so on i will just be rooted with cwr 3xxx and be on the EXt4 file system?

 

[Omniren]

One more question:

Where do I type in "adb shell mount" to check if I have ext4? Do I open command prompt and do it?

 

[Omniren]

One more question:

Where do I type in "adb shell mount" to check if I have ext4? Do I open command prompt and do it?

Nm. Stupid question. The terminal... haha.

 

[madinky]

I would use Odin to go back to stock and try again. Could be a bad flash.



Part 2, Steps 1 & 7

Thanks,
Took a few hours trying to figure out what odin was and how to use it. and that I had to backup all my files etc. but now it's running much smoother.

At start up the "metal" Android logo was flashing on my first time.
this time its a solid logo and so far no problems.

 

[dlm308rem]

When running the run.bat file I get an error on the line: adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system any ideas would be greatly appreciated. it says mount: operation not permitted.

Thanks in advance.
Fred,
dlm308rem@gmail.com

 

[kitchin]

worked really well, great instructions. Since i'm new at this, yours being the first attempt at anything, is there anywhere i can find well done instructions on getting a new boot animation? i saw the Xoom animation and now im hooked. Thanks again for the awesome job

 

[ragnarokx]

When running the run.bat file I get an error on the line: adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system any ideas would be greatly appreciated. it says mount: operation not permitted.

Thanks in advance.
Fred,
dlm308rem@gmail.com

Is this Part 1 or Part 2 where this problem occurs?

worked really well, great instructions. Since i'm new at this, yours being the first attempt at anything, is there anywhere i can find well done instructions on getting a new boot animation? i saw the Xoom animation and now im hooked. Thanks again for the awesome job

Myself or Paul627g will work on that today and try to have something posted by tonight.

 

[dlm308rem]

It is in part one when running the one.click.2.5.5. I have odin back to stock then ran the samsung update to eb. all seems well I do have root access, as when I adb shell and su it allows me and I do see it on the epic 4.g to allow. I have had problems in the past with this device as it relates to installing clockworkmod. One of my biggest reason for rooting is free hotspot tethering. I can install the wifi tether -pre8.apk it installs and runs but will not broadcast to be seen by other devices. The other reasons are for flashing different kernels and roms till I find one I really like.
Here is the entire batch job messages.

C:\download\SAMSUN~1\again\eb13\one.click.root.exploitv2.5.5>run
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 *
Mount system as r/w, cleanup old files, do some basic configuration
mount: Operation not permitted
cannot stat 'rootsetup': No such file or directory
Unable to chmod /data/local/tmp/rootsetup: No such file or directory
/data/local/tmp/rootsetup: not found
rm failed for /data/local/tmp/rootsetup, No such file or directory
rm failed for /system/app/Asphalt5_DEMO_ANMP_Samsung_D700_Sprint_ML.apk, Read-on
ly file system
rm failed for /system/app/FreeHDGameDemos.apk, Read-only file system
Copying files onto phone...
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
cannot stat 'busybox': No such file or directory
failed to copy 'remount' to '/system/xbin/remount': Read-only file system
Setting permissions...
Unable to chmod /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/remount: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
link failed File exists
Installing busybox...
Installing clockworkmod redirector
failed to copy 'recovery' to '/system/bin/recovery': Read-only file system
push: recoveryfiles/recovery -> /system/bin/recoveryfiles/recovery
failed to copy 'recoveryfiles/recovery' to '/system/bin/recoveryfiles/recovery':
Read-only file system
push: recoveryres/images/progress_bar_right_round.png -> /system/bin/recoveryres
/images/progress_bar_right_round.png
failed to copy 'recoveryres/images/progress_bar_right_round.png' to '/system/bin
/recoveryres/images/progress_bar_right_round.png': No such file or directory
chmod: /system/bin/recoveryfiles/*: No such file or directory
chmod: /system/bin/recoveryres/*: No such file or directory
Unable to chmod /system/bin/recovery: Read-only file system
Installing clockworkmod recovery...
1401 KB/s (0 bytes in 313888.000s)
2288 KB/s (0 bytes in 5820868.002s)
RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /data/local/tmp/zImage
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
Cleaning up files...
rm failed for /data/local/tmp/rageagainstthecage-arm5.bin, No such file or direc
tory
rm failed for /data/local/tmp/root.sh, No such file or directory
Press any key to exit the script.
Press any key to continue . . .


Fred

 

[hun73rA]

so far this has worked very well. thanks!

 

[yujioh]

By any chance, does anyone's Home Button fail to work after running this update?

 

[Agent0013]

Messed up accelerometer

I applied the official update.zip file to go to 2.2 and then ran the one click root listed in step one to root the phone. I just wanted to restore backup data saved with Titanium Backup.

Now the accelerometer z-axis does not work right. The x and y raw data go from -10 to 10 as you tilt the phone. The z goes from -19 to -10, and apps like Google Sky Map don't track the sky at all.

This is the second phone this has happened to right at the same step. Last time I ran the scrip that applies ext4 at the same time as rooting the phone, this time I stayed on RFS and just did the root. (one.click.root.exploitv2.5.5.zip)

Is there a way that the exploit is erasing some calibration data for the accelerometer and messing it up that way? Or is my computer frying out the circuits?

I have insurance, which is why I got a new phone, and they tried replacing the tilt sensor, along with the whole slider, but it did not help at all. I thought before it was fried, but after happening a second time, maybe it is just a calibration value somewhere. Anyone know how I might fix this. I have tried to use the sensorcalibutil_yamaha and it can change the readings from a range of -19 to -10 to ranging in -10 to 0, but it never goes above 0, which is needed for the device to track above the horizon.

 

[ragnarokx]

Phone should be lying on a flat surface when calibrated.