yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson XPERIA X10 Mini] 00DSoul00:
1.- Have not changed the IMEI

2.- Pay credits to unlock the bootloader online (there are many websites that provide this service)
[Sony Ericsson XPERIA X10 Mini] GURAYAGARRY:
Can u guve me the link or website or anybody who can unlock bootloader ..
[HTC Wildfire S] iximedaixi:
well about 3 weeks ago every thing was going very well i'm using CM7.1 ( stable ) with the latest kernel and updated lib files when suddenly i noticed that my volume and power buttons doesn't work from the first click some times i have to press like 6 of 7 times to get it to work and it's really frustrating i thought if i re flashed a new rom i'm thinking CM7 RC3 maybe will fix this issue but while i was in the recovery screen the volume buttons were also lagging so i think it's not a software related issue am i right ? !! or reflashing a new rom and kernel well fix the problem

oh and i still have 2 monthes remaining in my 1 year warranty so if i asked them to fix my phone ( if it's a hardware related issue ) will they tell me it's rooted it's out of warranty ? !!

thanks in advance
[HTC Wildfire S] ankitjoshi90:
same here....power and vol buttons have to be pushed multiple times to register click....in recovery too...i think its not a soft related problem....
[HTC Wildfire S] titochan:
Looks like ur volume and power buttons have been used extensively to boot into recovery and flashing roms & kernels !! NICE !!;):p

Rooting does not void you from certain hardware warranty and warranty on accessories(as i recall i read this somewhere while reading endlessly before rooting)..

This policy may vary from one country to another..but give it a shot..to be on the safer side unlock ur bootloader(though it will say relocked) and unroot ur phone before visiting the customer care..Best of Luck !!
[HTC Wildfire S] sukhjit321:
My buttons are fu***ed too. :X
[Samsung Galaxy Nexus] herzzreh:
How do I disable automatic login on GTalk? I noticed that it's one of the things that eats up battery. All other versions had the option and I can't find it here
[Samsung Galaxy Nexus] ÜBER™:
Don't think you can but usually only logs in upon boot up otherwise its logged out I thought.
[Samsung Galaxy Nexus] herzzreh:
Ugh... I guess I'll have to get used to this.
[Samsung Galaxy Nexus] jamerican413:
Don't know if you can disable auto login but you can sign out in GTalk's settings. (Top right menu within the program.. .)
[Samsung Galaxy Nexus] rickbosch:
Just log out. It won't log you back in until you tell it to.
[Samsung Galaxy Nexus] phositadc:
couldn't he just disable the app?

-Sent from my GSM Galaxy Nexus (RAScream+Trinity).-
[Samsung Galaxy Nexus] RogerPodacter:
If you log out then gtalk never logs back in even after reboot.
[HTC Sensation] lurch4653:
I'm a bit of a noob but have previously s-off and HTC dev unlock, & flashed numerouse roms. Today I flashed back to stock which still showed s-off and updated the to the new HTC sensation firmware 3.33 which is smoother. I have flashed CWMR but can't get super user to install without busybox which I have tried via app and zips. I am also now showing hb 1.29 I'm 3hrs in now and its doing my head in. Any ideas welcomed
[HTC Sensation] lurch4653:
Thanks all managed to sort it out by super wipe delete su, reinstal cwmrsu zip. And its works
[Galaxy S II General] DaReDeViL:
To all of i9100 users having flashed the latest 4.0.4 firmware (Official / Leaked) with

stock kernel

, PLEASE BE AWARE that

using cwm to erase

data/factory reset OR to restore a nandroid backup

MAY BRICK YOUR PHONE

!!!! Trust me, I just got mine bricked and by searching a litlle bit I discovered I'm not the only one -> see here and here ... and the number is growing ...

Actually confirmed firmwares having the emmc bug :

XXLQ5/6/7/B - ZCLPL - XWLPM/O/T/U - MUGLD3‎(?)

Here's how to BRICK your phone :

-Flash the 4.0.4 firmware with/without its pit file

-Use any 4.0.4 based kernel - stock or modified (ex cf-root)

-Go to cwm and do a wipe data & wipe cache and/or perform a nandroid restore of any previous firmware

=> The process begins normally but it may/will switch off at any time without waking up ever again !!!!!

Symptoms of 4.0.4 HARDBRICK :

-Phone dead

-No power up

-No boot

-No download mode (odin mode)

-No charging (usb/ac)

-Not detectable by pc / jtag

-Usb jig & jtag useless

-With battery(charged) inserted, phone(off) gets hot near the camera lens

