yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] seka1980:
really need some help here people,

im trying to root and unlock my GS2 ive just used odin to put "PhilZ-cwm6-XWLSD-OXX-4.87.tar.md5" on the phone

the phone rebooted with the yellow triangle and restarted fine but ive run root checker and it says its not rooted,

do i need to try a different version of PhilZ-cwm6 - Safe Stock Based Kernel?

below is the info my phone is running anroid version 4.1.2

Baseband version

I9100BVLS4

Kernal version

3.0.31-889555

dpi@DELL224#3

SMP PREEMPT fri may 31

KST 2013

Build number

JZO54K.I9100XWLSY

any help will be much appreciated

jon
[Galaxy S II Android Development] makis206:
You tried to flash XWLSD file on XWLSY firmware, just download the XWLSY file and try again? Why didn't you try with the zip? No external SD?:)

Sent from another Galaxy
[Galaxy S II Android Development] seka1980:
I dont know where to get the XWLSY firmware from?

any ideas on what to do next
[Galaxy S II Android Development] makis206:
Here you are: http://d-h.st/users/philz_touch/?fld_id=21691#files

You just need one of them, tar.md5 for Odin or zip to flash it from your recovery (needs external sd), you choose..:)

Sent from another Galaxy
[Galaxy S II Android Development] seka1980:
first of all thanks so much for the info

ok so i downloaded the link you sent me and flashed the phone again then restarted

as before the yellow triangle came up as it booted then i tried to use samsung quick root

and again i got the message - Error make sure you have flashed insecure kernel

am i doing something wrong?

am i right in saying that by flashing with - PhilZ-cwm6-XWLSY-ORA-5.10.0.tar.md5 this should put an insecure kernel on my phone

cheers

jon
[Galaxy S II Android Development] makis206:
How did you flash this file, via Odin? Because that's the right way. When you flashed it, did you manage to get to the main menu? Don't you have Superuser app in your app drawer? I don't know what this "samsung quick root" does..

If you flashed it correctly with Odin you should have Superuser, otherwise i would suggest you to try the zip file from your phones recovery menu (hope you have external sd card to put the zip in..)

Don't mind about yellow triangle, let's install Superuser first and we will fix/erase it after with triangle away app..:)

Sent from another Galaxy
[Galaxy S II Android Development] electricsheepdreamer:
I've never used Samsung quick root but if you had flashed signed.zip version from external SD (post #3, check it, different methods described), you would have been rooted and without the triangle.

Cheers, man.
[Galaxy S II Android Development] Matt3333:
Any reason why fixing permissions on recovery would cause a bootloop?
[Galaxy S II Android Development] Phil3759:
fix permissions is the most useless stuff in recovery

It was dropped in recent sources and will disappear on next update

I personally never used it, except once by mistake months ago when I added the confirm option to avoid the mess

By the way, that only time I did by mistake, some of my apps got corrupted, which is logical
[Galaxy S II Android Development] iloveindia:
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>

DVLSH (i9100T) - XWLSS - XWLST - XWLSW - DXLSD - XXLSQ (i9100P) - ZSLSJ (fixed for bootloop)

is it OK if I flash above recovery for I9100ZCLSJ????

please reply
[Galaxy S II Android Development] It_ler:
Sorry, I don't know if it will work on your phone.

Backup all important stuff ... just in case.

If you are confident enough, flash it and report back if it worked fine.

I think here not much people using the same ROM as you.
[Galaxy S II Android Development] iloveindia:
it was a waste of time and internet bandwidth, some crappy ROM couldn't even install it. Back to akop jb milestone 2.
[Galaxy S II Android Development] Óðinsdagr:
Are there any general concerns about using the *rooted .zips on a factory 2.3.3 GB I1900, trying to help out a friend. Thanks for any help afforded me
[Galaxy S II Android Development] electricsheepdreamer:
I think there's no Philz kernel for 2.3.3. GB.

