yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] sfhub:
I didn't post that because FD02+CWM-Rogue was necessarily safe or not, but just because it was the last repack that Steady officially put out.

There are 2 programs of concern:

1) Recovery - handles your wipe data/factory reset and nandroid restores (and backups which are always safe)

2) update-binary - included in the ROM's update.zip (outside of the control of the developer or Recovery)

You need all the pieces you regularly use to be in safe configurations to really be safe. If Samsung fixed the core EMMC firmware lockup/superbrick bug, then all situations are addressed. If you patch the kernel then all situations where you use that patched kernel are addressed, but there can be situations where you unwittingly install a different kernel as part of a ROM install or you just prefer to stick with stock repacked kernels. You can make sure you have a "safe" Recovery, in which case your wipe data/factory reset and nandroid restores are safe, but you should also make sure the ROM you are flashing does NOT perform a format() in the install script. If it does, make sure the update-binary included is a GB-based variety. If you can guarantee neither, flash that ROM on a GB-based kernel/recovery.

Even if your Recovery is "safe" you can still superbrick if you install a ROM which has bundled an "unsafe" update-binary in the ROM's update.zip AND the install script performs a format() call.

This can lead to confusing examples of safe/unsafe combinations and bricking/non-bricking situations. One really need to understand the nature of the problem or it quickly degenerates into voodoo science with sacrificing of chickens so the brick gods don't visit you.

---------- Post added at 12:46 PM ---------- Previous post was at 12:35 PM ----------

I have not stated whether that Rogue CWM was considered safe or not for

Wipe Data/Factory Reset

Nandroid Restores

Because I have not yet been able to contact Steady regarding how it was built. I believe it was built against GB-based CM7 sources so it should be safe for those two operations, but until I know for sure, I won't say anything about it.

Now keep in mind, as the previous post described, even if your Recovery is "safe", you can still superbrick if you install a ROM with an ICS-based update-binary and the updater-script performs a format(). This is outside of the control of the person who built/packaged the recovery as those two files are provided by the ROM developer/packager.

The only ROMs I've encountered with both those qualities are CM9 and AOKP. I've spoken to both darchstar and T.C.P and they have said they will be making changes to get rid of format() and replace with delete_recursive(). This should theoretically make those ROM installs safe to install in ICS-based kernel/recovery even if they still use the "unsafe" ICS-based update-binary.
[Samsung Epic 4G Touch] TrayLunch:
Excellent clarification. Thanks for the reply, but man, go enjoy your vacation. Don't worry about us until your done dodging bullets from other international super spies.
[Samsung Epic 4G Touch] HaiKaiDo:
Also sbrissens 3.0 kernel has been safe for months (it would seem). Ive wiped atleast 50-60 times while testing some cm9 and aokp stuff and have had no brick.
[Samsung Epic 4G Touch] TrayLunch:
Have you had confirmation from the dev of this? I ask because the eMMC bug is tricky in that it "...MAY NOT be triggered every time, so you can do the same operation with no issues then on your Nth attempt it bricks." (to quote sfhub)
[Samsung Epic 4G Touch] T.C.P:
The kernel we are talking about is a 3.xx kernel built from source. Emmc bug isnt present.
[Samsung Epic 4G Touch] wraith404:
So we should NOT sacrifice chickens?? :D Moloch is angered.

Anyway thanks for making clear that flashing zips could still format, I knew and completely forgot to mention that, leaving my information quite dangerous. I only run appending scripts these days.
[Samsung Epic 4G Touch] TrayLunch:
EMMC bug is always present as it is a firmware issue. GBs recovery just has double safeguards against triggering it. If sbrissens 3.0 kernel is based on a GB 3.xx source, then it goes without saying that it is fine because it is GB based. I was unaware that it was based on GB, so that was my ignorance. My apologies.
[Samsung Epic 4G Touch] TrayLunch:
Now, to lazily educate myself further, why is it recommended to go back to EL26+CWM rather than EL29+CWM?

