yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] leaderbuilder:
Might need some more reading. Agat63 is a forum member. He is a generous and valuable developer and contributor here. He has put together custom CWM recoveries with stock kernels and he's built many from source. Recoveries that he's put together are referred to as Agat's recovery. Just as the one's put together be ru have his name. They've done the coding compiling and work.

Please do yourself a favor. And read a little more and you'll get it.
[Samsung Epic 4G Touch] JCred:
What prevents its from having a permanent recovery (e.g. Amon_Ra for the OG Evo). From my understanding, Samsung seems to feel the need to repartition for every update, but why can't something reside on the phone that tricks updates into ignoring a reserved/hidden portion of storage?

Samsung: just one-click (or countless hours) away from awesome. :D
[Samsung Epic 4G Touch] MoHoGalore:
Kernel/recovery are together with this phone...
[Samsung Epic 4G Touch] Danielhammons1:
Will do, thanks though, I thought this may have been what I was looking for the title mislead me lol
[Samsung Epic 4G Touch] JCred:
I understand that much, but don't all custom recoveries have a kernel? I guess what I'm asking is why/what is different about this device that prohibits the use of a stable, OS version agnostic, permanent recovery, i.e. what it's the cause? Is it hardware native, a byproduct of Samsung code, or an inherent hurdle produced by Android 4.x (this is my first device to run ICS and jelly bean and I never ran gingerbread on it)? I hope I don't come off as complaining - just the opposite - I'm amazed at the effort you devs have to put into each new release and am just trying trying to learn and understand. Again, thank you all!! :thumbup:
[Samsung Epic 4G Touch] garwynn:
Recovery images do not always have a kernel (zimage) because they are usually in a separate image called boot.bin. This one merges the teo and their init routines.

Binary count up to 80. Swapping recovery binary doesn't break first boot but obviously won't work without the symlinks and scripts. Now a process of going through sbin symlinks and script s until we find the culprit.

Sd card still not always mounting in revovery. Wonder if vold is not launching as it should...
[Samsung Epic 4G Touch] Danielhammons1:
I will, sorry I ask a lot of questions it's just like there seems to be so many answers and ways to do everything I just want to make sure I am understanding correctly but thank you all for your patience, I appreciate the help greatly
[Samsung Epic 4G Touch] jdsingle76:
I think you posted in the wrong thread Daniel :). Reading so much you're getting confused, not a bad thing in XDA.

On another note, hello G my friend, glad to see you still have all your scruples after dealing with this kernel+ recovery stuff. As always, thank you and Agat for your dedication and hard work on this. I am certain you are close! :beer:
[Samsung Epic 4G Touch] garwynn:
Home due to flooding so still plugging away.

Issue with first data is in m symlinks. Think it's mkdir but still doing a few at a time until I know for sure.

External SD card not mounting in this test but that may just be an issue of vold not running. I'll work on that next.

Internal memory working fine.
[Samsung Epic 4G Touch] jdsingle76:
Stay dry bro, and especially that build box lol(kidding). Thanks for the updates! Keep safe my friend.
[Samsung Epic 4G Touch] garwynn:
FINALLY!

First boot after data is now working properly. Apparently the symlink for mkdir (using the busybox in CWM) creates the dirs in a manner that causes other apps to have permission errors. Remove the symlink and it works fine.

Preload was added but I haven't tested. I'm building a 0.3.16 now for all builds and will post TARs shortly.

At a minimum it should work for internal memory backups/restores, data wipes and the new kernel without reboots.

Once we get the external SD card mounted we'll update the version to 0.4.0.

I rebooted to ROM and it too doesn't see the SD card. Now to figure what I broke in fixing this...
[Samsung Epic 4G Touch] xthedakmanx:
Not sure if this has been discussed before (probably has :P) But is the recovery not setting permissions correctly or somethin?

Roms don't seem to want to boot, expecially on GB28, with a fresh start. They work fine after a dirty flash though.

