Database Users

plz vote ( are u with LPY ICS or going back to GB)

THERE IS ANOTHER POST AND POLL THIS IS REDUNDANT
~~~THREAD CLOSED~~~
plz vote ( are u with ICS or going back to GB)

There is already a post with this exact same question and a poll to answer.
Pointless waste of a thread.
On topic: LPY ICS !

Using stock ics latest update and ....hell no! No never gb for me. This rom is f!cking great. All i need now is a custom kernel(thats made with original sourses). No home made brick kernels with no wifi, black camera screen, buggy speaker.

updated to LPY two days ago... loving it so far...
wifi is good, battery life is good, no overheating problems...
The only 'complaint' i have is that it seems to be a bit of a memory hog... but i can wait for a strimmed down custom Rom based on this one to take care of that issue...
overall, pretty damn happy with it
M

Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now

just i want to know the no of bricked phones compared to all

ratcom said:
Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now
Click to expand...
Click to collapse
Considering what we've seen CM9, repacked i9220 kernel, or home made kernel has been the common denominator in every brick

Totally using official ics and loving it. ;-)
Sent from my GT-N7000 using XDA Premium HD app

Note_E said:
Considering what we've seen CM9 has been the common denominator in every brick
Click to expand...
Click to collapse
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?

If it ain' broken, DON'T FIX IT!!!
Zapped through server hops to XDA forums

sehooo said:
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?
Click to expand...
Click to collapse
Are you rooted with CWM?

Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?

Ueihtam said:
Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?
Click to expand...
Click to collapse
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to believe that source considering the amount of donations. I look at what's happening and the results of the numerous upgrades being flashed over the past few days to use that as an indicator. Until LPY kernel source is released and the experts can comb through it, there is no real answer. I don't use CM, it's just not my flavor...but I really mean no disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.

Note_E said:
Are you rooted with CWM?
Click to expand...
Click to collapse
just flashed LPY and not rooted till now

sehooo said:
just flashed LPY and not rooted till now
Click to expand...
Click to collapse
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged, but his home grown kernel is not, but all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering it's a source of donations.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
just i want to know no of bricked phones as there are alot of rumors and i read alot and didn't find the solution to get back to gb OR stay on LPY and go for root

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering the amount of donations. I don't use CM, it's just not my flavor...but I really mean not disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!

Note_E said:
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).
Click to expand...
Click to collapse
i got force close with some applications like youtube and applications which need root which i setuped before on rooted GB before upgrading

vetchems said:
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!
Click to expand...
Click to collapse
Correction: before "official" CM9 there was imilkas...which bricked many others. then there was xplod's donated device during kernel development which you can take that as you will.
My argument is valid...I'm using common denominators. But if you read my whole post, I said there is no real answer...so I'm not trying to be "right"...it's my opinion/observation

I moved back my sister phone to GB because of the brick issues in LPY ICS and high battery usage !
Sent from my GT-I9100 using Tapatalk

Soft/Hard brick on LPY - My theory of the cause

I am in no way an expert and what I am about to say could just make no sense. But after reading hundreds of posts on the subject I believe that ONE common pattern emerges. The brick is not really caused by a faulty wiping process of either CWM or Stock recovery. It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_

pakalrtb said:
I am in no way an expert and what I am about to say could just make no sense. But after reading hundreds of posts on the subject I believe that ONE common pattern emerges. The brick is not really caused by a faulty wiping process of either CWM or Stock recovery. It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_
Click to expand...
Click to collapse
like how? if its not a faulty wiping then why the faulty process combination? its the kernel source. samsung changed something to make it problematic with cwm. the rest of GB is fine. but since the leak of ICS and the latest official one, the problem persisted.

Ashren81 said:
like how? if its not a faulty wiping then why the faulty process combination? its the kernel source. samsung changed something to make it problematic with cwm. the rest of GB is fine. but since the leak of ICS and the latest official one, the problem persisted.
Click to expand...
Click to collapse
i think samsung changed kernel against cwm(as we know it is very popular) to brick phones thats how they would earn some extra money: from repairing, buying new phone. Just my opinion

EdgaBimbam said:
i think samsung changed kernel against cwm(as we know it is very popular) to brick phones thats how they would earn some extra money: from repairing, buying new phone. Just my opinion
Click to expand...
Click to collapse
i second that. just like how apple did to their baseband kernel every now and then to block jailbreaking.

