yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] tugler:
CF is it save to flash the new LQ5 kernel with Mobile Odin if i'm running the LQ5 stock rom?

cheers!
[Galaxy S II Original Android Development] angelomaldito:
+1
[Galaxy S II Original Android Development] djdeeles:
My wifi broke with ne lpq cf root kernel :(
[Galaxy S II Original Android Development] It_ler:
On which ROM?

Have you already wiped cache partition and Dalvk cache in recovery?

Does flashing the stock kernel solve the wifi issue?

Maybe it is not the correct CF-Root kernel?!
[Galaxy S II Original Android Development] djdeeles:
Sorry i mean LQ5 kernel with LQ5 rom.

Other kernels no problem stock LQ5 kernel or older 4.03 kernels
[Galaxy S II Original Android Development] danieldmm:
I flashed and no Wifi Problems. :)
[Galaxy S II Original Android Development] aashgaur:
im on checkrom v7 !! shud i flash lq5 kernel ?? if yes .. then how ?? thnxx :)
[Galaxy S II Original Android Development] danieldmm:
Wich kernel you have?
[Galaxy S II Original Android Development] aashgaur:
i have the stock kernel .. which came with checkrom !! i.e - 3.0.15-19100xxlq5-cl753921
[Galaxy S II Original Android Development] aji_kambas:
Im using kernel

3.0.15-I9100TDULP9-CL422302

dpi@DEELL149#3

so, which cf-root i should use???
[Galaxy S II Original Android Development] It_ler:
Then CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip (UPDATED) should work.
[Galaxy S II Original Android Development] aashgaur:
i ve got the brick bug in my kernel ... how shud i install this kernel ??
[Galaxy S II Original Android Development] danieldmm:
Just flash With ODIN or Mobile ODIN... i did that a couple of hours, not a problem, i as also in Stock Kernel.

Cheers
[Galaxy S II Original Android Development] It_ler:
Try CF-Root-SGS2_XW_KPN_LP9-v5.4-CWM5.zip ... nearest match to your kernel version.

Make a backup before flashing ... just in case ...
[Galaxy S II Original Android Development] af974:
Dude....take care of what you are doing http://xdaforums.com/announcement.php?f=1058
[Galaxy S II Original Android Development] GFXi0N:
Any way to make the mmc bug free? Like some chip rom update or something alike? Is it even possible?

I heard somewhere there is a similar solution like that, only Samsung does not allow its publication.... What do you know about this, chainfire?

Thanks
[Galaxy S II Original Android Development] :
Thanks

Thanks CHAINFIRE for this amazing method to root our phones. I have donated before:).but what about XXPL7 and XXLP8

with the OPS CSC.

Thanks snowman77/BLUSNOWMAN
[Galaxy S II Original Android Development] It_ler:
I think you are looking at the baseband/modem version, not the kernel/Build version. (Modem and CSC are not important for choosing the correct CF-Root kernel.)

Kernel/build versions should be XWLP7 / XWLP8.

For XWLP7 use CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5.zip.

And for XWLP8 use CF-Root-SGS2_XW_XSA_LP8-v5.4-CWM5.zip.
[Galaxy S II Original Android Development] AndehX:
I had 3.0.15-I9100BVLPB-CL709089 and I flashed CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5.zip which gave me the bootloop. tried CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5-PROPER.zip and got the same result.

Which kernel should I use now?
[Galaxy S II Original Android Development] ManDone.vRs:
Hello to all ! I have Siyah kernel 3.3.1+ ! Should i flash stock kernel ???
[Galaxy S II Original Android Development] leolysenko:
CWM

Have you tried erasing in CWM with this Kernel? Factoru reset/ wipe, dalvik cash?

---------- Post added at 04:50 PM ---------- Previous post was at 04:42 PM ----------

You can get rid of the emmc bug only by changing the chip i think.

---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------

