yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] MR.change:
OMG ,I was just about to send you a pm regarding this when i saw this thread

I wrote this on several threads already ,but here we go:

I was already running CM9 build#3

I downloaded the update yesterday from samfirmware and also downloaded cf-root xxlpy kernel .

flashed both files using Mobile ODIN and the flash went well ,then I did a full wipe as suggested by DR.ketan

also went well

the OS booted as usual ,fiddled with it for about half an hour then decided that CM9 was much better, so I rebooted into recovery ,done a nandroid backup in case I wanted to restore the stock ICS back later on.

then went ahead to restore my CM9 nandroid backup ,the restore began:

erasing boot image.......

flashing boot image......

restoring system .......

[stuck for a while.....then]

error restoring system

so I tried again but with a different restore point

erasing boot image.......

flashing boot image......

restoring system .......

[phone stuck for a while.....then restarts]

it happened 5 or 6 times with all my restore points

finally it struck me like a train that the bug is still present and that I've just corrupted the system partition of my emmc.

after plugging it to the charger ,then turning off and on again ,I tried to restore back to XXLPY as a final attempt ,and what do you know it got stuck for a minute at system partition but then suddenly it resumed restoring and I was able to boot into the stock ICS once more.

I decided not to test my luck again so I flashed stock GB using mobile ODIN ,and after booting into it I flashed back my CM9 and then restored my old CM9 nandroid backup.

bottom line is that I was lucky I could still boot into recovery ,and luckier still that system partition responded again after a while.

and sorry about Chas's phone ,I hope he gets it fixed soon ,my prayers be with him.
[Galaxy Note GT-N7000 General] duowing:
Could this be completely kernel related or could this be CWM related in the way that it's not working correctly with ICS whether official or leaked? Also this could be very similar to the situation we had with the HTC Thunderbolt. People were randomly bricking. Everyone at first thought it was related to the Gingerbread leaks because that's when the bricking first started showing up. After a while it turned out that people who had not rooted, wiped, installed custom roms, etc were bricking. It just turned out to be luck of the draw with the internal memory dying. It wasn't wide spread, but it happened. People were pretty much saying it's just a matter of how many wipes, read/writes, etc that your internal memory would decide to go for. Some people were flashing the leaks and roms like crazy back and forth every day with no problems. Some people died after flashing one time.
[Galaxy Note GT-N7000 General] androidindian:
Haha true! Its relatively simple to get the phone repaired in India... but a Pain too..wouldn't want to go through it again...

I did do a couple of wipes and flashes via cwm yesterday to lpy rooted and stock and still great so far. I'm back on cm9 though :) but didn't see any issues

In fact if you go through all the posts in this thread and dev thread only one guy has faced an issue...others are all fine.

Also know a few others who are running fine on lpy..
[Galaxy Note GT-N7000 General] MR.change:
****...sorry about your phone mate ,you sure don't deserve this.:(

and yes I seriously think it is kernel related (see my post above)

I chose WIPE from Mobile ODIN and since it wiped from recovery AFTER flashing that would mean that I wiped from LPY kernel:eek:

add to it that I tried restoring my Nandroid backup ,and that would mean two wipes on an effected kernel.

no wonder it nearly bricked ,I'm soooo lucky it didn't brick actually.
[Galaxy Note GT-N7000 General] jbg1:
i did the exact same, can we go to cm9?
[Galaxy Note GT-N7000 General] hxkclan:
Haven't had any issues with the LPY rom. Flashed it on top of CM9 build#7 and factory wiped the whole thing. No issues whatsoever.
[Galaxy Note GT-N7000 General] chasmodo:
You were extremely lucky to scramble home, I'd say. I'm genuinely pleased that it

worked for you.:)

