Database Users

LPY ROM. Performance is fine. Do i need to worry?

I have flashed my rooted SGN to LPY ROM using mobile ODIN. First two days i had issues however now it seems fine.
1. Battery working fine 24Hrs on average with single charge (With 3G and Wifi on always)
2. No issues with screen or swype.
3. No issues with any other apps as of now
With all the Kernel related posts i'm a little worried. My phone kernel also shows as XXLPY. Please suggest if I need to do anythig to fix it.
Sent from my GT-N7000 using XDA

just do not do any full wipe, either from phone or CWM and you should be safe.

cracklenet said:
I have flashed my rooted SGN to LPY ROM using mobile ODIN. First two days i had issues however now it seems fine.
1. Battery working fine 24Hrs on average with single charge (With 3G and Wifi on always)
2. No issues with screen or swype.
3. No issues with any other apps as of now
With all the Kernel related posts i'm a little worried. My phone kernel also shows as XXLPY. Please suggest if I need to do anythig to fix it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Danger lies in changing ROMs, as long as you keep it you're safe.
Should you decide to flash sth different, then read the instructions several times, then again, and one more time, part of the bricks happened due to small mistakes by experienced flashers.
Sent from my GT-N7000 using xda premium

Is Full wipe and Factory Reset the same?
After installing the ROM i had done a factory reset. Nothing happemed but for some setting changes. I'm able the use without issues.
Please advise.
Sent from my GT-N7000 using XDA

cracklenet said:
Is Full wipe and Factory Reset the same?
After installing the ROM i had done a factory reset. Nothing happemed but for some setting changes. I'm able the use without issues.
Please advise.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
yeah someone pls reply to this question cause i flashed LPY twice and i did the factory reset and cleared the cache but did not get any problem.

I also flashed and wiped a couple of times while in LPY. I'm having no problems so far, but I read someone tried to flash with PC Odin and brocked because his eMMC was ALREADY damaged.
Is there a way to know if my device has some kind of damage?

aami.aami said:
yeah someone pls reply to this question cause i flashed LPY twice and i did the factory reset and cleared the cache but did not get any problem.
Click to expand...
Click to collapse
Wipe data/factory reset is where the problem lies. You can do it and be fine but you could do it again and be bricked. I did a wipe after install before the problem was known.
Just do what has already been posted don't factory reset from cwm or settings. If changing rom read everything several times before flashing
Sent from my GT-N7000 using xda premium

cracklenet said:
I have flashed my rooted SGN to LPY ROM using mobile ODIN. First two days i had issues however now it seems fine.
1. Battery working fine 24Hrs on average with single charge (With 3G and Wifi on always)
2. No issues with screen or swype.
3. No issues with any other apps as of now
With all the Kernel related posts i'm a little worried. My phone kernel also shows as XXLPY. Please suggest if I need to do anythig to fix it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I am in the same boat as you bro. I think that you should stick to ICS for now. I am doing the same. It seems that google and samsung are already aware of this bug so i choose to wait instead of risking a bad flash. It seems that none of the methods are 100% right now so just i recommend you stick to ICS just be cautious and don't delete large files (larger than 1gb) and don't use CWM nor factory reset for now... In the end we are lucky we didnt get our devices bricked in the first place.

yllivia said:
I am in the same boat as you bro. I think that you should stick to ICS for now. I am doing the same. It seems that google and samsung are already aware of this bug so i choose to wait instead of risking a bad flash. It seems that none of the methods are 100% right now so just i recommend you stick to ICS just be cautious and don't delete large files (larger than 1gb) and don't use CWM nor factory reset for now... In the end we are lucky we didnt get our devices bricked in the first place.
Click to expand...
Click to collapse
there is already new ICS LPF, reportedly safe and faster than LPY - there is also/already dr ketan's guide on whats and hows

yllivia said:
I am in the same boat as you bro. I think that you should stick to ICS for now. I am doing the same. It seems that google and samsung are already aware of this bug so i choose to wait instead of risking a bad flash. It seems that none of the methods are 100% right now so just i recommend you stick to ICS just be cautious and don't delete large files (larger than 1gb) and don't use CWM nor factory reset for now... In the end we are lucky we didnt get our devices bricked in the first place.
Click to expand...
Click to collapse
yea ,,in the same boat as well and equally confused man .....
wish thr was a magic wand for this to fix it ,,,lol
so i guess most of us are finally deciding to stay on LPY even after entropy is saying to stay away from LPY ?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
p107r0 said:
there is already new ICS LPF, reportedly safe and faster than LPY - there is also/already dr ketan's guide on whats and hows
Click to expand...
Click to collapse
u see the issue with that idea is that most of us have already wiped the cache after installing LPY so now trying to go to LPF cud potentially result in bricking it .....what do ?

p107r0 said:
there is already new ICS LPF, reportedly safe and faster than LPY - there is also/already dr ketan's guide on whats and hows
Click to expand...
Click to collapse
From what i have read LPF has 0x19 firmware therefore has potentialy the same problem with bricking
Sent from my GT-N7000 using xda premium