Negative publicity would cost a lot more to samsung then the profit of selling/repairing less then 50 bricked phones worldwide, you guys should stop reading conspiracy novels

EdgaBimbam said:
i think samsung changed kernel against cwm(as we know it is very popular) to brick phones thats how they would earn some extra money: from repairing, buying new phone. Just my opinion
Click to expand...
Click to collapse
Except that stock recovery is also affected.
Nothing to do with the power button - just a broken MMC driver.

I believe this. Samsung will be generating more revenue this year.
There are thousands of users outside XDA who are waiting for OTA/Kies updates of their regions.
----
Probably my last samsung phone. Delayed and dangerous update.

friedje said:
Negative publicity would cost a lot more to samsung then the profit of selling/repairing less then 50 bricked phones worldwide, you guys should stop reading conspiracy novels
Click to expand...
Click to collapse
why dont u provide the community with a solution rather than publicising ur conspiracy theory.
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
Entropy512 said:
Except that stock recovery is also affected.
Nothing to do with the power button - just a broken MMC driver.
Click to expand...
Click to collapse
Stock recovery is also affected when u try to wipe a note with rooted/cwm kernel as far as I can tell. As long as it its stock virgin, no problem.

pakalrtb said:
I am in no way an expert and what I am about to say could just make no sense. But after reading hundreds of posts on the subject I believe that ONE common pattern emerges. The brick is not really caused by a faulty wiping process of either CWM or Stock recovery. It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_
Click to expand...
Click to collapse
150% FALSE
i dont touch the power button in recover ever, i use the menu-key/home-key/vol-keys
yet i still bricked my phone

Boy124 said:
I believe this. Samsung will be generating more revenue this year.
There are thousands of users outside XDA who are waiting for OTA/Kies updates of their regions.
----
Probably my last samsung phone. Delayed and dangerous update.
Click to expand...
Click to collapse
Most Notes are under some kind of warranty. If you believe that Samsung would brick phone intentionally to make $$ then I disagree with you in every way.

Intentionally or unintentionally... not everyone but hundreds of users will have pay for MoBos just because they flashed official ICS.
And 'you flashed it yourself' is NOT an excuse. It proves Samsung has poor quality control and testing, period.

pakalrtb said:
It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.
P_
Click to expand...
Click to collapse
I never ever touched anything during cache wipe in CWMR, and I still got the black brick.
So much for your little theory.

chasmodo said:
I never ever touched anything during cache wipe in CWMR, and I still got the black brick.
So much for your little theory.
Click to expand...
Click to collapse
Did you (at any earlier date) flash CM9 or a variant of CM9 on your note?
My theory/hypothesis is that these bricks are occurring when LPY is flashed on a note that has, or has previously had, CM9 or a variant flashed on it.
I am not sure that the ICS kernels themselves are actually faulty.

It's the cwm. Period. A lot of people call it a bug, i would assume it is a feature designed by sammy devs to avoid tinkering with their software.
I am on stock LPY and i did a data wipe via stock recovery.
Zapped through server hops to XDA forums

Isn't Samsung known to be one of the most dev friendly manufacturers? So why would they try to keep people from tinkering with it? As far as I can tell, they just made a mistake. Besides, I know it's cliche, but we all know that when you tinker with stuff you do so at your own risk. Our experiences with the Note should serve as a reminder of that.
Sent from my GT-N7000 using Tapatalk 2

clandestino123 said:
My theory/hypothesis is that these bricks are occurring when LPY is flashed on a note that has, or has previously had, CM9 or a variant flashed on it.
Click to expand...
Click to collapse
Very interesting theory ideed. Tell me, how does your pet theory cover at least half-dozen hard-bricks happening after upgrading from stock GB, rooting and then doing a wipe?
clandestino123 said:
I am not sure that the ICS kernels themselves are actually faulty.
Click to expand...
Click to collapse
I see.
____________________________________________________________
Entropy512:
These kernels are fundamentally dangerous. Samsung introduced some sort of bug in the eMMC driver that can permanently damage the eMMC flash storage of the phone.
Kernels that have been confirmed affected are:
XXLPY official ICS release for the GT-N7000 - At least one user has fully hardbricked and at least 2-3 others have "blown" /system or /data partitions - one of those was after wiping with stock recovery
____________________________________________________________
Chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
____________________________________________________________
These two are top-notch kernel developers, and they don't know what they are talking about? Get out of here....