Thanks for the kind words, BTW.
[Galaxy Note GT-N7000 General] clubtech:
I had the exact same problem but i was never ever on a leaked Kernel OR LPY. the last update of CM9 (#7) has some issue with restoring system for some reason. I also have a problem doing a back of build #7 with their own Kernel getting stuck on backing up the system partition.

Again i was never on LPY or any leaked kernel before so it is safe to say that the problem you are describing is not related to LPY but more to the latest build of CM9.
[Galaxy Note GT-N7000 General] decat:
I had the same problem last night.

First I flashed ICS LPY + CF root, played a bit and made a nandroid back up.

Decided to check the Alba one and flashed it too. Performance on the stock LPY seemed to be better so I tried to recover the nandroid backup.

While recovering I got the same error as you.

Booted in download mode and flashed a GB rom and all became fine again.
[Galaxy Note GT-N7000 General] kimzplaze:
Let's just stay clear from cwmr operations until this is cleared up by the devs =D.. After reading through the threads for this, seems like some encountered near- brick situations via nandroid (one cwmr operation )

To b on the same side, dun do stuff thru cwmr for the moment.. =D
[Galaxy Note GT-N7000 General] MR.change:
yes ,I was extremely lucky ,but almost had a heart attack (at 2 am :D)

but seriously sorry about your phone ,you are a very nice person and this shouldn't be happening to nice people:(

I was on build 3 ,and I was able to restore it just fine when I flashed back to GB.

besides ,like I mentioned before ,I had many Nndroid backups ,most of them are stock GB ROMs

and none of them would work.

so it's not a cm9 issue ,that I'm sure of.

very pleased that it worked for you

now stay clear of LPY please
[Galaxy Note GT-N7000 General] chasmodo:
Absolutely not. Things that happen in CWMR are completely disconnected from the

Rom you are using. It's the same as if the Rom didn't exist at all.

So, it's either the kernel, or CWMR, or the incompatibility between the two.

Sorry I'm out of thanks for today, so I'll just repeat thank you for your kind words.:)
[Galaxy Note GT-N7000 General] kimzplaze:
Sorry to hear that.. But what were you doing before you get the brick.. =(
[Galaxy Note GT-N7000 General] MR.change:
well ,I'm not out yet

so +1
[Galaxy Note GT-N7000 General] altae:
I'm kind of surprised because of this thread. I mean we are talking about root, CWM, custom roms, altered kernels... but some here take it for granted that the reason for this one brick must be the official ICS rom by Samsung. If I had to look for the reason for this brick I certainly would not start with the official Samsung rom.

We use software/ tools on our phones that most of us (me included) not really understand. There's the one good, chainfire, that provides everything. Do we know what exactly he does? Please don't misunderstand me, I don't want to blame anybody of anything. I just want to say it sounds a bit strange to me to blame an official rom for a bricked device when there are root, custom roms and the like involved.

As far as I am concerned I'm not afraid that my Note running the (rooted) official ICS rom suddenly bricks.
[Galaxy Note GT-N7000 General] Mystic38:
Can we put this into perspective here?..

1. There are probalby well over 6M Note users at present, of which 95% or more are NOT present on XDA... (we need to remember to keep balanced viewpoints soley for this reason)

2. Any given tech market usually split USA ~50%, EUR~30%, ROW~20% and Germany is typically 30% of Eur market...

3. If we assume Note sales are split in a similar fashion then this means that potentially 500,000 (approx) users may have received notification in Germany of either OTA update or notification via Kies...

So, lets assume that only 10% of those that have been notified have so far upgraded.. this means that approximately 50,000 folks have upgraded so far...and even if my approximations are far off, it still means tens of thousands have upgraded.

yet, I have not seen a SINGLE post where someone has gone from a stock unrooted ROM, updated it and seen ANY type of issue like mentioned.

any such issue regarding OTA or Kies notified updates bricking phones would be all over the German technical press.... so lets calm down.

On the other hand, if any issue or item is ONLY affecting those that are on custom, crafted, botched, created, rooted or otherwise modified from clean pure 100% stock german ROM then it will be all over XDA... but it wont be a bug to its correct definition.
[Galaxy Note GT-N7000 General] chasmodo:
I'm the one who got the brick.

And just to clarify, nobody said, not even once, that the official Rom is to blame.

Kernel and CWM were suspected by the kernel Devs (Entropy and CF). I'm sorry

if you don't know what a kernel is. I just find it a little odd that you have such a

firm opinion when talking about things that you so freely admit you know nothing

about.

Anyway, here's my take on the issue:

http://xdaforums.com/showpost.php?p=25968344&postcount=14

It's in this very thread, and you could've read it if you wanted to bother just

a little.

My gut feeling is that you're right. I don't exactly agree with your choice of

words (botched Roms), but I think that users on unrooted stock ICS are safe.

Provided they don't do any wiping/formatting from stock recovery (not much

chance of that happening).

But it's just my gut feeling. The fact is nobody knows for sure.
[Galaxy Note GT-N7000 General] deathst:
Still.. Most of the brick devices are either running some custom ICS rom or that leaked chinese ICS.

