Database Develop

[Q] EMMC bug - Is it safe to factory reset ICS on LPQ UK rom?

I have heard a lot of talk about an emmc bug affecting stock Ice Cream Sandwich builds realeased by Samsung. THe general consensus seems to be that it is not safe to wipe/factory reset the stock Samsung ICS roms.
The question I have is do we know if the recent UK region ICS update (XXXLQ2) is affected by the emmc bug?
Can anyone confirm that if they factory reset after upgrading to LQ2 ICS that they bricked their phone or that it was a successfull wipe?
I can confirm that i have factory reset my phone successfullu after installing LQ2 update although my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
I look forward to your replies, i know there are geniuses on this forum who can enlighten us.

We wont know if its affected until someone reports a brick.
But I would guess its still affected by the emmc bug.

As Entropy says in his PSA:
"All ICS official releases for the Samsung Galaxy Note (GT-N7000) as of late May 2012 - This includes XXLPY, ZSLPF, and DXLP9, and future kernels should be assumed affected until further notice."

So the bug is in offical releases?
SO this bug is in the official releases that you can install via kies?
Will Samsung patch this bug?
Surely they must be aware of it since the number of bricks going to the service centers must be rising astronomically. If we are aware of it how can they not be when they have tested many devices at factory?

Better hold on to gb then rushing to ics with emmc bug. Wait for awhile until some one found a solution. Or else you will stuck like me with no gb backup to revert back.
Sent from my GT-N7000 using XDA

This is a XXLQ2 Brick I Guess.

Lol thats a total facepalm. But whats the cause of his brick? I couldnt read it all cause I laughed so hard that I got tears in my eyes.

JazonX said:
This is a XXLQ2 Brick I Guess.
Click to expand...
Click to collapse
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3

chasmodo said:
No, that brick was not caused by the LQ2 kernel; it happened because the guy had used an ancient updater script for his Rom.
http://forum.xda-developers.com/showpost.php?p=26951708&postcount=3
Click to expand...
Click to collapse
Yeah thats exactly what I thought. As I said, couldnt read it all.

Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?

I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.

Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.

Belfia said:
Well, you might aswell count on beeing affected. But if you dont need to factory reset then everytging is fine.
Click to expand...
Click to collapse
Cheers just hope i don't need to factory reset before a fix is sorted. Don't really want to go about changing roms as i like tw and like to keep my phones standard.

volvo940seturbo said:
I too have the LQ2 update and would also like to know if this is also affected by the brickbug i have not done a factory reset and currently have no issues with my phone. I do not intend on doing a factory reset until i know that Samsung have fixed the issue.
Click to expand...
Click to collapse
Run the "GotBrickBug" app by Chainfire under the Themes/Apps section and see what firmware you have.
More than likely the LQ2 ROM still has the faulty MMC_CAP_ERASE code because Samsung hasn't admitted to the problem at all yet.

dbreloaded said:
......my phone has problems caused by this update - random reboots, crashes to the homescreen, screen going black and buttons not responding etc. Could these problems be caused by the emmc bug?
Click to expand...
Click to collapse
I initially update by Kies to LQ2 and had random homescreen force close, black screen,green dots on the screen, apps freezing...etc. Done a factory reset, then downgraded to GB UK, factory reset again, downloaded the LQ2 Firmware via Check FUS PC version and flashed ICS LQ2 using ODIN PC and everything is running smooth. No bugs to report after more than 1 week.

rdosti said:
Contrary to beliefs I have had no issues on my Indian ROM ICS.
I believe it may have something more to do with custom kernels, etc rather than Stock firmware?
Click to expand...
Click to collapse
I'm afraid this is not correct! Its a bug in stock ICS kernels (or other ICS based kernels that are not specifically modified) that enable the eMMC erase command.
Some custom ICS based kernels now have this command disabled. But as for now, it is considered unsafe to flash or specifically full (data) wipe from any stock ICS ROM (some ICS ROMs do a full wipe when flashed!). It is still statistically a rare event, but the only way to be 100% sure safe is to flash from a GB based kernel, such as Abyss 4.2 kernel.
Samsung is working on a "fix" for the faulty firmware in the emmc chips but what this fix will be is unknown.
It has been reported that, unrooted, on a Stock ICS ROMS (and hence stock kernel) has super-bricked after doing a factory reset.
You may be able to do a full wipe/reset/custom ICS kernel ROM and not suffer any immediate ill effects but the bug can manifest itself at a later date.
If you really want to get the bug, the best way would be to fill up your internal memory, then do a factory wipe, rinse and repeat!
GB kernels don't use the erase command, so are totally safe.
So to summarise, it is not safe to factory reset on LQ2 UK rom! Samsung have not yet issued a fix!
EDIT: Wow, its even more complicated than above lol!
See here for updates and the first sign of a fix!
http://forum.xda-developers.com/showthread.php?t=1698977&page=14

