yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] Tungstwenty:
All 4.0.4 stock kernels (XWLPM, XWLPO and the previous leaked LQ5) have it enabled and can therefore lead to bricks.

---------- Post added at 02:34 AM ---------- Previous post was at 02:31 AM ----------

I didn't have a chance to look at it yet.

Being a 4.0.4 build, the code changes against e.g. XWLPG should be a lot, even if they are not important - which makes the identification of relevant changes much harder than in incremental builds.

I'll try to have a look specifically at EAS when I have some time, though.
[Galaxy S II General] SaneinOne:
I'm experiencing issues with text selection and some MP3s not playing.
[Galaxy S II General] lsv-1:
What youtube problem bro?

---------- Post added at 08:12 PM ---------- Previous post was at 08:03 PM ----------

Can I root XWLPO using the method posted on this thread http://xdaforums.com/showthread.php?t=1501719 without exposing myself to a hard brick? Thank You.
[Galaxy S II General] jlevy73:
Thanks for the link
[Galaxy S II General] catalin.anghel:
Hi guys I have a simple question :

It's safe to use stock XWLPO whit out any other modem or kernel?:confused: because from what I understand from this posts is not safe to use.

I tested the 4.0.4 Russia and I didn't have a problem whit that until I used titanium backup and I have problem whit the root:(
[Galaxy S II General] aakib:
yeah it is dead safe for u to install LPO... i was scared before installing it... but now em loving it... everything works like a charm... really awesome rom...!!!

& if u wanna root, using the injectable CWM method... its the safest... i've done it myself... so it wont gonna brick your SGS2... :)
[Galaxy S II General] catalin.anghel:
Thx AAKIB for information, I will try today this ROM and will come back whit impression
[Galaxy S II General] Brotuck:
@Tungstwenty

If the code in the kernel has no safeguard built in, but Samsung releases official 4.0.4 firmware anyway. Now in Russia and in the Nordic countries.

Doesn't that say that the brick chance with only stock stuff is minimal ?

I mean the number of SGS2 users in those 2 countries alone are huge.

If lots of devices would brick from stock-only stuff then repair centres there would make overtime to fix those phones by replacing the mainboard.

I read that the Galaxy Note also has the same "problem" with newer firmwares. So i guess they would know that something is wrong by now..and fixed it.

It is interesting to know if Samsung even considers this "flag" as faulty.
[Galaxy S II General] Goldie:
Anyone on LPM who is willing to test the S3 lockscreen for me please PM me. You need to be able to rescue yourself should get loops or whatever :)

Thanks...

https://www.youtube.com/watch?v=LSaZ5AzROe8&feature=youtube_gdata_player

https://www.youtube.com/watch?v=ICt0_fWRZTU&feature=youtube_gdata_player
[Galaxy S II General] mcmanuf:
RIL and Modem version

Hello.

Can someone please run this program and tell me which RIL version the phone has?

https://play.google.com/store/apps/d....sibbor.getril

I have tried installing the LQ6 modem on my SGS2(the same modem as the XXLPO release) but it says the RIL and Baseband(modem) does not match.

My baseband is currently XXLPX.
[Galaxy S II General] me_max:
About 2)

I don't really see a bug there as you simply can use your hardware-back-button
[Galaxy S II General] drelite08:
It's the easier way, and I've always done that too :D
[Galaxy S II General] ricnar456:
Is not possible brick using only stock this was discussed some pages back, only using cwn.

ricnar
[Galaxy S II General] maortrol:
Got some questions: ¿did anybody tested SiyahKernel 3.4.1 for SGSG2 i9100 with LPO rom? ¿Is everything working fine with it? ¿Is there brick risk using SiyahKernel 3.4.1?

http://www.gokhanmoral.com/

Thanks in advance for your answers... :D
[Galaxy S II General] Dasmikko:
Just make 100% sure, is it safe to flash through odin when i'm on LPO with siyah kernel and do a downgrade if needed?
[Galaxy S II General] milu_m:
I have currently RIL Unknown and Baseband I9100XXLQ6. Probably because it isn't yet in database of known RIL's.
[Galaxy S II General] cpl.Bower:
Where is that flag? Offset and Instruction
[Galaxy S II General] ricnar456:
you can change the flag but you don't know if the flag are used in other parts of the code for other differents tasks, maybe you can corrupt them.

