Siyah kernel 3.1RC6 and BRICKED GALAXY S2

Search This thread

FeuchtVonLipwig

Senior Member
Apr 7, 2012
197
65
Berlin
wow a friend of me told me to redownload the kernel that day because i didnt see it and now i just read that it bricked some devices.

i guess i will be less flash-happy with new kernel releases in the future
 

ninjazin

Senior Member
Sep 22, 2009
276
73
Stockholm
Happend to me as well. Luckily my warranty period was not over so I got the mainboard replaced by the service centre free of charge.
 

slk-A4

Senior Member
Nov 24, 2007
214
23
no more responses in this topic, so I guess all bricked phones are repaired by Samsung or are bricked for ever (for those who are out of warranty).
I would like to know how many S2s were bricked by Siyah´s Kernel
 

advr

Senior Member
Mar 5, 2007
236
22
i have wrote a guide in a forum, what helps many peoples there with similar problems, like bootloops, not flashable and so on...

its in german, but think googletranslate can do ;)
http://www.pocketpc.ch/samsung-gala...ranleitung-bereinigung-bootproblemen-etc.html

short... the thing is that THE BOOTLOADER from KH3 only can make the internal card working again!!! here you can download it from my dropbox.

flash this with odin, battery out, downloadmode, flash a 3part samfirmware, i recomend LPJ, because, last 3part.
then you can flash after a factoryreset all what you want ;)


This is what I was looking for!!

My GS2 is back on track!!

YES!!

Thanks!

Ad.
 

spike86

Member
Apr 25, 2012
14
4
Hi! just ordered the new board! how should it come? Is os already flashed or i need to flash it myself?
 

crusaderlong

Member
Nov 6, 2012
6
0
samsung s2 bricked

Hi Folks

I have rooted my device priorly and tried to update the device to Jelly Bean.
1. Flashed cache
2. Installed Speed mod kernel from the package

Speedmod Kernel:

Leaked ROM:

3. Restarted device in recovery mode
4. there was no display (went down with dimm pixels)
5. Hence restarted with (volume down_power+center button)
6. Via Odin updated the below
PIT:eek:map4_all_20110627_emmc.pit
PDA:CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.tar


Then device went black and now im not able to do any thing.
Is there any one who have come across this situation. If recovered plz share your comments.
 

atulalvenkar

Senior Member
Mar 8, 2011
1,029
364
Hyderabad
Hi Folks

I have rooted my device priorly and tried to update the device to Jelly Bean.
1. Flashed cache
2. Installed Speed mod kernel from the package

Speedmod Kernel:

Leaked ROM:

3. Restarted device in recovery mode
4. there was no display (went down with dimm pixels)
5. Hence restarted with (volume down_power+center button)
6. Via Odin updated the below
PIT:eek:map4_all_20110627_emmc.pit
PDA:CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.tar


Then device went black and now im not able to do any thing.
Is there any one who have come across this situation. If recovered plz share your comments.

Why did you flash a pit file? From the name it looks like the pit file is for other SGS2 i.e I9100G as it says OMAP.

Can you boot into download mode? If not your device might have been permanently bricked and you will need to either go for JTAG or
go to service center.
 

crusaderlong

Member
Nov 6, 2012
6
0
Since im new to this concept. I followed a stupid forum and just followed the steps. And this is where i end up now.

Finally, as you said i have given my hadset to samsung service centre and keeping my fingers crossed.

Lets hope for the best.

Thanks for your reply- atulalvenkar



Why did you flash a pit file? From the name it looks like the pit file is for other SGS2 i.e I9100G as it says OMAP.

Can you boot into download mode? If not your device might have been permanently bricked and you will need to either go for JTAG or
go to service center.
 

atulalvenkar

Senior Member
Mar 8, 2011
1,029
364
Hyderabad
Since im new to this concept. I followed a stupid forum and just followed the steps. And this is where i end up now.

Finally, as you said i have given my hadset to samsung service centre and keeping my fingers crossed.

Lets hope for the best.

Thanks for your reply- atulalvenkar

You've basically flashed firmware meant for a totally different phone on your phone. Although both phones use SGS2 name they are very
different internally. The one talked about in this forum is I9100. The firmware you flashed is for I9100G.

If you have warranty it might be fixed under it. if not then they'll have to replace motherboard and charge about $150-200 depending on your
country.
 

crusaderlong

Member
Nov 6, 2012
6
0
Atulalvenkar

Ar you sure, Replacing the motherboard is the only solution . Bcoz i read sometimes flashing the s/w also would fix the issue. Is it true?
If replaceing the MB is the only solution then in have to stop putting effort on this.




You've basically flashed firmware meant for a totally different phone on your phone. Although both phones use SGS2 name they are very
different internally. The one talked about in this forum is I9100. The firmware you flashed is for I9100G.

