yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] rafflax:
I upgraded from 4.0.3 to 4.0.4 and it was fine. The new firmware worked better than the previous one. Then, I decided to downgrade to 4.0.3 spanish version and it's already perfect, though the performing of the phone was better with the 4.0.4.
[Galaxy S II General] ioglnx:
Did you used Odin 1.85?

I flashed also the 4.0.4 Firmware fom Sammobile in Odin 3.04 it gave me an error in 1.85 Odin it flashed just fine.

I'm running the 4.0.4 LQ5 since it was out - but now I want to go to Cyanogenmod 9.

So I have to flash first the 4.0.3 ICS Smasung Offical to then flash CM9? Is there a guide to get back from LQ5 (4.0.4) to 4.0.3?

And how do I get in the recovery mode I just know how to get in the Download mode with Volume+Home and Power button is this the recovery mode?

Thanks for answering
[Galaxy S II General] ali jamali:
hi

i have 2 S2 with ICS 4.0.4 LQ5

first 1 with 32GB in emmc

I use pc Odin to flash it without pit file

and iroot it by Stock_LQ5-CWM kernal

in emmc check i get

the Second one with 16gb in emmc

I use pc Odin to flash it without pit file

no root no use other kernal

in emmc check i get

------------------------------------------

no i need to know wo i can back to the 4.0.3

without HARDBRICK my phones

without died my phones

sorry for my bad English

and please help me
[Galaxy S II General] rafflax:
To go back to 4.0.3 you only have to flash the rom you choose (at least It's what I did choosing the spanish version). Recovery mode access is pushing volume up+home+power

You lose memory when you flash the pit file. There is information about that.
[Galaxy S II General] cpl.Bower:
Just flash ARO, and dont EVER erase/wipe the cache with CWM and you will be fine
[Galaxy S II General] retrorom:
Thanks OP for this useful information. I am running Paranoid Android 1.6a at the moment, guess I'll rather stick to this 4.0.4 :D
[Galaxy S II General] idpro:
is there any way to repair that, mine bricked too 2 days ago by xwlpm :(
[Galaxy S II General] hawkn:
Ok, how nice, I called the repair center my self, and because I've changed the housing myself (perfectly performed) they would not fix/replace my phone.

They won't even try, so I've just ordered myself a jtag adapter, molex port, new soldering iron, soldering wire and a few other small things, cost 64GBP = 75USD, MUCH cheaper than buying a new phone so I'm giving it a shot, if I fail, well, I have a new soldering iron, thin soldering wire and a few other items I've needed, but have not ordered until now :) and yeah, If it fails, I think I might go for a S3 as sec. phone as well :)
[Galaxy S II General] karendar:
Holy crap dude, you are funny! Even if you're the smartest person alive, your post count is proportional to your contributions to the forum. Entropy512's contributions to the SGS2 community is far superior than most "Recognized contributors" and his post and thank count shows it. The fact you keep on arguing with him when you obviously do not know anything about MMC_CAP_ERASE and what it truly does, nor do you even know that LQ5 was leaked, then officially pushed through Kies and that there are possible issues with stock recovery is appaling, sad and comical.

XDA is all about taking risks to get what you want out of your phone. It's not because it's a noob infested territory that it brings more "pain" to the user phone experience. It's because people who lack the skills and knowledge try and do things they are not qualified for. Have you ever tried to fix an appliance you were not qualified for? Instructions are available everywhere to do it, if you choose to do it, it's your own fault if you fail miserably and trash your appliance. Same applies to phones.

Entropy512 IS working with Samsung to feed them on the matter, wether you like it or not. And he was part of the original MMC_CAP_ERASE issue when update5 source dropped and effectively bricked many phones. If Samsung enabled something by mishap in their kernel, stock CAN brick the phone because of a partition formatting. You bring nothing concrete to the conversation except saying LQ5 is a Godsend. No valid arguments, no constructive criticism, just plain fanboyism about a ROM that has possibly caused issues with people.

And what about the reports from the official Russian 4.0.4 build that bricks have occured? Was that a leak? No?

Sit down, my friend and watch the parade go by while you play with XXLQ5. In the meantime, some people have work to do.
[Galaxy S II General] Prufrock:
Much as I loved the fluidity of this new firmware, I've gone back to 4.0.3, as this just kills my battery. Flashed back using Odin and normal stock firmware, then restored with my nandroid back up. Oh, well.....sorry to all those who bricked their devices. :(
[Galaxy S II General] Entropy512:
Currently, almost surely your attempt will fail, but I'm really hoping we'll get the information to change this soon. HOWEVER - if you get indications the JTAG adapter did at least connect and boot your phone, please send me a PM. I may require the assistance of yourself and others who are capable of JTAG recovery if I receive the documentation I'm supposed to receive in a week and a half.
[Galaxy S II General] hawkn:
Well, I know for a fact that my riffbox DOES fix these kind of problems :)

