Related
thinking about going with the international note! I live in the US so there is no warranty for us here so i wanted some users honest opinion.. how hard is it to brick? and what should i definitely avoid especially after watching so many users brick with just that one kernal
samtruongg said:
thinking about going with the international note! I live in the US so there is no warranty for us here so i wanted some users honest opinion.. how hard is it to brick? and what should i definitely avoid especially after watching so many users brick with just that one kernal
Click to expand...
Click to collapse
what kernel?
Angelom? i think it was where it fried many users motherboards
hmm problem is a lot overclock their phones or undervolt it without testing it gradually and finding the sweet spot...flashing the kernels (custom) dont brick phones, mostly its the users (who dont bother to read and just do it)...if you are afraid to brick i guess you have to stick to stock...
Just avoid ICS until it is official. Then give a little time for custom ROMs to pop up based on the official version. You might even consider, as hard as it may be, not updating to the official ICS directly after it shows up. Give those with warranties enough time to try it out first and report stability.
great idea really appreciate it! any clue as to what is the best, stable gingerbread based rom is?
beestee said:
Just avoid ICS until it is official. Then give a little time for custom ROMs to pop up based on the official version. You might even consider, as hard as it may be, not updating to the official ICS directly after it shows up. Give those with warranties enough time to try it out first and report stability.
Click to expand...
Click to collapse
indeed...ive seen the posts...theres no ics kernel yet that is stable or proper for the note as of the moment as there is no kernel source release yet...and flashing into wrong phone versions will almost do the same
Sent from my GT-I9100 using Tapatalk
You can always consider getting a 3rd party insurance plan from Squaretrade or Ensquared. Some of the forum members with International Notes on here have either of those insurance plans. I'm looking into getting it myself (1 year plan) when I receive my Note from the 1saleaday.com promotion. Still hasn't shipped out as of the time of this posting . I figure 1 year insurance would be OK since I'm putting the phone on Straight Talk prepaid (thus saving roughly $50/month) instead of getting on AT&T's plan, which comes out to saving $600 in one year. After one year of insurance the phone breaks, dies, etc., the money I saved by going prepaid, I can use it to buy the same phone (can probably get a used Note at a cheap price after a year) or another phone, and by then the Galaxy Note 2 should be out.
Not meant to be a prick but 1daysales is pretty shaddy seller. Friend ordered some.gadget from them last year took him a month to get it just to find out it was a refurb
Sent from my GT-N7000 using Tapatalk
ICS does not cause any problems with actual bricking of the device. The only actual bricks I have found of this phone have come from flashing a touch version of the newest CWM...I was hit hard by this myself...and since I live in the US as well, I was forced to by an entirely new phone.
smalmagal said:
ICS does not cause any problems with actual bricking of the device. The only actual bricks I have found of this phone have come from flashing a touch version of the newest CWM...I was hit hard by this myself...and since I live in the US as well, I was forced to by an entirely new phone.
Click to expand...
Click to collapse
^ this is the number ONE thing i am trying to avoid!
You shouldn't have to worry, man. It was a freak thing. That's not to say something like this couldn't happen again, but tampering with any Android phone shouldn't cause you any trouble if you know what you're doing. Another phone was hit by the same CWM touch kernel issue as well...and there were plenty of bricks around as well. The Epic 4G, I think? It fried the internal memory (EMMC) and made the phone completely useless. It's called "The Monster" 'round these parts. ;-)
smalmagal said:
You shouldn't have to worry, man. It was a freak thing. That's not to say something like this couldn't happen again, but tampering with any Android phone shouldn't cause you any trouble if you know what you're doing. Another phone was hit by the same CWM touch kernel issue as well...and there were plenty of bricks around as well. The Epic 4G, I think? It fried the internal memory (EMMC) and made the phone completely useless. It's called "The Monster" 'round these parts. ;-)
Click to expand...
Click to collapse
a lot of note users had that issue as well...im new at the threads on note and they had warned me about it...any links on the discussions about the touch bricks?thanks
Sent from my GT-N7000 using Tapatalk
i bricked my N7000 tonight doing a wipe/flash off of LP6 leaked kernel
why do i think its LP6 kernel cause?
last night i used the same rom i was building and flashed it again tonight, straight away when i hit flash i knew something was wrong because no progress bar showed up, i gave it 10 minutes and still stuck, rebooted holding recovery button combo, screen went black and she was toast. no cwm, no download, no os boot, no pc connection.
either way its a goner, but the good news:
i am sending it back to the guy i bought it from and he will deal with samsung india for me and ship it back *no he wont scam me im not even worried about that
so i dont know how long it will take, but i hope you enjoy your selves and be safe!
JamieD81 said:
i bricked my N7000 tonight doing a wipe/flash off of LP6 leaked kernel
why do i think its LP6 kernel cause?
last night i used the same rom i was building and flashed it again tonight, straight away when i hit flash i knew something was wrong because no progress bar showed up, i gave it 10 minutes and still stuck, rebooted holding recovery button combo, screen went black and she was toast. no cwm, no download, no os boot, no pc connection.
either way its a goner, but the good news:
i am sending it back to the guy i bought it from and he will deal with samsung india for me and ship it back *no he wont scam me im not even worried about that
so i dont know how long it will take, but i hope you enjoy your selves and be safe!
Click to expand...
Click to collapse
As I wrote you I think people shouldn't flash LP6 or CM9 kernel because they are too heavy modified without kernel sources.
Sent from my GT-N7000 using Tapatalk
once again, im glad its not because of LPY..
dont misunderstand me, im not happy that you brick your device..
Sorry to hear that. I hope you get it back soon.
Sent from my GT-N7000 using xda premium
Damn its getting to the point of being insane the amount of bricks.
Neobuddy89 bricked his as well.
m3dd0g said:
As I wrote you I think people shouldn't flash LP6 or CM9 kernel because they are too heavy modified without kernel sources.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
this i agree with 100%, by the time i get my note back im sure kernel source will be out and custom kernels will be out that wont be any issue, atleast i hope thats the way it works out HAH should be a good month or 2 before i get it back though :\
antiochasylum said:
Damn its getting to the point of being insane the amount of bricks.
Neobuddy89 bricked his as well.
Click to expand...
Click to collapse
You see I have say this weeks ago don't flash. Sorry for my friend Neo...
Sent from my GT-N7000 using Tapatalk
Wow this is why dev is stalling.. so many big names are bricking..
Sent from my GT-N7000 using Tapatalk 2
Sorry to hear Jamie
RIP and condolences to your note so sorry to hear that
Sent from my GT-N7000 using Tapatalk 2
Hey Jamie that sucks dude but your lucky the guy will fix it for you !
Sent from my GT-N7000 using xda premium
Sorry to hear, hope to see you back soon.
Hope to see u back here soon dude.. Sorry for ur note loved ur rom.. Guess i'll be sticking with stock ics for now.. I darent touch it lol
Sent from my GT-N7000 using xda premium
One of the bigger names here, I remember you were the first dev. to release an ICS ROM... I hope everything goes well.
Sorry to hear it man. Jesus, our devs are dropping like flies
Sent from my GT-N7000 using XDA Premium HD app
Bad luck man. Hope to see you back soon.
I bricked my Note few days ago when wipe data from LP5, buy another new replacement mainboard, right now feel very afraid when flash a new ROM... may be brick again at any moment! Remember the same with Samsung Omnis before. I never have this issue with HTC. Waiting if HTC will release a new big s ame screen, will back to him. I beleave HTC is more carefully design theys phone, compare with Samsung.
Q2V said:
I bricked my Note few days ago when wipe data from LP5, buy another new replacement mainboard, right now feel very afraid when flash a new ROM... may be brick again at any moment! Remember the same with Samsung Omnis before. I never have this issue with HTC. Waiting if HTC will release a new big s ame screen, will back to him. I beleave HTC is more carefully design theys phone, compare with Samsung.
Click to expand...
Click to collapse
Have fun with locked bootloaders
it happens, we all take the risk's just being here so no reason for me to be upset
for now im a bb 9800 user which i think is even worse then bricking my phone! haha
phone goes out to india this week, hopefully have it back before july haha
I flashed LP5 and LP6 kernel and firmwares many times. Never got any problems. This is because I carefully follow instructions and I always know what I'm doing.
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
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
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Edit: here a link to the issue http://forum.xda-developers.com/showthread.php?t=2091045
Tapatalking on my n7000
msedek said:
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Tapatalking on my n7000
Click to expand...
Click to collapse
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Samsung :thumbdown: for that..
click THANKS BUTTON if I helped…
Recognized Distributor™
i know of a close relative with a white s3 , after two months of purchase the set stopped charging from wall socket, the charging worked with laptop ......since he had warranty he was told the motherboard needed replacement and he got that done. the back of it has a spider-like faint grey mark and he asks me if its cracked or what ....he doesnt want to go back to service centre and wont let me root it and he doesnt have patience for xda. he is on 411 still.
he didnt pay for it himself, doesnt have a job yet and its not a gift...pretty chaotic situation if u ask me !!
bloody money grubber *** *****. Poor quality control. There's still no permanent solution for N7000 emmc brick bug.
sepehrthegreat-iran said:
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Talk to him and make him read about it here
http://forum.xda-developers.com/showthread.php?t=2091045
Check if he have an affected device..
Tapatalking on my n7000
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
krivinash said:
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
msedek said:
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
Click to expand...
Click to collapse
The brick bug on the Note shouldn't be a problem anymore. Just flash the PhilZ kernel which gives you root without increasing the flash counter and you're Note is fixed. You can also download Chainfires got brick bug app.to see if your Note is affected at all. Or you download the brick bug app from the play store which does the same.
Sent from my revived Galaxy Note
N7000
My Samsung Galaxy Note is on JB Alliance Rom XXLSC Beta1.1 which comes with it's own kernel and I don't think PhilZ is supporting it, PhilZ and Alliance Cook had a minor misunderstanding/fallout, (I could be getting my Roms mixed up) I've flashed different Roms 10+ times. Started to worry reading threads on here so downloaded the eMMC Brickbug Check app. All's good here
Maybe you wiped on STOCK ICS KERNEL which is known to cause the Brickbug
click THANKS BUTTON if I helped…
Recognized Distributor™
Arobase40 said:
The brick bug on Note is just a legend... ^^
The only safe kernel I'm aware of is the stock one !
The sole time I flashed a non stock kernel I got my Note fully bricked !!!
Click to expand...
Click to collapse
Yeh you are right!so can you post a video wiping on your stock kernel???!!!
I really appreciate the job that Phil and other Devs are doing
Sent from my GT-N7000 using xda premium
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What you believe it's completely different from what's a FACT... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase formating .. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
msedek said:
What you believe it's completely different from what's a fact... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase commands.. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
Click to expand...
Click to collapse
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
<<do not,under any condition,I repeat do not wipe from your stock ICS recovery>>
sent from galaxy s4(testing dev edition) using xda premium
sepehrthegreat-iran said:
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
sent from galaxy s4(testing dev edition) using xda premium
Click to expand...
Click to collapse
I'm not disrespecting anyone.. Own experience it's bullcrap.. Software developing and electronics engineering its not popular believes or "experiences" everything its done by scientific methods, procedures and knowledge of how things works..
A clear example could be that an engine its build to reach [email protected] if you force the engine beyond that it will get damaged...
Now some people could force it to 160kph and maybe it will work some times.. But at some point it will break.. And you know this because engineers made the engine to work Max at those speeds and RPMs..
It's matter of design.. Not "experiences"
Tapatalking on my n7000
Its been reported that stock ICS is unsafe, since the day it was released, people know about it and avoid it, so anyone saying that it is safe is talking nonsense, if they wanna take the risk and brick their device then thats their choice.
Moving back on to the S3 chips, my GF has had hers several months now and luckily havent encountered any issues at all, I tend to only find device faults AFTER ive purchased them !! i really need to research more before buying
the S3 is 100% stock, my GF wont let me mod it but luckily the device has warranty for the lenght of the contract which is 24 months, so if it ever breaks within this time they'll just fix it for me free of charge
Still, it makes me wonder WTF are a giant company like Samsung doing about this issue ? SGS 2, SGS 3, SGN 1 (unsure about SGN2)
this isnt acceptable from Samsung, regardless if <5% of devices suffer this, I would expect sudden death and insane chips from a cheap chinese knock off, but not a £500 smart phone.
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
They knew about it. It was fixed in Galaxy Nexus eMMC firmware but yet they kept shipping other devices with the same firmware.
Cut the crap: Do you know more about the emmc brick bug than some elite and recognized devs here ?
qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Before ICS (gb and older) , Android used recursive deletion.. (no mmc_cap_erase procedures in the kernel).. Samsung didn't know about it because the chip was designed under another required process and there's no way to know this kind of things until you produce something in big scales.. As you said you could spend months wiping everyday on stock ICS and never get brick, but after 6 months of doing it the next day you brick...
Entropy went to samsung and he tried several times to brick a note in front of samsung engineers with no luck.. But the bug its there from the first ICS firmware to the very last and considering we are still officially on ICS, i dont think it's a "retro" information...
Exynos source has nothing to do with the emmc chip and what kind of delete/formating methods will damage it.. Heck even deleting big files (over 500 mb) could trigger the bug.
Once again you are talking nonsense
Tapatalking on my n7000