yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] JCred:
I've installed all 3 of the .0 releases. 1.0 (flashed via .tar in mobile Odin pro) allowed more to perform a Nandroid with agat. (though I haven't attempted to use it). 2 and 3 would not flash via .tar in mobile Odin pro, but the .zip flashed fine in recovery. Have not attempted any backups in them, but have had no issues with the kernels, themselves (other than the auto power-on when plugging in) governors/schedulers all worked with no-frills cpu control. Flashed the Kobridge universal init.d enabler in 3.0 and, then Comadose 1.4 w/crossbreed and disabled nofrills to see if his clock/gov/sched scripts would stick. They did.

Prior to the source kernel, I have been running GB27 (the sextape leak via one-click-restore) with stock kernel and no mods or scripts. I'm still running it, but with the .3.0 kernel, active busybox/scripts and noticeable improvement. The kernel, itself, has been a solid upgrade. And... I am odexed. Go figure. :D
[Samsung Epic 4G Touch] leaderbuilder:
I remember you saying that. KO. One reason I have not even thought about repartitioning. Even when I had a soft brick some time ago that wasn't responding to usual Odin methods, I contemplated using the partition/PIT fix but finally was able to get a stock odin ROM on.

I'm sure with the guys we have working on it we'll get it.
[Samsung Epic 4G Touch] helix4u:
I'd be willing to bet that if you added that same d@mn "sysctl -w kernel.hung_task_timeout_secs=0" line in to lpm.rc that the boot into rom from charging issue would disappear. Probably best tested with a 0.3.13h build with the changes made to the ramdisk(?)

... I'm still suspecting that why it thinks it has hung tasks is just something not configured right in watchdog dealing with hotplug or something... but again, I'm still pretty new to all of this.
[Samsung Epic 4G Touch] dataman:
Fancy Galaxy S3 is keeping Agat busy

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

Hopefully he will have some time to tweak S2's Recovery before it is abandoned,

I will move away from S2 as well when the LTE 4G is at least equal to Wimax 4G in coverage. That wont happen this year probably. I still love this phone with all the mods going around.
[Samsung Epic 4G Touch] abodamer:
I experienced this as well with 3.1. But just the Music folder contents. The card still had the available space being reported as if the music files/folders were still there. Reformatted the ext SD card and used my latest Ext SD card backup (which I thankfully made before moving to JB as a precaution) to restore everything.
[Samsung Epic 4G Touch] Mattix724:
Knowing how he works, he's not just going to abandon a project until it has been completed. Agat is a good guy and he just needs some time, remember his wife is the one using his old S2.
[Samsung Epic 4G Touch] garwynn:
This resolved the battery charging reboot. Thx.

I'm still stumped on the data wipe causing reboots. So much that I tried building a clean CWM today and testing that.

The results are identical to Agat's.... so no good there. I'll hit Agat up and see if he has any ideas. It's almost as if it's erasing too much but it's doing a format of the partition and not by address - so shouldn't be an issue.

Testing the add of preload on my CWM. But that data issue is a big one IMHO.
[Samsung Epic 4G Touch] garwynn:
Can someone test wiping data in GB27 repack?
[Samsung Epic 4G Touch] robrooter:
I can if not done yet Garwynn.
[Samsung Epic 4G Touch] btoddweber:
So 0.3.13 is good?
[Samsung Epic 4G Touch] garwynn:
After I fix the data issue and test adding both preload and EFS will I release something new. For now 0.3.14 should do simple nandroids and still be a stable kernel.

If you need to wipe data yhe stock kernel or flashing a restore one click seems the best alternatives at the moment.
[Samsung Epic 4G Touch] helix4u:
Confirmed. Also loosing sdcard with 0.3.14. Odin one-clicks save the day again.

0.3.13h is still most stable for me as both a kernel and recovery.
[Samsung Epic 4G Touch] crawrj:
Doesn't work. I even flashed back to EL26 safe recovery and that didn't work either. It appears to be something to do with the new JB file system. Don't know anything about kernels though so I have no idea.
[Samsung Epic 4G Touch] robrooter:
Did you use agats thread? That was the requested test. I did it and jellyverse flashed fine. Full wipe and reinstall. Even did battery mod...and boot animation.
[Samsung Epic 4G Touch] helix4u:
See attached recovery log grabbed from /cache/recovery/last_log after a recovery session in 0.3.14. The first 20 lines-ish and the last 10 lines-ish are the most interesting to me.