A while ago I flashed my old HTC Desire Z and it was epic, flashed radio over bootloader and at the same time I made the mistake of repartitioning the device, a complete brick was very much there.

After that point I could not get bootloader, fastboot, recovery or anything, the phone was stone cold and dead, after appr. 30 minutes with my riffbox and some updates, the phone was reset with correct partitioning, bootloader, radio etc. and I'm still using it as a sec phone :)
[Galaxy S II General] renansalgado:
First, sorry for my English, I am Brazilian.

I need help.

I installed the leaked rom LQ5 with the pit file recommended by this post: http://xdaforums.com/showthread.php?t=1751529

and root: http://downloadandroidrom.com/file/GalaxyS2/kernels/ICS/CFRoot

How do I go back to 4.03 safely?

I do not understand about the kernel, and wanted to return to the original kernel.

The ROM I used before: I9100VJLP7_I9100ZTOLP4_ZTO (4.03 Brazil)
[Galaxy S II General] josuemf:
are they playing a prank on us?

how come that hard resetting and flashing a new kernel, leads to a bricked phone?

WTF?!
[Galaxy S II General] jaykay0079:
I installed LQ5 and was running great had really good battery life.. after reading posts I decided to move back to CM9. I just had stock kernal with just busybox and superuser install to get root access.

1) Flashed Stock Sammy Rom 4.0.3 via odin 1.85

2) After that phone got booted fine but got lots of FC's.

3) Did factory wipe/reset via 3 button combo.

4) Installed latest SiyahKernel-S2-v3.3.3c. via odin.

5) Flashed CM9 latest nightly.

6) Did wipe cache/dalvik cache/fix permission

7) Booted fine into CM9 and did the restore via Titanium Backup.

Happy days... :-)

Hope it helps....
[Galaxy S II General] ali jamali:
Thank you my first phone Successfully back from 4.0.4 to 4.0.3 and after it i back to 2.3.5 :laugh:

but i have other phone wirh 4.0.4 and emmc check say my phone have insane chip and i get brick bug

what i can do to back to 4,0,3 Successful without get HARD BRICK ??

emmc check screen-shot

sorry for my bad English again
[Galaxy S II General] Entropy512:
JTAG can't recover from this damage - the eMMC chip is in la-la-land, certain regions of it are so trashed that any attempt to read or write them will make it lock up until power is cycled.

However the process I've been told will wipe the chip clean of damage will also wipe it clean of bootloaders - JTAG CAN recover from that at least.

There's a low-level bug in the eMMC chip that gives it a chance of choking and becoming severely corrupted if an ERASE command is sent to it.

Secure erase (CWM) has a very high likelihood of damage

Nonsecure erase (stock recovery) has a much lower, but not zero as the evidence over the past week has shown, likelihood of damage. Samsung believes it is zero, but the evidence we're all seeing says otherwise - and in a situation like this, where the price of being wrong is so high and the benefits of being right are so little - why take the risk?
[Galaxy S II General] cpl.Bower:
Do the same that you did with you other phone and remember DONT wipe or factory reset with CWM.
[Galaxy S II General] hawkn:
My thought was to use riffbox to clear everything on the chip, the whole partition layout and such, then repartition the chip, install bootloader etc.

I wrote earlier that I'm able to tart the phone in recovery mode, only all I see onscreen is the s2 logo, but adb kinda works, it auto-reboots after appr. 3-4 minutes.

But I'm able to start several utils trought adb such as parted.

Only thing is that the phone hangs and reboots a minute later :P

If, and I say IF, it is just a corrupted partition table, and not phycial errors, it should be possible to recover from this error with jtag and nand wr directly, my experience with the riffbox is that It doesn't use recovery mode or download mode, it reads/writes the nand/emmc directly.

I found a video on youtube where they recovered a s2 with emmc bug, but lame ass me forgot to save the link, this is why I orderd a molex port, jtag adapter and such.

