yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] evantonio:
can you give a little more insight on that? i'm trying to get into download mode, but i'm stuck at a screen that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."

(kies won't recognize the phone)

before i was at this screen, i was trying to use odin one-click install to get ICS onto an at&t galaxys2 i727.

any help on how i can get back into download mode, or somewhere else where i can do something, would be a big help.
[Samsung Epic 4G Touch] Majin101:
you have to use odin and flash the stock el29 cmw
[Samsung Epic 4G Touch] evantonio:
any tips on getting into download mode? when i reboot the phone i'm able to get to the screen that gives me the option of download mode or continuing a regular boot-up, but when i click either one it brings me to the firmware error screen.

---------- Post added at 03:29 AM ---------- Previous post was at 02:47 AM ----------

never mind. i was able to use odin 1.3 to get it all fixed. thanks!
[Samsung Epic 4G Touch] trithumb:
i have the same error. I can get into download mode fine. I just cant get anywhere else. When i plug my phone into my computer it doesnt even make any attempt to connect to the computer... no successfully connected, no error failed driver nothing... hellllppppp
[Samsung Epic 4G Touch] pro_granade:
I actually just encountered this, and I found this way out, I flashed the AGAT recovery with the odin executable.
[Samsung Galaxy Player 4.0, 5.0] shahrukhraza:
just post your best pics you got with your galaxy player!
[Samsung Galaxy Player 4.0, 5.0] eerie_silence:
Nice thread, thx.

Last pic:
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
I know it's a little girly, but this was the first picture I took, and IMO the best! For some reason it just does really good with flowers!View attachment 1075827

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] alljokingaside:
This seems fun
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Let me try... the biggest problem I have with the camera is no zoom, which kinda limits its usefulness.

Sent from my 5.0 USA GenGin + ICS theme
[Samsung Galaxy Player 4.0, 5.0] MajinZERO:
The lasc pic I got. Here you go

View attachment 1131886
[Samsung Galaxy Player 4.0, 5.0] ScienceCat:
This is a pretty nice idea.
[Samsung Galaxy Player 4.0, 5.0] server60:
Some mine pics...
[Samsung Galaxy Player 4.0, 5.0] Rapydax:
These were made in Paris (obviously)
[Samsung Galaxy Player 4.0, 5.0] QuanticZero97:
Here are some ;)
[Samsung Galaxy Player 4.0, 5.0] Mashed_Potatoes:
Please tell me that you have the Korean model with 5mp and a better sensor, because my YP-G70 has a **** camera.
[Samsung Galaxy Player 4.0, 5.0] the playa!:
pretty darn amazing pictures i would say! :)
[Samsung Galaxy Player 4.0, 5.0] captpete1:
Here's one using Camera ZOOM:
[Samsung Galaxy Player 4.0, 5.0] vallt1:
nice

those are some really good pictures right there.
[Samsung Galaxy Player 4.0, 5.0] TheKryptonite:
Derp.
[Samsung Galaxy Player 4.0, 5.0] snickersboy41:
I didnt want a 3rd party launcher (too heavy for Samsung galaxy player), but I did want to customize it to my liking :)
[Samsung Galaxy Player 4.0, 5.0] QuanticZero97:
Sorry for not answering, didnt notice :D I have international 8GB model (3,2 Mpix camera)
[Samsung Galaxy Player 4.0, 5.0] QuanticZero97:
Here are some more...
[Samsung Galaxy Player 4.0, 5.0] walrusmonarch:
Those are really good pictures dude! I didn't even know the camera on the SGP was that good lol. Now I wanna try taking some pictures with mine :laugh:.
[Samsung Galaxy Player 4.0, 5.0] QuanticZero97:
Thanks, and good luck :)
[Samsung Galaxy Player 4.0, 5.0] shahrukhraza:
Are you some professional photographer or something!? Because those are really amazing pics if they were really taken from the player. And this was from the stock camera right? I had no idea it could take such good lowlight pictures!
[Samsung Galaxy Player 4.0, 5.0] QuanticZero97:
Haha im not a professional... pics were taken with stock camera app... you just need patience and steady hands because of slow autofocus :D
[Samsung Galaxy Player 4.0, 5.0] SerkTheTurk:
This was taken from my 4.2 after hurricane sandy
[Samsung Galaxy Player 4.0, 5.0] ygnacz:
These are mine...
[T-Mobile Samsung Galaxy S II SGH-T989] d3athb4dishonor:
As far as stability and performance. Just picked one up today coming from a My Touch Slide 4G and I plan on rooting soon as I get home lol.

