Every single one of these threads has someone in it that has memory related issues (corruption, file disappearing, or straight up bricking), and none of them flashed the wrong rom. This is just the past months' worth, I don't feel like going back any further. As someone who came from a device that was absolutely RIDDEN with bricking issues (the Sprint Epic Touch 4g), I've done the research and can tell you this seems JUST like the stuff people see when dealing with this same issue.
I don't get it, why are people getting so damn defensive about this? Brick your devices, I guess I don't really care, we're just trying to help. It's something worth thinking about.
Every single one of these threads has someone in it that has memory related issues (corruption, file disappearing, or straight up bricking), and none of them flashed the wrong rom. This is just the past months' worth, I don't feel like going back any further. As someone who came from a device that was absolutely RIDDEN with bricking issues (the Sprint Epic Touch 4g), I've done the research and can tell you this seems JUST like the stuff people see when dealing with this same issue.
I don't get it, why are people getting so damn defensive about this? Brick your devices, I guess I don't really care, we're just trying to help. It's something worth thinking about.
Those are all related to either known issues or GB roms?
Non Touch recovery has been known to cause bootloops but bootloops are not bricks.
okay, point taken, but again, theres literally no harm in knowing things, and it's a pretty safe thing for this issue to be looked into instead of written off.
okay, point taken, but again, theres literally no harm in knowing things, and it's a pretty safe thing for this issue to be looked into instead of written off.
TDJ seemed to have looked into why the touch recovery was causing bootloops so it hasnt been written off but it hasnt panned out as bricking devices. These possible brick issues where the reason why some devs where careful at first but now all devs seem to be working with ICS bases so the looking into has happened. However currently it seems the amount of bricks is equivalent for ICS as GB (The amount of GB bricks on your posts make it seem like GB might even have an edge).
TDJ seemed to have looked into why the touch recovery was causing bootloops so it hasnt been written off but it hasnt panned out as bricking devices. These possible brick issues where the reason why some devs where careful at first but now all devs seem to be working with ICS bases so the looking into has happened. However currently it seems the amount of bricks is equivalent for ICS as GB (The amount of GB bricks on your posts make it seem like GB might even have an edge).
Had to thank you for the post, glad to see people agreeing on stuff. That's kind of why I made this thread, so everyone can be on the same page as to where our device stands in the ICS brick "scare".
So, my phone has the firmware revision "0x25". If you follow the instructions there, you can see that this firmware has a KERNEL level fix going on, but thats only for ICS kernels:
Quote:
We now have an update on why this bug is happening and which PRV/fwrevs are affected. PRV/fwrev 0x19 are susceptible to the EMMC /data corruption issue (which should now be referred to as EMMC lockup issue). PRV/fwrev 0x25 has the fix for the lockup issue but has a separate 32KB of zeros data corruption issue, which is being patched in the kernel (our kernels don't have that patch). All these problems are in the EMMC firmware. It can potentially be updated, but nothing is publicly available. EMMC lockup issue is triggered on erasing the EMMC. The only piece we have not been able to explain is why GB-based kernels seem immune to the EMMC lockup problem whereas ICS seems more susceptible to the problem. Presumably both are doing ERASE commands, but possibly in slightly different ways. See these posts for more details [#1 / #2]
So, I'm not sure what devices and what firmwares everyone is running, but if what I'm reading is correct, there are scenarios in both firmwares that could potentially cause a brick. Regardless of firmware, there are EMMC firmware bugs in these chips across multiple firmwares. This is why I feel the need to have some extra caution, and perhaps this is why there seems to be more GB related bricks rather than ICS related bricks for our devices; the 'fix' that samsung issued for the 0x25 firmwares was recently checked in, meaning its in the ICS kernels.
Based on this info, I think I'm going to wait until the next ICS leak specific to our device before I erase anything in any recovery. Obviously, that's just me though.
Ever since the introduction of multi-window with things like Cornerstone and … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
ICS Leaks Causing Bricks?! Updated With More Info.(New Link)
Print
Email
View Profile
View Forum Posts
Follow on Google+
Follow on Twitter
Linear Mode