ricnar
[Galaxy S II General] GregX80:
Guys can somebody please tell me if is battery life any better in 4.0.4 than in 4.0.3?
[Galaxy S II General] afiqsabri:
is the new rom working with siyah and speedmod ? usually, they wont, i have issue with xwlpm xxlq6, camera and video no live preview:(
[Galaxy S II General] cmvcarlos88:
Hi, i´m using LPO and i want to know if like wanam said in his thread i can flash or wipe with cf root lpg. He said that to come back to 4.0.3 if we are on 4.0.4 is: flash cfroot lpg with odin and then i can wipe and install any rom or restore a nandroid. Am i ok? I want to flash lidroid´s mod for lpm to this lpo and i want to be sure before doing anything.
[Galaxy S II General] gevans35:
It seems much the same to me.
[Galaxy S II General] coolbuddyin:
If i update via OTA,will i loose root?
[Galaxy S II General] It_ler:
Have a look at my thread => http://xdaforums.com/showthread.php?p=26775950

On my phone, XWLPD has best battery life so far.

XWLPM is a little bit worse and XWLPO (on first battery cycle) has even worse battery life. But still OK, compared to other stock ROM versions.

Depends on many different influences ... that's my experience so far.
[Galaxy S II General] neerajganga:
i think yes
[Galaxy S II General] Tungstwenty:
I became aware of this whole issue back when there were reported bricks from a few people (dozens, hundreds ???) due to running custom kernels that were using released kernel sources and that somehow they decided or missed a change in the erase thing.

What I mentioned before about stock recovery is that I *think* it still has its risks, altough they're perhaps lower. That doesn't mean the kernel is safe, but maybe the probability of it happening is smaller.

The way that I think the updated LQ5 CF-Root minimized this was changing the bundled CWM recovery, not the kernel itself.

While I agree with you, I also think there are 2 important factors that lead to no known reports of bricked devices in stock recovery:

1. If a full partition erase is only performed on /cache and not on /data (for example), given the fact that the cache is 100Mb and the data is 2Gb the odds are different. Plus, AFAIK there were people with the vulnerable chips that ran data wipe and didn't happen to have problems. So, it's a probability and perhaps in stock recovery it's even smaller

2. How many power-users are there that use stock recovery? I'd say that if they're power-users, the big majority of them will be running a CWM or even a custom kernel.

And for whoever only has stock everything ("careful" power-users + regular users), what are the odds that they in fact use recovery to do wipes?

Furthermore, if they do end up with a problem, are they likely to post on forums (regular users at least), describing something they totally don't understand? IMO they'd be going to customer support and not even be aware of what happened.

Anyway, I'm not at danger myself but given the fact that I inspected the code, just thought I should leave the warning.

The fact is that I don't have proof that it can brick; just a strong hunch (of a probability that can be smaller, true) that it can still occur.
[Galaxy S II General] tariq2kn:
I'm getting very good battery life.

Phone: XWLPO

Modem: XXLQ6

Kernel: Siyah 3.4.1

Launcher: Apex 1.2.4
[Galaxy S II General] Gillion:
Let me condense to the most important thing you wrote for this particular post.

Hahahaaa...

OK son...

Samsung is not doing anything wrong in releasing the ROM's as they are.
[Galaxy S II General] Brotuck:
I think this part is the most important thing.

When users are rooted they can become a victim of malicious software.

Not saying that CWM is malicious, but the risk is definitely there.

Even if stock kernel is not able to brick the phone, it still is possible to do so with any app.
[Galaxy S II General] xpresservers:
Is it safe to flash XWLPO with Mobile Odin? Any chances of brick? Do I need separate modem, kernel or firmware itself have modem and kernel ?
[Galaxy S II General] tylerdurden83:
This attitude towards Tungstwenty? Really?
[Galaxy S II General] maortrol:
¿Does anybody have a link for downloading XXKG5 modem in .tar (ODIN flashable) file? I can't find it...

I'd like to test it in this LPO rom... LQ6 modem seems to drain battery for me... :(
[Galaxy S II General] Gillion:
An interesting question is then: does Samsung know which carriers and regions have the phones with the faulty firmware and ... would they release a ROM via kies for that Carrier and Region, knowing the eMMC feature is enabled and likely to brick a phone made for that same carrier and region ?

OR does the e3 boot utility, when asked to wipe a phone, brick said device ?

Is Samsung willing to replace phones damaged via a Carrier/Region Kies authorized update ?

The way I see it... if you go through Samsung official procedures (and don't void the warranty by installing custom ROM's or rooting the device) then nothing should go wrong. If it does they (Samsung) should immediately replace the device.

I have seen no reports of ordinary users who update through Kies destroying their device doing a wipe with these ROM's

It is mostly us ... the people who do things that Samsung does not want us to do... that are feeling the pinch.

The alternative is to wait for a ROM from Samsung that is made for a Region or Carrier known by Samsung to have a batch of phones with the eMMC firmware bug.
[Galaxy S II General] jenskristian:
It's safe and you only need the one file. I did myself yesterday.
[Galaxy S II General] It_ler:
If you don't want to flash the modem as zip file in CWM, then use Mobile Odin app and a stock ROM tar file, which contains the modem you want.

With Mobile Odin app, you are able to select only the modem of a ROM and flash it.
[Galaxy S II General] Tungstwenty:
Interesting point.

I do have some doubts however that they have deliberately shipped the defective chips to "contained" areas. They should be pretty much spread across the globe. Perhaps on the variants (HK, USA, ...) it could be more controlled, but for the general I9100 I'd guess there's no such correlation.

If you go through the official procedures - Kies / OTA, I'm not sure whether there will ever be any wipe (or specifically, erase). Also, those ordinary users as I mentioned before, are likely to go directly to the repair center and not post in forums, *IF* they do get the bricks. Remember that they aren't flash/wipe-holics like us :) so even with faulty hardware + unsafe driver they could only very rarely suffer anything.