Again, sorry if I am burying you guys with n00b-esque questions, but I want to be able to educate myself so that I am better equipped to help others.
[Samsung Epic 4G Touch] Ascertion:
Because the EL29 rogue isn't official CWM, and will fail on installation of any AOSP rom.
[Samsung Epic 4G Touch] locoboi187:
It's not lol. EL29 CWM was just recently released lol
[Samsung Epic 4G Touch] TrayLunch:
EL29 CWM has been out in the Auto Root Package for a long while my friend.
[Samsung Epic 4G Touch] MoHoGalore:
Can you give an example?
[Samsung Epic 4G Touch] :
Jesus Christ! when is the official will be release. I am soo funky! tire of these leaks. Someone need to put RTV in the crack.
[Samsung Epic 4G Touch] blackroseMD1:
The multitude of Status 7 errors that people get when trying to flash CM9/AOKP etc.
[Samsung Epic 4G Touch] kali323:
GB is based on 2.6 kernel, no such thing as gb 3.xx source. Sbrissen 3.0 kernel is based on the international gs2 ics source.

Chris41g never release a stock EL29 cwm kernel, thats why we use the EL26. The only EL29 has rogue recovery not stock cwm
[Samsung Epic 4G Touch] nhfi:
in order to get OTA ICS

I have been running FE22 with no issues at all..Thanks to the dev's who have been providing all the leaks. If I want to get the OTA when it comes, do I have to go back to EK02 unrooted? or can I have a rooted version?
[Samsung Epic 4G Touch] MoHoGalore:
I get that and am in no way trying to seem hateful.

I've seen issues with status 7 but o guess what I'm asking is an example of which rom triggers the status 7?

Not saying I'm experienced by any stretch of the imagination but...

Every time I see an el26 to start, I've always used el29 and guess I've been lucky.
[Samsung Epic 4G Touch] Wacky2bakky:
May I ask where you got the FE26 leak? Were all on FE22
[Samsung Epic 4G Touch] Mattix724:
I haven't seen any difference in using EL29 cwm vs EL26 cwm...

I used EL29 cwm recovery only tar to flash early ICS leaks... as of recently I've been using EL26 cwm to flash.
[Samsung Epic 4G Touch] MoHoGalore:
Guess we're getting off topic and discussing another thread issue that sfhub has many times addressed. Sorry about that.
[Samsung Epic 4G Touch] nhfi:
Sorry typo
[Samsung Epic 4G Touch] gmangut:
Preorders start tomorrow btw... On the .s3
[Samsung Epic 4G Touch] wasscomedy:
Do you know how to pre order anf where?
[Samsung Epic 4G Touch] DevalB:
www.sprint.com/galaxys3
[Samsung Epic 4G Touch] gmangut:
Actually

Pre-order begins June 5 atwww.sprint.com/galaxysiii.
[Samsung Epic 4G Touch] funeralplanner:
Where do we get ff02?
[Samsung Epic 4G Touch] kc_exactly:
FF02 hasn't been provided to the masses.

And, there is a thread specifically for the S3.
[Samsung Epic 4G Touch] TrayLunch:
EL29 with root should take the OTA just fine (you'll lose root) as long as you haven't uninstalled preinstalled apps without backing them up first. If you don't leave a backup as a marker, the .zip won't install.
[Samsung Epic 4G Touch] TrayLunch:
My apologies again. I was getting my build numbers confused. I take it the international ICS build doesn't have this problem? How so?

Thank you for the explanation. I'll keep that in mind when I go to flash something other than a stock release. To date, I've only used CWM to create backups before I flash from EL29 and install mods from .zips. I stick to the Odin OCs for my ICS releases.
[Samsung Epic 4G Touch] nhfi:
your talking about all the sprint stuff like nascar etc...?
[Samsung Epic 4G Touch] TrayLunch:
No, I'm talking about Google and Samsung apps like AP Mobile and Gapps. Anything that won't give you the option to uninstall in app management that you remove with a third party app with root permissions, like root uninstaller. If you download the Auto Root Package, it actually has a tool that you can use to check if your phone will take an OTA. I forget exactly how to get to it, but its relatively easy to find.
[Samsung Epic 4G Touch] EggosEvo:
If you weren't joking, go to settings, then to About Phone at the bottom, then system updates. Check away my friend! I do it daily.
[Samsung Epic 4G Touch] TrayLunch:
That doesn't "manually check" for an update. That only activates if an update notice has already been pushed to your phone. You'll notice that it doesn't do any sort of search before it comes up with the screen telling you that you have the most up to date OS.
[Samsung Epic 4G Touch] Omar04:
I think EL29+CWM direct boot is for CM9 and on the site CM says don't use it for any other ROM than CM9.
[Samsung Epic 4G Touch] sfhub:
I haven't been following sbrissen's kernel so apologize if this is already known, but the "bug" isn't in the kernel per-se. It is in the EMMC firmware (ie the hard drive controller for the MMC memory, something we don't normally have access to)

