yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] neerajganga:
here are some more

u can bookmark dem :)

http://obihoernchen.net/downloads/?dir=SGS2 Modems

and

http://xdaforums.com/showthread.php?t=1131950
[Galaxy S II General] dptnl:
Is there any ICS theme available yet for this great firmware?

I had this in the past

http://xdaforums.com/showthread.php?t=1334922 but googling UHLPS shows it is related to 4.0.3 and all other builds are misleading - do I need to search for xwlpm instead?
[Galaxy S II General] Extend:
1st Thank you

I went through the ROOT/UNROOT guide, downloaded the files to SDCARD booted into recovery mood and when trying to access the SDCARD the following message appears E:failed to mount /sdcard (No such file or directory)

What do you think, i'm very disappointed :(
[Galaxy S II General] EARNEST_EU:
I see, thanks. Is it safe to root this ROM with this kernel CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip ?
[Galaxy S II General] Tungstwenty:
If all you want is root, it should be: just flash that zip, boot once with it, and you'll get root. Then flash the stock kernel again.

If you want to permanently have a custom kernel, with CWM recovery, I don't know if

a) that one works with LPM and

b) CAP_ERASE has been fully patched so that using CWMR is safe - it *might* be, but since it wasn't built from sources, nobody is 100% sure
[Galaxy S II General] It_ler:
I am using this CF-Root v5.6 for XXLQ5 on my XWLPM ROM rigfht now.

After first boot, I had some issues (FCs and camera bug).

Then I wiped cache, Dalvik cache and fixed permissions in recovery mode, now everything works fine - even the camera.

Haven't tested Bluethooth yet, as I do not need it.

Only serial number is shown as 00000000 ... but this is not so important IMO.

---------- Post added at 10:14 AM ---------- Previous post was at 10:10 AM ----------

In recovery mode:

Have you already tried to "apply update from internal storage "?

Maybe the sdcards (internal/external) are mixed up.

Is there an option for mounting sd cards/stroages?

Maybe you have to mount the sd card before.

Sorry, never had this kind of issue before.
[Galaxy S II General] Extend:
I never tried the method "apply update from internal storage" before , There is not option for mounting sd cards/storages in the recovery mode , do you think that i might test using external sdcard? get one from a friend and test?

Thx
[Galaxy S II General] It_ler:
Yes, good idea.

As I have an external sd card, I always put some files on internal and some on external sd card. So if I can access one sd card, I don't bother about mounting the other one.

In one rooting guide I read that you should store all files on the external sd card. Maybe that will work on your phone.

