yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] master acehole:
-_____________________________________-
[Samsung Epic 4G Touch] KELO777:
What do u mean ?

SORRY I DON'T UNDERSTAND BUDDY WHAT DO YOU MEAN BY brix city ?
[Samsung Epic 4G Touch] FrameCityJackal:
Redman came to his house and took his phone :confused:
[Samsung Epic 4G Touch] ungovernable1977:
Bricked fone.
[Samsung Epic 4G Touch] daniel4653:
Can we donate or do something to help you out steady?

Sent from self nominated team "Z" member's phone.
[Samsung Epic 4G Touch] musclehead84:
Yeah i agree. Hes done alot for us.
[Samsung Epic 4G Touch] kc_hubbard:
Curious to know what it was that you think bricked your phone. I know there's an entire thread about this and I've read about all the others, but as you're clearly someone who's very experienced at dev'ing/modems/etc I'd like to know what happened.
[Samsung Epic 4G Touch] agentfazexx:
Sucks... guess FB27 is gonna have to wait.
[Samsung Epic 4G Touch] kc_hubbard:
Just my opinion here, but I don't think this precludes you from using FB27. Just don't try to use any CWM-based recovery while on FB27 (or any other ICS-based ROM for that matter). If you need/want to flash a different ROM once you are on ICS, make sure to odin back to stock/rooted EL29 (or maybe any stock/rooted GB ROM) first.
[Samsung Epic 4G Touch] agentfazexx:
I make regular backups in CWM, so that's a deal breaker.
[Samsung Epic 4G Touch] JohnCorleone:
Best Redman reference ever! Sorry to hear about da brick Steady. Hopefully its a blue light only and you have insurance
[Samsung Epic 4G Touch] musclehead84:
Confirmation number: 0LK74240WA647081S.

Just sent a small donation to u SH. sorry it wasn't more but I wanted to help out. You've done alot for this community. It was sent under my wife's email address.
[Samsung Epic 4G Touch] Steady Hawkin:
Thanks bro, we really appreciate it!

Just called Sprint and they got a shipment in, which means I'm going to get a new phone on my lunch break today. Then its back to puttin in work! :D
[Samsung Epic 4G Touch] agentfazexx:
Wahoo, you rock dude.
[Samsung Epic 4G Touch] cidica:
Right on man. Glad Sprint is gonna hook you up cause you do awesome work :)
[Samsung Epic 4G Touch] digweed4me:
Donation coming tonight steady

I am rocking fb 27 with no recovery .

Oh man i missed rogue recovery
[Samsung Epic 4G Touch] cjwaggsrx8:
+1 man you are the shiz!!!
[Samsung Epic 4G Touch] countryteazer:
More great news! Glad you got it all squared away. This phone NEEDS you.
[Samsung Epic 4G Touch] musclehead84:
Thats awesome news man. I hope everyone on here can help these developers out. Even one dollar can help. Thanks to the developers and the users on here
[Samsung Epic 4G Touch] Dchibro:
Yeah I sent some funds their way yesterday coincidentally. Maybe my donation bricked his phone! :D

Edit - I have to admit, all these bricks lately, especially adding sbrissen and Steady to the mix, has me really nervous to go anywhere from FB21 now. I'm even nervous to Odin a EL29 TAR now, after reading some things today. I have everything downloaded to move to FB27 and I can't pull the trigger on doing anything out of fear.

Edit 2 - Eff it. I'm always as careful as one can be and I have insurance. I'm not gonna let fear rule me. Here I go!!!!
[Samsung Epic 4G Touch] musclehead84:
Honestly man just do what u know works. Don't flash any temp recoveries. Use Odin to go back to gingerbread. I bricked my phone and I'm back on ics. Just be careful on what u do. Ask if u don't know something. Good luck
[Samsung Epic 4G Touch] kc_hubbard:
+1 on the odin back to GB before you do anything. (knocking on wood) I've gone back and forth probably 15 times the last 3 or 4 days doing it this way. I won't even try to upgrade ICS to ICS w/out an odin to GB first.
[Samsung Epic 4G Touch] agat63:
I'm on FB27 as well.

