yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] pizz0wn3d:
Is anyone else having this issue? More importantly, has anyone else solved this problem? I've searched (as effectively as I can via mobile) and found a thread or two discussing it, but no one seems to have a solution.

Regardless of the ROM, it seems that a lot of apps immediately FC when I open them after restoring their data. Installing the app by itself works fine, but the moment I attempt to restore the data I get the FCs.

It's quite infuriating really, as it's preventing me from trying any MIUI ROMs because I can't get them to boot without doing a data wipe (no, I won't run a ROM without my apps' data, sorry)

Checking and unchecking the "follow all symbolic links" option hasn't worked either.

Basically, HALP!

Herp derp Captivate Tapatalk 2
[Captivate Q&A, Help & Troubleshooting] pizz0wn3d:
So... I'm the only one with this problem?

Herp derp Captivate Tapatalk 2
[Captivate Q&A, Help & Troubleshooting] RootTheMachine:
I only had this problem because I was using a datafix script and didn't have the symbolic links option checked. I lost all my data because of this. Now would be a good time to check if my new backups even work...

EDIT: They work fine... Maybe try deleting all of yours and doing it again, and have symbolic links checked.
[Captivate Q&A, Help & Troubleshooting] pizz0wn3d:
Sorry I never replied, I had a response typed out and never posted it =/

My problem seems to have disappeared after coming back to SimplyAOKP from my nandroid. I don't actually use a datafix script.

Here's what prompted me to post this:

I wanted to try out the port of Andy's MIUI v4, so I wiped all of my backups and made new ones (didn't check the symbolic links option before backup) as well as a nandroid. After flashing MIUI, I'd say about half of my apps worked fine. The rest FC'd immediately. Now that I'm back on SimplyAOKP, the backups work fine =/

After thinking about it, I realized that I usually move my larger apps to the SD, and never did that on MIUI. So in the end, the FCs mightve come from my datadata partition being full (I never checked, just figured it was the same old backup problem and nandroided back) . If the problem resurfaces, I'll post back here and hope for the best.

Herp derp Captivate Tapatalk 2
[Xperia Play Q&A, Help & Troubleshooting] Deleted member 4493700:
Is it possible to make the screenshot apk from the verizon 2.3.4 update work on 2.3.3? I have the apk for it
[T-Mobile Samsung Galaxy S II SGH-T989] singlebyte:
Not sure why this isn't posted on a top sticky thread. This is a serious issue. Just thought I would bring it over.

http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/

http://xdaforums.com/showthread.php?t=1698977
[T-Mobile Samsung Galaxy S II SGH-T989] singlebyte:
You can check to see if your chip is currently one of the risks. Download gotbrickbug and just run the app. My GS2 does have the issue.....so I am going to hold off flashing ICS (custom wipes/kernels) until Sammy comes up with a fix.

http://xdaforums.com/showthread.php?t=1693704
[T-Mobile Samsung Galaxy S II SGH-T989] Saxysaxplayer:
Scratch that, it DOES... wow, I thought it was only Exynos versions.
[T-Mobile Samsung Galaxy S II SGH-T989] daveid:
Mine says it is probably safe.
[T-Mobile Samsung Galaxy S II SGH-T989] xUnreachablex:
I have one of the chips known to have this fault and was trying to figure out how I haven't bricked yet considering I've flashed a few roms based off the samsung ICS leak.