Good luck !
[Galaxy S II General] EARNEST_EU:
I just followed the root/unroot guide. Worked like a charm. Going to test the phone now
[Galaxy S II General] lavazzabg:
This russian 4.0.4 rom is really bad in IO operations. Quadrant shows how slow it is best. Pretty bad because it reminds me the IO lag of 2.3.6. XXLPG was superb :( Other than that the visual additions are more than welcome and very good.
[Galaxy S II General] It_ler:
My kernel/ROM tests show nearly the same result for XWLPM => http://xdaforums.com/showthread.php?p=26775950

Good ROM, good battery life, subjective smooth, but some benchmarks show low results.

Only the Vellamo (browser) benchmark got best result of all tested kernels/ROMs on my phone so far.

So everyone has to decide, what is more important: New features/having the most recent firmware, or benchmarks results/best performance in IO operations.
[Galaxy S II General] metzo32:
Hey guy's ..After reading a lot's of threads ,still you can flash and root this ROM

But ,still nothing out for kernel or permanent CWM work with it too ! is that right ?

So, can't install anything to this stock ROM through CWM ?
[Galaxy S II General] MaKTaiL:
Yes, stay away from CWM. Using stock kernel + stock recovery is fine.

If you want to flash a custom ROM, first flash an 4.0.3 firmware through Odin (not Mobile Odin).
[Galaxy S II General] metzo32:
Yep, I see Thanks..I'm on custom ROM now, But would like to give it a try ,best root is

Root/Unroot way..then I want try Dnight kernel to see how it goes

Sure I'll not use stock to wipe ,better to install any kernel to wipe through it to go back .
[Galaxy S II General] It_ler:
Stock recovery is safe.

If you flash DarkKnight kernel on XWLPM ROM, you will have root and permanent CWM recovery.

Most custom kernels have "safe" CWM recovery too, but you should check the corresponding kernel thread to be sure.
[Galaxy S II General] EARNEST_EU:
Is there a way to install an octo/8way locker?

PS: the contact list bug is still present.... Bloody Samsung
[Galaxy S II General] MaKTaiL:
What bug?
[Galaxy S II General] khal_nayak:
after reading a lot of threads and posts, this is what i udnerstand, plz correct me if im wrong

- this LPM 4.0.4 ur not supposed to flash if u come from some custom rom or will result in brick so to be safe ur supposed to goto some stock firmware and then PC odin to flash this LPM

- CWM will brick ur phone if u flash this LPM and use CWM to reset or restore

what i dont understand is after we flash this LPM, can we use siyah kernel and then use CWM to atleast clear cache and dalvik and factory rest device and even if ppl who want to goto their older rom using CWM restore would it be safe if using custom kernels like siyah etc?

the main issue is ppl trying to restore or go back to 4.0.3 or some custom rom once they have tried this LPM and due to the kernel flag it results in brick but is it safe for ppl like me who r currently using LPG and would want to goto LPM and i restore my contacts, sms, apps etc using titanium backup and some other apps
[Galaxy S II General] chris3lx:
Thanks for your help. I flashed LPM with the latest cf flash 5.6 with no problems. Had to wipe cache, dalvik cache and fix permissions but now everything is working great.
[Galaxy S II General] EARNEST_EU:
I remove SIM contacts from the list of contacts to display, yet, they still appear
[Galaxy S II General] metzo32:
So, any of the mods ,themes, toggles are working with this ROM please.. ?

I mean compatible with 4.0.4 ?
[Galaxy S II General] Tungstwenty:
The problem occurs if you have the stock kernel and execute the CWM recovery under that kernel.

If you install Siyah, the kernel will no longer contain the "CAP_ERASE problem" and therefore data wipes are safe (including from the CWM included in Siyah).

Think of it like this: CWM asks for wipes to be done, and the kernel handles those requests. However, the stock kernel doesn't handle them in a safe way - it's a kernel bug, altough it might look like it's CWM's because he's the one asking for the wipe. If the kernel didn't have the bug, CWM's request would work with no issues. Using Siyah instead of the stock kernel, you'll have a kernel that handles those requests safely.

The problem with using Siyah or any of the other custom kernels is that they don't yet fully work on 4.0.4 and there are identified issues with: Camera preview, Video playback, Bluetooth (and perhaps one more thing, I don't remember).

Currently there's a fix for Camera and Video but not for Bluetooth.
[Galaxy S II General] It_ler:
Have a look here => http://xdaforums.com/showthread.php?t=1756242

There is a description how to brick your phone with XXLQ5 ROM (is similar to XWLPM for that issue).

And how to avoid the brick.

With most recent custom kernels (such as Siyah) you are "safe".

And Chainfire also povided a CF-Root kernel for XXLQ5 which is "safe" => v5.6.

And stock recovery is also "safe". Only ""unsafe" custom kernels and injected CWM may brick your phone on XXLQ5 (and XWLPM) when wiping or restoring.
[Galaxy S II General] ricnar456:
Cwn has the bug, recovery stock call wipe in right way and have no bricks at all, using 4.0.4 kernel.

Cwn need make calls for wipe like recovery stock, and all will be perfect.

WIPE FROM RECV STOCK + KERNEL 4.0.4 = NO BRICKS

WIPE FROM CWN + KERNEL 4.0.4= BRICKS

CWN need to be changed for wipe like recovery stock.

ricnar
[Galaxy S II General] combat44:
WIPE/BACKUP/RESTORE FROM CWM + KERNEL Siyah (N.E.A.K, Phenomenal, etc.) = NO BRICKS
[Galaxy S II General] metzo32:
So, how to keep permanent CWM after rooting the ROM then, how to install mods etc...?
[Galaxy S II General] ricnar456:
But Kernel 4.0.4 is oficial samsung code, and cwn not.

Cwn has to change, samsung will not change anything the first kernel not compatible with cwn was released a month ago was LQ3 for NOTE, and continue releasing the same kernel in a lot of countries, without problem, now 4.0.4 has the same kernel not compatible with cwn.

Cwn is not samsung code, samsung is not responsible or guilty for the damages made from wiping from cwn, only for damages made from his own code=> CWN need adapt to OFICIAL CODE not OFICIAL CODE adapt to CWN.

ricnar
[Galaxy S II General] Tungstwenty:
I don't know the CWM code, but I agree with your general idea. If the wipe function could be done in the same way as the stock recovery, perhaps it could be changed to work in the same way.

BUT, on the other hand, CWM has much more things - nandroid backup and restore, zip install, etc. If CWM is changed to be like the stock recovery in every way, no more extra features so we might as well use the stock recovery :)