Just followed the guide in OP.

Comming from FB21.

DL'd and moved zip files with rom and modem to sd card.

Boot to recovery.

Wiped phone using Calk's format all zip.

Flashed rom. Flashed modem and booted to system.

Everything works as it should.

Known bugs are there but that's it.

IMHO this build is the best and most stable from all ICS roms we had so far.
[Samsung Epic 4G Touch] Steady Hawkin:
I cant thank all of you enough for all of the support (and donations ;) ) you have given us, it really does mean allot. Good news is, got a new phone and I'm back up and running! Bad news is, I'm reluctant to release anything until this issue gets sorted out. If you or anyone you know has bricked, please have them fill out the questionnaire on my G+ page (link can be found in my sig). Thanks fellas, let get this **** figured out so we can put it in the rear view!
[Samsung Epic 4G Touch] Dchibro:
Word to that. I really hope we get to the bottom of this soon. Honestly, I'm following the advice of a few around here and I'm not flashing anything via an ICS kernel repack with CWM until this data partition EMMC thing gets figured out. If I'm using CWM to flash anything until further notice, it will be from your stock EL29 repack. This may be over cautious, but the time spent waiting for Odin to flash the EL29 TAR and subsequent kernel repack is better than driving down to a Sprint repair center.

Edit - I'm probably going to use this as motivation to drop the coin on Mobile Odin Pro too.
[Samsung Epic 4G Touch] Kurupt1:
Dam no issues here, never flashed cm9 and only used repackaged kernels and have had zero issues switching ICS builds. Currently on fb27 waiting for the repack, this build is so smooth. Hope you brickers figure it out.
[Samsung Epic 4G Touch] musclehead84:
From what ive read and from my brick it wont happen if u have a stock repacked kernel. Its being cauaed from flashing temp recoveries. Ive used the fb21 repack to fladh roms, backup, restore, and wipe without any problems. I think the stock repacks are prerty safe. Its the fladhing of temp recoveries on top of the linux 3.0 stock kernel that causes problems.
[Samsung Epic 4G Touch] kc_hubbard:
I'm scared that until we actually get kernel code, and therefore the recovery code that comes w/ the ICS kernelo, we may never get to the bottom of this. Not sure it can be reverse engineered either as flashing/wiping like we have been puts a phone in jeopardy of being bricked.

In any case, keep up the good work Steady. Your stuff has always been too good to jump ship now, especially since it's looking likely that Google/Samsung has caused us all the problems.
[Samsung Epic 4G Touch] Dchibro:
I totally buy this, except, unless SH comes here and corrects me, I'm very doubtful that he was messing around with temp recoveries at all.
[Samsung Epic 4G Touch] musclehead84:
Yeah I would like to see what he was doing when he bricked his.
[Samsung Epic 4G Touch] firket2000:
+ 1
[Samsung Epic 4G Touch] scarmon25:
Mine bricked by flashing CM9 from the rogue repack while on FB17 I believe. May have been FB21. I believe the brick happens when you wipe data from any recovery other then the stock recovery while on ICS. I have been odining back to stock EL29 before flashing another ICS ROM when coming from an ICS ROM and haven't had any issues. Seems that if you stay away from custom recoveries and flashing things while on ICS the chances of a brick go way down. Just my take on it.
[Samsung Epic 4G Touch] iniz94:
Yup, what he said.

My phone was bricked when I flashed Blazer's ICS alpha ROM for VIPs over to my phone. It wasn't working how I liked it so I wiped my data using CWM Touch and got the data partition error. Luckily I now got a replacement though so beware of CWM Touch and ICS Recoveries in general.
[Samsung Epic 4G Touch] Admiral2145:
voltage