But off course, correct me if I'm wrong and you can prove something else ;)
[Galaxy S II General] Entropy512:
If you've suffered from the Superbrick bug due to wiping on an affected kernel, it is not a corrupted partition table. It's low-level damage to the internal structures of the eMMC chip that is well known to be unrecoverable via JTAG. (Josh at mobiletechvideos.com apparently gets 3-5 devices damaged like this per day - he can't repair them.)

From the perspective of the CPU, the chip has a large chunk of physical damage to a memory region that is close to the partition that was wiped in size and location. (So wiping data usually leaves a bootable device, wiping /system will often hit the bootloader with "splash damage".) Any attempt to touch those regions will hang it.

The good news is that it isn't really physical damage even though it behaves like physical damage - it's such low-level data corruption that the methods for repairing it are not part of the JEDEC eMMC standard - they're Samsung vendor-specific commands which are currently undocumented. The hope is that in a week and a half, I will be receiving documentation on these commands from the Samsung engineers I'm meeting with.
[Galaxy S II General] hawkn:
So what you are saying, is that in near future it might be able to fix this with a flash from DM or jtag with the commands you refer to ? :cyclops:
[Galaxy S II General] karendar:
And maybe, HOPEFULLY, find a solution to corner the bug and maybe even repair it for good.
[Galaxy S II General] ali jamali:
OK thank you my friend i try it tomorrow

after i back to 4.0.3 can i wipe by CWM ?
[Galaxy S II General] Black Coffee:
Am a victim too, but got it fixed for free from near by Samsung Service centre.. They changed the dead motherboard !! ;)
[Galaxy S II General] cpl.Bower:
Only with 4.0.3. You could try also this code (with the phone) : *#87976633#
[Galaxy S II General] ali jamali:
so you mean

i can wipe in 4.0.3 by CWM or by this code *#87976633#

if i back to 2.3.5 after i back to 4.0.3

and do wipe cash and data with stock kernel

nothing will be happen such as hard-brick ??
[Galaxy S II General] WandersonGD:
Man this ROM is a brick mess..
[Galaxy S II General] hawkn:
I think I'm just caling it 200USD or so for a new motherboard, easy and the I can repair the old mb if a fix appears.

Will follow this issue all way.

EDIT: So, the seller I found tells me the same every time I ask for shipping costs, if I ask something or tells something, same answer every time.

He wants me so send him my bricked MB, the I can order a new one for 135USD incl. shipping.

Does not sound serious to me, so continuing with bricked phone for now, I HATE THIS !

Did not find a used MB anywhere else than ebay, only people buying them :silly:
[Galaxy S II General] cpl.Bower:
Dont mess with 4.0.4

Yes, you can use CWM or that code.

Exactly.

The thing here is, if you wipe/factory reset with 4.0.4 and CWM, in that case it will brick your phone.
[Galaxy S II General] moshxsoft:
sorry for my english :)

do you mean we can fix our devices that hard bricked with lq5? even it won't turn on, just black screen?

i sent Josh (mobiletechvideos.com) and told him about this problem and my device is hard bricked with CWM and after reset factory and won't turn on after that, and he told "Unfortunately this is a dead EMMC FLASH chip. You will need to locate another mainboard pulled from a working phone to swap into it.".
[Galaxy S II General] bombaybadboy:
I have sgs2 and been trying to make sure i didnt have brickbug, its only a few weeks old and eMMC check came back No sane chip but when i tried the gotbrickbug apk it didnt reconize my chip. Is it possible that eMMC check results might not fully reconize chip or is this a good result
[Galaxy S II General] Vihru:
i take my phone to service center and now they mailed me that my display is broken...

and i have same situation that i was make factory reset in CWM when my phone shutdown..

so what you say to this? i mean how can display been broken? :D

everyone has motherboard?
[Galaxy S II General] DaReDeViL:
So here I am again. I just got my S2 fixed (mb changed) for approx 100€ (used mb !). They tried every jtag box with no success. Now i had to upgrade it to XWLPG via odin then used cm9 resurrection to avoid cwm wipe and flashed the latest build, because i still have an insane chip....
[Galaxy S II General] moshxsoft:
very expensive man.

tomorrow my device i will take it from service center, i don't know how much cost me?
[Galaxy S II General] Red_Vex:
XWLPG is 4.0.3 that does not contain wipe bug.
[Galaxy S II General] karendar:
Your input on the matter is of major importance! We thank you for your intervention, as none of us knew this! ;)

Re-read what he wrote: His S2 was fixed, flashed to LPG to get his phone working, BUT his chip has the brick bug still, so he's not going back to LQ5.
[Galaxy S II General] DaReDeViL:
Hehehe never ever again !!! A 100€ lesson ;)
[Galaxy S II General] khrone:
Yet to be bricked, have a bad chip so i guess ill stick with LPG for now and wait for a good release of 4.0.4 before moving... might not work to say at samsung customer service that "tried the leak and managed to stay away from bricking so could you guys fix my chip just incase" :D Still got warranty left on my phone if i odin a stock firmware in
[Galaxy S II General] TheCreat:
I have the same chip, it's also a very new phone (about a week old in my case, shipped with ICS already). Another person posted somewhere (also with this chip) who got it when he recently got his motherboard replaced. So I'm assuming (!) that this is a new charge of chips and that I'm bug-free. This is pure speculation of course, and I'm surely not gonna risk anything by flashing something potentially dangerous.

