yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] Rawi666:
On the other hand siyah kernel 3.1rc6 is a good way to "refresh" your SGS2.

Imagine a situation where your warranty is about to end and you want "fresh new" SGS2 :)

Just flash siyah, wipe and enjoy a new SGS2 that service center will give you :D

I'm curious if they will extend warranty period for the new unit or not...
[Galaxy S II General] hIdd3N-:
yeah... and an attorney would call that fraud. :mad:

i'm keeping a racist comment for myself now.
[Galaxy S II General] crachel:
Great idea! You could get a new phone AND be a liar and a thief! Seems like a great trade off.
[Galaxy S II General] Stitch!:
Same experience here btw, hardbricked my phone. I dont consider myself to be a noob, and I tried basically everything that is possible. adb recovery, my jtag, eventually ended up replacing the motherboard. Now my phone is working great again. The main problem was. Samsung warrenty center i send it to initially told me it was not working due to water damage. After getting a second opinion from a friend I knew they where lying about this. No waterdamage whatsoever, just a non responsive motherboard.

Replacing the motherboard is not very hard, but you need a steady hand and some tools. If you are not sure you can do it i would recommend just paying a service center to do it. the 50 euros i saved by doing it myself may not be worth losing your warranty for most people.
[Galaxy S II General] kachrukamble:
In the end, do you got motherboard under warranty or you paid price for the same?
[Galaxy S II General] sinancetinkaya:
here is a good explanation about emmc http://www.quantumservice.biz/artik...r-mbr-based-emmc-flash-images-processing.html

I'm not an expert but I don't think the brick is caused by emmc chip's hardware issue. May be some partitions like MBR were removed during the wipe which shouldn't be?

Damn I thought bricking SGS2 was not so easy. Now I see even a command like dd if=/dev/random of=/dev/block/mmcblk0p1 bs=4096 on a rooted SGS2 can brick it completely ?
[Galaxy S II General] Crescendo Xenomorph:
And flashing any latest kernel can't fix it?

My 2cents: mount it in linux PC and run fsck... Last time it helped me to recover my internal SD...

---Sent from my Samsung Galaxy S2 via [ALTIMIT] Network
[Galaxy S II General] itchetrigr:
Has anyone who is still able to adb, try deleting the partitions and repartitioning ?
[Galaxy S II General] kachrukamble:
Today my bricked motherboard disported to Samsung India headquarter. They will examine the board.

If they found anything custom on the board (chances are very less as eMMC chip is also corrupted.) I will have to pay for motherboard price. Which is $150+taxes.

If they didn't found any illegal flashing history, I am good to go.

So people send your devices to service center.

This is the hope for survival.
[Galaxy S II General] jashy67:
Good luck bro, I'm crossing my fingers and my toes! Hope all this **** will have a happy ending. ;)
[Galaxy S II General] luizlee86:
Omg.. I feel bad reading this thread.. i stopped using Siyah on rc4.. so I could be with a bricked phone..

Hope there is a solution (even seeing that the only one is sending to repair center).

BUT, if jtag can be a solution in some cases, for those who live in Brazil, there is a repair center with jtag at mercadolivre.
[Galaxy S II General] Breaksomeoff:
Sounds like a terrible brick, you have my sympathy.

Sadly, this is the time we live in. Due to the complexity of our devices, more and more things are getting bricked via unofficial flashing of software. I myself had a £200 device turn into a paperweight about 7 years ago, it's a horrible feeling.

If you update immediately on anything unofficial then you are taking risk, no matter who has done the update. I stayed on 3.1rc5 as I always look at changelog and give it a day. I noticed blnww was removed and didn't want to lose it, but this could of easily happened to anyone and I hope you get a resolution soon.
[Galaxy S II General] jchusted:
That's Nice.

Was to phone totally dead ?

They where not able to see that the phone was rooted ?
[Galaxy S II General] sauron96t6:
Fast assistance... sounds good!

I'm happy for you!!! :)
[Galaxy S II General] qqqqqq0:
be careful
[Galaxy S II General] Entropy512:
Rogue recovery - I'm guessing you're on an Epic 4G Touch?

That's interesting - it looks like your partition table is hosed up, it thinks that many of those partitions are 0 length. Cache is good, the rest are screwy. I'll come up with some additional commands to try tonight.

Originally gokhan and I were leaning towards voltage regulator stuff, but I think it's something else.

Samsung set MMC_CAP_ERASE in the MMC driver of the kernel for some devices - confirmed for Korean M250* devices. It may be that some eMMC chips don't like this feature and get fried.