The issue I had was no access to sdcard.... but the fstab errors at the top also mention the data mount... so it might be worth looking into for the data wipe problem.

Edit:

I've been trying to find a good place to find logs on what to look at to for the hung threads problem.

https://groups.google.com/forum/?fromgroups=#!topic/android-platform/RwZqc8s1yFY mentions /data/anr/traces

....So I pulled that and attached it as well.

Edit2:

The same log from a 0.3.13h session shows the same fstab warnings at the top.... and I can see sdcard. it didn't show the bottom failed to mount issues though.. but that doesn't give much info to go off of... hrmm...
[Samsung Epic 4G Touch] garwynn:
Confirmed the error is a bad format of data. Took a while to figure out a method to confirm but here's how I did it:

1) Format data (both by factory reset and format partition options)

2) Boot to ROM. Let it boot loop.

3) Reboot back to recovery

4) Back up to SD card

5) Pull SD card to PC, unzip data and find logs.

Attached is the dumpstate which shows everything having issues accessing data, apparently due to permissions.

Sounds like a possible uid issue. Still investigating.

Also confirmed this happens in GB27 repack so folks we have a rather serious issue here.

Continue to restore from backup or if needed I'll make a tarball of the empty data image from GB27 restore that will do the job via Odin.

More when I figure out a way to handle this issue.
[Samsung Epic 4G Touch] Fugi888:
Just DL'd and installed..... gonna go thru it! hope everything works here!

BTW - AWESOME JOB TO ALL DEVS... :beer:
[Samsung Epic 4G Touch] garwynn:
OK, now that I took my break and got GN2 up to speed on it's new build...

I'm checking the Open Source release again to see if maybe there's something I missed.

Going to copy the platform objects into CM on my build box and try building recovery again.

Let's see if that fixes my problem.
[Samsung Epic 4G Touch] garwynn:
Testing this CWM (same version):

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

Think it may contain the answer to our data wipe issue.

If so I think I know how to fix it.

Edit: No dice. Still digging.
[Samsung Epic 4G Touch] CyberpodS2:
That CWM looks cool none the less, would be cool to see it on the E4GT. Nice find!
[Samsung Epic 4G Touch] GrimeSyndicate:
While you're going back to the drawing board, is there any way to build a safe version of the touch based CWM for the e4gt? Just a thought...

Edit: Ugh.... That's what I get for not following the link (but in my defense, a terminally slow 3g connection in the area makes for very deliberate and sometimes oversight-ridden surfing)
[Samsung Epic 4G Touch] garwynn:
Touch defaults to off for this device though I may look at it again later.
[Samsung Epic 4G Touch] abadasstanker69:
Seriously... Looks cool as hell. +1
[Samsung Epic 4G Touch] garwynn:
Still have the data issue though. If we can fix that we can run many different cwm versions out there.
[Samsung Epic 4G Touch] xpanmanx:
+1.

What's the safest way for me to get back to a working SD card?

Thank you :)
[Samsung Epic 4G Touch] Stryke_the_Orc:
Flash back a stock kernel and only use the repacks to flash until all this is worked out.
[Samsung Epic 4G Touch] xpanmanx:
Go with the GB27 one-click from here ... http://bit.ly/125Yiyh

...then v0.3.0 from here? http://bit.ly/ZgJKef
[Samsung Epic 4G Touch] leaderbuilder:
For GB27 Kernel listed top of Kobridge's post Or the Agat's GB27 Repack Stock with just a repack Then go with 3.1 not 3.0. 3.0 will cause boot loops for many if you've got tweaks that haven't been adjuste/removed for the new kernel source.
[Samsung Epic 4G Touch] Goddly:
adjusted here.. ;) just amke sure your running the newest version if your running my tweaks. (0.3.0 is what ive been running as my dd so far, except for large file transfer lockups, no backups, powers itself on when plugged in.) I think i runs good. but the kinks will get sorted im sure.
[Samsung Epic 4G Touch] blackcanopy:
Does this happen only with wipe data option within recovery? Or does it still happen if flashing Tdunham's JB wipe all 2X script too? How about factory reset within settings menu?

Something I've noticed while using 0.3.0 kernel recovery... As it has been mentioned already, if you reboot into recovery and wait, it'll reboot the system after 4-5 minutes of idle time ...

But, as long as you are being active in recovery (pushing volume up /down etc...) it stays in recovery. Is there a kernel panic or time out feature with these JB KERNELS that can be disarmed?