-JUST A PIECE OF PLASTIC !!!!

-You feel really stupid about trying all this new stuff

And now here's how to avoid 4.0.4 hardbrick :

-DO NOT flash any stock 4.0.4 firmware ;)

-If on 4.0.4 stock firmware, keep away from stock kernel (ex: use siyah kernel or latest speedmod)

-Use "eMMC Brickbug Check" app to verify whether you have an insane ship or not

-Backup your apps (titanium backup) and backup all (cwm) and copy all data from internal sdcard

-DO NOT wipe any partition or data

-Flash any official 4.0.3 stock firmware in download mode via odin (do not use mobile odin)

-Do not get tempted again by any unsafe leaked or official firmware !!!

Downgrade from 4.0.4 :

-Reboot the phone in download mode (Home+Vol.Down+Power)

-Use Odin to flash a safe kernel (ex. siyah) then reboot to cwm (Home+Vol.Up+Power)

-Optionally do a nandroid backup then perform a data wipe/factory reset

-Use advanced menu in cwm to reboot in download mode to flash your preferred "safe" firmware

While waiting for someone to find a way to revive such bricked phones, I hope you guys take care of your precious S2, you only know its value when it's gone ;)
[Galaxy S II General] protomanez:
Thanks for the heads up mate!
[Galaxy S II General] drelite08:
I used nandroid to do a restore after messing with mods and it didn't brick.
[Galaxy S II General] donalgodon:
So, is there any safe way to get LQ5 downgraded to LPG?

I have been running LQ5, but this has me a little worried.

---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------

You were on LPQ and did a nandroid restore to LPG? (or what version was the restore?)
[Galaxy S II General] ballmead:
Flash it with Odin?
[Galaxy S II General] drelite08:
I'm on LQ5. It has both restored to LPS (new argo one) back up and a second back up I made before trying the mods. Both were fine. Using Phenom 5.5 medium.
[Galaxy S II General] donalgodon:
So, is it the manual formatting of the partitions or the nandroid restore that causes this?
[Galaxy S II General] bundi22:
i flashed LQ5 4.0.4 with odin, tried it out for 20 mins, then flashed latest fluxi through odin, then restored CM9 backup. all good for me
[Galaxy S II General] m.kochan10:
I've run LQ5, full wiped, restored nand backups several times today without any problems, but maybe I was just lucky. Anyway, time to run Odin, apologize LPG and wait for official. Don't wanna risk the brick.
[Galaxy S II General] The Undertakerr:
And here is nr3 who bricked his phone with 4.0.4LQ5 kernel.

It happens with both stock and CFkernel(=99%stock) LQ5...

http://xdaforums.com/showthread.php?p=28383119#post28383119

(Read post 5836 and futher)
[Galaxy S II General] graemeg:
this is good work, Well done author for speaking out, too many senior members flying round this forum banging on about how good a rom this is and that its legite, im sorry you bricked your phone, i hope you revive it.

I DIDNT flash this, because i saw the 8gb pit file and immediatley alarm bells rang out, that is not the stock samsung pit file, and i argued this with someone who insisted it was all legite, i know u dont need to use the pit file anyway, but the fact remained if the pit file was dodgy, the rest could have been, so i avoided it, and im glad i did.

This happened with a rom and kernel for ics on the galaxy note, UNFORTUNATLEY the phones were hard bricked when they did a cwm wipe and even a jtag service could not revive them.

FOR ANYONE whos flashed and done a nandroid, restore it, DO NOT DO A WIPE, and run ya restore and keep to oit for now, for anyone who didnt do a restore then im very sorry for yous, but i dont think there will be a fix, it usually requires a new mainboard, anyone who hasnt flashed this yet, ignore ALL OF THE other posts youve read about how good this rom is, DONT EVEN go there, avoid LQ5 if you can.

I really hope a fix can be found for you all.
[Galaxy S II General] donalgodon:
Sounds like the problem is the manual wipe via CWM recovery.
[Galaxy S II General] angelomaldito:
It WILL NOT brick your phone" it MAY brick your phone, i think that would be more precise, as I've restored LPG via CWM (after flashing CF-Root LPG on LQ5 firmware, as CF-Root LQ5 wasn't available yet). After CF-Root LQ5 was made available and I've learned that flashing LQ5 with Mobile Odin and unchecking "data" it wouldn't wipe my apps, then I've flashed LQ5 with the respective CF-Root and now I'm enjoying contact tabs on phone apk (as it was once upon a time on GB) and favourite contacts viewed as list instead of two column grid ;-) Ah, and no bugs so far!

