yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] rujelus22:
Just flashed the t version last night and I have to say I like what you have done. I tried the first version you had and you are right that blue was killer to read. So far so good with everything I have tried. Keep up the good work.
[Samsung Epic 4G Touch] greatlakesghost:
Thanks man. Must have been bad luck on my behalf.:rolleyes:
[Samsung Epic 4G Touch] JohnCorleone:
Oh he definitely cares about his work. I don't blame him if he's uneffected by what people think of it though

Edit..unless its a core group of master devs

Sent from my SPH-D710 using Xparent ICS Tapatalk 2
[Samsung Epic 4G Touch] isaac2k10:
love the green and white, great work agat
[Samsung Epic 4G Touch] bigpeng:
Wtf... How did i miss new recovery!

:banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead::banghead:
[Samsung Epic 4G Touch] puff601:
That would be awesome! Downloading now, preciate it guys
[Samsung Epic 4G Touch] steindog99:
The .tar file would go in the pda slot in odin correct?
[Samsung Epic 4G Touch] agat63:
Yes. That's correct.
[Samsung Epic 4G Touch] ntborg:
I see a repacked FE26 coming in the future. Your going to be busy Agat.:eek:
[Samsung Epic 4G Touch] agat63:
I'm kinda ready...:cool:
[Samsung Epic 4G Touch] okantomi:
Have you been following sfhub's suggestions in the discussion thread about the emmc super brick bug? He is suggesting that kernel and rom developers can make perfectly safe flashable zips right now, without waiting for source. It's pretty fascinating.
[Samsung Epic 4G Touch] agat63:
Kernels are pretty safe.

There are only cople of things to be avoided.

I'm on repacked kernels ever since we start gettings them and I'm flashing a lot of zip files. But I'm on TW roms only.

I wasn't following that discussion but I'm defenetly gonna look it up.

Thanks.
[Samsung Epic 4G Touch] okantomi:
This is just the lastest post that touches on his suggestions...

http://xdaforums.com/showpost.php?p=26757432&postcount=400

If you scroll up you will be able to follow in more detail.
[Samsung Epic 4G Touch] ojones838:
Agat63, congrats for Mijjah using your repacked FE22 kernel in his ver 13.4 Blend ROM. I was wondering why it seemed that no one was using it. I guess alot of testing was done before relying on it... ;) Of course it was going to hold up to scrutiny.
[Samsung Epic 4G Touch] agat63:
Out of curiosity I checked Mijjah's thread and it says rom comes with sfhubs repacked kernel not mine.

May be he just forgot to update the thread or he is really using sfhub's repack.
[Samsung Epic 4G Touch] chris41g:
the keys to making recovery safe are two-fold:

recovery:

GB-based or ICS based with a patched ext4 library

update-binary

same as above

as for recovery, mine, and agats are gingerbread based and are safe regardless of the kernel they are packaged in. including wipe functions. point 2 is where it gets tricky. we cant control what update-binary someone packages with a script. if someone uses an ics update-binary and issues a wipe command in the edify script, its brick city, worse than shaq at the free throw line..

so safe is not something i would call it. safer.. maybe, but to be safe it would have to be controlled. until i can exclude ics updater scripts from executing, then IT IS NOT SAFE.
[Samsung Epic 4G Touch] leaderbuilder:
its brick city, worse than shaq at the free throw line..

:)
[Samsung Epic 4G Touch] bigtoysrock:
100% your kernel bud, "Goods" area forgot to get updated, but if you look alittle lower in the builds changelogz, credit to you is there. :D Thanks for your work.