anyone know the voltage table for thise 1.2.1 rogue? and or can we flash calk's undervolt scripts?
[Samsung Epic 4G Touch] Dchibro:
Well its not for certain that it will happen. I went from FB17 to FB21 by flashing Calks wipe all ZIP in the Rogue FB17 CWM repack, flashed FB21 ROM and modem and I was just fine. I'm not pushing my luck anymore though until this **** is figured out.
[Samsung Epic 4G Touch] skeet07:
Flashed from FB17 to FB21 and then FB21 to FB27 using the Rouge repack kernels without any problems. Wiped data (factory reset), dalvik, and /system each time.
[Samsung Epic 4G Touch] Kurupt1:
Exactly, doing this seems fine. Can't wait for fb27 repack cmonnn steady!:D
[Samsung Epic 4G Touch] iondokk:
For what it's worth.... If I'm on Ics and want to try a new version, I have been nandroiding my sig setup (would think any EL nandroid would work) after I test an ics build then boot, then back to recovery then flash new ics versions. No brixz. No yellow triangle! I also mobile Odin rouge kernel after flashing ROM and modem.

Hope this helps.

Samsung Epic Touch 4G

(ROM) XPLOD SE V0.2

(KERNEL) Rogue14

(THEME) NONE

(MOD) Madoggin- LS Mod

(MODEM) FB21
[Samsung Epic 4G Touch] dgn_sandibalz:
I never post in dev section. First and probably last since I know squat about developing.

The description above is a little different because you are flashing calks wipe. Whereas, from most of the posts I've read, most of our bricks happened when we attempted to use the recovery wipe option or factory reset. Especially when using the temporary touch recovery.

I have a feeling that the temp recovery sits on the data partition or thereabouts. It definitely doesn't sit where the normal recovery would or it wouldn't be temporary. I also think that the new linux base for ICS is handling the partitions a little differently.

So, when we select a factory wipe, or just try to wipe data, those small differences in temp touch recovery and linux base are corrupting the data partition and that only. When I was trying to get mine unbricked everything seemed to odin properly and the phone would turn on, and hang up at the black samsung screen. When booting into the recovery it would give the e: errors. Essentially stating that the data partition didn't exist.

I will say, I've never had an issue with rogue recoveries or cwm recoveries. Only the temp recovery. And even that only related to wipe data and factory reset. Otherwise it worked great.

You do some great work SH. I did fill out your survey on G+. I think there's some good conversation in here: http://xdaforums.com/showthread.php?t=1504808
[Samsung Epic 4G Touch] wbyrd:
This is exactly what I've done too, no problems for me either. Hopefully it stays that way!
[Samsung Epic 4G Touch] Dchibro:
I'd say this is a very good line of thought. But therein lies the problem with this kind of issue. Until the problem is specifically identified, even innocent trusted applications can get lumped in with the "problem" applications. There are so many variables involved, and people who've bricked often omit crucial details that could help narrow the problem to one or two possible root causes. Also, even with multiple reports of "hey i used Calk's format all and it worked fine" (like I did above) or "I did the standard wipes and no brick", you will still get those that say "well maybe you were lucky and it's just a matter of time", which continues to instill the shadow of doubt.

Still, as I said earlier, I highly highly doubt Steady was messing around with temp recoveries, so unless we hear more from him on what led to his brick, we can't exclusively link the corrupted data partitions to that alone. Now, if he was testing his work on a new touch recovery when he bricked, then that would help my mind rule out the stock kernel CWM repacks as being a potential problem.
[Samsung Epic 4G Touch] Steady Hawkin:
Here is the story fellas:

I was on CM9 Alpha4, and I was flashing our FB21 rev2 to pull some logs. I had flashed Alpha4 and our kernel about four or five times already without any kind of issue. For whatever reason the next time I went to reflash Alpha 4, I booted into recovery wiped cache and dalvik cache (as I had done four or five times already with the same recovery and rom build) and it just hung at installing update. It was at that time I knew my luck had run out. No Odin (including using the jig I have), no connection to ADB, no nothing, just the blue light of death.

These bricks are concerning for a variety of reasons. The biggest IMO, is that there does not seem to be a single constant. People are bricking on different recoveries, with different roms, with different scenarios each time. TBH at this point I have no idea what is causing it or where to even start. I will say it is possible that these stock kernels from Sammie could play a role in the chaos, but thats just a guess.