I know we've been having issues with the JB kernels not backing up the preload partition from day 1, maybe there's a clue in these thoughts that might spark thought in a more brilliant mind than mine to help resolve the issues.

Garwynn, we certainly appreciate All of your efforts and relentless mentality to whip this beast into submission.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] garwynn:
All the reboot issues have been worked around. Didn't try that script... any cwm so far seems to have the data format problem in GB27, even repack.

I could try mounting data to not panic on those but will increase the risk of data corruption if I read correctly.
[Samsung Epic 4G Touch] helix4u:
The reboot issue is exactly the reason that I run 0.3.13h. For people running 0.3.0, its pretty much the same, but without the reboot problem in recovery. Yes, this is achieved by disabling hung tasks from causing kernel panic, but if you're running 0.3.0, you're already running this way on the rom side (recovery and low power mode don't have the workaround in 0.3.0, but stock roms for some reason don't set the hung task timeout). So, IMHO, the safest is the stock kernel, if you want recovery, 0.1.0 or 0.3.1 are good choices... if you want recovery + new governors, 0.3.13h is best.
[Samsung Epic 4G Touch] GrimeSyndicate:
Ok, So I'd really like a safe recovery + new governors, but I tried flashing the gb27 0.3.13h with little luck. Booted to samsung galaxy sII screen and hung there, but i realized (Facepalm) I was on an AOSP based ROM. So, first off, I would like to know the proper method of flashing the 0.3.13h repack (or any of them, I'm sure instructions are the same) and then I'd just like to confirm: the only rom's that can be flashed w/this kernel/recovery combo are those which are TW based, yes? If so, what TW based roms are ya'll running that are awesome & stable enough to be a dd. Then, finally, does an updated recovery and kernel with all the greatest governors and schedulers aboard exist for AOSP based roms? All the AOSP roms seem to have similar kernels included, that have the standard govs with pegasusq and pfq scheduler included, not much in the way of excitement to be had there. And no overclocking/underclocking to be had with the lot of em. I'm terribly sorry if this has been answered elsewhere, or if this is the wrong forum to ask this (these) question(s), but I've searched and lurked a-plenty. Also, I've seen rwilco12's instructions for flashing ICS .zip kernel updates, as well as his instructions for ICS .tar kernel updates, but JB is not ICS, so I'd rather not assume instructions are cross-compatible. Thanks in advance.
[Samsung Epic 4G Touch] Goddly:
Installation are the same, though as you know , if coming to TW a full wipe is warrented, i flashed with mobile odin .tar file tho some roms insructions will vary depending on kernel etc. there are some great Roms out there for TW, and all that ive tested are good enough for dd.
[Samsung Epic 4G Touch] xpanmanx:
Trying to get away from 0.3.14, I one-clicked the GB27 stock kernel, then Mobile Odin'd 0.3.1.

Now I'm seeing 0% deep sleep and 200MHZ is like 83%.

The white "sleep" lines in BMW are small with lots of slowly descending red in between.

I'm using System Tuner Pro, BBS and BMW to look for the problem but nothing's leaping out at me.

I reflashed 0.3.1 from recovery. No joy.