EDIT: OP is updated to what is current.
[Samsung Epic 4G Touch] sfhub:
Just to clarify, ICS update-binary updater scripts are fine in general EXCEPT for "format()". As long as ROM creator gets rid of format() from the Edify install script (let's say replace it with delete_recursive()) the ROM creator should be able to make the ROM install safe, even using the ICS-based update-binary. T.C.P has said he would make that change when he gets back and I've message darchstar but haven't heard back.

Those are the only 2 I know of so far that are using both the ICS-based update-binary AND doing a format() in the Edify install script.

Now once we get ICS source code, from Samsung, folks will likely patch the kernel to block the problematic calls as well so if you use those compiled kernels you'll be doubly safe. Your kernel will block the problematic calls AND (from our current efforts) both Recovery and update-binary install scripts will avoid making the problematic calls in the first place.

I've suggested we take both approaches, because some people will like to stick with repacked stock kernels and at this moment, we cannot be assured of where Samsung put the workaround for the problem. Depending on where they put the workaround, the stock kernel may or may not still be susceptible to the bug. Even if it susceptible, if we have eliminated all the ways the problematic call is made from Recovery and update-binary, then we'll be safe even with an unsafe stock kernel from Samsung.
[Samsung Epic 4G Touch] Kebetz:
Didn't I hear that these latest kernels have a stop gap for that emmc issue?

You stealin' Sammie's thunder?

:p jk jk Well done, man. Flashing now.
[Samsung Epic 4G Touch] Ben's:
Hats off to you agat. Works like a charm! Thank you for all your hard work :thumbup:
[Samsung Epic 4G Touch] neudof:
Great job agat!

Is it possible to remove the factory wipe option completely from recovery until it works?

Was thinking it might help the noobs and the illiterate... and the lazy :-)
[Samsung Epic 4G Touch] bigpeng:
It does work, I've tried it every rom flash (tested since FE10 rogue recovery). It is the "stock" one was the problem. Regardless, I'm not saying to do it, just from my experiences it's been fine... It's much better and cleaner to use Calks format all or Modified format all.
[Samsung Epic 4G Touch] Kebetz:
Come on, man.. you know damn well the preferred method is to flash new firmware while submerging your phone in an even mix of blueberry/pomegranate juice so it receives the proper antioxidants.

Sheesh..
[Samsung Epic 4G Touch] BigJPNut:
Anyone else's init.d support not working with this? agat63 I flashed back to the FE16/rogue kernel you put in your rom by accident and init.d works again. Also tried sfhub plus kernel and it works. I dont know if im missing anything or what?
[Samsung Epic 4G Touch] Esoteric68:
You know it's possible to give well deserved kudos to agat for his work without taking unnecessary and incorrect potshots at the other hard working Devs.

Thanks agat, I flashed your kernel this morning to give it a spin.
[Samsung Epic 4G Touch] darren.wlsn1:
i always see you posting usefull help but this post is best you ever posted(imo)and i totally agree. all the blood/sweat/tears this developers do for us and for free and then ya read your quoted post, just a shame.
[Samsung Epic 4G Touch] CyberpodS2:
How can I tell if it is working, I'll post my findings too.

---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------

+1
[Samsung Epic 4G Touch] bigpeng:
As far as i know init.d works, i applied kobridges tweaks after applying the kernel though and as far as i know, if kernel doesn't have init.d already, it automatically makes it work, but I'm sure if it didn't, agat/ACS would've caught that?

Idk, anything can be overlooked though, these devs working on very little sleep... :p
[Samsung Epic 4G Touch] bigpeng:
You know it's working if you go into the directories like in screen shot and the values match the script in the /system /etc init.d folder.

Mine all does, I'm sure theres other ways to find out if it works but that's one way I do it.
[Samsung Epic 4G Touch] Esoteric68:
Thanks Darren, I suppose I get all 'mama bear' whenever it seems like people aren't appreciating the work of our entire Development community and that is not in anyway meant to take appreciation from agat because he's obviously a very important part of that group. In fact this repack is fantastic!

Thanks again agat :) awesome work as always.
[Samsung Epic 4G Touch] sfhub:
Actually we've duplicated the EMMC brick in multiple recoveries, including stock, so it appears the problem is in the kernel.

Some emmc revisions could be immune to the problem and it isn't deterministic, so you can wipe a couple of times with no issues, than bam the next time it hits you.

That's why I don't really suggest it is safe based on my own experiences. If I happen to have a revision that is immune to the problem, my experiences wouldn't be useful to someone who is susceptible.
[Samsung Epic 4G Touch] Esoteric68:
Yeah I'm part of that wipe a couple of times with no issues group. I'm thankful that people threw up the stop sign for me when they did, although I now have a spare phone, just in case. lol
[Samsung Epic 4G Touch] agat63:
Thanks for explanation.

I didn't even try the wipe and not planning to. Actually even on GB I haven't used that option from recovery menu since Calkulin's format all is faster. Does all wipes in one click instead of 3 (cache/data/system).

I did it for recovery backup/restore option only since SH and Team Rogue don't wanna CWM be packed into ICS kernels yet.
[Samsung Epic 4G Touch] sfhub:
We actually determined the code that Samsung checked in is not in our kernel. Even if it was, we are not clear if it is addressing the issue we are seeing because the description of the bug fix doesn't lead to an immediate connection to the mechanism for persistent damage to EMMC blocks leading them to be unwritable.
[Samsung Epic 4G Touch] rujelus22:
Is there any way to get the ability to do an adb remount. It says Operation not permitted with this kernel.
[Samsung Epic 4G Touch] agat63:
That's one thing I didn't even think of checking/testing yesterday.

