yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] raytez:
could someone break this down a bit more ....casue i have tried this over and over and every time it seems to work but always boots to stock recovery. dont understand why it isnt sticking
[Epic 4G Android Development] flyers2114:
It looks as though it worked......did you try to boot into it?
[Epic 4G Android Development] gdbassett:
Thanks Bobdud5. I will give it a try, (however I'm already on noobnl's Andromeda v1.3.0). If this doesn't work, can I use the samsung recovery to return to stock and then re-do all of the steps, (1-click kernel install followed by 1-click recovery)?

UPDATE: Reinstalled the same adromeda kernel I already had installed (v1.3.0) followed immediately by 1-click recovery and it took.
[Epic 4G Android Development] evoguyfhp:
just did this on the epic worked amazing!! :D
[Epic 4G Android Development] krazyflipj:
How would I know if the kernel installed? Is the kernel name different under about phone setting?
[Epic 4G Android Development] flyers2114:
you should see Samsung noobnl Andromeda Galaxy Kernel v1.3.0.....in settings/ about phone/build number
[Epic 4G Android Development] krazyflipj:
Thanks! So it looks like i can't get the recovery or the kernel to work. Damn this is starting to piss me off!!

FYI I'm already rooted via the following method found here:http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/

Is this why its not working?
[Epic 4G Android Development] lv2bll:
people are having trouble with that root method, try the one click method stickied on top, i suggest you factory restore if you go that route though
[Epic 4G Android Development] aztecjester:
Ok so I'm having the same problem as a lot of other people. It only boots to samsung recovery tool. I have unmounted my sd card and ran the .bat a couple of times. I'm pressing all three buttons and holding them to power on... still nothing! Should I start from scratch and redo?
[Epic 4G Android Development] dangdang:
How do we uninstall this recovery and go back to stock?
[Epic 4G Android Development] krazyflipj:
Uninstall method in OP
[Epic 4G Android Development] dangdang:
So on our phones the stock/custom recoverys coexist?

I'm used to flashing on the n1 and don't yet understand how samsung partitions their phones.
[Epic 4G Android Development] jimmyz:
My experience for whats it is worth

1. Tried the one click clockwork installer- got no error messages but could not boot into the custom recovery

2. Installed the Andromeda kernel- then reinstalled the clockwork recovery- NOW I can boot into the custom recovery!

One question- is there a way to flash back to the stock rom using this recovery?

EDIT- for the hell of it I reflashed the stock rom with odin the re-ran the one click clockwork installer- this time it worked without pre-installing the andromeda kernel!!!
[Epic 4G Android Development] krazyflipj:
Did u remove this before doing the update? If so, were u able to install clockwork after update?

Sent from my CM6 powered device
[Epic 4G Android Development] plmiller0905:
After installing the update, I re-rooted my phone by using the 1-click method w/out the kernel and ran the clockwork recovery bat file. However, when I push all three buttons, the phone goes into stock recovery and not clockwork.

any ideas?
[Epic 4G Android Development] skeeterslint:
You need to reflash a boot kernel before you can reinstall a recovery after the update.
[Epic 4G Android Development] plmiller0905:
What do u mean?

Just to try, I went back to stock, rooted my phone using 1-click w/out the kernel, flashed clockwork, flashed the update.zip, then ran the root w/ the kernel and my phone worked well. I didn't have 1 problem. I also had clockwork. But is this the method we're not suppose to use. We're not suppose to the kernel with the update or can we?

I know we can't update without the stock kernel. But after we update can you then flash the 1.3.0 kernel. Because I did and like I said I didn't have any problems.

but let me know what you think.
[Epic 4G Android Development] krazyflipj:
So you were able to flash clockwork after the update?
[Epic 4G Android Development] plmiller0905:
It flashed correctly, but when I press all 3 buttons to go into clockwork recovery, it takes me into stock recovery instead.

However, when I unrooted my phone (Odin), then re-rooted w/out the kernel, flashed the update, re-rooted again but this time w/the kernel, then flash clockwork, everything worked. But that's where I'm confused because it's postings that state not to use the kernel with the update....so I don't know what to do.