ANYONE who had flashed the new CF-ROOT _XX_LQ5_5.6 please let me know if you tried erasing in the CWM (wipe).
[Galaxy S II Original Android Development] dragon135:
There will be cf-root for LPM?

Sent from my GT-I9100
[Galaxy S II Original Android Development] CamoGeko:
No!

Flash the latest Siyah 3.3.3.
[Galaxy S II Original Android Development] :
Guys, come on... I highly recommend you to stop using this LQ5 crap until official 4.0.4 releases. But if you brick your phone, do everyone a favor: admit you were warned. Do not post things like: bricked my phone!! Do not EVER flash leaked firmwares.
[Galaxy S II Original Android Development] ManDone.vRs:
i flashed last 3.3.3b and every 1 hour my phone go freeze ! need to pull out battery :((
[Galaxy S II Original Android Development] GFXi0N:
Experience told me best kernel is default cm9 kernel. Siyah and other ones give few advantages in return compared with the risks they imply... Always use at your own risk, expect wakelocks, battery drains, freezes....
[Galaxy S II Original Android Development] aji_kambas:
yes, this cf-root work! thanks bro :D
[Galaxy S II Original Android Development] Krendelrus:
It would be nice to see CF-Root for XWLPM release; also could you, Chainfire, check it for safety?
[Galaxy S II Original Android Development] danieldmm:
I was in Stock Kernel LQ5 , I flashed v 5.6 whith ODIN, then i copy my new ROM to Sdcard, XXLQ5 Light By TugaPower, I boot to Recovery, i did Wipe Data/Factory Reset, then i Flash my new ROM, my ROM already do Wipe cache and Dalvik. Everithyng good, but that its me :good:

Cheers
[Galaxy S II Original Android Development] Gwystyl:
Try the program gotbrickbug from chainfire before you flash anything, and be careful of it reports you have the brick bug...
[Galaxy S II Original Android Development] leolysenko:
Well, my friend, unfortunately you are wrong. The new official 4.0.4 for Russia is out and it has the same problem as the leaked one. In the russian forum we have 2 bricks only this evening with the new XWLPM which is official.
[Galaxy S II Original Android Development] joaobarroso:
It's safe to flash and root with mobile odin pro?

With mobile odin i still get the stock kernel, rigth?
[Galaxy S II Original Android Development] uncle.baze:
This is not an issue 4.0.4 firmware.

This is a problem because of the lack of brains and curves hands.

Idiots trying to restore a backup of 4.0.3 while in 4.0.4 and get a brick, but a thousand times it is said that you can not do that. It's like that SGS2 fyrmvare pour from the other models, and then wonder brick.
[Galaxy S II Original Android Development] leolysenko:
not only. You can also brick your phone if you wipe in CWM.

---------- Post added at 09:57 AM ---------- Previous post was at 09:55 AM ----------

ATTENTION!!!

THE NEW XWLPM CAN BRICK YOUR PHONE!!!

The kernel from the new XWLPM russian firmware has the same problem as the leaked XXLQ5 one. In the russian forum we have 2 bricks already. So, please,

AVOID WIPING AND UPDATING BACKUPS IN CWM WITH THIS KERNEL!!! TO AVOID ANY RISK I WOULD RECOMEND NOT USING FAKE CWM AT ALL

Better wait for a fixed kernel from CHAINFIRE !!! :good:
[Galaxy S II Original Android Development] Gammelgustav:
Every 4.0.4 since now has this "bug" -> MMC_CAP_ERASE command...

On LQ5 do not even wipe Dalvik Cache!!

It will brick your phone immeditialy! (Yep HardBrick)

And not to wipe Data should know everybody! ;)
[Galaxy S II Original Android Development] MacDrunk:
my cell carrier just release his ics update 4.0.3 PDA I9100UMLP6 and CSC	I9100TCELP6 is there a CF-Root
[Galaxy S II Original Android Development] mythtrandyr:
If you use stock kernel...you never brick your Phone, in LPM...Brick bug can be obtained only if you use CWM ... without the use of CWM firmware is completely safe ...
[Galaxy S II Original Android Development] whiskerp:
If you use touch CWM started from standard recovery by "installing" CWM.zip, then I believe you can backup, restore, wipe cache safely on a 4.0.4 ROM.

I have rooted using this method and had no problems. I do not have CWM running as an app in 4.0.4.

regards

Peter
[Galaxy S II Original Android Development] Chainfire:
Installing a ZIP inside Touch CWM can still brick.

It's the exact same story as using the non-Touch CWM.
[Galaxy S II Original Android Development] leolysenko:
thats exactly what I said. Do you have a problem with understanding?

---------- Post added at 01:49 PM ---------- Previous post was at 01:46 PM ----------

you can install the root using touch CWM but do not use touch CWM for wipes!!! You will get a brick!!!
[Galaxy S II Original Android Development] leolysenko:
Сf root

Chainfire!

Planning a CF ROOT for XWLPM?

thanks in advance :)
[Galaxy S II Original Android Development] whiskerp:
OK, thanks. I have reverted to XWLPI for safety as my phone has the brick bug. I was impressed by the low battery usage of XWLPM but not willing to risk bricking my phone.