Being afraid of the bug I flashed a rooted GB kernel before using Odin to upgrade from LPY to LPF The bug is apparently in the way the kernel sets the emmc chip erase process This apparently mainly affects the /data partition so flashing a gb kernel should be safe. I then used odin to update to the newer firmware.
Sent from my GT-N7000 using xda premium

gurnishdhillon said:
yea ,,in the same boat as well and equally confused man .....
wish thr was a magic wand for this to fix it ,,,lol
so i guess most of us are finally deciding to stay on LPY even after entropy is saying to stay away from LPY ?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
u see the issue with that idea is that most of us have already wiped the cache after installing LPY so now trying to go to LPF cud potentially result in bricking it .....what do ?
Click to expand...
Click to collapse
As far as i know there has been no reports of bricks on LPF but most of the people that flashed LPF flashed it from GB. We in the other hand are stuck we might have a leftover from flashing LPY. I would rather risk downgrading to GB then jumping to another unsettled ship. I am staying here just taking precautions NOT to use Recovery nor any kind of thing that involves wiping data.
Originally Posted by Chainfire
Ok so it still isn't really clear if the problem is still present in LPY, or if the issue is "left-over" due to previous ROMs.
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)
Click to expand...
Click to collapse

gurnishdhillon said:
yea ,,in the same boat as well and equally confused man .....
wish thr was a magic wand for this to fix it ,,,lol
so i guess most of us are finally deciding to stay on LPY even after entropy is saying to stay away from LPY ?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
u see the issue with that idea is that most of us have already wiped the cache after installing LPY so now trying to go to LPF cud potentially result in bricking it .....what do ?
Click to expand...
Click to collapse
What you can do is only swap the kernel using mobile odin. I swapped it with the LPF CF-Kernel and everything is fine. But be advised, LPF has not been confirmed to be save yet.
Sent from my Galaxy Note running ICS

cracklenet said:
Is Full wipe and Factory Reset the same?
After installing the ROM i had done a factory reset. Nothing happemed but for some setting changes. I'm able the use without issues.
Please advise.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Yes. The problem is intermittent - you can often wipe once or twice, sometimes even ten times, before getting nailed.
Others (like xplodwild) get nailed the first time.

craig432 said:
From what i have read LPF has 0x19 firmware therefore has potentialy the same problem with bricking
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
No, XXLPY/ZSLPF don't "have" the eMMC firmware. The eMMC firmware is part of the eMMC chip itself - right now, whatever you have is what came with your phone. There is currently no way to change it.
The problem is that the firmware has a bug that will cause it to sometimes do VERY bad things if an erase command is sent to it:
I9100 update4 kernels don't support MMC ERASE at all - so they don't trigger the bug in the firmware in the first place
M250S Update5 does - So it triggers the bug - We don't have source for any other ICS kernel yet but I suspect they all have MMC_CAP_ERASE set
What I can't figure out is why Gingerbread isn't dangerous despite having MMC_CAP_ERASE set. I need to read in more detail, but it might be that even if the driver supports MMC_CAP_ERASE, some other change between 2.6.35 and 3.0 makes ERASE get used in situations it didn't get used in previously.
You need two things: buggy firmware (so far, nearly every Note and Exynos-based GS2 has this) and a kernel that will fire ERASE commands at the chip when wiping.
If a method can be found to update the flash chip's firmware, then XXLPY and ZSLPF will become safe when running on fixed chips.

Hey entropy is it possible to use the cm9 kernel with lpy? I'm assuming it is but don't want to take any risks

Somebody please shed light on this ?
- Is it possible that affected kernels inflict damage every time you perform factory reset or wipe data from recovery but it does not brick your phone.
But in future it might get bricked even on safe kernel just because you had used affected kernels ??
**** I had used recovery on LPY many times.

[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

How to install CM9 -- brick proof -- guaranteed :)

Galaxy Note N7000.
Was running stock ICS-ROM Samsung.
Always wanted to install and use a custom ROM but was always afraid of BRICKS..
But yesterday ended up being sucessfully running CM9.
Steps I undertook were as follows:
1. Installed Samsung Kies.
2. Check for update from Samsung Kies and updated Kies.
3. Connected my phone to Kies and checked if Kies detected the phone properly.
After sucess, exit Kies.
4. Downloaded PC Odin from this link
http://forum.xda-developers.com/attachment.php?attachmentid=815370&stc=1&d=1323799721
password:samfirmware.com
5. Download pre rooted GingerBread ROM
SGN_XX_OXA_KJ1_FACTORYFS.zip (thx dr.ketan)
http://d-h.st/HJM
6. Run PC odin
7. Reboot Note in download mode
vol. down+home+power buttons
8. Connect Download mode note to PC
9. PC odin ID:COM turns yellow:
(ALL THE BEST NOW)
10. In PC ODIN
Auto Reboot and F.Reset Time ---> Ticked
Others --> Unticked
10. Click PDA and select the SGN_XX_OXA_KJ1_FACTORYFS.zip you had downloaded.
Click start.
Wait for 10minutes.
Your phone will restart.
11. WOW..!!! now ur on a GB Rom
And its a safe kernel
Now you can play around
Plus already rooted
12. Now to get this GB Rom working
go to recovery mode (vol up + home + power)
clean dalvik cache and wipe data and factory reset
13. Time to install CM9
14. Download
CM9 latest nightly:
http://get.cm/?device=n7000
Googleapps:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
15. Copy these 2 files in the internal SD card anywhere (do not rename)
16. Reboot into recovery mode:
vol up + home + power
17. Flash the 2 files from where you saved them:
"install zip from sd card" option in recovery mode
now flash cm9 file
then flash gapps file
18. DO A DATA WIPE / FACTORY RESET
19. Reboot
And wow..
Enter the world of custom ROMS
[[[to switch to another ROM, follow steps 1 to 17, and after that flash the ROM of your choice]]]

