Database Develop

Anyone else paranoid about flashing ics?

With so many horror stories being posted, I don't know what to believe. When will it be relatively safe for us to update to ics?
I came from an HD2, and that was a treasure for flashing different roms. But it seems like the note is so easy to brick.
Edit: All I've done so far is root my note using Dr. Ketan's method.

It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.

I've flashed dozends of ROMs on my old HTC desire including ICS. At the end it worked always fine.
1. Backup
2. Wait after flashing - some roms need their time. After 10 min I've sometimes put out the battery to restart...
3. Enjoy
So don't fear!

I'm waiting for ICS OTA also. There have been lots of mixed reports with the previously leaked ICS ROMS - some bricked and some not. I've had a great run with flashing GB ROMs and Kernels but will wait for more official versions.
BTW - A colleague has a Note about four weeks old bought via the web. It turned out to be a German handset and he was successfully able to flash via KIES. I'm jealous - my Note 6 months old and I am still waiting for official ICS !

If you dont have any crazy combination of rom with custom kernel and cwm then is fine
Just dont wipe before flashing
And wipe after flashing
Sent from my iPad using Tapatalk

The fact that we have had ANY bricks at all suggests to me that this is not safe to flash, and even though I have been able to successfully flash LPY and run it, (not without problems), the bit that concerns me is the bricking due to large file copying which has been mentioned by various people.
Since I regularly copy large files to and from the device, I do not plan to subject my device to testing the theory.

I flashed ics yesterday and everything went fine, Iam always paranoid when comes to flashing but research before actual flash is vital! SEARCH button overheats and Iam ALWAYS following instructions!
Dont know what would I do without xda and those so capaple devs!
Galaxy Note!!!

I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.

nandihno said:
Just dont wipe before flashing
And wipe after flashing
Click to expand...
Click to collapse
Why is it safe to wipe after flashing and not before? I thought it was the other way around?

neos_83 said:
Why is it safe to wipe after flashing and not before? I thought it was the other way around?
Click to expand...
Click to collapse
It is the other way around.
Anyway, I fear this might be another superbrick in the making...
http://forum.xda-developers.com/showthread.php?t=1653290
And another one...
http://forum.xda-developers.com/showthread.php?t=1649982

vetchems said:
I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.
Click to expand...
Click to collapse
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.

to answer the original question... no... because i thoroughly read as much as i can find before i flash anything...even google it to see if there are problems ... hence i have ics rumming and running without any strange issues...

tbong777 said:
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.
Click to expand...
Click to collapse
I decided I did not want to "tip toe" around my normal processes with this device and went ahead and flashed CF Root with CWM. Going to need CWM to flash Roms and the LPY kernel has nt proven to be all that safe either. There is at least one case of a Superbrick wiping from Stock Recovery.
I bought these devices to mess with. I have a back up S2 and the s3 is out....Worst that can happen is I sell for parts.

well i am lucky so far as i dint have any issue with my note even after flashing lpy somany times from cwm may b me lucky till now

I'm terrified of flashing any roms on now after all the horror stories. I honestly don't even really care if I have ICS. I just hate how slow the stock ROM is. I would be very very happy with CM7 with SPen functionality.
This kind of sucks coming from an LG G2X which had so many stable roms and kernals to choose from
I thought a Samsung phone would have had even more but I guess not.

Probably like everyone else, I read Entropy's thread and became SUPER paranoid. He said there's no way to tell if you're slowly degrading the emmc or not unless you're on a 100% safe kernel / rom. I'm confused about the rest of the details. Apparently cm9 is 100% safe, but even the official ics can brick our note if we still have reminants of a leaked ics rom / kernel?
People alot more knowledgable than me have been bricking their note, so I will wait for an idiot proof method.

I would luv to see a step by step guide on video.
Also still dont grasp the fact that even if we put an official ics from Germany will won't get upgrades.
Sent from my GT-N7000 using XDA

I've been using lpy since release, and although I've had no problems so far, don't have cwm just root, but the more posts IM reading about people experiencing bricks from many different methods is definitively scaring me.
Chasmodo is a very reputable developer as is Entropy. I heed their words and will flash back to GB today, it's just not worth the risk.
Sent from my GT-N7000 using xda premium