Therefore, no problems here regarding LQ5 and restoring 4.03 with CWM.

PS.: I didn't used the included .PIT file. Did you?
[Galaxy S II General] donalgodon:
The thing I'm noticing here is that when people have manually formatted partitions via CWM or included the PIT file, they have experienced this bug.

My S2 has the bugged emmc chip, according to Chainfire's "got brick bug?" app, but mine flashed fine. I wonder if it was because I did not format partitions, nor did I use the pit file. I flashed via Mobile Odin.
[Galaxy S II General] DaReDeViL:
@ angelomaldito : You're right, the LQ5 will NOT AUTOMATICALLY brick your phone but it may EVENTUALLY happen !!!! At least in my case, I first flashed the LQ5 rom then flashed the latest and correct CF-root and then went back to cwm and wiped data/factory reset and wiped cache and launched a nandroid restore, which stopped in the middle of the process leaving me with a S2 unresponsive and maybe hard bricked for good !!!

This said, the exact scenario happend to a lot of people, i'm not the only one. LOGICALLY, if it's reproductible then it's not a bad manipulation but a SERIOUS PROBLEM that must be dealt with !!!!!!!

Edit : First post made clearer (Will => May) ;)
[Galaxy S II General] donalgodon:
So, probably, the best option would be to Odin back to 4.0.3 and then restore nandroid backup from there?
[Galaxy S II General] tariq2kn:
I have flashed lq5 through odin without repartitioning/.pit.

I haven't flashed cwm & am using the stock kernel.

It's working smooth since I flashed, no issues.

It seems to me that the wipe from cwm seems to be bricking the phone.
[Galaxy S II General] buxz777:
same thing happend a while back with a siyah kernel based on a samsung source that could brick your phones if you wiped or factory reset in cwm

i think the advice then was to go to a cm9 firmware with cm9 kernel as its safe without wiping , then flash through odin a safe stock firmware like lpg for example

apparently this doesnt effect cm9 kernels so anyone scared of bricking should maybeflash that then work from there to avoid bricking

there is more here https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB
[Galaxy S II General] marcellocord:
You guys are totally late... Want some kickass 4.0.4 that will never brick your phone? Yeah, you know what I mean :P

But seriously. That's the problem with leaked ROMs, in G Note was the same thing. I made a bad call flashing it to test, didn't like it, bad performance, and then, restored nandroid. PS: didn't brick. But was wasted time and was dangerous
[Galaxy S II General] goolby:
I always flash to SpeedMod K2-21 kernel and restart recovery before i wipe/flash my phone whit new rom, so no risck here because i know that SpeedMod is safe !
[Galaxy S II General] atifsh:
Yes, you can do data cache wipe if you are on stock recovery.
[Galaxy S II General] Brotuck:
Another question on the eMMC Brickbug Check app posted on the first page.

I installed this and ran the test, it passed. So now my eMMc is safe ?

Hot to interpret this app ? Because it also is telling me that i have the Insane chip.
[Galaxy S II General] atifsh:
you are partially correct, its not Sammy roms its the kernel, remember what happen with siyah kernel? How many were on stock roms when they got bricks? in case you don't know most were using aosp roms.
[Galaxy S II General] atifsh:
I yet to see a chip that's safe in s2 :D

Do not remember exact wording, but app said I have the chip that had issue with emmc.
[Galaxy S II General] GFXi0N:
CM9 + siyah is not cm9 anymore. Stay on cm9 stock, no kernel changed.

For saying more: mention a different kernel on cm9 nightly thread and see how much they like them. :-)
[Galaxy S II General] :
I understand what you are trying to say, it's correct but you completely misunderstood what I was trying to say and it's not what I meant ;) . The guy was asking about the procedure how to get rid of LQ5 in the safest possible way. And not about what ROM is the most stable or about user's experiences. I'm a huge fan of CM myself (I update it almost every day).

I understand risks with leaks, but I am not suggesting anybody to flash the leak :) and for example XWLPG (and I guess the majority of S2's fw) I can bet is definitely more stable and safer than every nightly build.

About using Odin...yeah it can be dangerous sometimes due to the heavy stuff that can be transferred and possible connection errors. Unfortunately it's the only tool that allows us to install: bootloaders, .pit etc and it's the Odin that can revive soft-bricked devices. Thus it cannot be replaced by CWM. I personally don't find using Odin more risky than flashing anything via recovery, and especially not flashing a stable firmware. In our particular problem with LQ5 I feel much more secure using Odin than performing any sort of operation in CWM. (But since you can flash cm9 via odin as well, it's maybe not that bad idea to try with that instead.)

