Database Develop

Doubts, afraid and don't know how to do it safely

Ok, i know this must be here somewhere but i just can't find it. Too much time digging i guess....
I'm tired of waiting for samsung to release a solution and want to try something else.
Currently i'm on ics with lpy (german stock) so i have the famous problem (already checked). Here's the doubt: if i go back to gb with pc odin won't i have a chance to brick my device ?? I'm talking to dload an official gb rom (from dr ketan's thread) and do it as it's supposed to be done.
If i brick it will it be "the one"??
Second doubt: what rom can i flash safely?? I read a lot of threads with a lot of kernels and so far the only ones mentioned to be safe are cm9 and franko...... So basicly i need a rom with one of those??
So i can just do it like this: flash gb with pc odin, dload rom (and kernel) from what i like?? After i tried it out and don't like it and with a supposed safe kernel i can alway flash a new rom ?? No possibilty to superbrick it??
What is currently the best combination regarding battery and performance since they all claim the same............?????
Another (stupid) question: every time i flash an unofficial rom it will increase the counter or with the newer ones this is annulled? I know with a jtag i can clear them.
So basicly i'm confused and afraid to play around with this device. I have flashed other android devices in the past and did a bit of reading, the only thing that still is unclear is the possibility of superbrick........
Thanks for the help,
becosemsaida

Speedmod and Dafuq kernels are safe as well. Basically you are good to go with the knowledge you have.
Flash an older GB rom with PC Odin without the hardbrick risk, root it and flash a CWM kernel and then flash a rom based on CM9 or any safe kernel, just stay clear of roms based on official Samsung roms unless you replace the kernel with a safe one and never wipe data, cache or Dalvik on an official ICS rom.
I've been using the official AOKP rom, build 39 at the moment. It's fast, smooth, great battery life and excellent customization, based on the CM9 kernel so it's safe from the superbrick.
If you use a safe rom you can use CWM to wipe and flash other roms without the risk of superbricking.

same as above, flashed rootable GB then rooted using cfroot... and waiting for samsung to release the fix

I had the same problem I was afraid to be on the official ICS and last week I had solved like previous members said.
- First I flashed GB rom (I preferred KKA because it is directly rootable which dr.ketan mentioned it on his root guide)
- Then I rooted it with zergrush (see dr.ketan's root guide) it is the easiest way to root the device without yellow triangle
- After that I have flashed Paranoid Android ICS rom which is based on CM9 and is totally safe against the superbrick bug. It is also really exciting to use my Galaxy Note on the tablet mode with this rom I can recommend it to you.
Anyway if you really dont want to use any of the custom roms you can also flash ICS but not with its original kernel because it is totally risky.
you can use Mobile Odin and before flashing you can select an ICS stock rom but you have to change the kernel with speedmod or franco kernel. then with this combination you can flash and wipe your data after flash completes.
most of the people says that the bug is in the official ICS kernels and it triggers the emmc bug which superbricks the device. So with the other custom kernels you should be safe.
As final words I still would say that the safest way is to flash a custom ICS rom which is not based on official ICS roms. For example Paranoid is a CM9 based rom and is totally safe.
So decision is yours dude

[Q] Galaxy Note GT N7000 eMMC Bug/Kernel Related Question

Hi, I have an international varient of the Galaxy Note GT N7000 which using Chainfire's Got Brick App v1.1 says:
eMMC Chip
Type: VYL00M
Revision: 0x19
Verdict: Danger! This eMMC chip is "Known" to have the brick bug!
I once had installed a custom Kingdroid ROM v3 and wiped it but it had resulted in a Hardbrick/Superbrick so i had to take it Samsung Service Center to get it fixed. They have repaired it and given me back the handset with the Stock ICS ROM. Here are the details:
Model Number: GT-N7000
Android Version: 4.0.3
Baseband Version: N7000XXLPT
Kernel Version: 3.0.15-N7000JPLPD-CL643396
[email protected]#3
SMP PREEMPT Thu May 31...
Build Number: IM74K.JPLPD
Now i have done some researched and found that this bug is only triggered with kernels (ICS stock & leaked) which have the eMMC_Erase function/command. GB kernels are not known to have this erase function so they are safe.. Also the two safe kernels are franco r3 and speedmod k3 (Correct me if im wrong). Can anyone please guide me on the following:
1) Should I flash Stock Gingerbread OR ICS Kernel(franco/speedmod)?
2) Should I use Recover or ODIN?
3) Plz Provide the links for the Kernels - Franco R3 & Speedmod K3 which are safe?
4) Will the above Kernels provide root access?
5) Is abyss kernel safe (because it supports GPU overclock)?
6) Can i flash an ICS kernel over a Gingerbread ROM?
For answering please answer in a similar numbered way so that it is easy to read and understand for me as well as future audience! Thanking everyone who takes time to read and answer!

