yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] volvo940seturbo:
As a galaxy note user and one that is not into the whole routing flashing thing, just wants to enjoy the phone and do my own thing, I find this whole emmc bug very frustrating, along with all the use this that or the other rom replies. All I want is information on what/if/when are Samsung going to do anything to resolve this issue. At first when I saw this thread, I thought I may get some insight as to what and when there maybe a solution from Samsung as I have some issues with my note that I feel could be cured by doing a factory reset, but this option seems to be still unavailable even after the latest 4.0.4 update, so I am left in a position of having no real solution other than maybe rooting yet that too seems unreliable solution, so all I want to see from this thread is genuine real information on the progress of the official fix to this issue.
[Galaxy Note GT-N7000 General] shoey63:
wrong thread
[Galaxy Note GT-N7000 General] straycat:
Taking in mind we talk about Samsung, sooooo... never and ever?
[Galaxy Note GT-N7000 General] PaulF8080:
Sorry to jump into the middle of topic. I was referred to this post by a Galaxy Note topic. I may be repeating something.

My question is if the EMMC is blank, won't the boot process look for another boot device? Why not make a bootable micro SD card and boot from that. Then make the eMMC bootable again.

FYI Very good eMMC partition build description(no efs). http://processors.wiki.ti.com/index.php/Android_gingerbread_eMMC_booting. I like Ti's eMMC doc because they don't have translate Korean->English.
[Galaxy Note GT-N7000 General] :
have you read any of this forum at all?
[Galaxy Note GT-N7000 General] PaulF8080:
This forum? I thought I explained why I may be asking a stupid question. I read the Note forums and somebody cross posted.
[Galaxy Note GT-N7000 General] satishp:
Sorry to be out of topic, but Samsung has apparently found a fix for the bugs on the Note and announced it today. Its the Note 2. Prove me wrong. This day seems to mark the end of the Note and Samsung will definitely move on and forget the Note. So we are all covered as long as we are in warranty. I myself bought a Note about 3 months ago and it is pointless for me to upgrade so soon. It makes me feel bad too. We can only hope for a fix as long as Entropy stays with his Note. Once he moves on to another device, we are back at the mercy of Samsung. :( People may bash me for commenting off-topic. But this may be the hard truth,
[Galaxy Note GT-N7000 General] chasmodo:
Consider yourself bashed for talking inanities.
[Galaxy Note GT-N7000 General] PoisonWolf:
Entropy is the one talking to the engineers, he is the one who has been coding kernels for a long time, he is the one with am actual degree related to the matter, and even Google's engineers have spoken about this.

do not be just a guy typing non-useful garbage behind your monitor like you represent all of a Samsung.

Seriously, let those who know what they are doing do what they are doing.
[Galaxy Note GT-N7000 General] friedje:
At least he learns fast :)

for the rest i think we can close back the thread until Entropy has news from Samsung, as all has been said and discussed before...
[Galaxy Note GT-N7000 General] reinbeau:
This question does not belong in this thread. Take it to your device Q&A section.

Sent from a state of Serendipity
[Galaxy Note GT-N7000 General] EhsanCh:
Is there any news if samsung published a way to fix bricked phones ?
[Galaxy Note GT-N7000 General] willstay:
I said Samsung is NOT working on EMMC brick bug and my post got deleted? Nice moderation!!

Sent from GNote.
[Galaxy Note GT-N7000 General] Spiralzz:
Probably because you contradicted the title of this thread...
[Galaxy Note GT-N7000 General] willstay:
I don't need to contradict. Time has. This thread is almost 3 months old. Usually by this time, Samsung can create a new version TW.
[Galaxy Note GT-N7000 General] bongski55:
I don't think Samsung has any interest in solving or remedying this bug. After all how many Galaxy Series owners do a "recovery", flash a ROM,etc that can trigger this bug? Very minimal number I think from the 10 million.