I know I'm opening a whole can of worms, but what could be causing this and how do I kill it before it kills my battery?
[Samsung Epic 4G Touch] kvevand63:
Odd thing happened today when I did a nandroid backup via Agats 0.3.0 (my approx 20th backup/restore using 0.3.0). The file in the attached screenshot appeared in my clockworkmod/nandroid backup folder. Within the file, the following appeared; "CWM based recovery v6.0.3.0, d710". Just thought I would share this, never occurred before, probably nothing to be concerned of.
[Samsung Epic 4G Touch] someguyatx:
A lot of theae discussions are over my head and I have not had time to test anything lately so I just dropped in to say thanks. I also hit that thanks button on the last few pages of posts. Really appreciate what you guys are doing to get this working properly.
[Samsung Epic 4G Touch] jdsingle76:
These guys do amazing work. Thanks for recognizing them. And guys doing said amazing work(I know you're reading, lol) keep the test requests coming, you know we're ready to help when needed!
[Samsung Epic 4G Touch] xpanmanx:
Ok, it's better today. Maybe I didn't let the kernel settle in....?
[Samsung Epic 4G Touch] garwynn:
Slammed at work, not sure if I'll have to make another test.

Hopefully now that Agat sounds like he's back around I'll confer with him and see if we can figure that problem out.
[Samsung Epic 4G Touch] garwynn:
(Copied from Google Talk session)

Just waiting for the build box to be available again to start looking at it.
[Samsung Epic 4G Touch] kc_hubbard:
That's possible...but hard to know for sure since you weren't able to figure out what your wakelock was. Could have been the media server issue that is known to go away after a reboot or who knows what else. Next time, go ahead and take screenshots of BBS showing the partial wakelocks and post them. Lots of pretty bright folks here who would try to help.
[Samsung Epic 4G Touch] xpanmanx:
Thanks! But I'm having an evil issue with BBS where it shows "plugged" all the time. I'm working through that one with Chamonix and the contributors to the BBS topic.
[Samsung Epic 4G Touch] helix4u:
Dunno if this helps with the data wipe problem, but I'm finding this in my logs when I try to wipe data: see attached.

btw, would the difference in filesystems have anything to do with recovery.fstab, where it leaves 16k (length=-16384) alone on the partition? or is that something else?
[Samsung Epic 4G Touch] garwynn:
OK, didn't have time to type this up last night so here's last night's update (a little late).

The size difference is due to the length shortening in the fstab.

But here's the interesting point. I tested both ways and it creates the file structure fine.

Ran e2fsck manually and checks out.

It was also bugging me that the dumpstate seems to get halfway through init before freaking out.

It matches the actual data partition having file structures created.

If it were a bad FS it should be an all or none situation - not work and then panic later.

So I ran a test: Wipe data/factory reset in CWM (Agats and my own), flash stock kernel to boot to rom.

Boots fine!

So while Agat and I may disagree where the problem is I'm ruling it out for now.

So where is the problem?

We know this:

Stock Kernel (unmodified) - Works

Stock Kernel (Source build or Repack) - Doesn't work

The only difference between the first and second is the ramdisk. It's got to be in there somewhere.

So that's where I'm going back to today.

If you guys flashing a custom ROM are flashing a different kernel it could explain why you're getting other results.

Here's the other thing I can tell - the boot loop is

only

happening when you boot the first time after a wipe.

After that it seems to behave just fine for the 5 minutes I ran each test.

You should be able to run this test with posted kernels if you want to try it out for yourself.

I'm trying to think of a way I can echo notes into the logs as checkpoints in the init script.

This may help us get a better idea of

where

in the process it is when it panics - and possibly what's doing it.

More to come but we are making progress. Sorry for the delays with this folks!
[Samsung Epic 4G Touch] garwynn:
We're definitely in the right direction now.

After a few more tests I ran something I should have a long time ago.

1) Unpack stock ramdisk

2) Rebuild with 3.0.71 kernel source - do not replace the modules

Kernel works fine, data wipe fine.

OK, let's try another test but this time replace only the modules built by the kernel.

This works too.

So... it sounds like we're down to whatever Agat replaces for the GB27 repack.

I need to confirm with him but that should cut it down to 3-4 things.
[Samsung Epic 4G Touch] leaderbuilder:
Thanks garwynn and agat! You guys are amazing. You support is greatly appreciated.
[Samsung Epic 4G Touch] helix4u:
If you're interested, attached are my notes on unpacked initramfs when diffed against E4GT_JB_ramdisk.
[Samsung Epic 4G Touch] MoHoGalore:
I hope others, like you, understand the effort Garwynn is putting into this. First hand knowledge - it is what it seems, which is a lot.

Don't mean to gush for a team member but I do hope he gets the acknowledgement that he deserves. And by all means, Agat as well.

/sob moment
[Samsung Epic 4G Touch] jdsingle76:
Amen to that. This thread is one of the ones I follow daily, and am constantly seeing Garywnn posting his latest tests. Not only had he worked diligently on getting us a working kernel+ recovery, but been gracious enough to keep us updated almost real time. I salute your efforts, and am with MoHo and so many others when I say thank you, truly.:thumbup::beer: And yes, of course, Agat, as well!
[Samsung Epic 4G Touch] boXerrumble:
I'm curious. What do you mean when you say "replace modules"? Did that way work on the ICS builds and isn't on the current JB builds?
[Samsung Epic 4G Touch] leaderbuilder:
It's amazing the time and effort garwynn hrad been putting in. I was going to piss and moan over my 16hr days, but I know he's been swamped at work and is STILL working his tail of here!