All I know is that when I unrooted my phone (1-click unroot), then got the update, re-rooted (1-click w/out the kernel) and flashed the clockwork...I cannot get into clockwork,
[Epic 4G Android Development] Firon:
Do NOT flash 1.3.0 after updating. Stick with stock.
[Epic 4G Android Development] plmiller0905:
ok...that's where I'm at now. But clockwork doesn't work after I reflash it.
[Epic 4G Android Development] jimmyz:
can you PLEASE elaborate on this comment. Sorry for the noob question but what exactly is a boot kernal- in other words why cant you load a custom recovery using the stock kernal? thanks
[Epic 4G Android Development] plmiller0905:
Yeah...can you please explain.
[Epic 4G Android Development] krazyflipj:
Im so lost on this. Please correct me if im wrong but this is what I've gathered so far from diffrent threads:

- to flash clockwork, u need custom kernel

- you can't flash custom kernel if you've updated to DI07

- you can flash update while root and have clockwork

Sent from my CM6 powered device
[Epic 4G Android Development] guruleenyc:
a. for clockworkmod, you need to be rooted

a. not sure...mod?

a. yes
[Epic 4G Android Development] guruleenyc:
Anyone know if ClockWorkMod ROM Manager is working with this? I know its not working with Quick Boot app...
[Epic 4G Android Development] plmiller0905:
Ok...I'm going to unroot using Odin and return to fully stock, then I'm going to root using the 1-click method without the kernel, then I'm going to flash clockwork and last I'm going to flash the update and see if this works....I'll report back.
[Epic 4G Android Development] PlankLongBeard:
Method..

K, I just went through it like you guys right now.. :rolleyes:

Did find something of interest though.. If you Odin to Stock.. Then Update.. Then flash the Kernal W/ Root and then The recovery you get what we seek.. :D Then, to clean up the Non-1.3.0 use, use the uninstaller as this will flash stock everything, including the zImage, besides recovery.. ;) Then flash the 2.2.4 aaannnddd your good.. :p

Enjoy..
[Epic 4G Android Development] poulosjr:
Is there a true clockwork recovery dedicated for Epic 4G in the works I really don't want to go thru the backdoor route LOL :(
[Epic 4G Android Development] plmiller0905:
So clockwork will still be there Because we're flashing it after the update ...correct?
[Epic 4G Android Development] krazyflipj:
Before I try this, I wanna make sure I understand correctly. So what you are saying is after update you:

Step 1) Flash Kernel (Directions found here)

Step 2) Flash clockwork following directions here

Step 3) Uninstall following Uninstaller found in step 1

Step 4) Flash 2.2.4 found here

Do you do this all in one shot or is there a reboot needed after each step?
[Epic 4G Android Development] PlankLongBeard:
Yes.. Thats what I did..

I then flashed the update afterwards and it removed Clockwork.. So yes.. Recovery Sticks after the uninstall and 2.2.4 flash. I thought I'd throw that out there too.
[Epic 4G Android Development] krazyflipj:
Thanks for the help. What sucks is that i'm gonna be doing all the commands manually since i'm on a mac. Will report back once I'm done.
[Epic 4G Android Development] odub303:
I was actually able to flash to stock, root with one click 2.2.4, flash clockwork, access clockwork recovery, and apply update.zip. I now have an updated stock kernel, with root and clockwork recovery. Yay!
[Epic 4G Android Development] odub303:
Same problem here, so I did it in a Parallels virtual machine running Windows 7. I got sick of typing all the commands lol.
[Epic 4G Android Development] plmiller0905:
You're a life saver. Thanks so much. I've been trying to get this for the longest. Thanks again :):)
[Epic 4G Android Development] krazyflipj:
Damn after doing all the steps manually i still don't have clockwork!
[Epic 4G Android Development] odub303:
I spoke too soon. Immediately after another reboot I was unable to access Clockwork Recovery. The power on button combo brought me into the standard Android system recovery :(. At lest I have the update installed, all my apps and info back, and I am still rooted :).
[Epic 4G Android Development] bsnyder217:
i keep getting an error "failed to copy Zimage" anything i can do to fix this
[Epic 4G Android Development] PlankLongBeard:
Your Welcome.. I am very glad to have helped..
[Epic 4G Android Development] plmiller0905:
Ok..I did run into a little problem. After I followed all the steps, I flashed back to one of my nandroid backups. Well long story, after I flashed back to that nandroid backup and the phone rebooted, Media Hub was not activated anymore, I lost root and clockwork again.

