yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] btoddweber:
If I'm on gb27 rooted...do I still need to update through Samsung? Just flashed aio in jellyverse and got sprint zone update notice. Is that just Sprint telling me or does it not recognize that I already have gb27?

in a comadosed jellyverse rocking Agats GB27 rec kernel
[Samsung Epic 4G Touch] garwynn:
That's probably an update to the Zone app itself. No need to reflash if already on GB27.
[Samsung Epic 4G Touch] stangdriver44:
First off have to say thanks for all the hard work and keeping us moving forward. Looking forward to see how far we can go. Coupe of questions, is there ever going to be kernel support for Swipe to Wake and also wondering about OTG host?
[Samsung Epic 4G Touch] primo523:
You can do it with regular Odin too. But mobile Odin is cake. Where are you in the process? Qb is a good teacher. Watch the video

https://www.youtube.com/watch?v=9W-1FPfgclM&feature=youtube_gdata_player
[Samsung Epic 4G Touch] garwynn:
With no major issues reported yet I will start patching Linux versions and enable the stock governors. I'll try to have new builds out today if possible.
[Samsung Epic 4G Touch] robrooter:
Thanks garwynn. Your contributions will be missed.

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] cerj:
Awesome
[Samsung Epic 4G Touch] cerj:
Created and restored a nandroid, without flashing the rom first. Prior to this kernel/recovery, we had to flash the rom then nandroid to get the preload. Not now, all of the things I have tried are working fine. Thank you garwynn
[Samsung Epic 4G Touch] dataman:
Oh power menu mod... I use that as part of TD AIO.
[Samsung Epic 4G Touch] garwynn:
0.4.0 updated with new md5s for all 3. Hopefully it will put that last issue back to bed.
[Samsung Epic 4G Touch] prguzman1978:
Haven't been up to date with this thread but is 0.4.0 the closest to being a stable version?

Three things cannot be long hidden: the sun, the moon, and the truth...
[Samsung Epic 4G Touch] crawrj:
I spent about 6 hours on it trying everything under the sun and the only thing I couldn't get to work is accessing sdcard by computer from recovery.
[Samsung Epic 4G Touch] blackcanopy:
Did you by chance try USB switcher?

https://play.google.com/store/apps/details?id=in.zatta.USB_switch

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] crawrj:
That wouldn't impact recovery would it? It works fine from within the system just not in recovery.
[Samsung Epic 4G Touch] blackcanopy:
I was assuming you had your phone booted up while trying to access the SD card via PC. My bad, I misread your post

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] garwynn:
USB Mass Storage for recovery:

Right now the driver attempts to mount it as mtp/adb access in recovery.

So I'm guessing that's why it's not cooperating with the recovery USB access.

I'll change the product id to test and see if it will properly recognize using the various combinations.

If it pans out I'll push out a new version soon.

BTW, did anyone get it to even recognize in Device Manager in recovery?

(One way or the other..)
[Samsung Epic 4G Touch] crawrj:
No problem at all. Thanks for trying to help me anyway.
[Samsung Epic 4G Touch] agat63:
Did few small mods to recovery along with all other findings we got.

Running tRec_v0.3.4 now and it seems to work.

Tried everything and no problems yet.

Didn't check if I have acces to external_sd wile in recovery. Will try it tonight when I get home.

That would be the last thing for me to test.

It looks like Garwynn did find the cure for the the problem.

Kudos and thanks.
[Samsung Epic 4G Touch] jdsingle76:
Agat! ! You and Garywnn rock. You have 0.3.4 up anywhere? I'd be happy to test the external sd if you want. Thanks again guys for all you've done
[Samsung Epic 4G Touch] blackcanopy:
In recovery, external SD on mine is showing a list of about 35 folders/files and doesn't allow scrolling down beyond the last still. But I am able to access the external SD.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] agat63:
No I didn't upload it.

Recovery is part of kernel so I just made a new recovery binary and included in test kernel