The 3.xx kernel MMC driver will normally allow mmc erases as it is a standard feature. Going through mmc_erase() is the code path that triggers the EMMC lockup/superbrick bug, so by default the 3.xx kernel *IS* susceptible to the bug.

One needs to explicitly disable some support for mmc_erase() in the kernel mmc driver to have a "safe" kernel that works around the EMMC firmware lockup/superbrick bug. Is that what you are saying was done? I wasn't clear what "EMMC bug isn't present [in 3.xx]" meant in that context.

Look in drivers/mmc/host/mshci.c for MMC_CAP_ERASE It needs to be removed/disabled for the kernel MMC driver to workaround the EMMC firmware lockup/superbrick bug.
[Samsung Epic 4G Touch] EggosEvo:
What about the "Update Firmware" button? I thought that one manually checked for the update.
[Samsung Epic 4G Touch] blackroseMD1:
I believe that his kernel is being built from the Intl' update-4 code, which is supposed to be safe. I may be incorrect, but I don't believe I am.
[Samsung Epic 4G Touch] sfhub:
It does, but if your MEID isn't in the list that is supposed to receive the update, it will just say no update available. It doesn't allow you to preempt the normal ordering of how they release the OTA.
[Samsung Epic 4G Touch] TrayLunch:
W3rd! Now go back to your vacation! This is the last time I'm telling you, Mr!
[Samsung Epic 4G Touch] Whosdaman:
No that is for modems only.

In ics they built in a manual checker. Go to system updates then update system software
[Samsung Epic 4G Touch] EggosEvo:
Alright. Thanks for clarifying.
[Samsung Epic 4G Touch] sfhub:
I looked in the source tree sbrissen checked in and verified MMC_CAP_ERASE is NOT enabled in mshci.c so that means it should be safe.
[Samsung Epic 4G Touch] TrayLunch:
STOP WORKING, YOU!
[Samsung Epic 4G Touch] veritasaequita:
i do recall there being a dialer code to check for updates. ill have to digg around and see if i can find it again. haven't seen it since i was on my G2.
[Samsung Epic 4G Touch] winfan:
Here's a theory tell me your thoughts.

FF02 was released on Friday, lets say they begin testing this build for 1 week in the mean time source is released on June 7 as Samsung indicated before. S3 sales begin today giving them a week to gain pre-orders which might sell out. Ota could release next week along with Tmobile's date. Sprint benefits gaining pre-order sales, Samsung gets to release source code and sprints testing policy follows the 1 week roll out. Possible ota on June 11. Thoughts?
[Samsung Epic 4G Touch] TrayLunch:
I'm still holding out for source to drop tomorrow.
[Samsung Epic 4G Touch] daniel4653:
Hope it drops tomorrow.
[Samsung Epic 4G Touch] winfan:
Hopefully it will but it could be June 7 if you follow their words ver batem.
[Samsung Epic 4G Touch] TrayLunch:
I don't want to argue semantics, but that can be contested. If memory serves me, Samsung said that they would hold source no later than the 6th. I take that as meaning on or before, but no later than. I could be wrong. It happens often. LOL!
[Samsung Epic 4G Touch] winfan:
Agreed. And also doesn't source drop 3-4 days before ota release?
[Samsung Epic 4G Touch] winfan:
Just checked and they haven't uploaded source yet
[Samsung Epic 4G Touch] daniel4653:
And if its from samsungs side that means June 6th Korea time which it is already there. Currently 1am ;)
[Samsung Epic 4G Touch] RustedRoot:
Off-topic: GS3 pre-order up on Sprint's site: 16gb, $199; 32gb $249 Both are 1.5 ghz dual core processors. Only 50 bucks more for the 32gb? Guess which one will sell out first?

