Siyah kernel 3.1RC6 and BRICKED GALAXY S2

kachrukamble

Senior Member
Oct 21, 2010
5,065
1,337
113
Cloud
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
 
Last edited:

ram3n

Senior Member
Nov 16, 2010
1,040
1,364
0
Yesterday 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, BUT.........
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 easily avoided 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.
I will add Names for those who bricked S2 in OP
Thanks
Kachrukamble
Sad story bro. I know that feeling.

GM must be happy to hear that :D

Sent via my s2 monster
 

bala_gamer

Recognized Contributor
Mar 29, 2011
12,297
6,999
0
Madurai-Chennai
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
of course you can flash 3.1, it solves the issue. only the last updated rc6 had the problem. IF you are on rc6 better flash the updated kernel before doing any factory reset/data wipe to be in the safer side.


So did any one had a chance to solve it without going to service center??
 
  • Like
Reactions: RobinRichard

haasgo

Senior Member
May 22, 2011
1,050
463
0
Hamburg
of course you can flash 3.1, it solves the issue. only the last updated rc6 had the problem. IF you are on rc6 better flash the updated kernel before doing any factory reset/data wipe to be in the safer side.


So did any one had a chance to solve it without going to service center??
What the hell happened? Efs cleared?

Gesendet von meinem GT-I9100 mit Tapatalk
 

Ghost-of-the-Sun

Senior Member
Jan 6, 2012
210
36
0
I'm one of the "lucky" owners of a bricked-by-Siyah phone :(
I tried to flash a stock rom with odin but it doesn't work. I tried with:
- KI3, which is a 3-file-fw + .pit. The flash process hangs on data.img
- ILA2, which is a 1-file-fw. The flash with Odin is successful, but the phone can't boot and stays on the "Samsung Galaxy S2" screen all the time.

The only way to access recovery I found is to flash rogue recovery, but it can't mount internal sdcard so I can't flash anything
 

bala_gamer

Recognized Contributor
Mar 29, 2011
12,297
6,999
0
Madurai-Chennai
I'm one of the "lucky" owners of a bricked-by-Siyah phone :(
I tried to flash a stock rom with odin but it doesn't work. I tried with:
- KI3, which is a 3-file-fw + .pit. The flash process hangs on data.img
- ILA2, which is a 1-file-fw. The flash with Odin is successful, but the phone can't boot and stays on the "Samsung Galaxy S2" screen all the time.

The only way to access recovery I found is to flash rogue recovery, but it can't mount internal sdcard so I can't flash anything
if you can access download mode, then you have many ways to recover your s2 without reaching SC
 

kachrukamble

Senior Member
Oct 21, 2010
5,065
1,337
113
Cloud
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
Happy to hear that you saved, many people didnt

Sent from my HTC EVO 3D X515m using Tapatalk
 

TheSniperFan

Senior Member
Oct 14, 2011
621
187
0
Unless the hardware is damaged, every full-bricked Galaxy S2 can be recovered witha J-tag repair.
If one does not have the hardware hardware to perform such a repair, he has to either purchase it or find somebody that has it nearby.
 

jt999

Member
Jul 31, 2008
18
1
0
Mine is bricked, partly due to me not reading the posts. I'm able to get into download mode, will have a play with Odin on the off chance something fixes it but I guess it's unlikely...
 

haasgo

Senior Member
May 22, 2011
1,050
463
0
Hamburg
Yes I can access it, but the internal sdcard is never mounted so I can't use my phone... I hope somebody will find and share a fix for this problem :-(
Try to enter 3e recovery and factory reset phone and see what happens mate. Wait for like 5 mins and if buttons light up ur good...

Gesendet von meinem GT-I9100 mit Tapatalk
 

ninbert

Member
Oct 16, 2011
12
0
0
Dang I'm on siyah rc6 still running, if I flash 3.1 or another kernel its safe right?
Its safe using cwm app
flash immediately 3.1 without wipe

---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------

is CWM available at all on Siyah bricked mobiles?
its available but working with errors because of the mount problem of some partitions.
 

Logi_Ca1

Senior Member
Jun 29, 2011
475
98
0
Well this just reinforces my belief to stick with stock kernels.

To the people with bricked phones, hope you guys are able to unbrick it without too much pain! :(