chasmodo said:
Very interesting theory ideed. Tell me, how does your pet theory cover at least half-dozen hard-bricks happening after upgrading from stock GB, rooting and then doing a wipe?
I see.
____________________________________________________________
Entropy512:
These kernels are fundamentally dangerous. Samsung introduced some sort of bug in the eMMC driver that can permanently damage the eMMC flash storage of the phone.
Kernels that have been confirmed affected are:
XXLPY official ICS release for the GT-N7000 - At least one user has fully hardbricked and at least 2-3 others have "blown" /system or /data partitions - one of those was after wiping with stock recovery
____________________________________________________________
Chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
____________________________________________________________
These two are top-notch kernel developers, and they don't know what they are talking about? Get out of here....
Click to expand...
Click to collapse
Great but either way you make it worse. Its already been said and resaid...and stickied. This **** is getting so lame now

freedomispopular said:
Isn't Samsung known to be one of the most dev friendly manufacturers? So why would they try to keep people from tinkering with it? As far as I can tell, they just made a mistake. Besides, I know it's cliche, but we all know that when you tinker with stuff you do so at your own risk. Our experiences with the Note should serve as a reminder of that.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
+1 for this
Sent from my GT-N7000

Note_E said:
Great but either way you make it worse. Its already been said and resaid...and stickied. This **** is getting so lame now
Click to expand...
Click to collapse
Yes you are right. This is lame - until you brick your device.
What i really don't understand in all this discussions is the mistrust in Chainfire.
We all are more or less using his great work. almost every custom rom has it's roots in CF-Kernel.
Now Chainfire give a warning and people try to argue it away. What's that?
Same to Entropy...
It's a bit like not using safety belt in a car. In the most cases nothing happens....
Though I'm eagerly waiting for ICS - I'll wait for a new update from Sammy or a new statement from CF.
And yes, the discussions should be stopped. but there are new roms released and the risk is growing....

trahzebuck said:
And yes, the discussions should be stopped. but there are new roms released and the risk is growing....
Click to expand...
Click to collapse
as well as profit .... samsung

why sammy still roll out many new ics for many country if ics got kernel brick proble

share your idea, i not sure would i update my phone with safe or risk firmware

The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..

Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums

praetorius said:
Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
Virgins don't use Gnotes, they would be scared of something so big

friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
+1

vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
it's not true

friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
Good one lol
Elle est bonne celle la

friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
+1 that means you have to risk to get what you wanted.

vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
You should know that this isnt true... Brick with ICS stock have happened... no CWM involved at all.

I guess they depend on that OTA and Kies update are not Wipe upgrade so no one will have a problem. Still, it's not a good idea to give people a poisoned Ice Cream!

So far in my country (Singapore), I have not heard of super bricks on the local forums yet.
They warned about no cwm wipes though .
Closest so far was someone who softbricked at bootloader after OTA update, then WIPED and FACTORY RESET his phone, and failed too.
Saved by flashing ICS via Odin.
Time will tell over the weekend about this issue.

vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
WRONG. There are reported instances of people bricking in stock factory reset.

praetorius said:
Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
Is this true? I updated OTA and did a full wipe in stock recovery (how could I imagine that was risky?). Never flashed anything onto this Note before. Now, everything works (except for the heating and the poor battery life, due to wakelocks, i guess) but I'm scared to death, so i haven't even tried to go back to GB via pc odin.
Has anybody got a hard brick doing factory reset in a "virgin" Note??

oscarsalgar said:
Is this true? I updated OTA and did a full wipe in stock recovery (how could I imagine that was risky?). Never flashed anything onto this Note before. Now, everything works (except for the heating and the poor battery life, due to wakelocks, i guess) but I'm scared to death, so i haven't even tried to go back to GB via pc odin.
Has anybody got a hard brick doing factory reset in a "virgin" Note??
Click to expand...
Click to collapse
Seems to be lots of guess work going on. I have been checking my local forums, so far nothing out of the ordinary. Not sure about the other regions though.
The thing is that the bug has a probability of bricking your phone each time a wipe occurs, making it practically difficult to tell whether our OTAs are actually immune or we are being lucky thus far.