Just wanted to get some ideas on what I should try out.
[T-Mobile Samsung Galaxy S II SGH-T989] xcrazydx:
Try searching. There are already at least 3 of these threads.
[T-Mobile Samsung Galaxy S II SGH-T989] d3athb4dishonor:
Lol damn my bad cool guy.
[T-Mobile Samsung Galaxy S II SGH-T989] xcrazydx:
No problem, happy searching!:D
[T-Mobile Samsung Galaxy S II SGH-T989] blackangst:
Lazy man's way? Go into the development thread then click the stats link to sort by replies. Then start at the top :)
[T-Mobile Samsung Galaxy S II SGH-T989] rolf90:
Juggernaut but just wait until they update the gb roms since some maintenance update came out recently.
[T-Mobile Samsung Galaxy S II SGH-T989] mysticfrog:
my personal preference was juggs with the beautiful theme.. i ran that one for a while... cm9 is another great one.. those were my two favs man...
[Samsung Epic 4G Touch] ijoshv2:
Due to an error in the kernels we've been flashing to our devices, a lot of users have been experiencing a FULL BRICK. Full brick meaning you may as well play golf with your phone, it's dead.

I've been told there is a fix, BUT YOU MUST NOT FLASH ANYTHING FROM CWM. The bug is originating from flashing a corrupt kernel from CWM or mobile ODIN.

Here's a cut from the article:

Just like you, I don't wish to brick my E4GT. xST4T1K has posted a comprehensive guide to find your options on removing the affected ICS kernels from your device, and hopefully resulting in you not bricking the crap out of your phone. Go check this page: http://xdaforums.com/showthread.php?t=1525495

I DO NOT take credit for finding this bug, credit goes to Entropy512 and XDA TV's EGZTHUNDER1 for alerting me of this bug. I have safely removed the affected ICS kernel from my phone and custom builds, now it's your turn.

The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.

Please, once again, GO TO THIS PAGE and explore the options of returning your phone back to dry land.

As a reminder, DO NOT FLASH

ANYTHING

FROM CWM OR MOBILE ODIN.

While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.

Safe flashing, XDA members.
[Samsung Epic 4G Touch] KBizzle:
Maybe this sticky from the general forum should just be moved over to here.

http://xdaforums.com/showthread.php?p=23149990
[Samsung Epic 4G Touch] slick_rick:
Weve kinda known this for a while now since the February leaks... js. Still, safe flashing everyone lol.
[Samsung Epic 4G Touch] bigpeng:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...

USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...

DO NOT WIPE FROM STOCK OR CWM RECOVERIES...

If you do what is said above, you won't brick your device.

Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?

NOW again....

USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...

DO NOT WIPE FROM STOCK OR CWM RECOVERIES...

Quite Easy.

In the end, it's called following directions.

Edit: just to clarify... Wiping cache/dalvik cache from stock or cwm repacked recoveries is safe.