In fact it is happening with many other kernels:

Any ICS leak for Epic 4G Touch (Sprint GSII)

Any ICS leak for Galaxy Note

The UCLD3 ICS leak for AT&T Galaxy S II

Apparently Korean M250* kernels (due to language barrier, we often don't hear about these until there's a reason to do serious digging) - These are the only ones where there is source to analyze.

I9100 users need to realize how lucky they are that this is the ONLY device with Exynos that didn't receive dangerous ICS kernels, even in the leak phase.

I think Samsung is aware of the issue and trying to solve it - see: https://github.com/Entropy512/kernel_galaxys2_ics/commit/d069cc5cb9f0fd9409ea10d4037e4c0e68701b8e - they disabled TRIM which is a relative of ERASE. Unfortunately they left ERASE in - I think this is the cause of the issue.

Those who are softbricked:

cat /sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/name

in a shell

Gokhan has VYL00M, as do I in my Note (haven't checked my 777 yet) - he's actually done multiple wipes with the "bad" kernel without issues.

Also, to those talking about repartitioning - you would need to do it using a PIT file in Odin. However I think more data needs to be collected first - I'll have some more commands to run tonight.
[Galaxy S II General] Stitch!:
I replaced it myself, got it for 90 euros through someone in wholesales, since I didn't leave any marks and kept the seal intact, I can still apply for the normal warranty in case my screen breaks or something.
[Galaxy S II General] sauron96t6:
Disassembling S2 - How to

Excellent video step by step to replace the motherboard by yourself!

http://www.youtube.com/watch?v=65pvAINg2ME&feature=related
[Galaxy S II General] mckeowngoo:
Is this the JTAG required?

http://www.amazon.co.uk/gp/aw/d/B005ARV26O/ref=redir_mdp_mobile

Doesn't seem that expensive if it is.
[Galaxy S II General] Bor_NL:
That's a jig to reset your flashcounter
[Galaxy S II General] kamesam:
Help with Galaxy S2 i9100 "softbricked"!!

Hi,

I got the "softbrick" I guess. I can flash kernels, bootloaders and firmwares without /data, with .PIT or without it. But when I try to wipe data or flash a firmware that goes through data, then I got stuck (GB or ICS - doesn't matter). Either with Odin or CWM. All buttons still operational so I can still get to download mode or recovery.

Can you please provide more details on

cat /sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/name

What exactly it will do?

Do we need to run it through ADB (In this case, can you point me to some references in the forum on how to use it for this purpose)? Do we need to be root?

Thanks in advance,
[Galaxy S II General] mckeowngoo:
Don't I feel like the f**king idiot!

So how much does one of these things cost and has anyone got a link please?
[Galaxy S II General] Entropy512:
In an ADB shell - and doing that command pulls the identification of your flash chip - I'm wondering of those who softbricked have a different chip than gokhan does.
[Galaxy S II General] sauron96t6:
Riff-Jtag-Box

RIFF-JTAG-BOX

http://www.riffbox.org/downloads/GettingStarted.pdf

http://forum.gsmhosting.com/vbb/f634/riff-jtag-box-important-manuals-1051474/
[Galaxy S II General] kachrukamble:
I am wondering of those soft brick devices had single boot or dualboot.
[Galaxy S II General] igottu:
Did you know Siyah actually means Black? So your phones are! :rolleyes:
[Galaxy S II General] KennyLegend:
And????

It was only 1 version of Siyah had issues and not everybody using it got bricked.
[Galaxy S II General] kamesam:
I tried to ADB to the S2 but it's not recognizing the device. It says 'error: device not found'. I am able to ADB to another Samsung device (i5500) though, but not to my S2. I don't know much of ADB. What am I doing wrong here?
[Galaxy S II General] Crescendo Xenomorph:
I got something on the net, are they the same explanation for those TRIM/ERASE commands that mentioned in your github (https://github.com/Entropy512/kernel_galaxys2_ics/commit/d069cc5cb9f0fd9409ea10d4037e4c0e68701b8e)?

What's the difference between TRIM and ERASE command?

I'm really curious, how come an erase/trim command can fries the chip...

Thanks..

Cheers,

Crescendo

SDHCI host controller has TRIM/ERASE capability, enable these caps for erasing
purpose.

ERASE command needs R1B response. So for such command with busy signal, before
sending command, SDHCI host driver will simply set a maximum value for timeout
control register which is safe to use.

Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>

drivers/mmc/host/sdhci.c | 16 +++++++++++--
1 files changed, 11 insertions(+), 5 deletions(-)

diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index 655617c..fe7cbd0 100644
a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
@@ -41,7 +41,6 @@

static unsigned int debug_quirks = 0;

-static void sdhci_prepare_data(struct sdhci_host *, struct mmc_data *);
static void sdhci_finish_data(struct sdhci_host *);

static void sdhci_send_command(struct sdhci_host *, struct mmc_command *);
@@ -652,16 +651,23 @@ static void sdhci_set_transfer_irqs(struct sdhci_host *host)
sdhci_clear_set_irqs(host, dma_irqs, pio_irqs);
}

-static void sdhci_prepare_data(struct sdhci_host *host, struct mmc_data *data)
+static void sdhci_prepare_data(struct sdhci_host *host, struct mmc_command *cmd)
{
u8 count;
u8 ctrl;
+	struct mmc_data *data = cmd->data;
int ret;

WARN_ON(host->data);

-	if (data == NULL)
+	if (data == NULL) {
+	/*
+	* set timeout to be maximum value for command with busy signal.
+	*/
+	if (cmd->flags & MMC_RSP_BUSY)
+	sdhci_writeb(host, 0xE, SDHCI_TIMEOUT_CONTROL);
return;
+	}

/* Sanity checks */
BUG_ON(data->blksz * data->blocks > 524288);
@@ -921,7 +927,7 @@ static void sdhci_send_command(struct sdhci_host *host, struct mmc_command *cmd)

host->cmd = cmd;

-	sdhci_prepare_data(host, cmd->data);
+	sdhci_prepare_data(host, cmd);

sdhci_writel(host, cmd->arg, SDHCI_ARGUMENT);

@@ -1939,7 +1945,7 @@ int sdhci_add_host(struct sdhci_host *host)
mmc->f_min = host->max_clk / SDHCI_MAX_DIV_SPEC_200;

mmc->f_max = host->max_clk;
-	mmc->caps |= MMC_CAP_SDIO_IRQ;
+	mmc->caps |= MMC_CAP_SDIO_IRQ | MMC_CAP_ERASE;

/*
* A controller may support 8-bit width, but the board itself
1.6.6.1
[Galaxy S II General] drakester09:
Just FYI, I have VYL00M on my i777

Luckily I did not flash the ATT leak nor we had a rc6 for I777.
[Galaxy S II General] pejmany:
No, the Bell Galaxy S II (i9100m), white, if it helps.

It seems like the i777 and i9100m may be different, still don't know though.

I tried out the cat command, got

N:\android-sdk\platform-tools>adb shell
~ # cat /sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/name
cat /sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/name
cat: can't open '/sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001/name': No
such file or directory
~ #

Then again, I may have just done it wrong :/ Open to retries :P

And yeah, in my thread I figured it was partition table, I asked if there's a way to rewrite mbr if I can get the partition data from another gsii

If that ^ makes no sense, I hope you got the idea of what I was going for, cause I'm not too bright definition wise xD

EDIT: should i try reflashing ki3 again before doing the cat?
[Galaxy S II General] sinancetinkaya:
Yes siyah means black in Turkish, so ?

Bad things happen everytime during development progress, Gokhan cannot test all the code line by line in every aspect. A code worked well on his device might not work on your device.

The thing shocked me more than the bug is that how easy brickable our SGS2s are!

If you don't want get your SGS2 bricked, don't even root it. Even a bad written root required program can brick your device, it doesn't have to be a kernel.

I hate Samsung at software side (I agree Samsung makes awesome hardwares).

There have to be a fail safe option, at least the bootloader must not be accessible by OS but something like ODIN (Just like HTC's S-OFF)
[Galaxy S II General] sauron96t6:
Sound good! Would take a security option (eg. boot from the S2 external Sd). IMHO this section shall not be accessible bootloader .... cannot risk the brick, if happens we must put hands in our pocket and pull out some money!! :eek:
[Galaxy S II General] Tiyaj:
RR

That's bad.. I have tried most of the Siyah kernels on Resurrection Remix ROMs.. No issues so far.. I am now using CM 9 kernel comes with Resurrection Remix 1.7. Try it. One of the Best.. :)
[Galaxy S II General] pika456:
if you semi fix the boot (boot loop)

have you tried to full restore from cwm backup? or flash different kernel?

usually it fixes my boot loops, from other causes however
[Galaxy S II General] Roger00:
For anyone interested there's a sgsII with a broken screen for sale on ebay, they will ship to Europe: http://www.ebay.ie/itm/200750570855?ru=http%3A%2F%2Fwww.ebay.ie%3A80%2Fsch%2Fi.html%3F_from%3DR40%26_trksid%3Dm570%26_nkw%3D200750570855%26_fvi%3D1&_rdc=1
[Galaxy S II General] gokhanmoral:
I want to make something clear again: it was not siyahkernel's bug, but it was samsung update5 source's bug. since I rebased my sources on update5 sources with v3.1rc6 some people had this problem.

that bug was in siyahkernel's v3.1rc6 and that kernel is already removed and I have uploaded another rc6 which is based on update4 sources.

I feel bad and I am sorry. However, I am not sorry because of a bug that I made but I am sorry because phones are bricked because of that problem. I am almost 100% sure that the problem which bricked phones is caused by Samsung's mistake or otherwise I would completely stop releasing new kernels.

you may choose not to use siyahkernel again and choose one of the available several high-school kiddie's work which are usually just a blind mix of other kernels but that will not make your device any safer because most kernels have very similar patches/code.

there was only one way that I could avoid that problem in rc6 and that would be to say in several threads that "wow, update5 base rocks, but I have no time to rebase my sources on it" and wait for somebody else do it before me.. then I would wait and see if there were any problems.... if I did that the result would be different but there would again be some bricks.. it wouldn't be you or siyahkernel users but it would be some other kernel's users...

If you blame me more than Samsung in this matter I won't (and can't) stop you but I don't think it is fair.
[Galaxy S II General] ephraim:
Well said GM.
[Galaxy S II General] g00ndu:
GM, i don't think we are blaming you at all for the bricks, or at least the majority of the users here. Caveat emptor applies when anyone decides to flash other than stock roms. FYI, i don't even use your kernel, has always been on speedmod. it is only recently i started using dorimanx kernel. i know the risks, and i know what's the worst scenario would be, and if it happens, i will not blame anyone but myself.
[Galaxy S II General] sinancetinkaya:
Are you talking to me ?

If yes, what the hell are you talking about?

Which part of my message is blaming you?

FYI, I'm on your side!
[Galaxy S II General] gokhanmoral:
no, I was talking to everyone. and "you" words in my post refer to those who had their devices bricked.

I just wanted to clarify something in your post but the rest of the post has nothing related with you or your post.

although there are no sides here I know that you don't blame me.
[Galaxy S II General] Crescendo Xenomorph:
Don't let any people that say bad things about you and your kernel make you down. You got too many followers to stop making GREAT kernel like this.

Let's concentrate and innovate once more, never ending innovation. As we are expecting GREAT KERNEL from you...
[Galaxy S II General] igottu:
Umm.. what? I'm not trying to be rude but this smugness won't get you anywhere.
[Galaxy S II General] gokhanmoral:
neither I am trying to be rude but that part is a fact.

I am not saying that siyahkernel is the best. there are already alternatives which people can find more comfortable.

that part may not seem too much related with what I was trying to say and may seem smugness but it is not. It was an answer to those who had no idea about what was going on and thinking that choosing just another kernel would make them safer.

anyway.. "siyahkernel is not the best" would be enough as an answer to you.
[Galaxy S II General] spike86:
can technics in sc know that i tried to connect jtag?
[Galaxy S II General] kachrukamble:
I geuss no. See jtag is a service to recover bootloaders. Sc only intrested whether you rooted or not
[Galaxy S II General] m.ecore:
samsung shape up ????????

Still putting down other dev's work .the fact that your arrogance remains so strong points to dodgy judgement .Samsungs fault !!!!!!!!ONLY SIYAH KERNELS DESTROYED THE PHONES .from now on its only highschool kids who make my kernels speedmod/neak etc.
[Galaxy S II General] mahtew:
Two weeks ago probably You would say how gokhan is great etc. etc./

YOU DECIDED TO USE HIS KERNEL. IT WAS YOUR DECISSION. FLASHING NON STOCK SOFT CAN DESTROY YOUR PHONE! DIDN'T YOU KNOW THAT?? IF YOU KNOW THAT THEN YOU SHOULDN'T BLAME ANY ONE. IT'S YOUR OWN F... FAULT

Have YOU read the disclaimer on the first page of the thread??

IT WAS SAID MANY MANY TIMES.

My phone is also bricked. I don't know if it can be repaired.. And so what? I decided to chose this kernel. SO IT WAS MY FAULT. Probably, If I would visit more frequently last pages of SIYAH KERNEL THREAD then my phone wouldn't be bricked.

This thread should give us an answer how to repair our phones. NOT HOW TO FLAME!
[Galaxy S II General] BrandoHD:
What arrogance, you guys are unbelievable.

He has clearly stated his case and in case you were not reading the thread, the issue is not with the kernel but with the source code he based the kernel upon, many other devices have been bricked by many other kernels/kernel devs due to this and those kernels only had one thing in common, SOURCES Samsung does need to shape up, they released official sources and some unofficial that does not work with the hardware even for the device they released it for (Galaxy Note, I777 and Korean GS2) and that is close to unacceptable.

But yet you feel you had to create an account on 24th April 2012 to make one post about a topic that you are clearly ignorant about should be enough to show everyone else to regard your "opinion" as vacuous...

This thread are for those that unfortunately bricked their devices, it is not a thread to blame GK especially when blame is, in his words "unfair"

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

It seems that the only option is motherboard replacement, embedded flash memory chip is dead, you may not have to worry about Samsung service center seeing your flashing history
[Galaxy S II General] gokhanmoral:
I was not thinking about answering your previous post but this one deserves an answer.

idiot? considering your attitude and narrow-minded approach, it seems that your mind is bricked way before than your device. and I am sorry for you that it is not possible to replace your brain. I advise you to find someone to plug you a jtag, in whatever way you like, maybe it will help you relax...
[Galaxy S II General] karendar:
Not really being smug from my point of view, depends on how you wanna take it I guess. Choice of words could have been better, but the message gets across. Copying someone's repo and taking bits and pieces left and right is a "Beginner's attempt" at kernel coding. Which alot of kernels are initially. It's a learning method. Gokhanmoral's product is more mature than some people who begin modding kernels and his point was to say you could have taken any kernel on the thread from a total noob beginner and scrap your phone.

Modded kernels are a risk. This is a simple lesson in humility for everyone who's got a bricked phone, reminding them that it CAN happen and you can only blame yourself for flashing knowing the risks. And it's a lesson in humility for the kernel coders to not always throw everything brand spanking new into the wild without testing things first.
[Galaxy S II General] sahibunlimited:
^LOL

10 chars
[Galaxy S II General] Fustigador:
i just wanna say that guys like gokhanmoral work for all of us for free, and if u guys want optimized roms or kernels u all know your risks, it can brick your phone, and if there is solution like jtag, please take it!

ty gokhanmoral for ur amazing work and all other devs from XDA
[Galaxy S II General] Cristiano Matos:
Couldn't be better!

:D
[Galaxy S II General] czesiu:
Just to clarify:

Do I understand correctly that there are (probably) thousands of samsung devices bricked with official updates with this code?
[Galaxy S II General] Cristiano Matos:
Maybe not thousands but a bunch for sure.
[Galaxy S II General] czesiu:
only hundreds with

official

updates?
[Galaxy S II General] KennyLegend:
Yes. Any Samsung phone that was flashed with a kernel using the update 5 sources could have been bricked.
[Galaxy S II General] Curron:
gokhanmoral just don`t listen to ****talk like this one, as a member of this forum he aught to know that he uses what he downloads from here on his own risk !! :confused:

---------- Post added at 12:28 AM ---------- Previous post was at 12:18 AM ----------

There is about one way to be shore not to bric a smartphone - don`t get one !! :eek
[Galaxy S II General] sauron96t6:
I'm waiting to get my S2 back... now is still under repair. Definitely want again to have a new kernel Siyah

gokhanmoral number one! :)
[Galaxy S II General] Entropy512:
Probably. Admittedly for many devices, the kernels responsible are leaks (I777, Note, Epic 4G Touch), but the Korean official sources are problematic too. Unfortunately due to the language barrier it's hard to know what's going on exactly with those device, but there have been some people indicating indirectly that there are grumblings in Korean dev communities about this problem.
[Galaxy S II General] chukkie:
So many fools talking out of their anuses. Many phones were bricked using rc6, nd even via official samsung updates heck even several galaxy notes were bricked! All the haters of gokhanmoral can GTFO for all I care. Everyone of us on these forums have ALWAYS acknowledged there is always a risk with unofficial software! Stupid idiots. Keep criticising him and he can just get fed up which such abuse.
[Galaxy S II General] prosumerhacks:
dude! have some respect with your words... :mad:
[Galaxy S II General] KennyLegend:
Yes mate. Gokhan and Entropy have already clarified this in the last few days.
[Galaxy S II General] bala_gamer:
Loads of pages full of flaming from siyah haters or trollers !! :eek: Isnt this thread meant to discuss "how to service GS2 and get it back successfully"?

The nature of the problem is described clearly from some elite developers and still!!!

Oh never mind, some people will never understand something. Good luck to all bricked gs2 users, get your devices soon guys.