During this massive migration we're doing, I've made a habit of sneaking out of the server rooms to the bathroom just to check the forums. :) Thanks to all here who give.
[Samsung Epic 4G Touch] cdss:
Appreciate all the work you guys have done for this community on this, because you guys are relentless, I know you will get it working the way we all are hoping it will, thanks :beer::beer::beer:
[Samsung Epic 4G Touch] jigwashere:
I'm awestruck at Garwynn's effort, dedication, and professionalism.
[Samsung Epic 4G Touch] garwynn:
It works the same way except for this new twist on first time boots. Fortunately it seems rather easy to get around so now it's more just trying to get all the temp fixes into permanent solutions as soon as I can.

External sd cards are still acting up but hoping we can figure that out in the next few days. If we can get the major issues resolved or have a relatively easy workaround in place I'll probably bump them all to 0.4.0 as it is a big step closer.

In case people are wondering about my versioning... 1.x.x should be nothing short of a a rock solid kernel and recovery. We're not there yet but doing this debugging and testing has taught me a lot.
[Samsung Epic 4G Touch] JCred:
Me: hits "thanks"

Xda via tapatalk: "Post thanks action denied"

Me: types "Thanks for all the ongoing effort" :thumbup:
[Samsung Epic 4G Touch] helix4u:
Me too.. Learning new stuff everyday. Like today, I learned how to do repacks from a windows environment. I fiddled around and ended up with one of your builds (0.3.13h) with no more reboot while charging issues and also changed the recovery background to black instead of grey. Fun stuff.
[Samsung Epic 4G Touch] robrooter:
I did a data and cache wipe on app and it fixed that issue.

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] garwynn:
Well... yet another thing learned. This one seems to be the only documentation on this that I could find.

Those on the S3 may want to pass this on.

In the ramdisk was a binary called ffu and I had no idea what it did.

So I opened it up in a hex editor and in the jumble saw this:

Well, FFU in theory sounds right for Firmware FixUp.

And it's mentioning the 2 commands that were causing sudden death issues in the GS3 eMMCs.

So that's clearly not what's causing my problems but learned it's instead part of the fix for GS3s.

It patches at boot time so it's likely a temporary patch to the eMMC firmware, much like we saw for another one.

But the one we saw in eMMC bug research was open source - this one they seem to want to keep closed for some reason.

Also did figure out how to get ADB running even if it's in the boot loop.

I'll apply that change as well.

Still plugging away...
[Samsung Epic 4G Touch] robrooter:
Garwynn...you my friend are a machine. Do you ever need a recharge? ;)

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] garwynn:
I'll recharge when I get this fixed.... assuming there's a break in the next 10 or so days between now and when the S4 comes out. As soon as I get the stuff for that I'm going to be back to double duty for a while.... but of my own choosing.

I feel bad for MoHo - since I'm not burning my upgrade for an S4 he's volunteered for testing things until I get the cash together to get one out of pocket.
[Samsung Epic 4G Touch] robrooter:
At least it is by your own choice. I am truly great full for all the time and work you put in.

BTW... am free tonight if you need a tester. Am looking for a rom that don't mess with the kernel. I see that Jellyverse flashes stock at end. So my tests have been for nothing. Sorry I did not notice this earlier bro. PM me if you need me. :thumbup::thumbup::thumbup::beer::beer::beer:

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] crawrj:
This will work for you. http://xdaforums.com/showthread.php?p=40017509

I also want to say thanks to Garwynn and everyone else working on this. Your dedication and persistence is commendable. You are truly going above and beyond on this. And it is greatly appreciated.
[Samsung Epic 4G Touch] Danielhammons1:
I have the virgin mobile epic 4g touch and it's jellybean and I've been looking for a reliable recovery for it and this seems right but if you don't mind could you explain to me exactly how you got this to work? I have mobile Odin and I've read a lot and talked to several people. Is this a recovery for jellybean sph d710 Gb28? Sorry if I sound stupid but this phone and recovery and kernels are so much different than what I've been used to so it's like starting all over.
[Samsung Epic 4G Touch] MoHoGalore:
At this time, Garwynn is working to hammer out issues with GB27 (Sprint).

Once he gets those issues resolved, he'll apply to GB28(VM) and GC01(Boost).

If you haven't already, read this thread in its entirety but the nature of your question suggests that you have missed several key topics.
[Samsung Epic 4G Touch] Danielhammons1:
I've read this thread and several others closely to try to figure it out, what is agats recovery? That's why I stopped and read here because this one says jb and any kind of working recovery would be fine, I understand how to do it with the el26+cwm and my stock kernel but this made me wonder if there's already a way just not with the cwm, like agats?