I'm running on my wifes phone. Once proved good I'll share that binary with Garwynn so he

can include it in his next kernel if he wants.

I semiretired from E4GT remember? :p
[Samsung Epic 4G Touch] crawrj:
From a computer? External XD works fine in recovery for me. I just can't mount it to a computer from recovery.
[Samsung Epic 4G Touch] crawrj:
Here is what mine shows.
[Samsung Epic 4G Touch] blackcanopy:
No, I have not tried from a computer. You are able to access all files on your external SD? It must be something on my end that I can only see the first 35 or so in recovery.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] crawrj:
Well I just counted and only had 32 in my folder. Going to copy a few more and test again.

Edit: OK I had a total of 44 and could scroll through all of them.
[Samsung Epic 4G Touch] garwynn:
OK, quick test was good. I have to remove MTP because it will not work alongside mass storage.

But I'll push out v0.4.1 shortly.
[Samsung Epic 4G Touch] Goddly:
Kobridge 41 tweaks need to be removed from initd, for the 4.3a it works with the 3.1 kern/recovery because its stock,(upgraded linux) any new govs it doesnt play well with, its that single script,in the init.d.
[Samsung Epic 4G Touch] leaderbuilder:
I am able to see phone.

Could be because I used the USB Switcher app to change storage modes a while ago (also I think TD's AIO mod that has that in there too).

Note that I did remove KO's tweaks (deleted the init.d folder) a while ago too.

https://www.dropbox.com/s/2vv7xhgf4n1tc2d/001SysInfo.jpg

https://www.dropbox.com/s/ycspdjz3sjdd1sr/1.png

https://www.dropbox.com/s/gfruw6ikordpc28/2.png
[Samsung Epic 4G Touch] garwynn:
Goddly,

Thanks - I've decided to leave hotplug out though for the time being. It's my hope we can somehow adapt the dynamic one built in 3.0.71 to work for this device instead of using a secondhand one.

Update:

0.4.1 out for all 3, enjoy!
[Samsung Epic 4G Touch] Goddly:
Understood, just pointing the fact out the gentleman a page back.. ;) ive been holding off updating, (Rom and tweak pack) for a substantial gain in recovery/kernel area, Do you feel (personally) that your updated 4.0 is that gain? Or should i continue to wait until 4.1 when all mounting issues have been addressed.. (computer) i dont wanna release with 4.0 when an updated 4.1 is pending in a few hours.. lol. Great work again brother ;)
[Samsung Epic 4G Touch] garwynn:
See my update above your post. ;)
[Samsung Epic 4G Touch] crawrj:
Works perfectly now!
[Samsung Epic 4G Touch] jdsingle76:
Great work man. I think I speak for everyone when I say we never doubted you two for a minute. Dove tailing off Goddly's post, will you give us the thumbs up when you think these are ready to bake into our builds? I know folks are gonna want these coming outta the gate! Thanks again man, seriously, awesome job.
[Samsung Epic 4G Touch] garwynn:
Big things left to address:

1) Getting Agat's CWM back in and making my CWM test changes on that. Shouldn't be too hard.

Other than that I'm not planning any major enhancements to the kernels as the tweaks seem to handle what you guys want fairly well. That would mean I revision it to v1.0.0 and Agat and I would probably be done with this in general. And at that point I'd say it's okay but still think linking to the kernel is better.

Now, here's something that we should consider talking about. If someone wants to continue working on these kernels after that - and has a Linux box set up for this - you have the repos. Fork it, start making your own changes and continue it from where we leave it off. Getting the kernel good is one half - someone has to (hopefully) keep looking at it and improving it where possible.

Happy to advise anyone who would like to take the reins after we get it going.
[Samsung Epic 4G Touch] dataman:
1) Any reason to change the CWM to Agat's? Any benefit one over the other?

2) Is it feasible to enable the touch screen in CWM? any downside to that?

3) Would you please include the MD5 in the actual file for the final release?

