• 5,596,706
  • 44,294

Workaround for SGS2 Owners with Soft Bricks after LQ5

Workaround for SGS2 Owners with Soft Bricks after LQ5

As of late, the Samsung Galaxy S II I9100 has been running into some problems. Not only is there a hard brick bug from a leaked kernel that no one should ever flash, but the bug affects many users differently. Some may be hard bricked, while others may only be soft bricked. There are many users who’ve already flashed the kernel and don’t know how to get rid of it. All in all, the LQ5 leak is quite dangerous.

The problem is a little complicated. When users flash the LQ5 leak from Samsung, they are flashing a kernel that has a hard brick bug. The bug is activated upon attempting to flash anything from recovery and from performing a factory reset. Basically, don’t wipe, format, or flash anything. For more info, XDA Developer Admin and Elite Recognized Developer pulser_g2 has written up an important announcement accessible from the link above. If you have not already gotten bricked in some way from it, there is also instructions on how to safely flash away from it.

For those who were fortunate enough to get only a soft brick out of it, XDA Forum Member d.fx may have a solution for you. Keep in mind that this will not work for hard bricked devices. For those that have only been soft bricked, d.fx’s solution is likely your best option. Luckily, the process is not complicated. Users are directed to flash a modified PIT file via Odin to the device. The hope is to create a new data partition. As d.fx explains:

What you need to do if you’re in the same situtation i was into (make sure of it) is to flash a modified pit file which is gonna create a new data partition on your internal sdcard, leaving the faulty one aside, and thus getting a brand new data partition which is gonna make your phone work again, but at the cost of having a smaller internal SD. Other than that, your phone should work exactly as it did.

After flashing the PIT file, users are instructed to flash a purely stock image via Odin to restore functionality to the phone. Afterward, users are to perform a factory reset. When it’s all said and done, the Galaxy S II should be back to proper working order except the internal storage will have less space, as the corrupted data partition will never be recovered. It won’t solve the majority of the problems, as the majority get hard bricked. Even for soft bricked users, the workaround may only be temporary. As XDA Elite Recognized Developer Entropy512 explains:

The way to think of it is: When eMMC damage occurs, usually the partition that is wiped and regions of the chip immediately adjacent to it get damaged.

If you repartition such that the damaged region is not used, you may be able to restore operation. However, if you do another wipe, you may crater an additional chunk of the chip. Also, it is unknown how the wear leveller will behave as the undamaged space is used – it may interact negatively with the damaged regions over time. Many users who have implemented repartitioning workarounds indicated that their phone acted strangely for a while, and I believe some experienced more severe failures over time.

For additional details and download links, go to the original thread.

Want something on the XDA Portal? Send us a tip!

XDA TV: Most Recent Video

Buy/Sell on Swappa