yashsingh1/xdaforums huggingface dataset:
[Epic 4G Q&A, Help & Troubleshooting] TexasAggie97:
I am having problems with my internal memory dropping below 50MB remaining internal memory and even though I uninstalled several apps (or moved them to my SD card) my internal memory remains nearly the same.

I am wondering if there is some sort of "back-up" folder on my internal phone storage that is taking up a lot of unneeded storage space.

I am running SleeperROM 3.0.0 and have seen some "back-up" folders on the SD card, but don't know where to look on my internal phone storage. I did not have these memory problems when I was running SleeperROM 2.1.0 (or whatever the last version was) even though I had the same number of apps on the phone.

Does anyone know where files cached from internet, e-mail, back-ups are located?
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
A few apps that updated recently are larger. All apps are stored in data partition on the phone not the Sd card.
[Epic 4G Q&A, Help & Troubleshooting] TexasAggie97:
I see that even though I move apps to the SD card, there is still some remnance on the phone. But is there any folder(s) out there that may be storing documents or data from e-mail, web, etc...?
[Galaxy Tab 10.1 General] podtalje:
I have installed the bootloader and CWR 6 from the p4 folder on the droidbasement.

After that I have installed three or four different ROMs through recovery without any problems.

When I finally wanted to load the CM9 rom for the last time and selected "clear data", the tab has frozen at "formatting cache ..".

I waited for a while and then pressed power button. It turned off and now I am also stuck in APX mode.

I am still waiting for battery to discharge, although based on some posts I doubt it will help.
[Galaxy Tab 10.1 General] decatf:
I had this problem with cm-9-20120828-EXPERIMENTAL-p4wifi.zip and the associated recovery.tar.md5 hosted by pershoot. The device froze while doing the clear data option in CWM. It will only show up as APX in device manager.

I've been waiting about a week and a half for the battery to drain. It is still not drained yet.

Based on the Epic 4G Touch thread it looks like the draining method is not likely to work.

The fact that this does not affect GB kernels could explain why nobody seems to have reported success with the draining method yet in the recent brick bug cases. The draining method may have worked in the past with whatever issue(s) were causing the devices to be stuck in APX mode with GB. This does not seem to be the case so far with ICS and this corruption bug. The EMMC corruption bug seems like a more serious issue than simply doing a battery drain will solve.

If this is the case then wouldn't it be inadvisable to be suggesting the battery drain method to people? I mean if the drain method is not a solution to this problem then users will be left with their devices in a worse state. There have been users saying that their device will not charge after the battery has been completely discharged.
[Galaxy Tab 10.1 General] rayoco:
So, ¿What do I do if I have a faulty chip?
[Galaxy Tab 10.1 General] nakedninja42:
Either Samsung Warranty or see if Mobile Tech Video can repair. I've seen people say they were able to get their phones revived by Mobile Tech.
[Galaxy Tab 10.1 General] PookiePrancer:
Link to Mobile Tech Video, please? Lost a Tab 7 to this bug.
[Galaxy Tab 10.1 General] nakedninja42:
Don't know how to contact them, just read others able to get it fixed by them.
[Galaxy Tab 10.1 General] fix.kowalski:
I have an eMMC-related issue (Galaxy Tab 10.1 Google I/O Edition/ p4wifi), which leaves the tablet as bricked, but I am not sure it is the exact same problem.

1) running pershoot's cm10, not cm-9

2) no more boot in recovery (but from an external recovery using fastboot, which is still working)

3) heimdall no longer working (see )

4) normal boot loops (only) because /data is mounted read-only (I have the adb logcat) presumably due to fs-errors

At the end, the tablet is bricked, even if it is in a boot loop. Any interest in the logcat?
[Galaxy Tab 10.1 General] rayoco:
RE:

My tab isn't screwed in this moment. But what I do to prevent a Brick?
[Galaxy Tab 10.1 General] pershoot:
you do not have a brick.