I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
You Flash it in Odin, It will give you CWM and Root too !
Ive attached the kernel to the post for you.
Abyss kernel is safe, But its for GB ROMs only, You are on ICS so it wont work.
I dont know if you can flash ICS kernel over GB ROM, However, Your are on ICS so you shouldnt need to worry about that.

don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.

azzledazzle said:
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
Click to expand...
Click to collapse
Thanks for the confirmation mate, one more thing to ask you: Is the speedmod kernel faster than the stock ICS kernel? Is there any flaws such as battery drain/WIFI problem with it? Also does it support GPU OC? Thanks once again for your help!
little-vince said:
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
Click to expand...
Click to collapse
Firstly get your Galaxy Note checked using Chainfires App (Gotbrick v1.1). If the verdict says "Danger" only then does your device have this problem. My Galaxy Note (Rev 0x19) had this problem and came with GB out of the box and i upgraded it to ICS through Samsung Kies and it worked fine. So i do not think that while updating to ICS via Kies will cause this problem. As of what i know it is triggered when a command eMMC errase is triggered when either doing a factory reset or wipe through recovery. The update as such did not brick my device, however this does not mean it cannot brick yours. I am no expert on this so be a little cautious while updating. I would suggest stick to GB until Samsung Releases a safe stock ICS ROM with a safe Kernel. Cheers!

really easy
1: (optional ) in GB do factory reset (after you have made a backup with TB)
2: put phone in Download mode.
3: use PC odin flash STOCK ICS rom
4: reboot device let it load
5: put device back into download mode
6: use PC ODIN flash Speedmod k3-3
7: reboot
8: launch CWM and tell it to reboot in cwm recovery
9: load your custom rom of your choice
i HIGHLY recommend doing ONLY THE FACTORY RESET WIPE data and cache in GB before you start anything.
ONCE you are in ICS and have successfully loaded speedmod or franco's kernel then it is safe to do a factory wipe if you want. but ONLY after one of those 2 Kernels are on your device.
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .

rp4k said:
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
Click to expand...
Click to collapse
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?

little-vince said:
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
Click to expand...
Click to collapse
Yes, this bug is known to trigger usually when you do a wipe using the recovery. However there have been some cases when doing a factory reset via the settings has also resulted in a brick. However if you stay away from recovery and do not intend to doing flashing/wipes then i guess you should be ok. And it is a matter of time before Samsung Comes up with a solution. They are said to be working on this bug already. I have the N7000 which i bricked once while flashing and then wiping but i got it repaired since i had warranty. Since then i have stayed away from wiping or installing any custom roms so the device has not given any problems. Hope this info helps! Cheers!

Rom doesnt load during boot
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it

cuteglen said:
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
Click to expand...
Click to collapse
What rom are you on? Have you performed any wipes or factory resets?
Sent from my GT-N7000 using xda premium

Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance

iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium

I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.

SpyderTracks said:
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again

iraqi4ever80 said:
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
Click to expand...
Click to collapse
Only from GB kernel such as abyss. If you flash from ics kernel you WILL brick. This goes for all cm based roms.
Sent from my GT-N7000 using xda premium

kyllerbuzcut said:
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
Click to expand...
Click to collapse
Hiya, yep, you can just delete the zimage file, no need to replace, it will just skip writing that partition.
Sent from my GT-N7000 using xda premium

Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?

kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Try mobile odin. If you point to the tar, it should load all the components. You can then review which components are being flashed.
Sent from my GT-N7000 using xda premium

iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Add goku, dafuq, gl-notecore and abyss42 (GB) to your list.
2. Only do it from a GB firmware or at least a GB kernel like abyss42. SPECIFIC instructions per firmware is listed for a reason. Follow those instructions to the letter.
3. No.
Sent from my GT-N7000 using xda app-developers app

kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Stock rom in a zip? Are you sure you are nit flashing a custom rom? Point us to the file/thread please.
If it is a custom rom, the it is meant to be via CWM.
1. Flash abyss42
2. Reboot recovery
3. Do your wipes
4. Flash.
Im sure there is a specific instruction on where you got that file. Or better yet, go to dr. Ketans thread and get your stock rom from there.
Sent from my GT-N7000 using xda app-developers app

