yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] bluelavender:
ok, i think i'll flash your kernel now without wipe... Thanks :)
[Galaxy Note GT-N7000 General] ajamils:
I'm also among the unfortunate ones who got their Note bricked by flashing Stunner. I have been running Stunner since the first release and never had any issue until this latest release.

Now just waiting to hear back from mobiletechvideo whether this can be restored via jig or I'm totally f**ked. :(
[Galaxy Note GT-N7000 General] sutekidane:
I sent mine out to MobileTechVideo yesterday and they should be receiving it tomorrow. I really hope they can fix it with JTAG :(
[Galaxy Note GT-N7000 General] Entropy512:
Hardbricks can't be restored with a jig - JTAG goes WAY beyond jig. Bad news is that most of the ICS-caused failures seem to be the first hardbricks that JTAG can't resurrect.
[Galaxy Note GT-N7000 General] thebz1:
Do you think that I can send it to Samsung to fix even though it's the international model and I'm in the U.S.?
[Galaxy Note GT-N7000 General] ajamils:
I talked with Josh (the owner of MobileTech) and he told me to hold off from sending the phone just yet as he isn't sure if these can be fixed by JTAG and he want to test on the phones that he is already getting (probably yours and couple of other XDA members).

Lets hope for the best otherwise I will be in line for S3 :(
[Galaxy Note GT-N7000 General] Kikasa23:
actually, i always wanted to try these custom roms but threads like this always stops me. :(
[Galaxy Note GT-N7000 General] Gaugerer:
A lot of people are flashing development ROMS who are not developers and therefore don't fully appreciate the problems and risks involved. Some end up with bricked devices due to damaged hardware which means the device needs to go away for repair. So even doing a full firmware backup before flashing does not mean you can restore your device back to working order because software can overdrive hardware causing it to fail.
[Galaxy Note GT-N7000 General] mcreego:
I'm running latest ics Stunner rom without facing any issue...If I want to go back to Gb is it safe or could I brick my phone.

I really don't understand how flashing a kernel could burn the motherboard and when it happens.

Is also safe to keep Stunner rom if this don't give me problems?

:)

Thank You in advance for Your kind reply
[Galaxy Note GT-N7000 General] brooon:
More Infos

Gentlemen, please get me into the picture: WTF happened here? Was it a new Stunner Update? I´m still on Stunner V5, running smooth and reliable...what should I expect? Is it safe to run it like it is now? Or should I go back to GB via Abyss 4.2 immediately?
[Galaxy Note GT-N7000 General] Lanarix:
It's probably safe to go back to GB as long as you flash the right way. The problem is flashing Stunner rom, not flashing GB rom when you want to get rid of Stunner rom.

Yes, it is safe to keep your Stunner rom running like this.

Your phone can't just brick when you're already successfully on Stunner V5.0

I'm also on 5.0 just because it's stable enough for me, it shuts down randomly once every couple of days but who cares.. Atleast it's not bricked.

Don't worry about your phone, as long as you don't try to update it or do anything else you're fine.

We'll just have to check the Stunner thread to see if it's being fixed, before that time I'll stay on V5.0 :)
[Galaxy Note GT-N7000 General] MR.change:
Well actually if I understood entropy's posts here ( a must read) then I'd say using leaked ICS ROMs will gradually degrade the condition of the emmc ,while flashing or restoing anything under such kernels will probably kill it.

Solution to return to GB safely is to flash a stock ROM via Pc ODIN ,that should bypass the broken kernel wipes I think.
[Galaxy Note GT-N7000 General] @denny:
leave as is and wait for confirmation from some one who knows what he is talking about.ie entropy etc
[Galaxy Note GT-N7000 General] Abagnale:
I'm running stunner rom 1.4.26.1 and I heard from the good source that only version 1.4.25 was causing the bricks. Any version above is brick free :)

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] :
My understanding based on having seen first-hand the angelom kernel catastrophe, the more recent stunner issues and the information entropy provided earlier in this thread is that the stock leak kernels we are using for ICS have no safeguard that prevents them from directly harming your emmc IF something goes wrong when flashing. That is, under normal, ideal operations where no error occurs during writing to your system partition, you're probably safe even on an affected kernel. If even a couple of bits get corrupted while writing to your system, though, nothing stops the affected kernel from pissing all over your emmc as happened in both the angelom and stunner incidents (where there was an error in the script formatting system).

If this is the case, then using Entropy's ICS kernel (or presumably any rooted GB kernel) to write to system is safe, even if you try to run some faulty formatting script. And in fact, of those who flashed the dangerous build of stunner (1.4.25 build 1) before it was pulled, no bricks were reported from the ones who had flashed it using entropy's kernel. Also I am thinking that perhaps neobuddy fixed this issue in the LP6 kernel that he had rooted himself (props to him for doing it without chainfire), because he and other LP6 users managed to flash the corrupt package without issue as well.

I propose that for a matter of safety, the first stepping-stone to flashing any ICS rom from here on out to be flashing entropy's kernel in desktop odin (which presumably, as another poster mentioned, circumvents having to use another kernel to write to the system partition) and THEN flashing the rom.zip in recovery.

Does all this make sense? Anyone want to confirm?
[Galaxy Note GT-N7000 General] MR.change:
That's Pretty much what I understood from entropy's posts ,but what I don't know is if abyssnote kernel 4.2 has these issues? I thought it was based on GB and thus safe to use?

And if my understanding is true then one wouldn't need PC ODIN to flash ICS ,but rather flash abyssnote 4.2 and then flash any ICS ROM.

But here is another culprit (again correct me if I'm wrong) ,most ICS ROMs come with their lp5 kernels and will override abyssnote kernel thus putting you at risk again.

So what needs to be done after flashing a ROM.zip with Recovery or even PC ODIN is to flash entropy's kernel using PC ODIN so as to overwrite the faulty kernel safely.

Did I make any sense?
[Galaxy Note GT-N7000 General] :
This is correct, abyssnote should also be fine for writing to system, but you don't want to be flashing it in cwm from an affected kernel. It would be ideal if you flashed ANY unaffected root kernel using Odin before flashing a ROM in recovery. I believe it is okay for a ROM to include an affected kernel, too, so long as you don't do very intensive writing to the system partition while using it, but you would need to flash an unaffected kernel in desktop Odin again before flashing something else in recovery.
[Galaxy Note GT-N7000 General] E90 Commie:
Let's see here: I am now running Criskelo V2 LP6 without any problems. The kernel is the leaked LP5. I guess that everything is OK as long as I stay on this combination - i.e just using it.

It seems a bit strange to me that "the kernel degrades emmc" by just using the ROM as usual. I fully understand the issue with WRITING to the emmc but not that it would be "dangerous" to just use the ROM.

The question is when it comes to flashing a different kernel: is Mobile Odin OK or is PC Odin an absolute necessity?

Since the Mobile Odin boots its own kernel and does the flash completely separated from the system kernel, I can't see any problems with using that method to replace the LP5 leak kernel.

The most important question is: should I quickly replace the LP5 kernel with a different one or is everything OK as long as I don't flash new ROMs using the LP5-CWM?

My device is working great with Criskelo otherwise, no issues at all.
[Galaxy Note GT-N7000 General] rebista:
When the "degrading" can also happen when deleting "larger" files then I guess "normal use" can be dangerous too.

Today I deleted a large file and the file manager got stuck. And now I am a bit worried about what could have been the reason for this ...
[Galaxy Note GT-N7000 General] remixtech:
This morning I came back to GB, I will wait for CM9 custom Kernel. Don't want to take more risk every day.

Cm9 will come in a near futur I hope...
[Galaxy Note GT-N7000 General] JuliancitoD:
What does everyone means by "large file"? Just a couple of megabytes or is it gigabytes?
[Galaxy Note GT-N7000 General] E90 Commie:
It is important to have a confirmation here:

Should everyone that are using the LP5/LP6 kernel immediately flash a different kernel through PC Odin (or Mobile Odin) since the current kernel can damage the emmc just from NORMAL USE OF THE ROM?

I.e - I am running Criskelo V2 LP6 with LP5 kernel, should I immediately download a different kernel and replace LP5?

Or can I keep the device as it is (it is working normally) and then flash a new kernel later - as long as I DON'T USE CWM for that flash?
[Galaxy Note GT-N7000 General] copperdawgnc:
Need an expert

What should we do?
[Galaxy Note GT-N7000 General] ahalford:
I guess, CPU load, while processing large file, and not perfectly optimized kernel. There can be some hanging with user apps, if it's not optimized for ICS, but if it's stock file manager - it's a rom problem.

I'm on LP5 kernel. I do feel slight heat add on heavy processes, comparing to GB. Although, I can't judge in objective, cause the phone is in fairly thick case (Case Mate Emerge Smooth) and it's definitely not cold weather in Israel. I was observing heating issue with GB also, and I can't tell it's very big difference. Also, it's naturally, when coming to custom rom, to follow more closely all possible issues, and, as result, to get a bit over-impression about what's going on.

Anyways, I'd say - if someone is getting fc's or stuck on constanst base, may be it worth to come back to stock GB.
[Galaxy Note GT-N7000 General] :
Well the thing is that the system partition isn't the only thing on your emmc. The parts that your phone has non-su read/write access to might also be affected by this kind of "feature"-that is, there's nothing stopping your kernel from pissing all over your data partition or internal sdcard if there's a hiccup in data transfer while installing an app or even just taking a photo. If that happens it could make one of those partitions unusable, as happened in the I9100 forums, but this seems unlikely and as far as I know hasn't been reported on a note. If you want to be super paranoid, by all means flash entropy's kernel asap or return to gb, but I've been using ICS leak kernels since about the week of the LP1 repack without an issue and I'm going to wait until entropy's kernel is a little less alpha before I make that transition.

If mobile Odin boots its own kernel to flash things then it should be safe to flash a kernel that way provided chainfire's mobile Odin N7000 root kernel isn't affected by this (it's probably fine), but as usual most devs recommend desktop Odin over mobile Odin for just about anything so I'd rather go that path.
[Galaxy Note GT-N7000 General] E90 Commie:
Thanks for the answer!

My plan is to stay on the LP5 kernel until that new Entropy Kernel has been updated a bit further. Returning to GB is obviously an option but I am not very interested in that at the moment.

The Mobile Odin is, according to the information available (and that is what it does) boots it's own kernel when you flash so it should be safe to use to flash a safe kernel.

I have updated a couple of apps and copied large files to the emmc with the LP5 kernel using USB Mass Storage mode without any problems yet. I don't notice anything amiss with my Note. So I don't see the need to be super paranoid. I guess it is OK to just stop installing and updating apps and just use the device and wait for a new kernel.
[Galaxy Note GT-N7000 General] Entropy512:
A bit more information:

The way flash memory works, it needs to be erased before writing to it. This is a bit different than spinning magnetic disks, where you just overwrite it. Writing new data to a blank disk and writing data over existing data were identical in performance.

As a result, with magnetic disks, the classic way of deleting a file or formatting a partition was just to delete references to it - the actual file contents would still be there. On flash, this was not optimal for performance because writing to blank blocks is much faster than writing to a block that has info on it because that block must be blanked first.

Eventually, the TRIM command was added to various operating systems, such that when a partition was formatted or a file deleted, the OS could tell the flash controller that those blocks were no longer used and could be erased immediately. It makes the wear leveller's job easier to have a list of "unused" blocks.

I believe MMC_CAP_ERASE is related to TRIM (I haven't had time to figure out the exact differences) - even with TRIM disabled, it seems to make a difference. Gingerbread kernels and I9100 ICS kernels don't support TRIM or ERASE. ICS kernels for SHW-M250S/K/L support ERASE - and these seem to have a risk of hardbricking or permanent eMMC damage when you do a large ERASE - confirmed for a wipe in CWM and any operation that wipes first, suspected for wiping in 3e recovery of a non-repacked leak kernel that is affected, and I suspect a large file deletion (such as a video file of hundreds of megabytes) may also be risky - but I'm not sure.

It seems like ICS leaks for the Epic 4G Touch, AT&T Galaxy S II (SGH-I777), and the Galaxy Note (GT-N7000 and GT-I9220) have the same issue as the SHW-M250S/K/L kernels based on reports. Unfortunately leak kernels don't have source so there's no way to tell what changed, no way to know which ones are dangerous and which ones aren't. For this reason I don't trust any ICS leak kernels for the above devices.

This may be a problem only for a small percentage of users - 1%, 2%, maybe as high as 5% - who knows. Other people are fine with the affected kernels - for example Task650 and ktoonsez never had any issues with the UCLD3 leak kernel, but others hardbricked. gokhanmoral was able to wipe multiple times with SiyahKernel 3.1rc6 (based on SHW-M250L ICS sources instead of GT-I9100 ICS sources), but others hardbricked or experienced permanent damage when wiping.

Right now, MMC_CAP_ERASE seems to be the suspect - but no one can be entirely sure without:

Source code for leaks of affected devices that don't have source (Note, E4GT, I777)

Taking dangerous risks such as trying to reproduce the problem - if you reproduce it, it's time for a motherboard replacement.

The only thing we know for sure is that the GT-I9100 ICS leaks and official releases seem safe, as are kernels built from the I9100 Update4 source drop, as are all known Gingerbread kernels for any device.
[Galaxy Note GT-N7000 General] remixtech:
I did. But I wrote a bit fast. I correct : all the ics leak available for us (except entropy one) are dangerous.

Envoyé depuis mon GT-N7000 avec Tapatalk
[Galaxy Note GT-N7000 General] MR.change:
This is actually quite interesting , I didn't know that mobile ODIN uses it's own kernel to flash ,even though I use it as my preferred flashing method.

Although I think the reason most devs refrain from using it is because it doesn't maintain root on ICS ?

Can anybody confirm or deny this please?
[Galaxy Note GT-N7000 General] TexasBlack:
OK y'all my problem is that I'm stuck in version 5 stunner... my cwm won't work for anything... I tried to flash abyss red,1.4.26 and 25....it gets stuck in installing mode....so wtf....
[Galaxy Note GT-N7000 General] remixtech:
---> You lost root...
[Galaxy Note GT-N7000 General] TexasBlack:
So can I just root while I'm in stunner 5...or what's my next process
[Galaxy Note GT-N7000 General] yanix:
I think chill392 was referring to Angelom's ICS-based Kernel which was discontinued.

http://xdaforums.com/showthread.php?t=1526852
[Galaxy Note GT-N7000 General] brycestejskal:
Download mode and Desktop Odin to a GB Rom

I Lost root as you did when I used Abyss 4.2 to go from GB to Stunner 1.4.26. Reflashed Abyss and restored Nandroid. Then used mobile ODIN to flash LP1 Repack and then flashed 1.4.26 and root was maintained.

If you lost root you will need to Download mode with desktop odin.
[Galaxy Note GT-N7000 General] :
If you don't want to download+flash the entire LP1 repack you could just odin flash any root kernel to restore your root without wiping your note. Here is a link to the LP6 repack kernel in a .tar which you can flash in the PDA slot in desktop odin. (the action of flashing this kernel with odin should not harm your emmc despite this being one of the kernels affected by the emmc_write problems)

http://xdaforums.com/showpost.php?p=25224106&postcount=160

I still urge people to start flashing Entropy's kernel at least in mobile odin prior to flashing new roms, though
[Galaxy Note GT-N7000 General] Latoc:
Ok guys,

So now that I am back to GB, and everything seems to be working right, is it still possible that my flash memory is damaged and will give me trouble down the road ?

Is this like an unnoticed cancer that will kill you later, or more like a heart attack...?

Thanks for your answer.
[Galaxy Note GT-N7000 General] :
You're probably fine. Losing root is not necessarily related to emmc corruption.
[Galaxy Note GT-N7000 General] Latoc:
Thanks for your answer.

I have not lost root or had any problem when I was using the different ICS roms, it's just that I am worried I might have screwed my phone without noticing it YET...

Fingers crossed.
[Galaxy Note GT-N7000 General] tugas2khas:
I was on Alba v2 and the go to stunner 1.4.25... then to stunner 1.4.26, patch the stunner 1.4.26.1, something went wrong (i only got half of the apps). later flashed 1.4.26.1 full... use it about 1 day. Note turning hot.

This morning i flash abyss kernel and flash litening rom (GB).

Mostly I flash through CWM. I don't know if i am effected or not, but now I'm on GB N7000XXLC1.

I am tempted to flash another ICS (just downloaded MidNote 1.1). Is it okay for me to flash, or should I wait until everything settle down?
[Galaxy Note GT-N7000 General] ajamils:
So any update from the people who got bricked? Has anybody been able to bring back the Note to life?
[Galaxy Note GT-N7000 General] graemeg:
Absolutley agree, im still on Rooted GB stock rom.

Everytime i think oh this new Ics custom looks ok, i find a thread like this, im still avoiding custom roms because too many notes are being bricked, ill wait for official ics to be safe.
[Galaxy Note GT-N7000 General] sutekidane:
My Note's supposed be delivered today to MobileTechVideos, but USPS decided it was too late and will be delivered tomorrow. I will report back what Josh has to say about it when he starts working on it. I seriously hope this will fix the Note, and let this be a good lesson to myself about using leaked releases :(
[Galaxy Note GT-N7000 General] Djoudi:
I'm not installing it

Me too I've done the same, but now I decided not to install any custom roms until further notice, because the risk is so big that we can not just flash roms without any warranty.

The developers are doing a huge job to bring ICS to Note, we say thanks to you all.

"Why aren't you working with Samsung, ICS will be available more quickly. :)"

I council you not install any cooked ICS ROM, wait for the official update.

Dj
[Galaxy Note GT-N7000 General] :
If you are going to flash another rom, I would recommend using odin to flash Entropy's kernel .tar and then flashing midnote from CWM recovery within Entropy's kernel. Entropy's kernel is still in alpha stages and some people are having problems charging, but there is no risk of emmc corruption in wiping with it. You can flash a different kernel (presumably LP5 or LP6) in CWM or odin once you are in a working midnote install. If you want to be paranoid about your flashes, always odin Entropy's kernel before writing to your system partition.

EDIT: Your note is probably getting hot because the LP6 kernel by neobuddy frankly isn't that great. If you flash LP5 in mobile odin you'll probably be fine.
[Galaxy Note GT-N7000 General] @denny:
Just to let you know got mine back , jtag didn't work, will have to send to Samsung for motherboard replacement, this is gonna be expensive....I have bought another note and am running stock on it,I Dare not put even root on it and I have to say I forgot how good stock really is it's quick and EVERYTHING works:D and when ics comes out I'll get rid of a bit of bloatware, when my brick comes back I'll sell it to recoup some of my loss.if I ever did go down the rom route again it will be only with the likes of experienced devs like the cm9,checkrom, criskello who really test their stuff and know their stuff, this has been one expensive lesson...one last thing it would have been nice to at least got a pm from Neobuddy to say woops sorry about that mate and here's exactly what happened to your note and this is how you can try to avoid that sort of thing in the future.
[Galaxy Note GT-N7000 General] sutekidane:
Oh damn. Thanks for news... this is a very, very expensive lesson :(
[Galaxy Note GT-N7000 General] greenlant:
Asking for advice!

I´m still on Stunner V.5 (flashed LP1 before, but the settings are saying that I´m on LP5?!). I flashed Abyss 4.2 once, because I wanted to try out criskelos ROM; but reverted back to Stunner sucessfully (again), without any issues.

Generally: no issues at all, but I´m afraid that something may happen (bigger files etc.).

So what am I supposed to do? Should I just flash Abyss V5 via CWM and restore my ROCKET ROM GB Backup? Is this safe? Or do I have to flash something via Odin PC? Or via ODIN MOBILE (which I purchased as well).

Whats the best solution? The easiest for me would be the CWM-Abyss-CWM-Restore Version, just because I´m familiar with that. But then there are the stories about wiping bricks & stuff...so is it dangerous to flash Abyss 4.2 and wipe afterwards, just before restoring my backup?

Damned, I´m the confused one...^^
[Galaxy Note GT-N7000 General] MatanZ:
Why do you say that about gingerbread kernels? The kernel appears to support MMCTRIM in mmc_blk_ioctl(), and Abyss 4.2 is compiled with support for this feature (CONFIG_MMC_DISCARD).
[Galaxy Note GT-N7000 General] matius44:
Your best and safest solution is PC Odin one of the pre rooted Gingerbread ROMs, then get the CF Root kernel for that ROM and flash it using the "already rooted.bat" method

From there you can keep that ROM or restore your GB backup without issues
[Galaxy Note GT-N7000 General] mac231us:
NO problems here..on ICS since late Feb..various versions

CM9, Stunner, MIUI (mostly), LiquidROM, Alba ROM, Jdroid...criskelo early on..tried all..flashed..mobile ODin..straight PC Odin too..(heck with the triangle nonsense..do not care if something goes wrong, will see then)..clean installs..dirty installs..bootloops (sometimes through my own trying out things)..done all kinds of my own noob-type 'modding' if you can call it..LP1/5/6..luckily avoided the Angelom kernel that caused many bricks..

so my Note runs fine..just fine after all that fiddling around..may have flashed easily over (make that) 100-200 times..really

and plenty of nandroid backups and restores along the way..currently running off a restore that works great..MIUI v7..not perfect but works for regular stuff, sms mms calls internet wifi data camera gallery usb playstore etc..never bothered too much with some specifc dpi/tablet-mode stuff
[Galaxy Note GT-N7000 General] ajamils:
I am going to go ahead and order a new Note. Was waiting for S3 announcement but I just cannot live with a crappy phone for another day.