Regards

Peter
[Galaxy S II Original Android Development] MeX_DK:
The brick bug is easy to avoid. It just requires a minor change in the fw file that you are trying to flash.
[Galaxy S II Original Android Development] whiskerp:
Can you elaborate? Thanks.
[Galaxy S II Original Android Development] MeX_DK:
You can read about it here:

http://xdaforums.com/showpost.php?p=27074278&postcount=69

But a "way" to make a kernel safe according to the above post is:

And for your phone to brick the following 3 conditions must be met:

1) A defective eMMC chip/fwrev that is unable to handle eMMC ERASE commands (command 38) properly. (I'll provide a link with more detail on the nature of the bug later) - This condition is the one Chainfire's new app checks for. By the way, M8G2FA fwrev 0x11 (seen on some Kindle Fires) is also suspected of being defective.

2) A recovery binary that attempts to erase partitions when formatting them. Most ICS recovery binaries fit in this category, most Gingerbread recoveries do not attempt to perform an erase operation so are safe. Note that also, an affected update-binary in a ZIP could be a cause of problems too. (e.g. flashing a firmware that has an ICS update-binary and formats the partition could cause a problem even with a "safe" recovery.) So a kernel can be repacked with a "safe" CWM (such as the most recent CF-Root releases) but it will still only be partially safe.

3) A kernel that allows attempts to erase a partition to actually happen. (as opposed to reporting "not supported" and doing nothing.) - A common way of rendering a kernel safe is to remove MMC_CAP_ERASE from the capability flags in drivers/mmc/mshci.c
[Galaxy S II Original Android Development] Fidalgos:
can we help me?

Sorry about my question :o

I upgrade my SGS2 yesterday to the last ICS 4.0.3 official firmware and now... I have this Kernel: XWLP7 and CSC:LP5(XEU) the Kies show this:

PDA:LP7/PHONE:LPS/CSC:LP5(XEU)

I don't see on the first page of this topic... the CF-Root compatible to my current Kernel:confused: So... I appreciate very much if you can help me please :)

Thanks in advance!
[Galaxy S II Original Android Development] As1r:
What about the new Firmware from VF. BULPD? Is there a CF-Root the branded Kernel? Or an Kernel who is the nearst to them.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] leolysenko:
here you go: http://download.chainfire.eu/158/CF-Root/SGS2/CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5.zip

---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------

try this: http://download.chainfire.eu/171/CF-Root/SGS2/CF-Root-SGS2_XX_NEE_LPD-v5.5-CWM5.zip

but before flashing it make sure you have the stock kernel downloaded also. If the CF ROOT does not work and the phone does not start, flash the original kernel back with Odin.
[Galaxy S II Original Android Development] Fidalgos:
Thanks very much for your help;)