The issue is Wiping Data (Don't use the option) :mad:
[Samsung Epic 4G Touch] DjKurt:
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
[Samsung Epic 4G Touch] ijoshv2:
In a world where users flash before they research, common sense doesn't have a stronghold.
[Samsung Epic 4G Touch] bigpeng:
The issue is from Wiping Data from stock and cwm recoveries, you can wipe cache and dalvik with no worries. Those don't mess with partitions.
[Samsung Epic 4G Touch] scarmon25:
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
[Samsung Epic 4G Touch] bigpeng:
That sucks, sorry to hear that...

I was one of the first to test cwm repacked recoveries for agat63 since FE10 and have flashed 37 times to and from different roms and done backups and restores countless times and I've been fine.

I haven't been fearful of any bricks since I tested these repacked kernels.

Hope it does get figured out once source hits though.

Edit: btw what kernel (with or without cwm repack?) did you brick in?
[Samsung Epic 4G Touch] scarmon25:
It was back when CM9 first was released. I was using the el26 cwm kernel to flash. I was on one of the ice builds I can't remember. I odined the kernel cwm combo el26 and then ran a format all and flashed cm9 and ggot the blue light special haha

Its all good though. I have read alot of info in this including the one mentioned. One thing that was mentioned in one of them is that the bug had been triggered be deleteing a large file off the internal memory. That worried me. So I've been weary of ICS builds since. The fact that the issue seems to be that info getting wrote to a certain block of the emmc has me worried that it could be triggered by more then wiping of flashing. I have ran agats ROMs and I have to say he seems to be doing something right. Whether it is because he is staying TouchWiz or what for some reason his users seem tto not have many issues. But just keep in mind that it may not just be kernel/recovery related.

Safe flashing is key and I never want to see someone brick. Just be careful in whatever you do. :)
[Samsung Epic 4G Touch] xST4T1K:
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place. ;)
[Samsung Epic 4G Touch] ijoshv2:
I couldn't have said it any better, my friend! :p

As far as those who've bricked their phones, it is truly unfortunate.. Google themselves has been brought into light on this situation, and are working to correct this issue in the kernels that they've been adding in with their firmware.

As far as your useless phones go.. Try filing for an insurance claim, I guess! NOT my professionally recommended advice.. But IF someone were to have stolen that useless phone of yours and you were to never see it again.. Well, who am I to say that's not a reason to get a replacement from asurion! Lol!
[Samsung Epic 4G Touch] ijoshv2:
By the way, xST4T1K.. Bumped you thanks count up a little more. ;)

Thank goodness I ran into these threads before I decided to flash anything else.. Been running a solid ICS rom for a few weeks, now. But I'd rather get back to safe land on GingerBread Island and use Apex Launcher. Wouldn't care for the huge difference in the settings menu. Would miss the lockscreen, though.. Not aiming my finger at an unlock tab has gotten habitual!
[Samsung Epic 4G Touch] elliwigy:
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
[Samsung Epic 4G Touch] scarmon25:
I would never want to scare anyone away from trying these great builds on XDA. What I do want though is to make people aware that no matter how many tines you flash something. Always treat the flash your about to do as if it was your first. Sometimes we get to comfortable in what we're doing. We have to remember that this is a pretty expensive device and if something happens you may be buying a new one outright. Not everyone has insurance or can throw out that kind of cash. Do safe flashing practices and make sure you read the OP. When flashing leaked software make sure to flash from stock or the most current OEM released build such as EL29 in this case. Verify the right files are in the right slots of Odin. Make sure you're flashing files in the right sequence when in a custom recovery. Thing like that. I believe in the openness of android and never want to see anyone say they aren't going to flash something because they are scared. With the right ammount of reading and precautions. There is no reason to be scared.

Just for example. And this is not an exaggeration. Between this phone,my wife's phone, my last phone, my wife's last phone, and numerous friends phones. I have well over 200+ flashes. I have only had one actual brick. And that brick was because I got too comfortable in what I was doing. So, odds are if you take tthe time to do it right. You will succeed. Also.
[Samsung Epic 4G Touch] darren.wlsn1:
i cant figure out why this is not locked yet....
[Samsung Epic 4G Touch] elliwigy:
i agree scarmon.. you said it better than i could.. if i wasnt tech savvy and i read the op i would have been scared away.. it says in all caps not to flash in cwm and says many have experienced bricks.. it can be worded differently but its freedom of speech.. when the initial leak came out and we had rogue ics kernels and the LOSt kernel we werent sure why people were having bricks until we figured out what was causing it.. we've known this for a while and since then hard bricks have dropped drastically.. and every single developer insisted not flashing from ics kernels and every rom has a disclaimer in the op for this reason.. only bricks ive read have been user error for a while ie. unplugging device during odin flash or battery dieing during mobile odin flash etc.. plus this is in the dev thread.. right now most people come here for ics roms since thats what devs are working on.. and many have gone safely back to gingerbread many times.. the ics roms have hundreds of thousands if not millions of hits and how many posts about hard bricks?
[Samsung Epic 4G Touch] kyamora:
I've been flashing ICS roms since FB17 and haven't had any bricks. I've been making sure to only flash things from EL26 and it's been smooth sailing.