Only someone that is more or less involved in CWM development would be able to comment on whether the wipe function could be changed so it doesn't generate problems even with these not-so-robust kernels, just like the stock recovery (allegedly) doesn't...
[Galaxy S II General] MaKTaiL:
You said everything. If Sam wants to keep this firmware they must have a good reason.

We must change the kernels to remove EMMC_ERASE or modify CWM to suit our needs without briking devices.

I'm quite happy with Stock now, so I'll keep from flashing anything.
[Galaxy S II General] ricnar456:
But all bricks are from wiping from cwn, i don't hear of bricks using cwn in orher ways => if cwn change the wipe part only, avoid the risk and can be safe used in all ways.

ricnar
[Galaxy S II General] Brotuck:
The reason why siyah is now "safe" is because one driver has been left out.

I think chainfire did the same in the modified cfroot.

I do agree with ricnar456 that the issue should be solved in CWM and is not to be expected to be fixed from Samsung.

Basically Samsung has no problem, we create a problem when we try to mod the phone by adding CWM.
[Galaxy S II General] Mittaa:
I would really like to hear some comment from Koush (Koushik Dutta) the creator of CWM and Rom Manager :)
[Galaxy S II General] ricnar456:
The millons of normal users who update to 4.0.4 from OTA or KIES in SGS2 and NOTE have no bricks at all (0%)

The ton of bricks are tech or mod users (XDA or other MOD forums) who use cwn.

Sansung will have a problem if the group millons of common users brick cells, not for a little group of mods who use mods and not oficial code.

Is a pity but is a fact.

ricnar
[Galaxy S II General] Mittaa:
Have recovered from nandroid a few times without any problem (I have this bad chip too).

Last time was from leaked I9100XXLQ5 Open Europe back to I9100UHLPS Argentina.

Does Rom Manager always wipe when recovering from one firmware to another?

Or is it only when you tick "Wipe" that brick could occurs?
[Galaxy S II General] ricnar456:
only the author of cwn can reply this.

we only know the stories of persons who brick their phone and all tell was wiping from cwm.

ricnar
[Galaxy S II General] metzo32:
So, the best way Now, just to root and keep the stock kernel as it is ?
[Galaxy S II General] khrone:
So its safe to use LQ5 stock after i do complete wipes and formats of phone prior to odin ? Safe to use latest siyah?
[Galaxy S II General] cpl.Bower:
he dont give a ****...

Wait... It was SAMSUNG who build the phone with a FAULTY eMMC chip, not US, neither the CWM author. They MUST fix this thing, somehow
[Galaxy S II General] Mittaa:
Why do you think that? Out of experience?
[Galaxy S II General] ricnar456:
but you cannot break with stock code, the emmc chip is a internal spec and cannot be changed, only avoid the problem, while you cannot break now with stock code, samsung avoid the problem, cwn need avoid the problem now

or do you think samsung will repair cwn code?

Samsung has no problem, when the phone can be breaked with stock code, start the problem for samsung otherwise not problem at all.

ricnar
[Galaxy S II General] darkcossack:
The emmc chip might be an internal spec however the CAP_ERASE problem is a problem in the stock kernel's code. The only firmware that has bricked phones has been due to this faulty code (and in all instances, IIRC, it's been with leaked firmwares!)

No, Samsung won't repair CWM code - but knowing of the emmc issue, it should have set the CAP_ERASE value to 0 in the stock kernel.

ffs it's cwM, not cwN!
[Galaxy S II General] vassall89:
Can i flash lpm over lq5 without any issue?
[Galaxy S II General] MaKTaiL:
Yes.
[Galaxy S II General] xpresservers:
Is it safe to flash mobile using mobole odin and lpm formware? Mobile odin can inject root while flashing. Currently i have i9100XWLPG (4.0.3)
[Galaxy S II General] khal_nayak:
thanks for the info so other than that, is LPM more fluid and battery efficient than LPG?
[Galaxy S II General] Extend:
It works :D , 1st i would like to thank you very much for guiding me through my problem, i followed the same steps on the ROOT / UNROOT guide, was able to fix the Security --> Screen Lock

It seems that i have a problem with IMEI due to old upgrade from 2.3.3 to 2.3.5 as i do not receive software updates via OTA or KIES, i do not have a backup of the efs partition to recover the IMEI number.

Last question what is the different between rooting using the busybox thing and rooting using a rooted kernel? what is the advantage & disadvantage.

Thx
[Galaxy S II General] ricnar456:
maybe this value is used in other ways in new kernels and cannot be disabled, cwn need to change, if you don use cwn don't have bricks.

ricnar
[Galaxy S II General] tylerdurden83:
You need to get your stuff fixed.

It is called CWM, not CWN