Can my Galaxy Note be saved?

Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!

Were you on stock ICS when you did the wipe ?

Akiainavas said:
Were you on stock ICS when you did the wipe ?
Click to expand...
Click to collapse
Yes, downloaded via Kies.

I think you have fallen victim to the infamous eMMC "superbrick". Contact Samsung, they are well aware of this problem and will surely replace it for you as it's plaguing devices running their stock ICS. The problem is with their kernel and the eMMC chip to it doesnt even matter what were you trying to do.
When they do replace it - first, flash a GB rom via Odin, and then install CM9. CM9 kernel is safe and superbrick bug free. Whatever you do - never try doing a wipe/factory reset on stock Samsung ICS rom.

Akiainavas said:
I think you have fallen victim to the infamous eMMC "superbrick". Contact Samsung, they are well aware of this problem and will surely replace it for you as it's plaguing stock ICS devices. The problem is with their kernel and the eMMC chip to it doesnt even matter what were you trying to do.
When they do replace it - first, flash a GB rom via Odin, and then install CM9. CM9 kernel is safe and superbrick bug free. Whatever you do - never try doing a wipe/factory reset on stock Samsung ICS rom.
Click to expand...
Click to collapse
Yeah, I feared that was the case. The problem is, I now have the yellow warning triangle on bootup, and my "binary count" has increased to 9. Does this mean Samsung won't replace it?
if that's the case, is there any way to reset the binary count and remove the triangle in its current state?

You might try resetting the counter with a jig. I don't know if it will work in its state, but you may not have much to lose.
Sent from a guy on a buffalOOooo.

Generally - USB Jig is the only way to reset it on a bricked device.
There is one way other way though:
http://www.mediafire.com/?5bmrc6cf81w5mya
This kernel is supposed to reset binary counter, and many users reported that it actually did the trick - mind that this kernel also causes hard brick. It's a last effort for people whose devices are already bricked.
You nees to flash it via Odin, disconnect and go into recovery. At first boot you will still see the triangle - in the recovery, select reboot. Now the triangle should disappead, and binary counter should be set to "no".
Remember that this kernel causes a hard brick. Use it only if your device is already bricked and you intend to send it to Samsung. It will work only on ICS devices.

Akiainavas said:
Generally - USB Jig is the only way to reset it.
There is one way other way though:
http://www.mediafire.com/?5bmrc6cf81w5mya
This kernel is supposed to reset binary counter, and many users reported that it actually did the trick - mind that this kernel also causes hard brick. It's a last effort for people whose devices are already bricked.
You nees to flash it via Odin, disconnect and go into recovery. At first boot you will still see the triangle - in the recovery, select reboot. Now the triangle should disappead, and binary counter should be set to "no".
Remember that this kernel causes a hard brick. Use it only if your device is already bricked and you intend to send it to Samsung.
Click to expand...
Click to collapse
Thanks very much for your help. I really appreciate it.
So do you think it's worth contacting Samsung first - before trying to reset the binary - or do you think they'll refuse to replace it once they know I tried flashing an unsupported ROM?
Thanks again!

I think you might try contacting them first, just ask all the info you need without giving them the serial numbers - before you send the phone in. They might replace it anyway - they know very well it happens because of their defective kernel/emmc chip. Although i'm afraid they might find out and refuse to fix it for free.
If they turn you down, then flash the kernel and contact them again. If you're going to do it in person and they refuse cause they "remembered you" ( shocking, but it happens... ) then simply get a friend or family to bring them your phone.
Just say that Kies messed up your phone - they'll know what the problem is
Hope they'll get it fixed for you. Let us know how it went.

Akiainavas said:
I think you might try contacting them first, just ask all the info you need without giving them the serial numbers. They might replace it anyway - they know very well it happens because of their defective kernel/emmc chip.
If they turn you down, then flash the kernel and contact them again. If you're going to do it in person and they refuse cause they "remembered you" ( shocking, but it happens... ) then simply get a friend or family to bring them your phone.
Just say that Kies messed up your phone - they'll know what the problem is
Hope they'll get it fixed for you. Let us know how it went.
Click to expand...
Click to collapse
Okay, I'll do that. Thanks again for all the info! I'll let you know how I get on.

