Database Users

Siyah kernel 3.1RC6 and BRICKED GALAXY S2

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

kachrukamble said:
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
Click to expand...
Click to collapse
Sad story bro. I know that feeling.
GM must be happy to hear that
Sent via my s2 monster

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

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?

RobinRichard said:
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?
Click to expand...
Click to collapse
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??

bala_gamer said:
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??
Click to expand...
Click to collapse
What the hell happened? Efs cleared?
Gesendet von meinem GT-I9100 mit Tapatalk

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

Ghost-of-the-Sun said:
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
Click to expand...
Click to collapse
if you can access download mode, then you have many ways to recover your s2 without reaching SC

RobinRichard said:
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?
Click to expand...
Click to collapse
Happy to hear that you saved, many people didnt
Sent from my HTC EVO 3D X515m using Tapatalk

bala_gamer said:
if you can access download mode, then you have many ways to recover your s2 without reaching SC
Click to expand...
Click to collapse
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 :-(

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.

Ghost-of-the-Sun said:
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 :-(
Click to expand...
Click to collapse
Did anyone try flashing a boot loader? Nothing to lose now really
Sent from my GT-I9100 using xda premium

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...

Ghost-of-the-Sun said:
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 :-(
Click to expand...
Click to collapse
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

Dang I'm on siyah rc6 still running, if I flash 3.1 or another kernel its safe right?
Its safe using cwm app

is CWM available at all on Siyah bricked mobiles?

bartoloandre98 said:
Dang I'm on siyah rc6 still running, if I flash 3.1 or another kernel its safe right?
Its safe using cwm app
Click to expand...
Click to collapse
flash immediately 3.1 without wipe
---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------
itchetrigr said:
is CWM available at all on Siyah bricked mobiles?
Click to expand...
Click to collapse
its available but working with errors because of the mount problem of some partitions.

itchetrigr said:
is CWM available at all on Siyah bricked mobiles?
Click to expand...
Click to collapse
Bricked means dead in this case, you can't do anything with dead piece..

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!

Does anyone know how to find a jtag service in korea, seoul? my phone is fully bricked and i need it back asap ....

if u are chicken as me

i think to be in safe with ICS
1- u should forget the word of wipe with its Derivatives ( format and full earse ) neither from cwm or OS menu -FACTORY RESET -
2-U shouldn't delete large files or copy large files neither from built-in explorer or from mass storage
3-if u see a thread about ICS leak or repacked close it dont read
4-dont go back to GB as u may be bricked in the way to it
5-read all threads of galaxy note
that is what i really decided to do after i flashed lpf on my GT

Exactly the same as me, the only difference being that I am on LPY. Was not brave enough to move to LPF however I pleased with LPY because I am not having any issues with it yet.

HasC said:
Exactly the same as me, the only difference being that I am on LPY. Was not brave enough to move to LPF however I pleased with LPY because I am not having any issues with it yet.
Click to expand...
Click to collapse
i think there are chickens better than us while we are browsing the site they closed there GT and putting it at home in safe place.

I tried all possible combinations. .. I even did the cwm full wipe in german ics. . and installed a German and Taiwanese ics and returned to the gb. .. and all that i survived. seems to be fools really have a luck

sehooo said:
i think to be in safe with ICS
1- u should forget the word of wipe with its Derivatives ( format and full earse ) neither from cwm or OS menu -FACTORY RESET -
2-U shouldn't delete large files or copy large files neither from built-in explorer or from mass storage
3-if u see a thread about ICS leak or repacked close it dont read
4-dont go back to GB as u may be bricked in the way to it
5-read all threads of galaxy note
that is what i really decided to do after i flashed lpf on my GT
Click to expand...
Click to collapse
I am on RR V1 ICS with LPF kernel. I can proudly say, right now, I am a chicken too, haha

ukicar said:
I tried all possible combinations. .. I even did the cwm full wipe in german ics. . and installed a German and Taiwanese ics and returned to the gb. .. and all that i survived. seems to be fools really have a luck
Click to expand...
Click to collapse
I flashed LP1, Lp5, lp6, lpy and lpf from all release Im able to go back to GB roms no problem. All we need to follow is the golden rule..don't perform any wipe and if you do it will cause you sleepless nights. Been reading different threads and almost all brick incidents are after when they do full wipe or even cache and dalvik. Also having abyss 4.2 saves me a from misery if ever I want to do flashing from rom to rom same as restoringbmy GB back up.
Sent from my Nokia 3310 Using XDA Premium

sehooo said:
4-dont go back to GB as u may be bricked in the way to it
Click to expand...
Click to collapse
If you brick on the way back to GB and you are moving back to GB with Odin or Heimdall, then the damage was already done.
So yes, staying put and laying low will be safer on the assumption that your emmc is already corrupted and you wish to ride out the storm until a less than $200 solution is presented.
On the other hand, if your emmc is still good, the possibility of corrupting it inadvertently or by accident is infinitely greater by staying on an affected ICS build.
Personally the suspense was killing me so I took the gamble to move back and luckily did not brick...but the risk was real and I would not feel comfortable recommending to anyone else whether to do it or not.
My point is this, be informed that both decisions carry risks and it is up to each person to decide which risk is more acceptable for their situation.
Sent from my GT-N7000 using XDA

I never did any wipe on lpy so i simply flashed GB on pc odin.. then wipe on gb kernel
Sent from my GT-N7000 using XDA

No issues
Updated from non root, factory 2.3.6 to ICS, only thing I have done is
to use the root method CWM, NO other mods done to the device.
No issues....so far, gone on however long it was made available from
Kies.

[Q] Confused... ICS leaks can brick the Note, will official releases do the same?

I'm sorry. I SWEAR I read tons of threads but things still aren't clear to me.
ICS leaks seem to possibly brick the Note.
But there are several threads with official ICS firmwares for the Note (ex: http://forum.xda-developers.com/showthread.php?t=1646088)
Can I use the official ICS firmware to upgrade my Note? Or should I wait a bit more?
Thanks!

From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?

leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?
Click to expand...
Click to collapse
Kernel says 2.6.35.7-N7000UBKK8
I suppose I'll stay on GB. Things look a bit scary even with the stock kernel!

The official can brick the note muaaahuahuahuahuuaaa
Seriously as the previous poster said only if you are into wiping and restoring you MAY be in danger
Sent from my iPad using Tapatalk

fjhuerta said:
I'm sorry. I SWEAR I read tons of threads but things still aren't clear to me.
ICS leaks seem to possibly brick the Note.
But there are several threads with official ICS firmwares for the Note (ex: http://forum.xda-developers.com/showthread.php?t=1646088)
Can I use the official ICS firmware to upgrade my Note? Or should I wait a bit more?
Thanks!
Click to expand...
Click to collapse
Well I upgraded my Note and it is completely fine, my friend with a Note as well hasn't told me about his phone being bricked either. But I'm not sure about all the others though, since mine is the Hong Kong official one, and I never use the leaks so they don't really bother me.
Sent from my Galaxy Note

leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?
Click to expand...
Click to collapse
When you say factory reset you mean going into settings and then "data factory reset"? I normally do that after a huge update and format my SD card too. So that is a no no on ICS?
Sent from my GT-N7000 using xda premium

Hagow said:
When you say factory reset you mean going into settings and then "data factory reset"? I normally do that after a huge update and format my SD card too. So that is a no no on ICS?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
That is correct.

leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel.
Click to expand...
Click to collapse
Bull****. I have tried to do wipe from CWM and MobileOdin over and over again more than 15 times at ICS leaks and ICS stocks and custom kernels and custom ROMs. Never got any problem.

anonymous572 said:
Bull****. I have tried to do wipe from CWM and MobileOdin over and over again more than 15 times at ICS leaks and ICS stocks and custom kernels and custom ROMs. Never got any problem.
Click to expand...
Click to collapse
You might want to read the stickies in this forum regarding the fact that it's not an issue that effects all users. But it effects some by bricking their phones.
Along with the advice to not tell others that the problem doesn't exist based on your experience.

diji1 said:
You might want to read the stickies in this forum regarding the fact that it's not an issue that effects all users. But it effects some by bricking their phones.
Along with the advice to not tell others that the problem doesn't exist based on your experience.
Click to expand...
Click to collapse
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".

anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
How can you say that man,,,thr are so many ppl on Xda here that are reporting to have bricked thr devices......or are you saying that as long as you r not rooted , this bricking thing just wudn't happen?

anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
and I never saw anyone without this strange wipe problem, want to know for sure? go install an app by chainfire called got brickbug?
http://forum.xda-developers.com/showthread.php?t=1693704
maybe you are lucky to have an unaffected chip ,but 99.9% of users have a known damaged chip fw.
I suggest you go read the sticky in which it says that some people have wiped 19 times and got a full brick on the 20th attempt ,some even more .
I myself have wiped once safely ,but the second wipe made the emmc go nuts ,luckily however it was not fully dead ,and I restored it ,barely .
besides ,samsung and Google have both confirmed this bug ,so who are you to state otherwise?!!
http://forum.xda-developers.com/showthread.php?p=27137024
so I would like to suggest that you stop spreading dangerous miss information to the noobs or I'll report your post next time.

MR.change said:
besides ,samsung and Google have both confirmed this bug ,so who are you to state otherwise?!!
http://forum.xda-developers.com/showthread.php?p=27137024
so I would like to suggest that you stop spreading dangerous miss information to the noobs or I'll report your post next time.
Click to expand...
Click to collapse
+1
The source of the problem has been found and confirmed...how can people still be ignorant and spread bad advice.
As Mr.change said above, yes there is a problem even with official ICS, you may get lucky but you will run into a problem eventually if you keep wiping data/factory reset with affected ICS kernels...so best not to do so.

What would be the alternative to a factory reset then? I'm waiting to receive a new Note and intend to install stock ICS straight away but I worry that I'll mess up my first ever Android install and have to start again. Could you re.install the update without a wipe?

solarboy said:
What would be the alternative to a factory reset then? I'm waiting to receive a new Note and intend to install stock ICS straight away but I worry that I'll mess up my first ever Android install and have to start again. Could you re.install the update without a wipe?
Click to expand...
Click to collapse
if you are new to this then I would advise that you stay way from it till you learn your way around the basics of flashing using PC ODIN ,mobile ODIN ,and recovery.
then flash stock ICS with a safe custom kernels and you should be safe.
besides ,samsung stock ICS isn't that different from GB ,same look and same performance . you'd want to install CM9 to get a taste of true ICS.
so like I said ,take your time ,bricking your new shinny phone can be devastating .

anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
The problem is you don't know if you will hit the problem until you find out the hard way.
Once you've hit the problem there is no recovery.
So stop telling everyone that they are safe because you got lucky.
People who want to run ICS should use a kernel that has a safe configuration (MMC_CAP_ERASE removed from drivers/mmc/host/mshci.c) - This includes, but is not necessarily limited to (check the kernel's info) the CM9 included kernel, Hardcore's Speedmod ICS, and Franco.kernel r3 and above. Be sure to verify that you're running a safe kernel with CPUSpy before dropping into recovery - a few people had Mobile Odin fail to flash a safe kernel when they were on a dangerous one and then bricked because they didn't verify.

شكرا

solarboy said:
شكرا
Click to expand...
Click to collapse
you are most welcome my friend
لا شكر على واجب

nandihno said:
The official can brick the note muaaahuahuahuahuuaaa
Seriously as the previous poster said only if you are into wiping and restoring you MAY be in danger
What do u mean..? doing a factory reset is a common thing.. who on this earth doesn't do a factory data reset at all on their phone.. and if u ask me we must do a factory reset after updating to a new rom.
Pity on samsung.. their official builds destroy the phone. I can't believe.. how they released it without testing.. and why didnt the stop their ****ty ics update from being live till now..
i also have a question .. Has Samsung acknowledged the fact that their stock ics can cause bricking issues?
Click to expand...
Click to collapse

It was nice to meet you!!

It was nice 8 months experience,just Super bricked my Note while perfotming a wipe with CWM,too bad couldnt claim the warrenty.
Thanks for everyone who helped me during this period,both Developers and Members.
Jack

Sorry for your phone man.
Btw which kernel were you using?

Boy124 said:
Sorry for your phone man.
Btw which kernel were you using?
Click to expand...
Click to collapse
German LRK DBT stock 4.0.4 and it was running fine no problems,just wiped it to test the Paranoid Android JB 4.1.1,which was actually the last thing it did.

I see. But you can't flash roms using stock recovery. Anyways it confirms the bug still exists.

What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.

jgaviota said:
What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.
Click to expand...
Click to collapse
Unfortunately doesnt boot up,just stuck on the Gt-7000 logo but the download screen works,however when try to flash with PC Odin stops at the factoryfs.img which after research discovered is a Superbrick symptom.

hagba said:
too bad couldnt claim the warrenty.
Click to expand...
Click to collapse
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.

Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877

YLNdroid said:
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.
Click to expand...
Click to collapse
First thing on monday,

dr.ketan said:
Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877
Click to expand...
Click to collapse
Dr.Ketan,
I have tried the PIT procedure,but its such a long and tedious process Im not sure will be able to make viable partition for normal usage.
However will see what Samsung does on Monday.

So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.

He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium

dr.ketan said:
He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I made a mistake of wiping twice from Settings under android in Indian Stock DDLP8 stock 4.0.3 but luckily never bricked. But now I take care not to. But do you think I may have caused damage in the first two wipes? I see no issues till now but just asked.

It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium

dr.ketan said:
It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have the affected emmc firmware VYLOOM 0x19. Its just that I turned out to be lucky. I dont believe Samsung would fix the Indian firmware (4.0.3) while the bug remains on the latest 4.0.4 ROMS. If there is a fix from Samsung, we Indians are the ones who usually get it last. But strangely, I havent heard of any superbricked Indian Notes in this forum.

satishp said:
So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.
Click to expand...
Click to collapse
I think Samsung's claim was that you won't get bricked if you stick to stock and don't root. I'm not saying that's true . Even seems unlikely since I think you can factory wipe from the settings without root, IIRC (memory's rusty, haven't been on a stock ROM for ages).
There were some bricks with CM10, but only from people who flashed from stock ICS or stock ICS based ROMs. Flashing from the safe ICS kernels seems to still be safe.
satishp said:
But strangely, I havent heard of any superbricked Indian Notes in this forum.
Click to expand...
Click to collapse
Maybe that's because Indians are careful enough to read the instructions before risking their device? I doubt it's because Indian Notes have had some special pixie dust sprinkled over them while they passed customs.

If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium

dr.ketan said:
If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2

Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.

msedek said:
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2
Click to expand...
Click to collapse
It says big files shudn't be deleted. Though frankly speaking i have not seen any case brick by that, though we cant ignore comments from recognised developer.
But wat best idea i found to manage file is
Connect device with PC as mass storage and manage files from PC explorer. I believe that is safe way.
hagba said:
Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.
Click to expand...
Click to collapse
That was your bad luck this time, otherwise both have same effect.

Ics 4.0.3 xxlpy

Without looking I upgraded my Note N7000 from Gingerbread to ICS XXPLY which is a version with the dreaded brick bug. Not only did I install it OTA but I was having problems and actually did a hard reset yesterday. The phone is running fine but I have read that it's best to return to Gingerbread until the problem is resolved. Does that seem to be the consensus?
I'd appreciate your opinion.

humphster said:
Without looking I upgraded my Note N7000 from Gingerbread to ICS XXPLY which is a version with the dreaded brick bug. Not only did I install it OTA but I was having problems and actually did a hard reset yesterday. The phone is running fine but I have read that it's best to return to Gingerbread until the problem is resolved. Does that seem to be the consensus?
Click to expand...
Click to collapse
it all depends on how you feel about ICS, the brickbug itself should not happen under normal usage, only when you try to fectory reset / wipe operations,
so without doing those the only time you should be careful is when attempting to flash new ROMs (which may require you going with additional intermediate GB / safe kernel flashing - the safety instructions are always in the ROM thread),
the only thing I'd suggest - should you decide to stick with stock ICS - is upgrading to a newer version, like recent LRG (reportedly LPY was the worst ICS ROM in terms of battery life and performance)

Not only lpy, all ics stock roms having this bug. If you are worrying abt wiping you made, just find 'emmc brick bug' from market n scan device, if it nit damaged, then it shud pass.
If you are happy with ics then you can stay on it, but avoid wiping/reset.
Sent from my GT-N7000 using xda premium

Got Brickbug
dr.ketan said:
Not only lpy, all ics stock roms having this bug. If you are worrying abt wiping you made, just find 'emmc brick bug' from market n scan device, if it nit damaged, then it shud pass.
If you are happy with ics then you can stay on it, but avoid wiping/reset.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I downloaded the app and ran it. The "Verdict" was the the emmc chip (VYLOOM) is known to have the brick chip.
As I understand it, however, you are advising to go back to gingerbread or leave it alone.
I like ICS but not more than having my phone.
Thanks for your reply.

humphster said:
I downloaded the app and ran it. The "Verdict" was the the emmc chip (VYLOOM) is known to have the brick chip.
As I understand it, however, you are advising to go back to gingerbread or leave it alone.
I like ICS but not more than having my phone.
Thanks for your reply.
Click to expand...
Click to collapse
i say keep ICS and just download a safe kernel if ur into flashing custom roms.
You can stick with the stock kernel if you want just refrain from doing a factory reset

Thanks
chickentuna said:
i say keep ICS and just download a safe kernel if ur into flashing custom roms.
You can stick with the stock kernel if you want just refrain from doing a factory reset
Click to expand...
Click to collapse
I think I'll just hang on to what I've got and wait for the cavalry from Samsung.
Thanks to everybody.