There are reports of russians bricking their device using STOCK recovery, not CWM. So stop advertising that STOCK recovery is safe, because it isn't, it just has a smaller chance of triggering the brick.

It IS Samsung's fault. CWM triggers a wipe using what the kernel says it should do, and so it does. It's not CWM's fault if Samsung sold us phones with a malfunctioning hardware inside them. Samsung can't sell phones with a broken emmc chip and then put the instruction to brick it in their official kernel. If they really want mmc_cap_erase to true in their official kernel, they must first fix their faulty emmc hw with the proper fw upgrade.
[Galaxy S II General] Tungstwenty:
Here's another example, hope it helps understand the issue and the 2 different opinions :rolleyes:

Imagine we were talking about the display instead of the emmc chip. Now imagine that the hw of some units is somewhat faulty and if a certain color such as green is displayed with max brightness for more than 5 seconds, it will permanently damage the display.

Samsung has prevented problems by having the driver slightly reduce the brightness in those situations, as a workaround for the faulty hw, so that game developers don't damage the displays as a secondary effect of some game that chooses to display the entire screen in green whenever you win :D

Now, in *some* of the official ROMs (in particular the kernel part) they ended up not including this protection of reducing the green brightness. It's something the custom kernel devs have already learned (the hard way) so their kernels are safe, but Samsung occasionally lets out official builds that don't include the protection for the faulty hw.

Whose fault us it for damaging the screen?

Is it the game/app developers for coding something according to the chip specifications and expecting to work properly?

Or is it Samsung's for having faulty hw (it happens) but not building in the properly safeguards (must not happen)?
[Galaxy S II General] ricnar456:
-------------------------------------------------------------

leolysenko	11th July 2012, 03:42 PM (Last edited by leolysenko; 11th July 2012 at 03:38 PM.) #7484

Member

Thanks Meter 21

Posts: 51

Join Date: Mar 2012

Location: Moscow

MORE INFO >

Quote:

Originally Posted by Dimer81

As i understood, there r reports of bricks with the stock recovery on LPM

Response:

I know lots of bricks in our russian forum 4pda.ru since XXLQ5 was leaked. About 10 I guess, maybe even more. Plus I have seen two bricks here on XDA. All of them were bricked with original kernel +CWM.

--------------------------------------------------------------

Posted By leolysenko

Exactly. No bricks on stock! I am that russian :D...

Exactly. No bricks on stock! I am that russian :D

-----------------------------------------------------------------------

Stop telling lies, there are NO reports of russian forums of bricks using stock, a member of this russian forum, come to xda, and some post back, denied this version and tell all bricks was wiping from cwm.

ricnar
[Galaxy S II General] tylerdurden83:
Also read what tungs wrote, you still think it's ok for samsung to sell broken chips to us and not release the fix?
[Galaxy S II General] ricnar456:
Put me a link to one case broken with wiping from stock, forget the russian forum this was denied from a member of this forum, and forget repeat others words, put a direct link to ONE only case.

The note problem was similar only wiping from cwn is the problem I read all the cases, and no problem at all if you don't use wipe from cwn and i flash the note of my chief twice with two different "brick" roms and wiping two times from stock recovery and perfect. (i read carefully case by case i don't want to be fired hehehe)

ricnar
[Galaxy S II General] Brotuck:
Offcourse Samsung needs to builtin this protection again.

On the other hand, why should they ? There is no need for it when staying on stock firmware. Because no major problems are reported here.

But this seems to be a never ending story, it would be easier to update CWM.
[Galaxy S II General] lavazzabg:
Gyus, does someone has auto brightness bug ? .... My cell twice or more a day unticks auto brightness to static. It is so annoying.