Example:

Install GB28 Stock Rooted

Runs fine.

Install GB28 kernel+agats

Runs fine.

Install http://xdaforums.com/showthread.php?t=2230938 through recovery

Works fine

Format everything and install it through recovery

NOT fine :P
[Samsung Epic 4G Touch] garwynn:
I just fixed that problem. New builds for all 3 coming as soon as sd card is visible again.
[Samsung Epic 4G Touch] xthedakmanx:
Hooray ^_^
[Samsung Epic 4G Touch] garwynn:
Figured I broke something in the init scripts and since all those changes were not needed except for 2, replaced them with stock, re-added what was needed and seems all good. Tested preload backup and also seems okay.

Building 0.4.0 for all 3 and will have out sometime today. Unless someone finds a new big issue these should be a good daily... but as always will need your help testing. Will post update when links are up.

One thing - for the moment I've removed Agat's recovery and added a brand new CWM 6.0.3.0. I'll be re-titling that soon and removing some of the "Nos" that I know most folks hate.
[Samsung Epic 4G Touch] garwynn:
Well, daughter's taking a nap so got done faster than I thought. Version 0.4.0 posted for all 3 including MD5 checksums on OP of each.

And unless a big problem pops up I'm going to take a break and relax this weekend and let you all give some feedback. Enjoy!
[Samsung Epic 4G Touch] robrooter:
Awesome garwynn. I am glad you have worked out the bugs. So does 4.0 still have the governors?

Enjoy your break. You have earned it!!!

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] garwynn:
Yes. All govs in again.
[Samsung Epic 4G Touch] robrooter:
Great. I am running comadose. It requires 3.0...will flash 4.0 now to test if it still works for everybody.

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] gharlane00:
Sweet enjoy the well earned down time.
[Samsung Epic 4G Touch] btoddweber:
Awesome! !!!!

Jellyverse 3 mixed w/ ComAdose 1.4 Crossbreeder while modded on pegasusq & noop!!
[Samsung Epic 4G Touch] helix4u:
Test results 0.4.0:

External sdcard not showing up in either recovery or rom
[Samsung Epic 4G Touch] MoHoGalore:
I'm assuming GB27 since you're Sprint but want to confirm what you're using..
[Samsung Epic 4G Touch] jdsingle76:
Awesome man. Thanks for everything. Flashing now
[Samsung Epic 4G Touch] garwynn:
Let me check again..
[Samsung Epic 4G Touch] helix4u:
Correct.

Having adb problems as well. Gunna run home for lunch and test adb on my regular environment.
[Samsung Epic 4G Touch] robrooter:
Yep same here. No SD card at all.

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] jdsingle76:
Same G and MoHo, no go on mount usb storage in cwm, only phone's hd shows up when hooked to pc via usb. Running latest jv, flashed through MO.
[Samsung Epic 4G Touch] DarkEye45:
I flashed 0.4.0 and I CAN see the External sdcard in recovery but CANNOT see External sdcard in ROM.
[Samsung Epic 4G Touch] gharlane00:
When I boot to recovery I get

E:Can't open /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't open /cache/recovery/last-log

E:Can't open /cache/recovery/last-log

When I try to do a backup I get

can't mount backup path

No SD when looking in Root Explorer.
[Samsung Epic 4G Touch] kvevand63:
Garwynn..first off I would like to thank you, Agat, and all other devs involved with the kernel. Very much appreciated. I just flashed 0.4.0 via mobil odin, checked the clear dalvik box. Device sat on Galaxy II splash screen for approx 15 seconds, then rebooted fine. However, no S/D card found, and also if this is of any help, I use Tegrak o/c and this message appeared; 'failed to install o/c module, insmod failed to run'. Again thanks for all you do for the e4gt, reverting back to 0.3.0 for now, waiting patiently for updates.
[Samsung Epic 4G Touch] garwynn:
Tested GB27 0.4.0 tar and sd card is visible. ADB working in stock, recovery probably needs to probably just be changed again.
[Samsung Epic 4G Touch] crawrj:
Also missing SD in both recovery and system.
[Samsung Epic 4G Touch] jdsingle76:
Hmmm, you were able to mount usb storage in cwm? What steps did you take if you don't mind sharing
[Samsung Epic 4G Touch] garwynn:
USB mounting not working. I got close but device id not found.