Anyway I've flashed many roms and I still find the official stock ones the most stable and safe in general. Which doesn't mean they are my favorite ones of course ;) Ok EOT here ;)
[Galaxy S II General] atifsh:
:cool:

Never mind!
[Galaxy S II General] rumsam:
Bricked my S2

I flased LQ5 and tried formating data using CWM and my phone freeze immediately.

Now phone not switching on ,tried charging (phone heating up not charging) tired all sorts of hard reset soft reset. any solution?
[Galaxy S II General] atifsh:
Buy new phone, or if under warranty try it.
[Galaxy S II General] rumsam:
but the problem is that i flashed temporary CWM (touch) and tried formatting data..anyway Phone still under warranty...will try my luck with sammy!
[Galaxy S II General] atifsh:
yes lq5 kernel + any kind of cwm + wipe = hard brick
[Galaxy S II General] shoman94:
Jesus, people just don't get it.
[Galaxy S II General] rumsam:
Hope samsung wont check my root and custom firmware counters.. :(
[Galaxy S II General] turborider:
im so happy that my phone is not bricked after installing this firmware and everything was ok appart of the lost on 75% my 16gb sd card photos and videos of my kids :silly: ,never ever again going to install anything like that in the future well not next 3 months when my contract finish and get 'Samsung Galaxy Note 2' in September :D
[Galaxy S II General] Brotuck:
So basically the topic is wrong.

Because the rom and kernel itself will not brick the phone.

Its only us that want to add stuff like cwm to change the stock experience that is risky.

Verstuurd van mijn GT-I9100 met Tapatalk
[Galaxy S II General] bbk:
Hi,

I've got a LQ5 (with root with a temporary CWM.zip)

Can i install Siyah v3.3.3b with my temporary CWM ? Or must i try with ODIN (but i'ven't any computer near me)
[Galaxy S II General] atifsh:
ask in that thread. if you read few posts.... this kernel is not for 4.04 and got lot of bugs plus the development of siyah has halted if im not wrong, so you better change the rom
[Galaxy S II General] bombaybadboy:
The panic i am reading on some these threads seems unreal. People seem to be treating lq5 like a timebomb on there phones and panicing and making the mistake everyone is warning against. Its not hard instructions just stay away from cwm and stick to odin and keep a level head
[Galaxy S II General] veyka:
It was previously reported that wiping from stock recovery, or doing a factory reset can cause this bug.

There was at least one person in the note section who bricked their phone using the stock recovery, and the sgs2 has the same emmc chip, and the same bug.

I get that flashing anything is a risk, but running known dangerous firmware just seems silly, if you want 4.0.4 go CM9, otherwise stick to 4.0.3 until there is a safe leak. :rolleyes:
[Galaxy S II General] atifsh:
Stop misleading, stock recovery is safe, this is not galaxy note,
[Galaxy S II General] Brotuck:
Please stop comparing note roms to i9100 roms.

They are not the same.

Until someone points me to a post that confirmes that stock recovery bricks the phone, i will keep telling that the problem is not LQ5 but it is CWM developed by non samsung employees.
[Galaxy S II General] veyka:
Of cause its not a galaxy note, but its the same bug, with the same chip, cause by the same root issue which is a bug in the eMMC firmware being brought to life when MMC_CAP_ERASE is enabled.

This is what happened on the note, this is what is happening here.

Go read this post on the portal about it.

Issue seems to present most often on anything that wipes a partition.

EDIT: oh and as you wanted a post where someone has had their phone bricked by stock recovery, see here.
[Galaxy S II General] atifsh:
And you will not find anyone :D
[Galaxy S II General] hawkn:
Ok, so I was a morron like several others flashing the leaked LQ5 rom from sammobile.

It worked great, I installed Siyah 3.3.2 and it still worked great.

The problem came when I flashed with LPG rom, it failed with a big red sign in odin.

Tried reflashing LPG and this time it flashed ok, but no boot, just hangs on the first logo when powering on the phone, after a while it reboots itself and this goes on until I pull the battery or it runs out of juice.

Tried flashing the LQ5 rom again, this time it hangs for ever when writing data.img file, even tried last night and this morning it was still on the data.img and no progress.

Tried flashing superold 2.3.3 from sammobile, this actually kind of worked.

After this I got the little box showing up like the first time I powered on the phone.

It complained about /efs /cache and something like /last-log -recovery or someting.

It took forever to get into recovery mode, but I got there.

I flashed CF-root and could still get into recovery with all the errors appearing.

Now I tried flashing LPG and when rebooting after flash this failed to boot.

I've tried several times now and it is still the same, but I think it might be something here for people who are able to get into download mode.

Seems to be an opening for recovering the phone in some way or another.

Lucky for me this is my work phone as I have 2 weeks left of my vacation, my private number has moved in to a shiny blue I9300 :D:D:D

---------- Post added at 12:07 PM ---------- Previous post was at 12:05 PM ----------

I will say the problem is with the rom !

Had a similar issue on a HTC phone and had to resurrect it with my riffbox.

Sadly I don't have a soldering iron or adapter to fix my i9100 the same way :crying:
[Galaxy S II General] GFXi0N:
My question still is: Could we upgrade by software our Emmc chip to version 0x25,which has this bug covered?

Chainfire? Any expert on the matter?

That would be the ultimate solution because it looks like a pure firmware issue, not a hardware limitation with those chips...
[Galaxy S II General] Subtract:
Try to flash a 3-part firmware with odin. Use the PID-File too and use Re-Partition. Helped me after searching 5 hours x.x
[Galaxy S II General] veyka:
Not at the moment, hopefully samsung will put out a real fix for this nonsense with time, until then just avoid anything with MMC_CAP_ERASE enabled in the kernel.

If you read the portal post i linked a few posts up there is more info on it, and they mention something about why upgrading the firmware isn't as easy as it sounds if i remember correctly.
[Galaxy S II General] Gammelgustav:
Another tip - disable MMC_CAP_ERASE in Kernel if you're experienced enough ;)

Sent from my GoaTrip Galaxy S2
[Galaxy S II General] atifsh:
be happy in your bubble, im not going to go read the user who might bricked by his own fault and drop on LQ5. iv done it many are done it, and we still are on LQ5 happily.

go look for the youtube video one user post where he showed wiping, you still want to trust what you read than what you see?

heck i can make a video to show you if you want.
[Galaxy S II General] Fox05:
But is it still safe to wipe data from phone or CWM in XXLPW? :)

