FORUMS

Analysis & Opinion

Top Forum Discussions

Android/Google admits to the eMMC bug

371 posts
Thanks Meter: 82
 
By sol_671, Senior Member on 19th May 2012, 01:38 PM
Post Reply Subscribe to Thread Email Thread
It's an article that I came across.

http://www.xda-developers.com/androi...d-ics-kernels/

If this article has been posted, sorry, Mods could delete this.
Sent from my SPH-D710 using Tapatalk 2
Last edited by sol_671; 19th May 2012 at 01:43 PM.
The Following 4 Users Say Thank You to sol_671 For This Useful Post: [ View ]
 
 
19th May 2012, 04:50 PM |#2  
Wizard Knight's Avatar
Senior Member
Flag Long Island, New York
Thanks Meter: 261
 
More
Its a non issue in my opinion. If you flash leaks, you know the chances. I flash the leaks and know o could end up with an epic doorstop. Long as its fixed when the official ota comes, it's cool

Sent from my SPH-D710 using Tapatalk 2
19th May 2012, 08:32 PM |#3  
scarmon25's Avatar
Senior Member
Flag Knoxville, TN
Thanks Meter: 2,175
 
Donate to Me
More
Nice article. Very informative. I personally never flash anything while on ICS. But based on that article that might not even be enough. It also gives us an idea that until Samsung/Google has fixed the issue we won'tbe sseeing an OTA updates. At least I would hope they wouldn't OTA an update that is going to brick a **** ton if devices.

I was victim of the superbrick towards the beginning. Whatever it did it really messed that thing up. If JTag can't repair it then it's hosed. Thanks for sharing.
19th May 2012, 10:25 PM |#4  
blackroseMD1's Avatar
Senior Member
Flag San Diego, CA
Thanks Meter: 439
 
More
It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.

Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.

On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.
The Following User Says Thank You to blackroseMD1 For This Useful Post: [ View ]
19th May 2012, 11:40 PM |#5  
HaiKaiDo's Avatar
Senior Member
Thanks Meter: 479
 
Donate to Me
More
Quote:
Originally Posted by blackroseMD1

It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.

Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.

On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.


Yep Sbrissen and entropy got this fixed. Ive used his 3.0 Kernel and flashed about a billion times to test it lol. Its awesome and brick proof :] I just hope people wait for sbrissens 3.0 to be finished before they starting "borrowing" from it and calling it their own -_-.
19th May 2012, 11:48 PM |#6  
garwynn's Avatar
Forum Moderator / Recognized Developer
Flag Chi-town
Thanks Meter: 8,206
 
Donate to Me
More
Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/show....php?t=1644364

Let's avoid hype on this, OK?
19th May 2012, 11:52 PM |#7  
HaiKaiDo's Avatar
Senior Member
Thanks Meter: 479
 
Donate to Me
More
Quote:
Originally Posted by garwynn

Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/show....php?t=1644364

Let's avoid hype on this, OK?

Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.
20th May 2012, 12:15 AM |#8  
garwynn's Avatar
Forum Moderator / Recognized Developer
Flag Chi-town
Thanks Meter: 8,206
 
Donate to Me
More
Quote:
Originally Posted by HaiKaiDo

Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.

My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.

Hope that clears up why I mentioned hype.

Sent from my SPH-D710 using XDA
20th May 2012, 12:25 AM |#9  
HaiKaiDo's Avatar
Senior Member
Thanks Meter: 479
 
Donate to Me
More
Quote:
Originally Posted by garwynn

My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.

Hope that clears up why I mentioned hype.

Sent from my SPH-D710 using XDA

Ahh yeah I got ya. I agree, I would much much rather see a fix and the knowledge that comes with it than seeing people get upset. I for one am happy to see things progressing and have no wish to blame anyone for anything. Even though it was a serious issue, we all take the risk of flashing things that are unknown upon ourselves.
20th May 2012, 12:41 AM |#10  
LudoGris's Avatar
Senior Member
Flag New Hampshire
Thanks Meter: 97
 
More
Quote:
Originally Posted by blackroseMD1

The fault here lies on both the person that flashed and on Sammy for their crappy code.

You're kidding me, right? Fault of Samsung? We are flashing ROMs that are for internal purposes only. They could introduce an unknown android virus or brick code just to test the response time of their workers, and if we flash it then it is soley our fault. I won't fault Samsung or any other company for our crazy obsessions or need to be on the cutting edge, download their internal projects, and put them on our fully functional devices before they have said to do so.

Now if they release it as official and it bricks the device it is exactly the opposite and 100% their fault, not the flasher.
The Following 5 Users Say Thank You to LudoGris For This Useful Post: [ View ]
20th May 2012, 01:16 AM |#11  
scarmon25's Avatar
Senior Member
Flag Knoxville, TN
Thanks Meter: 2,175
 
Donate to Me
More
Yeah. Anything other then official released software is on our heads. If I flash a leak and I brick my phone, which I did, then its my fault. I flashed Sbrissens CM9 back when he first released it. He sent me a test build. I flashed it. I bricked it. It was completely my fault. Wasn't Samsung or Sbrissens. Now if Samsung had officially released that file to the public and said oh yeah this is 100% safe to flash. Then maybe it would have been on them.

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes