[beerbong]

 Cita: Originalmente Escrito por LtsRacer

Las pruebas es que leas el solo te dice lo que se ha posteado

Gracias. No hace falta que me hagas leer. Llevo meses leyendo sobre el tema. Aporto pruebas:

De aquí: http://forum.xda-developers.com/show....php?t=1633943

 Cita:

Kernels that have been confirmed safe:
All known Gingerbread kernels for the Galaxy Note and other affected devices listed above
Kernels built from the GT-I9100 Update4 source code release - this includes XplodWILD's CM9 release and my DAFUQ release, hopefully more kernel choices will become available soon
Kernels that have had MMC_CAP_ERASE disabled in mshci.c should be safe, look for it in the listed features of the kernel - preliminary results are good, no bricks have been reported by anyone confirmed to be actually running such a kernel yet.

De aquí: http://forum.xda-developers.com/show...1672571&page=6

 Cita:

Q: Difference between GB/ICS Wipe

Originally Posted by Ken Sumrall (Android)
IIRC, when using recovery to wipe the phone on GB, the make_ext4fs() library would not issue an erase command first, it would just write one a new blank filesystem. This, of course, doesn't really erase all the private data of the user, so we changed make_ext4fs() to first erase the partition, then write out the new filesystem. You can see the code in system/extras/ext4_utils/wipe.c, which didn't exist in gingerbread, but does in honeycomb and later. It is the erase operation on the rev 0x19 firmware that can cause the emmc chip to lockup. (emphasis added)

Creo que dos posts, uno de Entropy512 (reconocido desarrollador de android y quien encontró el bug) y otro de Ken Sumrall (ingeniero de google/android, uno de los que encontró el bug en los prototipos del nexus) es más que suficiente para afirmar que los kernel de GB son seguros. Si necesitáis más pruebas sólo tenéis que decirlo. No me cuesta mucho buscarlas.

Y por favor no me mandéis más a leer, me paso el día leyendo unos cuantos foros de desarrollo en android