Bottom line is, playing with ICS before we have any sort of source is going to be a gamble. If you dont have insurance on your phone I would hold off. I'm going to continue to do my best to try and figure out what is going on, but I cant guarantee anything. With the help of the other dev's I hope we can get this situated so we can move forward. In the meantime Team Rogue will continue to play with fire in a quest to move development forward.
[Samsung Epic 4G Touch] klbjr:
Ok so I read through the last few pages of posts and I'm still confused on what is the best step to flash. I'm currently running MIJJz BLEND ICS v1.2 and want to flash up to v1.4 but scared of all of the brick stories and how not to flash from ICS to ICS, so just what is the proper or safest way?
[Samsung Epic 4G Touch] Dchibro:
Thank you very much for taking the time to report Steady. I think the critical part of your story that stands out to me is CM9. So far, I've seen these three components stand out the most to me in people that have reported bricks ...

1) ROM Manager/Temp Recovery

2) Touch Recovery

3) CM9

I'm not saying any one of these are specifically and solely responsible, just that I've read a ton of the brick threads and these seem to be involved most often. Obviously when it comes to Android flashing, it's important to know that doing A leads to B. When doing A leads to ?????, things get dicey.

I wish you the best in trying to narrow this down, although I'm doubtful we'll ever get a definitive answer. Hopefully the problem just dies away as we transition to ICS.
[Samsung Epic 4G Touch] kc_hubbard:
Hey man, you've probably already seen these, but there's a couple of good threads in the general section concerning these bricks where sfhub has been pretty involved. He has a theory on what the problem is but has to date not been able to correct any of the bricked phones. May take a look if you haven't already.

Crap, cant find the other thread right now...if I do, I'll post.

http://xdaforums.com/showthread.php?t=1509795
[Samsung Epic 4G Touch] FrameCityJackal:
Ha i think that flew over peoples heads

I guess tonights da night for steady to get dirty in this kernel lol
[Samsung Epic 4G Touch] mick3444:
So, Just to be clear.....When flashing with CM9 alpha 4, its safest to use the odin file?
[Samsung Epic 4G Touch] FrameCityJackal:
Yes go back to bone stock. IMO its best because technically CM9 is a whole different framework/files/ect and not TW. Thats why wipes are important if you have a file still installed from previous set up you can and will most likely brick ya ish
[Samsung Epic 4G Touch] Admiral2145:
Hopefully we can see a FB27 kernel for all the new roms... I really appreciate your work.
[Samsung Epic 4G Touch] shaolinmastr:
Can not get this file to Odin. It starts and then hangs up. Any ideas?
[Samsung Epic 4G Touch] Steady Hawkin:
FB27 is being tested. Assuming we find no issues we will likely release later today.
[Samsung Epic 4G Touch] lafester:
thanks steady!

would it be possible to release a version with stock cwm?

with all the problems people are having with cm9 it would be a nice addition :)
[Samsung Epic 4G Touch] agentfazexx:
YES!!!!!!!!!!!
[Samsung Epic 4G Touch] daniel4653:
Dude there is already a fb27 kernal with stock recovery.

Sent from self nominated team "Z" member's phone.
[Samsung Epic 4G Touch] lafester:
Dude I think you are confused.
[Samsung Epic 4G Touch] cjwaggsrx8:
Agreed
[Samsung Epic 4G Touch] daniel4653:
You said stock recovery. Not rouge recovery.

Sent from self nominated team "Z" member's phone.
[Samsung Epic 4G Touch] Steady Hawkin:
No, we will not be doing any repacks with pure stock CWR. If you want to use it on CM9 for now you will need to use Mobile Odin to flash.
[Samsung Epic 4G Touch] agentfazexx:
So to use CM9 with CWM, just flash the Odin tar once the FB27 repack is uploaded?
[Samsung Epic 4G Touch] lafester:
No problem never hurts to ask :)
[Samsung Epic 4G Touch] krazyflipj:
He said stock cwm recovery. There are 3 types of recoveries:

- Stock android Recovery: Recovery that comes with cm9. It only can flash gapps and official Samsung rom builds)

- stock cwm recovery: Recovery that Sbrissen recommends to flash cm9 (Found in CM7)

- Custom CWM recovery ex:Rogue, ACS, etc.

Can't wait for FB27 kernel to come out!

Sent from my Epic Galaxy S2
[Samsung Epic 4G Touch] BigJPNut:
Tried to flush fb21 rev 2 with mobile odin pro from market...still fc's after wiping cache/dalvik cache on cm9 alpha4. Same thing when I use odin pc. Will your new kernel be compatible with cm9? Meaning the same tweaks he includes with the included alpha4 kernel?
[Samsung Epic 4G Touch] Kurupt1:
Can't wait hope it is released tonight!
[Samsung Epic 4G Touch] Tibedabeeto:
Where do I find the link for EL29 rogue recovery tar? I just restored back to stock el29 and want to add recovery, but cant find it anywhere.
[Samsung Epic 4G Touch] musclehead84:
Look in the third post. All the older releases are there. There is the zip and tar.
[Samsung Epic 4G Touch] Tibedabeeto:
I don't know if it is just me, but those links don't work. I get to the Android file hosting site but after the 10 seconds go away it takes me to a page with random characters. Or if I click the link that says if it didn't direct me I get to a page not available. I tried on my computer as well as my phone.
[Samsung Epic 4G Touch] sfhub:
If you are seeing pages and pages of random characters, then that is the file, but your browser is displaying it instead of saving.

If it is just a single line of letters/numbers, then that is probably the md5 checksum and you've clicked on the wrong link thinking it was the link to the file.
[Samsung Epic 4G Touch] Tibedabeeto:
Its the whole file but just showing the characters on the page and not downloading. Any suggestions on how to get the file? Since it goes to a count down I can't right click and download.
[Samsung Epic 4G Touch] Tibedabeeto:
I tried in opera and it worked once I click the link twice. Thanks for everyone replies.
[Samsung Epic 4G Touch] BigJPNut:
Did you run into a problem with the FB27 kernel?
[Samsung Epic 4G Touch] Steady Hawkin:
Sorry for the delay guys, but it will be worth the wait. We now have bootanimation working on both CM9 and TW based ICS roms. Also fixed the issues we were having with flashing on top of CM9, which means Odin tar's and CWM zip's are good to go. We made some small changes to the recovery and we want to make sure its solid before its put out for public consumption.

At this point the only issues we have left are: notification lights are broken when you flash over CM9, and you still can not install apps on external sdcard (although you can access your external sdcard) on CM9. For the time being you will have to live with these. In the meantime we will continue to test, and shoot for a release tonight or tomorrow. Thanks for your patience!
[Samsung Epic 4G Touch] Vgamer4550:
Thanks for the effort, these 500 dollar toys are worth the wait :) I'ld rather have to wait on some apps installs then force it and not have any apps.
[Samsung Epic 4G Touch] agentfazexx:
So this CWM kernel will work on the CM9 ROM?

I heard a rumor somewhere that the CM9 ROM is known for bricking the E4GT?
[Samsung Epic 4G Touch] ElAguila:
Thanks for the work you are doing. And eventhough you didn't have to, thanks for dropping by and letting us know how things are going with the new kernel. Looking forward to it.
[Samsung Epic 4G Touch] MДЯCЦSДИT:
Can I include this in MIUI4? I don't own the phone but people say this kernel works best and I think it would be of my best interest to include this.
[Samsung Epic 4G Touch] MikeC84:
Might want to try and see if it works baked in the rom first. Saw this yesterday from Steady..

https://twitter.com/SteadyHawkin/statuses/176096275945627650
[Samsung Epic 4G Touch] Steady Hawkin:
Yes you can and thanks for asking :D