So far has anyone managed to brick their phones from STOCK GB?

If you want to flash this ICS rom.. Just Flash back to GB with Odin (Not Mobile odin) and flash this ICS with Odin? Better safe then having a expensive paper weight..
[Galaxy Note GT-N7000 General] altae:
Look I'm sorry but have you read the header of the thread? It says "4.0.3 LPY affected with BRICK BUG".

Furthermore that's the text of the op:

To clarify that I'm not to lazy to read I'd like to stress question 1 "why is the bug present on an OTA update".

Do we agree that the op talks here about a bug in an OTA update = bug in an official rom? So the op does indeed blame the official ICS rom.

I don't want to go any further and argue with you about whether I know what a kernel is or not. Just want to say that you could be a bit more careful how you talk to other people. I did only express my opinion and explicitly wrote that I don't want to blame anybody of anything. I really don't see why you feel yourself that much concerned that you need to tell other people that they did not bother to read the thread. Because I did not talk about you apart from the fact that I mentioned your case as the one famous brick.
[Galaxy Note GT-N7000 General] chasmodo:
Does it say OTA anywhere in the title?
[Galaxy Note GT-N7000 General] Colingajewski:
Maybe I'm too timid, but I stay with official Roms. I just don't want to end up with a dead phone. No disrespect to those who like to experiment and develop.

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] altae:
Look to tell it in your own words: If you just bothered a little (to read my post completely)... you would have realized that the OP indeed talks about OTA. And other people in this thread also talk about OTA, official ICS rom or the like. That's why I thought I had to add something to the discussion. Because I'm really surprised how someone can suspect an official rom having caused a brick when there are rooted kernel etc involved. Once more, I did not talk about you.

One last thing concerning the header: That's the name of CF's kernel: CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5.zip

That's the description of the rom: N7000XXLPY---------4.0.3---------2012 May-----------N7000OXALPY--------

So what was the op talking about in the header and in the initial post?
[Galaxy Note GT-N7000 General] chasmodo:
Ok, St Galen, I'll step aside.

Sorry to have caused you any aggro.
[Galaxy Note GT-N7000 General] be_vigilant:
i had a heart skipping moment...

was on cm9 but plagued by SODs so decided to try official ics. restored my GB nandroid then flagged official rom through mobile odin replacing kernel with chainfires. hated the official ics so wanted to go back to cm9.

rebooted into lpy cwm and chose restore cm9. it locked up and rebooted at flashing system.

it had restored the cm9 boot as i was in cm9 cwm. however every time i chose to restore it would hang on system then reboot. my heart sank...

got the phone working again by flashing redpill kernel, then restoring gb.

that's it for me now with official ics. its cm9 or official GB from now on
[Galaxy Note GT-N7000 General] captainhakan:
I got pissed off to see the threads about official german ics has risk to brick my Note at first as i love my german rom.So far so good. I did have a single issue with german ics rom. Then i decided to dive in to see what was really happening and i came to realise it's just chas's Note that bricked so far. I totally agree with Mystic's conclusions below and i'll stick to official ics release. I just returned to official kernel from chainfire's cwm kernel by rooting it with mobile odin pro. I am pretty confident with the stability atm. If Samsung seen a little bit of chance to brick phones by official ics rom they would make announcements urgently as Germany is very strict community against these kind of consumer issues. You should have seen many german people spreading the bad news everywhere online regarding their phones got bricked using official ics roms but no report so far other then chas's note and he was using CWM obviously. I see no risk in using the official rom as rooted as well since i don't mess up with CWM till Chainfire hopefully comes out with a fix soon.
[Galaxy Note GT-N7000 General] iyousif:
I am really sorry for you brother and hope you will get a replacement very soon :)

So, we still don't know if it's the official or CF-Root but we all agree CWM and kernel are not playing well together, right?

Can anyone post a download link to official LPY kernel? Thanks!

Edit: Any SAFE way to revert back to official kernel while being able to keep the Root and only the Root? Thanks!

Don't need CWM until it's confirmed playing nice with official, this may need official source code I guess!