Confirmed SD card not visible in ROM. Looking into it.
[Samsung Epic 4G Touch] jt_hatch:
Tested 0.4.0 (tar via modin) w/ Jellyverse 2.0 & confirmed same thing (no external SD in ROM).
[Samsung Epic 4G Touch] helix4u:
Clear the cache from recovery and you shouldnt get those cache errors anymore.

Btw adb issues i mentioned above were having to do with my work machine. Adb is working on my regular home setup.
[Samsung Epic 4G Touch] jdsingle76:
In cwm, install zip from sd card I'm getting E: Can't mount /sdcard/. I can't get it to show up anywhere bro, no matter what I try. Hope that helps
[Samsung Epic 4G Touch] blackcanopy:
Maybe I don't quite understand.. I flashed 0.4.0 using 0.3.0 kernel/recovery and rebooted. I then booted into 0.4.0 kernel/recovery and made a nandroid. I then booted the device and used root explorer and navigated to storage/extSDCard/clockworkmod/backup and the backup I had just made was there.

While I was on recovery I did notice that choosing to install from external SD card only allowed the top 20 or so ( or however many fit on the screen) to appear in the list, but alloyed me to see external SD none the less.

one more thing..., if the kernel could not see the external sd card, wouldn't we lose the data stored on that per app? Meaning widget apps settings as well as apps settings. I haven't noticed anything out of ordinary using 0.4.0 kernel.... So what am misunderstanding?

Edit: has anyone having issues with external SD tried mounting external SD in recovery.. Or in settings?

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] MoHoGalore:
To the edit comment, yes. Won't mount in recovery.
[Samsung Epic 4G Touch] garwynn:
0.4.0 already redone for Sprint and Virgin - Boost doing as I type.

Seems this one (losing external SD card in ROM) was broken by the updated defconfig so I've gone back to the old one.
[Samsung Epic 4G Touch] btoddweber:
So updated can see sd?

In a jellyverse riding a tweaked pegasusq
[Samsung Epic 4G Touch] garwynn:
Yes, tested GB27 on mine before posted.

All 3 redone. Boost was also missing ramdisk due to typo so that one HAD to be done one way or the other.
[Samsung Epic 4G Touch] fabolousrmx:
Hey everyone I'm getting random SoD's with this kernel and comadose tweaks. I'm on jeleverse 3, kernel 3.0 and tweaks 1.4.

Any tips on how to solve?
[Samsung Epic 4G Touch] garwynn:
How much do you want to bet I left in hotplug?

I'll look at it tomorrow. Spent too long on this today.
[Samsung Epic 4G Touch] jdsingle76:
You certainly have Garywnn. Take the rest of the night off, that's an order lol. And have a :beer:
[Samsung Epic 4G Touch] garwynn:
Binary count hit 100. Should I leave it or TA it? :)
[Samsung Epic 4G Touch] helix4u:
Test results for updated 0.4.0:

So far, so good.

ext-sdcard problems have been eliminated (now visible in recovery and rom)

backup/restore - good

data wipe - good

battery pull does not lose paid apps (user suggested test)

zip installs - good

Edit: Data Wipe and nandroid restore confirmed to now be working. I like it :)

---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------

HA!, never hurts to reset it every once in a while :laugh:
[Samsung Epic 4G Touch] dataman:
Thanks GArwynn.. on GB27 sPrint Ko Rom with Goddly 1.4 and TD AIO

SD card shows up in both recovery and ROM.

