[WARNING] Samsung 4.0.4 firmwares (Official / Leaked) may lead to HARDBRICK

Search This thread

jebuchanan

Senior Member
May 10, 2012
870
773
Root it, use a safe kernel, enjoy.

Sent from my Samsung GT-i9100M
ROM Dilidroid UHLPS
Kernel Siyah 4.15
 

-iNCEPTiON-

Senior Member
Apr 29, 2011
1,482
521
Islamabad
I have a safe problem .. I am on 4.0.4 , how can i avoid bricking my phone ... :) plz help .. M glad i saw this thread before i rooted my phone ...thanks

Sent from my GT-I9100 using xda app-developers app

Anyone?

I have actually downloaded CF-Root For LPH But it says it has problems mounting SDCard partition, so i am confused about it... i have downloaded Siyah kernel , so i wanted to ask that if i flash Siyah kernel , i would have root access ?? i just want to get rid of some stupid apps i have on stock ICS 4.0.4 :(
 

Mittaa

Senior Member
Jan 18, 2009
1,960
531
Anyone?

I have actually downloaded CF-Root For LPH But it says it has problems mounting SDCard partition, so i am confused about it... i have downloaded Siyah kernel , so i wanted to ask that if i flash Siyah kernel , i would have root access ?? i just want to get rid of some stupid apps i have on stock ICS 4.0.4 :(

Flash Siyah then your rooted and can get rid of your stupid apps ... and besides that you are safe from the nasty, ugly, bugly brick bug :)
 

Pooshkis

Member
May 15, 2009
12
0
Plese, need help, tried to downgrade firmware from 4.0.4 to 4.0.3 using Odin and now i'm getting an error: android.process.acore has stopped, and can't really do anything.
is there anything I could do now or is my phone bricked?

Thanks in advance!
 

Mittaa

Senior Member
Jan 18, 2009
1,960
531
Plese, need help, tried to downgrade firmware from 4.0.4 to 4.0.3 using Odin and now i'm getting an error: android.process.acore has stopped, and can't really do anything.
is there anything I could do now or is my phone bricked?

Thanks in advance!

Have you tried using Odin PC ?
 

-iNCEPTiON-

Senior Member
Apr 29, 2011
1,482
521
Islamabad
Flash Siyah then your rooted and can get rid of your stupid apps ... and besides that you are safe from the nasty, ugly, bugly brick bug :)

