I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
donalgodon said:
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
Click to expand...
Click to collapse
On S2, cwm can be flashed without a kernel
Kernels based on stock and that only include cwm and root are affected if not specifically patched
Sent from my GT-I9100 using Tapatalk 2
donalgodon said:
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
Click to expand...
Click to collapse
Your missing nothing actually, you are totally right in the fact its the kernel itself, but since the kernel is part of the rom, when you flash with odin, that is the reason the warnings are about...
so the best thing is actually just avoid the specific roms, and have a known good kernel...
FWX
Related
Getting a bit confused about all this, so am wondering if i've got it right. A rom is the whole thing, it includes a kernel and so forth? So a Kernel is a part of the rom right? And you can flash kernels individually without flashing a whole new rom? But what is a firmware then? Just another name of a rom?
Also on the Galaxy S2 can you flash custom roms, like Lite'ning, without getting root first? Or do you need to get root before flashing custom roms? If you can flash custom roms first without rooting, will the custom rom then give you root as long as it includes it?
And you also got recovery, which is a separate thing again? Galaxy S2 comes with a very basic one if i've understood correctly, but there is others out there that you can install, which also gives you the ability of flashing roms straight from the microsd/phone storage?
So have i gotten any of this? Hope am not to far off
Edit: http://forum.xda-developers.com/showthread.php?t=1246131 looks like most of my questions where answered there, though am still a bit unsure if it's possible to flash a custom rom before you root?
ROM's and FIRMWARE: The ROM or Read Only Memory is the internal flash memory where the core operating system resides. The Firmware is a device specific part of the ROM that controls various hardware components. So the firmware is contained in the ROM but in the context of Android the terms are often used interchangeably.
KERNELS: Different kernels offer different advantages, some are fast, some are light weight on the battery and some are a mix, so yes you can in most cases flash a different kernel with a ROM, and then your phone will be running the custom ROM you picked with the new kernel you flashed.
Rooting: You must have a rooted phone inorder to flash a custom rom, but rooting in my opinion seems really safe and it really easy to do on the SG2
There are things that allow you to flash from your SD card and you do that by entering clockworkmod revovery, apps like rom manager also allow you to flash from sd card, but you can always use odin, which is safe and fast
hope this helps
Thanks, and very nicely explained =) Another question then, what is the reason one need root before you can flash custom firmwares? As i heard Galaxy S2 doesn't really have any safety measures put in to stop things, like HTC do with their bootloader. Another thing is that i checked the thread for the Lite'ning rom, and saw the installation procedure, and it doesn't mention anything about having root before starting, so am getting a bit confused there.
You don't need to root before flashing a custom ROM as long as you can enter download mode (power up with volume down, home and power button pressed) and can flash the ROM via Odin.
If the ROM is flashable only via ClockWorkMod recovery (a zip that you copy on your phone) then you need to flash something that includes that recovery before flashing the rom (like CF-Root or any kernel that includes CWM).
Lite'ning ROM that you mentioned earlier is flashable via Odin so no problem.
Every ROM includes a Kernel, the only thing they sometimes don't include is the modem like in VillainROM, you have to flash it separately. And also, if a ROM is announced as rooted, when you flash it, you will have root regardless of the state before flashing
Thanks once again =)
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Nitrius said:
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Click to expand...
Click to collapse
Yes it will revert back everything
Nitrius said:
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Click to expand...
Click to collapse
If you dont flash a modem it will just use the one you had before. They talk about it in the old thread and also in the new but not in the firsts posts, you'll have to do a search.
Plus Modem Kernels are interchangeable .
KH3 Firmware with KI4 modem and KH1 kernel .
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
jje
I am new to samsung devices, I come from HTC.
Basically my question is, what determines the recovery of the phone? On HTC, the recovery was separate from the ROM and kernel. On samsung, from what I am reading it appears it is dependent on the kernel.
Does this mean if you brick your ROM you have no recovery to fix it (nandroid or whatever). If so, then what do you do in that situation?
Probably a newbie question, but I just want it cleared up.
As i understand it yes it's tied into the kernel and no if you screw something up you'll always have recovery you can 3 button press to get to it.
Sent from my SGH-I777 using XDA App
JeremyLeroy96 said:
I am new to samsung devices, I come from HTC.
Basically my question is, what determines the recovery of the phone? On HTC, the recovery was separate from the ROM and kernel. On samsung, from what I am reading it appears it is dependent on the kernel.
Does this mean if you brick your ROM you have no recovery to fix it (nandroid or whatever). If so, then what do you do in that situation?
Probably a newbie question, but I just want it cleared up.
Click to expand...
Click to collapse
Recovery is in the kernel, but we have a way to flash anything to the device even if the kernel is hosed - download mode (aka Odin mode). It's tough to completely brick a Samsung as long as you don't kill the bootloaders (don't flash anything with boot.bin or Sbl.bin, and don't flash anything designed for another device unless you've received specific directions from a developer here that it's OK - right now this means you can flash I9100 firmwares ONLY if you follow the directions for Hellraiser.)
Hi,
So unfortunately yesterday i (hard)bricked my phone. (yes my version is 4.0.4 BUT i've flashed five ROMs previously without any problems)
I tried to find other solutions such as Jig and JTAG but no luck for me here (in Sweden)
So instead i, today, went to the service department in the store which i bought my GT-i9100 from. They have now sent it to another location specified in repairing mobile phones.
Obviously my phone was rooted and as far as i know my warranty has been vioded.
So that's why i wonder: if they actually can open my phone, will they see that it has been rooted or does the phone somehow format everything and goes back to factory settings?
And if they can open it and see that it has been rooted, what can they do with my phone then?
Thanx for time
If you corrupted the emmc via the 4.0.4 emmc bug in kernel then I wouldn't worry about it as they will simply open device and replace motherboard. You can avoid emmc bug in future by simply flashing a custom kernel, keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again.
Btw, JTAG fix is for when you corrupt bootloader. If you corrupt emmc, depending on how bad it is (you may be able to connect/partition) the only way to fix is to replace the IC (nand) chip or more simply/quickly to replace whole board.
TheATHEiST said:
If you corrupted the emmc via the 4.0.4 emmc bug in kernel then I wouldn't worry about it as they will simply open device and replace motherboard. You can avoid emmc bug in future by simply flashing a custom kernel, keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again.
Click to expand...
Click to collapse
I do have a custom kernel - Siyah. I've used Siyah on all my ROMs yet. (except for those ROMs which came with it's own kernel, but then i re-flashed Siyah) And as far as i know Siyah should be completely free of the brick bug.
" keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again"
If i flash stock ROM wont i just get the stock kernel also? And for what purpose should i re-flash a custom kernel after flashing stock ROM?
Thank you theAtheist. Appreciate your work (helping others in the way necessary ) And also giving answer to All questions asked.
WardenBerret said:
I do have a custom kernel - Siyah. I've used Siyah on all my ROMs yet. (except for those ROMs which came with it's own kernel, but then i re-flashed Siyah) And as far as i know Siyah should be completely free of the brick bug.
" keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again"
If i flash stock ROM wont i just get the stock kernel also? And for what purpose should i re-flash a custom kernel after flashing stock ROM?
Thank you theAtheist. Appreciate your work (helping others in the way necessary ) And also giving answer to All questions asked.
Click to expand...
Click to collapse
Because a kernel is the link between Hardware and ROM.
You can flash as many kernels as you wish, as long as they're compatible with your current ROM.
Brick bug shows up only in 4.0.4's kernels, that's why flashing a safe kernel (like siyah) is recommended to avoid it.
I've beeing trying to change my ROM. I'm trying to install Clockworks recovery and it doesn't work. I've tried using Rom Manager, EZ recovery and doing it manually. Each time it just goes into the default recovery. I've also tried twrp. Any help?
GT-I9200T
Andriod version: 4.1.2
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
MistahBungle said:
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
Click to expand...
Click to collapse
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Also what about Rom Toolbox? Will that be bad aswell?
AcademyA said:
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Click to expand...
Click to collapse
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
MistahBungle said:
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
Click to expand...
Click to collapse
When finding the Kernel code, I type in getprop in terminal. I see stuff like the build number but I can't find the Kernel code anywhere. The only thing I see that is related to Kernel is ro.kernel.qemu: [0]
What are you doing in terminal ? You're overthinking this. I realise it's in the thread, but that's completely unnecessary nonsense
Phone settings/about device - build number.
My final post to this thread. You're on your own.
Alright! Everything's working now. Thanks for the help.
Well. I had my SII a long time ago, but luckily my chip was sane and I had exactly the right software version as the newest philz kernel. This time I got my friend's phone who asked me to put cm11 in it. Unfortunately his chip is insane as well there is no version matching to philz kernel's versions at all. He has XXMS7. The closest version of philz I see is XXMS1 but I'm not entirely sure if it's close enough to use it safely(especially with insane chip in the phone).
Any advices or soultions? Need help a lot.
T4underbolt said:
Well. I had my SII a long time ago, but luckily my chip was sane and I had exactly the right software version as the newest philz kernel. This time I got my friend's phone who asked me to put cm11 in it. Unfortunately his chip is insane as well there is no version matching to philz kernel's versions at all. He has XXMS7. The closest version of philz I see is XXMS1 but I'm not entirely sure if it's close enough to use it safely(especially with insane chip in the phone).
Any advices or soultions? Need help a lot.
Click to expand...
Click to collapse
First, no need to worry about the chip. There are chips that proved to be dangerous in relation to trim, which your friend has. AFAIK there are no other concerns with the chip.
I have never tried to root my phone with another kernel, but I'm pretty sure that one would be fine.(In the philz thread, he says most XW and XX kernels are interchangeable) If you are only trying to install CM11, I think you can just flash that kernel, then just reboot straight to recovery. Make sure you have a "kitkat compatible" recovery to flash from the xxms1 recovery, reboot to recovery again, then flash CM11 and gapps etc. This is what I would do. And if you have issues, you can always flash the stock rom again with odin
noppy22 said:
First, no need to worry about the chip. There are chips that proved to be dangerous in relation to trim, which your friend has. AFAIK there are no other concerns with the chip.
I have never tried to root my phone with another kernel, but I'm pretty sure that one would be fine.(In the philz thread, he says most XW and XX kernels are interchangeable) If you are only trying to install CM11, I think you can just flash that kernel, then just reboot straight to recovery. Make sure you have a "kitkat compatible" recovery to flash from the xxms1 recovery, reboot to recovery again, then flash CM11 and gapps etc. This is what I would do. And if you have issues, you can always flash the stock rom again with odin
Click to expand...
Click to collapse
Thanks for the feedback. I'll try to do that.