clear cache and dalvik works fine and running zip files works fine. didn't do any data clearing nor backup
[Samsung Epic 4G Touch] Stryke_the_Orc:
LOL, I hadn't wiped it since I started working on multiwindow, when I reset it the other day it was 403:what:

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] blackcanopy:
Has anyone tried a battery pull to see if it bootloops or if we lose paid apps? I would try but I'm out and about not near a PC (safety net) to recover if something goes bad.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] leaderbuilder:
What I've found so far. [Stock Odexed, Stock Kernel, with TD's AOI odexed mods.]

Flashed .tar successfuly via Mobile Odin (leaving clear Dalvik unchecked).

Boot into ROM could see and use ExtSD.

Back to recovery. Could see and use ExternalSD.

So on to create Nandroid. It Backed up - boot image, recovery image, system data , android secure, cache,

AND

preload.

Cleared cache and Dalvik cache. Rebooted, system upgrading/updating and then ROM booted without issues.

Checked MD5Sum of backup (via AFV app) and it was successful.

ExternalSD and files still available.

Rebooted to see if CPU changes (on demand/noop) would stick; They did and everything else seems to work too.

Later tonight, if I get home at a decent hour, I'll try a full X2 wipe install an AOSP ROM then wipe and restore nandroid.

Thanks again garwynn Looks great!
[Samsung Epic 4G Touch] gharlane00:
New 0.40 is working perfectly for me. SD card mounts in recovery and ROM. Backup ran without a hitch.

Thanks!!
[Samsung Epic 4G Touch] crawrj:
In addition to this:

ADB works from recovery

ADB sideload works

Can't mount usb to pc from recovery

I wiped cache and dalvik and rebooted to system no problem

Factory reset from recovery and was in a boot loop

Did a restore and could boot again

Went back to recovery and did a factory reset got stuck in a boot loop

Odined stock tar

Odined recovery

Did factory reset and no problem

Installed rom and did a factory reset and no problem

Installed my stock zip that wipes data and no problem

Restored data only and did a factory reset and no problem

Did a complete restore and wiped data and back into a boot loop

So it appears that something was corrupt in my original system

To recap, the only thing that isn't working for me is that I can't mount usb to the computer from recovery.
[Samsung Epic 4G Touch] jdsingle76:
What rom are you running?
[Samsung Epic 4G Touch] cerj:
Im watching your kernel/recovery Backup the Preload partition right now. Think you may have it garwynn. Cant restore at the moment, but I will let you know shortly. The recovery is saying Preload Backed up successfully. Thank you
[Samsung Epic 4G Touch] helix4u:
when you got the bootloop after a restore, you're probably restoring the old kernel in the process... that'll give ya a good ol bootloop.
[Samsung Epic 4G Touch] crawrj:
I will double check that but don't believe it is the case. Because I hadn't restored when I got the first boot loop. Also I made a backup while on .4.0 which is what I restored so that wouldn't be it either. Not sure what the issue was but still testing. I just Odined back to stock, installed .4.0 and now my sdcard is gone in recovery and system again.
[Samsung Epic 4G Touch] helix4u:
did you make the backup pre or post updated-0.4.0? The first release had those issues.

We're having some fun downtime while they do update work on the site.... I love it when that happens.
[Samsung Epic 4G Touch] crawrj:
That is the real question. I am thinking so but haven't gotten to test it yet. But that wouldn't explain the first boot loop because that was definitely on the current release. After I Odined the current .4.0 again I have lost my sdcard completely with the system up. Oddly it shows up in recovery.

Edit: After another reboot it is gone from recovery and system. f#$@ Odined back to stock and sdcard is back.
[Samsung Epic 4G Touch] rdavis429:
It took a whole, but generating md5 sum and then I should be good!

Edit: :good:
[Samsung Epic 4G Touch] boXerrumble:
Installed updated v0.4 zip in recovery over v0.3, installed Exit_Only tweaks, and installed Crossbreeder. No issues. Made sure to Wipe Cache/Dalvik before flashing.