Thijsvr said:
It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.
Click to expand...
Click to collapse
I also initially thought it was all speculation and anecdotal evidence. However, it appears that at least one user who has upgraded a brand new Note via Kies to LPY and wiped immediately thereafter has bricked his device.
That being said, I updated via PC Odin, rooted with temp CWM and full wiped from stock recovery thereafter without any issues (so far, been 3-4 days now). The performance improvements that ICS brings are significant, IMHO.
Basically, update if you really want to and refrain from wiping if possible (i.e. if you are not facing any FCs etc).

[Q] EMMC bug - Is it safe to factory reset ICS on LPQ UK rom?

I have heard a lot of talk about an emmc bug affecting stock Ice Cream Sandwich builds realeased by Samsung. THe general consensus seems to be that it is not safe to wipe/factory reset the stock Samsung ICS roms.
The question I have is do we know if the recent UK region ICS update (XXXLQ2) is affected by the emmc bug?
Can anyone confirm that if they factory reset after upgrading to LQ2 ICS that they bricked their phone or that it was a successfull wipe?
I can confirm that i have factory reset my phone successfullu after installing LQ2 update although my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
I look forward to your replies, i know there are geniuses on this forum who can enlighten us.

We wont know if its affected until someone reports a brick.
But I would guess its still affected by the emmc bug.

As Entropy says in his PSA:
"All ICS official releases for the Samsung Galaxy Note (GT-N7000) as of late May 2012 - This includes XXLPY, ZSLPF, and DXLP9, and future kernels should be assumed affected until further notice."

So the bug is in offical releases?
SO this bug is in the official releases that you can install via kies?
Will Samsung patch this bug?
Surely they must be aware of it since the number of bricks going to the service centers must be rising astronomically. If we are aware of it how can they not be when they have tested many devices at factory?

Better hold on to gb then rushing to ics with emmc bug. Wait for awhile until some one found a solution. Or else you will stuck like me with no gb backup to revert back.
Sent from my GT-N7000 using XDA

This is a XXLQ2 Brick I Guess.

Lol thats a total facepalm. But whats the cause of his brick? I couldnt read it all cause I laughed so hard that I got tears in my eyes.

JazonX said:
This is a XXLQ2 Brick I Guess.
Click to expand...
Click to collapse
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3

chasmodo said:
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3
Click to expand...
Click to collapse
Yeah thats exactly what I thought. As I said, couldnt read it all.

Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?

I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.

Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.

Belfia said:
Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.
Click to expand...
Click to collapse
Cheers just hope i don't need to factory reset before a fix is sorted. Don't really want to go about changing roms as i like tw and like to keep my phones standard.

volvo940seturbo said:
I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.
Click to expand...
Click to collapse
Run the "GotBrickBug" app by Chainfire under the Themes/Apps section and see what firmware you have.
More than likely the LQ2 ROM still has the faulty MMC_CAP_ERASE code because Samsung hasn't admitted to the problem at all yet.

dbreloaded said:
......my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
Click to expand...
Click to collapse
I initially update by Kies to LQ2 and had random homescreen force close, black screen,green dots on the screen, apps freezing...etc. Done a factory reset, then downgraded to GB UK, factory reset again, downloaded the LQ2 Firmware via Check FUS PC version and flashed ICS LQ2 using ODIN PC and everything is running smooth. No bugs to report after more than 1 week.

rdosti said:
Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?
Click to expand...
Click to collapse
I'm afraid this is not correct! Its a bug in stock ICS kernels (or other ICS based kernels that are not specifically modified) that enable the eMMC erase command.
Some custom ICS based kernels now have this command disabled. But as for now, it is considered unsafe to flash or specifically full (data) wipe from any stock ICS ROM (some ICS ROMs do a full wipe when flashed!). It is still statistically a rare event, but the only way to be 100% sure safe is to flash from a GB based kernel, such as Abyss 4.2 kernel.
Samsung is working on a "fix" for the faulty firmware in the emmc chips but what this fix will be is unknown.
It has been reported that, unrooted, on a Stock ICS ROMS (and hence stock kernel) has super-bricked after doing a factory reset.
You may be able to do a full wipe/reset/custom ICS kernel ROM and not suffer any immediate ill effects but the bug can manifest itself at a later date.
If you really want to get the bug, the best way would be to fill up your internal memory, then do a factory wipe, rinse and repeat!
GB kernels don't use the erase command, so are totally safe.
So to summarise, it is not safe to factory reset on LQ2 UK rom! Samsung have not yet issued a fix!
EDIT: Wow, its even more complicated than above lol!
See here for updates and the first sign of a fix!
http://forum.xda-developers.com/showthread.php?t=1698977&page=14

What did I do wrong? N7000 bricked.

Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!