Confused :(
[Galaxy Note GT-N7000 General] MR.change:
That maybe true ,as stated by chasmodo himself ,the cause of the bricks maybe due to incompatibility between CWM and LPY kernel .

And even if the kernel is effected without CWM ,there wouldn't be any chance of users reporting the issues for the following reasons:

1.no one without CWM is going to flash custom ROMs .

2. People with stock recovery are also unlikely to perform wipes.

3. Even if some poor chap with 100% non rooted stock kernel brick his phone then he wouldn't know the reason and just take it to Samsung warranty .
[Galaxy Note GT-N7000 General] Note_E:
Let's be real. As soon as LPY hit XDA, everyone began flashing like HAM (as JayZ would put it). People were coming from different roms, kernels, bootloaders. I think the problem would've manifested in more units straightaway. The only thing we can do is give it time and research the issue

Also, there seems to be people who are not happy with LPY and flashing back...haven't seen anything happen with that either.
[Galaxy Note GT-N7000 General] sudisk:
Don't be. I also believe that Sammy ICS kernels are no longer compatible with cwm included with cf-root.

Sent from the great Note
[Galaxy Note GT-N7000 General] beestee:
Just be sure to use MOP or PC Odin to flash the fix rather than the still-in-question CWM from the CF-Root LPY kernel.
[Galaxy Note GT-N7000 General] Princeomi:
Try Bodivas pre rooted official roms. use pc Odin:)

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] bamboo12:
why is no one pointing the finger at the cm9 kernel, when a user bricks coming from i9220 --> cm9 it's i9220 kernels fault but when cm9 --> n7000 kernel, it's naturally n7000 kernel's fault

maybe it's just ics in general that's the problem
[Galaxy Note GT-N7000 General] iyousif:
Thanks, but he did removed it!
[Galaxy Note GT-N7000 General] mobilevil:
dev said mobile odin is not using it's own kernel to flash, it is using your system kernel to flash.

looks like mobile odin is flashing a temp kernel to flash just before reboot! this is still dangerous
[Galaxy Note GT-N7000 General] Tiny Wiz:
Why on earth would you go into LP6 CWM and do a restore ?

Haven't you read any of the warnings about why not to restore and wipe from any ICS leak?

Maybe I am not following what you are saying, but blaming the official ICS... Just don't make any sence to me.
[Galaxy Note GT-N7000 General] bamboo12:
so he belittle someone for flashing from ics kernel and bricking their phone, and then he does the same thing himself and bricking his own phone.. the irony!
[Galaxy Note GT-N7000 General] chasmodo:
It's a typo, obviously. He meant to say LPY - he was on official Rom, so it couldn't have been LP6.
[Galaxy Note GT-N7000 General] musashiro:
after all, 6 is near to Y on the keyboard..:)
[Galaxy Note GT-N7000 General] Drakosha:
Success story :)

Hi!

I was on official (rooted) LC1. Here's what I did:

1) Removed SD Card (Always do that, Samsung likes to accidentally wipe it along with internal memory)

2) Format internal memory from settings

3) *2767*3855#

4) Fresh clean Note! :)

5) Flashed LPY with PC Odin, finished "Config wizard"

6) Flashed CFRoot with PC Odin, updated SuperSU binary, installed Busybox

7) Flashed back the extracted original LPY "zimage" with PC Odin (just need to pack it in the individual TAR, then Odin flashes it without questions)

8) Format internal memory from ICS settings

9) *2767*3855#

10) Fresh clean ROOTED ICS Note with busybox! :)

11) Deleted "android.secure" folder from SD Card in card reader and put the card back into the phone.

No problems at all. Now my rooted Note has 100% stock firmware, 100% stock kernel, stock recovery, no triangle - and no worries of bricks or incompatibility.

I recommend this method to everyone - used it many, many times on Note, SGS2 e.t.c. If you're not concerned with flash counter, than just flash stock rom with PC Odin --> flash CFRoot with PC Odin --> Flash original zimage with PC Odin. That's it.

WBR - Draco.
[Galaxy Note GT-N7000 General] Latoc:
Your method is very clean and logical. I work like that too.

Never have any problem aside from known bugs. No SODs, no random reboots, nada.

If only everybody could flash like you do, the threads would be purged from all the crap posts...