So what I did was revert back to stock by using Odin, flash the update, flash the kernel, flash clockwork, remove the kernal, flash 2.2.4 (PlankLongBeard Post..Thanks!) Then I used Mybackup Pro to reinstall all my apps because TB wasn't working properly. Nevertheless, after i installed all my apps back onto the phone,I rebooted it. When it came on, I confirmed that I still had my root. I then booted down and confirmed that I still had my clockwork, which i did. I turned the phone back on it...and confirmed that I still had root.

So far everything is working fine like it should.
[Epic 4G Android Development] sdotA85:
Any fix or work around for this error? Dev mode on...Unmount...

exploit and busybox made by joeykrim and one click installer and andromeda galax

y kernel made by noobnl

Press any key to continue . . .

copy and run the exploit (may take 2 minutes)

cannot stat 'rageagainstthecage-arm5.bin': No such file or directory

Unable to chmod /data/local/tmp/rageagainstthecage-arm5.bin: No such file or dir

ectory

cannot stat 'root.sh': No such file or directory

Unable to chmod /data/local/root.sh: No such file or directory

/data/local/root.sh: not found

remove joeykrim root method

mount: Operation not permitted
[Epic 4G Android Development] krazyflipj:
Man I cannot flash this recovery for some reason. The only thing I got working is rooting

*UPDATE* I was finally able to get clockwork on my Epic using a Mac!
[Epic 4G Android Development] noobnl:
fixes in build 31 incompatblilty with build 30 and di07 kernel
[Epic 4G Android Development] ryanmgarvey1:
stuck in recovery

ok..so i finally got clockwork installed and it wont let me select anything and when i pull battery it still goes back to clockwork...any suggestions to get phone booted????? thanks in advance:
[Epic 4G Android Development] :
I was andromeda kernel and I saved the .zip file (root explorer) to my sd card and clicked install by accident. Well install failed but it rebooted to airplane mode and was moving very slow. We'll I left it running all night and the power died in my battery(I fell asleep lol). When I woke up I put a new battery and the phone booted. Everything worked perfectly! Andromeda kernel was my build, and my version was di07. Well I flashed a restore from when I made a backup before the update and It kept booting to airplane mode no matter what I did. I could wipe, do restores of everything, and always the same. I was on the verge of doing a flash to stock with odin, but I restored a backup that was made using clockwork (beta 20 I believe) where it had my date wrong. (December 31 1999 I think)

So after I wiped everything (factory reset, cache partition, and dalvic just to be safe) and restored it and everything worked. It restored me back to dg17, andromeda kernal, everything. (Where as every backup made with beta30 restored me back to my baseband, version, everything was unavailable)

I really think whatever was changed from 20 to 30 in clockwork changed to where something didn't backup correctly. I have 3 backups done with root/andromedadg17, di07 stock, and root plus stock kernel dg17, all made with beta 30.

The only restore that actually works right is the one I made in beta 20 of clockwork. Restoring any of the others after I've done the di07 "update not successful" ota boots me into a slow phone without 3g/voice/data functions. 4g still works though.

I have to restore back to to my beta 20 backup and then wipe everything, then restore whichever file I want. Even "flashing" the v.4 deodex rom has to be done after I've restored my beta 20 backup so I can have mobile network.

If this "issue" is what the incompatability with di07 is in the beta31 version that's cool. Although even after the unsuccessful di07 update install, I did a full wipe and restored the v.4 deodex rom but it always booted without network support. Only by restoring the beta20 backup, wiping, then flashing the v.4 rom would it work.

Sorry if this seems like too much info. Using my phone and add meds wearing off takes me a while to type this all out. Ha!