4) Finally is it possible to have the JB x2 built in to CWM?

Thank you for the awesome job!
[Samsung Epic 4G Touch] CyberpodS2:
Purely my personal opinions here... LOL

1) The menu is much friendlier to flashaholics.

4) This would be sweet.
[Samsung Epic 4G Touch] jdsingle76:
I volunteer MoHo! Lmao! ! ! Thanks for keeping us updated. Awesomeness abounds my friend! :beer::beer::beer::beer: all around!
[Samsung Epic 4G Touch] helix4u:
Might be fun to set up a dev environment on a VM just to tinker and learn so that contributing is easier... fulfill some curiosity I have. But taking the reins is for someone with a lot more knowledge and experience.

Jeebus! I leave the forums alone for half a day and miss out on all of the exciting new kernel testing... :laugh: Guess I'll have to start in on testing this tonight after I take the ladies out shopping. (insert sarcastic "YAY!" here) lol.
[Samsung Epic 4G Touch] btoddweber:
Will this cwm be ok for flashing modems or is el26 or one click the way to go?
[Samsung Epic 4G Touch] jdsingle76:
I've used this cwm for flashing everything. Only issues I've had were with usb and sd
[Samsung Epic 4G Touch] MoHoGalore:
While I appreciate that nomination, in 9 days we'll be diving into the S4. :D

I can setup another build box for use by an up and comer though. ;) (Hint, HINT, JD..)
[Samsung Epic 4G Touch] jdsingle76:
Haha....if Garywnn is willing to teach, you have the build box, and everyone has the patience, then I'm in lol
[Samsung Epic 4G Touch] ewilley2008:
Anyone have problems with governor and I/O scheduler changes not sticking after reboots ? Using 4.1 and Rom Toolbox
[Samsung Epic 4G Touch] leaderbuilder:
Not me. Do you have it 'set on boot'. Also give it a minute after reboot for all apps and settings to start and stick.
[Samsung Epic 4G Touch] robrooter:
It happens to me once after every data/cache wipe when I flash another kernel version. Once flashed go back in and re set "on boot" and it should work fine till another kernel flash.

I use trickster mod. I see it writes a script when I open. I bet the script re sets it when it finds a different kernel.

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] ewilley2008:
Yep have it set on boot, always boots to cfg/ondemand, going to try another app and see if it sticks
[Samsung Epic 4G Touch] helix4u:
First, make sure you check apply on boot in rom toolbox. If you've already checked the apply on boot box in rom toolbox, you might have conflicting scripts from some other tweak that sets them as well.
[Samsung Epic 4G Touch] leaderbuilder:
^that^

I know in the past I had a few different things all set differently, RomToolBox, PimpMyRom, Trickster etc. Once I got them all in sync all was good. Then on to using just one 'tweak' app.
[Samsung Epic 4G Touch] ewilley2008:
It was on my end, should have done more testing before posting, it was happening after kernel flash.
[Samsung Epic 4G Touch] jdsingle76:
I can assure you, there's never been more testing done on a series of kernels than these. Garywnn and Agat63 have worked relentlessly since source dropped to get us a working kernel+cwm. And Agat doesn't even have this phone! Please understand the entire situation and the painstaking work that's been done before posting rude comments about things you do not understand. Btw great work on the kernel Garywnn and Agat63, as always.
[Samsung Epic 4G Touch] Goddly:
Wanna say, To ALL Boston Mass Residents, WaterTown, and surrounding communities.... Hats off to you and yours id buy you all a beer if i could CHEERS!

​
[Samsung Epic 4G Touch] graffix31:
Here here. I was actually a block and a half away sitting outside eating lunch when the whole thing went down. It was an insane scene. I live south of Boston so I wasn't In lock down thank God. Amazing to watch the whole thing unfold so quickly. Everyone in law enforcement and all of the residents deserve a lot of credit. :thumbup:
[Samsung Epic 4G Touch] ewilley2008:
I shouldn't even respond but there was no rude comment, my comment was directed at myself for me not testing more
[Samsung Epic 4G Touch] jdsingle76:
Very well, thanks for clearing that up. :thumbup::)
[Samsung Epic 4G Touch] prguzman1978:
I was so curious that I drove to Umass Dartmouth and there was 2 black military helicopters...