I only have a doubte about this file... because is XEN and not XEU like my current ROM :o
[Galaxy S II Original Android Development] Phil3759:
Kernels are same usually, it won't affect you in anyway
[Galaxy S II Original Android Development] Fidalgos:
Is what I see on Kies:

PDA:LP7/PHONE:LPS/CSC:LP5(XEU) and in SGS2 About:XWLP7

So... is secure to use the file posted from @leolysenko with this name: CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5

Once more... Sorry for my questions :confused:
[Galaxy S II Original Android Development] As1r:
There is no Stock Kernel available at this time from Bulpd. -.-

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] Phil3759:
Yes, it is safe and kernel is same

However, I was on LP7 and it is one of the first stock ICS releases. It was really very bad coming from Gingerbed: FC, slow, buggy...

I wanted to go back to GB at that time. XWLPG is more mature and official proven release. I would really go LPG for a good ICS experience

You can extract the zimage file from your tar.md5 rom file using winrar or 7zip

Then, if you need it, flash that file with mobile odin

I wrote a guide here to do it:

http://xdaforums.com/showthread.php?t=1746794

It is at the Mobile Odin Free section

Look at the root method while you are there, the Method 1. Worth it if you want root simple and safe
[Galaxy S II Original Android Development] leolysenko:
you got me laughing out loud! If there is no stock kernel how come you have it installed? :laugh:
[Galaxy S II Original Android Development] As1r:
Oh *g*, I meant that there is no one available on Intratech's Thread and I don't extract it from the Firmware. Ok ok and forget to look at Samobile ^^. Hehe got it flashed few hours ago.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] Fidalgos:
OK :) I have now SGS2 rooted with the posted file from @leolysenko and when finish root... I have on restart th Yellow Triangle (I use my jig but don't remove the counter) so... with the apk Remove Triangle from Chainfire v.151 do the job.

:good:Thanks for your help and Thanks to @leolysenko

Regards from me and from PORTUGAL
[Galaxy S II Original Android Development] Phil3759:
As I said above, extract the zimage file from the ROM file downloaded from sammobile

The zimage is the kernel, you can flash in mobile odin app
[Galaxy S II Original Android Development] leolysenko:
You are very wellcome;)
[Galaxy S II Original Android Development] timberwolf60:
Next time don't used Odin to flash cf root or other rooted kernel, used this method: http://xdaforums.com/showthread.php?t=1501719.

No more binary counter increase and triangle warning. Your phone will be rooted. Finally you used allianceOTA to flash your favorite kernel.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3c kernel, jkay 14.1 mode.
[Galaxy S II Original Android Development] leolysenko:
I would not recommend this method on 4.0.4.

BUT if you still choose to use it on 4.0.4 DO NOT USE the CWM further for backups or wipes!!! It will brick your phone!
[Galaxy S II Original Android Development] As1r:
@ Phil And leol. Thx for help and big Thx for the fantastic guide. Got added it into my favs.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] danieldmm:
May I know why? Since XXLQ5 I use this method to Swype kernels (Siyha 3.3.3c, CF ROOT LQ5 v 5.6 and Stock Kernel XWLPM)

And let me say I use a lot. :D

And never have issue so far.

Cheers

Enviado pela minha bomba i9100 através doTapaTalk.
[Galaxy S II Original Android Development] MeX_DK:
Bricking only happens if the kernel allows EMMC_CAP_ERASE if that is removed from the capacity flags of the Kernel then you can do backups/restores etc without risking anything.
[Galaxy S II Original Android Development] Phil3759:
That method for root, at least my scripts, doesn't touch data and cache partitions at all. Only 2 files are copied to /system and some files deleted from system. So, it should not trigger the brick bug in anyway
[Galaxy S II Original Android Development] bkhaliq:
help needed

Hi

I have ICS 4.0.3 (GT-i9100BULP7 | LP8 | IML74K.BULPD), can someone tell me how to root it.