Was that I9100?

No problem.
[Galaxy S II Android Development] It_ler:
Search for CF-Root kernel. That might help to root the phone on GB ROM.
[Galaxy S II Android Development] sprognut:
Hiya im on a I9100P and on a xlss rom.

Can someone point me to the right download so I can get this phone rooted please?

Thanks so much

Jess
[Galaxy S II Android Development] electricsheepdreamer:
Look here, Jess.

http://xdaforums.com/showpost.php?p=44609552&postcount=3767

No problem.
[Galaxy S II Android Development] sprognut:
fab thats what i was looking for thank so much
[Galaxy S II Android Development] Koudelka:
hi

I have used PhilZ-cwm6-XWLSD-OXX-4.93.6-signed.zip to root my phone.

1- If I want to update to latest version I can use PhilZ-cwm6-XWLSY-ORA-5.10.0-signed.zip or its better to stay with the current 4.93.6 version ?

2- I am using now SuperSU and not superuser, If i want to update to latest 5.10.0 i should use philz_installer.cfg to disable superuser install so i dont lose all supersu configuration?

thanks in advance

info:

PDA: I9100XWLSD

PHONE: I9100XXLS8

CSC: I9100OJVLS6

Build Number: JZO54K.I9100XWLSD
[Galaxy S II Android Development] Phil3759:
Better to update

And yes, to keep SuperSU, use my cfg file
[Galaxy S II Android Development] ManBearrrPig:
i am new here and i would like someone to point me to the right kernel.

i am on stock 4.1.2 (UK) gt-9100.
[Galaxy S II Android Development] electricsheepdreamer:
Hey there.

See (and write down if you like) your build number (at the bottom of Settings>About device)
[Galaxy S II Android Development] JAlfredoP:
Hi Friends, a question, is thies Kernel compatble with the ROM Resurrection Remix 4.2.2 CM ? Thanks
[Galaxy S II Android Development] It_ler:
No, this kennel is for stock or stock based ROMs only.
[Galaxy S II Android Development] Phil3759:
There is a cm compatible version also
[Galaxy S II Android Development] swimao:
I'm not getting what is the right kernel, can someone point me right one, pls?

Here goes the screenshot of my phone details.
[Galaxy S II Android Development] electricsheepdreamer:
This one. Np.
[Galaxy S II Android Development] knight84:
thanks works wonder!!
[Galaxy S II Android Development] Phil3759:
PhilZ Touch 5.11.2 / CWM 6.0.3.7

http://d-h.st/users/philz_touch/?fld_id=16062#files

Please check change log in main thread

IMPORTANT:
[Galaxy S II Android Development] electricsheepdreamer:
Hey Phil,

regarding unattended reboot, I've just tried it on this latest version (after taking the battery out and long pressing the power button for 10 secs) and the phone stucks at Samsung logo.

BUT, if I long press the power button again (until Samsung logo dissapears) it boots just fine.

No issues so far, nice and smooth.
[Galaxy S II Android Development] Phil3759:
Thank you for your confirmation

I also tried it on latest stock ROM and sounded not bad

I can always revert if needed
[Galaxy S II Android Development] makis206:
Works perfect on stock XWLSW, thanks Phil!

Sent from another Galaxy using Tapatalk 2
[Galaxy S II Android Development] sharp87:
[MENTION=4666971]Phil3759[/MENTION] : you are amazing...
[Galaxy S II Android Development] pdario:
This morning I updated to lates 5.11.2.

All went fine; I used the phone and now I just updated to latest SwiftKey. Phone crashed, force rebooted: after boot animation, it returned to boot logo.

I deleted caches from the recovery, but now it not even gets to boot animation, it stays on the boot logo.

NO WAIT!!! While I'm writing, it started the boot animation and now it's rebuilding dalvik-cache. Got to lock screen... It runned a little and now it's freezed in black screen.

Another force reboot, boot logo, boot animation... Lock screen, sd mounted, mobile connected, unlock ok... it seems working...

WTH could have happened??

[EDIT]

??????

The trigger is trying to input the Amazon password in the Amazon app-store app!

When I tap there (that field does not accept paste, BTW), the app goes black, the keyboard is visible, but the phone is freezed.

Then I have to force restart several times, wiping caches, to get to home again.

I tried using the stock keyboard (as I just updated SwiftKey...), but the crash is the same.

[EDIT]

No way out: I had to make a full restore.

After that I updated swift key and tried the Amazon password: a new freeze, but this time the phone rebooted correctly after force reboot.

It seems the previous PhilZ version can handle this, so I'll keep it till some clarifications here, thank you!
[Galaxy S II Android Development] guido_glx:
Hi... will this new update work on this ROM? WanamLite V14.6 LSW 4.1.2

http://xdaforums.com/showthread.php?t=1436817
[Galaxy S II Android Development] sharp87:
S..
[Galaxy S II Android Development] mohammedsarhan:
Bootloop issue again after the last update.

Thank you Phil for your always great work.

but after yesterday update to the kernel. i had phone crash, and phone stuck at Samsung logo.

cache and dalvik cache wiped, reinstall the new kernel=>> stuck at SAmsung logo

reinstall the previous version 5.08.5 =>> Boot loop
[Galaxy S II Android Development] electricsheepdreamer:
Hey try this, when stuck on Samsung logo, hold the power button pressed until the logo goes away and wait and see if it will boot.

---------- Post added at 06:57 PM ---------- Previous post was at 06:57 PM ----------

Yes.
[Galaxy S II Android Development] Phil3759:
As i said many times, i think Samsung left i9100 with a buggy JB kernel/rom. The 5.11.2 is completely pure stock, unlike previous versions.
[Galaxy S II Android Development] Parte:
Hiho,

Will the V5.11.2 work on this ROM ?

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

Omega V24 (XWLSW)
[Galaxy S II Android Development] guido_glx:
Works great, just like you said it would, thanks again!

And thanks PhilZ obviously...

Enviado desde mi GT-I9100 usando Tapatalk 4
[Galaxy S II Android Development] phozy888:
Hi Guys,

5.11.2 CSC is OXX - can I use this for UK ? Im currently using XEU XWLSW neatrom and wanted to know if I had to keep the XEU as im UK based.

Thanks
[Galaxy S II Android Development] electricsheepdreamer:
Yes, you can use it on XEU XWLSW NeatROM.
[Galaxy S II Android Development] pdario:
Maybe I lost some past message, but why not patching it anymore?

If this is the case, I cannot update your kernel anymore, unfortunately...
[Galaxy S II Android Development] Phil3759:
Patching jb is probably useless. We always had a doubt. But now, after one year and no bricks, i assume it safe. Also, patching it bugs the format sdcard menu in phone.

Why add useless bugs now that the risk is probably gone?
[Galaxy S II Android Development] pdario:
Not sure to understand, still... What about the brick I had yesterday?

Am I wrong somewhere?
[Galaxy S II Android Development] CheekyLord:
---

But does this ONLY happens cuz WE HAVE this kernels with disabled 'mmc_cap_erase' ..??(!!) :confused:

---

Greetz

Edit/

Am not sure and little scared about future kernel using, so my question.

SentFrom RootBox
[Galaxy S II Android Development] kt-Froggy:
Correct me if I am wrong, but to my knowledge the only EMMC brick scenario was 4.0.4 with stock kernel and stock recovery. JB seems to be safe with ALL kernels and recoveries, hence Phil's decision to stop patching.

Judging by your post, what you had was just a minor glitch. A brick is called like that for a good reason... :)
[Galaxy S II Android Development] pdario:
Minor glitch? I had to scratch the phone and restore it: fortunately I had a one day old nand backup.
[Galaxy S II Android Development] shoey63:
Please allow me to join the discussion (As a former superbricked Note1 owner - same hardware as I9100)