http://shop.sprint.com/mysprint/sho...0119&flow=AAL&planSKUId=&ptn=&tabId=dt_phones

@Jay: Don't tase me bro
[Samsung Epic 4G Touch] garwynn:
The open source site is hosted from S. Korea so if we see a drop I would hope to see it around mid-day to afternoon our time. (Depends on what time they release I guess...)

---------- Post added at 05:14 PM ---------- Previous post was at 05:05 PM ----------

...the person that noted this already had a point. Looking at Sprint's community blog for the E4GT:

Release EG30 wasn't released until 9/16 (Initial release) - Delay of 45 days

EK02(11/2) --> 12/7 - Delay of 35 days

EL29(12/29) --> 1/25 - Delay of 27 days

FF02(6/2) --> ? (3 days and counting)

They could easily justify that it is taking time for internal testing and validation... but most people would just call shenanigans on that if they *just* happen to release it at the end of the month (after they get many of the GS2 users not "in the loop" to jump ship to the GS3, that is.)
[Samsung Epic 4G Touch] rokair:
I'm fairly sure that it will NOT actually come with it but the following wording in the Specifications have to make you wonder if the phone will ship with the SD Card. (Again, I'm sure it doesn't but it doesn't say compatible with...)

Memory

16GB and 32GB internal memory(ROM), 32GB MicroSD card

EDIT:: And, there I go contributing to the off topic. Err. Sorry.
[Samsung Epic 4G Touch] someguyatx:
Samsung didn't say anything this is info that was heard from somebody, who told somebody else etc... at this point I'm not holding my breath. In the meantime Wicked Sensations rom is pretty nice.
[Samsung Epic 4G Touch] TrayLunch:
Point taken. To append my previous statement:

A guy posted here that his source at Samsung told him that the source code for ICS would be held no later than 6/6.

I don't think TCR has anything to gain by lying to us, but I could be wrong. He posts what he's been given. That makes him an easy target especially if there is any change to that information that his source or he isn't made aware of. I respect that, as it isn't an easy choice to make. Time will tell.
[Samsung Epic 4G Touch] reddragon72:
There is none and never has been a pre-mention from Samsung about when they were going to release source code it just appears. LOL

And we also have to take into count that the T-Mobile's, seriously different, variant of the SGS2 is getting their OTA on June11th. If we want to follow trends, which in this case we do not, then we can say it'll take roughly 3 months from June 11 to get our ICS update because that is how long it took from T-Mobile GB first leak(which is still not officially released) in the Vibrant to the Sprint Epic 4G GB update. I don't like those numbers at all when reversed!
[Samsung Epic 4G Touch] TrayLunch:
Agreed, I do not like those trends at all, so I will hold on to my hopes that TCR's source is good. As far as pre-mention goes, we aren't talking about a press release here. We're talking about inside info. Like I said, it could be bad info. I hope it's not. Time will tell.
[Samsung Epic 4G Touch] someguyatx:
I don't think anybody ever thought he was lying. Do you guys remember the telephone game they used to play in school or camp. You start on one side of the room with a phrase and tell the person next to you and its totally different by the time it makes it around the room. Also there are so many variables involved in a software release that could mess things up. And finally the 6th is Korean Memorial Day, financial markets are closed and chances are most people are off.
[Samsung Epic 4G Touch] TrayLunch:
Good call on the Korean Memorial Day. I wasn't even aware of it. If memory serves me correctly, there were those that said they'd take what he had to say with a grain of salt and those who flat out said it was "an attention grab." That's calling someone a liar by dressing it up in a pretty ball gown.

EDIT: Did I just let my Texas slip out? LOL!
[Samsung Epic 4G Touch] :
FF02 Is FINAL