marcelo.ellmann said:
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
Click to expand...
Click to collapse
ALWAYS flash a GB Kernel or ROM BEFORE flashing a CUSTOM ICS ROM.

Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.

marcelo.ellmann said:
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
Click to expand...
Click to collapse
Because of an eMMC brick bug!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
The guide I followed is from here take a few moments to read and understand then you will have no troubles in rooting/flashing again!

hing98 said:
Because ICS has not been officially released on the Galaxy Notes therefore we use a GB Kernel or ROM before we flash any custom ICS ROM.
Yes it was confusing at the start but to avoid bricking you must alwaysfollow the guides given by the Developer!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
Click to expand...
Click to collapse
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium

stoney73 said:
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry was reading from another guide. Your right
---------- Post added at 01:12 PM ---------- Previous post was at 12:23 PM ----------
hing98 said:
Sorry was reading from another guide. Your right
Click to expand...
Click to collapse
Anyways its a bug that bricks your device,
you can find more information here
Cheers

I had a galaxy S where flashing process was different Wen u flash CM9 roms and if you want to get back to GB roms only way out was PC Odin and moreover you can wipe on ICS roms and install other roms. But wen i got the note the procedure was slightly different Brickin problems and moreover wen you are in ICS you can get back to GB with GB kernel only no need for PC odin. Just keep a copy of Abyss kernel 4.2 in your sd card and be sure to flash it when changing roms.....

Doesn't Franco rev3+ solve the brick bug?
Hi all,
since you're saying we have *always* to flash a GB kernel before having a factory reset, are you talking about those having the CF/Stock kernel?
I'll make it clear: as far as I know, Franco made a kernel that should avoid the brickage since its 3rd version (thread here --> http://forum.xda-developers.com/showthread.php?t=1491428). Who installed this kernel could just wipe from ICS and install any ICS ROM. Am I wrong? If so, please explain the whys.

UNBRICKED!
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

[Q] In light of the eMMC bug, is the N7000 still worth getting?

Hi All,
Just curious how serious the eMMC bug is, and whether the N7000 is still worth getting??
1) Is the bug only present in ICS Roms, with unsafe kernels?
2) Is the phone safe using any of the GB or JB Roms, assuming it is only ICS thats at fault with the chip?
3) I've heard CWM is also dangerous to use, is there a certain one/version to use? (namely, Philz?)
4) How do you prepare the phone from ROM flash? All other Android devices I use to do Factory Reset Wipe in CWM, followed by wiping System and the Cache section. What can I do now, or cant I do... for fear of bricking?
5) Is this App [GalaxSim Unlock, by spocky] ok to unlock, does it work or can it be dangerous in light of eMMC? Or should I get a carrier unlock?
6) If using this phone normally, normal Apps... Is there a risk to bricking if the App write to write to the internal storage?? (such as saving files/settings) or is only if you attempt to wipe it?
7) Whats the absolute do's and DONT's with this device, like to stay away from....
I'm really keen to buy it, but dont want to end up with a BRICK through a silly mistake....
- sorry for all the questions, just really confused by whats ok and whats not...
Thanks, Lister

Emmc brick bug was there in ICS for sure but it is not worth trying on JB as it is no fun to see if the device gets bricked or not.
You can use GB (which has safe kernel) you can do the wipes. ICS and JB there are many custom kernel which are brick bug safe, meaning that it would not brick your phone if you have these kernel (say Philz for example) which also give you CWM and you can do wipes as many times you want without the risk of getting bricked. Philz kernel is available for all the versions.
For how to flash stock rom and list of stock roms use this:
http://forum.xda-developers.com/showthread.php?t=1424997
i dont have any idea about unlock, you may wait for someone to respond to that.
when using the phone normally there is no risk of brick.
Dont wipe the device on stock recovery and you are safe, to be safer always use Philz kernel. if you want to claim warranty at any time you can always flash stock rom again.

Own a note for 5 months now and this device is as good as any for the flashing of ROMs and kernels. So this is surely a safe buy. The PhilZ kernel is not particularly what i am fond of as it caused problems for the flashing of certain ROMs as the recovery is CWM based and not CWM recovery. And i do not have any info about the unlock app