It would be nice to get an official confirmation (or denial) on these chips though...

I assume there is no (safe) way to test the chips?

Swyped on my Galaxy S2
[Galaxy S II General] Vihru:
you many have got motherboard broken with this leaked firmware..

but service center mailed that my display is broken :D

so i dont think so that firmware can broke my display? O_O
[Galaxy S II General] fs1023:
Got my repaired phone back from bricked LQ5 state. For you guys who know what this means repair report said:

"The main printed circuit board, that control's your handset's functionality was found to be faulty"

Hope this might help the devs etc in some way

Regards

fs1023
[Galaxy S II General] moshxsoft:
are you change the motheroard?
[Galaxy S II General] fs1023:
I assume the PCB was replaced seeing it was faulty but do not know for sure.
[Galaxy S II General] imsad:
my phone working with xxq5. root with cwm 5.6. stock xxq5 kernel. no brick.
[Galaxy S II General] cpl.Bower:
That means, they changed your mb because the emmc bug and the bootloop because of the CWM (shouldnt we sue those guys? :laugh: ) and wipe with it.
[Galaxy S II General] zokimk79:
I have leaked LQ5, rooted with latest CF Root 5.6. Little change on TW launcher with default homescreen and appzorter.

It works so smooth and i like it. Its really better then 4.0.3.

If i dont touch CWM, wipe, flash..etc, should i need to worry about brick?
[Galaxy S II General] bombaybadboy:
In other words they dont know so they just replaced mb, if you have a look at the service manual they have a precise guide and when all fails they just replace mb
[Galaxy S II General] Ramzi619:
How do I change the Kernel? (YES IM A NOOB)

I'm on 4.0.4 XXLQ5 and my kernel is 3.0.15-i9100XXLPQ-CL753921

se.infra@sep-83 #3

SMP PREEMPT

It's all mumbo jumbo to me :/
[Galaxy S II General] meromero:
firmwares LPM and LQ5 brick the GS2 or only the LQ5 brick GS2 ??? Sorry for my Bad English jajaja
[Galaxy S II General] Entropy512:
XWLPM and XXLQ5 are both dangerous.

Please use full build codes including region in the future when talking about firmware releases.
[Galaxy S II General] tufoz:
hi guys..

i flashed 4.0.4 leaked..then i tried to go back to 4.0.3 via CWM..

now i can enter in download mode.. and flash via Odin..but..after flashing on "pda" an official firmware..the phone doesn't boot.. it freezes on the black screen with the logo of SGS2.. what can i do?
[Galaxy S II General] meromero:
thanks and sorry for no specific region in my question
[Galaxy S II General] pendroz:
+1
[Galaxy S II General] iNeri:
lol. That's right, after 8 days in Samsung service try to figure out at the end they just replace the mb :p

Send your devise to service center for motherboard change or flash a modified pit file whit the cost of losing a few gb of your sd card

Enviado desde mi GT-I9100 usando Tapatalk 2
[Galaxy S II General] Gen s2:
Fix?

try an older bootlaoder?

flash back to 4.0.4 > backup if needed > full wipe > odin flash to offical 4.0.3.

my method fixed it for me ^

I had this same problem with CWM using official carriers ROM or Official ROM since 4.0.3 if using CWM free or premium.
[Galaxy S II General] 43358005:
many thanks for the heads up!
[Galaxy S II General] cubic:
You can try to repair your bricked phone according to this manual http://xdaforums.com/showthread.php?t=1760107
[Galaxy S II General] hawkn:
Did not work for me, tried every single pit file I came over, stock, custom etc. total brick.:(

Thanks for the effort though :fingers-crossed:
[Galaxy S II General] bkjugg:
I've download an app "eMMC Brickbug check" and under "brick bug?" it shows "YES. Insane chip." What does it mean?

sry for engl :)
[Galaxy S II General] dabenaute:
brick bug

:)

Hello,

That's mean,if you use CWM for "wipe data/factory reset";you can brick your phone(some people say:HARDBRICK);)
[Galaxy S II General] ant987:
I tried too the "got brick bug?" application and it says: DANGER! tHIS eMMC chip is *KNOWN* to have the brick bug!