It's just the standard rom file from sammobile.It does come as a zip you know. If you unzip it, then use rar on it you can see all the bits. I thought if I just put a different zimage in there it would just go ahead and use that, but didn't seem to like it after I zipped it all back up again.
Tonight I've ended up getting chainfires excellent CF-Root kernel.Flashed that through odin, over my speedmod kernel.
Put just the factoryfs part of the stock rom zip onto the SD card and flashed that using the cwm app that CF-Root installs for you.. Now have CF-Root kernel and 4.0.4 firmware.
If you don't already have a "safe" kernel then I dunno what the brick chances would be, but since I had a safe one already I thought it couldn't hurt to try it out.
The reason I haven't flashed the hidden, cache, model and sbl parts of the zip is that simply they wouldn't fit on my SD card If it behaves funny or I can make space then I'll try the rest too. And the reason I didn't flash the zimage from the zip should be fairly obvious. Because I don't want a brick
EDIT: I managed to clear some space on the SD and flashed the rest of it. Seems to be working ok, so far anyway. I'm hoping the battery issues from 4.0.3 will be a little better. This is a really good way of doing it all as you can just swap out a potentially bad kernel for one that has been 'protected' by having te emmc cap erase turned off.

Safely go from Official stock Gingerbread to Official Samsung ICS ?

Ok, I hate to be a noob, but I feel that I have to in this case.
I just got a new unlocked G-Note and it has has gingerbread. However I want to install ICS, Been trying to research through the threads myself, but its overwhelming for someone who hasn't been here to follow the threads from the beginning
I would appreciate some advice or steps to safely go from bone stock G-note to Official Samsung ICS
Current "About phone" Info:
Model number
GT-N7000
Android Version
2.3.6
Baseband Version
N7000XXLB2
Kernel Version
2.6.35.7-N7000XXLC1-CL-CL1003701
[email protected] #2
Build number
GINGERBREAD.XXLC1
PDA: N7000XXLC1
PHONE: N7000XXLB2
CSC: N7000OXXLB3
The guilds quickly get confusing, I have done a great deal of flashing device over the years, but have never been this lost.
Help/warnings are welcome

Hey man! Seems like you want to upgrade from GB to ICS on the Galaxy Note. GB is far more stable and bug free on the Galaxy Note. This is one device where upgrading to ICS is more of a downgrade. So to be honest i would recommend that you stay on GB until samsung get out a stable ICS ROM for the Note.
Firstly what i would recommend you to do is download chinfires app called Gotbrick.(Google it) Install the app on your Note on GB and see the verdict. The verdict will tell u if your Note has the eMMC brickbug. If the verdict tells "Danger" then upgrading to ICS is equal to suicide because all stock ICS kernels are known to have the eMMC_Erase functionality which will cause this bug to superbrick your phone.
However if you still want to take the rist then the steps to upgrade are: you can try the connecting your phone to your PC and run kies. It will automaticly check for updates and install them. Another method is using the phone itself. Goto Settings>About Phone>Software Update and check for updates. It should update to ICS automatically.
If none of the above work then use the ODIN method:
For the ODIN method the steps are:
1- Register and Download the Stock ICS for your region from here:http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-N7000&r=-1#modelsa
2-After download you should get a zip file. Unzip the content. You will get a .tar.md5 file.
3- Next get ODIN v1.83 (download it if u dont have it)
4- Make sure you have Samsung Drivers Installed on your PC and put your phone in download mode(Volume Down + Home + Power) and connect it to your PC using USB Cable
4- Then run ODIN as admin and then click the PDA button and choose the .md5 file you extracted. Make sure only Auto Reboot and F.Reset Time are checked in ODIN. Then click the start button and Let it flash the new Firmware.
After flash complete you should have Stock ICS 4.0.3 on your Note. What i would recommend is to flash a safe ICS kernel like Speedmod N7000 k3 on it to prevent it from getting bricked.
If this helped please click the Thanks button! Cheers!