i rooted it before the update with "CF-Root-SGS2_BU_VOD_LPC-v5.4-CWM5".

After the update my mobile is unrooted

my i9100 also has the BrickBug Chip issue
[Galaxy S II Original Android Development] Phil3759:
You can use xw_xen_lp7-5.4 cf root in post 1. It is cf root for your kernel

Or look at my signature...
[Galaxy S II Original Android Development] Sandzak385:
Can not download the CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip , it gives me a Database Error in your site Chainfire
[Galaxy S II Original Android Development] timberwolf60:
I used this method to root xxlq5 and xwlpm, after that I used allianceOTA to flash siyah 3.3.2 and later upgraded to siyah 3.3.3c. Due to siyah kernel not compatible to 4.04 which cause Bluetooth, camera and video playback problem. So I restored back by cwm to xxlpw and paranoid dual boot. No problem. This was a more easy way for rooting for s2. Even I flashed any ics firmware through mobile Odin with everroot disabled, I was easily get my phone rooted by this method. CF root was excellent to me but now I used dual booting with siyah kernel and enjoy.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3c kernel, jkay 14.1 mode.
[Galaxy S II Original Android Development] timberwolf60:
If you flashed the stock rom with rooted device, the best way by using mobile Odin pro with everroot enabled, then your phone will remained rooted and enjoy!

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3c kernel, jkay 14.1 mode.
[Galaxy S II Original Android Development] leolysenko:
MeX_DK, timberwolf60, Phil3759,

sorry If I made myself misunderstood. Of course this method works and one can get root access. I simply want to warn people NOT TO USE the same CWM for wiping and backups with new kernels from XXLQ5 and XWLPM.
[Galaxy S II Original Android Development] bernard134:
Waiting for Chainfire to update: DXLPB CMW CF-Root Kernel
[Galaxy S II Original Android Development] gkahd:
Brick Flag

@Chainfire

It might be a good idea to flag the CF root kernels that might cause the brick so people can look into the dangers.

(Not that it is CF-Root's issue but the CWM with the bad kernel combo is dangerous).
[Galaxy S II Original Android Development] whiskerp:
Sorry if I'm showing my ignorance but could CWM be built NOT to use EMMC_CAP_ERASE at all? If like the Samsung PDA it didn't use this potentially dangerous facility then it would not brick phones. If the flag is not set then it doesn't use the dangerous code so presumably it doesn't need it.

Peter
[Galaxy S II Original Android Development] MeX_DK:
That particular flag is set at kernel level as far as I understand. Hence Chainfire can make his kernel "safe" to flash if he made certain that particular flag was removed from the capacity flag of the kernel. That is my understanding at least
[Galaxy S II Original Android Development] M3drvr:
I can't download anything from the first few posts. Site down or what?
[Galaxy S II Original Android Development] seghier:
problem with chainfire site
[Galaxy S II Original Android Development] jvlopez:
Site down

any official mirror?
[Galaxy S II Original Android Development] timberwolf60:
Thank, I had been using cwm to done a nandroid backup on xxlq5 with siyah kernel and no problem.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3c kernel, jkay 14.1 mode.
[Galaxy S II Original Android Development] leolysenko:
THe problem appears only with XXLQ5 and XWLPM kernels:

"I simply want to warn people NOT TO USE the same CWM for wiping and backups with new kernels from XXLQ5 and XWLPM."
[Galaxy S II Original Android Development] whiskerp:
Does the backup process brick your phone or is it the restore process? If its just the restore then of course you can flash a safe kernel before you perform a restore. But if the backup also bricks then its pretty bad.

Peter
[Galaxy S II Original Android Development] sohail667:
thnx is this compatible with xwlpg
[Galaxy S II Original Android Development] Gammelgustav:
Which should be logical to all them who tried in TouchRecovery and bricked... :rolleyes:

Sent from my Galaxy S2
[Galaxy S II Original Android Development] Gammelgustav:
Sure - search for the right version on first page. ;)

