Database Users

Kernel issue - Bricked By a Stunner Rom version

Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.

I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?

gedster314 said:
I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?
Click to expand...
Click to collapse
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2

octavian90 said:
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Your right. Why don't you just give the guy razor blades and sleeping tablets even before he explains his issue.
Yes I'm new to the Note but I have brought back many phones back from the "BRICK".

Nothing works, I can't boot into download or recovery

Any ICS kernel based on the leaks seems to carry a danger of permanent damage to the eMMC.
So far the only safe Samsung ICS kernels seem to be those based on the I9100 update4 source base.

Well what would you recommend I do from here though? I want to get this fixed as soon as possible.

Check the end of stunner thread... Send it to mobile video review for jtag
Sent from my GT-N7000 using Tapatalk 2

every time i consider bumping to a Custom ICS I see a thread like this or some issue that is a showstopper for me.
I'm glad I haven't yet had ICS.

I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.

sutekidane said:
I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.
Click to expand...
Click to collapse
don't lower your hopes down, I've seen countless and numerous times of Bricked Notes being revived and restored thru JTAG. This process is the much low level process you can get of restoring your Note into it's normal process. I don't see why your Note can't be restored if it's done thru JTAG.
(Not unless you have a broken ICs or chipsets already, which contitutes a hardware failure and that's the time you may have to replace it.)
JTAG is trusted already and proven to restore almost all bricked Notes.
Just from my own experiences..
Cheers

Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium

sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck

MrSlippyFist said:
sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck
Click to expand...
Click to collapse
Just installed 1 4.26... I would recommend you to try it...its on another level than beta 5 ...very smooth n stable
Sent from my GT-N7000 using xda premium

thebz1 said:
Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.
Click to expand...
Click to collapse
try to use jig bro maybe it will solve the gnote

Oh no...not another CWM touch recovery-esque fiasco. I thought we were over that? And, damn that sucks dude. I've been in your exact shoes. This is my second phone, and I currently use Stunner as my daily driver...so I'm a bit worried now!

androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
so why aren't the other roms running lp5 bricking the phone?

androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
No it's a specific problème of stunner... It happens...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Envoyé depuis mon GT-N7000 avec Tapatalk

thebz1 said:
Well what would you recommend I do from here though? I want to get this fixed as soon as possible.
Click to expand...
Click to collapse
do you have a JIG or the tools to create one by yourself ? this seems your only solution for now, anyway does your phone enter to boot animation or it just doesn't flick ?!

there isnt much any of us who had our phones bricked can do about, and yes it was a version of ics stunner that did the damage, i have a feeling its gonna be a motherboard replacement

back and menu buttons stopped working

bell galaxy s vibrant. i did the #*#*2663*#*# in the dialer and then updated the touchkey firmware and now both touchkeys dont work. tried flashing back to stock ugkg3 with odin. didnt fix. now the phone has ics milestone 5 on it and they still dont work. luckily the nav bar can be used and customized. how can i reenable the buttons?

Try flashing an older from in Odin. Something 2.2 from bell.
Sent from my GT-I9000 using Tapatalk 2

but if flashing back to stock 2.3.3 in odin didnt work why would that? i guess ill try

If not I'd say the buttons are just dead.
Sent from my GT-I9000 using Tapatalk 2

lol why was i able to simply click something that killed my buttons. kinda crappy

Currently I am in your boat as well with those buttons dead, but even though I am on 2.2, my kernel is different (I got other problems, phone won't work with stock kernel), I still can't fix my problem. So, yours might get fixed cause you're on stock on everything, try using 2.2 or lower. It should fix, unlike me.

im not on stock, im on 4.0.4 ice cream sandwhich, aokp milestone 5 rom

you should do the same so u can enable the nav buttons and forget the physical ones. u can have home menu back and multitask on the nav bar, plus the phone runs soooooooooooooooooooooo much smoother, its like i traded an old vibrant for a galaxy nexus

I have this problem before probably a year ago and I fixed it, I think, by first flash the stock 2.2 rom, then after the flash go to that menu again (which caused this trouble) and hit update again.. If it works then flash the 2.3 or better.. This is from my memory from a year or so ago
It is fixable and I got the fix method from this forum.. Forgot exactly which thread since it has been long time.
Good luck!
Sent from my Galaxy Nexus using XDA

Speedum said:
I have this problem before probably a year ago and I fixed it, I think, by first flash the stock 2.2 rom, then after the flash go to that menu again (which caused this trouble) and hit update again.. If it works then flash the 2.3 or better.. This is from my memory from a year or so ago
It is fixable and I got the fix method from this forum.. Forgot exactly which thread since it has been long time.
Good luck!
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Buddy that's what I wrote in my post, but showed the only difference I have is that I have to use custom (speedmod kernel) kernel to boot up otherwise my phone won't start. So, when I get back to everything stock, I will for sure try that number thing again on 2.2 to fix it. Thanks.

i will try too and report

Dit it?
grasshoxda said:
i will try too and report
Click to expand...
Click to collapse
So, dit it work? :fingers-crossed:
Cheers,
AT

[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

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.

Google released Jelly Bean update 4.1.2

Google today released update for nexus 7 Build Android 4.1.2. Added landscape mode..
Source code in AOSP.

Hoping this version of Android will be on the 7.7.

marwanxx said:
Hoping this version of Android will be on the 7.7.
Click to expand...
Click to collapse
haha i don't think so ^_^
best regards
Sifou
Galaxy Tab 7.7

Nothing is imposible.

It already merged by CM and you will get it on PA 2.18
Sent from my Nexus S using Tapatalk 2

yeah, i get a number (4.1.2 instead of 4.0.4) what's the big deal?
best regards
Sifou
Galaxy Tab 7.7

sos_sifou said:
yeah, i get a number (4.1.2 instead of 4.0.4) what's the big deal?
Click to expand...
Click to collapse
not only number is changed. I'm using custom Paranoid ROM on my Galaxy tab 7.7. It has better performance and looks nicer ) User interface veery smoth

well, i must admit that the software experience improved a lot (its a huge improvement) from honeycomb to ics.
i dont think that it will be the same from ics to JB, or the 4.1.2
best regards
Sifou
Galaxy Tab 7.7

If 7.7 doesn't get the JB update from Samsung I will sell my tab and gets an Ipad.:victory:

how to install this rom ?
albert.mob said:
not only number is changed. I'm using custom Paranoid ROM on my Galaxy tab 7.7. It has better performance and looks nicer ) User interface veery smoth
Click to expand...
Click to collapse
hello, would you like to tell me please how did you installed this rom on tab 7.7 ? all whay i know is after installing this rom or other roms you will not get calls and bluetooth and wifi issues ... gps will not work anymore.. then what s the use behind ?

sos_sifou said:
well, i must admit that the software experience improved a lot (its a huge improvement) from honeycomb to ics.
i dont think that it will be the same from ics to JB, or the 4.1.2
best regards
Sifou
Galaxy Tab 7.7
Click to expand...
Click to collapse
Well, FWIW ICS to JB (4.1.2 or 4.2.2) on my other tabs makes a marked improvement in the overall speed and fluidity of the tabs. Whether or not the same will hold true when (or if) the 7.7 gets stock 4.1.2 or 4.2.2 remains to be seen.

is there anyone of you that still uses stock firmware like me? tried PA but have to revert back to stock ics despite the brick bug danger

If you mean stock as in from samsung, yes, I have it on my tab but I am using a different launcher though to speed things up.

ascariss said:
If you mean stock as in from samsung, yes, I have it on my tab but I am using a different launcher though to speed things up.
Click to expand...
Click to collapse
me too..using nova launcher instead of the ugly touchwiz..i can live without the bells and whistles of PA because stock is stable

JAYZE said:
is there anyone of you that still uses stock firmware like me? tried PA but have to revert back to stock ics despite the brick bug danger
Click to expand...
Click to collapse
The "BrickBug" has had me spooked also. But, after reading as much as I could from other sources, flashing CWM alleviates that issue. That said I still would shy away from Factory Reset from ICS nevertheless. Or proceed with caution.
Granted I could be wrong but am always on the lookout for a definitive "fix".

skeeterpro said:
The "BrickBug" has had me spooked also. But, after reading as much as I could from other sources, flashing CWM alleviates that issue. That said I still would shy away from Factory Reset from ICS nevertheless. Or proceed with caution.
Granted I could be wrong but am always on the lookout for a definitive "fix".
Click to expand...
Click to collapse
so true..but i still encountered some soft bricks randomly when many apps were installed..for instance when i used the offline feature of Google Currents..my tab won't flash via odin so i have to reset using cwm many times..
do you think the new jelly bean firmware is free from brick bug?

JAYZE said:
so true..but i still encountered some soft bricks randomly when many apps were installed..for instance when i used the offline feature of Google Currents..my tab won't flash via odin so i have to reset using cwm many times..
do you think the new jelly bean firmware is free from brick bug?
Click to expand...
Click to collapse
One hopes so. But I'll always include CWM/kernel substitution. I'll deal with soft brick any day of the week compared to hard brick. Even jtag has failed for some.

JAYZE said:
me too..using nova launcher instead of the ugly touchwiz..i can live without the bells and whistles of PA because stock is stable
Click to expand...
Click to collapse
+1
Stock + nova here... This is good enough for me.
Im waiting for the JB update too, but i can live without it.
Sent from my HTC One X using xda premium

Arobase40 said:
Me too I use a stock firmware or if I use a custom firmware, I always replace the custom "safe kernel" with the stock kernel from Samsung.
Sorry to repeat it again, but I never got any issues with Samsung stock kernel whether with my G-Note or my GT P6800.
The sole time I got a brickbug was with a custom firmware on my G-Note as I forgot to replace the custom "safe kernel (from PhilZ)" with a Samsung stock one... ^^
Once my G-Note got repaired, I reflashed it with the same ICS custom firmware but that time with a stock kernel and I never got brickbug again, despite numerous Factory Resets.
My G-Note has now a completely stock Jelly Bean 4.1.2 from Samsung and so far so good no issue at all !!!
My GT P6800 is still with a stock ICS 4.0.4 from Samsung and I don't plan to use any custom firmware since it works fine with a very good battery life time.
The only change I made both on my G-Note or P6800 was to root them.
Click to expand...
Click to collapse
Pretty close to the same here. Am under the distinct impression that rooting and using CWM also offers as much "protection" from brickbug as can be had at the moment. Running LQ1 right now but was considering flashing LQ2. Looking for a bit better battery.
Been following daniel_hk in the Android section. His work on the JB CM10.1 looks very very promising! Check it out!

Arobase40 said:
Sorry for daniel_hk or any other Cyanogen devs I'm not willing to flash any Cyanogen ROM as I want to keep compatibility with all stock Touchwiz apps and features, and more importantly I don't want to mess up my GT 7.7 as I don't plan to change it for another device as long as it suffices my needs.
Click to expand...
Click to collapse
I 100% agree with you, CM might be the latest and greatest of all Roms but in my opinion if all the features are not working as they should why should I even bother. I know it's a choice whether to install or not and I appreciate what the CM devs have done for our community but I just don't like how they have approached our tab, if you are not going to have a 100% working rom then don't put it out there.:banghead: Sorry for my little rant. I am just patiently waiting for JB if it ever comes out if not I am quite happy with ICS.
Sent from my GT-P6800 using xda premium