fastboot boot the stock IO recovery and do a factory reset in there. this will format /data. you will be revived.
[Galaxy Tab 10.1 General] fusionjack:
From my point of view, these following steps should prevent the device to be bricked:

* Flashing CWM 5 or CWM 6 from droidbasement.com CM10 folder either with mobile odin or odin.

* Flashing A1 kernel 1.6.4 that has MMC_CAP_ERASED disabled.

These are applied for those that have Stock ICS or CM9 build 09/01.

Correct me if I'm wrong.
[Galaxy Tab 10.1 General] podtalje:
What I would also like to know is how many users of Galaxy Tab 10.1 are using faulty eMMC chip?

This can be simply checked with BrickBug application:

http://xdaforums.com/attachment.php?attachmentid=1303502&d=1346829980

Please report in this topic which eMMC chip is used in your device.

Additionally what would also be helpful for others is information if default ICS kernel supports MMC_CAP_ERASED command and if there is any situation that this happens on stock ICS if you issue Factory reset. Maybe someone with more knowledge can answer this.
[Galaxy Tab 10.1 General] pershoot:
yes, the stock ICS kernel does support mmc_cap_erased (as is the published source). this is how it ships from nvidia. removing it is an after thought. the root of the issue is the chip inside.
[Galaxy Tab 10.1 General] djmatt604:
P7510 here.

eMMC chip

Type: MAG4FA

Date: 02/2012

CID: 1501004d414734464112e20982d12f00

FwRev: 0x12

Brick Bug?

YES. Insane chip.

I'm running a memory test right now. EDIT: My test passed. Took about 10 minutes to run with the app. I was on CM10 for a short time but have since moved back to Infamous2 ICS with the A1 kernel.
[Galaxy Tab 10.1 General] Ackoman:
I got the same result as djmatt604 (as far as the brick bug goes that is, not tried the memory test)
[Galaxy Tab 10.1 General] GalaxyNinja:
What now?? I don't want to brick. I'm on CM10 cwm6.
[Galaxy Tab 10.1 General] zerong:
My tab have eMMC Brickbug (i tested it with the little apk soft).

I am lucky ! Three days ago i flashed A1 kernel and when i choose to wipe i selected wipe data reset factory (i did it fastly and wipe partition line is just under) !!!!!! Happy to see my previous kernel had applied git patch to disable mmc_cap_erase !!!!! so all have been ok when reboot ! ouf !!!
[Galaxy Tab 10.1 General] keithmoore:
This happened to me about a week ago, I was flashing 'cm-9-20120901-EXPERIMENTAL-p4.zip' using TWRP, now I can only see the tab in 'apx' mode.

Trying to send commands via 'nvflash' gives an 0x4 response, which indicates a locked bootloader (I believe).

Currently trying the 'battery drain' option, but as my tab had just been fully charged this is taking a while.

Of course, my tab is over 12 months old and therefore out of warranty!
[Galaxy Tab 10.1 General] Localhorst86:
eMMC chip

Type: SEM16G

CID: 02010053454d3136479061538a135e00

Revision: 0x90

Verdict: Unknown Chip, don't know if dangerous. At least it isn't one of the chips known to be bad.

I have been using TWRP and CWM 6 various times and did a full reset (inlcuding data wipes on TWRP), no bricks. I assume my chip is safe.
[Galaxy Tab 10.1 General] serosis:
I got the brick bugger.

Although oddly enough, never bricked while doing a factory reset.
[Galaxy Tab 10.1 General] podtalje:
OK, thats what I thought.

Do you maybe know if this command is executed when doing Factory reset on stock ICS ROM from Samsung. I think a lot of users would like to know that and it would also be a little easier to claim warranty by saying it happened on stock Samsung ROM.
[Galaxy Tab 10.1 General] podtalje:
I have also updated the first post with some details about nvflash utility which can work with APX mode. Maybe someone with unlocked bootloader will be able to get more details.