kill.i.an said:
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Click to expand...
Click to collapse
You may also try manual/adb repartition method described in here to revise your phone. cheers.

kill.i.an said:
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Click to expand...
Click to collapse
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium

forest1971 said:
You may also try manual/adb repartition method described in here to revise your phone. cheers.
Click to expand...
Click to collapse
Thanks!

JB calhoun said:
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Stock recovery? Where would I find that?
The problem is, I cannot flash any ROM. It just hangs during the "factoryfs" process in Odin. When I try to install stuff via ClockworkMod recovery, it fails. Sometimes I get an error like "cannot mount (or access) /system."

JB calhoun said:
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not true I'm afraid...
If you've damaged the eMMC chip:
- You can still get into recovery.
- You can still get into download mode.
If you did a factory reset on stock ICS kernel and can't flash "factoryfs" data because Odin gets stuck at this point, and repartitioning does not help - that's the "superbrick".
It happens because using data wipe on stock ICS kernel runs a format procedure which damages Note's defective eMMC chip. If it happened, repartitioning won't help as parts of the storage are corrupted and Odin simply cannot put data there. I seriosusly don't know how could Samsung not see that the format command introduced in ICS ( it was not present in GB, that's why GB kernels are safe ) damages the chip... didn't they test the software at all ?
Take a look here:
http://forum.xda-developers.com/showthread.php?p=28048062
This guy managed to recover his device, but what he's left with is Note with 3-4GB less storage, and remember that once the eMMC chip is damaged, it will never be completely reliable again.
Here's a guide on how to revive superbricked Note. Bear in mind it might not work though:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
It's still best to try and get it replaced though. If Samsung won't replace it for free - then try reviving it.

Akiainavas said:
Not true.
If you've damaged the eMMC chip:
You can still get into recovery.
You can still get into download mode.
If you did a factory reset on stock ICS kernel and can't flash "factoryfs" data because Odin gets stuck at this point, and repartitioning does not help - that's the "superbrick".
It happens because using data wipe on stock ICS kernel runs a format procedure which damages Note's defective eMMC chip. If it happened, repartitioning won't help as parts of the storage are corrupted and Odin simply cannot put data there.
Take a look here:
http://forum.xda-developers.com/showthread.php?p=28048062
This guy managed to recover his device, but what he's left with is Note with 3-4GB less storage, and remember that once the eMMC chip is damaged, it will never be completely reliable again.
Here's a guide on how to revive superbricked Note. Bear in mind it might not work though:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
It's still best to try and get it replaced though. If Samsung won't replace it for free - then try reviving it.
Click to expand...
Click to collapse
Yeah, I'm certainly going to speak to Samsung over the next few days. I'm going to wait a little while for my JIG to arrive and try to remove the binary count, then I'll give them a call. I don't see how they can refuse to replace it really —*it is their software that caused this (I think).
Keeping my fingers crossed.
Thanks for all the advice, guys.

kill.i.an said:
Yeah, I'm certainly going to speak to Samsung over the next few days. I'm going to wait a little while for my JIG to arrive and try to remove the binary count, then I'll give them a call. I don't see how they can refuse to replace it really —*it is their software that caused this (I think).
Keeping my fingers crossed.
Thanks for all the advice, guys.
Click to expand...
Click to collapse
JIG is probably the best thing to do. Clear the counter, get rid of triangle and send it in. As you said - it's Samsung's kernel that causes this, and they know it.
Good luck mate.

Okay, here's a surprise: Because I can still enter download and recovery mode, I decided I would try to reset the binary counter before my JIG gets here. So I downloaded the kernel from another thread, and it worked perfect. I then tried to flash the stock ICS ROM so that there was no evidence of another one, and this time it didn't get stuck on "factoryfm" in Odin.
So I now have a working Galaxy Note. I have no idea how that happened (maybe the PIT I flashed earlier kicked in), but it's working.
Now the question is, do I attempt to install CyanogenMod again, or should I just stick to a working Galaxy Note and be happy?

Stay with what you have.
Sent from my GT-N7000 using xda app-developers app