Sent from my SPH-D700 (codename: awesome)
[Epic 4G Android Development] rldev:
Why does the download link for ver 31 has a file named 30 inside?
[Epic 4G Android Development] jimmyz:
the zimage btw ver 30 and ver31 look identical
[Epic 4G Android Development] gdbassett:
I actually flashed 30 on DI07. I had restored to stock with odin and then updated followed by andromeda immediately before flashing 30 though. I suppose I'll flash 31 for the fun of it.
[Epic 4G Android Development] sdotk:
Any advice????? :'( PLEASE!

one click installer and Clockworkmod Recovery v2.5.0.9 build 30 made by noobnl

Press any key to continue . . .

copy and run the exploit (may take 2 minutes)

* daemon not running. starting it now *

* daemon started successfully *

239 KB/s (5392 bytes in 0.022s)

2 KB/s (88 bytes in 0.037s)

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

[*] checking NPROC limit ...

[+] RLIMIT_NPROC={3712, 3712}

[*] Searching for adb ...

[+] Found adb as PID 2205

[*] 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.

remove stock recovery patcher

rm failed for /system/etc/install-recovery.sh, Read-only file system

rm failed for /system/recovery-from-boot.p, Read-only file system

copy kernel and flasher

1419 KB/s (313888 bytes in 0.216s)

1149 KB/s (5662108 bytes in 4.808s)

flashing kernel

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

page_msize: 4096, phy_unit_size: 262144

src: /sdcard/zImage

dst: /dev/block/bml8 partition size: 0x780000

part_size: 0x780000

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 262144 bytes

read 157084 bytes

read finished

wait 60 second

cleanup

done

Press any key to continue . . .
[Epic 4G Android Development] DevinXtreme:
Before you run the .bat, do this:

adb shell
su
remount rw
exit
exit

You're system isn't being mounted, can't be written to. Had this problem. Also, update to build 31. Has worked better for me in every instance.
[Epic 4G Android Development] Coucher:
I'm rooted using noobnl'a one click method posted here as well and that with through without any problems using the same computer, cable, and drivers, so I'd think that none of those are the issue.

I've tried running this about 4 times with the same results. Still boots into the stock recovery via the volume down/camera/power button method. Any thoughts?

run
one click installer and Clockworkmod Recovery v2.5.0.9 build 30 made by noobnl
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
337 KB/s (5392 bytes in 0.015s)
5 KB/s (88 bytes in 0.015s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2997
[*] 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.

remove stock recovery patcher
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
copy kernel and flasher
1786 KB/s (313888 bytes in 0.171s)
421 KB/s (5662108 bytes in 13.119s)
flashing kernel
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
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/zImage
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 157084 bytes
read finished
wait 60 second
cleanup
done
Press any key to continue . . .

I'm guessing the problem is happening here:

But being VERY new to all of this I'm not sure what could/would be causing this?

Thanks for any help.
[Epic 4G Android Development] Coucher:
This was the problem for me as well.

Did the remount via adb and everything worked fine then on the Clockwork install.

Thanks!!
[Epic 4G Android Development] Poryhack:
Disregard.
[Epic 4G Android Development] Firon:
http://firon.net/xda/one.click.clockworkmod2.5.0.9-flasher-build-31.zip

Try this one. It attempts to remount /system as rw before removing those 2 files. It's otherwise the same as the previous version.

edit: build 32 is up with this fix. Use that instead. :P
[Epic 4G Android Development] guruleenyc:
Awesome! When do you think the Quick Boot, button mapping and ROM manager compatibility will be available?

Thanks for all your hard work!
[Epic 4G Android Development] Xerexis:
After running the one.click.stock.flasher._.root.uninstaller-di07 I was going to install the update from the SD card and rebooted into recovery mode and it booted to the clockwork recovery but the home button does not work to allow me to select the options in clockwork and once the phone reboots it is rebooting to clockwork recovery and that is it. I can not get past the clockwork recovery screen the power button allows me to move between options in clockwork recovery but can do nothing else. can not get the android system to load.
[Epic 4G Android Development] akei1:
press the "h" key on the keyboard for enter, not home:)