You will want to wait until we release the update to FB27 because it will include some bug fixes (see previous post here). Also, I can confirm the new build will work via flashing from desktop Odin, mobile Odin, and CWR zip on CM9 and TW based roms. Previous versions had issues via flashing from desktop Odin and CWR on CM9. Not sure if it will work on MIUI because I have not tested it.
[Samsung Epic 4G Touch] agentfazexx:
Sweet so were 100% compatible with CM9?
[Samsung Epic 4G Touch] MДЯCЦSДИT:
Miui==cm9
[Samsung Epic 4G Touch] odub303:
Come on man, do a little research before you say stuff like that. The CM9 ROM isn't bricking anything. It was functions in certain recoveries that was causing the bricks.
[Samsung Epic 4G Touch] agentfazexx:
Just repeating what I read... so flashing a bad recovery is what will brick it?
[Samsung Epic 4G Touch] MДЯCЦSДИT:
Recovery in general is broken on the epic touch cm9
[Samsung Epic 4G Touch] agentfazexx:
It is? Wouldn't flashing this just replace the recovery?
[Samsung Epic 4G Touch] barnacles10:
Bro, you've been teasin us since the drop of our first ICS leak. I check for a thread on the reg. Can we expect this soon or what?
[Samsung Epic 4G Touch] agentfazexx:
My PSU in my dev box went up. Waiting on the new one.
[Samsung Epic 4G Touch] barnacles10:
Ah of course. Darned PSU's..
[Samsung Epic 4G Touch] agentfazexx:
Had the PC for quite a while too. Kind of surprised it died.
[Samsung Epic 4G Touch] barnacles10:
They always seem to go out when you're working on something big.
[Samsung Epic 4G Touch] agentfazexx:
Trying to say I'm full of ****?
[Samsung Epic 4G Touch] lafester:
did you donate as instructed?

this will help speed things along :)
[Samsung Epic 4G Touch] barnacles10:
Just speaking generally.
[Samsung Epic 4G Touch] agentfazexx:
Hm alright then.
[Samsung Epic 4G Touch] sfhub:
We are all FoS until after we drink our coffee in the morning.
[Samsung Epic 4G Touch] Dchibro:
LOL what just happened here?
[Samsung Epic 4G Touch] BigJPNut:
Please post that link you read....i would like to read that myself.

---------- Post added at 09:59 PM ---------- Previous post was at 09:57 PM ----------

Hey steady does the new FB27 kernel for cm9 include the same tweaks as the kernel in the current cm9 alpha4 rom?
[Samsung Epic 4G Touch] toprock23:
No cwm recovery on fb27? No problem! I just flashed 1.6 on stock recovery. Mod wiped, flashed, and almost pissed my pants. It's working perfectly :) Thanks team noc.

*posted on wrong thread* my bad!
[Samsung Epic 4G Touch] Steady Hawkin:
Links are up. Please read OP and changelog.
[Samsung Epic 4G Touch] nibrwr:
Can I assume that the FB27 kernel works with AOKP since it works with CM9?

Thanks SH & Team Rogue
[Samsung Epic 4G Touch] repl1ca:
DO NOT FLASH. Odin locked up and will not flash the .tar

Had to Odin stock FB27 and start over

Tried twice same thing happened
[Samsung Epic 4G Touch] firket2000:
Any one else having this problem?
[Samsung Epic 4G Touch] odub303:
I flashed on cm9 with mobile odin, no problems thus far.
[Samsung Epic 4G Touch] LordJummy:
Thanks for the new repack!

About to mobile odin it into my Blend ICS goodness setup. I'll update this post if it's successful or not.

*UPDATE: flashed with mobile ODIN, no problems. New kernel working perfectly. Sweet!! Thank you so much
[Samsung Epic 4G Touch] rde34:
Odin'd back to fb21 rev2 and flashed through cwm. Everything works fine. So far camera and minor bugs appear to be fixed.
[Samsung Epic 4G Touch] maddness505:
anyone try the zip file in recovery yet?
[Samsung Epic 4G Touch] BigJPNut:
I flashed with odin pc...workrd perfectly on cm9 and AKOP....thanks steady....awsome work!
[Samsung Epic 4G Touch] rde34:
Yeah, worked fine.
[Samsung Epic 4G Touch] Vgamer4550:
Worked fine here using Standard Recovery...
[Samsung Epic 4G Touch] repl1ca:
idk, maybe bad download. I'm going to redownload the zip and flash zImage using autoroot