kill.i.an said:
Okay, here's a surprise: Because I can still enter download and recovery mode, I decided I would try to reset the binary counter before my JIG gets here. So I downloaded the kernel from another thread, and it worked perfect. I then tried to flash the stock ICS ROM so that there was no evidence of another one, and this time it didn't get stuck on "factoryfm" in Odin.
So I now have a working Galaxy Note. I have no idea how that happened (maybe the PIT I flashed earlier kicked in), but it's working.
Now the question is, do I attempt to install CyanogenMod again, or should I just stick to a working Galaxy Note and be happy?
Click to expand...
Click to collapse
How much capacity do you have on your internal storage? If it is less than 11GB you may have a damaged chip and just managed to unbrick it.
I think if you can flash GB with Odin you should be fine, and once you get to GB everything is (relatively) safe.
I had a similar problem when I was trying to flash GB from stock ICS using odin, it stuck at FactoryFS and I thought I had superbricked it, but it turns out I was using a dodgy USB cable and using a good USB cable I managed to flash GB again and recover it, and now I am using CM9 - Never going back to stock ICS after this.

[Q] Sorry folks - this is probably a dumb question

Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick

nickpb said:
Firmware: 2.2
Click to expand...
Click to collapse
It would be simpler just to connect it to KIES and let it update your ROM according to its specs without any worries, If it fails than you can chose latest ROM from here its based on region, so chose latest for your region
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

nickpb said:
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
Click to expand...
Click to collapse
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess

AlwaysDroid said:
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
Click to expand...
Click to collapse
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2

Hi.
I think if u be in GB ROMs , it's better , then go to new bases like ICS or JB slowly.

Hey I recommend you just to update it via Kies. You will probably get 2.3.6 GB Value Pack. Its pretty good, and stable, atleast for me. If you are not satisfied with preformace that you get with it, you can install custom kernel, such as semaphore, so it would get better,
If you lived with froyo till now, you wont need anything more than GB. And you can be sure about stability, good signal, no restarts and so on, that you can get on some custom ICS and JB roms...

snapper.fishes said:
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Sent from my GT-I9000 using xda premium

AlwaysDroid said:
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Click to expand...
Click to collapse
Please don't be misleading. CM10 is certainly good in it's own right, but there are quite a few things that are not working.
For instance, Google+ instant upload is completely non-functional because of an incomplete implementation in both the camera and gallery apps. This is clearly a rom problem.
The gallery app also has no settings. There is a menu option to access settings, and one would expect to see a settings screen similar to the one in CM9 when that settings menu is clicked. Instead the user is greeted with a blank screen.
Users need to be fully aware of what they are getting when choosing a rom and making statements like "it is almost perfect" is subjective and can be misleading.
Finally you say that CM10 has "almost no bugs" and then follow it with "... nothing" which is an obvious contradiction. Which is it, almost none, or absolutely none?

[Q] N7000 emmc bricked can now only run GB

Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers

You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app

ttibbetts83 said:
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks ttibbetts83, I will try that and see how i go