Hi Treacherous_Hawk and Varad297,
Thank you both for your comments and suggestions, all this info I am picking up is very useful for me... As I may of said above, but have certainly said in other places across this board (and other sites). I'm fairly ok/confidant when it comes to Android, and the other Android hardware in my collection. (ZTE Blade, HP Touchpad, and MK802-II) Dont suffer from any kinda serious bug, and are brick free, they will never die... But I must admit, I am a little scared of this eMMC bug in N7000.
So thanks for putting my mind at rest....
If / When I do get this phone (through a mate of a mate), in October when her contract runs out. Will be locked to Vodafone UK, and I am T-Mobile UK, and I believe its currently running on Android 4.1.2 JB Stock.
However I want to flash the P.A.C. Rom to it straight away, as I have this on my ZTE Blade and HP Touchpad and love it...
So whats the best way to do it...??
1) Download Philz Recovery (and which version would I need, being that the rom its on is 4.1.2, and the rom I'll be taking it too is 4.2.2)
- I assume I copy this to SD Card, and flash in Stock Recovery, via going to Download Mode
2) What steps would I follow to clear of current rom? What wipes are safe, or are they all safe with Philz? Normally I do Factory Data wipe, and then System and Cache...
- Are these fine under Philz recovery? As from above two comments... First reply says its safe to do so, second reply says its dangerous... Just really scared about this bug, cant believe Sammy released a device like that...
3) I assume I flash it in Philz CWM, rather than ODIN? Do I need to re-flash a kernel straight after or is the one in P.A.C. (4.2.2) safe from bug?
4) I think the ROM is pre-rooted, but what should I do in case its not? Use ODIN or is there an easier method?
I assume flashing the above rom, via the above method (Philz CWM) will then result in the Yellow Triangle, and bump the count upto 1? So do I just use Triangle Away to clear and reset this, and this is again safe of bricking???
Thanks, Lister

Dude dont panic.
P.A.C. Rom is rooted and does not trigger the emmc bug.
Safe way from stock is as follows:
1.
!DO NOT WIPE ANYTHING ON STOCK!
2.
Get philz kernel for your stock version.
there are packages for flashing with either ODIN which involves connectiong a Computer or with Stock Recovery, which does not involve a computer.
The latter, which is simpler is simply a file on SD you can flash through stock recovery (when off press power+home+volup), it wont even void your warranty.
That provides you with a CWM like recovery from which you can wipe or flash other roms WITHOUT triggering the brickbug.
3.
Get your favourite Rom and flash it through cwm recovery.
BTW: Almost everyone who releases for N7000 puts something in the description that says if the rom is bricksafe.
All newer AOSP/CM based roms should be bricksafe.
Most of the customized Touchwiz Roms are also bricksafe, but watch their thread to be sure.
hjsdfbglsmhjc8we
EDIT:
IMO if you get the Note 1 for free or cheap its well worth getting. If you plan to buy one rather look for the Note 2 because I feel that it is better supported and has better customisation diversity.
Or if I ask myself what my next phone will be... dunno. Maybe a Nexus or Xperia Z or HTC? I cant seem to find the perfectly blended device. Might go with Jolla Sailfish device if it proves usable.
EDIT 2:
I think someone should sticky this as a simple guide for this. Also the existing stickies really need a cleanup to not confuse people with too much information out of differing times.
Does XDA pay moderators? I'd happily clean stickies and test stuff all day. (I'd also assume a neutral persona/state of mind for such activity.)

Hi Illidan Pornrage,
Thank you so much for going into great detail of the steps I need to follow, I'm starting to feel more comfortable at doing and using this now... So any ROM that says they are Brick free means there is no way to trigger it?? Not that I have ever done this, maybe when I first got my Android back in 2010 just to see what it was like... If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? (not that Im likely to ever use it... just making sure).
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
I am so use to CWM on other devices, I am scared of using the wrong selection on the famous N7000 eMMC brick bug... lol
But with the other steps, thank you so much, such a HUGE HELP!!! and I am sure that will put other new (to N7000) users minds at rest...
-- So useful that ya know the above ROM too, as it makes it even easier/safer for me knowing all is gonna be ok with it...
Cant wait to get ROMing now... Just gotta wait till October... b*gger!! lol
Cheers, Lister

If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? Yes as often as you like. I flash cm nightlies, so I wipe very often.
And my window manager somehow always loses focus of the textbox. So I write half posts and have to edit 346243 times. Sorry.
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
Also yes.
As for 100%. I cant assure you that nothing obscure that only happens 1 in a million times happens. But the menchanism that triggers the great evil bug is removed from philz and the mentioned roms.