Three things cannot be long hidden: the sun, the moon, and the truth...
[Samsung Epic 4G Touch] robrooter:
Been running 4.1 since release. Nice work garwynn. You hard work and dedication is really appreciated. The kernel is running as smooth as can be! Thank you very much garwynn!

E4GT Rom-a-holic!!!
[Samsung Epic 4G Touch] CyberpodS2:
+1 I could not have said it better!

I did just discover something that got me thinking about an added feature though. It might not be an issue if and when you go back to Agat's recovery, but I just realized this and recent AOSP kernels now look the same. :) Would it be a problem for anyone involved to add the word SAFE to the recovery title? EX. instead of CWM-based Recovery v6.0.3.0 it could be CWM-based SAFE Recovery 6.0.3.0. I just worry there will come a time when I forget what recovery I am on and have a date with a blue light... LOL
[Samsung Epic 4G Touch] leaderbuilder:
I like that idea too! Pretty interesting idea.

Between TWRP and the latest working TW (SXTP_Agat_GB27-v0.4.0) ones, it gets tough sometimes to remember where you are on which one; especially when just flashing the kernel to switch them to restore a nandroid made with another.

But I do see the issue with some inexperienced or ignorant (meant in the non-dorogatory sense; Lacking knowledge or awareness in general) people not really knowing what they're doing and then bricking anyways. :P

Maybe a qualifyer - SAFE (ER) or (?).

Eitherway garwynn especially, and the other devs and contributors have been freaking great!

Loving this kernel and recovery. Brought back a new sense of excitement to me to flash between ROMs much quicker and safely.
[Samsung Epic 4G Touch] crawrj:
Or just say TW-CWM-... and AOSP-CWM-... For figuring out which zip to flash just rename the zip to whatever fits you best. Garwynn-TW-JB-041.zip for example.
[Samsung Epic 4G Touch] CyberpodS2:
My point was while your in the recovery. I just had one of those moments where I froze as I was about to install the kuban beta. had just restored 3 different nandroids (PIB, WORv3 & BB8) back to back using 0.4.1 to verify it worked properly. I rebooted and it occurred to me I could not tell if I was in 0.4.1 or still in the recovery from PIB. I just flashed 0.4.1 to make sure, but it got me thinking.
[Samsung Epic 4G Touch] crawrj:
No I get your point and agree with you. That is where the TW and AOSP suggestion came in. The zip part was just addressing a different aspect. When you are in recovery wanting to install a kernel and you have 10 kernel zips to choose from.
[Samsung Epic 4G Touch] CyberpodS2:
Ya we're on the same page. It's scary looking in my download dir sometimes. LOL
[Samsung Epic 4G Touch] atlharp:
+1 . This kernel has been smooth without problems. Thanks again for your work! :thumbup:
[Samsung Epic 4G Touch] helix4u:
It's pretty easy just to unpack the initramfs and modify the clockworkmod logo and then repack. Could just change the color or something so that you know that something is different... I'd do it and upload, but I dunno how the whole getting permission to do that sort of thing from the developer works...

Edit: I actually already have this done. Zips and tar.md5s, MD5 checksums for all. Just changed the clockwork logo to black and white in one version, changed clockwork logo and android install logos to black and white in the other version. Would just need permission to link to them from garwynn(?)... i think...?
[Samsung Epic 4G Touch] garwynn:
Because JB has the eMMC bug fixed in the kernel, any version of recovery used while using a GB27 kernel should avoid it. It's double protected as the new recovery versions avoid that step unless enabled - which old kernels did manually.

So not sure it's really needed.

I broke my own rule - 0.5.0 out for all 3. Agat's recovery back in with preload added.

