Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.
I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?
gedster314 said:
I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?
Click to expand...
Click to collapse
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2
octavian90 said:
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Your right. Why don't you just give the guy razor blades and sleeping tablets even before he explains his issue.
Yes I'm new to the Note but I have brought back many phones back from the "BRICK".
Nothing works, I can't boot into download or recovery
Any ICS kernel based on the leaks seems to carry a danger of permanent damage to the eMMC.
So far the only safe Samsung ICS kernels seem to be those based on the I9100 update4 source base.
Well what would you recommend I do from here though? I want to get this fixed as soon as possible.
Check the end of stunner thread... Send it to mobile video review for jtag
Sent from my GT-N7000 using Tapatalk 2
every time i consider bumping to a Custom ICS I see a thread like this or some issue that is a showstopper for me.
I'm glad I haven't yet had ICS.
I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.
sutekidane said:
I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.
Click to expand...
Click to collapse
don't lower your hopes down, I've seen countless and numerous times of Bricked Notes being revived and restored thru JTAG. This process is the much low level process you can get of restoring your Note into it's normal process. I don't see why your Note can't be restored if it's done thru JTAG.
(Not unless you have a broken ICs or chipsets already, which contitutes a hardware failure and that's the time you may have to replace it.)
JTAG is trusted already and proven to restore almost all bricked Notes.
Just from my own experiences..
Cheers
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium
sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck
MrSlippyFist said:
sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck
Click to expand...
Click to collapse
Just installed 1 4.26... I would recommend you to try it...its on another level than beta 5 ...very smooth n stable
Sent from my GT-N7000 using xda premium
thebz1 said:
Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.
Click to expand...
Click to collapse
try to use jig bro maybe it will solve the gnote
Oh no...not another CWM touch recovery-esque fiasco. I thought we were over that? And, damn that sucks dude. I've been in your exact shoes. This is my second phone, and I currently use Stunner as my daily driver...so I'm a bit worried now!
androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
so why aren't the other roms running lp5 bricking the phone?
androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
No it's a specific problème of stunner... It happens...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Envoyé depuis mon GT-N7000 avec Tapatalk
thebz1 said:
Well what would you recommend I do from here though? I want to get this fixed as soon as possible.
Click to expand...
Click to collapse
do you have a JIG or the tools to create one by yourself ? this seems your only solution for now, anyway does your phone enter to boot animation or it just doesn't flick ?!
there isnt much any of us who had our phones bricked can do about, and yes it was a version of ics stunner that did the damage, i have a feeling its gonna be a motherboard replacement
Related
Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the stunner ics 4.5 beta showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Try taking out the battery for a few minutes, put it back again and try entering download mode again.
What's sky ics rom?
Sent from my GT-N7000 using Tapatalk
hey thanks for the reply, i've tried that already as well. no download mode working here.
itsjiffybruh said:
Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the sky ics showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Click to expand...
Click to collapse
hmmm try to pull down battery, put it back again, try to turn on download mode, do this several times if it wont help, try to charge phone and do same. goodluck
sorry, i meant stunner ics. got confused with sky ics cuz i just put that into my friends skyrocket.
You didnt follow the instructions ti install the rom so you now have a brick
Try pluggingn it top the pc , if you hear some noises on the pc then your noté is alive
Sent from my GT-N7000 using xda premium
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
thor2001 said:
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
Click to expand...
Click to collapse
Well, i was in CWM and then installed the rom then pressed restart phone on CWM menu. Went downstairs and when I came back it didn't turn on.
if it doesn't turn on at all is it a hard brick?
I ordered a usb jig from amazon for $7.00 and it will arrive tomorrow, I heard the usb jig only works on soft bricked phones though and since mines won't even turn on will there be any chance at all of it working?
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
itsjiffybruh said:
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
Click to expand...
Click to collapse
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
.Hell. said:
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
Click to expand...
Click to collapse
Ill definitely keep you guys updated. My usb jig isn't scheduled to arrive until monday so i might just try to go to the att store today and try to get a replacement.
siuming720 said:
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
how would they be able to test it if it doesn't even turn on?
hi try this not my work dont now if it works
Default Bricked Galaxy Note N7000 or Incorrect ROM Flash Easy Fix
Ok simple you won't see nothing on the screen because the bootloader is wrong.....
Just put the battery in then do following.
1. hold vol down+home+power for 15 seconds...
2. release then press volume up...
Note: Don't worry about seeing anything on the screen or any keys light
it will be blank this is because bootloader is incorrect
3. open odin you should see comxx in listed flash the original bootloader back
into phone this will/should resume visual display.
I have attached necessary files to resume
Load File in PDA NOT BOOTLOODER
4. Wait 10 seconds.. Remove Battery Then Boot Back into Bootloader following steps 1&2
5. finally flash Stock Rom to resume the whole phone to original state.
Hope That Helps......see hear for post http://forum.xda-developers.com/showthread.php?p=23052721#post23052721
Sent from my GT-N7000 using Tapatalk
thanks for the help. i read that on another post and already tried it. unfortunately its a no go.
Just came back from att center and they said that they couldn't replace it for me on the spot because they don't have the phone in stock since its a newer phone. I gotta call the number they gave me now.
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
itsjiffybruh said:
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
Click to expand...
Click to collapse
First of all I think It wouldnt have raised the binary counter and give triangle because you didnt use Odin to flash (Am I right?).
Second thing Thought it had given you a triangle since your phone is dead.
So they cant find that you flashed a custom kernel or the binary.
itsjiffybruh said:
how would they be able to test it if it doesn't even turn on?
Click to expand...
Click to collapse
Oh.. I didn't see you can't enter to cwm
Sent from my GT-N7000 using xda premium
On 22.4.2012 many people bricked their S2 while performing full wipe having Siyah kernel 3.1RC6.
What disappointed me is the update on development coming from developer in real hurry these days.
Developer need to test their development 1000 times before releasing it to users.
As a rule only we the user are responsible flashed kernel knowing the risk of RCs and BETAs.
We can't blame developer for this disaster.........
This thread is for those who bricked S2 and now are in process to recover their devices.
As a general habit, posts on bricked devices can be avoided easily by fan boys.
So now we need to help each other in the process of device recovery.
Please discuss here, what you are doing, any fix whether you found or not.
Thanks
Kachrukamble
kachrukamble said:
Yesterday many people bricked their S2 while performing full wipe having Siyah kernel 3.1RC6..
What disappointed me is the update on development coming from developer in real hurry these days.
Developer need to test their development 1000 times before releasing it to users
As a rule only we the user are responsible flashed kernel knowing the risk of RCs and BETAs.
We can't blame developer for this disaster, BUT.........
This thread is for those who bricked S2 and now are in process to recover their devices.
As a general habit, posts on bricked devices can be easily avoided by fan boys.
So now we need to help each other in the process of device recovery.
Please discuss here, what you are doing, any fix whether you found or not.
I will add Names for those who bricked S2 in OP
Thanks
Kachrukamble
Click to expand...
Click to collapse
Sad story bro. I know that feeling.
GM must be happy to hear that
Sent via my s2 monster
release candidate = not final = beta = not fully tested =still bugs = bricked = bug = because still beta= your own risk = your fault. Hope this helps.
Sent from my GT-I9100 using xda premium
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
RobinRichard said:
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
Click to expand...
Click to collapse
of course you can flash 3.1, it solves the issue. only the last updated rc6 had the problem. IF you are on rc6 better flash the updated kernel before doing any factory reset/data wipe to be in the safer side.
So did any one had a chance to solve it without going to service center??
bala_gamer said:
of course you can flash 3.1, it solves the issue. only the last updated rc6 had the problem. IF you are on rc6 better flash the updated kernel before doing any factory reset/data wipe to be in the safer side.
So did any one had a chance to solve it without going to service center??
Click to expand...
Click to collapse
What the hell happened? Efs cleared?
Gesendet von meinem GT-I9100 mit Tapatalk
I'm one of the "lucky" owners of a bricked-by-Siyah phone
I tried to flash a stock rom with odin but it doesn't work. I tried with:
- KI3, which is a 3-file-fw + .pit. The flash process hangs on data.img
- ILA2, which is a 1-file-fw. The flash with Odin is successful, but the phone can't boot and stays on the "Samsung Galaxy S2" screen all the time.
The only way to access recovery I found is to flash rogue recovery, but it can't mount internal sdcard so I can't flash anything
Ghost-of-the-Sun said:
I'm one of the "lucky" owners of a bricked-by-Siyah phone
I tried to flash a stock rom with odin but it doesn't work. I tried with:
- KI3, which is a 3-file-fw + .pit. The flash process hangs on data.img
- ILA2, which is a 1-file-fw. The flash with Odin is successful, but the phone can't boot and stays on the "Samsung Galaxy S2" screen all the time.
The only way to access recovery I found is to flash rogue recovery, but it can't mount internal sdcard so I can't flash anything
Click to expand...
Click to collapse
if you can access download mode, then you have many ways to recover your s2 without reaching SC
RobinRichard said:
Thanks for the info buddy. I'm in RC6 only. I was planning to do a full wipe and try out a ROM, and luckily I saw your post. Do let us know if you find a fix (for bricked phones). So can I just flash Siyah v3.1 and this problem will go away?
Click to expand...
Click to collapse
Happy to hear that you saved, many people didnt
Sent from my HTC EVO 3D X515m using Tapatalk
bala_gamer said:
if you can access download mode, then you have many ways to recover your s2 without reaching SC
Click to expand...
Click to collapse
Yes I can access it, but the internal sdcard is never mounted so I can't use my phone... I hope somebody will find and share a fix for this problem :-(
Unless the hardware is damaged, every full-bricked Galaxy S2 can be recovered witha J-tag repair.
If one does not have the hardware hardware to perform such a repair, he has to either purchase it or find somebody that has it nearby.
Ghost-of-the-Sun said:
Yes I can access it, but the internal sdcard is never mounted so I can't use my phone... I hope somebody will find and share a fix for this problem :-(
Click to expand...
Click to collapse
Did anyone try flashing a boot loader? Nothing to lose now really
Sent from my GT-I9100 using xda premium
Mine is bricked, partly due to me not reading the posts. I'm able to get into download mode, will have a play with Odin on the off chance something fixes it but I guess it's unlikely...
Ghost-of-the-Sun said:
Yes I can access it, but the internal sdcard is never mounted so I can't use my phone... I hope somebody will find and share a fix for this problem :-(
Click to expand...
Click to collapse
Try to enter 3e recovery and factory reset phone and see what happens mate. Wait for like 5 mins and if buttons light up ur good...
Gesendet von meinem GT-I9100 mit Tapatalk
Dang I'm on siyah rc6 still running, if I flash 3.1 or another kernel its safe right?
Its safe using cwm app
is CWM available at all on Siyah bricked mobiles?
bartoloandre98 said:
Dang I'm on siyah rc6 still running, if I flash 3.1 or another kernel its safe right?
Its safe using cwm app
Click to expand...
Click to collapse
flash immediately 3.1 without wipe
---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------
itchetrigr said:
is CWM available at all on Siyah bricked mobiles?
Click to expand...
Click to collapse
its available but working with errors because of the mount problem of some partitions.
itchetrigr said:
is CWM available at all on Siyah bricked mobiles?
Click to expand...
Click to collapse
Bricked means dead in this case, you can't do anything with dead piece..
Well this just reinforces my belief to stick with stock kernels.
To the people with bricked phones, hope you guys are able to unbrick it without too much pain!
Does anyone know how to find a jtag service in korea, seoul? my phone is fully bricked and i need it back asap ....
More info and source credits here, thanks to codeworkx https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB.
ATTENTION:
We've contacted Samsung about the problem where performing a mmc erase could hardbrick your phone (i9100, i9100g, n7000, m250 - MAG4FA, VYL00M, and KYL00M with firmware revision 0x19 // T989 and I727 with fw rev 0x12) if it's having a faulty emmc chip.
Read this thread for more informations about it: http://forum.xda-developers.com/showthread.php?t=1644364
They're working as hard as possible on a clean solution which will be ready soon.
Please be patient and try to not flash any leaked kernels or kernels based on sources where MMC_CAP_ERASE is present.
This app http://forum.xda-developers.com/showpost.php?p=27014974&postcount=1 can be used to identify if your phone is affected or not.
CM9 kernels are safe to flash.
Please share!
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Click to expand...
Click to collapse
New Clarifications by Entropy : http://forum.xda-developers.com/showpost.php?p=28416723&postcount=403 - Must Read.
To check whether your phone has the brick bug, download the Got Brickbug app from Chainfire: http://forum.xda-developers.com/showthread.php?t=1693704
Also do read the article on xda for more info.: http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
Nice!
That is a really good news after some time.
Sent from my GT-N7000 using Tapatalk 2
Good news!
Looking forward to see how Samsung solve this nightmare
Sent from my GT-N7000 using xda premium
How many time to fix this Samsung BUG? How maby people need ti brick our 600€? If samsung knows why no first before? Grrrrr...
All hard work its from XDA devs!!!! Thank you devs!!
Enviado desde mi GT-N7000 usando Tapatalk 2
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
nandihno said:
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Teamhacksung dev codeworkx been in touch with Sammy guys so its genuine news...check link in op
Sent from my GT-N7000 using xda premium
at least we now have some hope...hopefully...
So to be clear...
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
ripnetuk said:
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
Click to expand...
Click to collapse
Flashing is not the problem but wiping is
So if they release a new update then simply don't wipe on your ics but wipe only after you install the new update
If however you want to be extra careful like I am
Flash a gb rom via odin then wipe that then flash said ics update via Odin
Sent from my iPad using Tapatalk
While there have been brickage reports using either PC Odin or CWM, there have been none regarding Odin Mobile Pro. So, when I flashed back GB, I used Odin mobile Pro. Everything went smooth.
//troll mode activated
It's just like Microsoft patching windows vista
//troll mode off
This is a true victory for XDA developers!
My deepest respect for all of you guys :thumbup:!!
Are they releasing a fix for brickd phone or a prevention update?
blue_panther9_9 said:
Are they releasing a fix for brickd phone or a prevention update?
Click to expand...
Click to collapse
Prevention.
Sent from my GT-N7000 using xda premium
I really hope this mess will soon be over. Let's hope while they are resolving the brick bug they also take a look at the wakelock thing. Contrary to others I have encountered this problem very rarely (1 time so far). Nonetheless it would be nice to see a solution.
Sent from my Galaxy Note running ICS
Good news but given that we haven't seen ics roll out in all countries, who knows when this will get fixed.
Another thing that bugs me. Is there possibility that Samsung push the solution for this bug and carriers just ignore it and continue with pushing the infected ics?
I guess that all we need is just one good release and everyone can flash it.
Hope to see it soon.
Sent from my Samsung Galaxy Note using XDA app
ripnetuk said:
Can someone confirm the following is correct please?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
Click to expand...
Click to collapse
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
ashoksoft said:
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
Click to expand...
Click to collapse
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Just updated op too
This is great news! Many thanks to entropy and chasmodo and all who've worked on this and sacrificed for us!
Also thanls to those who took it seriously.
Sent from my GT-N7000 using xda premium
MOD Edit: I have removed this as it is potentially dangerous. Wiping on any current stock ICS kernel could potentially damage your device, just because you successfully completed the operation once, does not mean its safe. Please read the warnings properly, if you would of done this first time you would know what i have just explained.
This is totally irresponsible and stupid advice that you are givig(PLEASE IGNORE IT).You do not know yet if your device is damaged tho i am sure you will regret your decision at a later date.to go against the advice given by knowledgable devs is inept at the least
Sent from my GT-N7000 using xda app-developers app
Even you wipe cache and data with stock kernel, it doesn't happens everytime.
it occurs once in while, and no meaning for this kind of clue.
One more thing, if you wipe something you won't get error same time, this will reflect next time when you flash ROM, it stuck at certain point if last wipe caused damage to device.
I flashed crisko rom now and was succesful..so no errors..n to prove me i did the same on my frnds note n it workes evrytime....
Sent from my GT-N7000 using xda app-developers app
Just hopping this will be deleted soon. Even if you did 100 successful wipes that says nothing. If thousands of people flashing this way even one brick per thousand flashes would be a huge mess.
Gesendet von meinem GT-N7000 mit Tapatalk 2
Better To Stay Safe rather than taking chances.. Post here when ur device will be bricked.. C how it feels..
shivil.sahni said:
I flashed crisko rom now and was succesful..so no errors..n to prove me i did the same on my frnds note n it workes evrytime....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Really wish there was a "No thanks" button for ridiculous posts like this.
If you had even bothered to research this issue, you'd find that there are plenty of people who successfully wiped dozens of times on stock ICS kernels, yet still got bricked by their last wipe.
It might not happen the first time, it might not happen after 100 wipes, but that doesn't mean it won't happen, so the safest course of action is to use Abyss.
hit thanks if u find it intersting n useful
Click to expand...
Click to collapse
About as useful as a chocolate teapot!
Regards,
Dave
REPORTED
Im nt saybg dat u shud try dis u all shud be on safe side...i did dis test fr people who bychance flashed kingdroid or ny aroma rom on unsafe kernel n want to go back bt thinkinh dat it will brick shud nt panic and go ahead if not confident...i didnt hope i would get dese responses for a risk i did on my note fr others
Sent from my GT-N7000 using xda app-developers app
"
No need to go to abyss jst directly wipe frm aroma....hit thanks if u find it intersting n useful"
Taken from your first post. You are indeed advising an unsafe method. ..anyone new could quite easily brick their device after reading your post
Sent from my GT-N7000 using xda app-developers app
Thats the most idiotic thing I've ever heard. NO ICS kernel is 100% safe from the eMMC brick bug.
If you want to be safe, then only full wipe by using Abyss 4.2.
Maybe you already caused some bad blocks in your partition, and you just don't know it.
Also, your grammar is horrible to look at, it hurts my eyes
kaukassus said:
......Maybe you already caused some bad blocks in your partition, and you just don't know it.....
Click to expand...
Click to collapse
Indeed, I believe that's what happened to mine. After what has been written so much about on these forums, its just simply incredible we see an OP like we now have here.
Total BS. How on earth did the OP flash a ROM from stock recovery?
I would say stop dicking around and don't risk others' phones.
If you want to get thanked post something that makes sense.
There have been superbrick incidents on the latests Firmware as well.
Boy124 said:
Total BS. How on earth did the OP flash a ROM from stock recovery?
I would say stop dicking around and don't risk others' phones.
If you want to get thanked post something that makes sense.
There have been superbrick incidents on the latests Firmware as well.
Click to expand...
Click to collapse
He had CWM on it, but still on a stock kernel. He was dumb, and used an unsafe kernel to flash a ROM
shivil.sahni said:
I flashed crisko rom now and was succesful..so no errors..n to prove me i did the same on my frnds note n it workes evrytime....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
It seems you have not read any of the sricky notes & warnings pasted throughout the forum. Pls. do not misguide. You even risked your friends device. Pls. understand the seriousness of the situation & also convey the same to your friend.
? Has anyone actually figured out the 3rd factor in this emmc brick bug yet? Like to make it brick every single time? Like. Factor one is having faulty chip, factor 2 is wiping on unsafe kernel, and factor 3 the thing that makes it brick everytime cause there must be something else involved otherwise everyone that wiped would get bricked?
Thread Closed
I have removed this as it is potentially dangerous. Wiping on any current stock ICS kernel could potentially damage your device, just because you successfully completed the operation once, does not mean its safe. Please read the warnings properly, if you would of done this the first time you would know what i have just explained.
It was nice 8 months experience,just Super bricked my Note while perfotming a wipe with CWM,too bad couldnt claim the warrenty.
Thanks for everyone who helped me during this period,both Developers and Members.
Jack
Sorry for your phone man.
Btw which kernel were you using?
Boy124 said:
Sorry for your phone man.
Btw which kernel were you using?
Click to expand...
Click to collapse
German LRK DBT stock 4.0.4 and it was running fine no problems,just wiped it to test the Paranoid Android JB 4.1.1,which was actually the last thing it did.
I see. But you can't flash roms using stock recovery. Anyways it confirms the bug still exists.
What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.
jgaviota said:
What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.
Click to expand...
Click to collapse
Unfortunately doesnt boot up,just stuck on the Gt-7000 logo but the download screen works,however when try to flash with PC Odin stops at the factoryfs.img which after research discovered is a Superbrick symptom.
hagba said:
too bad couldnt claim the warrenty.
Click to expand...
Click to collapse
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.
Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877
YLNdroid said:
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.
Click to expand...
Click to collapse
First thing on monday,
dr.ketan said:
Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877
Click to expand...
Click to collapse
Dr.Ketan,
I have tried the PIT procedure,but its such a long and tedious process Im not sure will be able to make viable partition for normal usage.
However will see what Samsung does on Monday.
So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.
He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium
dr.ketan said:
He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I made a mistake of wiping twice from Settings under android in Indian Stock DDLP8 stock 4.0.3 but luckily never bricked. But now I take care not to. But do you think I may have caused damage in the first two wipes? I see no issues till now but just asked.
It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium
dr.ketan said:
It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have the affected emmc firmware VYLOOM 0x19. Its just that I turned out to be lucky. I dont believe Samsung would fix the Indian firmware (4.0.3) while the bug remains on the latest 4.0.4 ROMS. If there is a fix from Samsung, we Indians are the ones who usually get it last. But strangely, I havent heard of any superbricked Indian Notes in this forum.
satishp said:
So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.
Click to expand...
Click to collapse
I think Samsung's claim was that you won't get bricked if you stick to stock and don't root. I'm not saying that's true . Even seems unlikely since I think you can factory wipe from the settings without root, IIRC (memory's rusty, haven't been on a stock ROM for ages).
There were some bricks with CM10, but only from people who flashed from stock ICS or stock ICS based ROMs. Flashing from the safe ICS kernels seems to still be safe.
satishp said:
But strangely, I havent heard of any superbricked Indian Notes in this forum.
Click to expand...
Click to collapse
Maybe that's because Indians are careful enough to read the instructions before risking their device? I doubt it's because Indian Notes have had some special pixie dust sprinkled over them while they passed customs.
If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium
dr.ketan said:
If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2
Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.
msedek said:
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2
Click to expand...
Click to collapse
It says big files shudn't be deleted. Though frankly speaking i have not seen any case brick by that, though we cant ignore comments from recognised developer.
But wat best idea i found to manage file is
Connect device with PC as mass storage and manage files from PC explorer. I believe that is safe way.
hagba said:
Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.
Click to expand...
Click to collapse
That was your bad luck this time, otherwise both have same effect.