Sent from my Galaxy S2
[Galaxy S II Original Android Development] leolysenko:
I am not sure of this. I know that some guys tried to restore backups from 4.0.3 and got bricked. But I would not recommend using CWM at all - you never know. Better wait for a new CF ROOT with fixed problem.
[Galaxy S II Original Android Development] whiskerp:
I can understand a restore bricking as it could wipe the partition before a restore. But a backup will only read stuff and write to a regular file.
[Galaxy S II Original Android Development] MeX_DK:
Its not the wiping as such that causes the bricking. IF the partition was only wiped there was no problem. Bricking happens when the kernel tried to format, and deletes the partiation in the same process. That is when you will get your brick. If it just deleted all the files in the folder no problem.

Its semantics really. Wiping is a bad expression to use, since if it was only wiping there would be no issue. But if it formats AND erases the partition, then thats where you will get in trouble.

But I am hoping that Chainfire will soon release a XWLPM kernel so I can finally upgrade :)
[Galaxy S II Original Android Development] uncle.baze:
+100500!

I hope we will wait. :)
[Galaxy S II Original Android Development] mark wild:
CheckROM RevoHD V7

Hi, community...! :) :) :)

I have made the biggest mistake in my SGS2 history. For the first time, I flashed a ROM without reading the whole post about the ROM. So I installed

CheckROM RevoHD V7 (Kernel 3.0.15-I9100XXLQ5-CL753921)

. I see that there is a CF-Root kernel, but I'm worried that I could get my phone bricked. I searched and read a whole lot of this thread and the checkrom.com threads, but I couldn't find a definitive answer to my question.

- Is there a way to Root my phone (get CWM) and flash another ROM? A step by step guide, maybe, someone can point me towards?

With the best regards

A XDA FAN.
[Galaxy S II Original Android Development] Mario1968:
For semibricked devices you can try to look here:

http://xdaforums.com/showthread.php?t=1667886

Relatively simple way to revive your phone from a MMC_CAP_ERASE brick with PIT files

there is a section about the i9100 device, read on:)

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Odexed

Siyah 3.2.7.2

Jkay V14.1
[Galaxy S II Original Android Development] Phil3759:
No, a brick with MMC_CAP... makes your phone dead and only a motherboard change will fix it. It is a superbrick, not semibrick
[Galaxy S II Original Android Development] dancingbear84:
Hi

I have been an android user for a few years now, but I find I am wanting a stock android experience not touchwiz. I have a kernel version of 3.0.15-I9100XWLP7-CL340913dpi@DELL134#3

I saw that you linked to the LP7 kernel

I don't fully get what you mean by "XWLPG is more mature and official proven release. I would really go LPG for a good ICS experience"

I assume I am to root using the CFLP7 that you linked, but then look for a ROM with XWLPG? or are you suggesting rooting with a CF XWLPG kernel.

Please don't flame the Noob, I'm trying to learn and I don't want to end up with a brick.

Thanks
[Galaxy S II Original Android Development] leolysenko:
Give me your kernel version. Settings - About Phone - Kernel version
[Galaxy S II Original Android Development] Phil3759:
I did not link to any LP7! I linked to a guide to root any ICS phone with CWM image

LP7 is buggy, FC+++, lags...

LPG is more stable. Imagine LP7 as a test release...

This one maybe will work, in post 1

CF-Root-SGS2_XW_XSA_LP8-v5.4-CWM5.zip

have a backup of your kernel in case you get a boot loop

Or use the root method 1 in this link, it will work at 100% and is very safe

http://xdaforums.com/showthread.php?t=1746794

Good luck
[Galaxy S II Original Android Development] CamoGeko:
Dude, every day I come to this thread I see you promoting your own guide in pretty much every post.

I think the link being in your sig is good enough. If people want to use CF-Root kernel to root their S2 then let them do that. Don't keep telling everyone to go somewhere else (like, your thread), its not cool.