Ana Menü Android Telefon Yazılım Rom Destek Teknoloji Sitesi

xda'de sabit konular arasında gözden kaçmış olabilir.
   
   Linklerin Görülmesine İzin Verilmiyor Üye ol Veya Giriş Yap
   
   DO NOT FLASH OR WIPE USING ANY ICS LEAK REPACK
   
   These kernels are fundamentally dangerous. Samsung introduced some sort of bug in the eMMC driver that can permanently damage the eMMC flash storage of the phone. This leads to unusable partitions at best, and at worst a hardbricked device. The nature of the failure is so severe that the usual method for hardbrick recovery (JTAG) is unable to recover devices damaged in this manner.
   
   Kernels that have been confirmed affected are:
   All ICS leaks for the Samsung Epic 4G Touch (SPH-D710)
   All ICS leaks for the Samsung Galaxy Note (GT-N7000)
   UCLD3 ICS leak for the AT&T Samsung Galaxy S II (SGH-I777) - Other leaks may also be affected
   Kernels built using the most recent SHW-M250S/K/L official source code release as of May 3, 2012 - This includes SiyahKernel 3.1rc6 for GT-I9100 (all other Siyah releases are safe)
   
   Damage is not guaranteed - it may only affect a small percentage of users, but even a 5% chance is far more dangerous than the effectively 0% chance of hardbricking due to kernel bugs in safe kernels.
   
   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
   
   If you are running an affected kernel:
   STOP USING IT IMMEDIATELY. FLASH A SAFE KERNEL USING ODIN/HEIMDALL.
   DO NOT wipe in recovery
   DO NOT flash anything else in recovery
   In general, DO NOT use recovery at all
   
   Right now, what we know:
   Some people can wipe with affected kernels as often as they want without problems. Just because you didn't brick, DO NOT advise other users that they will be OK.
   Based on reports from the Epic 4G Touch community, some people can wipe/flash 20-30 times before hardbricking - Just because you didn't brick once, DO NOT continue flashing with an affected kernel
   The source of the problem is somewhere within the changes between I9100 Update4 and SHW-M250S Update5 - Linklerin Görülmesine İzin Verilmiyor Üye ol Veya Giriş Yap
   
   What we don't know:
   Exactly which source commit above is responsible
   How to determine if a future kernel or source release is safe without putting user's devices at risk - You only need to reproduce the problem once to be hosed.
   
   
   
   
   Detay için pek zamanım yok o yuzden genel olarak belirtilmek istenen leak üzerine kurulum yapıldıktan sonra recovery üzerinden yapılan wipe yada flash işlemleri hafızada bad sektör benzeri sorunlara neden olabiliyormuş ki bu iyi ihtmal kötü ihtimal ise hardbrick'e neden olabilme ihtimali.
   
   musait olduğumda daha fazla detay yazmaya çalışırım.