cheezusweezel
Enthusiast
- 5.012
Chainfire hat seinem ICS CF-Root Kernel ein Update (auf Version 5.6) gegönnt, womit der Brick-Bug zumindest verhindert werden kann.
Siehe hier: xda-developers - View Single Post - [30.05.2012][CF-Root 5.6] KJ*,KK-19A,KL-1378,LA-1346,LB1,LC1,LP-1YF89 - su+bb+CWM5
---------------------------------------------------
Download: CF-Root 5.6 LRQ
1. als zImage: https://www.hidrive.strato.com/lnk/OiOx4r03
2. als tar-File: https://www.hidrive.strato.com/lnk/JgOxYb6o
3. als cwm.zip: https://www.hidrive.strato.com/lnk/jhOx4J3u
Download-Übersicht der neuen CF-Kernel, LPY bis LRQ: Alle v5.6
Installation: tar oder zImage per MobileOdin / tar per OdinPC / zImage per Initial_Root-Flasher oder CWM.zip per CWM-R !!!
---------------------------------------------------
PhilZ-cwm6 Kernel für LRT, flashbar über Stock-Recovery, bringt Root+CWMR: https://www.hidrive.strato.com/lnk/taOxYGjs
Die obige Version kann natürlich auch mit jedem anderen CustomRecovery installiert werden.
Hier auch noch die Version für OdinPC, als tar: http://www.mediafire.com/file/6uml9sbmsmm4s4d/PhilZ-cwm6-XXLRT-DBT-2.5.tar.md5
---------------------------------------------------
PLEASE READ THIS ENTIRE POST BEFORE FLASHING, IT IS IMPORTANT
By now you have undoubtedly heard about bricking issues on the Galaxy Note, and various other devices. There is a bug in the Samsung stock ICS kernels that can trigger flash corruption and hardbrick your device.
There is a kernel source patch that works around the problem. It doesn't fix it, it just makes sure the problem isn't triggered. As you may or may not know, CF-Root's are not built from source, they are binary modifications to Samsung stock kernels.
As such, it is impossible for me to apply that patch to the source. I have received quite a bit of criticism from people who think they know what they are talking about for not implementing this patch - but as you may understand from the above, there's nothing I can do about it for CF-Root. The bug will disappear from CF-Root kernels as soon as Samsung fixes the issue in their builds, and not earlier.
However, I have patched the CWM included in the v5.6 CF-Root kernels, so CWM will no longer trigger the bug. But, I cannot be 100% certain that patch works. I have done about 50 restores and wipes today (both can trigger the bricking bug) and my device is still fine. But, I may have gotten lucky, or my device may not be affected at all.
In the same way, we will not know which stock Samsung kernels do or do not have the bug. Until they update their source and we see the problem is fixed (or Samsung outright tells us), any Samsung firmware release is suspect - and we won't know if the bug is present until somebody hardbricks on that kernel
Thus keep in mind, while I think CWM recovery will no longer trigger the problem (but I cannot guarantee it), the problem *is* actually still present in the kernel itself. As far as we (and the Android developer who released a lot of information about this) know, nothing else triggers the code that triggers the bug, but to be safe, I wouldn't be using the factory reset function in Android itself, or anything like that.
BEWARE: update.zip's can trigger the bug if they use "format" commands!
There is and cannot be any guarantee for CF-Root. You use it at your own risk. If you wan't to be safer, use a custom-built kernel of which the developer claims the problem is patched.
Siehe hier: xda-developers - View Single Post - [30.05.2012][CF-Root 5.6] KJ*,KK-19A,KL-1378,LA-1346,LB1,LC1,LP-1YF89 - su+bb+CWM5
---------------------------------------------------
Download: CF-Root 5.6 LRQ
1. als zImage: https://www.hidrive.strato.com/lnk/OiOx4r03
2. als tar-File: https://www.hidrive.strato.com/lnk/JgOxYb6o
3. als cwm.zip: https://www.hidrive.strato.com/lnk/jhOx4J3u
Download-Übersicht der neuen CF-Kernel, LPY bis LRQ: Alle v5.6
Installation: tar oder zImage per MobileOdin / tar per OdinPC / zImage per Initial_Root-Flasher oder CWM.zip per CWM-R !!!
---------------------------------------------------
PhilZ-cwm6 Kernel für LRT, flashbar über Stock-Recovery, bringt Root+CWMR: https://www.hidrive.strato.com/lnk/taOxYGjs
Die obige Version kann natürlich auch mit jedem anderen CustomRecovery installiert werden.
Hier auch noch die Version für OdinPC, als tar: http://www.mediafire.com/file/6uml9sbmsmm4s4d/PhilZ-cwm6-XXLRT-DBT-2.5.tar.md5
---------------------------------------------------
PLEASE READ THIS ENTIRE POST BEFORE FLASHING, IT IS IMPORTANT
By now you have undoubtedly heard about bricking issues on the Galaxy Note, and various other devices. There is a bug in the Samsung stock ICS kernels that can trigger flash corruption and hardbrick your device.
There is a kernel source patch that works around the problem. It doesn't fix it, it just makes sure the problem isn't triggered. As you may or may not know, CF-Root's are not built from source, they are binary modifications to Samsung stock kernels.
As such, it is impossible for me to apply that patch to the source. I have received quite a bit of criticism from people who think they know what they are talking about for not implementing this patch - but as you may understand from the above, there's nothing I can do about it for CF-Root. The bug will disappear from CF-Root kernels as soon as Samsung fixes the issue in their builds, and not earlier.
However, I have patched the CWM included in the v5.6 CF-Root kernels, so CWM will no longer trigger the bug. But, I cannot be 100% certain that patch works. I have done about 50 restores and wipes today (both can trigger the bricking bug) and my device is still fine. But, I may have gotten lucky, or my device may not be affected at all.
In the same way, we will not know which stock Samsung kernels do or do not have the bug. Until they update their source and we see the problem is fixed (or Samsung outright tells us), any Samsung firmware release is suspect - and we won't know if the bug is present until somebody hardbricks on that kernel
Thus keep in mind, while I think CWM recovery will no longer trigger the problem (but I cannot guarantee it), the problem *is* actually still present in the kernel itself. As far as we (and the Android developer who released a lot of information about this) know, nothing else triggers the code that triggers the bug, but to be safe, I wouldn't be using the factory reset function in Android itself, or anything like that.
BEWARE: update.zip's can trigger the bug if they use "format" commands!
There is and cannot be any guarantee for CF-Root. You use it at your own risk. If you wan't to be safer, use a custom-built kernel of which the developer claims the problem is patched.
Zuletzt bearbeitet:
