yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] 4hn:
Wipe data?

Thx for your kernel AGAT. :)

been using this couple of weeks and working pretty good!

I want to ask a question, maybe this is a silly question.. :o

I am currently on FH13 with AGAT 0.54 kernel and i am planning to wipe all my data, because i messed up with some stock app (unable to unblock from gemini app manager/titanium backup).

can i wipe from [Settings]-[Privacy]-[Factory Data Reset] or from recovery - [wipe data/factory reset]?

Is it save since I already use AGAT kernel?

or should i use this method?

Wipe data/factory reset from ODIN

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

or maybe there is another safer option?

I live in Asia so I will not risking my phone got bricked.

Many thanks and regards,

Ahn.
[Samsung Epic 4G Touch] agat63:
My FH13 github is plain source. I don't use it for my kernels.

I did merge FH13 source with my FF18 source and my current git is E4GT_ICS_kernel.

That's what I'm using for my 5.x builds.

I don't have time to check my git right now. I'm not home and I'm posting this with my phone.

I'll take a look once I get home but to best of my knowledge that source doesn't have EMC_CAP_ERASE line.

If it does than I'm terribly sorry.

That would mean when I merge 2 sources I forgot to disable that.

I'll post more info when I get it.
[Samsung Epic 4G Touch] gharlane00:
I have done at least a dozen wipes with 5.4 without issue. I'm pretty sure it is safe.
[Samsung Epic 4G Touch] CyberpodS2:
Is it possible that flashing certain JB roms with it might be the issue? Not the wiping by itself like with a format_all.zip but whatever wiping the installer script does is not stopped by the "safe" kernel?? I am not educated enough to do anything more than ask troubleshooting questions...
[Samsung Epic 4G Touch] rwilco12:
A dozen? I average that in a day! ;)

I can add to what Agat said though, I just checked my Repo and I've had over 600 downloads total on his 5.4 kernel. I think the problem may lie with AOKP or JB...
[Samsung Epic 4G Touch] PhAkEer:
That's what I'm talking about ! I knew I had a Mr Glass out there somewhere... ( I NEEEEEEEEVVVVVVVERRR wipe unless it is unavoidable or

if it gets so cluttered with scripts that I have to sift through a couple(Hndrd)mb scattered throughout /etc, /data/log, /data local... its my rule. If I can't find the log I'm looking for instantly, .. it's time for a wipe.
[Samsung Epic 4G Touch] agat63:
Let me try to explain how the recovery works.

When we were dealing with brick back sfhub gave me a nice lecture to this subject.

In recovery:

1. When using tasks from recovery menu like wipe cache, wipe dalvik wipe/factory reset recovery is using binaries packed into recovery.

Since recovery has been compiled with CM7 (GB) source the bug is not present in recovery and any task is safe.

Thus that many successful wipes using my kernels with tREC.

2. When flashing zip files.

Any flashable zip has updater script and updater binary packed into it.

Recovery will read updater script and execute it line by line.

To execute commands from updater script recovery needs binaries and will use binaries packed into zip file.

At this moment your current kernel and/or recovery binaries are not that important since those are not used.

As you can see there are 2 sides to this problem. 2 major components.

You need safe recovery/kernel to perform tasks in recovery and you need safe binaries packed into zip to make it safe to flash.

Please someone correct me if I'm wrong here because that's how I understand the process.

Many ICS rom zip files had GB binaries packed into them so we haven't seen any bricks since CM7 (GB) compiled recovery has been used for wipes.

AOSP/AOKP/CM/JB are coming with their own binaries and I can't say if those binaries are safe.

Crhis41g has created a safe recovery that would use binaries packed into it no matter what binaries are coming with zip.

But since it has an additional argument to use it's own binaries most of old zip would not work with it.

Updater scripts should be edited for that additional argument for recovery to work.

I think we should check with rom dev's and make sure they have safe binary files packed into zips.

Id they have than we should look closer to how ICS kernerls/recovery flashing JB and may be there's something that we need to do to make that process safe.
[Samsung Epic 4G Touch] agat63:
Let me try to explain how the recovery works.

When we were dealing with brick back sfhub gave me a nice lecture to this subject.

In recovery:

1. When using tasks from recovery menu like wipe cache, wipe dalvik wipe/factory reset recovery is using binaries packed into recovery.

Since recovery has been compiled with CM7 (GB) source the bug is not present in recovery and any task is safe.

Thus that many successful wipes using my kernels with tREC.

2. When flashing zip files.

Any flashable zip has updater script and updater binary packed into it.

Recovery will read updater script and execute it line by line.

To execute commands from updater script recovery needs binaries and will use binaries packed into zip file.

At this moment your current kernel and/or recovery binaries are not that important since those are not used.

As you can see there are 2 sides to this problem. 2 major components.

You need safe recovery/kernel to perform tasks in recovery and you need safe binaries packed into zip to make it safe to flash.

So if updater script has format() command in it it will use binaries from zip to perform format() and if binary not safe it might cause the brick.

Please someone correct me if I'm wrong here because that's how I understand the process.

Many ICS rom zip files had GB binaries packed into them so we haven't seen any bricks since CM7 (GB) compiled recovery has been used for wipes.

AOSP/AOKP/CM/JB are coming with their own binaries and I can't say if those binaries are safe.

Crhis41g has created a safe recovery that would use binaries packed into it no matter what binaries are coming with zip.

But since it has an additional argument to use it's own binaries most of old zip would not work with it.

Updater scripts should be edited for that additional argument for recovery to work.

I think we should check with rom dev's and make sure they have safe binary files packed into zips.

Id they have than we should look closer to how ICS kernerls/recovery flashing JB and may be there's something that we need to do to make that process safe.
[Samsung Epic 4G Touch] leaderbuilder:
he he. I know that feeling. with half a day off I've already flashed three different builds!
[Samsung Epic 4G Touch] umrico:
I was on Agat a week ago and thought I was safe. I flashed the format all zip and then installed AOKP. It forze in the middle of the install and I left it for 15 mins but never recovered. Pulled battery...blue LED. Just thought I'd let you know you are not the only one I just didnt post it in the forums as its a risk I take on my own and don't blame anyone for. I did go to IRC to see if anyone knew of anything I could do but of course there is nothing.

Hope this helps in some shape or form!
[Samsung Epic 4G Touch] agat63:
Both cases have 2 things in common.

My kernel and the attempt to flash AOKP rom.

I think for now we can say that these 2 things don't work nice together.
[Samsung Epic 4G Touch] vanberge:
Agreed.

Maybe worth putting in OP if you haven't already?
[Samsung Epic 4G Touch] umrico:
Agreed :)