Thanks Arobase40.
I'll get a strong coffee and read your reply from top to bottom and then plan my next move.
The repair was done by people unrelated to Samsung.
I currently have GB v2.3.5, (SGN_XX_OXA_KJ1_FACTORYFS) which works well, it would seem.
I'd love to get ICS back on it but need to gather info (such as that from yourself) before I do anything.
A bit more info on the state of the emmc storage: Using 'adb shell' and executing the command DD did in fact find bad blocks in partitions 9-11 (can't recall right now exactly which ones), so there are issues there.
The partition that is in place now, __appears__ to have successfully skipped those bad blocks.
And on something slightly tangential to the current topic, I know that doing a 'WIPE DATA' from the recovery menu zaps emmc, but does that also happen when you do a factory reset from within Android? From memory, when doing so, it seems to go into recovery mode and do it, so I'd expect that it'd also damage emmc.
Cheers

arobase said:
As opposed to all alarmist and contradictory posts about eMMC bug on stock Samsung ROM : GB or ICS, I never got any issues with this so called eMMC bug and never got bricked G-Note as long as I kept at using the stock kernel, nevertheless I made various and numerous wipe whichever the ways (from recovery or the settings)...
For rooting, I always used the temporary Touch CWM to flash (which has been may be removed from XDA, I guess as it was supposed to cause bricked devices) anything : superuser, busybox, and other custom ROM... ^^
BUT when I flash a custom ROM, I always removed the custom kernel (so called "safe"), and replace it for a stock kernel and never got issues with it.
The first and last time I flashed a custom with custom kernel I got my G-Note bricked (just forgot the replace the custom kernel for a stock one... ^^) !!!
So, if you want to flash an ICS version, get one from Sammobile, and flash it with PC Odin !
You shouldn't have any problem with them !!!
Get all root and busybox files from dr Ketan, and if you can find it again use the temporary Touch CWM which has NO kernel inside : it WORKS quite fine !!!
Click to expand...
Click to collapse
Unfortunately there are no high trees on XDA beause you should look for one before typing this utter personal nonsense that could brick anybody's Gnote.
Taking your own convictions for thruth is one thing, sending innocent ppl into the jungle is another...
What you are saying is: If there is a lightning storm, just go into an open field en enjoy. I cannot say it is 100% safe, but I never got struck....I think they removed the tree i used to seek shelter from the rain, but if you search real hard you might find it anyway.
---------- Post added at 10:33 AM ---------- Previous post was at 10:17 AM ----------
amanmasgaman said:
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
Click to expand...
Click to collapse
Actually you should be happy that they revived your Note after brick even if it's only running GB for now.
However if you are a brave person you can do the same trick on ICS.
Just read and understand the thread that is a guide on doing so.
You can root your GB without a problem, but there is no obligation for it to install ICS with odin.
However what you do need is the following (besides a lot of patience and courage) :
1. get the ICS files you want to flash including the pit file.
2. get a program called PIT MAGIC to recreate a suitable pit file
3. determine where your bad blocks are located
4. Load the pit file into the magic program and alter the stock pit file
with the values needed to ommit your bad emmc area
5. save it and then flash your note in odin with your newly created pit file and repartition ticked.

@OP: could you please check your internal storage capacity? Is it aroung 8GB?

Arobase we are not going to rediscuss this matter for another 556643 pages.
Just ask yourself : if there was no problem then why did samsung patch their JB kernels for it. http://forum.xda-developers.com/showpost.php?p=34933643&postcount=683
Also nobody asks you to reconsider your own experience and beliefs, but the day someone follows your instructions and bricks his phone, are you going to pay for a new motherboard ?
I'll stop this discussion here, and just hope nobody will get struck under the tree.

[Q] eMMC brick Bug question

Hi Folks
Im a new proud owner of a Note, just got it today and loving it so far, waiting for JB in March though .
Ive checked and my Note has the "YES insane chip", however, i only flash Stock roms through odin and use Stock recovery after each flash, so am I right in reading that its only custom ROMS and Kernels that can brick it, so I never have to worry about it bricking or is there something i should be careful of when flashing stock roms as well.
Thanks

No, if you wipe your data through a factory reset there is a high chance in bricking the device.

XxPixX said:
No, if you wipe your data through a factory reset there is a high chance in bricking the device.
Click to expand...
Click to collapse
Oh.. wow, how can Sammy release hardware like this then, thats pretty bad. I take it the New S3s and Note 2s dont have thiese chips then.
Cheers

Samsung claims, that recent stock recoveries are safe, no one knows for sure if that's true.
If you want to be absolutely safe, use a recent custom kernel, those are known to be safe, since they completely disable the broken erase function.

guv. said:
Samsung claims, that recent stock recoveries are safe, no one knows for sure if that's true.
If you want to be absolutely safe, use a recent custom kernel, those are known to be safe, since they completely disable the broken erase function.
Click to expand...
Click to collapse
I did a factory reset > wipe Cache earlier and it booted ok thankfully. Im on UK XXLRK 404 (July 2012) so how recent do Samsung mean, but it seems to be on all 404 Roms (s2/Note), but thanks for the heads up... can I just say though that I would Never "Factory Reset" through Settings because im not sure if it wipes the cache or does much really, also the next and only update ill be doing will be JB 412 in March, if it arrives
Cheers

Can I just ask, when JB comes out in a few weeks, would you recommend to flash a safe kernel first, then update to JB.. or because Im Updating, should I just flash straight to stock JB in ODIN, then reset through Stock Recovery.
EDIT:
Also, Im new to this device so could anyone recommend a safe fast kernel to use with a stock 404 Rom.. Unrooted
Thanks

speedmod, Philz, hydracore.. all are safe
if you are not rooted then update via kies. or via odin.. dont do reset in stock recovery of ICS... or JB yet as not yet confirmed safe.. may be after the sources come out.. one of the devs can confirm it

I was trying my hands on ubuntu from paranoid, but flashed ics, and mistakely i didnt wipe anything before flashing,so i did wipe on ics kernel, so it was stuck on bootloop ,but i could enter recovery and download. so i first flashed philz kernel and did a wipe and downgraded to gb. So i want to know is this the emmc brick bug or a soft brick..

so if your phone is working you were lucky..

nokiamodeln91 said:
so if your phone is working you were lucky..
Click to expand...
Click to collapse
Ya my phone is working but what kind of brick was this. i have read about emmc brick bug but couldnt get what is it.

A soft brick
Sent from my GT-N7000 using Tapatalk 2