Now I'm running the most recent AOKP and it's running very well.
[Samsung Epic 4G Touch] RainMotorsports:
Your credit is pretty thin too. Entropy is a big name in this issue but him and some random dude that apparently notified you very very late about this issue doesn't even cover half of it.

The front page news on the issue was pretty late as well. Just lets the general population know about it.

Its things like this "While I have heard" that is the problem with your post. That and begging for a sticky, talk to a moderator if you feel its important.

Flashing a non-ics kernel through ODIN does not fix any issue. Flashing from a safe Kernel avoids the issue, If your on ICS flashing the GB Kernel from ODIN would be the safe method. Gingerbread as far as we have known and hundreds of flashes per person per hundreds of phones later. No one has been known to trigger the eMMC firmware bug though gingerbread. So yes flashing from a Gingerbread kernel as we have since the phone came out is the safest known way. You don't need anyone to tell you that.

You come in and say "Do not flash anything from CWM". This is inaccurate it suggests one can not flash from EG30+ CWM which has never been a known danger. Obviously EK02 would be more popular due to supporting full modems rather than patch. EL26 was the last to have true CWM which is why EL29 Rogue is less often suggested.

The danger is not in flashing ICS. The unknowing user is going to be flashing ICS from EL29 which is safe. The danger is after they are there, and they try a factory reset, or install a CWM or Unlocked Recovery Kernel and flash something, or flash an update.zip through stock recovery. Yes they need to know, the information should be accurate however.
[Samsung Epic 4G Touch] coiledwire:
If anyone wants details of this emmc firmware bug, there's some really knowledgeable people in this thread.

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

The info is very detailed, but these are the individuals to watch. OP if your serious about helping our community with this emmc bug, I hope you join in that conversation instead of asking to sticky this thread.

Sent from my SPH-D710
[Samsung Epic 4G Touch] carhauler1969:
I've been running ICS roms since FB05, through the current FE16 leak. For most of that time I was flashing with the repacked ICS kernels, I've never had a problem. :eek: *But* I never EVER wipe/system or /data with the repacked recovery itself. I've always used Calkulin's FormatAll since very early in the EVO 4G days. All I ever wipe in the recovery itself is /cache & /dalvik cache.

:o I've also recently started heeding the warnings about flashing with the ICS kernels leading to damaging the eMMC chip, so now I flash everything with the EL26/Stock CWM repack kernel. :)

The article linked in the OP of this thread really opened my eyes as to what the cause of all the bricks was, & I consider myself lucky not to have hard bricked my phone, or my wife's E4GT.

Heed the warnings, Google is aware of the problem, & I believe the fix has already been implemented at least by Google, going by what I read in the article.

Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 Pro
[Samsung Epic 4G Touch] RainMotorsports:
Your credit is pretty thin too. Entropy is a big name in this issue but him and the news poster that apparently notified you very very late about this issue doesn't even cover half of it.

Its things like this "While I have heard" that is the problem with your post. That and begging for a sticky, talk to a moderator if you feel its important.

Flashing a non-ics kernel through ODIN does not fix any issue, the real issue is permenant. Flashing roms or resetting from a safe Kernel avoids the issue, If your on ICS flashing the GB Kernel from ODIN would be the safe method. Gingerbread as far as we have known and hundreds of flashes per person per hundreds of phones later. No one has been known to trigger the eMMC firmware bug though gingerbread. So yes flashing from a Gingerbread kernel as we have since the phone came out is the safest known way. You don't need anyone to tell you that.