I'm at work and can't check it now.

If anyone else can confirm that I would defentetly look into it tonight.
[Samsung Epic 4G Touch] quasarsky:
thanks agat. still waiting on your odin one :)
[Samsung Epic 4G Touch] agat63:
I can do it tonight.

Gotta get home from work.

I was too tired yesterday to make it.

Been 2 crazy days with FE14 and FE16 leaks.
[Samsung Epic 4G Touch] quasarsky:
cool thank you. any chance you can mix this up in there too? :D

http://xdaforums.com/showthread.php?t=1658471
[Samsung Epic 4G Touch] agat63:
Were you asking me?

If yes these tweaks are not part of the kernel.

Those are init.d tweaks and as long as kernel supports init.d you can install them yourself with any rom from provided list.
[Samsung Epic 4G Touch] playya:
Boy have I missed this option since running ICS....
[Samsung Epic 4G Touch] rujelus22:
It works on the Rogue ICS kerenels.
[Samsung Epic 4G Touch] mojo4321:
If you don't want to wait for the tar can't you pull the ZIMAGE from the CWM zip and flash it with MobileOdin, Odin or HC-kTools? I've done this with other kernels and MobileOdin. With Odin I think you use the PDA slot. I have never used HC-kTools, but it has the capability. Can someone who knows more than me please confirm before anyone bricks using these methods.
[Samsung Epic 4G Touch] agat63:
Have you tried to adb shell with this kernel?
[Samsung Epic 4G Touch] ReActiveDisorder:
Very risky agat63 :D I will see how this plays out before I include CWM Recovery With any of my repacks.
[Samsung Epic 4G Touch] agat63:
I haven't been a single day without CWM recovey.

Till I figured out the repack I was using FD02 with CWM.

Now with every build I make one for myself.

Chrisg41 has ACS recovery source on github.

I'll try to recompile/rebuild it without wipe/factory reset option in menu.

As for flashing between ICS and AOSP/AOKP/CM with repacked ICS kernels it has been said so many times not to try that if anyone will do it he/she has no one to blame except themself.

It was risky till it has been figured out what causes the brick. No all we have to do is follow dev's instruction and stay away from steps/tasks that might cause it.

With the develpment I do you can imagine how often do I flash new stuff and CWM recovery never failed me.
[Samsung Epic 4G Touch] The Root:
Crazier things were tried on the old epic. There has to be a level of responsibility the user assumes. I like the experimentation going on here. That's how we ended up with dual boot kernels and such.
[Samsung Epic 4G Touch] chris41g:
I like this thread... I don't have a lot of time on my hands.. but I you have some questions, I'll try to answer them.. I like people taking initiative. My personal suggestion, is to fork the recovery, and rename it.. make it your own.. I can help you on skinning and changing up some features.. but if you want to continue it why not make your own version..
[Samsung Epic 4G Touch] timmetal6669:
Lmao duh, everyone knows about the anti oxidant flash.
[Samsung Epic 4G Touch] bigpeng:
Agreed, name it... Godly Recovery... Or, just Agat63's Recovery, same difference. :p
[Samsung Epic 4G Touch] CyberpodS2:
Plus your OP has REALLY BIG RED LETTERS IN THE WARNING and is in effect the fence between the users and the Lions, Tigers & Bears! If zoos did not put up really big fences they would be responsible for morons getting eaten. IMO if a guy wants to climb the fence, he's free to call for help but if someone doesn't get there in time he might be lunch...
[Samsung Epic 4G Touch] The Root:
Because I asked him to do it. Lulz

I wanted our recovery working again.
[Samsung Epic 4G Touch] JohnCorleone:
look who the wind blew in!! I tested the original ACS Recovery (OG Epic) for Chris and his dedication to perfection is relentless! I think I was testing it for 2 months before he released it. Good to see you around Chris! Appreciate you offering advice and help

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] chris41g:
Hey I like that title.. Recognized Contributor.. If anyone deserves it, you do...
[Samsung Epic 4G Touch] JohnCorleone:
Thanks Chris! Hopefully before long I can contribute more than help and answering questions though.

Edit..I appreciate that coming from you!

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] timmetal6669:
I've use both those methods several times with no issues. That's really not how you brick.
[Samsung Epic 4G Touch] Esoteric68:
Chris thanks so much for your contribution to this project.
[Samsung Epic 4G Touch] agat63:
Thank you very much.