Another possible option would be to binary patch the kernel instruction that enables the faulty operation so it becomes disabled, making sure the driver protects the physical device.
[Galaxy S II General] maortrol:
Thanks, but I think i'ts a space wasting to carry a full rom (more than 300 MB) on the internal memory only for flashing its modem...

So I'm looking for a simple .tar file with XXKG5 modem, but I'm unable to find it, and I don't know how to create a .tar file with the modem.bin extracted from the KG5 rom... :confused:
[Galaxy S II General] Phil3759:
Extract modem file from tar, mobile odin will flash it
[Galaxy S II General] Phil3759:
No

Cf root is an insecure kernel too

Quick Root uses an insecure kernel, but then you flash your stock kernel after root

No super brick risk on insecure kernel, it is only when you do a wipe with cwm

Also look in my signature for even more root ways ;)
[Galaxy S II General] maortrol:
I already tried that; I extracted the modem.bin from the .tar file of the rom, then I put it into the internal memory of the SGS2, but Mobile Odin didn't recognized that file as flashable... :confused: The reason was that I had renamed the file to "Modem KG5.bin" and due to that, Mobile Odin didn't recognized it!!! :laugh:

Now I've just copied the file modem.bin whitout any changes in its name, and Mobile Odin does recognize that file as flashable!!!

I didn't know that I couldn't rename the file, honestly... I learn something new every day... :o
[Galaxy S II General] AlkaDragos:
Hello, i have a question :) Can i flash a modem from 4.0.4 ROM to a 4.0.3 ROM? Thank you.
[Galaxy S II General] Tungstwenty:
I'm running modem XXLQ6 on stock XWLPG rom, so yes ;)
[Galaxy S II General] AlkaDragos:
Oh, thank you. I will try it...i have some weird problem since i flashed ICS, sometimes i loose signal (no network) for 2,3 seconds then it comes back...and my call gets disconnected or i can't hear nothing. So i thought it must be from modem, since it's the only "driver" related to network / data. Or it can be from ROM too? Maybe someone else had this problem too and can lend a hand? Thank you for your answer. :highfive:
[Galaxy S II General] kicksilver:
Damn, you guys are talking about rather expert stuff here.

I am running unbranded ICS stock rom 4.0.3. So all I gotta do is to wipe the phone by dialing *2767*3855# and then flash it through Odin?

I want all stock. Will this install the stock kernel too?
[Galaxy S II General] leolysenko:
any stock firmware includes everything you might need. LOL. Download it, flash it through ODIN and if you face any problem reset the phone with the code *2767...this will completely wipe out your data including progrmas, contacts etc.