I must say I love your recovery none the less though and thank you for all you do :)

---------- Post added at 09:29 PM ---------- Previous post was at 09:27 PM ----------

Just for the record, IIRC, it was AGAT 0.5.4 and it was the Build 2 of AOKP JB just FYI and Calkin format all script.
[Samsung Epic 4G Touch] tdunham:
Someone correct me if I'm wrong but I'm pretty sure that 90% of the reported bricks we were seeing (and there were a LOT) right before source dropped were coming from flashing to AOKP not TW ICS. Also, I keep seeing references to the different binaries that are being used to flash in CWM. That could be a contributing factor as well.
[Samsung Epic 4G Touch] Mattix724:
Not trying to hijack this thread, but if you are going to flash any AOSP rom... Odin the EL26 direct boot CWM recovery, wipe data factory reset, flash the ROM, flash gapps, reboot.

No offense to you Agat, I for one think that it has absolutely nothing to do with your kernel. I have used the FI03 recovery without any issue when flashing AOKP. I did not use Calks format all, I simply selected wipe data factory reset and then flashed the ROM.
[Samsung Epic 4G Touch] agat63:
No offence taken.

I'm not a programmer nor am I a coder.

I'm learning as I go and this kind of feed backs and info are very important.

We all trying to make our experience with our phone as pleasant and good as possible and that includes trying different roms, kernels, mods, themes and tweaks.

More feed back we have more chances would be to identify the problem and either fix it or find a workaround to avoid it from happening again.

And it's not important what causing it. My kernel, updater script, updater binaries or something else as long as we can figure it out.

That's the only important part. And as we kinda got to the bottom of the bricks in early day with combined effort of many XDA members I certainly hope we can do it again. But it should be combined effort again.

I'm not that ignorant to call my work "perfect" and "error free".

If you have problems with my work I wanna know it because that's the only way I can try to fix it (if I can).

In early stages my recovery been execively tested by sfhub, isoteric68 and others and was deemed "safe" with some reservations.

We have seen couple of new sources since and few new roms as well. CM10 and JB are new source build roms that are haven't been tested back than.

So, this kernel/recovery combo wile being safe for previous builds might not be safe any more for new ones.