My attitude towards this bug is- if Samsung provides a solution thanks you if not then I am not losing sleep over it.
[Galaxy Note GT-N7000 General] thez3ro:
I think samsung will remove the bug in the next official software release, that will be jelly bean... ;)

That is why its taking so long :)
[Galaxy Note GT-N7000 General] ilanifer:
hello, i have a bricked emmc, does anyone know if there's a way to replace the emmc chip ?

i have a friend who is expert in soldering elctronic circuits - could it be helpful ?
[Galaxy Note GT-N7000 General] Mario1968:
Hi, in the Samsung repair center they simply change the motherboard for this issue not only the chip, then I think is very expensive to buy the chip and change it by a qualified personnel:(

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1.2

Jkay V14.1
[Galaxy Note GT-N7000 General] PaulF8080:
When I found a bad chip while working on a PC motherboard line, the expert used a very expensive surface mount machine. The new chip had an array of tiny solder balls that he aligned to the motherboard with a microscope and an x-y positioning table.
[Galaxy Note GT-N7000 General] friedje:
unfortunatly just changing the chip won't be enough.

After having it replaced you would need a jtag to program

the bootloader into it.
[Galaxy Note GT-N7000 General] PaulF8080:
You seem to understand the boot process. Could you explain why you can't boot from a bootable SD or USB with OTG when the eMMC is empty. That is what they do on the Nook.
[Galaxy Note GT-N7000 General] :
Why is there so much rediculousness here...

sent from a kindle fire on cm 9
[Galaxy Note GT-N7000 General] friedje:
You can read up on it in the following thread :

http://xdaforums.com/showthread.php?t=1313588&page=11

Or check the odroid pages at hardkernel.com.

they have a developer board using the same soc as the g-note.
[Galaxy Note GT-N7000 General] dekelm8:
JTAG emmc

There is anyway that i can get the files to write on the emmc with JTAG ???

I have the JTAG box (riffbox), and they saying on their website that the box are supporting writing emmc to N7000 Models.

So anyone have any idea how i can rewrite me emmc chip?

Thanks.
[Galaxy Note GT-N7000 General] friedje:
Hint : http://xdaforums.com/showthread.php?t=1424997 :angel:
[Galaxy Note GT-N7000 General] Entropy512:
Because the CPU will only boot signed code. Effectively, our first-stage bootloader (IROM) is locked to only boot signed PBLs. We're lucky in that our SBL doesn't do signing checks of the kernel (fully locked bootloader).

As a result, we ONLY have the ability to boot from the eMMC itself. We don't have a USB-bootable or SD-bootable PBL like the one that was leaked for Hummingbird devices to make Unbrickable mod work.

If you have a clean eMMC chip (no damage), JTAG will work.

How expert? Can he desolder and resolder a fine-pitch BGA chip without damaging anything nearby? I'm not talking Xbox reflow repairs here - reflowing a chip without removing it is MUCH easier than remove-and-replace.

Getting a proper replacement chip will be extremely difficult, properly soldering it on will be nearly impossible.

I got news from my contact that they have submitted a patch to mainline Linux to protect devices - I was out of town most of last week so I'm going to ask how we can verify which Samsung kernels have had that protection method backported. https://lkml.org/lkml/2012/8/17/54
[Galaxy Note GT-N7000 General] Mario1968:
Hi Entropy512, thanks for the explanations, but this PBL could works if it is placed on another place (USB, OTG, SD)? And then it can find the SBL if not resides on MMC?

Sorry for the noob question

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1.2

Jkay V14.1
[Galaxy Note GT-N7000 General] garwynn:
Hallelujah! They

finally

decided to add a fixup to handle these cases!

We've got builds in progress for our phones so I'll start checking code releases after 8/17 and advise if I see the fix in there. (*Edit* Scratch that, kernel is from 7/31. Will keep checking as we're supposed to see JB builds as early as this month.)

Also looks like the time spent on this will end up being worth it in the end - having the materials like the eMMC specs I hope gave enough ammo to finally sway their opinion.

I just wish it wouldn't have taken so danged long for them to accept what was being said and patch it. About a day's dev work (and then applying the code change to all the various kernels) instead of the headaches and the problem will now be avoided.

Will have to keep an eye and see when this makes it to AOSP as well - that will effectively resolve it for builds like CM10/AOKP without having the current workaround.

Will keep you advised.
[Galaxy Note GT-N7000 General] PaulF8080:
I guess I am a noob here, but I saw my first bootstrap code in 1970. I could see it because it was implemented with discreet diodes. I have the same question. Couldn't someone make a full image of the eMMC(encryption and all) using Linux dd?
[Galaxy Note GT-N7000 General] Entropy512:
No... If there were a way to boot from alternate sources on Exynos 4210 devices, Rebellos and AdamOutler would've brought us Unbrickable Mod by now.

While I'm not sure if the PBL does signature checks of anything later in the chain (IBL, SBL), it IS hardcoded to only boot later stages (IBL, SBL) from eMMC. Since the CPU performs signature checks of the PBL, it can't be modified to boot IBL/SBL from elsewhere. :(
[Galaxy Note GT-N7000 General] Eric-Mod:
Is there something New? :cowboy:

I can't wait to get my 8GB back :D
[Galaxy Note GT-N7000 General] Pika007:
Aside from fixing already-bricked devices, what about brick protection?

Anyone knows if the new LRQ has the trigger removed?
[Galaxy Note GT-N7000 General] zhoudxnz:
Just out of curiosity I opened the file boot.bin in a stock rom with a hex editor.

Looks like the file has 3 parts. (my purely guess)

0-0x1FFF (8k): It has text "SB20_CONTEXT" (secure boot 20 context) at the end. Is this BL0_stage1? already signed by Samsung?

0x2000-0x2F4F + padding zeros: this part has more text, like "Ibl: pbl_read_emmc441() read 8k" Looks like this is IBL, hard coded to read PBL from emmc.

0x8000-0xD55F: this is PBL, because I can see "Welcome to Samsung Primitive Bootloader...".

If the first 8k has Samsung's signature, the CPU should be happy to accept it. Then what we need is a custom IBL that can read PBL from somewhere else other than the doomed emmc. Does it make sense to you?:rolleyes:
[Galaxy Note GT-N7000 General] MR.change:
I'm running it right now, and while there is no way to tell, I can bet you that the bug is still there.

Maybe with the newer JB builds? When they update the kernel version to 3.4
[Galaxy Note GT-N7000 General] shoey63:
@ Entropy. Managed to sign Speedmod kernel so it can be flashed from stock ICS 3e recovery . Dr. Ketan wants to put it into his rooting guide with your approval (still waiting for Hardcore to get his permission). Do you envisage any problems?
[Galaxy Note GT-N7000 General] dekelm8:
Did you know where i can buy the emmc chip? or what is symbolic name? did 'SANDISK" still producing the flashes for samaung (if yes i can get one, my friend work in SANDISK)???

please if anyone knows any of my question please answer... :)
[Galaxy Note GT-N7000 General] :
How about read the forum...rediculous post
[Galaxy Note GT-N7000 General] dekelm8:
I read it, but you don't expect from me to read all the 58 pages right?:p
[Galaxy Note GT-N7000 General] SpyderTracks:
Read them all then read again until you understand it.
[Galaxy Note GT-N7000 General] :
the chip is non removable. Apperently its soldered down onto board. So it is not as easy as sliding a new sd card in.
[Galaxy Note GT-N7000 General] Entropy512:
I'd need to talk with Rebellos again, but I'm fairly certain the IBL chunk is also signature-checked. Either that or the pre-IBL stuff that is signed is hardcoded to go to the eMMC for the IBL. I don't remember exactly, but that's the problem:

We only have signed components that are hardcoded to go to eMMC - so we could possibly USB-bootload the signed component, but then it would go and try to boot an IBL or (if IBL is also signed) PBL from eMMC.

That should work OK.

I'm going to try applying Samsung's patch to a test kernel to see if it's possible to check the compiled image for the patch by looking for all the chipid strings later this week.
[Galaxy Note GT-N7000 General] zhoudxnz:
I found something about usb boot. It was committed by Samsung for their EXYNOS5 chips, but it may apply to EXYNOS4 as well. (Read some comments by a Samsung developer in the source code saying EXYNOS4 and 5 have the same OM pins layout. But couldn't find the link anymore.) Anyway, according to this piece of code, seems like usb_boot is a special case which might not depend on OM pin configuration.

Rather it is enabled by a register EXYNOS_IRAM_SECONDARY_BASE = 0x02020018. No idea about what heck that is. But someone else may know. Being a noob about git, I couldn't figure out a way to pull out code around to have a better look. Maybe you guys can get some insight. Thanks. :)

https://gerrit.chromium.org/gerrit/#/c/16388/8/arch/arm/include/asm/arch-exynos/cpu.h

32	/* Address of address of function that copys data through USB */
33	#define EXYNOS_COPY_USB_FNPTR_ADDR» 0x02020070
34
35	/* Boot mode values */
36	#define EXYNOS_USB_SECONDARY_BOOT» 0xfeed0002
37
38	#define EXYNOS_IRAM_SECONDARY_BASE» 0x02020018

https://gerrit.chromium.org/gerrit/#/c/23348/3/arch/arm/cpu/armv7/exynos-common/spl_boot.c

/* Copy U-Boot image to RAM */
static void copy_uboot_to_ram(void)
{
unsigned int sec_boot_check;
unsigned int uboot_size;
int is_cr_z_set;
enum boot_mode boot_mode;
mmc_copy_func_t mmc_copy;

#if defined(CONFIG_EXYNOS_SPI_BOOT)
spi_copy_func_t spi_copy;
#endif
usb_copy_func_t usb_copy;

uboot_size = exynos_get_uboot_size();
boot_mode = exynos_get_boot_device();

if (boot_mode == BOOT_MODE_OM) {
/* Read iRAM location to check for secondary USB boot mode */
sec_boot_check = readl(EXYNOS_IRAM_SECONDARY_BASE);
if (sec_boot_check == EXYNOS_USB_SECONDARY_BOOT)
boot_mode = BOOT_MODE_USB;
}
debug("U-Boot size %u\n", uboot_size);

if (boot_mode == BOOT_MODE_OM)
boot_mode = readl(EXYNOS_POWER_BASE) & OM_STAT;

switch (boot_mode) {
#if defined(CONFIG_EXYNOS_SPI_BOOT)
case BOOT_MODE_SERIAL:
spi_copy = *(spi_copy_func_t *)EXYNOS_COPY_SPI_FNPTR_ADDR;
spi_copy(SPI_FLASH_UBOOT_POS, uboot_size,
CONFIG_SYS_TEXT_BASE);
break;
#endif
case BOOT_MODE_MMC:
mmc_copy = *(mmc_copy_func_t *)EXYNOS_COPY_MMC_FNPTR_ADDR;
assert(!(uboot_size & 511));
mmc_copy(BL2_START_OFFSET, uboot_size / 512,
CONFIG_SYS_TEXT_BASE);
break;
case BOOT_MODE_USB:
/*
* iROM needs program flow prediction to be disabled
* before copy from USB device to RAM
*/
is_cr_z_set = config_branch_prediction(0);
usb_copy = *(usb_copy_func_t *)
EXYNOS_COPY_USB_FNPTR_ADDR;
usb_copy();
config_branch_prediction(is_cr_z_set);
break;
default:
panic("Invalid boot mode selection\n");
break;
}
debug("U-Boot copied\n");
}
[Galaxy Note GT-N7000 General] Sadra.imam:
I confirm this.i just flashed my phone several times before and today and wipe cache from recovery and everything.

No brickbug. Flash counter or anything else.

The phone have stock ics rom. No mods. Rooted. Unlock.

LRI MAX Austria

Fresh one.2 weeks old

Moderator EDIT:

THIS IS NOT A FACT, BRICKBUG CAN HAPPEN AT ANY MOMENT.
[Galaxy Note GT-N7000 General] :
I dont understand why people are unable to read. You put yourself at great risk for hard bricking your phone if you are on a particular chip. Just because it didn't happen that time, doesn't mean it won't happen. Furthermore, you may have have a corrupt partition.
[Galaxy Note GT-N7000 General] Sadra.imam:
Actualy im able to read.thank you.....

And if i didnt knew the risk why would i post comment here!

Anyway.....
[Galaxy Note GT-N7000 General] porcusor:
Please please keep this clean. Some of us are waiting for updates from developers and you are only cluttering this thread with junk! Please read the entire thread and if you understand every word and if you have something usefull to add, then by all means do.

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] jetmarc:
I do embedded programming, but not on EXYNOS chips. My understanding of the code is the following:

The boot_mode can be forced by the calling code (which is not included in the snippet). If it is BOOT_MODE_OM, then the external pins are used to actually select the bootmode. Apparently this is the case on some Samsung phones (see "unbrickable mod" thread). However, it may or may not be the case on the N7000. As said, it depends on the calling code.

If it is BOOT_MODE_OM, *and* the RAM variable is set to FEED0002, then the pins are ignored and USB boot is possible. Googling for FEED0002 suggests that it is used for the 2nd attempt to boot, presumably after a failed 1st attempt. This must be done in the calling code, which -again- I can't inspect.

We can test if BOOT_MODE_OM is selected, simply by changing the pins and verifying that it fails to boot. If it would still boot from EMMC, then all further stuff is futile.

In the favourable case of BOOT_MODE_OM, where simply the pins are difficult to access, there is a chance that calling code does indeed retry with FEED0002 after a failed attempt. This could be help on a device where the EMMC is damaged enough for the 1st boot to fail. In this scenario it is perfectly possible that a good N7000 cannot boot from USB, but a defective one can.

Unfortunately it is equally possible that the ROM code does not include timeouts for EMMC reading. In that case, the 1st attempt would never finish and thus the system would never reach the 2nd attempt. Also, if the 2nd attempt is reached after an EMMC failure due to the damage discussed in this thread, it's probably not possible to repair it anyway because it must be recovered with a reset first.

These particular problems could be avoided by inducing a temporary fault in the EMMC communication, making the 1st attempt fail without actually reading from the memory array. This would be a hardware attack though.

So, for a pure software boot we would need (too) many conditions to be true:

- BOOT_MODE_OM issued from calling code

- 2nd attempt performed by calling code

- first bootloader in EMMC damaged

- but not damaged enough to "lock" the EMMC (requiring powercycle)

Quite unlikely...
[Galaxy Note GT-N7000 General] dekelm8:
I know that regular user cannot replace it in home, but i worked in cellphones lab for 8 years.

anyway i purchased the emmc chip over the net (around 70euro), and flash it with my riffbox.

Now is work like a charm, all the 16GB just like new. :):):):):):):):):):):):):):):):):)