iihito702 said:
share your idea, i not sure would i update my phone with safe or risk firmware
Click to expand...
Click to collapse
Because its SAMSUNG
Slow (on updates)
Absurd (with end user policies)
Meaningless (this does not need an explanation)
Selfish and shameless (won't admit there's a bug)
Unreliable (isn't it?)
Neglected (end users are always neglected)
Garbage (garbage software on great hardware)
I hope this helps, OP.

Well I guess that Samsung are looking at it like this.
Problem nearly only occurs in CWM during wipe/reset so people effected are nearly "only" the ones that have moddified there phones. I dont think its because Samsung does not care about the "modding/developer" comunity but this is only a very small percent of the total number of customers who buy Note's.
Secondly.
As far as I have seen all official OTA roll-out have been non-wipe. Which mean most people will never wipe there phone. Even then out of these only a VERY few will actually have any problem and I guess Samsung will simply take those warrenty costs that might come from that.

Boy124 said:
Because its SAMSUNG
Slow (on updates)
Absurd (with end user policies)
Meaningless (this does not need an explanation)
Selfish and shameless (won't admit there's a bug)
Unreliable (isn't it?)
Neglected (end users are always neglected)
Garbage (garbage software on great hardware)
I hope this helps, OP.
Click to expand...
Click to collapse
Bahhh they all suck. I'm coming from all HTC and this phone to factory support ain't no different..
I remember the little game HTC played with us EVO users when they limited our fps to 30 and tried stroking us it was a limitation due to HDMI out or whatever..
Then someone here cracked it and they changed their tune.
At least we aren't dealing with locked boot loaders. All these companies suck so I buy the best hardware I can and run a cyanogenmod variant.
Sent from my GT-N7000

senectus said:
You should know that this isnt true... Brick with ICS stock have happened... no CWM involved at all.
Click to expand...
Click to collapse
Anyone you personally know who've experienced this?
Sent from my GT-N7000 using Tapatalk 2

Entropy512 said:
WRONG. There are reported instances of people bricking in stock factory reset.
Click to expand...
Click to collapse
Reported but never really confirmed. Could be just a case of user error.
Sent from my GT-N7000 using Tapatalk 2

Honestly, there have been a lot of "reported" bricks even before lpy came out due to user error. It's just now that it's being highlighted because a few hardcore flashers experienced it. I personally think it's being blown out of proportion. Just my opinion i'm a member of a lot of note forums with regular people who don't do hardcore stuff except flash stock roms and never do i see them posting that thier phones got bricked due to lpy or any stock ics roms released by samsung.
Sent from my GT-N7000 using Tapatalk 2

My Big blunder

What y'day i did was i thing biggest blunder ever i caused on android.
Here is story
My friend came to me to get update to ICS for his device SGS 2.
I have done lots of flashing/rooting so it was not a big task for me, just i have asked abt his device and i have downloaded require ICS ROM for his device.
I have flashed it with odin
it was failed.
I have retry again fail
Lost recovery as well download mode too.
I was confidient (N over smart)
used JIG to get into download mode
find out pit file and flashed it
find out boot loader and flashed it
Nothing nothing it was semi bricked
Downloaded GB ROM and flashed
Fail, here i exhausted
And ask my friend are you sure your device is i9100 and not the varient?
he : yes it is i9100G
ME : then wtf you said it is i9100 when i have asked you at starting of procedure
He: but you said digit is same, so i think 'G' have no meaning
Me : 'G' is same important as g-sp*t
Then i got perspirated, and badly searched for correct pit (Here really i can say Note forum is much organised)
after 2hrs of search i found correct pit N bootloader (i think bootloader is almost same) but it was abt 3am and battery was emptied
Again in morning managed battery and flashed correct pit
then stcok GB and then ICS
and phone wokeup after a full night of deep sleep But Now i need a good sleep. But thnx God at last everything is fine.
Moral :
Confidence is good to have, but over confidence can kill U
Never trust any person who is not enough sound, N always check urself before flashing/modding(Look before you leap!! perfectly said dennis )

Interesting and useful experience sharing! Thanks.

there's a lesson for us all in that tale Dr Ketan!
Look before you leap!!
dennis

wow~.... your friend nearly killed his device by withholding that tiny bit of info... lol
Glad to see you recovered it for him

That happened with me. When in december last year i got my sgs2 at that time i was not aware if there is i9100g is present in the market.
So for rooting purpose i had to download insecure kernel or an older rom.
I flashed a i9100 and was stuck at samsung logo.
After that i researched here about it and found out thelat samsung screwed me.

Nice,
Moral..... Don't bother to play with others device...

Thanks for sharing Dr,
And I learn my first root from ur thread...thanks a lot

brililant and scary story im pretty sure u wont repeat this when someone comes to you with a US Note

Never
Sent from my GT-N7000 using xda premium

My last phone was a galaxy Ace. On the Ace forum, there is lots of this due to people assuming the i etc, is the same version!
Sent from my GT-N7000 using Tapatalk

Moral of the story: don't trust friends to know ****.
Sent from my GT-N7000 using Tapatalk 2

What a great thread, sounds like you're a good mate as well, a lot of other people would of said, sorry, and bye!
Sent from my GT-N7000 using xda premium

doctors don't say "Sorry, Bye!".. they save lives.... and smartphones
never say never

dr.ketan said:
Then i got perspirated, and badly searched for correct pit (Here really i can say Note forum is much organised)
Click to expand...
Click to collapse
that be true ,when I had my s2 I found it hard to learn anything ,too much info all over the place .
here it's much easier to find what you're looking for
dr.ketan said:
And ask my friend are you sure your device is i9100 and not the varient?
he : yes it is i9100G
ME : then wtf you said it is i9100 when i have asked you at starting of procedure
He: but you said digit is same, so i think 'G' have no meaning
Confidence is good to have, but over confidence can kill U
Never trust any person who is not enough sound, N always check urself before flashing/modding(Look before you leap!! perfectly said dennis )
Click to expand...
Click to collapse
ermmm ...how did you miss the big 19100G below the samsung logo?! I'm sure I've seen a G variant before and it stated 19100G on boot.
anyway your story is a good reminder that even if you are a pro you need to double check everything
thanks for sharing

MR.change said:
ermmm ...how did you miss the big 19100G below the samsung logo?! I'm sure I've seen a G variant before and it stated 19100G on boot.
Click to expand...
Click to collapse
As i am used to do these stuff, I have swith off device N just put in download mode. yes there will be tiny letter on download mode screen too (first line), but really does we check it ever?

G

dr.ketan said:
As i am used to do these stuff, I have swith off device N just put in download mode. yes there will be tiny letter on download mode screen too (first line), but really does we check it ever?
Click to expand...
Click to collapse
I guess we should check it from now on.
to be honest I also made a mistake with my friend's S2 ,though not that big but still, I rooted and installed CM9 all the while talking about nandroid backup and that he shouldn't worry about loosing his stuff cause a nandroid restore will return them all
in the end he wanted to go back to GB ,so I rebooted into recovery and viola it hit me like a train that I forgot to make a nandroid backup in the first place lol.
mistakes do happen it seems ,but one should learn from them so as not to repeat them .

Well try to flash the software for engine of a ferrary on a fiat...
wwwrrrouuuuummmmmm or brick - that's the question.
Nothing is more funny than real life.

@Mr.Change
Ya once it mistake, but repeat of mistake is stupidity.
Though it was misunderstanding, but i believe it was my blunder, b'coz i shudn't have to rely on his answer. if he is sound then why wud he come to me for just flashing, thats why i cudn't sleep for half night.

I had similar situation, i ordered and payed a i9100, who came with the mail and my first look on the box?
"Hm what's with the G letter, what this means?!"
Google straight away - and guess what? Completly different as Samsung said improved phone but do i need G version? No, i dont cause i suspected that most of the custom roms will be build for original i9100.
I spand half of my day explainin a guy who sold me the phone that this isn't phone that i ordered!
At the end i asked: Do you have Galaxy Note? He said yes i do, excellent i'm coming to get it
So guys be careful when you're buyin or flashin phone

I just cant brick my phone - WARNING ON ODIN -

Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?

jeroen180 said:
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
Click to expand...
Click to collapse
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...

Well, it is a brick bug, so it is only a chance - not definitive. I have stock ICS infected with the bug, but haven't nor plan on flashing or anything like that so...

friedje said:
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Click to expand...
Click to collapse
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it

jeroen180 said:
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
Click to expand...
Click to collapse
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.

friedje said:
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
Click to expand...
Click to collapse
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.

pboesboes said:
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
Click to expand...
Click to collapse
Well the fact of having a dangerous chip is one of the conditions....
So if you don't have it then not ALL the conditions are met..
Believe me if all the conditions are met, it will brick, it"s not random.
Then, Jeroen stated that he tested with Chainfires app, and he does have the faulty chip.
Finally I haven't seen a Note in the wild yet that doesn't have a faulty chip.

I feel like the OP. Before I knew of the bug I flashed and wiped many times. But I only flash stock roms. I don't know if that helped or not.
Sent from my GT-N7000 using xda premium