Official Samsung Galaxy Note (N7000) Thread

Premature with your testing, the brickbug is in ICS, not GB. Your potential problems only start after ur upgrade.

I did the upgrade without even knowing the risks, my phones working fine, but I was personally pretty close to a factory reset after some incorrect adjustments to my build.prop file. Luckily I had finished all my setting up so I went for a reflash instead which fixed the file.

I see... My mistake then.....:D

I had a look on sammobile and saw the UK Rom was the LQ2 or something to that effect.... Isn't the UK version of ics on the suspect list of the brickbug...? Is there a list of the safe roms, stock ones and customs...? And also unsafe ones...?
 
I see... My mistake then.....:D

I had a look on sammobile and saw the UK Rom was the LQ2 or something to that effect.... Isn't the UK version of ics on the suspect list of the brickbug...? Is there a list of the safe roms, stock ones and customs...? And also unsafe ones...?

The eMMC bricking issue is kernel related, not ROM related. It is triggered by doing a factory reset/data wipe in CWM for the most part, which is why they advise you to not flash kernel's via CWM. Seems that even a factory reset in the Settings menu can possibly brick it.

From XDA:

Don't do a wipe/factory reset, don't do a Nandroid restore with an unsafe kernel, and ESPECIALLY don't flash anything in CWM with an unsafe kernel.

Chainfire's latest CF-Root kernels should render wiping and Nandroid restores safe by disabling the trigger conditions in the recovery binary, but it is not possible to render ZIP flashing safe in this manner. (The ZIP itself contains the binary that does the format operation.)


FWIW- Rather be patient and wait for more confirmed safe kernels. So far, only two are deemed safe.
 
The eMMC bricking issue is kernel related, not ROM related. It is triggered by doing a factory reset/data wipe in CWM for the most part, which is why they advise you to not flash kernel's via CWM. Seems that even a factory reset in the Settings menu can possibly brick it.

From XDA:

Don't do a wipe/factory reset, don't do a Nandroid restore with an unsafe kernel, and ESPECIALLY don't flash anything in CWM with an unsafe kernel.

Chainfire's latest CF-Root kernels should render wiping and Nandroid restores safe by disabling the trigger conditions in the recovery binary, but it is not possible to render ZIP flashing safe in this manner. (The ZIP itself contains the binary that does the format operation.)


FWIW- Rather be patient and wait for more confirmed safe kernels. So far, only two are deemed safe.

That may also explain why CWM has no bootloader available, I tried installing it twice from CWM and the Note was never in the confirm list so I kept just canceling it. I flashed a 1 time CWT to install SU.
Read on that link you posted, recovery is also not the only way, at least 1 confirmed bricked device using factory reset in the phones settings. Seems any form of usage of the recovery, no matter where you trigger it from is dangerous.

They also do say the bug is essentially random and is not guaranteed to trigger, but I agree with the statement "but even a 5% chance is far more dangerous than the effectively 0% chance" so far I have only ever needed to use any form of recovery related stuffs when flashing custom roms which I had no intention of doing with my note anyway. Personally just find it too suspect that the official ROM is 655mb and the custs I have found so far have all been under 150mb, I can understand a size difference, but one that great just makes me wonder.

Only reason I ever used a custom ROM was to get ICS onto my nexus S and other than deep idle, and some of the govenors I liked, I never used any of the additional features that CM9 had over stock and well Deep Idle was buggy till v7 anyway.
 
Ok. Do no cwm for the note. And from what I can tell on this forum and xda is that custom roms with custom kernels are suspect. If you choose a stock Rom, released by Samsung, maybe from sammobile, then all should be fine as you wouldn't have the need to factory wipe.....
 
Ok. Do no cwm for the note. And from what I can tell on this forum and xda is that custom roms with custom kernels are suspect. If you choose a stock Rom, released by Samsung, maybe from sammobile, then all should be fine as you wouldn't have the need to factory wipe.....

Official rom directly from samsung incl kies updates are affected, using them just decreases ur likelyhood of needing to use any of the trigger actions.
 
Oh my.... I didn't know that. But in a case that ics is released through kies and we all update. Should one of us do a factory reset from within the settings menu and the phone bricks, would the warranty still be fine.... As long as you not rooted ofcourse....
 
Oh my.... I didn't know that. But in a case that ics is released through kies and we all update. Should one of us do a factory reset from within the settings menu and the phone bricks, would the warranty still be fine.... As long as you not rooted ofcourse....

Warranty is still fine, just a major schlep. 3 week round trip for a phone repair and the major inconvenience of restoration. Problem would lie with the odin users, not sure what effect that would have on your warranty.

from what I know once its bricked it needs a hw reset, I bricked my nexus s, but if sammy sa can check ur rom, they know ics aint available locally yet.

Problem was originally believed to be a problem with cwm and custom roms, but later came out that the root cause comes from the official samsung kernal.

Apparently its 1 line of code that badly interacts with the specific hardware of the note, s3 and evo g(i think).

Of the reported cases from what I read, only 1 so far is from an official unmodified rom/kernal.

I am using the UK firmware from sammobile, I don't with core stuffs, my experience with custom kernals has been dismal and have removed CWM. Actually removed CWM before reading all this as I had no intention of putting on a custom rom, if it aint broken, don't fix it.

I will however enable TB's auto backup and probably by that sync app someone recomended in another topic to send said bacup to my pc. At least then of anything terrible doeas happen Im at most a few days out on my app data.
 