Woohoo :D
[Samsung Epic 4G Touch] iniz94:
Shareeeee
[Samsung Epic 4G Touch] Esoteric68:
Give up the goods man and no one gets hurt! lol
[Samsung Epic 4G Touch] TrayLunch:
Lemme guess, you're not sharing.
[Samsung Epic 4G Touch] isaac2k10:
nice

Sent from Isasc's Rooted & Suited E4GT...
[Samsung Epic 4G Touch] winfan:
Is this an RC (release candidate)?
[Samsung Epic 4G Touch] fatboypup:
i wanna smother you in ants bee's and honey
[Samsung Epic 4G Touch] satur9ine:
Any new OTA info? Please?
[Samsung Epic 4G Touch] :
It says final
[Samsung Epic 4G Touch] rwright64:
No way!
[Samsung Epic 4G Touch] winfan:
This is the final build and they will use this as ota? Just confirming what you said there. Do i have it Correct?
[Samsung Epic 4G Touch] Esoteric68:
lol
[Samsung Epic 4G Touch] :
Final but who knows if its OTA
[Samsung Epic 4G Touch] fatboypup:
all hail king sextape :)
[Samsung Epic 4G Touch] humdrum2009:
NICE

Thanks sextape (pause) lol.
[Samsung Epic 4G Touch] Ascertion:
I knew the 36th time would be the charm.
[Samsung Epic 4G Touch] fatboypup:
plugging my phone in now ..... must have full battery :eek:
[Samsung Epic 4G Touch] someguyatx:
Perhaps the 6th was good info after all :confused:
[Samsung Epic 4G Touch] thirdcoastraised:
The fact that anyone took what was said about the potential builds to mean Sprint could "choose" one is ludicrous. That would be like putting crack and wax in front of a recovering crack head and hoping he would choose the wax rather than potentially commit suicide with the choice he would most likely make. Samsung would not give Sprint a choice in the matter. Sprint has the OTA and it could be ff02, it could be fe16 hell for all we KNOW, it could be a modified fb07 renamed fe25, just because the different rdfs are coming out doesn't mean that is going to be your OTA. We know Sprint is currently focusing on GS3 which I preordered today myself, but rest assured Samsung IS NOT building new updates for E4GT.

Yes the Tmo gs2 is significantly different, but they too were succeptible to the emmc issue NOT JUST E4GT...ALL SAMSUNG GALAXY S2 VARIENTS! So again, Sprint is simply playing the "business first" card but our E4GT will receive the update. Btw I'm tracking the preorders pretty closely and for all the crap folks talk about Samsung, the GS3 is set to smash records today in terms of preorders....that says a ton right there.

I will be one of many with both devices, but personally am looking forward to watching reactions when source is finally released and again in November when Android 4.1 is released and this whole scenario plays out again

Sent from the only ROM Epic enough to run on my Epic 4G Touch... The Blu Kuban 1.0.3.6!!! Sprint quit screwing around and let's "Sprint" forward!
[Samsung Epic 4G Touch] fatboypup:
pretty sure im gonna keep this handset as a backup to my sg3 and not sell it I see it still rocking for a long while
[Samsung Epic 4G Touch] winfan:
Thanks for the information. Do we have a chance to install this one?
[Samsung Epic 4G Touch] thirdcoastraised:
Guess time will tell...either way guys and gals, its been a fun ride, now keep your hands inside the car as we prepare for one final hyperdrive run on the rollercoaster that is "ICS for E4GT"

Sent from the only ROM Epic enough to run on my Epic 4G Touch... The Blu Kuban 1.0.3.6!!! Sprint quit screwing around and let's "Sprint" forward!
[Samsung Epic 4G Touch] kc_exactly:
I was beginning to think we would never see this. Sextape has came through yet again.

Have you noticed any changes other than the version number?
[Samsung Epic 4G Touch] satur9ine:
Sextape, here's what you do:

Create a new XDA user with the name of CintaDeSexo (no one will ever know it's you).

Post a linky of leak with said user name.

We all profit.
[Samsung Epic 4G Touch] Specialksg1:
Where is Adele, sex tape?? ;)
[Samsung Epic 4G Touch] winfan:
Could you please share the el29 to Ff02 update zip file? I appreciate your help and in no means am I demanding anything. If it can be done great if not we can wait.
[Samsung Epic 4G Touch] fatboypup:
NO WAYYYYYYYYYYYYYYYYYYY ....... give it to my one click odin wizzard guy ;)
[Samsung Epic 4G Touch] kasper19:
normally I would be dying to get the latest leak, but as I'm on cm9 ..... gimme the source dammit!
[Samsung Epic 4G Touch] satur9ine:
CM9 here as well. I still enjoy a good leak. :D

Umm, for the modem and kernel.
[Samsung Epic 4G Touch] tailsthecat3:
Won't be doing much until root and recovery. Gotta have a recovery for the safety of backups. Hope its possible
[Samsung Epic 4G Touch] edlee:
You are the effing man. Do you notice any improvements so far?
[Samsung Epic 4G Touch] Omar04:
Please share for the sake of our sanity! LOL :D
[Samsung Epic 4G Touch] leaderbuilder:
tick tock, leak.....where are you.....

:P
[Samsung Epic 4G Touch] davidstjohn1:
is this out yet
[Samsung Epic 4G Touch] tailsthecat3:
No
[Samsung Epic 4G Touch] blackroseMD1:
Should just set up one of those websites...

Is [build number] leaked yet?

[Yes] or [No]

Hahaha
[Samsung Epic 4G Touch] TrayLunch:
Request OP to add "sextape is a stinky jerk who smells his own farts" to thread title if he refuses to share, LOL!
[Samsung Epic 4G Touch] JosephD1014:
You guys realize from the screenshot he sent that he probably JUST got done installing it (notice how it just got done with media scanning so it just booted up) - depending on how he got it it probably needs to be repackaged so that we can use it. Give the guy a minute ;)
[Samsung Epic 4G Touch] TrayLunch:
That's usually sfhub who is on vacation. I say let him enjoy it, and we can wait.
[Samsung Epic 4G Touch] TrayLunch:
That was two hours ago. Minutes up, LOL! Update.zip is fine.
[Samsung Epic 4G Touch] locoboi187:
For all you guys know, FF02 could be a renamed FE22. No advantage to that except source lol
[Samsung Epic 4G Touch] Esoteric68:
Source is all I'm interested in, well not that I can do anything with it but I know the Devs can turn water into wine once they have their hands on it.
[Samsung Epic 4G Touch] sfhub:
If someone sends it to me, I'll have it out.
[Samsung Epic 4G Touch] TrayLunch:
Enough razzing and goading. How is it?
[Samsung Epic 4G Touch] daniel4653:
Thank you sfhub. Hope you are enjoying your vaca
[Samsung Epic 4G Touch] fatboypup:
my muthaeeeeefinnnnnnnng dogg!
[Samsung Epic 4G Touch] :
Enjoy

Also I will not be providing .TAR
[Samsung Epic 4G Touch] Esoteric68:
We can always count on you and that's a damn nice feeling.

Thank you.
[Samsung Epic 4G Touch] garwynn:
(Removed)
[Samsung Epic 4G Touch] Esoteric68:
Oh and he comes through with a clutch shot!

Thanks sextape :)
[Samsung Epic 4G Touch] peanut1596:
Fantastic. Thank you sextape.
[Samsung Epic 4G Touch] rwilco12:
Sextape I just want you too know I'm naming my next child after you. :-)

For everyone else I'll have the kernel posted as soon as my download is complete and I can pack it in a zip.

If nobody beats me to it I'll see if I can get the modem up too.

---Looking for a kernel? Find them all here!---
[Samsung Epic 4G Touch] kali323:
Thanks sextape. We appreciate what have you done for the epic touch community. I was one of the few that send you a donation a while back
[Samsung Epic 4G Touch] datajosh:
Not even to sfhub? :p Thanks for all the leaks during this whole process!
[Samsung Epic 4G Touch] Esoteric68:
Fantastic, thank you. Your thread is an awesome resource site.
[Samsung Epic 4G Touch] Currupt247:
has anyone downloaded it yet? my eta is 3 hours!
[Samsung Epic 4G Touch] master acehole:
^THIS!!!!!

And where does it say final?