Thanks anyway to all the forum about the info...
[Galaxy Note GT-N7000 General] SpyderTracks:
Any chance you'd be willing to make a video and let us know the source for the chip? Good job, mate :D
[Galaxy Note GT-N7000 General] :
+1

A tutorial of this would help many people
[Galaxy Note GT-N7000 General] Mario1968:
Please share the source of the chip and the necessary tools to achieve this fix

Anyway good job!

Mario

Inviato dal mio Galaxy S2 con Tapatalk2®

XWLPF Stock

Siyah 4.1.4

Jkay V14.1
[Galaxy Note GT-N7000 General] dekelm8:
Whats exactly you need?

i'll make later photo of the chip on the board + give you link to some online store that you can purchase it.

About the tools:

1. compatible tools for replacing the chip (is BGA chip, and it's mean that you're not able to see the solder balls, need special tool for do it in safe way).

2. RIFFBOX (or other box that can write JTAG to N7000).

* all the files you need you will get in the JTAG box you have on their website (for ressurection and boot ).

if have any question fell free to ask.
[Galaxy Note GT-N7000 General] Entropy512:
Some of what you mentioned above is consistent with stuff Rebellos has discussed with me - If the default boot sequence completely fails, it will default to USB booting. However, if the CPU even starts going down a valid bootloader chain, it won't transfer to the backup even if the beginning of the chain is valid but rapidly hits a dead end. For example if IBL+PBL are intact but SBL is gone (which seems to be the case in many Superbricks that were triggered when wiping /system), the CPU will see a valid IBL+PBL, start down that path, and the IBL+PBL will just hang.