menu is back

power is navigate

smiley on keyboard is navigate

h is enter
[Epic 4G Android Development] Xerexis:
Ok so I'm blonde. I knew that and it worked just perfectly. Thank you.
[Epic 4G Android Development] jokarak:
Strangest thing...every once in a while while following noob's scripts to root/install recovery/etc, the bat file will simply not work. However, if I simply follow the bat file step by step by typing it in myself in dos, it will work. My computer must have gremlins. Thanks for all the work, noob!
[Epic 4G Android Development] noobnl:
build 32 is up!
[Epic 4G Android Development] DanDroidOS:
I've tried to run this like 12 times and it wont finish! any ideas? I haven't had a problem with any of them so far, and I'm on my stock rooted ROM
[Epic 4G Android Development] stress1ner:
try running the .bat before plugging the phone in then when it says device not found plug it in, works for me that way.
[Epic 4G Android Development] jusinjusin:
I'm using build 32... and I still get the same problems as the other users. Running stock updated to DI07

EDIT: So, I went into termal, I see the #, so I guess I'm rooted. But the

"remove stock recovery patcher

rm failed for /system/etc/install-recovery.sh, Read-only file system

rm failed for /system/recovery-from-boot.p, Read-only file system"

Is still a little sketchy for me
[Epic 4G Android Development] daddymikey1975:
I really want to flash this clockwork recovery onto my phone, however, after I install the x64 drivers.. reboot the computer, reboot the phone (just for good measure)..

I plug the phone in and get :

Samsung Android USB device = OK

CDC Abstract Control Module (ACM) = (gets hung "installing driver software)

USB Mass storage Device = OK

S3C6410 Android ADB = (gets hung "installing driver software)

left it for about 10 minutes.. I do have USB debug checked..

Should I un-mount the SD card first ??

Normally I can get this type of stuff to work but I really feel like a newb here LOL
[Epic 4G Android Development] ragnarokx:
is there a way to confirm a successful install? it appears everything went through but i can only boot into the stock recovery.

edit: nevermind, used build 30 instead and it worked.
[Epic 4G Android Development] casual864:
Follow the instructions given in this thread about custom recovery.

http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=786305
[Epic 4G Android Development] jakmai:
yeah build 32 isnt working for me either.

edit: nvm i forgot to install the kernal
[Epic 4G Android Development] 1999TL:
install was a breeze. Thanks.
[Epic 4G Android Development] harrybozack:
Does it make sense to take a "nandroid" backup right at the DI07 update, after flashing from stock? That way you can restore that backup and flash any ROM without a problem without having to keep reflashing to stock with Odin3. Does that make any sense? Is this what people do?
[Epic 4G Android Development] flyers2114:
about time you got jumped in!!!.......lol:D
[Epic 4G Android Development] yellowxboy:
downloaded the 32 build but after unzipping the file, the folder is labled 30 ?

update: doesn't matter i guess, it works just fine.
[Epic 4G Android Development] guruleenyc:
I am battling with adb instability, but out ran through part of the way up to adb restart phase several times to no success. My epic is tuning stock rom w/root from an odin process a few days ago.

However, during this process, the phone blanked out a few times and I had to do a batt pull...

Now my phone doesn't shutdown and stay down, re-awakes after full power off....

The phone is stable besides that.

I will try adb out from another laptop today. What do you think happened?
[Epic 4G Android Development] ImSoHungry:
Yes, makes perfect sense. Coming from the Nexus, I had flash frenzy and later on CM nightlies everyday getting flashed, I actually like the calmness of it all right now on the epic and will probably flash only after things I feel needed are added to a rom (video out via 3.5mm, etc). Great work NTL everyone who got this working.
[Epic 4G Android Development] bomix:
Nice Job,

Got it to work

ONE thing to keep in mind if your using the new switch pro Widget that has reboot into recovery, That will mess you up.

I kept trying to get this to work, but the whole time it was me using the widget.

I held vol down + Camera + power button finally went into clockwork.. i'm such a dummy Great work.. now to do some flashing.. muhahhaha