Im talking for 4.0.4 Russian rom. Didnt have this problem with XWLPG :(

10x in advance.
[Galaxy S II General] drelite08:
Are you using a custom kernel? I have always had that on occasions with custom kernels on other roms.
[Galaxy S II General] lavazzabg:
No, im using stock kernel. I dont root or change kernels/roms.
[Galaxy S II General] sianzb0i:
can i use a ROM from a different region? where do i find the CSC for my region to extract and use.

For example i wanna flash XWLPM but my CSC is OLBxxx
[Galaxy S II General] It_ler:
First of all: I am glad that you could solve the issue.

Advantage/disadvantage of a rooted kernel ... this depends on the kernel an what features it brings.

CF-Root is more or less a rooted stock kernel, adding BusyBox, SuperSU, CWM recovery and CWM Manager app.

If you like this features, use CF-Root kernel to get rooted.

Other kernels have other "extra" features - look at the kernel feature list ... usually in the first post of the corresponding kernel thread.

Disadvantage ... some kernels are only compatible with special ROMs / ROM versions. And you will lose/replace the stock kernel.

Some custom kernels may be "unsafe", and may lead to a brick.

If you flash a rooted / unsigned kernel with Odin, you will get a yellow triangle at boot and the flash counter will be increased.

So, you have to think about getting rid of the yellow triangle and about reseting the flash counter (for ICS ROMs use TriangleAway app).

That are the main advantages/disadvantages of flashing a rooted kernel IMO.
[Galaxy S II General] leolysenko:
Sure you can. Flash the XWLPM Rom and after that flash your region CSC separately. You can extract the CSC simply from any fresh firmware from your region. To extract you have to open the ****.tar.md5 (firmware file) with WinRar or 7zip and copy the file named cache.img - this is the regional settings file you need.
[Galaxy S II General] sianzb0i:
Thanks. So cache.img is the CSC. Learnt something new.

Sent from my GT-I9100
[Galaxy S II General] lyriquidperfection:
You also need the hidden.img which is also part of the csc. Contains the user data apk's such as swype which I believe is also region specific.
[Galaxy S II General] igos2:
Is any stock CSC files compatible with any stock rom ?

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II General] timberwolf60:
You can used xxlpw csc for UK, Germany etc. Oxx CSC for Nordic countries etc. Used CDC select to change the code. This will wiped your data. So backup, backup first.

Send from my GT I9100 using Tapatalk2, 1st ROM Paranoid V1.6a, and 2nd ROM XXLPW, Siyah 3.3.3d kernel, jkay 14.1 mode.
[Galaxy S II General] lyriquidperfection:
Yeah pretty much as long as its for same device variant.
[Galaxy S II General] habibjamil:
Where do I copy the file cache.img on the device? Which folder?
[Galaxy S II General] milu_m:
Depending of what you use for flashing. If Mobile Odin then you may have in anywhere on your mobile device. If you are using Odin on PC then you must provide CSC in correct window. To make CSC you should take cache.img and hidden.img and combine them into one tar file. In Linux you'd do this:

tar cf csc.img cache.img hidden.img

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II General] Batskoning:
Installed this XWLPM and now it's booting..

How long does it normale take to boot..?

Now it's showing Samsung Galaxy SII, with the S glowing/shining :p

I hope it's not broken or something.. So, how long does it take to get past this S..

Greetings..
[Galaxy S II General] maysider:
czech language

I presume there is any language.....even czech language?

any problems so far?

thx
[Galaxy S II General] It_ler:
A few seconds.

If it stucks at boot logo, try to long press the power button and reboot again.

If it does not help, try to boot into recovery mode (press Volume UP + Home + Power till the recovery menu appears), wipe cache and reboot again.

If that does not help either, try to flash the ROM again.

Good luck !
[Galaxy S II General] Tungstwenty:
It's almost that...

tar [COLOR="Red"]-H ustar[/COLOR] [COLOR="red"]-[/COLOR]cf csc.[COLOR="red"]tar[/COLOR] cache.img hidden.img

The file should be in the ustar format. The extension, although it can be anything you want, should be .tar instead of .img so that you know it's an archive file.

Additionally, if you'd like to add an md5 checksum in the end (not really needed, more useful if transferring over the web), you'll also need to run this afterwards:

md5sum -t csc.tar >> csc.tar
mv csc.tar csc.tar.md5

The md5 extension lets Odin know that in the end of the file there should be a block with the signature and it validates whether it matches the archive contents.
[Galaxy S II General] lavazzabg:
Hello guys.

Does somebody has the same problem with 4.0.4 XWLPM:

When i put my phone on charger it doesnt turns off the display after 30 secs. It stays alive until i lock the device with the lock button.

When i disconect the charger it gets normal. Very annoying :(
[Galaxy S II General] It_ler:
-1

Can not confirm.

I just set the screen off time to 1 minute and plugged the phone on the charger.

After a minute, the screen is black now.

So, everything OK on my phone (running stock XWLPM with CF-Root kernel v5.6 for XXLQ5).
[Galaxy S II General] Nepyk:
Is LPM safe firmware or is it with similar problems as LQ5?. Can I use CWM after flashing it?

Thanks
[Galaxy S II General] It_ler:
I recommend no to use injected CWM ... only use permanent CWM of a "safe" kernel, such as CF-Root v5.6 (and most of the recent custom kernels).
[Galaxy S II General] EARNEST_EU:
I installed the stock ROM. Then I installed CWM and busybox zip files as per root/unroot guidelines. And then installed the Siyah 3.3.3d kernel. Works like a charm. No problems