More about this procedure can be found in topic http://xdaforums.com/showthread.php?t=1130574
[Galaxy Tab 10.1 General] goldlocke:
US GTab 10.1 here - from the first shipments surely.

eMMC chip

Type: SEM16G

CID: 02010053454d3136479061538a135e00

Revision: 0x90

Verdict: Unknown Chip, don't know if dangerous. At least it isn't one of the chips known to be bad.
[Galaxy Tab 10.1 General] Claus72:
This problem is, also, present in Galaxy Royal. Yes this command is executed also doing factory reset from stock ICS.

The only safe mode to make a hard reset if from a kernel with MMC_CAP_ERASE removed.
[Galaxy Tab 10.1 General] djmatt604:
Hmm. Not long ago when I came off JB to ICS I had flashed stock firmware (LPL) and did a factory reset because I had stuck at the Samsung logo on first boot. The wipe went fine and of course I am ok now. If this is a problem on the factory kernel, why is my device not a coaster right now?

EDIT: could it only be a concern with stock kernels for certain firmware releases perhaps?
[Galaxy Tab 10.1 General] Claus72:
I know but with emmc brickbug....if you have a brickable chip, and mmc_cap_erase is on.... brick is inevitable. You may brick your device after first or one hundread first factory reset. It's like playing russian roulette.

From Galaxy R thread:
[Galaxy Tab 10.1 General] djmatt604:
I am now running A1 1.6.4 with the mmc_cap_erase fix and will be installing the same kernel on the wife's tablet as well. Suffice it to say folks this is keeping at least me from wanting to flash any other ROMs unless they are known to be compatible with kernels that will sidestep this issue.
[Galaxy Tab 10.1 General] azncookiecutter:
Mine is bricked right now, from trying to restore from CWM, 0901 build if I recall correctly. Going to call a Samsung service centre here in Canada to see how much it'll cost to get it fixed. Good thing I still have extended warranty from my credit card when it was purchased, so it shouldn't cost me anything in the end to fix it.
[Galaxy Tab 10.1 General] pershoot:
ill also bring in another safeguard in to the build (kernel has been taken care of already), in case someone decides to flash a kernel with this capability in it on to the build.
[Galaxy Tab 10.1 General] jayceebee23:
Thank you. Thank you. Thank you! This will definitely bring us the ease of mind we once enjoyed when flashing ROMs as wonderful as yours. The XDA community group is lucky to have someone who still cares. Cheers!
[Galaxy Tab 10.1 General] waaahsabi:
Say, do you perhaps have an ETA for that update?

I had flashed the 09/01 (kernel 3.1.1.0) version you had in the cm9/p4 section a while ago, but i'm still using CWM 5.5.0.4. I have nand-restored and cache wiped a couple of times since then, but right now i'm not too sure what to do about that issue, other than holding still...
[Galaxy Tab 10.1 General] podtalje:
In your case before loading any new ROMs, I would suggest that you installl CWM from CM10 pershoot folder which is considered safe.
[Galaxy Tab 10.1 General] valent|n0:
this thread scares me from buying galaxy tab

should I stay away from custom rom and factory reset all together?

I like vanilla flavour though
[Galaxy Tab 10.1 General] georgesadam:
My tab has the brick bug MAG4FA known bad !

So i shouldnt factory reset at ALL ????????

Im using the italian ICS stock and i wanted to flash jellybean ICS rom v6 , so is it danger to data wipe my tab 7500 ?????

Is flashing the CWM from droidbasement cm10 p4 is the solution for this brickbug and doing the fatcory reset from there ?
[Galaxy Tab 10.1 General] Claus72:
Before hard reset you have to flash a safe kernel. If I have understood fine pershoot has told that his kernel is safe.

If you want to wipe data and avoid the risk of superbrick, follow this method for a safer flash:

1. Flash cwm from odin (if you don't have it);

2. Flash safe kernel from cwm (with eMMC erase bug off);

3. Do a wipe data/cache/dalvik cache from cwm;

4. Flash the new ROM;

5. Reboot.:cowboy:
[Galaxy Tab 10.1 General] CazeW:
You should be safe as you're using an older CWM. Only the CWM recoveries built from 3.1 sources have the bug enabled afaik.
[Galaxy Tab 10.1 General] Claus72:
Sorry but I don't understand :rolleyes:. I know that emmc is a chip bug that is activated by a flag in the kernel and wipe date.

I missing something? Flashing by cwm I know is always safe becouse don't wipe data.
[Galaxy Tab 10.1 General] georgesadam:
ok thanks for your answer but can i flash pershoot kernel on my p7500 on stock italian ics ???
[Galaxy Tab 10.1 General] CazeW:
Flashing by CWM is not safe if all these conditions meet:

1. A faulty chip.

2. CWM recovery built from 3.1 sources.

3. A kernel that doesn't have mmc_cap_erase disabled.

For us, the situations where you're at risk are:

1. You're using pershoots 09/01 CM9 rom (with kernel) AND 09/01 recovery.

2. You're using stock ICS kernel AND stock ICS recovery.

3. You're using stock ICS kernel AND pershoots 09/01 recovery.

4. You're using Yoda 1.0 or older than A1 V1.6.4 kernel AND pershoots 09/01 recovery.

No. Flash A1 kernel instead.
[Galaxy Tab 10.1 General] Claus72:
Thank you for the details.

Therefore A1 kernel is safe and what version of CWM is not built from 3.1 and safe?
[Galaxy Tab 10.1 General] CazeW:
The older CWM 5.x are safe and the one pershoot has on his site is also safe. There was only one CWM recovery made for our tabs from 3.1 and it was the 09/01 one which pershoot has already removed.
[Galaxy Tab 10.1 General] georgesadam:
Is there anyway to bypass this and make a full wipe without cwm because i really need to make my tab clean from my folders containing movies music data ..

I tried doing this using cwm but i still cant delete them .

If i flash a1's kernel can i stay on stock recovery and how so i can format it and is it safe ?
[Galaxy Tab 10.1 General] Dead Silence:
Good to know. I'm a double lucky winner, both my P7510 (ICS 4.0.4) and my SII (still on GB so safe, but want to go to ICS 4.0.4 soon) have the 0x19 version, so brickbug. I installed ICS 4.0.4. on my P7510 from HC3.2 using Mobile ODIN and wiped everything possible that one can select in Mobile Odin. I also selected ever root, but that didn't work and I powered down the Tab because ODIN got stuck. After rebooting ICS 4.0.4. was installed and works fine. I guess I'm lucky.

But I feel really insecure to install ICS 4.0.4 on my SII. when it is released for my phone doing a full flash and wipe everything.
[Galaxy Tab 10.1 General] Claus72:
I'm happy for you but be more careful for the future.
[Galaxy Tab 10.1 General] Dead Silence:
Yep, now I'm aware of this issue, I'm really carefull. Don't like to brick one of my babies :)
[Galaxy Tab 10.1 General] pitflyer:
I have the same SEM16G chip that outputs 'undetermined' for brickable status.

Still glad to hear that the development community has pretty quickly tackled a bug and implement workarounds for it.

Sorry for the brave new users who got bricked, especially those out of warranty!
[Galaxy Tab 10.1 General] keithmoore:
Decided to send my 'bricked' tab off to the service centre to see what they say, and how much as its out of warranty.

Will include a letter stating that 'as this is a known fault etc' to see whether they will fix it for free...
[Galaxy Tab 10.1 General] podtalje:
I would like to know if anyone has successfully claim the warranty or got it back from repair.
[Galaxy Tab 10.1 General] azncookiecutter:
Mine got to the repair depot up here in Canada on Monday, still waiting for them to get back to me regarding the repair costs (I'm out of warranty).
[Galaxy Tab 10.1 General] keithmoore:
Sent mine off to the UK service centre yesterday with a letter stating that I believed this was due to a 'known Samsung eMMC bug' as mine is also out of warranty. Will wait to see if I get good or bad news...
[Galaxy Tab 10.1 General] azncookiecutter:
Got mine back, seems like they replaced the whole mainboard. Haven't gotten a chance to see if the new one has a faulty eMMC chip or not yet. No charge, even though I'm way out of warranty.
[Galaxy Tab 10.1 General] keithmoore:
Got mine back too, and seems to have been fixed free of charge!

Was a bit concerned as the online status for the repair has showed 'cancelled' since last Monday...:laugh:
[Galaxy Tab 10.1 General] decatf:
Did you guys send it with the original receipt or with a photocopy of the receipt?

I tried asking but the Samsung service agent kept giving me an different answers. I asked if it cannot be a photocopy and he said it can't. Then he said it can be a photocopy. Wtf? Are these chat agents outsourced?
[Galaxy Tab 10.1 General] keithmoore:
I registered the fault with the help centre, and they sent me a bag. With the bag was a letter, and it said to include a photocopy of the receipt.

I also enclosed a letter along the lines of 'although I am out of warranty I believe this was due to a known eMMC bug...'.

Sent back to me fixed within a week, wiped.

Although the service letter stated 'we have installed the latest approved software' it was still 3.2. A connection to Kies downloaded 4.0.4.
[Galaxy Tab 10.1 General] Jane Shizuka:
I generally avoid asking questions and just lurk, since there is so much information around, but I am really worried in this case. Can someone confirm me a few things?

I have a Tab 10.1 wifi (7510) with the eMMc 0x12, a.k.a "You got brickbug!" and I did update my tab using Odin to Ics(4.0.4).

So, in OP, it was stated that

I don't really understand how to see if "2" and "3" are my case, I don't understand what is a recovery binary as well. However, knowing that I am already in ICS and with a brickbug eMMc, I should never, ever do a factory reset/data Wipe? And since most "rooting" tutorials I've seen include both data wiping and factory reseting multiple times, I should never root too?
[Galaxy Tab 10.1 General] Benzoman:
Most, if not all recent kernels have addressed this already. Their change logs or somewhere in the thread of what you want flash, should state it's been fixed to not be affected.

I'm sure someone will elaborate if the answers aren't in this thread already.
[Galaxy Tab 10.1 General] decatf:
Recovery binary means ClockworkMod Recovery.
[Galaxy Tab 10.1 General] CazeW:
As far as I've understood, the bug also appears in the stock kernel and recovery. You only run a risk of bricking if you wipe/factory reset from the recovery. If you either flash CWM from pershoot and/or A1/Yoda kernel, you will be safe.
[Galaxy Tab 10.1 General] Jane Shizuka:
Ohhh thanks, somehow I was under the impression that simply data wiping/factory reseting would be a risky operation. Your message makes me much more relaxed.
[Galaxy Tab 10.1 General] decatf:
I got mine back. The report says the PBA MAIN part was replaced. From what I can Google it looks like it might be the motherboard/mainboard.

GotBrickbug app reports that it has a vulnerable/faulty chip. That's a little disappointing.
[Galaxy Tab 10.1 General] ElBartoME:
Got mine back. They replaced the mainboard free of charge. I even got a unlocked bootloader now. And yes, I still have an insane chip...
[Galaxy Tab 10.1 General] emze:
i just ran the app to check if my tab has the bug and it does not. am i still at risk?
[Galaxy Tab 10.1 General] ElBartoME:
http://xdaforums.com/showpost.php?p=32663645&postcount=4232
[Galaxy Tab 10.1 General] jjuki:
I also have the faulty chip. I have only flashed stock ICS over stock honeycomb, and now JB CM10 from pershoot. No problems here at all, just followed the instructions. I did not try factory reset from stock ics recovery.
[Galaxy Tab 10.1 General] podtalje:
I think the only danger now is 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.

BTW, I have just received back my bricked Galaxy Tab 10.1. It was still under warranty and it was repaired free of charge.

I don't know exactly how they fixed it but I have checked the eMMC version and it is still problematic 0x12 version.
[Galaxy Tab 10.1 General] armint:
My galaxy tab got bricked some time ago, and I couldn't return it for warranty because I bought it in the states and I live in the Netherlands. (I had one year warranty, but it expired). I flashed it multiple times with ODIN, and after 4 times it worked again (seriously, not the first 3 times!). Now that it's working I checked if I it has the emmc bug, and it does. So... I don't know if it is this particular bug that I ran into, but mine was solved by flashing it several times with odin (flashing with recovery didn't do anything). So maybe someone else who ran into the bug is willing to try this? It might be an alternative to sending the tab back to Samsung.
[Galaxy Tab 10.1 General] podtalje:
If you encounter eMMC brickbug, you will not be able to use ODIN, because the screen will not turn on and the only thing available is APX mode. Here the only solution that could possibly work is to unlock bootloader and use nvidia nvflash utility but even in this case the results were not very successful.

My guess is that the problems you had are not directly related to eMMC bug..
[Galaxy Tab 10.1 General] tallgrasshawk:
I'm running CWM6.xxxx, one that I got from a thread somewhere here on XDA, not from pershoot on droidbasement. Is this going to be a safe recovery? Running CM10 10/17 with his kernel.
[Galaxy Tab 10.1 General] pmdisawesome:
Hi, I am using the GT-P7510 (Galaxy Tab 10.1 Wifi)

I flashed the CWM Recovery Version 6.0.1.5 from DroidBasement . Which is from Pershoot himself.

I am on Stock Samsung (Task ICS)

So would it be safe for me to factory reset , restore or wipe cache with this recovery?

Thanks In Advance
[Galaxy Tab 10.1 General] serzhanja:
to get brickbug your device has to meet 3 criteria, one coming from the chip, the other - from kernel and the t\hird - from CWM. If one is not met, you're safe and AFAIK pershoot removed brickbug-related stuff from CWM and his kernels
[Galaxy Tab 10.1 General] tallgrasshawk:
Ok, thanks. So I *should* be safe if I'm running pershoot's builds.
[Galaxy Tab 10.1 General] kronik420:
This is going to sound stupid but I actually need to format my emmc and I can't find a setting inside clockwork that allows me to flash the emmc. I'm having the gallery problem that a few people have that keeps saying DECVICE OUT OF MEMORY DELETE SOME ITEMS and then the screen goes black. Apprently formatting this emmc partition should fix the problem. i checked I don't have the emmc brick bug I'm running the latest CMW I go under mounts and storage but I don't see anything that has emmc. any suggestions are a way i can get it to show emmc. Thank You
[Galaxy Tab 10.1 General] jjuki:
Correct me if I am wrong, but formatting emmc will format your whole internal memory. You maybe need to mount emmc first in CVM to be able to format the emmc. Is your internal memory full atm?
[Galaxy Tab 10.1 General] djmatt604:
Hi all:

I am working on an AOSP ICS rom compiled from source for the 7510 that will likely use the stock kernel that compiled with the build. I have seen some conflicting opinions on the subject and would just like to be sure I have the facts straight so I don't release something that could be potentially dangerous.

Someone mentioned earlier in the thread that the problem lies not with the stock kernel, but if you try to execute a factory reset from stock Android RECOVERY. Can we say for sure that this is true? I have permission to incorporate some other kernels that have mention of a patch being applied to them for this problem, but don't know if they are compatible with a pure AOSP rom.

EDIT: I think I have this straight after a re-read of the thread.....I guess it really does boil down to the kernel at the end of the day doesnt it. I will have to check the kernel source now to be sure.....