Sorry to be a noob,
but i couldn't get a download link for the *chinfire's app Gotbrick* to check whether my SGN is not from *DANGER* to Stock ics update. =(

Looks like it's "Chainfire"
http://forum.xda-developers.com/showthread.php?t=1693704

OK, here's my experience with upgrading to ICS. I've had my note for about 2 months and have been following the forum trying to learn. It's very confusing to me and I was afraid to do anything so I did nothing. I live in Melbourne, FL and use Straight Talk. My note was purchased from Newegg and had a Brazil build number. Several days ago someone posted that Brazil was now on the "update to ICS" list, so I thought I'd check it out with kies. I use linux so I had to boot into my Windows 7 Ultimate OS(ugh). I opened kies and it said it could be updated to newer version, so I updated kies. Then I pluged in my note and low and behold it said update version available! I sweated a little and decided to go for it. It updated smooth as silk with no problems and now I have ICS! I have all the apps with all the data I had before update.
The new ICS is much quicker and smoother than GB, the difference is immediately noticable.
All the phone info changed to new numbers(android, baseband, kernel version and build number) and I didn't think to write it down so I can't post what it was. Anyway hope this info helps someone.

I agree that the update makes the UI quicker but however it makes the brick bug effective in the ICS kernel. With GB although the UI is slower, there is no risk of brick bug.
So its ur choice to choose between a relatively slower UI with no brick bug Or a faster UI but risking your phone. I recommend installing a custom GB rom which is stable and fast.
Sent from my GT-N7000 using xda premium

Hey, so I got really excited when ics came out and instanly went out to flash the repack (stupid, I know) and I checked and I do have the brickbug. So I know that I shouldn't flash using clockwork or do a factory reset and I wanna take your advice and flash a safe kernel like Abyss.
So I just wanna know if I should just flash it through clockwork and then I'll be ok right? My phone's performance and everything wouldn't be affected right? Also would prefer rather not downgrading to GB.
Thanks!

So yea, I do have the bug, but before I found out, I flashed ICS. Panic when I found out I could brick my phone, then flashed back
Question: Even though I have the bug, if I flash Stock Indian ICS, then Speedmod, will I be safe?

Daman1997 said:
Hey, so I got really excited when ics came out and instanly went out to flash the repack (stupid, I know) and I checked and I do have the brickbug. So I know that I shouldn't flash using clockwork or do a factory reset and I wanna take your advice and flash a safe kernel like Abyss.
So I just wanna know if I should just flash it through clockwork and then I'll be ok right? My phone's performance and everything wouldn't be affected right? Also would prefer rather not downgrading to GB.
Thanks!
Click to expand...
Click to collapse
Ok firstly i would like to say that if you do have the bug and are already on ICS then instead of downgrading to Gingerbread, try to flash a safe kernel. But stay away from Clockworkmod. Do not flash using CWM. Instead use ODIN to flash any kernel from the following:
Speedmod kernel
Franco Kernel
CM9 Knightlies
The best of these kernel is Speedmod kernel which has the best performance and best battery life. I have already made a tutorial on how to do this, just follow the steps on the tutorial found here: http://www.youtube.com/watch?v=o5K5Wm_201Y
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
DJTJ said:
So yea, I do have the bug, but before I found out, I flashed ICS. Panic when I found out I could brick my phone, then flashed back
Question: Even though I have the bug, if I flash Stock Indian ICS, then Speedmod, will I be safe?
Click to expand...
Click to collapse
Before you flash anything tell me what are you running currently? are you running a stock ICS or a Custom ROM? If you are running stock ICS then you can easily flash Speedmod kernel with ODIN and you will be safe. You can see my tutorial here: http://www.youtube.com/watch?v=o5K5Wm_201Y

endingcolt007 said:
Ok firstly i would like to say that if you do have the bug and are already on ICS then instead of downgrading to Gingerbread, try to flash a safe kernel. But stay away from Clockworkmod. Do not flash using CWM. Instead use ODIN to flash any kernel from the following:
Speedmod kernel
Franco Kernel
CM9 Knightlies
The best of these kernel is Speedmod kernel which has the best performance and best battery life. I have already made a tutorial on how to do this, just follow the steps on the tutorial found here:
Click to expand...
Click to collapse
Ok, really appreciate the advice will try the speedmod kernel through ODIN, but I also have mobile ODIN installed, but I shouldn't use that then I assume. Thanks again!

Currently on a leaked LPY ICS and I have the dangerous kernel. I'm suffering from poor battery life at the moment.
What do you suggest I do? Should I go back to GB or give a new kernel a try?
If I flash a new kernel over LPY will it be safe to perform a factory reset?

Putting ICS on My N7000

I just purchased a international Note off EBay. It has GB installed. I am not sure what country this is from but the phone's baseband version is N7000UBKK1 and the kernel version is 2.6.35.7-N7000UBKK2-CL705203. I would like to move to ICS. I need US English as the language. So:
(a) What firmware should I use? I want to use Odin to install.
(b) Is there any possibility of bricking my phone due to the eMMC issue? I have run the eMMC Check app from the Play Store and it says the chip is "insane". But the test of the memory completes without errors. I am not really sure I know what this all means but I want to avoid problems (who doesn't).
(c) I understand the brick problem is with ICS and not GB. Does this continue to be a problem with the various JB roms out there?
Thanks for your time and help.

Flash stock open German XXLRQ then, look for it in dr.ketan's thread for stock roms in note original android dev sticy.
There are no official jb roms for note yet and cm10 or aokp based custom jb roms are totally safe for wipes and all.
Sent from my GT-N7000

For people who just Dont know what version they need to install u can check this from settings -about,or simply just install kies and it will detect ur version,then u can let kies install it for u or u can download it from dr.ketan post then root it then flash any safe kernel as speedmod ir hydracore,one last thing just remember not 2 make any wipes while using stock ICS thats all.
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗

The brick bug only triggers on unsafe kernels like stock ICS and only if you do wipes like factory resets.
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2

So Should I NOT Use a Stock ICS ROM?
Markuzy said:
The brick bug only triggers on unsafe kernels like stock ICS and only if you do wipes like factory resets.
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Hello and thanks to you and the others who have so kindly replied. Does this mean I should find a non-stock ICS ROM to install? I was thinking that going stock would be safer. I was reading this guide <android.gs/update-samsung-galaxy-note-to-official-xxlrq-firmware-update> to updating to the ROM suggested above and near the end it speaks to possibly having to select ‘wipe data/ factory reset’ in recovery mode if, after the Odin install completes, the device fails to boot beyond the logo screen. I would not want to get to that point and not be able to do this if needed.
Also, I would eventually really like to get to JB - especially for the on-device voice command processing. If there is a recommended JB ROM that can do this now and avoid the brick problem, I would appreciate recommendations.
Thanks again for your knowledge and help.

whitedavidp said:
Hello and thanks to you and the others who have so kindly replied. Does this mean I should find a non-stock ICS ROM to install? I was thinking that going stock would be safer. I was reading this guide <android.gs/update-samsung-galaxy-note-to-official-xxlrq-firmware-update> to updating to the ROM suggested above and near the end it speaks to possibly having to select ‘wipe data/ factory reset’ in recovery mode if, after the Odin install completes, the device fails to boot beyond the logo screen. I would not want to get to that point and not be able to do this if needed.
Also, I would eventually really like to get to JB - especially for the on-device voice command processing. If there is a recommended JB ROM that can do this now and avoid the brick problem, I would appreciate recommendations.
Thanks again for your knowledge and help.
Click to expand...
Click to collapse
ofc you can use ICS Stock Rom. But just to be safe you have to flash safe kernel...Speedmod/Notecore/HydraCore are the safer kernels.
For JB there is no official update available from Samsung for our Note. But you can enjoy it with the efforts that developers are doing for us in XDA.
Go to Android Development Section and Have a look on the Topic Titles.Some of them are AOKP/PA/CM10/AOSP... For Me JellyCore is so far gud. You can find the link in my signatures.

I only know u r now in GB.
GB shld be ok to do full wipe. None reporting mmc brick on GB coz of full wipe.
So....
U can do ur full wipe first on stock GB.
Use pc odin to flash ICS 4.04 LRQ.
Voila.... U r on ICS alrd.
Once u r on ics, and on stock ics kernel....
Pls, do not ever do full wipe.
Unless, after that u root and install ics safe custom kernel, then u r safe to full wipe on ics.
Good luck!
Sent from my GT-N7000 at the corner of this rounded earth.

More in Jelly Core?
sahilarora2003 said:
ofc you can use ICS Stock Rom. But just to be safe you have to flash safe kernel...Speedmod/Notecore/HydraCore are the safer kernels.
For JB there is no official update available from Samsung for our Note. But you can enjoy it with the efforts that developers are doing for us in XDA.
Go to Android Development Section and Have a look on the Topic Titles.Some of them are AOKP/PA/CM10/AOSP... For Me JellyCore is so far gud. You can find the link in my signatures.
Click to expand...
Click to collapse
Hello and thanks. I guess it may make sense to bypass the stock ICS which seems to contain issues related to the brick bug and go to something like Jelly Core as you mention. I looked at the page for Jelly Core and see that it says to install using Clock Work Mod and to wipe from a safe kernel first. As a newbie I guess I have some questions:
(a) I am on GB which I understand to be "safe". Is that correct?
(b) Where do I get the CWM for this phone and how do I install it?
(c) To do the "wipe" does that simply mean to use the built-in reset to factory or does this mean something else?
Thanks

Hi there,
a. Yes, Stock GB's are generally safe
b. When your going to flash ROM, each ROM has it's own accompanying CWM.. so when your done choosing which ROM your going to flash your Note to, when your going to bootup in recovery.. and you get the standard CWMR...
c. Yes, Wiping is synonymous to doing the built-in factory reset on your phone (thru Settings), or the alternate way is to go to CWMR and wipe data. Different Methods, same result.

Thanks but...
letters_to_cleo said:
Hi there,
a. Yes, Stock GB's are generally safe
b. When your going to flash ROM, each ROM has it's own accompanying CWM.. so when your done choosing which ROM your going to flash your Note to, when your going to bootup in recovery.. and you get the standard CWMR...
c. Yes, Wiping is synonymous to doing the built-in factory reset on your phone (thru Settings), or the alternate way is to go to CWMR and wipe data. Different Methods, same result.
Click to expand...
Click to collapse
I am sorry but I am still a bit lost here. Before my N7000 I had a Samsung Skyrocket and flashed it using Odin from the GB that was on it to the stock ICS. I found several guides for this online and it worked fine and easily (although I still feared the brickbug). But this is basically all I know about this stuff.
So how do I flash something like Jelly Core? It sounds like I have to install some other was other than I did with Odin/stock ICS on my Skyrocket. Perhaps I need more of a tutorial on how to do this flashing of custom roms. Any suggestions?
I apologize to all for my thick-headedness.

the best and safest way first is to downgrade back to stock GB. Don't do any thing foolish by just flashing a stock ICS (with an unsafe kernel).
Downgrade first to stock GB and work your way up to eventually flash your preferred custom ROM (in cwmr or odin)

(Solved), Questions about Kernel, Camera and Mobile Odin

Hi. I'm an advanced Noob. I'm special . Just kidding. My Galaxy note is on stock ICS 4.04. The firmware is N7000XXLRK. I'm using the PhilZ kernel.
Question Number 1)
a) Kernel
If I would be on a Cyanogen, PA, TW based Rom and flash with MobileOdin the Stock ICS (XXLRK) is that safe? Or do I have to use a special kernel? I fear the brickbug.
b) Camera
My Galaxy Note has the ExynosAbuse installed. I clicked on root. After I wanted to take a picture with flash my phone suddenly turned of. There wasn't any reaction. Recovery and Download didn't worked. So I had to plug it in to my charger and it boots. This happened also when I clicked in on OneTimeFix for non-root-user. Is this normal? I already read about that this fix may brick my camera, but I thought it would be black (screen but still can see the shortcuts)
c) MobileOdin
Is MobileOdin able to flash a complete firmware?
Is a downgrade from 4.0.4 to 2.3.6 possible. (I come from Apple. My i**** needs SHSH which are certificates to downgrade.)
By the way... xxxda-developers.com for the win!
Send from my Galaxy Note.

1. Kernel is rom specific, or group-of-roms specific. You cannot use stock ( stock as in "Samsung" ) kernel with any AOSP based rom like Cyanogenmod etc. You also cannot use CM kernels with TW based roms. If you're going to flash Cyanogenmod then stick with the kernel they provide. CM team puts a lot of work to make it work on the kernel they provide so replacing it often causes more problems than it's worth. The brickbug is almost exclusive to Samsung kernels, as in "stock" ones. If you're using CM, you're safe. If you're using anything stock - you have to make sure, and since Samsung's newest 4.1.2 firmware still has it - i think it's safe to say they're NOT going to fix it.
2. Camera may break differently for many people, it's not always black or green screen. For now it's probably best to avoid using ExynosAbuse, root with traditional methods and be careful what you install on your device.
3. Yes, MobileOdin can flash a complete firmware.
4. Yes, in Android any downgrade is possible, you don't need any certificates. Just download the firmware you want, enter Download mode on your device, point PC Odin to your file in PDA section and hit start.

just to add some more
1: when using mobile odin make sure you on a safe kernel. though the newer versions of MO seems to flash CF kernel (its own) and then flash the firmware. so its ok
2: may be try a different battery now
3: Stock firmwares in tar.md5 format
4: always. nothing much to add