Even if you do get into USB mode, whether due to the "fallback" method or diddling with the xOM pins (Remember that contest a few months ago where XDA gave away a few free Galaxy S2 units? AdamOutler was the #1 winner and immediately started poking at the xOM pins. I think the unit survived about two weeks before suffering permanent damage, but MUCH was learned about I9100/I777/N7000 xOM configuration in the process.), the problem is that the CPU does signature checks of the beginning of the chain, and by the time the signature checks end, you've been forced down a path involving eMMC booting.

You probably would have gotten more favorable responses if you'd indicated before you have BGA replacement experience. :)

I'm surprised you were able to find a replacement chip from someone willing to sell in single quantities.
[Galaxy Note GT-N7000 General] PaulF8080:
I asked the question about USB booting after someone said there was an unreleased tool that could fix the bad sectors by clearing the eMMC. The tool wasn't released because the only way to flash was with JTAG. I just wondered if the boot sequence would move on to the next possible boot device, like PC's do.
[Galaxy Note GT-N7000 General] dekelm8:
This is just one link that i found on the way home...

http://www.suppliesnow.nl/english-product-1108-000424.htm

but i'll let you know about one more website were i get my from, and i think is the lowest price over the net something around 40€ if i'm not wrong, i just need be in the LAB again to see where we order it from.

* i checked it and I'm in 90% sure we get it from here: http://www.aswo-elektronik.hr/eng/index.html

** you need to register to order it **

if anyone want to learn how to work with that kind of chip, I'm think on YOUTUBE you can find tutorial about working with FBGA

The exactly kind of the chip is FBGA and not regular BGA... (but i think the different between both is just size or something like that, regular BGA skills should be enough... :)

Any question that i can help about i'll do so :)

Good Luck Guys.
[Galaxy Note GT-N7000 General] abhijit038:
Well, I have tried every stock ICS ROM released so far.I have done wiping on each of them for at least about 3-4 times. Actually, I always find myself reverting to ZSLPF, for it seems to have best colour rendering and sound quality.Every time I flash new ROM I tend to wipe.

Perhaps I'd do what you want if Samsung releases something better than this.
[Galaxy Note GT-N7000 General] letters_to_cleo:
^^ we'll it would be good if you can simulate it 10x (for the sake of deliberation) and don't limit on stock ICS only.. how bout CM9 as well?. Have you tried that also?

Stick to what you said to fully wipe your device more than 3-4 times. You said it for yourself, it needs a careful and methodical way of testing it.

10x doing a full wipe after flashing, would be I guess a good benchmark to test all stock ICS. (If you don't like to venture to custom ROMS that is) while waiting for Sammy to release that sought after update.

anyway, My point in all of this is that ROOTING doesn't brick the phone, the hardbrick bug is inherent in our Note and flashing stock /custom ICS Rom (with leaked or official ICS kernel) can give you the hardbrick bug.. even if your phone is NOT ROOTED.
[Galaxy Note GT-N7000 General] abhijit038:
All this time while switching between Roms and wiping, I was well aware of the fact that if I brick my phone, then I always have warranty as safeguard.Were it not for warranty, I wouldn't have ventured out, knowing the imminent impending danger.:D

Nevertheless, I would try switching to other stock ROMs and test.But installing CM9 will void my warranty, won't it ?