I'm assuming it's because I only use Darkside:superwipe (which doesn't touch emmc) to wipe and not those included in recovery. This make sense to anyone else or am I talking out of my a**?
[T-Mobile Samsung Galaxy S II SGH-T989] flipq88:
Dam mine says its bad too

Sent from Flip's SGS2

What im wondering is why hasn't it bricked yet. I flashed a bunch of different ics roms and back to gb with no problems
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
You havn't bricked because the brick only happens if you flash with an ICS kernel based recover and or ICS based updater binary.

All out current recoveries are GB based kernels with GB based updater binaries. so fare these have been deemed safe. there are patches that will be deployed with the ICS kernel source to workaround/fix this issue and make flashing with ICS based bits safe.

I have to admit guys i'm getting jaded with all this fear mongering and posting of OMG BRICK AAAAGHHH! when no one is reading into the issue fully and there for promoting fear and disorder. I see a lot of people freaking out about this lately but none have read the whole situation to see that currently your pretty safe with the recovery and update zips we have now.

Any bricks that have occurred because of flashing recently were not triggered by this bug, there was a bad fstab entry causing people to brick when partitioning or wiping sd-ext (don't know why people were wiping that any how we don't use or need it) as the recoveries we have been using to not meet the emmc corruption bricking requirements. From the research of Entropy, it appears its a bug causes by the way the 3.0 kernel sends the erase command to the emmc which fires off 32kb of corruption to the emmc causing it to crap the bed. this can also be caused but an update binary or ext4_utils binary that have been compiled by ics source as well. the solution to this will to be to disable MMC_CAP_ERASE in the 3.0 kernel so it is not used at all and just prints out a warning when something try to call it.
[T-Mobile Samsung Galaxy S II SGH-T989] thedark1337:
i have 0x25. So does that mean i am actually safe or am i going to brick somehow?
[T-Mobile Samsung Galaxy S II SGH-T989] LoopDoGG79:
Dude, are you f'n kidding!? Read Mr. X's post, the man just dropped some knowledge!!

Sent from the Darkside, ICS style
[T-Mobile Samsung Galaxy S II SGH-T989] Octane70:
So as far as i read, only the older TWRP 2.1.2 recovery was compiled from from an ICS kernel

correct?? so thats the one you want to stay away from??
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
0x25 is supposed to be "safe" with samsugns new patch set they are deploying in new builds, from what i understand from Enthropy512's postings

no 2.1.2 had an issue with fstab that caused sd-ext to be mounted to sbl2 so ifyou wiped sd-ext you bricked.

twrp are all GB kernel based as far as i know speaking with Dees_Troy
[T-Mobile Samsung Galaxy S II SGH-T989] Mafioso:
Wow thanks for the information, I have twrp 2.1.2 installed. It was so far working fine. Glad I didn't do a wipe from it. :D

I will change it ASAP

BTW too bad no one ported 4ext on this device yet, its has the best UI :(
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
you're fine unless you wipe sd-ext. otherwise update to 2.1.8 it removes sd-ext wiping and options
[T-Mobile Samsung Galaxy S II SGH-T989] Octane70:
X, i am using AOKP. whitehawkx baked the new telus kernel into it, I flashed using TWRP 2.1.8. I do have a brick bug, I am a little confused, do you think i am safe in this stuation?
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
your fine twrp 2.1.8 is gingerbread based kernel so it will not cause the issues to be put in motion that will corrupt the emmc
[T-Mobile Samsung Galaxy S II SGH-T989] Octane70:
Thanks for the answer X, appreciate it. So from what you wrote before, its not actually the rom kernel combo that bricking, it is the rom recovery combo? correct?.

So as long as your using a recovery based on GB kernel, you ae able to flash any ics rom kernel combo??, i hope i explained this properly.

Thanks again.
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
its just the recovery that can cause bricks if its based on the 3.0 kernel. its nothing to do with the roms.
[T-Mobile Samsung Galaxy S II SGH-T989] lolrus101:
I feel really lucky to have the 0x25 :D but just to clear things up do I have to stock and then go to UVLDE like everyone else?

Sent from my Galaxy S II
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
Oh god. This
[T-Mobile Samsung Galaxy S II SGH-T989] scott7175:
Do you recommend going back to stock picking up the lde
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
Why would i?

Here is the problem, ive explained how the brickign works at LEASt 10 times now in different threads and people still ask if they should flash to stock and panic and say OMG I MAY BRICK WHILE IM ALREADY FLASHED TO A ROM!!!?!?!?!

Please do this for me, what do you think flashing back to stock will accomplish and how will this protect you? given what i have already explain in this tread and how the brick bug works?

I really need to know why people keep asking this question.

Did you read any of this?

If you had, you would see the risk of bricking is only when you flash a rom from a recovery that is based off the 3.0 ics kernel that has not been patched to fix this bug. What part of this, that i have explained sparks the question that you should flash back to stock or that it will make you protected from a brick that ONLY happens when flashing in these circumstances?

People, READ. come one guys. I'm now past the point of sympathetic explanation because people are not reading and now on to full blown annoyment
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
I would give up. You cant undo weeks of hysteria with a few posts.
[T-Mobile Samsung Galaxy S II SGH-T989] LoopDoGG79:
Oh God what? That Mr.X perfectly explained why you should not trip about the brick bug, or that you lack the ability to understand what Mr.X said?

Sent from the Darkside, ICS style
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
i think im going to have a stroke soon.
[T-Mobile Samsung Galaxy S II SGH-T989] Towle:
NO! Source is coming soon! :p
[T-Mobile Samsung Galaxy S II SGH-T989] -Mr. X-:
If i die avenge my death lol
[T-Mobile Samsung Galaxy S II SGH-T989] akashptl:
I rarely post, but I felt it should be know I really admire you patience with these people!
[T-Mobile Samsung Galaxy S II SGH-T989] anomy13:
If OP could please quote this on the first page, first post, it will save Mr. X a lot of headaches!! :D:D:D:D
[T-Mobile Samsung Galaxy S II SGH-T989] scott7175:
Sorry mr x normally I read through before I post but I had a case of the f* ck its today
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
I was agreeing with him, chicken little much.

In the internet people use "this" when they agree with a post.
[T-Mobile Samsung Galaxy S II SGH-T989] xile6:
Ill do it let me just make a hit list lol.

But ya idk why people dont get it. Its not hard.

Simple. Of you flash any rom from an ics recovery you will get briked because the ics recovery will say delete this folder , which it thinks is another folder and bam your bricked.

Bit if your recovery is made under gb then all is good because it wont tell it to delete the wrong folder.

Thats pretty much it in a nut shell right?

Ics recovery uses the wrong delete comman bricking phone with the bug.

Gb recovery uses normal delete comman NOT bricking.
[T-Mobile Samsung Galaxy S II SGH-T989] pio_masaki:
So close... But no. Separate issues, and your combining twrps sd-ext deleting the wrong thing with emmc ics command issue.

Tapatalked from my Galaxy S II.
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
Here is the take away point although many people should have realized from not observing unwarranted bricks.
[T-Mobile Samsung Galaxy S II SGH-T989] pio_masaki:
+ 1. I was concerned yes but I hadn't bricked doing what I was doing, and I kept doing it that way.. I ran twrp the entire time and updated when the "fixed" version came out. Randomly freaking out and flashing again to not get bricked by...... flashing.... makes no sense to me. If bricking is so terrifying you shouldn't be flashing at all, it's always a potential outcome.

Tapatalked from my Galaxy S II.
[T-Mobile Samsung Galaxy S II SGH-T989] LoopDoGG79:
My bad, misunderstood. I'm probably getting to old for the internet. :p

Sent from the Darkside, ICS style
[T-Mobile Samsung Galaxy S II SGH-T989] LoopDoGG79:
Mr X, you have said only recovery's that are ICS based are the ones that can cause this bug. CWM and TWRP are safe. I have never heard if any other recovery's. Which recovery's can cause this?

Sent from the Darkside, ICS style
[T-Mobile Samsung Galaxy S II SGH-T989] jim93:
The recovery on a completely stock ICS phone like the new s2 in a few weeks when they come equipped with ICS or if the s3 chip suffers from this bug the s3 unless it was fixed.

---------- Post added at 07:37 PM ---------- Previous post was at 07:36 PM ----------

I figured possibly a misunderstanding but quoting with a "this" in agreement is so common I thought you would be current with internet lingo.moving on time.
[T-Mobile Samsung Galaxy S II SGH-T989] AznDud333:
cwm 5.0.2.7 isnt based off the ics kernel is it? ty in advance
[T-Mobile Samsung Galaxy S II SGH-T989] cubanb95:
Damn wish I knew about this a couple months ago before I bricked my first T989...is there a way to repair Samsung phones already hard bricked?
[T-Mobile Samsung Galaxy S II SGH-T989] Khizar:
none of the current t989 recoveries(cwm touch/nontouch and twrp) are based on ics kernel. they are all using gb kernels
[T-Mobile Samsung Galaxy S II SGH-T989] coraldayton:
All I'm hearing out of these people who can't read is "BLAH BLAH BLAH, I LOVE JUSTIN BIEBER".

Thanks for the info, Mr. X. Next time I'm in Ontario, I'll buy you a beer (:
[AT&T Samsung Galaxy S II SGH-I777] simplicityy:
I just received 2 batteries for the I-777 that I bought on eBay. However, they do not have NFC. For the hell of it, I double checked and tried turning on NFC in the settings and it said "error occurred". So I'm like yeah okay, figures. So I pop in the original battery (NFC capable) I was using and tried turning it on, and it was still not working. I'm on ICScrewed 2.1 with Siyah's last up-to-date GB kernel. Re-flashing didn't work. Help?

Stuff I've tried:

Wiping/Re-flashing

Back to stock, re-rooting, reflashing (was sure this would have fixed it...)
[AT&T Samsung Galaxy S II SGH-I777] gsrrr:
Did you try a wipe before reflashing?
[AT&T Samsung Galaxy S II SGH-I777] simplicityy:
Yes, I always wipe before flashing.
[AT&T Samsung Galaxy S II SGH-I777] MotoMudder77:
Maybe a ROM that isnt outdated, and not supported anymore.
[AT&T Samsung Galaxy S II SGH-I777] simplicityy:
I've been on ICScrewed 2.1 for a while, and the NFC always worked. The problem barely started when I put in a non-NFC capable battery.
[AT&T Samsung Galaxy S II SGH-I777] clay101eve:
Have you tried flashing anything else to see if the issue remained on other roms?

Clay
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
You're assuming people actually try and troubleshoot their problems for more than 10 minutes and search and read before posting here. Most don't.
[AT&T Samsung Galaxy S II SGH-I777] simplicityy:
Yes, I flashed back to stock. Problem still there.

Again, troll some more.
[AT&T Samsung Galaxy S II SGH-I777] clay101eve:
Labeling people as "trolls" won't get you help around here. Especially when they are the guys with most of the answers!

Keep searching, Google, xda forums, everywhere. Sometimes the answers are in obscure places. It's a pain in the ass, especially xda's search function, but it's worth the time. You may or may not find your solution but learn something helpful in the process. Right now I've screwed up supercharging my phone... Now im frantically looking for ways to fix without flashing. Butt im not going to ask for help until I know I have searched my ass off.

Clay
[AT&T Samsung Galaxy S II SGH-I777] simplicityy:
Keep kissing ass to your friends. Phalanx doesn't help. Look at his answer. Absolutely nothing to do with the OP. Instead, he's insulting me by saying I haven't searched, when I have. Not to mention, he does that in every thread I made. I'm pretty sure such behavior is trolling.

Anyway, like I said. I did search. All people have said is: pull battery out and put it back in, reflash (wiping of course too), and going back to complete stock and re-rooting and flashing. None of those have worked. See, you people assume I haven't searched, but I have...

Apparently, there was a flashable zip to fix this, but it was for a different phone when I was looking on Google.
[AT&T Samsung Galaxy S II SGH-I777] clay101eve:
All I can say is include everything you've tried in the OP. If you come across anything, make an update in the thread or an edit to the post, whichever is easier for you.

It took 2 people asking a question to get that you had tried two other possible fixes and they failed. Do you go to the doctor and tell him your head hurts but leave out the part where you damn near knocked yourself out working under the sink? No, you tell him everything you can think if that may have caused the issue in the first place.

No trolling, no judgment and for damn sure no kissing ass (see the thread where I pissed of Shoman). Just a normal guy trying to help ya out a bit.

Clay
[AT&T Samsung Galaxy S II SGH-I777] simplicityy:
You have a point with including all the info. But either way, why "thank" Phalanx for his useless post?
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Geez guys lol. Simplicity . My post wasn't aimed at u. However looking at it now i can see how u could take it that way. I was just making a general statement about a lot of the people that don't search for their answers . I apologize if u took it the wrong way. Good luck all, happy flashing.
[AT&T Samsung Galaxy S II SGH-I777] big_boludo:
What brand were the batteries so we know to never buy them?
[AT&T Samsung Galaxy S II SGH-I777] simplicityy:
http://www.ebay.com/itm/38039943412...X:IT&_trksid=p3984.m1439.l2649#ht_2564wt_1163

:l
[AT&T Samsung Galaxy S II SGH-I777] Divine_Madcat:
Final warning for everyone....

If you have a problem with another user, take it to the mods.. Do not continue a thread you feel violates rules. Report it, and move on...
[XPERIA X8 Q&A, Help & Troubleshooting] pipi14:
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
[XPERIA X8 Q&A, Help & Troubleshooting] BlackRabbit1703:
baseband

Sony Ericsson Xperia X8

Model number: (e15i)

Firmware version 2.1-update1

Baseband version M76XX-TSNCJOLYM-53404006

Kernel version 2.6.29 SEMCUser@SEMCHost#1

Build number 2.1.1.A.0.6

remember!

for upgrading your phone baseband must -015

1. maybe you can flash your baseband into 015, i.e X8i_2.1.1.A.0.6_Baseband_015

try to find ond gingerDX media fire file

2. or flash into X8 E15i 2.1.1.C.0.0._un.. you can find on google or 4shared

klick Thanks if I help you :D:D
[XPERIA X8 Q&A, Help & Troubleshooting] IHawkeyI:
I think the problem is with unlocking the bootloader. I am not sure but did you unlock the bootloader. If so , maybe you did it the wrong way, try to use the s1tool and read carefully all the warnings and instructions..
[XPERIA X8 Q&A, Help & Troubleshooting] mman1982:
question

Hi soft33!

Did you ever solved the problem? I am in the same trouble...
[Android Q&A, Help & Troubleshooting] Phelin:
Guys, is there any mods / way where you can enable weather widget on cm7 lock screen? And wanted to know how to set live wallpaper on lock screen...

any help?
[HTC One S] syntropic:
I don't know when this really happened, but it was a few days ago.

[Btw, I have not installed the update, and am rooted.]

Whenever I am on wifi using data (which seems to work pretty well ironically), my SMS ability completely breaks. When I try to send, I get an Ashley that says something like "message not sent, will send as soon as service becomes available"

Again, this only happens on wifi....below is a SC of logcat. You can see the errors apart on the bottom half of the screen

View attachment 1116634

Can anyone guess what happened? I don't think I deleted anything I wasn't supposed to...typically removing bloatware which others had already signed off on as safe.

I really do not want to factory reset or even flash my newly rooted nandroid backup from 3 weeks ago.... So any guesses are encouraged...

Syntropic

Sent from my HTC One-S (rooted), stock ROM
[HTC One S] strker45:
Make sure you have ipservice, ipprovider, and ims service installed as well as the stock messaging app.
[HTC One S] syntropic:
Yeah I double checked those things. They are there. And the result messaging app as well. But dammit this is something to do with the OS. I uninstalled GoSms, and had no luck with the default app.

When I reboot, it works fine for about 10 minutes, then crashes again... Don't know what it could be.

Maybe I need a better log viewer.

Sent from my HTC One-S (rooted), stock ROM
[HTC One S] syntropic:
On that note... Does anyone have a log viewer they recommend? I think aLogcat was lacking... Now I am using Log Viewer (the one with the pig head icon). It's better by far, but I figured I would check to see what others used.

Any suggestions?

Sent from my HTC One-S (rooted), stock ROM
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Clode:
Hi is there a way to change the double home button press App and bluetooth button.

I like to replace the Samsung voice recognitition voice with cyberon voice commander. Because Samsung ones is too too slow!

Thanks.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Clode:
mhhh. no help??

thanks anyway!
[HTC One X] MO3iusONE:
So I'm loving the phone but I feel like its too much for me. I had been using an iPhone 4 and a nexus s while in Korea. I'm currently in Germany and I was tempted by this phone. I was actually gonna return it but I guess there's no return policy with telekom in Germany? Any who, I might actually go back to the nexus s as a daily driver or even a droid pro then have the one x as my weekend phone. I blame apple for making me use to that tiny 3.5 inch screen lol
[HTC One X] LuffyPSP:
lolz... try use it a bit more. you'll get use to it.. you will feel uncomfortable to be back to smaller screen.
[HTC One X] norpan111:
Did you accidentally write here instead of your blog or something?
[HTC One X] hello00:
lols
[HTC One X] LuffyPSP:
Deserved a Thanks from me!
[HTC One X] MO3iusONE:
Ya know... After reading that it did read like something I should ha even posted on tumblr. Lol my bad
[HTC One X] Johnny0906:
Haha priceless ;)

I think if you are going to have a phone with several cores and so many features and basically act as a mini- computer then you should have a screen this size, this is just perfect not more or less just perfect and the 720p display is siiiiiiiiick :D

Cheers
[HTC One X] MO3iusONE:
Yea this phone being a power house was the selling point for me. The last phone I owned that was similar in size was the HTC evo which was a few years ago.
[HTC One X] LuffyPSP:
then stick with it man. :D
[HTC One X] GuestK00105:
I went from wildfire( small) to

Nexus one( middle) to this.

I thought the screen was to big at first but now I'm not having a phone that's smaller again!
[HTC One X] AJerman:
Haha, I've been going bigger and bigger too, each time saying it's big enough. iPhone (3.5"), SGS (4.0"), Infuse (4.5") and now the One X (4.7").

I remember when they announced the Dell Streak 5 and I thought 5" was ridiculous for a phone. Now that'd be a barely noticeable bump in size over the One X.

But at the same time, with the power these phones have, I've come to rely on my phone for a whole lot, and the extra real estate is very nice. The thinness makes it not seem so big. Plus with the bigger screen and 720p, it's actually not too bad to watch short shows or movies on.
[HTC One X] Nit3m4re:
I have to agree that originally having the phone, I started to find myself thinking it is far too big. However after nearly a month, I can't help but look at it thinking yes, this is the best sized phone ever. Its sick.
[HTC One X] BenPope:
I remember when phones were getting smaller. Does that make me old? :rolleyes:
[HTC One X] norpan111:
I do to! I used to envy those rich kids who could afford that little tiny Nokia phone...can't remember the name of it thou..now, hox and sgs3 was the only option because of screensize xD

Edit : this!
[HTC One X] muamers:
Its a 8200 if i remember :D That was a phone hahaha ... im not sure i could do anything with it anymore (or i would probably lost it every 5 min) ...
[HTC One X] Goku80:
norpan111 surprised to see you here buddy. you got yourself a one x?