If you have warranty it might be fixed under it. if not then they'll have to replace motherboard and charge about $150-200 depending on your
country.
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Atulalvenkar

Ar you sure, Replacing the motherboard is the only solution . Bcoz i read sometimes flashing the s/w also would fix the issue. Is it true?
If replaceing the MB is the only solution then in have to stop putting effort on this.

It looks like your brick has nothing to do with Superbrick. Looks like a traditional hardbrick. JTAG will probably fix you.

Please do more research and find the correct thread to discuss this, as you've necroed a completely unrelated thread (since all Siyah 3.1rc6 downloads were pulled months ago, this is the wrong thread.)
 

crusaderlong

Member
Nov 6, 2012
6
0
It looks like your brick has nothing to do with Superbrick. Looks like a traditional hardbrick. JTAG will probably fix you.

Please do more research and find the correct thread to discuss this, as you've necroed a completely unrelated thread (since all Siyah 3.1rc6 downloads were pulled months ago, this is the wrong thread.)

If this is not the correct thread .. Ten which the right one. :(
 

Scarface1991

Senior Member
Jul 30, 2011
2,602
1,642
If this is not the correct thread .. Ten which the right one. :(


Like others said, you probably messed up the bootloader and when you can`t go into download mode anymore and there is no sign of life from your device, then either try for service center, if you still have warranty or give it to someone who can repair it via JTag.

What country are you living in?
I live in Germany and I saw people in German Forums that they do JTag repair for a little cash. Just try to find someone who can do this for you.
 

crusaderlong

Member
Nov 6, 2012
6
0
I live in India. If Jtag is the prime way. Then i have to find a geek..


Like others said, you probably messed up the bootloader and when you can`t go into download mode anymore and there is no sign of life from your device, then either try for service center, if you still have warranty or give it to someone who can repair it via JTag.

What country are you living in?
I live in Germany and I saw people in German Forums that they do JTag repair for a little cash. Just try to find someone who can do this for you.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    release candidate = not final = beta = not fully tested =still bugs = bricked = bug = because still beta= your own risk = your fault. Hope this helps.

    Sent from my GT-I9100 using xda premium
    27
    This is one of those unfortunate incidents development efforts revealed such a result, which seems a bug in Samsung official kernel is causing it in one of the latest updates. Any developer, other than Gökhan, could have used the same sources for his kernel and got a similar result.

    this is exactly what happened.

    I used M250(S/L/K) sources as base. that device has the same specs as our device.

    I flash the kernel to my device and then upload. but there is no way that I can test/review Samsung's official kernel sources in every detail. I always avoid changes which can harm our devices but the problem is not caused by a change made by me.

    The same problem occurred with other devices which use exynos4 such as galaxy note, i777 and korean variants. we are just lucky that our stock kernel doesn't have that problem or everybody using cfroot would be having the same problem. other devices had the same problem and people were blaming improper packing of cwm recovery because there was no other change in the kernel image (it was not compiled), until we had the same problem by changing only the Samsung base.

    In other words, if you download and compile the official ICS sources for korean variant from Samsung's site and pack it with CWM Recovery, you will have the same problem. I doubt it happens only on high I/O load.

    although there is no proof of that some of us think that it only occurs if you use old gingerbread bootloader to be able to use jig to reset binary counter.

    I feel terribly bad for those who had that problem and I am very sorry for what happened. I wish I had a solution for that.
    I wish there was a way for me to foreseen that problem or test but there wasn't.
    I understand that people who had their devices bricked are angry and think that the problem is caused by me. In a way, they are right, it was my existence which made that problem occur. However, I want to restate that it was not caused by any of my changes and it was not my intention to brick your devices.
    I hope Service Center's will fix the problem.
    25
    ...
    The thing shocked me more than siyah kernel's bug is that how easy brickable our SGS2s are!
    ...

    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.
    22
    two weeks ago i disliked arrogance as much as i do today....!!!!Never heard of a kernel so much or any damage like this guys work.A new motherboard is just 1 of the 3 major parts they had to change.YOU dont know me from adam boy,so how can you say what i was PROBABLY doing to weeks ago.idiot.

    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...
    7
    On 22.4.2012 many people bricked their S2 while performing full wipe having Siyah kernel 3.1RC6.
    What disappointed me is the update on development coming from developer in real hurry these days.
    Developer need to test their development 1000 times before releasing it to users.
    As a rule only we the user are responsible flashed kernel knowing the risk of RCs and BETAs.
    We can't blame developer for this disaster
    .........
    This thread is for those who bricked S2 and now are in process to recover their devices.
    As a general habit, posts on bricked devices can be avoided easily by fan boys.
    So now we need to help each other in the process of device recovery.
    Please discuss here, what you are doing, any fix whether you found or not.

    Thanks
    Kachrukamble