You have been a great help since me trying to build GB kernels.

I do want to change some stuff here and was prepping myselfs to ask for you help (wanted to sync github, setup tools and than pm you).

Thanks for offer.

I'll defenetly try to emprove where ever I can and whatever I can.
[Samsung Epic 4G Touch] timmetal6669:
I gave him mad kudos. I apologize if I offended you. Didn't take any "potshots" directed at anyone though. I appreciate what all the devs do as well as contributers like us. No need to take"potshots" at me either. I even appreciate you esoteric. Thanks.
[Samsung Epic 4G Touch] JohnCorleone:
Lol...finding help isn't always easy..that's for sure! Some things seem to remain closely guarded secrets. I am glad you got your help Agat.

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] Alex1x:
So I can flash this kernel with FE10 rom?
[Samsung Epic 4G Touch] chris41g:
Anything i know, I will gladly tell.. I'm all for open knowledge.. sometimes I can't explain very well and sometimes I just don't know without doing it or looking at it..

a lot of the time I am just very busy. but I try to help anyone who takes the initiative to learn on their own and hit a wall.. not so much to spoonfeed. I have left a few guides and informative post, anyone who has read them knows i'm not a good teacher though lol
[Samsung Epic 4G Touch] agat63:
You are good enough teacher to me.

You just can't teach calculus to some one who didn't take time to learn basic math.

To ask right question one should know at least this:

Where I'm comming from?

Where I'm going?

What is the next step?

If I can't answer those questions for myself how can you do it?

But that's me and my approach to how I'm asking for help.
[Samsung Epic 4G Touch] timmetal6669:
I agree it was a ballsy(i.e.risky) move. Great job and thanks for all your hard work again.
[Samsung Epic 4G Touch] Esoteric68:
See risky sounds better than saying "being the one Dev with the Balls to get a good kernel together" because, intended or not, it did sound like you were saying other devs didn't have the balls to do this. I accept that isn't how it was intended and appreciate you clarifying that, I'm glad we can move forward and stay focused on the important stuff. :)
[Samsung Epic 4G Touch] Proboarder2712:
Nice recovery

Flashed from Rogue recovery 1.2.3(i think) that came with Cal's E4GT 2 ICS 1.5 rom. Running smoothly no issues.

Question if I may.

I can't seem to get my boot animations to start. I put them in system\media file. They worked when I used GB. Ever since I switched to ICS with calk, they wont start up. Instead they display my standard Galaxy animation. I know it isn't the kernel since both rogue and this one aren't starting. I thought read once that if you have a qmg file that it will always take that one so I've moved that one before and threw in the zip and I simply got a black screen.
[Samsung Epic 4G Touch] agat63:
There are few bootanimations available for our phone.

It's not only the zip file you put into your media folder there cople of other files need to be renamed in order for your bootanimation to work.

You can grab one of the zip files from this thread:

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

Replace bootanimation zip files in /system/media folder with your files using 7z copy modyfied zip to sd card and flash in recovery.

That should work becaus the zip's update-script will take care of the rest.
[Samsung Epic 4G Touch] agat63:
Coudn't wait till evening.

Called my daughter and asked her to bring my laptop to work.

Just connected my phone running running this kernel with ACS recovery and tried:

adb shell.

Connected without any problems.

tried su from terminal worked as well.

ls, cd etc.

Everything worked.

So adb shell is working with this kernel.

I'm running my tFE16 odexed rom with this kernel.
[Samsung Epic 4G Touch] timmetal6669:
Perhaps your kernel doesn't have boot animation support. You can manually hack it with root explorer, like this.

Rename /system/bin/samsungani to something else... (eg samsungani.old)Rename /system/bin/bootanimation to /system/bin/samsungani. After that it will load whatever bootanimation is at /system/media/sanim.zip, /sytem/media/bootanimation.zip. Or you can just flash another kernel. (like this kernel agat has posted) I believe.

You can download some kick ACE boot animations HERE

Gimme thanks if I helped you out.
[Samsung Epic 4G Touch] Proboarder2712:
Ah... I see.. they decided to screw with me...

Didn't realise that bootanimations now got update-scripts...