i am trying to flash SiyahKernel 5.0.1 (Latest Version) and tried 4.1.5 also but odin is giving me error saying that cannot open serial port :( and says FAILED :(

Kindly HElp .. i have tried changing the ports too
 

Reno29

Member
Oct 31, 2012
49
8
Anyone knows a 4.0.4 safe kernel? Or maybe a list, I'm running XWLPY and this problem worried me.

Enviado desde mi GT-I9100 usando Tapatalk 2
 

radx

Senior Member
Jun 22, 2008
90
15
I have a emmc bricked S2 here. Has there been any development on this where you can fix it somehow?

I've read this post (I dont understand everything):
http://xdaforums.com/showthread.php?t=1667886

And this:
http://xdaforums.com/showthread.php?t=1900612

The state of my phone is that it's completely dead. I cant get odin to recognize it. It wont wake up when I plug in a usb-jig.. Nothing wakes the screen up. Any help would be very appreciated.
 

Pooshkis

Member
May 15, 2009
12
0
I have a emmc bricked S2 here. Has there been any development on this where you can fix it somehow?

I've read this post (I dont understand everything):
http://xdaforums.com/showthread.php?t=1667886

And this:
http://xdaforums.com/showthread.php?t=1900612

The state of my phone is that it's completely dead. I cant get odin to recognize it. It wont wake up when I plug in a usb-jig.. Nothing wakes the screen up. Any help would be very appreciated.

don't know if i am exactly right, but I've red somewhere that the only thing you can do now is to change phone's hardware (some kind of micro scheme, maybe processor or smth).
 
Last edited:

radx

Senior Member
Jun 22, 2008
90
15
don't know if i am exactly right, but I've red somewhere that the only thing you can do now is to change phone's hardware (some kind of micro scheme, maybe processor or smth).

Thanks for replying. I did some digging around and from what I understand I need to reprogram the EMMC chip with a Riff Box. In some cases a new emmc chip is required. Either way, this is out of my league. I will try to get it repaired at a service shop. Thanks for replying though :)
 

gabohXD

Member
Oct 4, 2010
5
0
Hello xda-community, I'm a new user to this samsung devices so I have a long way to go with this...
I have some experience just with flashing custom rooms and rooting Motorola devices and a Dream G1, but samsung is just a new world to me so I hope someone can give me a little help here...
This is a little info of my device:
Samsung Galaxy S2 (GT-I9100)
Android official firmware 4.0.4 (Updated through the normal way by receiving the update from the company, I'm from Argentina)

(I never flashed a kernel so I don't know if this data is relevant):
This is what it says in Kernel Version:
3.0. 15-1133289
se.infra@SEP-129 #3
SMP PREEMPT Fri Oct 5 11:21:08 KST 2012

Baseband version:
I9100UHLPH

Compilation number:
IMM76D.UHLPZ

My "problem" here is that I want to Root it. I have read some guides in many places and some guides here but I'm still kind of confused with the kernel-flashing thing and stuff. I don't know how to know if a kernel or anything that I can download from the attachments in the guides will work with my device.
Please can anyone, by knowing this data from my cellphone, re-direct me to the proper guide for me?
Also, if you could tell me what would be best for my phone.. like if I should stay with the Stock rom or install a Custom one... I don't know if this is the best but I think I want to conserve the Official Firmware and just add the Root thing..
Any tip with this would be really appreciated. Thanks in advance!
 
Last edited:

seres88

Member
Nov 8, 2012
39
2
This my screen shot from got brickbugs? apps. Its shown my emmc chips got a brick bug. So, how to solve this and remove all brickbugs inside my chips. Any guide?

thanks for helping.

Sent from my GT-I9100 using xda premium
 

Attachments

  • uploadfromtaptalk1353228415828.jpg
    uploadfromtaptalk1353228415828.jpg
    19.4 KB · Views: 279

ghadap

Senior Member
Now I'm screwed a bit.. at Sam, it says 4.0.3.. when I done flashing, it shows 4.0.4.. Moral of the story; don't root yet+wipe anything+don't do anything.. Maybe i'll just wait for official 4.1.2? :silly:

Edit : Is it compulsory to "wipe data" when flash using Odin? I flashed my device with this ROM; I9100DXLPF_I9100OLBLPF_XME, from sammobile. It says 4.0.3, but turns out after flashing it, actually is 4.0.4 (About Phone properties).

Im not 100% sure. Is it safe for me to do this steps?

1) With Odin, I flash other official rom from sammobile (I9100DXLPB_I9100OLBLPA_XME or
I9100DXLP9_I9100OLBLP9_XME), without wipe anything..

2) If the flashing process successful, I just continue use it since data is still intact.

Sent from my Thoughts using Telepathy :banghead:
 

Reno29

Member
Oct 31, 2012
49
8
Just install siyah kernel via ODIN ,after that you can flash another Rom, or stay the same. Remember the problem is in the kernel, not in the rom

Enviado desde mi GT-I9100 usando Tapatalk 2
 

darknagel

Senior Member
Mar 27, 2012
331
61
29
Sylt
OnePlus 8 Pro

t4ure4n

Senior Member
Nov 4, 2009
269
25
London
Need advise for upgrade from Android 2.3.3 to 4.1.2

I understand that its the bug with stock kernel and not the ROM

I want to update my wife's SGS2 which is currently running
Code:
[B]Android Version[/B]: 2.3.3
[B]Baseband Version:[/B]  I9100XXKE7
[B]Kernel Version:[/B] 2.6.35.7-I9100XWKF3-CL276555 root@DELL101 #2
to [ROM][4.1.2][AOKP/CM/PA] GT-I9100/I9100P Vanilla RootBox [12/11][v3.2][Nightlies] with Dorimanx Kernel and I9100XXLQ6 Moden

Can you please advise me what will be the correct procedure for achieving this with risking a brickbug.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 201
    To all of i9100 users having flashed the latest 4.0.4 firmware (Official / Leaked) with stock kernel, PLEASE BE AWARE that using cwm to erase data/factory reset OR to restore a nandroid backup MAY BRICK YOUR PHONE !!!! Trust me, I just got mine bricked and by searching a litlle bit I discovered I'm not the only one -> see here and here ... and the number is growing ...

    Actually confirmed firmwares having the emmc bug :
    XXLQ5/6/7/B - ZCLPL - XWLPM/O/T/U - MUGLD3‎(?)


    Here's how to BRICK your phone :
    -Flash the 4.0.4 firmware with/without its pit file
    -Use any 4.0.4 based kernel - stock or modified (ex cf-root)
    -Go to cwm and do a wipe data & wipe cache and/or perform a nandroid restore of any previous firmware
    => The process begins normally but it may/will switch off at any time without waking up ever again !!!!!

    Symptoms of 4.0.4 HARDBRICK :
    -Phone dead
    -No power up
    -No boot
    -No download mode (odin mode)
    -No charging (usb/ac)
    -Not detectable by pc / jtag
    -Usb jig & jtag useless
    -With battery(charged) inserted, phone(off) gets hot near the camera lens
    -JUST A PIECE OF PLASTIC !!!!
    -You feel really stupid about trying all this new stuff


    And now here's how to avoid 4.0.4 hardbrick :
    -DO NOT flash any stock 4.0.4 firmware ;)
    -If on 4.0.4 stock firmware, keep away from stock kernel (ex: use siyah kernel or latest speedmod)
    -Use "eMMC Brickbug Check" app to verify whether you have an insane ship or not
    -Backup your apps (titanium backup) and backup all (cwm) and copy all data from internal sdcard
    -DO NOT wipe any partition or data
    -Flash any official 4.0.3 stock firmware in download mode via odin (do not use mobile odin)
    -Do not get tempted again by any unsafe leaked or official firmware !!!


    Downgrade from 4.0.4 :
    -Reboot the phone in download mode (Home+Vol.Down+Power)
    -Use Odin to flash a safe kernel (ex. siyah) then reboot to cwm (Home+Vol.Up+Power)
    -Optionally do a nandroid backup then perform a data wipe/factory reset
    -Use advanced menu in cwm to reboot in download mode to flash your preferred "safe" firmware


    While waiting for someone to find a way to revive such bricked phones, I hope you guys take care of your precious S2, you only know its value when it's gone ;)
    9
    You can find so many good customized firmware compilations out there :). But because of so many asking for a safe all-in-one stock package I decided to share my stock ROM variant.

    I've repackaged the stock GT-I9100 XWLQ2 firmware with CSC NEELP6 and hardcore's SpeedMod K3-32 kernel and the old GB jig-resettable bootloader ready to flash via Odin thus beeing pure stock (no theme no root no nothing) but safe because hardcore disabled MMC_CAP_ERASE functionality in his kernel. The jig-resettable bootloader will do it's job to get rid of the yellow triangle too ;) . This package works fine for me. It is non-wipe.


    Flash it via PC Odin WITHOUT doing any wipe before (for safety reasons regardless what version you're coming from). After you've finished installation, you can do any wipe in SpeedMod kernel's included CWM. And of cause: DO YOUR BACKUPS before you try this package, I'm not responsible for any inconvenience ...

    • If you like: After installing the firmware package you can root it flashing this SU-BB-Tweaks-XWLQ2-signed.zip from internal or external SD-Card via CWM. It contains ChainsDD's SuperUser.apk 3.1.3 and BusyBox 1.20.2 plus some minor tweaks (battery indicator, emo icons).

    On request: the original XWLQ2 bootloader is here if someone wants to flash it in favor of the provided old GB jig-resettable one. Doing so won't increase your digital binary counter but will require another solution (Chainfire's Triangle Away) if you need to reset the counter in the future.

    25.11.2012:
    Updated stock ROM XWLQ2 with CSC NEELP6 and SpeedMod kernel K3-32. Also updated original bootloader and SU/Busybox zip package to XWLQ2.

    28.10.2012:
    Updated stock ROM XWLPY with CSC NEELP6 and SpeedMod kernel K3-32.

    20.10.2012:
    Updated stock ROM XWLPY with CSC NEELP5 and SpeedMod kernel K3-31. Also updated original bootloader to XWLPY. New: added SU/Busybox zip package to be flashed via CWM.

    07.09.2012:
    Updated stock ROM XWLPX with CSC NEELP5 and SpeedMod kernel K3-31. Also updated original bootloader to XWLPX.

    26.08.2012:
    Updated stock ROM XWLPU with CSC NEELP5 and SpeedMod kernel K3-31. Also updated original bootloader to XWLPU.

    09.08.2012:
    hardcore released SpeedMod kernel K3-31 I'm using for two days now. I updated my custom package with the new kernel today.
    5
    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 ;)
    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.
    4
    what was the story youve sold to service center ???


    Samsung and Google are well aware of this issue since May and are working on a fix since, but as they said fix is being developed and needs extensive testing and who knows how long could it take

    so as much your initiative is ok ... it is completley useless as Samsung is well aware of chips that they ordered and witch of those are affected.
    got also all the information on what causes this issue - now they just need to develop a stable working fix and push it public

    or maybe they did their numbers and it came out that percent of the devices/mb/chips affected is ok to just handle it via service center repairs

    oh, and they well know that it is a isue wit stock samung recovery or whatever you call it - the one that comes with firmware - so your source is hmm wierd :)

    ---------- Post added at 05:11 PM ---------- Previous post was at 05:01 PM ----------

    ref -> plus.google.com/111398485184813224730/posts/21pTYfTsCkB
    Well, you're apparently quite clueless, since the contacts at Samsung referenced in that post ARE the ones I'm talking to.

    And no, they are NOT aware that people are suffering damage in stock recovery. They believe that it is totally safe, and have asked me to try and find devices that have suffered damage from stock recovery for analysis. I've passed 3 reports to them so far, but if there are two reports of stock XWLPM doing damage, that's more evidence that nonsecure erase isn't as safe as they think it is.

    Also, XXLQ5 is evidence that they, unfortunately, have not been working as hard on the fix as claimed... I've indicated to my contacts that the XDA community is extremely disappointed with this recent development. We were told one thing back in May, but the results with XXLQ5 are the exact opposite - instead of having fixes deployed, a previously safe device has been put in danger.
    4
    Ok but folks: what about the solution.... Is the affected chip version 0x19 upgradeable by software to 0x25 which is supposed to have the issue addressed? This is what I wish to know if is even possible

    Sent from my GT-I9100 using Tapatalk 2

    Possible? Yes, however the process fully wipes the chip. In addition, Samsung considers that information to be even more proprietary than the reset-without-upgrade sequence, which alone is proving difficult to get.

    The underlying bug can be rendered a non-issue by protecting the chip from ever seeing dangerous commands (which is why I9100 kernels previous to this one were safe). I am extremely disappointed in Samsung in that they claimed to be working on deploying a fix for this issue, but took a previously unaffected device and added the trigger conditions to its kernel.