BTW, Agat's working on his own kernel with some nice features. BOLO for it coming soon.
[Samsung Epic 4G Touch] helix4u:
I thought I saw something new brewing in his repos... :)

BTW, everything is looking good so far with 0.5.0.
[Samsung Epic 4G Touch] btoddweber:
Modems ok in agats to flash?
[Samsung Epic 4G Touch] jdsingle76:
Yes bt, no issues here
[Samsung Epic 4G Touch] btvolta:
Just when I thought .0.4.1 was going to be the final one. You're awesome for putting in all this hard work seeking perfection, and you are greatly appreciated!
[Samsung Epic 4G Touch] svicenty:
I'm really confused is the agat, cwm

Recovery the same because the 0.4.1 running cwm is running great or is the agat better. When I do a back up on agat it is save in a cwm folder????
[Samsung Epic 4G Touch] zilla1000:
Thanks for the great work, and the effort !

I just downloaded the 0.5.0 zip (3 times) and the checksum show differently then listed

5979f8fb4c3200c13130885e2c2461a9 SXTP_Agat_GB27-v0.5.0.zip (the checksum I got)

The .tar checksum is good; I used .tar and odin instead. If you got a chance, please check. Thanks.
[Samsung Epic 4G Touch] boXerrumble:
I can confirm the md5 mismatch on the zip file as well. Tried 3 times got the same md5 signature as is posted above this post.

EDIT: Tar md5 is okay. Flashed that. Kernel is running smoothly thus far.
[Samsung Epic 4G Touch] ACoolGuy:
The MD5 listed for the .zip appears to be the MD5 for .4.1. Possible that he simply forgot to update that MD5.
[Samsung Epic 4G Touch] b0ricua:
Is there an issue with this kernel and kobridge's GB27 ROM and/or his tweak pack?

I just mobile Odin'd this latest version and nandroid'd. When I rebooted my device kept locking up and rebooting on its own. Did that several times so I flashed GB27 stock kernel and all is fine now.

I'm running deodex Kobridge GB27 rom with "moderate" tweak and tdunham's mod.

EDIT: after searching it seems that older versions didn't play well with the tweaks. I'll remove and see if that helps.
[Samsung Epic 4G Touch] dataman:
explained many times..

the new kernels do not play well with Ko's tweaks.. because of one line in ko's tweak... you can manually fix it or just get rid of it till and if he updates it.

remove the tweak and use goddly's tweaks

http://xdaforums.com/showthread.php?p=40475680#post40475680
[Samsung Epic 4G Touch] blackcanopy:
If hotplug was left in the kernel, Kobridge tweaks would certainly cause those issues... But I believe hotplug was kept out of 0.4.1 and 0.5.0 (as well a several others)

Edit: open system/etc/init.d folder and remove Kobridge41 tweaks and reboot.

I was ninja'd during edit.. Lol

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] mjs2011:
So just to confirm, this recovery is actually safe to go back and forth between TW and AOSP? If so, holy crap that's awesome!
[Samsung Epic 4G Touch] CyberpodS2:
Yah I been back and forth between WOR and PIB a few times updating my backups. Gotta love it!
[Samsung Epic 4G Touch] leaderbuilder:
It's so nice having fully working backups for switching again! The devs here deserve so much credit ahs thanks.
[Samsung Epic 4G Touch] xpanmanx:
Dude you rock. 100% grateful.

Little typo during the installation. It says CWM where I thought it would say Agat's.

Thanks again man!
[Samsung Epic 4G Touch] dataman:
interesting development I just came across by AGAT...

He released his own version of Recover kernel for JB v1.0

http://xdaforums.com/showthread.php?p=40555138#post40555138

Edit:

love both Devs Garwynn and AGAT... and I know they are both awesome and work together on this, I was just wondering the difference of one over the other.
[Samsung Epic 4G Touch] MoHoGalore:
I think post #19 in agats thread answers any questions in full. This is not dev against dev. Not saying you're insinuating anything of the sort but let's let each thread stand on its own merits.