Phewwww..... so this eMMC bug is no big deal then....
Only an issue if you stay on stock firmwares really, esp that of ICS??
Well thats made me feel a whole lot safer and more determined to want to get it. Had my hopes set on getting it, and then when I heard about the eMMC bug, thought is this gonna be a wise purchase or will I be spending the best part of £150 (dont know the final price yet) on a very large and heavy paper weight!! lol
Thanks so much for putting my mind at rest, great help...

Hi Illidan Pornrage,
I've only just seen/noticed your updates to my original questions, thanks for the updates.... Re: Why am I going for just the Note 1 rather than the Note 2. Is that someone a know (mate of a mate) will be upgrading her phone (she prolly gonna go back to Apple... boooo) and so hopefully she will be parting with her Note (and cheaply I hope, esp re the bug... a-haaaa)
- and couldnt agree more about tidying up the Stickies, as yes a lot of it is out of date, hence my asking and checking... To which you fully re-assured me of the steps, so think this would be useful to all...
Just to add to this, which Philz Kernel would I need??
Phone: Galaxy Note 1 / N7000
Network: Vodafone UK
Current OS: Android 4.1.2 JB Stock
Planned OS to update Too: P.A.C. 22:30 (Android 4.2.2)
So not sure what Kernel I would need from the below link, and if so, can you explain why I need THIS one? What do I need to look for in a kernel?
http://forum.xda-developers.com/showthread.php?t=1901191
Also, can anyone confirm if they have a UK Note 1 on contract (esp Vodafone) as I am hearing the contract ones are unlocked by default. Its only PAYG that are locked down....
thanks, Lister

Hi Illidan Pornrage / Guys,
As per my above post, any idea what Kernel I need based on the above details...??
Thanks, Lister

[Q] Howto: Fresh and clean install of official 4.1.2

Hi,
I own a Galaxy Note GT-N7000.
I never rooted it, just used two official updates provided by Samsung and then flashed the original 4.1.2 using Odin.
I have rooted my older Android phones (San Francisco) and used to try all kinds of ROM's on many Windows Mobile phones - I am not a exactly a noob, I just did not mess with my Note, because I am happy with it just like it is and because it is my work phone, which needs to be 100% working.
However, battery life is getting shorter (so I just ordered a new original Samsung battery) and, worse, the phone is getting more and more unresponsive.
This is the real problem: whenever I want to do something, it takes like 1-2 seconds, if not longer, before the phone reacts. This is very annoying. I don't have that many apps installed (I just stick with my preferred ones, instead of betting on sheer quantity). Still, the other day, the phone complained that there is no free space to install upgrades of some apps.
To make it short: how can I install a clean original 4.1.2 as if my phone was just purchased, i.e. with a clean flash?
Before you flame me and tell me I should spend the next month reading the forum: I already did!
I am afraid of the brick bug, so I guess that doing a wipe of the flash is not an option, as i guess that the bug has not been fixed by Samsung on 4.1.2. On the other hand, I do not want to root my phone, to install some custom kernel, to then wipe the flash and revert to the official ROM, risking to activate the counter, etc. Not that I don't know my way around flashing, soldering, building the flash dongle or even JTAG - I just don't have the time and nerve.
So my simple question: How do I securely wipe the flash and install a clean official 4.1.2 ROM on my phone, getting rind of 2 years of garbage files and God knows what else is slowing down my phone.
Many thanks for those guiding my way - I don't want to believe that there is a planned obsolescence in course, like Samsung building a timer that makes the phone get slower and slower...
Cheers,
vma

If you really want to enjoy the speed of your phone, IMO, you should go ahead and try CM /AOSP roms. They will give you some time out of the "slowness".
Just saying. On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
But what my method would be to...
1. Install Philz kernel for JB using recovery and boot into recovery again... to get CWM recovery this time
2. Choose wipe data/factory reset ----> Clean for new rom install. (this will delete the current rom, data and cache)
3. Mounts and Storage -> Format Internal storage.
4. Mount USB storage and connect to PC... delete all files
5. Go to advanced menu and choose reboot download.
6. connect to PC and flash stock rom JB using odin,

Thanks for your reply.
However, you say:
nokiamodeln91 said:
On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
Click to expand...
Click to collapse
While in another post it says:
"Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM"
(http://forum.xda-developers.com/showthread.php?t=1424997)
This is what I don't get... Is it safe or not? Does this warning only apply to ICS, while JB is safe?
Cheers,
vma

Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.

nokiamodeln91 said:
Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.
Click to expand...
Click to collapse
Thank you for your kind help!
I will probably work on my Note this weekend.
Cheers,
vma