Been running it for about 2 hours now. Will report any issues if they arise.
[Samsung Epic 4G Touch] xpanmanx:
0.4.0 running strong here!
[Samsung Epic 4G Touch] robrooter:
Did some time tests for ya garwynn ;) but...

Firstly, I seen the qouted error as well. A davlik and cache wipe and reboot recovery makes it go away. A work around is to flash kernel as a zip in recovery following the same above steps.

Times!

Cache/ davlik - 5seconds

Recovery reboot - 30 seconds

Nandroid backup - 6 min

Data wipe - 15 seconds

Phone reboot - 4 and a half minutes

Reboot to recovery from rom - 30 seconds

Cache / davlik wipe - had same results

Restore Nandroid backup - 4 minutes

Reboot to backup - 3 minutes ( the time includes android optimization so it can be shorter depending on app count ;) )

General phone settle in time from a restore- 30 seconds.

I say it is working great so far!

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Working fine in ROM on my fiancé's GB08 rooted leak. At least I don't think I upgraded her to GB27 yet. Will try to get the phone away from her tomorrow to do recovery tests.

Thanks Garwyn!
[Samsung Epic 4G Touch] abadasstanker69:
Wow. This is awesome. Running great here! Thanks!

Had to brush up on the available governor options. In case anyone needs a quick reminder or even an in depth explanation

http://xdaforums.com/showthread.php?t=1663809