We know both have been working together for the common cause. Let it be what it is.
[Samsung Epic 4G Touch] btvolta:
For whatever reason I haven't been able to flash the tar file for the 0.4.1 or the 0.5.0 kernels with mobile Odin. I had to use the zip each time to get it to work. Any ideas why?
[Samsung Epic 4G Touch] dataman:
so you can flash any ROM with this but can you use it as daily Kernel Recovery on AOSP ROMs or you have to flash that ROM's kernel before booting it?

I am on Ko's Gb27 TW ROM and just installed this kernel/recovery and use it as my daily.. would that be the same on AOSP based ROMs?

Thanks
[Samsung Epic 4G Touch] btoddweber:
From what I understand theirs have the kernel baked in...but the CWM is the same so you can nandroid back and forth.
[Samsung Epic 4G Touch] svicenty:
Really you could be on tw ROM and flash over to a aosp ROM on 4.1 or 5.0

---------- Post added at 02:36 AM ---------- Previous post was at 02:21 AM ----------

How is 5.0 working
[Samsung Epic 4G Touch] dataman:
does AOSP ROMs have built in Recoveries too?
[Samsung Epic 4G Touch] jt_hatch:
On this phone (AOSP OR TW) recovery is baked into the kernel.

This recovery has been reported to work fine for flashing back and forth between AOSP and TW (or for making/restoring nandroids for either). This kernel will NOT work for an AOSP ROM. It will only work for TW ROMS.

i.e. if you flash an AOSP ROM with this recovery/kernel, OR restore a nandroid backup of an AOSP ROM with this recovery/kernel, you should NOT reflash this kernel/recovery and expect to be able to boot into the ROM. (Flashing an AOSP ROM or restoring a nandroid of an AOSP ROM will have overwritten this kernel/recovery with whatever is in the ROM or nandroid.)

Side note(s): 0.5.0 has worked great for me making and restoring nandroids (running Jellyverse). Testing agat's new 1.0 kernel. For anyone not following agat's thread, it seems he missed a few things that garwynn fixed in the recovery for 0.4.0/0.5.0, so it reboots while making a nandroid, but OC/UV works. He's going to get with garwynn/look at github to get it straightened out but at the moment he's out on the town in vegas with his wife, so... let's not pressure him. :D
[Samsung Epic 4G Touch] dataman:
Thanks I got it. AOSP ROMs have their own Kernel and recovery, but you can flash the ROM using this recovery, or restore your nandroid.
[Samsung Epic 4G Touch] svicenty:
Thanks for the info
[Samsung Epic 4G Touch] optimummind:
I wonder if anyone else has experienced this but when I was running on the v0.4.1 version kernel, YouTube videos stopped playing for me. I got a system message saying that the connection to the server was lost. I tried YouTube again right after flashing back to GB27 stock kernel and videos worked.
[Samsung Epic 4G Touch] garwynn:
Logcat during that time may be able to shed some light on that. Can you make one for me?
[Samsung Epic 4G Touch] helix4u:
No issues with youtube here.
[Samsung Epic 4G Touch] leaderbuilder:
YouTube works great for me too
[Samsung Epic 4G Touch] optimummind:
Sure, I'll flash back to v0.4.1 and get a logcat.
[Samsung Epic 4G Touch] Raistlin1:
IDK if it was 4.1 or ComaDose tweaks, I let my battery drain and then charge over night and when I turned on phone this morning (it was still plugged in) gsam showed the battery was only 97% charged. I ran 4.1 kernel for several hours and then flashed the tweak on the same day.

Running stock rooted GB27.
[Samsung Epic 4G Touch] srkmagnus:
Thanks for all the hard work and contribution to this device, [MENTION=4194834]garwynn[/MENTION] . Many people don't realize that doing what you and others do to bring the community development and continued support well after the OEM can be a second full time job in addition to what is going on in life.