Thanks.
[Galaxy S II General] hawkn:
I've been searching since last night and all I can find is 1-part files :crying:

I'm about to trow the phone into the ocean and tear my hair of my head, I've started getting gray hair over this now.
[Galaxy S II General] android_isda_shit:
Y u no send phone to service center
[Galaxy S II General] Subtract:
Here is a LPJ one, but it doesn't have a pit file in.

https://hotfile.com/dl/149957290/da7e0f0/I9100XXLPJ_I9100XXLPJ.zip.html
[Galaxy S II General] hawkn:
Now where do I get a pit file then....

I downloaded this: --> http://xdaforums.com/attachment.php?attachmentid=1185385&d=1341775209

But it seems it doesn't work, when trying to flash LPJ it hangs on "DATAFS", when trying to write data.img file to phone.
[Galaxy S II General] svceon:
http://xdaforums.com/showthread.php?t=1544689/

This one has. I guess this is what you are looking for. Worked for me, but i guess i didn't had the Hardbrick
[Galaxy S II General] superleeds27:
I9100XWLPM

Official 4.0.4
[Galaxy S II General] veyka:
I have no idea what planet you are on, I am not "living in a bubble", have you checked what eMMC firmware version you are on? You may be running on the sane version, others may not.

And yes, I will trust what Entropy512 and many other devs have stated over some random youtube video.

I would just think that its a bit unwise to band around that the firmware is perfectly safe without CWM, when it had been stated that the stock recovery or wipe may also trigger the bug.

And yes, disabling MMC_CAP_ERASE should negate any issues, which is what I believe chainfire will have done in the new CFroot release.
[Galaxy S II General] manoloto:
If the rom has made Samsung, the extent to which Samsung is responsible for damage sustained in the terminals ?
[Galaxy S II General] hawkn:
I guess the only thing I can say is, THANK YOU SAMSUNG !!! for killing my device!

I trusted the firmware upgrade, and thought like a morron that it was safe since it came from sammobile.

The only thing I can do is getting download mode Odin with vol - + home + pwr and factory mode with my little jig, flashing LPG or LPJ roms with 3-parts fails when trying to write data.img, it stays forever without any progress.

The only thing I can flash with success is GB roms, but they are worth nothing since I cannot get into Recovery mode nomatter what I do, it does not boot, and it gets stuck either at the little android dude in front of the box I saw the first time I powered on the phone (stays like that forever) or it just shows me the fancy s2 logo.

Here is a picture of where it hangs when trying to flash ANY ICS rom https://dl.dropbox.com/u/10646701/SGS2/20120709_153851-1.jpg