However since I bought the phone in Semptember 2011 I flashed a thousand of roms both GB and ICS with cf-root/siyah/speedmod kernels and performed wipes and never had a problem! I just discovered yesterday through the app that I have the brick bug! So what should I do now?! Should I stop flashing custom ROMs? I don't think I will be able, is like a drug for me :(
[Galaxy S II General] :
I think u should read at least last 10 pages of this thread.
[Galaxy S II General] burtallicus:
i have the same messages but the test pass? also flashed and wipe many times before
[Galaxy S II General] sandeepsivia:
i am unable to wipe data /factory

plz help me

now i am on xxlpq(4.0.3) and rooted but still unable to wipe data any way to wipe and factory reset

help help
[Galaxy S II General] adamsuail:
Thanks to the poster for the heads up but its too late for me, my phone is on the way to mobile tech videos for the Jtag repair....am using a 10$ old nokia and i dont want to look at it :crying:
[Galaxy S II General] moshxsoft:
hard bricked or soft??

in other words your phone can turn on or not?
[Galaxy S II General] Net.silb:
One more heads up:

Your phone will be sent back to you not fixed because jtag does not work in these cases, the only solution is replacing the motherboard..

I've also bricked my phone like this and I've decided to just buy an S3..

Good luck though!
[Galaxy S II General] crazy_4_and1:
To get one thing straight ( and don't answer if you are not sure or if you are just assuming the answer , because I use logic too , but it might not be enough to come to the right conclusion and might lead someone into HARD-BRICK ) . . .

If you are on a risky kernel (or the whole ROM for that matter) and have the 0x19 revision of eMMC chip :

1. Is it safe to flash a stock , non-leaked ROM with that is known to be safe ( without emmc_cap_erase function enabled ) via ODIN ,

2. and after that to flash a custom kernel with CWM recovery preinstalled (also "safe" - emmc_cap_erase function disabled )

3. Do a data/cache/system format via that CWM recovery ? ? ?

My logic is that even if you have a defective chip ,you cannot brick your device if you format data/cache/system via CWM recovery from a kernel that does not have the emmc_cap_erase function enabled - like CM9 kernels .

So basically is it safe to flash a stock ROM via ODIN , than a "safe" kernel (CM9 or Chainfires one that has emmc_cap_erase disabled ) and then format data/cache/system ?

---------- Post added at 12:59 PM ---------- Previous post was at 12:53 PM ----------

Can you boot your phone , can you go to download mode or to the recovery ?I have not read that XXLPQ is flagged as dangerous .

Read the post from Entropy512 on this page and you will get the answers to most of the questions . I essence , most of the i9100 are affected and potentially brickable . You bypass that by using safe kernels which cannot trigger the corruption of eMMC chip . Permanent solution is being discussed but it looks like it is going to be difficult to implement for the regular user in DIY conditions. Link to the page with Entropy512 post : http://xdaforums.com/showthread.php?t=1693704&highlight=xxlpq&page=24
[Galaxy S II General] planetf1:
On a related topic I'm considering

- backing up phone with CWM (on BULPD with Siyah 3.3.3d)

- upgrading to XXLPM via mobile Odin (with everroot enabled)

- including specifying a custom CSC

- not installing any alternate recovery (I only use recovery to restore)

In normal use this should be fine. I SHOULD NOT do a factory reset though.

I do not explicitly select to format cache etc

if I needed to reset *OR RESTORE A BACKUP* I should either

- install a custom kernel such as siyah which "mostly works" on 4.0.4, boot into cwm, and then do reset/restore

- or flash a 4.0.3 rom which is more safe (say stock BULPD) and then do factory reset from there

Is that correct?

Any differences using PC odin?

Or mobile odin 3?
[Galaxy S II General] adamsuail:
i wish it was a soft bricked, i would have fixed it myself, its Hard bricked...not powering on at all.
[Galaxy S II General] thorazine74:
I'm no expert but i think your logic is right, as long as the kernel has no mmc cap erase flag all operations should be safe.

However i think cfroot kernels are just stock+ root+cwm so they would keep the dangerous flag as long as the original stock kernel they are based on had it, which its believed to be the case with LQ5 & LPM. However it seems he patched CWM somehow in his latest LQ5 cfroot to not trigger the dangerous erase operation. I haven't confirmed this myself though so i would use a known safe cwm like CM9s.

Sent from MyToasterOven using SmokeSignals
[Galaxy S II General] adamsuail:
Their YouTube video showed the exact same cause/ symptoms, plus all the feedback is promising , so am really optimistic Josh Groce will be able to fix it, my shipment is international so it's going to take at least 10 days from now....i will definitely report back to help the others.

the repair costed me 84$ , do you think replacing the motherboard would have been cheaper?