Steps 6 and 9
it shud be PC Odin Not Mobile

sorry dr. ketan
my mistake
corrected
thanks

So...
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.

dr.ketan said:
Steps 6 and 9
it shud be PC Odin Not Mobile
Click to expand...
Click to collapse
Noticed that u are very experienced contributor, so mybe u can answer on my question, does the step by step guide is safe for galaxt note with brickbug? I realy want to flash, but i want to do it if i am on the safe side

Latvianization said:
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.
Click to expand...
Click to collapse
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!

SirRhor said:
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!
Click to expand...
Click to collapse
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?

Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.

I installed rom before 2 days and had similar doubts.
Just want to share what problem I faced :
The mobile should be in ON state when rooting CF I was doing it in OFF download mode

Latvianization said:
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?
Click to expand...
Click to collapse
CyanogenMod 9 is based on ICS, CM7 is based on Gingerbread. There wasn't a CM8 because Google never released the source code for Honeycomb.
And what you need is a safe kernel, because the kernel is what sends a erase command to a chip inside the phone and that's when you brick it (I think). That happens when you do a factory reset.
Now, what I always do when I want to change ROMS is to use AbbysNote 4.2 as a safe GB kernel so I can then flash the ROM/Kernel of my choice.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1362424&highlight=abyssnote
So let's say you want to go from CM9 to LiquidSmooth (or pretty much any other), which is the one I use now:
You go to CWM recovery, from there you flash AbyssNote.
Once the flashing is completed, you DO NOT exit CWM, instead you go to "Advanced" and then "Reboot to Recovery" so the phone will restart but it will go directly to CWM again, but now with AbyssNote installed.
AbyssNote has a TOUCH based recovery, so it is easier to use. Don't use the physical power and volume buttons to navigate.
From there you can safely do a factory reset, format cache, format Dalvik, flash a new ROM and Kernel.
AbyssNote will then disappear because it will be overwritten by the new Kernel of your choice. So every time I want to change to a new ROM, I repeat the steps above I haven't had any problems whatsoever.
I hope I'm right with my technicalities, but the procedures the OP and I describe are safe to try as long you follow the exact instructions, so before you try anything, read and re-read and you will be just fine.
---------- Post added at 12:38 PM ---------- Previous post was at 12:34 PM ----------
tribalkg said:
Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.
Click to expand...
Click to collapse
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360

Thanks for the useful information and for putting to rest some of my safety concerns.
Now you've wetted my appetite and I have to give it a go soon.
Sent from my GT-N7000 using xda premium

Thanks for this great guide! I haven't gotten my Note yet as I just ordered it yesterday but I have been lurking around the forums already and trying to understand how flashing roms and kernels works around here. Like someone already said before some of the guides / threads are 'a little' confusing for newcomers. I was really confused with the brick bug that people were writing about. This thread clarified things a lot for me and I believe it will help many more Note-newbies!
So, new Note community member reporting to duty here! :highfive: It's gonna be pretty neat upgrade considering from what phone I come from. Well, the Huawei at least was great step stone to android world gotta admit. I just got somewhat bored with the not so great custom scene.

SirRhor said:
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!

tribalkg said:
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!
Click to expand...
Click to collapse
Dont worry about AbyssNote, is safe in both respects. That's the one I always use to do anything that is flashing related.
If, for some reason, you start seeing that dreaded triangle at boot, you can use TriangleAway from Chainfire on Google Play.
Sent from a GNote, hell yeah!

Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.

tribalkg said:
Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.
Click to expand...
Click to collapse
Dont worry, I'm glad I can help you.
You can try Marker and Jotter as well, they work well.
Sent from a GNote, hell yeah!

thanks
thanks for the guide.

I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2

maddog2727 said:
I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
If you are on GB already, you just have to root the ROM and flash CWM because the brick bug is present only on ICS kernels. 99% sure.
There are some GB Stock ROMs that you cannot root directly, so it depends.
OTA updates from Samsung to ICS I'm not sure, you should ask someone else. When I got my Note it already had ICS, so I never did an OTA update. I don't use Kies at all.
I was very weary at first too, but with the instructions above you will be fine.
Sent from a GNote, hell yeah!

I've followed the guide from OP and now I'm rockin' CM9! No problems at all.
My content on the internal memory was intact (apps data, games data, etc), it's all there and I've flashed Indian ROM and then CM9. Have I made a mistake or what?

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.