A kernel is included, too.:D
[Galaxy S II General] kicksilver:
Hello.

I've been reading these threads about leaked 4.0.4 roms, and I'm seeing people talk about hardbrick with LQ5 modem, full wiping and etc.

I'd like to know if I'd have such problems flashing from completely stock ICS rom/kernel.

Of course I would and will full wipe before and after flashing it. (*2767*3855# rules!).

Just confirming my device won't explode or something....
[Galaxy S II General] gabriellazinho:
is there a way to brick the system if i flash a custom kernel ?
[Galaxy S II General] rizdroid:
XXLQ7, nothing new??? :(

#SGS2_Upd_Checker 01:33 GMT *NEW FW* Poland/Unbranded (I9100/LKAXEO) I9100XXLQ7/I9100OXALQ7/I9100XXLQ6/I9100XXLQ7

buld.prop

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D.XXLQ7
ro.build.version.incremental=XXLQ7
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Wed Jul 4 20:14:34 KST 2012
ro.build.date.utc=1341400474
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-107
ro.build.tags=release-keys
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=smdk4210
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 4.0.4 IMM76D XXLQ7 release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:4.0.4/IMM76D/XXLQ7:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=I9100XXLQ7
ro.build.hidden_ver=I9100XXLQ7
ro.build.changelist=753921
# end build properties
#
# system.prop for smdk4210
#

rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240

wifi.interface=wlan0
wifi.supplicant_scan_interval=15
#wlan.driver.apmode "unloaded"

net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-I9100.xml
net.streaming.rtsp.uaprof.bo=http://wap.samsungmobile.com/uaprof/GT-I9100BO.xml
net.streaming.rtsp.uaprof.hz=http://wap.samsungmobile.com/uaprof/GT-I9100HZ.xml

persist.sys.storage_preload=1

# Multimedia property for Smart View
media.enable-commonsource=true

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
ro.sf.lcd_density=240
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=128m
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
keyguard.no_require_sim=true
dev.sfbootcomplete=0
dev.powersave_fps=0
drm.service.enable=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-samsung
ro.error.receiver.default=com.samsung.receiver.error
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.kernel.qemu=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Galaxy S II General] kicksilver:
Just flashed it.

So far, so good.

ROM feels faster than 4.0.3, and they readded "Contacts" in the dialer tabs, not bad.

I will report about the battery usage tomorrow, everyone's saying its awesome.
[Galaxy S II General] jlevy73:
Doesn't look like it. Build date is July 6th compared to LPO which is July 18. Although the Polish builds always have run smoothly for me in the past.
[Galaxy S II General] khal_nayak:
so many ppl seem confused about the brick bug, let me make it clear what will brick ur phone

all 3 conditions need to be met

This bug requires three things for you to be in danger, and ALL of these conditions must be met for danger:

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

above info got from http://xdaforums.com/showpost.php?p=27074278&postcount=69
[Galaxy S II General] frz:
wildestpixel also has a few thoughts on the new ICS brikng our phones

Hes using a galaxy note, but....

http://wildestpixel.co.uk/index.php/7-news/25-bricking-your-gt-n7000
[Galaxy S II General] Brotuck:
Does XXLQ7 differ from XWLPO ?

Like in battery percentage on/off ?
[Galaxy S II General] maortrol:
Poland LQ7 is Android 4.0.3, not 4.0.4 (have just seen in SamMobile)...

EDIT: people in HTCMania.com has confirmed that is 4.0.4...

http://www.htcmania.com/showthread.php?t=423047
[Galaxy S II General] mcmanuf:
Can you tell me what the RIL version is? (can be checked with Getril on Market)

I have not been able to figure out which RIL matches the LQ6 baseband.
[Galaxy S II General] Tungstwenty:
Here's the output:

RIL: I9100XXLPX
md5sum: da204b...53dc7c
Baseband: I9100XXLQ6
Recommended: I9100XXLPX
RIL/baseband doesn't match

But from all I can tell, it seems to be working correctly - voice, sms, data...

Do you know what are the impacts of not having a match? Any particular symptom I can check for?
[Galaxy S II General] umberto1978:
The Radio Interface Layer is a part (the other is baseband) that dispatches commands to the hardware.

So i think: if you don't have any particular problems that's maybe related to a very similar content between LPX and LQ6 R.I.Ls

Maybe i am wrong...

This is what you can read at wikipedia
[Galaxy S II General] mcmanuf:
- Is this the stock XWLPO rom output? This means that samsung has not updated the RIL for some time, and that is must be compatible with the newest LQ6 baseband. Therefore Getril might be wring in its statement "RIL/baseband doesn't match".

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

- I don't know for a fact if there are any complications. I just know the default RIL and Baseband in Slim ICS 4.2 worked as s... in Denmark (3 Network). I kept loosing the GSM signal and kept roaming on other providers network. A very unpleasant experience.

I want to have as close a "stock" RADIO/GSM experience as possible due to the fact the the XWLPO is released in nordic countries (Denmark where i live included). I just don't want to go back to stock rom.

So I already have updated to I9100XXLPX RIL. Now I might update from XXLPX baseband to XXLP6 baseband so I am closer to the stock experience.
[Galaxy S II General] It_ler:
No, Tungstwenty has written: "I'm running modem XXLQ6 on stock XWLPG rom".

So it is the output of stock XWLPG ROM running with XXLQ6 modem.
[Galaxy S II General] Tungstwenty:
No, I'm still using XWLPG so it makes sense that the RIL doesn't match.
[Galaxy S II General] afiqsabri:
guys,

I just installed this 19100XWLPOm i found 2 problems with siyah kernel 3.4.1

1) still no live preview on the camera and playback video( already fixed with update *.zip file)