I flash your grand dad's phone... Cuz I'm incredible
[Samsung Epic 4G Touch] helix4u:
I still think you have the pre-updated 0.4.0...(mainly because I can't for the life of me reproduce the issue) I'd go re-download and replace the ones you have on there just to make sure.

I've had this error a few times swapping kernels and what I do to fix it is simply do a "wipe cache partition" in the recovery - reboot, and all is good. No dalvik reboot or any of that... wiping dalvik causes that annoying optimization of apps on rom boot that I try to avoid if I can help it.
[Samsung Epic 4G Touch] blackcanopy:
Garwynn, you might want to remove +Agat recovery from your thread title until his recovery is included again (if it does in the future) because people are confusing your kernel/recovery and calling it agat's 4.0. No disrespect/discredit to Agat intended here, but the title is a little misleading if the reader overlooked your post on page 52 saying that a new recovery is being used in your 0.4.0kernel.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] garwynn:
I need to talk with him tomorrow on that. Should be able to add back now but will lose preload until I update his. Or we will indeed relabel the CWM as a new Agat. More soon.
[Samsung Epic 4G Touch] dschachm:
I though you couldn't flash exit's and crossbreeder?
[Samsung Epic 4G Touch] boXerrumble:
Exit's tweaks are only compatible with Crossbreeder and Seeder. Otherwise, they shouldn't be flashed with other tweaks.
[Samsung Epic 4G Touch] crawrj:
No I was 100% sure I had the right kernel. After a few more hours of testing I think I found my issue. Everything was fine until I went to install my hotspot and power mods. I installed the hotspot and right after that the power mod. After the power mod finished I hit back and the phone rebooted by itself and went into a boot loop. The odd part is that I have done that dozens of times on 0.3.1. Gonna do some more testing today.
[Samsung Epic 4G Touch] dataman:
What power mod do you use? if I may ask..

any link?
[Samsung Epic 4G Touch] crawrj:
I am using this one. http://xdaforums.com/showpost.php?p=40106679&postcount=18

Edit: OK I found the issue I was having. Still not 100% sure why yet. But after a few hours of testing I decided it had to be one of the Mods causing the boot loop. So I checked all four versions of my mods and discovered that the update binary of the Odexed Hotspot was completely different than the other three. I fixed that zip and copied it to my phone. I went into recovery and installed both Odexed zips again and no boot loop. I rebooted and repeated the process about three more times. Everything is working now except the one problem of not being able to mount the sdcard to a computer while in recovery.
[Samsung Epic 4G Touch] WhiteZero:
0.4.0 did not seem to agree with my Kobridge GB27 ROM (with his 4.34A tweaks, Camera Mod, and tdunham's AIO 3.3). I'd boot and get to my homescreen, but it would then reboot itself after about 20 seconds. So I flashed back to 0.3.1, confirmed it booted OK and stayed up. So I flashed back to 0.4.0, booted up, and I'm greeted with the Android Welcome screen to enter my name. Phone then locks up with a constant vibro. So I boot back into Recovery and flash back to 0.3.1, and all is well again.

So yeah, I'm afraid to try it again...
[Samsung Epic 4G Touch] garwynn:
Folks, it's hotplug. I mentioned it already that I thought that was it.

Please give me time to get it removed.

In short,

If you're on 0.3.1 and 0.3.0 didn't work then 0.4.0 will not either.

I'll get it fixed as soon as I can.
[Samsung Epic 4G Touch] WhiteZero:
Ah, sorry. I'm not too well versed in all this. :eek:
[Samsung Epic 4G Touch] dataman:
I guess we need to explain in the OP that ko's tweaks are not compatible with the governors recovery kernel. Remove ko's aggressive tweak and install goddly's tweak pack v1.4 with the v0.4.0 recovery kernel...

Kobridge is busy with multiwindow and did not have a chance to update his tweaks to work with recoveries with governors
[Samsung Epic 4G Touch] garwynn:
Actually what I'll do is just remove it permanently from the kernel. Ran out of time yesterday when I swapped the defconfig. Been causing more harm than good anyhow.

Hopefully removing it will avoid the new dynamic hotplug from starting up.
[Samsung Epic 4G Touch] kobridge:
Thanks for this Kernel. This saves hundreds hours for me for multiwindow testing.
[Samsung Epic 4G Touch] bigbry87:
DL now. I will test the Sprint version.

Sent from me & my E4GT, on whatever ROM is the latest & greatest...
[Samsung Epic 4G Touch] willv23:
thanks for this, Testing Sprint version
[Samsung Epic 4G Touch] optimummind:
Just flashed the Sprint one and it's working great so far. I expected 4G speeds to be gimped, like in the past source releases, but it's great~! Yay~! On the stock kernel, my download was 8100. On the source, I got 8457~! :D Thank you!
[Samsung Epic 4G Touch] Stryke_the_Orc:
You aren't kidding, the way I was doing it sucked:p:D

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] primo523:
Just flashed with mobile Odin. Worked like a charm.. Flashed a battery mod right away... Profit :D

Thanks guys.
[Samsung Epic 4G Touch] jdsingle76:
Stryke, you may get the multiwindow WIP in no time now brother! :thumbup::beer:
[Samsung Epic 4G Touch] rancur3p1c:
What steps do I need to do to do this myself?

Edit oh this just kernel not rom itself
[Samsung Epic 4G Touch] mjs2011:
So even though I'm extremely happy on the TBAS4 Rom, if I wanted to try out a different Rom, would this recovery be considered "safe"? If so, I'm guessing it would only be safe to flash TW roms correct?

Just thought it may be good to clarify do we don't see an influx of emmc brick victims.
[Samsung Epic 4G Touch] dasesq:
I can confirm. I'm usually one to get slow 4g on source built kernels. But got over 12000 down on 4g
[Samsung Epic 4G Touch] rancur3p1c:
Think you need to get on to this recovery safely but once you're on it you can flash any number of jelly bean builds without problems
[Samsung Epic 4G Touch] CyberpodS2:
When I flash this on White out Rom I lose access to my ringtones other than the ones that came with the rom. Did it twice to verify. Not sure if any other changes yet, still playing. :) Flashing the rom over itself and clearing the caches fixed it. Also if I use the ADD option for ringtones in folders it won't save anything I pick. If someone has a suggestion of what to try or do to establish if it's a ROM or KERNEL problem, I'm all ears.