Last edited:
I have sent devices in under warranty that were rooted and custom ROMed and no issues.
I don't think this is something to be overly concerned about.
 
Last edited:
Warranty is still fine, just a major schlep. 3 week round trip for a phone repair and the major inconvenience of restoration. Problem would lie with the odin users, not sure what effect that would have on your warranty.

from what I know once its bricked it needs a hw reset, I bricked my nexus s, but if sammy sa can check ur rom, they know ics aint available locally yet.

Problem was originally believed to be a problem with cwm and custom roms, but later came out that the root cause comes from the official samsung kernal.

Apparently its 1 line of code that badly interacts with the specific hardware of the note, s3 and evo g(i think).

Of the reported cases from what I read, only 1 so far is from an official unmodified rom/kernal.

I am using the UK firmware from sammobile, I don't with core stuffs, my experience with custom kernals has been dismal and have removed CWM. Actually removed CWM before reading all this as I had no intention of putting on a custom rom, if it aint broken, don't fix it.

I will however enable TB's auto backup and probably by that sync app someone recomended in another topic to send said bacup to my pc. At least then of anything terrible doeas happen Im at most a few days out on my app data.

Ok, this has put me at ease.... I'm going to wait a bit till my 7 days has passed for returns (only got my note Friday past) so once that has passed, I'll download the UK ics Rom off sammobile, flash with odin pc and then root. At least that way I don't have to wipe data or anything, just flash and go.... I think I'll also download the LA4 GB firmware, just in case I need to send the phone in for repaires..... I think that will be the best option as I think the last time I wiped data on my s2 was about a month ago and that was when I installed the SA ics rom, I wanted a clean install as my themes and launchers were giving issues.... I should be safe that way....
 
Quick question folks. I'm on CM9 and Abyssnote redpill 4.2 kernel just now but it's not as smooth as I'd like. If I want to install the UK stock ics from sammobile, would I be okay to just flash directly from odin?
 
shame it sounds like you guys have to seek ics for the note from elsewhere for the meantime.i flashed polish ics from sammobile when it was released for the gs2 and rightly so because it took a couple of months to get the official from vodacom.i hope the wait isn't to long for everyone who doesn't want to go down the flashing/custom rom road.
 
Quick question folks. I'm on CM9 and Abyssnote redpill 4.2 kernel just now but it's not as smooth as I'd like. If I want to install the UK stock ics from sammobile, would I be okay to just flash directly from odin?

You should be fine, but I have no exp with that kernel to say weather or not its affected. As I mentioned earlier, no warnings were made about odin, just recovery mode. Someone posted a link to the checking app, not sure if it was in this thread or my one "Galaxy Note ICS" they mentioned searching play store but I found nothing.

I have flashed using odin twice on my new note and am replying from it.
 
Just search for brickbug in the play store. Should come up with only 1 result which is the one you need....
 
Left my micro usb cable at work. Will just go ahead and flash through odin tomorrow.
 
Just search for brickbug in the play store. Should come up with only 1 result which is the one you need....

I found it. It tells me 'yes, insane chip'. Now I just need to figure out wtf that means....?
 
not sure if you guys have indeed read of the posts for your relevant rom that you want to flash.

The procedure for most roms to flash is to reboot in recovery...
1. Make nandroid backup if you want.
2. Flash Abyss Kernel
3. Advance - Reboot Recovery
4. 3 Wipes
5. Flash rom...

Its really as simple as that.
 
not sure if you guys have indeed read of the posts for your relevant rom that you want to flash.

The procedure for most roms to flash is to reboot in recovery...
1. Make nandroid backup if you want.
2. Flash Abyss Kernel
3. Advance - Reboot Recovery
4. 3 Wipes
5. Flash rom...

Its really as simple as that.

Does this apply for ICS roms as well. Ever since the warnings on XDA, I'm extremely concerned about anything to do with recovery mode, wipes and cwm... Can you confirm if this has worked for you...?
 
Does this apply for ICS roms as well. Ever since the warnings on XDA, I'm extremely concerned about anything to do with recovery mode, wipes and cwm... Can you confirm if this has worked for you...?

Applicable yes, advisable NO. With the current bug its a very good idea to stay away from recovery if at all possible. There is no definite list of what exactly bricks the phone., The Abyss Kernel is said to be one of the safe Kernels, but unless your planning on constantly changing roms, messing around with recovery and screwing your phone to the point of needing recovery I would just leave well alone.
 
That's just it. I'm not interested in recovery or cwm, I'm not a flashaholic anymore, I've realised that for me, a stock rom is perfect... I just need to load the rom, and that's it... So I'm not even sure if I should worry about bricking, cause once I've flashed the rom I want, then I'm sorted....

Questions, questions.....:confused:
 
I dont see the problem... I haven't had any problems and I have flashed roms up to twice a day. and I also do the procedure as stated in my previous post.

If you are changing from a ics kernel... reboot recovery flash abyss --->advance reboot recovery --->wipes 3 and flash new roms...

I have gone from Paranoidandroid to kingdroid to rocketrom to aokp build 38 to paranoidandroid to rocketrom to aokp build 39 and so the list goes on...

I have changed kernels... speedmod...thor...
I have flashed modems....

All using recovery mode in cwm no problems... phone still functioning like a champ.

Currently using Kingdroid v3 with S3 addons and speedmod kernel 3.3

This method works for me.
 
Top
Sign up to the MyBroadband newsletter
X