2) my computer can't detect my phone, no mtp tranfer

help me :laugh:
[Galaxy S II General] It_ler:
Flash a compatible kernel, such as stock or CF-Root v5.6 for XXLQ5.
[Galaxy S II General] afiqsabri:
mine is XXLQ6, i dnt think there's a cfroot for it
[Galaxy S II General] It_ler:
You said that you've just flashed XWLPO.

I am also on XWLPO ROM and flashed CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip for rooting.

Everything works fine.

Alternatively you can flash stock kernel of XWLPO to get rid of your issues.

Just a suggestion ... it's your choice.
[Galaxy S II General] crazy_4_and1:
It's a problem with ROMs which are from june and younger ... i had no problems with sock 4.0.3 pre-june builds . Did wipes from recovery and factory resets from phone menu .
[Galaxy S II General] afiqsabri:
Can xxlq5 cfroot fits with my xxlq6,as ur suggested? I've never dne it b4
[Galaxy S II General] pastnova:
I flashed siyah kernel than flashed stock kernel.My root is ok just cmw gone.Everything work fine.

Tapatalk 2 ile GT-I9100 cihazımdan gönderildi
[Galaxy S II General] It_ler:
XXLQ6 ... are you speaking about the baseband/modem/phone?!

It's not a ROM or kernel version AFAIK.

For choosing the correct CF-Root kernel, you should have a look at your Kernel/Build version number.

Or dial *#1234# into your phone and look at the PDA version.

If it's XXLQ5, XWLPM or XWLPO, then CF-Root kernel v5.6 for XXLQ5 will work fine, as I have tested it already.
[Galaxy S II General] afiqsabri:
My baseband would be xxlq6. My kernel nw changed to xxlq5,how is that possible, build xwlpo with xxlq5 kernel, btw,what is baseband?:D
[Galaxy S II General] It_ler:
Baseband = modem.

It is the part of the firmware which is responsible for the mobile communication (phone calls, sms, mms, mobile internet, etc.).
[Galaxy S II General] dragon135:
Anyone notice local search feature is removed in LPO?

I cannot search my installed apps using long press menu / google search.

Sent from my GT-I9100
[Galaxy S II General] It_ler:
I can see only Google search when long press menu button on my XWLPO.

In which ROM version was this feature for local (app) search?

Never saw/used it.
[Galaxy S II General] khantastic:
yes its gone, its gone in S3 latest update as well, reportedly due to some apple's patent issue

i hope sammy will work out some alternative real fast...
[Galaxy S II General] mozzer2k4:
http://www.androidpolice.com/2012/0...rnational-galaxy-s-iii-will-put-it-back-soon/