All I want at this moment is to identify the problem and find a cure for it or workaround so no one will walk the wrong path again.

This is very expencive toy we have. Let us keep them safe and working.
[Samsung Epic 4G Touch] wiggerbrand:
Stuck at 99%

Reposting the battery not charging past 99% issue that prguzman1978 previously reported.

If I turn the phone off it will report 100% with blue led. Turn it back on and stuck at 99%.

Notes: I noticed the issue after flashing 0.5.4 via Mobile ODIN.

Previously I had the stock repack of FH13...but switched over to 0.5.4 after having issues with apps on the SD card disappearing. Pretty sure I could charge to 100% with the stock repack.
[Samsung Epic 4G Touch] leaderbuilder:
I believe you are right on, on this TD. Agat too mentioned something about this. It will be interesting to see when/if we can get some source (for our device!) what is going on.

Edit: I see he addressed this above. Darn refresh
[Samsung Epic 4G Touch] rovar:
I've had that happen occasionally after heavy use and partial chargrs. But 19.99/20 times my phone will charge to 100% without issues.

Using .5.4 with FH13 stock

Tappin' Typin'
[Samsung Epic 4G Touch] agat63:
Phone is charging to 100%.

You not seeing it while phone is off charge because theoretically the moment you unplug your phone it's not 100% any more.

It is set in SystemUI.apk and in frameworkres.apk.

Battery is to display % as following:

99%-99.9 - display 99%

We can change that callout to whatever we want. I can make 100% show till the charge dropps to 95 or less but it won't be true.

For any level it showing

X.0 to X.99 - X

That's why you can see 100% only when phone is plugged in.
[Samsung Epic 4G Touch] jbdavisjb:
Show of appreciation

I just wanted to let you know that those of us that want our OTG dongle to be more than a flacid appendage on our E4GT appreciate you picking up the torch. Also, just sent you some ch$$rs via PayPal as a show of appreciation. Our phones are much "smarter" because of you, tdunham, calk, and all the other devs on XDA! Many, many thanks for your labors! jbdavisjb
[Samsung Epic 4G Touch] JamesEh408:
Agreed...thank you
[Samsung Epic 4G Touch] todivefor:
Search is down so I apologize if this has been covered.

I tried ReCalk rom for several days having come from CM9 beta 1. I tried restoring my CM9 backup with AGAT_Recovery_tREC_0.2.2 and it failed with error during system restore. I reinstalled CM9 beta 1 and immediately restored my CM9 beta 1 backup with no problem. Then I restored ReCalk with CWM_based_Recovery_v6.0.1.2 (CM9 recovery) with no problem. So it seems that CM9 recovery can restore an AGAT nandroid, but AGAT cannot restore a CM9 nandroid.
[Samsung Epic 4G Touch] MoHoGalore:
Seen a few posts that cwm6 backups have to be restored via cwm6. Cwm5 won't even do it successfully so its not limited to Agats kernels.

Can't link to the posts just yet but they are out there.

Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
[Samsung Epic 4G Touch] todivefor:
Thanks. Didn't know Agat's was based off CWM5. Makes sense.
[Samsung Epic 4G Touch] MoHoGalore:
Heh, not exactly what i was meaning. Sorry. Saying that other kernel/recoveries have the same issue. Which i hope to link for you soon.

I do not in fact know what Agats base is.(other than thread says source) I apologize for the confusion.

The posts i hope to locate shortly, users found that for any successful restore, of a cwm6 backup, was going back to cwm6.

Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
[Samsung Epic 4G Touch] GWashington:
Curious, anyone running v 0.5.4 with the following files magically showing up on their sd cards?:

efsdev-mmcblk0p1.img

efsbackup.tar.gz

efsdev-mmcblk0p1.img.gz

Ever since I reverted to stock EL29 & then rerooted, back to the same ROM & same recovery, but a different version (AGAT 0.5.4 vs 0.5.2), these files continue to appear, even after deleting them!I flashed the exact same Blazer ICS ROM, the only difference is the AGAT version, other than different baseboards, which is why I'm asking this strange question here.

I have been looking for answers for a week & then today, I finally deleted the files from the sd card, rebooted to find them gone, only to have them magically reappear within minutes. I am at a total lose.

So, if AGAT recovery/kernel is somehow involved in these efs backups, which I doubt, someone let me know before I pull out the rest of my hair! I realize I'm grasping here folks, but I'm desperate ;)

Thanks!