Lil more of a pain but at least I figured out how to make my own now.
[Samsung Epic 4G Touch] tt281gt:
Damn Agat you're a beast! I am glad we have developers like yourself giving us hungry kids the food we need!
[Samsung Epic 4G Touch] steindog99:
adb shell and su work fine...adb remount does not...
[Samsung Epic 4G Touch] chris41g:
iirc adb remount does not work on secure kernels
[Samsung Epic 4G Touch] Nevell:
Agat is this the same kernel from the one you mistakenly released?
[Samsung Epic 4G Touch] Esoteric68:
I'm trying to figure out why my recently installed boot animation (Helix Blue http://xdaforums.com/showthread.php?t=1652725) is working fine running Blu Kuban with agat's repacked kernel. I flashed it the other day when I was on sfhub's repacked kernel. Does that mean it held tight even through the kernel change? (I sound like I'm talking in circles lol)
[Samsung Epic 4G Touch] agat63:
Sfhubs and my repack kernels are supporting custom bootanimation.

If you flashed bootanimation using zip files it should stick till you flash new rom and overwrite your system.

If you apply new rom you would have to apply bootanimation zip again if you want it back.
[Samsung Epic 4G Touch] timmetal6669:
Ya both kernels with boot animation support won't change the current boot animation installed in /system/ media. If you like boot animations, check out some of these kick ACE boot animations HERE
[Samsung Epic 4G Touch] Esoteric68:
Yay, that explains it! Thank you for the great animations as well as this repack, I'm using both of your work. :)

---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------

Thank you for responding. I was looking at your animations earlier. Very nice work. I'm trying to get my son to take my spare E4GT (he's stuck on a Blackberry) and I know he'd love the Simpson's animation. lol
[Samsung Epic 4G Touch] timmetal6669:
Ya I've had some PM's about that Simpsons boot animation. I might get it together tonight and make some movie themed boot animations cause they seem to be popular. I'll try to put a Simpsons boot sound file up later too Hope your son likes.
[Samsung Epic 4G Touch] Esoteric68:
No doubt he will. Thank you.

Oh, also Skyrim related stuff would go over BIG with him. lol
[Samsung Epic 4G Touch] quasarsky:
any luck for the odin tar? :)
[Samsung Epic 4G Touch] timmetal6669:
Make it yourself!

Easy Method: Download agat's flashable zip. Extract the contents. Put on SD card. Use root explorer to navigate to the files you just extracted. Hard press on the zimage. In the sub menu select "create tar". Use it with Odin mobile or pc Odin in the pda slot.
[Samsung Epic 4G Touch] bigpeng:
If you extract just the zImage you can put that right into kernel of Mobile Odin and works as well. Can't rename it or anything.
[Samsung Epic 4G Touch] Ralphie1:
works great thanks!!
[Samsung Epic 4G Touch] rbaucom:
Dang sir you are fast!

Sorry I couldn't try out the adb!

Glad it works!
[Samsung Epic 4G Touch] quasarsky:
itried that. its causing my computer to bluescreen. i'll wait for agat.
[Samsung Epic 4G Touch] bigpeng:
Quasarsky, do what i said and it'll work.

JC can vouch for it I'm sure, i told him how to do it thay way. He didnt know you could, but it worked.
[Samsung Epic 4G Touch] ih8aol:
I think mobile Odin can still see this zip if you extract it first. I have been doing this with ROM's.
[Samsung Epic 4G Touch] agat63:
Mobile ODIN is fine with zImage file and doesn't need tar.

I'm leaving office now. Will be home in an hour or so.

I'll make the tar and will upload it.
[Samsung Epic 4G Touch] CyberpodS2:
Yea I always keep the zip on my card and if I need to use mobile Odin I extract it with a long press...
[Samsung Epic 4G Touch] eljefe27:
Cm9 overwrites kernel and recovery

Edit. And i wouldn't flash cm9 in this recovery as stated by op in first post as its not tested flashing aosp-aokp or cm9

Edit 2 but maybe your in need of a paper weight
[Samsung Epic 4G Touch] quasarsky:
i followed exactly what you said. can you send me hte file to my email if yours worked?
[Samsung Epic 4G Touch] agat63:
ODIN tar with ACS repack is up and running.

OP updated. Link posted.
[Samsung Epic 4G Touch] BigJPNut:
I dont get it...i flashed this in the sfhub plus recovery and then the zimage in mobile odin and my init.d scripts stop working. Im on your FE16 rom agat63. Bad download? When I flash back to sfhub plus kernel or the agat63 FE16/rogue kernel, they work again. Any ideas on how to check this or confirm? For now im checking with rom toolbox and the values are stock with this kernel. The phone seems less snappy too. Like I said when I flash back to the FE16/ rogue kernel all is well. Im racking my brain and asked before, but nobody confirmed 100% their scripts were running properly.