Oh well, at least we can have a good laugh sometimes ;)
[Galaxy Note GT-N7000 General] crusciotto:
I totally agree with that and apart from recommending to read read read (ever wondered why mainly people with few posts do have few or no problems?) for me it helps a lot to both understand what and how to do things - but also what NOT to do.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy Note GT-N7000 General] chasmodo:
You unrooted your Rom when you flashed back the original kernel.
[Galaxy Note GT-N7000 General] iyousif:
Seems legit! If you just put a download links to all requested kernels along with this, it should be a reference to all. Thank you in advance.
[Galaxy Note GT-N7000 General] octavian90:
Oops
[Galaxy Note GT-N7000 General] be_vigilant:
typo/brain fart i meant LPY
[Galaxy Note GT-N7000 General] Princeomi:
Sorry for that!, may be ICS is dangerous for the Note. Lets get back to GB! ;)
[Galaxy Note GT-N7000 General] haven80:
All perfect here. Full root access gained after two flash with mobile odin the stock non rooted and flashing cfroot LPY using the "alredy rooted" method from pc.

Goodbye Gb.

Officially wellcome Ics.

Inviato dal mio GT-N7000 con Tapatalk 2
[Galaxy Note GT-N7000 General] mR.fR34ky:
Yes it is a nice method, but after all you just increased your counter, but it is actually doen't matter coz' chainfire will update the remove yellow triangle app after all :) Thank you for sharing, will definetly use when a nice checkrom and jkay mod is available and ofc when someone proove that lpy is not dangerous.
[Galaxy Note GT-N7000 General] kulisap:
lame

Brick GNote with an official update??
[Galaxy Note GT-N7000 General] puncosorock:
hello congrants. would you post your specs or your kernel when updated?

thanks
[Galaxy Note GT-N7000 General] musashiro:
ok based on the poll:

we have 67 brave souls (count me in)

and 5 cowardly users (sorry about the cowardly :D)

not trying to be ignorant but im getting tired of seeing users post :

"yes, full wipe on recovery solved the problem. all smoith now"

"ics rocks"

"no problems so far"

and on the other hand only one person got bricked using LPY Cfroot...

let me break down all the bricks I *saw* so far...

1. chasmodo. flashed LPY CFroot on CM9 then do a WIPE... (take note this is the only scenario where CFroot is responsible)

2. _Jkay_ got his phone bricked or the proper term is broken since his kid dropped the phablet..

3. CFroot, again he is coming from LEAK stuff...

4. JamieD81, again, he/she is from LEAK stuff...
[Galaxy Note GT-N7000 General] REVERSiN:
guys why are you all so mad :|

i mean WTH it's a brick it's not like we haven't seen any around lately, not first probably not last (with it would be)...

wake up all of you, who ever wants to flash the damn ROM just flash it without arguing with each other on the simple rumors, facts, bugs, what so ever!!

iam on ROM it runs smooth and perfect, though the guys who believe there is a bug do own us an answer as far as i know CF bricked his note so he can't test any of this, chas did brick his too and not a word of him.... give feedback something for now everyone running LPY is happy including me no issues i wiped dalvik, battery stat, data and flash a file so it works for me (iam not an example BTW) i decided to try it and it worked.

have faith i can't remember other OTA updates that has bugs you all could be right and you all (hopefully) be wrong so i gaven't seen complains about the ROM on any other forum WTH it's on XDA only ? any one bricked his device too ? come on people say if yes so we know

so far 1 < 1000XX users
[Galaxy Note GT-N7000 General] bamboo12:
problem is we can't flash anything unless someone cooks a rom for us, and with these scare campaigns the devs shy away from cooking roms
[Galaxy Note GT-N7000 General] SpyderTracks:
Geez, I hope this blows over soon, I don't think it's fair to bash our devs for bringing to light issues, no matter how presented.

I flashed the new official ics (800mb full pack) successfully over stock rooted GB lc1. Didn't have cwm installed, used mobile Odin, selected ever root and cleared dalvik cache. Root was retained, and all apps/settings.

Changed dpi to 160, got fc's all over the place, reverted to 240 and everythings working well, no issues at all.
[Galaxy Note GT-N7000 General] Hawklan_D:
Sorry I'm pretty new to all this, but isn't no rw mounting on \system and no cwm referred to as a partial root or 'not true root'?

I thought that meant you were crippled in terms of some root app functions (change dpi perhaps?) Not to mention limited flashing options...

Perhaps the argument is really the semantics of 'rooted'?
[Galaxy Note GT-N7000 General] musashiro:
dr.ketan said that that situation is partial root.. just flash LPY Cfroot on mobile odin..:D
[Galaxy Note GT-N7000 General] O_G:
Thread Cleaned​

I have removed some posts from this thread, please show each other some respect. There is no need to start a flame war, just report the offending post and move on. It will be dealt with be the moderation team.​