UPDATE: ALSO SEE POST #1826...same question, don't believe it was ever answered.
[Samsung Epic 4G Touch] Omar04:
Hey Agat have some feedback about your kernel and missing SD Card Apps such as Where's My Water and Where's My Perry...

If I flash kernel via CWM or PC Odin then all SD Apps gone and can't move any to SD but

If flashed vía Mobile Odin then all apps on SD or move to SD works like a charm. :confused:

---------- Post added at 02:26 AM ---------- Previous post was at 01:35 AM ----------

Suspects: If not Agat Kernel then Mobile Odin. I will check on that.
[Samsung Epic 4G Touch] rsngfrce:
Yeah, running AGAT 5.4 with stock FI03, I have those files and have been wondering what and where from for a while now. After reading your message, I decided to investigate and while I can't yet give you a perfect answer, I think I can answer a lot...

These files are backups of your EFS partition, which contains a lot of important info such as your IMEI, so these are good to have,you probably don't want to be deleting them. These are related to using the AGAT kernel, if you look in your data/.agat folder, I believe you will find copies of these files there as well (and some other files that were created at the same time as these files).

Do you have ExTweaks installed? I think these files might relate to that as well, because I find reference to these files in regards to the Siyah kernel, so I am thinking that AGAT with ExTweaks generates theses files. I don't THINK I noticed these files before installing ExTweaks.

After you reboot, these files will show up a short time later (replacing the existing ones if you haven't deleted them). What I don't understand myself is exactly what process is generating these backups... they don't generate immediately after you reboot, but a short time later. Not really sure how to use them either.
[Samsung Epic 4G Touch] Omar04:
Confirmed: AGAT recovery. :beer::D
[Samsung Epic 4G Touch] PhAkEer:
You don't use them, (well you can) by design they are used by the kernel (this part is speculation) and replace themselves when there is different information on your system from the backups (as a way to keep the backup current)

When I was playing around trying to fake my way into extweaks It ended up porting my "/data/.phake" folder into my efs backup as .settings

I concluded that the extweaks layout uses efs as its get outta jail free backup system... but I could be way off.

(And I did see somewhere the option to turn it off, like RU does, but I think I saw it in a kernel loaded file.. ie, an uneditable file)

Edit: A thought just occurred to me, hellcats ktool app; the install kernel aspect of it had a couple conflicts with agats kernel a while back so I stopped using it after months,,, but yeah, that app had also had an efs backup/restore feature. If it works with the same format it would make for an easy way to apply the efs backup if needed.

Just a thought.
[Samsung Epic 4G Touch] GWashington:
I don't have ExTweaks installed separately from what is built into the kernel, if that's what your asking, but thanks,

Hey guys,

Would love to hear from Agat on this as well to confirm all of our thoughts...

And, can these efs files be used to restore the efs folder & all it's info, if ever needed?

Thanks in advance Agat ;)

BTW PhAkEer, never used kTool, and keep in mind, the efs files were not being backed up to the sd in v 0.5.2.
[Samsung Epic 4G Touch] rsngfrce:
Stupid question, but will someone please confirm for me that logcat isn't disabled in Agat 5.4? Somehow logcat has become disabled for me and I am just trying to eliminate the possibilities... :banghead:
[Samsung Epic 4G Touch] Sloth:
Agat changed something after 5.2 because there were some charging issues so maybe that's why they don't appear in 5.2 just a thought :D
[Samsung Epic 4G Touch] agat63:
ExTweaks app has nothing to do with script packed into the kernel.

That add is like a frontend/UI for all kernel options and settings.

You don't have to install it to have efs-back perform. It does it with or without ExTweaks app.

In last 2 (I think) versions I have been using slightly modified enhanced ExTweaks scripts made rujelus22.

I did like additional options he added to his script.

