[Galaxy Tab 10.1 General] podtalje:
Since there have been several reports about bricking their tablet when doing the factory reset in recovery, I think it is useful to open the thread about this problem so we can gather all the facts in one place and keep other topics clean.

Below are the facts that I have gathered so far. I will update this post in the future with new info.

PROBLEM:

When doing factory reset in recovery the Galaxy Tab may freeze. After that it will no longer turn on. Most if not all of these problems happened when using cm-9-20120901-EXPERIMENTAL-p4.zip and ClockWork recovery 6, that was available in the same directory. But in theory this problem can also happen when doing factory reset from stock ICS.

DIAGNOSE:

It seems that the problem is in the faulty firmware of the eMMC chip. When erasing the data, a command mmc_cap_erase is executed which can corrupt data in the chip and make in unusable. After restarting the the only APX device is visible in device manager and the tab does not turn on.

Also worth noting is that the brick may happen already the first time you do the factory reset, but on the other hand you can wipe several times without any problems. So it's a little bit random.

There have been several reports with the same problem also on other Samsung devices and a lot of info on this bug can be found in the thread:

http://xdaforums.com/showthread.php?t=1644364

IS YOUR CHIP DANGEROUS OR SAFE?

There is an application made which will check which eMMC chip and firmware is loaded on your tab and will tell you if you are safe or not.

App can be found in thread http://xdaforums.com/showthread.php?t=1693704

WHAT TO DO IF YOU HAVE A FAULTY eMMC CHIP

There are three conditions that all need to be satisfied to for corruption to occur:

1. You have a faulty eMMC chip

2. kernel needs to support mmc_cap_erase command

3. A recovery binary that triggers calls to mmc_cap_erase()

Gingerbread recoveries don't issue this command, so if you are still on Gingerbread you are safe. Pershoot also removed support for this command from his kernels, so they should also be safe. Additionally this problem can be avoided if by flashing CWM 5 or CWM 6 from droidbasement.com CM10 folder either with mobile odin or odin.

WHAT KIND OF INFO WOULD BE HELPFUL and WHAT TO DO:

1. How many users were affected by this bug. Please report in this topic if you have encounter this problem on Galaxy Tab 10.1

2. What have you tried to solve the problem?

One possible solution which worked in the past was to fully discharge the battery. So far most of the users are still waiting for their tab to discharge, but some reports already indicate that this will not help. There have also been some users saying that their device will not charge after the battery has been completely discharged so maybe it is not the best idea to fully discharge the tab. I will update this when we will have more reports from tab 10.1 users. More about this procedure can be read in http://xdaforums.com/showthread.php?t=1478361

Another approach for solving this problem would be by using nvflash utility which can work in APX mode that our tab is currently in. If you are lucky and you have unlocked bootloder

you can try to load new image and recovery. If you receive error 0x4 error it means that you bootloader is locked and this approach will not work.

Details on this procedure can be found in http://xdaforums.com/showthread.php?t=1130574

3. Warranty - How many users have taken the tab to Samsung service center and did the fix it?

Also please add any other info that might be useful and I will try to keep this post updated .

---------------------------------------------------------------------------

4. Conclusions

- At the moment there is no known way to repair it yourself.

- So far those claiming warranty had not problems and tab was repaired free of charge.

- Avoiding brick:

The only danger now seems to bi if you are on stock ICS ROM and you execute factory/data reset in Samsung recovery.

If you are using custom ROMs and CWM you should be safe because all custom ROMs/krenels have now removed mmc_cap_erase() from list of capabilities.