Emmc brick occurs when "secure erase" hits stock ICS kernel.

This can happen in 3 ways.

1) Wiping with a Pre CWM 6.* recovery on a custom ICS kernel which does not disable secure erase. ie: eMMC_CAP_ERASE disabled.

2) Wiping on a Temp CWM, running on top of stock ICS kernel, where "wipe via secure discard" is NOT suppressed. As found in temp 5.*, but fixed in 6.*

3) Flashing a ROM/Zip with ANY CWM Temp recovery running on top of stock ICS kernel, where update_binary contained in the Zip doesn't have "secure discard/erase" suppressed.

In Stock JB kernels, Samsung has blocked the lethal "secure erase" command, and after a year or so with no bricks, it is now considered safe, even by [MENTION=4666971]Phil3759[/MENTION].
[Galaxy S II Android Development] pdario:
I don't know what type of brick struck me, emmc or anything else; what I saw is the kernel previous to 5.11.2 can boot normally, 5.11.2 has all sort of problems (stuck and boot logo, stuck ad boot animation, boot animation and then back to logo, got to lock screen and then freeze). Wasn't there a bug that corrupts data partition without a clean shutdown? That fits what I saw.
[Galaxy S II Android Development] Phil3759:
Thank you a lot [MENTION=4675598]shoey63[/MENTION]

At all: do not expect me to answer or explain what's superbrick. Make an effort and search.

shoey63 sum it up. I was one of the most careful, but now, after one year, if I continue patching JB I'd call my self stubborn
[Galaxy S II Android Development] Phil3759:
It's a ROM/kernel combo Samsung bug

On XWLSW ROM + XWLSW kernel, this seems to be fixed from all my tests
[Galaxy S II Android Development] pdario:
But did you use to have a patch for this too?

What about LSD ROM I'm using now? I'm planning a wipe to fresh install I9100PXXLSK_I9100PTIMLSK_TIM that is the latest 9100P rom for my network operator that has NFC enabled.

Do you know if it will suffer the bug with your unpatched kernel?

Thanks for your time.
[Galaxy S II Android Development] Phil3759:
Upload XXLSK

I will release it

You test and tell me ;)
[Galaxy S II Android Development] pdario:
Deal! :fingers-crossed:

http://xdaforums.com/showpost.php?p=39956660&postcount=2906
[Galaxy S II Android Development] guido_glx:
After half a day of using v5.11.2, exactly the same thing happened to me :crying:

I'm restoring a backup right now...

EDIT: backup restored, I'm back on v5.10
[Galaxy S II Android Development] Geekeek:
Tell you what I did.

1. Mobile Odin Pro

2. Downloaded Sammobile files. Will be using three of them. CODE, CSC and MODEM.

3. Download phils kernel for XXLSJ in OP

4. Now use open file in mobile odin and just choose above files and also kernel. It will automatically assign what sohuld go where so don't worry about that. Should be like this http://xdaforums.com/attachment.php?attachmentid=1486422&d=1353076220 (thanks to user bluefa1con)

5. Everroot, Wipe data and cache and wipe dalvik all should be checked.

6. Flash.

You'll boot up with the new rom.which is rooted and also have phils touch CWM. :good:
[Galaxy S II Android Development] Darkmind1:
I've already done this before having seen your post, but thanks for the help. What I did was:

1) Flash Odin Kernel. Binary counter increased to 1.

2) Flash CWM package of Philz Kernel.

3) Used Triangle Away App to reset flash counter. In this case, it was a bit more special than usual. The application could not detect status of my phone, so it had to boot into some special mode, which would then prompt me if I want to continue resetting flash counter or not. It went without any issues, just that you have to be careful so that values match.

I guess Mobile Odin and this are the only ways in my case.
[Galaxy S II Android Development] cdaarif:
ok man i don't get bootloop. Surprised ha, only i don't get bootanimation in neatromLPZ with 4.1.2 jb gapps but android is upgrading in touchwizUx 1.5.1. Some apps run some don't, gallery, camera, titaniumbackup, solid explorer, oi filemanager etc. They don't get sdcard !!! Can u plz check the cod of sdcard. Sometimes phone hang 3to5 sec, sometimes autobrightness select automatic. These r the problem.

sorry for my bad english.
[Galaxy S II Android Development] yahyoh:
i used the odin kernel to root the JB leak and there is no super user in device after reboot :silly:

any way thank u :good:

edit : i flashed the CWM SU and every thing working now

edit2 : tingle away working too :victory:

thanks alot and thank to CF :cool:
[Galaxy S II Android Development] Phil3759:
you are amazing in fact :laugh:

But I do not think it would be stable for daily use

I won't check anything for such an hybrid setup. Things work perfect if you flash everything from JB. Since the mount path changed for sdcard, if you mix things you get issues

Please just read carefully post 2, it is important before flashing things

short answer: odin packages are not pre-rooted and need an extra step. Use the zip ones from recovery if you are unsure
[Galaxy S II Android Development] Phil3759:
all these wipes are useless because XXLSJ leak is a wipe rom with data partition
[Galaxy S II Android Development] ionutzvio:
+1

@Phil3759

i have some nandroid backups made with cmw 6 in my phone. can i resore them with your recovery? are they safe? and if i falsc cm9 or 10 do i lose your recovery with cmw 6?
[Galaxy S II Android Development] Phil3759:
You can restore nandroids of course. My cwm6 is before everything a stock based cwm6

And if you flash another kernel, you will loose my recovery since our phone doesn't have a dedicated recovery partition
[Galaxy S II Android Development] itchetrigr:
thanks for the great work Phil3759

one thing to note

system/app folder are only symlinks to preload/symlink/system/app which means nandroids of XXLSJ wont work...

just tried a restore of a nandroid twice and ended up in a bootloop....
[Galaxy S II Android Development] King_Rat:
Thanks @ dev ^^

Q: So we can restore other rom nandroids but not a nandroid for leaked JB?
[Galaxy S II Android Development] Phil3759:
Will look at it. Koush just updated cwm to fix issues on jb and its new paths
[Galaxy S II Android Development] Damienoid:
Can someone confirm for me please, I have wanam 12.3 LPT build, which kernel should I use for my rom?
[Galaxy S II Android Development] JulianXhokaxhiu:
May i ask you where are the sources of your latest kernel?

BTW thanks for your great work and your latest kernel for JB ROM :)
[Galaxy S II Android Development] Phil3759:
Samsung sources. No recompile from source at all, it is original kernel untouched from Samsung
[Galaxy S II Android Development] King_Rat:
[Q] CWM compatibility

Does CWM.apk work with this kernel??
[Galaxy S II Android Development] Phil3759:
I do not support cwmmanager, try it at your luck and do not feedback or ask for support about it here please

Chainfire does not allow redistribution of the apk, so you are on your own and should stick to cf-root to use it
[Galaxy S II Android Development] Phil3759:
XWLPT
[Galaxy S II Android Development] Phil3759:
I fixed the nandroid restores

A new update will be posted soon, by end of day I hope
[Galaxy S II Android Development] hawkerpaul:
I can't seem to search on here for BLN, so is this enabled in your kernel Phil? (apologies if its been asked before)

If not, will you have any plans to do so please?

cheers.
[Galaxy S II Android Development] Phil3759:
No and no

No recompile from source planned
[Galaxy S II Android Development] Phil3759:
:eek:

XXLSQ is out and you ask for XXLSK?
[Galaxy S II Android Development] electricsheepdreamer:
OK. Just a small update from my side. After 2 days of running 5.11.2. (Flashed tar version via Mobile Odin) on NeatLite 4.8. (XWLSW based ROM) no issues yet.
[Galaxy S II Android Development] Phil3759:
Thank you

XWLSW here too. Despite my phone hangs all the time as it seems semi-dead, and I have to force reboot it all the time, I did not face any boot stuck issue
[Galaxy S II Android Development] pdario:
Thank my operator and Samsung for caring so much for 9100P.

I would like to start with a full LSK rom/kernel and then check if the latest 9100 kernels keep NFC enabled.
[Galaxy S II Android Development] android.racer:
same for me!
[Galaxy S II Android Development] FNTOG:
+1
[Galaxy S II Android Development] Phil3759:
would be better to update your ROM instead of using a probably semi fix
[Galaxy S II Android Development] bodomfan:
Is 5.08.5 the more stable release
[Galaxy S II Android Development] kt-Froggy:
Yep, that's right. An inconvenient, no doubt, but minor glitch. A problem which can be solved as easily as restoring from a nandroid backup is far from a brick, which, by definition, turns your phone into a paperweight.

BTW, Phil - LSD here (Disaster v.10), no problems within 2 days with 5.11.2. No particular testing, but multiple reboots. Smooth flying so far. Battery life is pretty much the same as it was before on 5.10, and earlier on Apolo.
[Galaxy S II Android Development] Mikros:
How can i upgrade but keep supersu and not install superuser? I read something about philz_installer.cfg but where do i find it?
[Galaxy S II Android Development] electricsheepdreamer:
There's a link in post #3 above the latest versions download link.
[Galaxy S II Android Development] Coempi:
Same scenario with me. Battery drain is higher at the moment, though, but I will wait for a few charging cycles.

Best regards, Coempi
[Galaxy S II Android Development] electricsheepdreamer:
Just a quick update from my side.

Yesterday, after a few days of trouble free use, I was running on 1% of battery, needed to do few things quickly and did shut down after. I thought it was done properly but after swapping a fully charged battery and powering on, I got stuck on Samsung logo but this time couldn't reboot successfully by shortly holding the power button.

Rebooted in Recovery, mounted data and it booted again but the phone spontaneuosly rebooted itself shortly after and hanged at Sammy logo. Then I tried a few things but nothing helped.

Restored nandroid backup with v.5.10. Everything works fine ever since (as it has been for past few months).
[Galaxy S II Android Development] asrock37:
I think it is because you have corrupted data, by clearing or wipe data it will fixed the issue. As you have said, you're doing something and suddenly it will shutdown, so that means that writing in your data is not complete.
[Galaxy S II Android Development] electricsheepdreamer:
Hey, I agree, it must have been some kind of data corruption going on.

Just wanted to make clear (from my previous description) that it didn't suddenly shut down. After I was done with what I had been doing (copying some small files from external to internalSD) I did power the phone off manually. (At least I thought so). Also it auto shuts down itself when the critical battery level is reached. But something somehow went wrong in this case.

Anyway, AFAIR I read Phil mentioned before that fixing for bootloop won't prevent data corruption but make booting possible in spite of data corruption being done.

To be honest, I'm not sure what exactly happened and if it is an isolated case (not very eager to double check) but from my previous experience with Sammy's stock based ROMs and fixed for bootloop Philz kernel (and I abused my S2 far worse than this time) before mentioned theoretical data corruption never created a single issue.

So the bottom line I could draw from this experiment is that during the regular use and being careful to have a safe amount of a healthy battery all the time, everything is fine. One can always perform wiping data, OFC or restoring nandroid backup in case something goes wrong.

But fixing for bootloop somehow always did the trick in the most direct, easiest way, in my experience at least.

Just my cent.
[Galaxy S II Android Development] Phil3759:
I can revert and patch for bootloop again as it was reported by many now

Crazy Samsung, they really do not care