You come in and say "Do not flash anything from CWM". This is inaccurate it suggests one can not flash from EG30+ CWM which has never been a known danger. Obviously EK02 would be more popular due to supporting full modems rather than patch. EL26 was the last to have true CWM which is why EL29 Rogue is less often suggested.

The danger is not in flashing ICS. The unknowing user is going to be flashing ICS from EL29. The danger is after they are there, and they try a factory reset, or install a CWM or Unlocked Recovery Kernel, or flashed an update.zip through stock recovery. Yes they need to know, the information should be accurate however.

Put it to you plain and simple

The kernel itself is not the problem, but the only fix/work around will have to be applied at this level. The bug is in the eMMC firmware which can not be updated by the end user. The bug is triggered on ICS kernels specifically by a particular erase operation.

If you want to come in and inform people of the problem at least make an attempt to have a basic understanding of the problem. I know very little about it myself. But your post has made it apparent you were only recently informed while we have known there was AN issue since at least March and very recently over the last month the details have been solidified by very hard working developers and researchers. Things that were sadly known to Google and Samsung all long.

The things you wish to "inform" xST4T1K of can already be gotten from several people here if he doesn't know. Can name 3 people that should be able to reiterate everything known. All of which you are about to "Discover".

Please read this entire thread if you have not yet - http://xdaforums.com/showthread.php?t=1644364
[Samsung Epic 4G Touch] chris41g:
wait... whats this about bricks and ice cream im confused.. so i pray to odin and get a new phone?? but what does any of it have to do with POPCORN!?
[Samsung Epic 4G Touch] bykim5:
1. Mobile Odin to flash EL26+CWM kernel.

2. Wipe data x 3, wipe cache, dalvik.

3. Flash new ICS leak, gapps.

4. Reboot

I use Odin to flash new modems. Kernels - i just use what came with the rom.
[Samsung Epic 4G Touch] chris41g:
I suggest not using mobile Odin if currently running an ICS leak kernel.. it uses the same functions as the CWM wipes.. so be safe and always use PC odin or Heimdall when leaving a leak kernel
[Samsung Epic 4G Touch] Kebetz:
You can MobO the kernel no problem.... just...No....... MobO!! system!!!!

I use HC-kTool a lot also.. love those apps...

But yeah, Mr. O.P, thanks for trying to help but I'm curious what..... what "credit" goes to whomever you said? I'm sure he's a great guy... but that article says he "brought it to their attention" not diagnosed,identified,studied,cured.

Or maybe it did, idk, who actually reads posts these days? ;)

Edit: Fraud too? Shame on you, MR OP!

Wind it back a couple months and youd see me thinking this issue was a known Touch Recovery specific problem (that's what EVERYONE said... at the time...) and and clicking on that factory reset button from rogue1.2.2 and blizzzooowww. (Idk) lol I guess my point is stop talking outta there and sit it finally!

Uh oh! He knows that there's a real life Freemason (yeah, I'm that good at bricking) here! I'd better hide!
[Samsung Epic 4G Touch] MJHawaii:
All you had to do was BUMP the thread your linking your OP I'm not even gonna say it the masses have spoken
[Samsung Epic 4G Touch] SantinoInc:
To the gallows with ye! :eek:
[Samsung Epic 4G Touch] MJHawaii:
But not before ye pint of bubbles :beer:
[Samsung Epic 4G Touch] jayharper08:
There is plenty enough discussion on this. It's posted in almost every thread. OP, I thank you for trying to help, but this is not going to do anything but turn into a derailed thread.
[HTC Wildfire S] ScardracS:
Marvel is the name of your device. The most famous are marvel and marvelc. i think the name is different because the device use different data connection, but i'm bot sure. I hope i can help you.
[HTC Wildfire S] Nightshadow931:
There are instructions for how to flash a ROM in every ROM thread.