Hope this answers some of your questions.
[Samsung Epic 4G Touch] leaderbuilder:
When (soon I pray) we get the source for the latest released/real build (there were some references to source for Boost and RDF for Virgin in another thread http://xdaforums.com/showthread.php?t=1833166&page=84 ),. will you be building your kernel with all the tweaks.

Hope so. Thanks for the work buddy!
[Samsung Epic 4G Touch] agat63:
If new source drops down I'll try to update my kernel to it.

As you know I'm paving the road to move to GSIII and I hope to get it within next couple of weeks.

If I do I won't have that much time for E4GT since my new phone will require some development as well.

But E4GT will stay in the family and I will be able to do some work.

I still hope I'll be able to bring OTG to this kernel before I make a move.

I have ordered the OTG cable and hope to get it in a day or two.

I have everything lined up to work with it. I know our hardware is capable of OTG (we had it on GB) it's a matter of finding right drivers and implementing them.

So fingers crossed.
[Samsung Epic 4G Touch] rbaucom:
Hi Agat, can you possibly check out the combination of your latest kernel blue tooth music streaming and running gps with screen set to navigation.

I re flashed back to stock as phone became so slow as in press screen and 5 seconds later response and would crash reboot within an hour.

If you tell me what log file application to use I'll re flash your kernel and upload log files.

Turning off bluetooth and bam instant speed again. Everything was stock but kernel. The name of the podcast application that I am using is Doggcatcher I have not tried it with any other music playing application.
[Samsung Epic 4G Touch] leaderbuilder:
Source dropped for FI27 http://xdaforums.com/showpost.php?p=32573484&postcount=841

Yay!!

http://opensource.samsung.com/index.jsp

And if you're still up for it what about your awesome slightly moded/themed ROMs? I have used those as my go to drivers. Fast relieable and easy.

Anyways. Thanks again for the work. Looking forward to the SIII stuff too; I may have one coming into the family in a couple months.
[Samsung Epic 4G Touch] rbaucom:
Will be sad to see you go, and thinking about the note2 myself.
[Samsung Epic 4G Touch] agat63:
I didn't think of note 2 because the original Note is too large and it's not comfortable to use.

You really can't do anything with one hand. Always need 2 hands to deal with it.

If Note 2 is a large as Note (and I guess it will be) it is out of question for me.

And believe me when I say I don't have small hands. :p
[Samsung Epic 4G Touch] rbaucom:
Lmao I do have small computer tech hands. I believe it's supposed to be a little taller, and planning on using it with a fly grip. The time to get it is far away so who really knows by then.
[Samsung Epic 4G Touch] agat63:
I think Note is not phone.

It's a Phablett (Phone + tablet). :p

I'll rather have them separatelly.

Not all in one.
[Samsung Epic 4G Touch] tdunham:
Big hands and also a big heart to go with it! :)
[Samsung Epic 4G Touch] lord dredd:
Hey there Agat ,

ssup mate ?

ummm.. i have noted that slow charge is fixed in the latest update as well,but why does my phone takes like forever to get charged fully.

i am seeing it takes like 4 hrs or so :(

i am using latest kernel of yours

clean blue ROM

is there anything i am missing .

thankies
[Samsung Epic 4G Touch] agat63:
Nothing I can think off.

After I posted the v0.5.4 I didn't have any complaints about slow charge in any way.

My phone is connected to PC so often that I never really charge it.

With all the tests I'm running my phone simply doesn't have time to drain the battery and honestly because of that I don't even know how good or bad the battery life is with all the changes and edits. :rolleyes:

I just hope that since there are no complaints it should be not too bad. ;)
[Samsung Epic 4G Touch] rbaucom:
You know I got the Asus transformer tablet before the s2, and after the s2 my wife ended up with it. She plays angry pigs on it. I loved the tablet (Samsung moment user) until I realized by using it how awesome my s2 was. I've probably

Used the tablet 3 times since then to vnc into my pc.

I love the concept of the padfone and the padfone two and if sprint had the padfone that would be my phone.
[Samsung Epic 4G Touch] rbaucom:
So Agat which logging application?
[Samsung Epic 4G Touch] agat63:
The only tool I'm using is adb logcat.

You can output logcat to a text file e.g:

adb logcat > c:/desktop/logcat.txt

Will create a logcat.txt file on your desktop.

You can send that text file to any location on your PC.

Then you can either PM me the text file or pastbin it and send me the link.
[Samsung Epic 4G Touch] rbaucom:
Ok installed it will try to replicate it with tomorrow morning drive.
[Samsung Epic 4G Touch] agat63:
FI27 source build kernel is up and running on my phone.

Too soon to say anything.

It's building and it's booting.

Now I can start adding all the stuff we had in previous kernels.

Just a quick update.
[Samsung Epic 4G Touch] Sloth:
You rock agat :D
[Samsung Epic 4G Touch] agat63:
I can't do all in one day (evening to be exact).

So gimmi couple of days to add everything to the kernel.

I don't want post plain stock.
[Samsung Epic 4G Touch] Sloth:
No worries take as much time as you need we all love your work and I for one am willing to wait :D
[Samsung Epic 4G Touch] rovar:
Take your time.

Tappin' Typin'