yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 Q&A, Help & Troubleshooting] PanchoPlanet:
I have been using CWM 6050 since before CM12, updated it while on CM11, did a nandroid ran with it for several months before flashing CM12, after flash tab was running great, no bugs all apps working then one day in the evening after using it part of the day, it was dead.

Flashed nandroid, CM11, and it was running again with a few app bugs until re-flased CM11 and gapps again.

Don't know what happened but tab is fine now.

Pp.

---------- Post added at 05:11 PM ---------- Previous post was at 05:06 PM ----------

I would buy Samsung again, have not had any problems after 3 past phones, currently have S4 and Note3, 7"Tab plus,and P5113.

My son has a Nexus 10 about year and a half old, and my debloated P5113 keeps right up with his stock Nexus 10.

Pp.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] brandon7gr:
Damn .... one more victim of this bull**** chipset! The tablet is dead ... so the only case now is the replacement of the motherboard? Since download mode and recovery works...if I flash via odin an official firmware and go to the Samsung service...and if the tablet is on the warranty will they change the m/b?? Do they have a reason NOT to change it?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] homephysician:
Hi [MENTION=4298060]PanchoPlanet[/MENTION], Hey [MENTION=4956856]Aandi[/MENTION], this may or may not be of any help. I have 2 tab 2 10.1, on one I ran slimP, the other slimkat. I updated slimP and went into boot loops. I've been flashing different roms and have always been able to pull it out one way or another. Long story short. The tab looped till battery died, I had to go to work so I left it looping. When I got home it wouldn't boot and it was on the charger all day. I unplugged it and set it aside for a week. I then used the other tablet during this time. I did a little more research and found that the battery could be removed. So I charged up the slim Kat tab, removed the battery and placed it in the non working tab. I booted into recovery and flashed my backup. It worked. The other battery I have in the slim Kat tab is charging. I will update on the battery later.

I thought my tab was toast but it's not. Maybe this is just a fluke but my tab wouldn't boot, charge or go to recovery. It wouldn't blink or nothing. I hope this helps someone else with a soft brick. Thanks for all you guys do to make our aging tabs live on.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] brandon7gr:
GOOD NEWS FOR ME !!!!

Ok lets take it from the beginning...the problem was that my tablet was booting in the latest CM12, but after the loading of the rom I saw only black screen (the tablet was working because the volume keys were ok..I could hear the sound. Then I tried to flash another ROM but I had some errors. I went to the download mode and tried to flash a stock ROM (the firmware installation was ok) but after the restart it stacked on Samsung Logo (I tried with two different firmware and I got the same mistake).

But since download mode was working..I flashed the latest version of TWRP thought odin. Then i went inside TWRP and I restore an old backup that I had (i think since two months) and it worked !!!!!! Now the tablet is booting and working again as before!!!! For those that they have the same problem with me just restore an old nandroid backup to check...

So..is everybody speaking about the same error like me or is it something different? What are the steps now in order to NOT have this problem again? Should we remain in this old backup that we have? Should we flash a new one?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] PanchoPlanet:
Good find, this may be a breakthrough to solving this chip issue.

What you did was a total motherboard reset by disconnecting the battery, did read about this somewhere but can't recall, typically when rebooting or doing factory reset the motherboard is constantly under power even if battery is at 1% there is still power present, by disconnecting battery wires and leaving motherboard without any current you get a proper motherboard reset and it comes back to life.

For those out there with dead tabs you should try disconnecting at least one battery wire for at least 3 minutes and then reconnect and see if this brings your tablet back to life.

This is similar to when you reset the the ecu on a car that has trouble clearing a fault code, you disconnect the battery for 5 minutes and the system will reset back to factory specs.

All my tabs are working at present but would not hesitate to try if one was bricked.

Pp.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=5018170]p0nc[/MENTION] you know your recovery is damn old?

Have you tried flashing a different recovery?

Edit:

[MENTION=5018170]p0nc[/MENTION] please try flashing my latest TWRP unside PhilZ Touch, reboot recovery once and see if TWRP loads. If yes, please wipe data, system, cache and dalvic. Flash a Rom, nothing else and reboot.

Your issue don't seems to be eMMC.

Before flashing a stock rom you need to wipe data, system, cache and dalvic first, else you will end in bootloop.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] p0nc:
Flashing in Odin (pass) and in recovery via zip, both work but changes nothing after a reboot and it goes back to my old philz recovery. I tried a new philz (6.57.8) and TWRP 2.8.4.1.

:(
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Ok :(

Please give me this information:

You are in bootloop right? Device doesn't boot? My idea is a little experimental, we could backup some partition on external sd. After that we can try parted to delete data and system and recreate the partition.

I am not sure, if it works or not. You can think about it and let me know.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] p0nc:
Enclosed the requested file.

And yes, im in a bootloop, and i would like to try it. To me this tab is already dead, and i have a new one. So experimenting with this non working tab 2 is fine by me! :)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=5018170]p0nc[/MENTION] thx a lot :)

I will write an tutorial for you incl. All needed backup commands and send you on PM late this evening.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] prdepune:
Andi .. details as you wanted

Sorry for the delay Andi,

Here is the information that you asked for along with Parted info.

- last used rom before the issue started

jzo54kp3100ddcna3 Android 4.1.2

- used recovery + recovery version number

CWM 6.0.2.7

- eMMC info

MAG2GA, 0x000015, 04/2012, ID 07

- device model + storage (e.g. P3110 16GB)

P3100, 16GB

Parted INFO

(parted) p

p

p

Model: MMC MAG2GA (sd/mmc)

Disk /dev/block/mmcblk0: 15.8GB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 4194kB 25.2MB 21.0MB ext4 EFS

2 25.2MB 27.3MB 2097kB SBL1

3 27.3MB 29.4MB 2097kB SBL2

4 29.4MB 37.7MB 8389kB PARAM

5 37.7MB 46.1MB 8389kB KERNEL

6 46.1MB 54.5MB 8389kB RECOVERY

7 54.5MB 789MB 734MB ext4 CACHE

8 789MB 810MB 21.0MB MODEM

9 810MB 2278MB 1468MB ext4 FACTORYFS

10 2278MB 15.2GB 12.9GB ext4 DATAFS

11 15.2GB 15.8GB 537MB ext4 HIDDEN

(parted) u s

u s

u s

(parted) p

p

p

Model: MMC MAG2GA (sd/mmc)

Disk /dev/block/mmcblk0: 30777344s

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 8192s 49151s 40960s ext4 EFS

2 49152s 53247s 4096s SBL1

3 53248s 57343s 4096s SBL2

4 57344s 73727s 16384s PARAM

5 73728s 90111s 16384s KERNEL

6 90112s 106495s 16384s RECOVERY

7 106496s 1540095s 1433600s ext4 CACHE

8 1540096s 1581055s 40960s MODEM

9 1581056s 4448255s 2867200s ext4 FACTORYFS

10 4448256s 29728733s 25280478s ext4 DATAFS

11 29728734s 30777309s 1048576s ext4 HIDDEN

(parted) q
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=1181770]prdepune[/MENTION] you haven't been on any custom.rom?

Used a different kernel?

Wiped in recovery?

Have you tried updating your recovery?

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] prdepune:
Yup .. very much .. this was second ROM. But I don't recollect the version. Second time flashed ROM was suggested by CWM thread.

I have tried almost everything including wiping recovery, updating it with latest compatible version, trying with TWRP, Philtz, etc.

I tried updating ROM with different versions. But the story remains same. Even after deleting data from ADB, everything comes back as soon as tab is rebooted. It boots to home screen & reboots in loops.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] fredy66:
[MENTION=1181770]prdepune[/MENTION]

You have installed cwm 6.02.7 ?

That means you have never installed a KitKat or lollipop based rom until the brick appeared?

This information is important.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] prdepune:
Yes, that's right.

Mine was jellybean ROM which I had flashed one year back .. this problem started suddenly when I forgot to charge my Tab & it was completely discharged.

When I plugged it in with the charger & powered it on next morning, it encountered reboot loop. This also means that I was not trying to do anything like flashing or updating with my Tab.

Now no matter what I do, ROM cares a damn! Recovery too is stubborn & doesn't get flashed with any other version.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=5353383]fredy66[/MENTION] thx for your pm first of all. Not sure, if [MENTION=4243514]Hashcode[/MENTION] can tell me some more after taking a look on the data sheet.

Maybe some devices getting to old now? Flash memory won't live forever... I have some sd cards bricked after some days of use in the past.

It's hard to debug such an issue on an old device. Shouldn't have happened it earlyer more often too?

Atm i think disabled trim is the safest way anyway.

Running new cm 10.2 builds right now, hope it can still be compiled :P

New Omni 4.4 builds are ready, p51xx still uploading.

[MENTION=5018170]p0nc[/MENTION] work killed me today, will pm you the tutorial tomorrow evening.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] p0nc:
[MENTION=5018170]p0nc[/MENTION] work killed me today, will pm you the tutorial tomorrow evening.

No rush, ill wait patiently :)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] fredy66:
[MENTION=220904]andi[/MENTION] only an interesting link for Hashcode

https://android.googlesource.com/ke...ec87554e201d146934b/drivers/mmc/core/quirks.c

At the end there is the code for reading out the smart report of emmc.

The patches at the beginning are not necessary.

Yes maybe the tab is getting old.

One question to the disabled trim.

Why is mounting with the discard option still possible?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Sabhastar:
Help

I'm using:

CWM Recovery 6.0.5.1 latest build, cm-12-20150206-UNOFFICIAL-p3100 ROM, eMMC MAG2GA, device GT-P3100 16GB.

Last night I installed an application, that application coming from a Clean Master backup. When I finished install that application, suddenly there's warning that says "Unfortunately, the process android.process.acore has stopped" and that warning keep coming up. I tried to flash the ROM and GApps again but it changes nothing, it always coming back to state before I wipe data/factory reset and same error. Am I experiencing a soft brick? Or a TRIM issue? How can I fix this? Really need help..:crying::crying: Sorry for my bad English..
[Galaxy Tab 2 Q&A, Help & Troubleshooting] prdepune:
Welcome to the "brick" world .. :laugh::p

Hope your problem is not that serious.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Sabhastar:
Well, I hope so. By the way, do you have any solution to this?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] PanchoPlanet:
Try opening up the tab and doing a battery disconnect.

Pp. Over and out.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] prdepune:
We are riding in the same boat!

If flashing ROM & recovery is not changing anything on your tab, most possibly it is bricked, I am afraid.

What you can try is a sequence of factory reset, flashing ROM & again wiping data, all for 3 times. There is no logic but that worked for me in my previous brick issue.

This time it is little different for me & nothing is working. TRIM got my tab.

Let us know more about it. Post the versions of ROM & recovery that you were/are using. Did you try to flash the recovery?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
Hey guys, please don't panic now... what a histery, LOL :D

[MENTION=6386420]Sabhastar[/MENTION] I had that pop-up on several devices several times in past years and none has bricked yet.

Try to wipe data of cLock app and reboot. If the warning still popups there, create a logcat and see what is causing it.

tetakpatalked from N7100
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Sabhastar:
I'm using CM12 latest build and CWM 6.0.5.1 latest build from [MENTION=5153662]Android-Andi[/MENTION]. I haven't tried to flash my recovery..

Can you provide the instruction to wipe data of clock app?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=6386420]Sabhastar[/MENTION] make a clean flash, only flash rom.

See.if it works, if it does boot back into recovery and flash the gapps. If you now have issues, then it's gapps fault.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Sabhastar:
Ok, will try this now, thanks for your help. I will post again after flashing ROM.

---------- Post added at 08:09 AM ---------- Previous post was at 07:52 AM ----------

[MENTION=5153662]Android-Andi[/MENTION] not working. It still come back to the state before factory reset and other wipe..
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=6386420]Sabhastar[/MENTION] is it possible to flash and boot TWRP?

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Sabhastar:
[MENTION=5153662]Android-Andi[/MENTION] haven't tried that yet.. Where should I flash TWRP? From Odin or I can use CWM?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Doesn't matter, both ways are ok

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Sabhastar:
[MENTION=5153662]Android-Andi[/MENTION] not working too. Already flash newest TWRP through Odin, but it come back to CWM Recovery 6.0.5.1..
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Please Backup all important partitions:

##### Backup EFS, Param, Bootloader and Modem
adb shell dd count=40960 bs=512 if=/dev/block/mmcblk0p1 of=/external_sd/efs.img
adb shell dd count=4096 bs=512 if=/dev/block/mmcblk0p2 of=/external_sd/sbl1.bin
adb shell dd count=4096 bs=512 if=/dev/block/mmcblk0p3 of=/external_sd/sbl2.bin
adb shell dd count=16384 bs=512 if=/dev/block/mmcblk0p4 of=/external_sd/param.lfs
adb shell dd count=40960 bs=512 if=/dev/block/mmcblk0p8 of=/external_sd/modem.bin

after that pull those files from your device too, to have a local copy too:

adb pull /external_sd/efs.img
adb pull /external_sd/sbl1.bin
adb pull /external_sd/sbl2.bin
adb pull /external_sd/param.lfs
adb pull /external_sd/modem.bin

If done, please ping me again :)

It will look like this:

android-andi@buildbot:~/android$ adb shell "dd count=40960 bs=512 if=/dev/block/mmcblk0p1 of=/external_sd/efs.img"
40960+0 records in
40960+0 records out
20971520 bytes [COLOR="Red"](20.0MB)[/COLOR] copied, 0.722992 seconds, 27.7MB/s
android-andi@buildbot:~/android$ adb shell "dd count=4096 bs=512 if=/dev/block/mmcblk0p2 of=/external_sd/sbl1.bin"
4096+0 records in
4096+0 records out
2097152 bytes [COLOR="Red"](2.0MB)[/COLOR] copied, 0.237640 seconds, 8.4MB/s
android-andi@buildbot:~/android$ adb shell dd count=4096 bs=512 if=/dev/block/mmcblk0p3 of=/external_sd/sbl2.bin
4096+0 records in
4096+0 records out
2097152 bytes [COLOR="Red"](2.0MB) [/COLOR]copied, 0.241455 seconds, 8.3MB/s
android-andi@buildbot:~/android$ adb shell dd count=16384 bs=512 if=/dev/block/mmcblk0p4 of=/external_sd/param.lfs
16384+0 records in
16384+0 records out
8388608 bytes [COLOR="Red"](8.0MB) [/COLOR]copied, 0.484039 seconds, 16.5MB/s
android-andi@buildbot:~/android$ adb shell dd count=40960 bs=512 if=/dev/block/mmcblk0p8 of=/external_sd/modem.bin
40960+0 records in
40960+0 records out
20971520 bytes [COLOR="Red"](20.0MB) [/COLOR]copied, 0.895080 seconds, 22.3MB/s
android-andi@buildbot:~/android$ adb pull /external_sd/efs.img
7454 KB/s (20971520 bytes in 2.747s)
android-andi@buildbot:~/android$ adb pull /external_sd/modem.bin
7411 KB/s (20971520 bytes in 2.763s)
android-andi@buildbot:~/android$ adb pull /external_sd/param.lfs
7317 KB/s (8388608 bytes in 1.119s)
android-andi@buildbot:~/android$ adb pull /external_sd/sbl1.bin
6109 KB/s (2097152 bytes in 0.335s)
android-andi@buildbot:~/android$ adb pull /external_sd/sbl2.bin
6179 KB/s (2097152 bytes in 0.331s)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] divyanshu.grover:
Should we also backup our partitions? Or wait until something positive comes out of this procedure in the end?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Backup.never hurts :) efs is most important if you use custom roms

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] divyanshu.grover:
Done :) Output attached below.

E:\Android\sdk\platform-tools>adb devices
List of devices attached
c16073a0b58f63f recovery

E:\Android\sdk\platform-tools>adb shell dd count=40960 bs=512 if=/dev/block/mmcb
lk0p1 of=/external_sd/efs.img
40960+0 records in
40960+0 records out
20971520 bytes (20.0MB) copied, 0.763031 seconds, 26.2MB/s

E:\Android\sdk\platform-tools>adb shell dd count=4096 bs=512 if=/dev/block/mmcbl
k0p2 of=/external_sd/sbl1.bin
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.204285 seconds, 9.8MB/s

E:\Android\sdk\platform-tools>adb shell dd count=4096 bs=512 if=/dev/block/mmcbl
k0p3 of=/external_sd/sbl2.bin
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.175109 seconds, 11.4MB/s

E:\Android\sdk\platform-tools>adb shell dd count=16384 bs=512 if=/dev/block/mmcb
lk0p4 of=/external_sd/param.lfs
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 0.425079 seconds, 18.8MB/s

E:\Android\sdk\platform-tools>adb shell dd count=40960 bs=512 if=/dev/block/mmcb
lk0p8 of=/external_sd/modem.bin
40960+0 records in
40960+0 records out
20971520 bytes (20.0MB) copied, 0.849273 seconds, 23.5MB/s

E:\Android\sdk\platform-tools>adb pull /external_sd/efs.img
2230 KB/s (20971520 bytes in 9.183s)

E:\Android\sdk\platform-tools>adb pull /external_sd/modem.bin
2149 KB/s (20971520 bytes in 9.526s)

E:\Android\sdk\platform-tools>adb pull /external_sd/param.lfs
2216 KB/s (8388608 bytes in 3.696s)

E:\Android\sdk\platform-tools>adb pull /external_sd/sbl1.bin
2047 KB/s (2097152 bytes in 1.000s)

E:\Android\sdk\platform-tools>adb pull /external_sd/sbl2.bin
2305 KB/s (2097152 bytes in 0.888s)

Edit: Also whenever I try to use parted, I get not found error. It is also not present in my sbin/sh folder, where the other command files are. Does the ROM not have the functionality or the kernel?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=5497042]divyanshu.grover[/MENTION] you are on TWRP, right? Maybe you need yo push the binary first and make it executable. Will check it sometimes later.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] ssqw1:
Here is the output:

C:\Windows\system32>adb shell dd count=40960 bs=512 if=/dev/block/mmcblk0p1 of=/
external_sd/efs.img
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
40960+0 records in
40960+0 records out
20971520 bytes (20.0MB) copied, 0.909973 seconds, 22.0MB/s

C:\Windows\system32>adb shell dd count=4096 bs=512 if=/dev/block/mmcblk0p2 of=/e
xternal_sd/sbl1.bin
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.292053 seconds, 6.8MB/s

C:\Windows\system32>adb shell dd count=4096 bs=512 if=/dev/block/mmcblk0p3 of=/e
xternal_sd/sbl2.bin
4096+0 records in
4096+0 records out
2097152 bytes (2.0MB) copied, 0.365540 seconds, 5.5MB/s

C:\Windows\system32>adb shell dd count=16384 bs=512 if=/dev/block/mmcblk0p4 of=/
external_sd/param.lfs
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 0.568787 seconds, 14.1MB/s

C:\Windows\system32>adb shell dd count=40960 bs=512 if=/dev/block/mmcblk0p8 of=/
external_sd/modem.bin
40960+0 records in
40960+0 records out
20971520 bytes (20.0MB) copied, 0.860535 seconds, 23.2MB/s

C:\Windows\system32>adb pull /external_sd/efs.img
2152 KB/s (20971520 bytes in 9.516s)

C:\Windows\system32>adb pull /external_sd/sbl1.bin
2010 KB/s (2097152 bytes in 1.018s)

C:\Windows\system32>adb pull /external_sd/sbl2.bin
1822 KB/s (2097152 bytes in 1.123s)

C:\Windows\system32>adb pull /external_sd/param.lfs
2364 KB/s (8388608 bytes in 3.464s)

C:\Windows\system32>adb pull /external_sd/modem.bin
2170 KB/s (20971520 bytes in 9.437s)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Allen404:
I tried to flash new recovery, roms, and original stock rom via Odin, it always revert back to SlimLP. And when on boots tons of "unfortunately the process..... just stopped", and it's just stuck like that, but no reboot. Is it the eMMC bug or is it another issues?

I'm using P3100 16GB, and the chip is model is MAG2GA.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Not many information given from you...

Recovery + version number?

Rom version + date?

Did you tried to wipe before flashing anything different?

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Allen404:
Whoops my bad

TWRP 2.8.1.1

CM12 20150118 (I've mentioned SlimLP, my mistake)

Well I just wipe cache and dalvik and dirty flash to newer CM12.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
It more sounds like.a.dirty flash issue.

Format cache, dalvic, system and data in twrp.

Reboot TWRP once.

Flash latest build.

Reboot into the rom now.

Don't flash gapps, you can do later.

This will help to see if the gapps are causing problems for you.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
Settings/apps/all apps.

But look here how one guy from HTC threads solve it:

This makes me belive that it wasn't cLock app data wipe, but maybe clear data on contacts app and contact storage...

If you do that, don't forget to export contacts before as vcf file (app People, settings, import/export, export to sdcard). If your contacts are synced with Google account, disable it before wiping contacts storage and people app data. Then reboot recovery, clear cache and dalvik cache and reboot OS. Stepwise, thus.

tetakpatalked from N7100
[Galaxy Tab 2 Q&A, Help & Troubleshooting] divyanshu.grover:
Yes, TWRP. Yeah maybe I could push it to external sd card and run it from there, since the internal memory won't work.

No hurry :) Just wanted to know, because maybe it would be needed in the resurrection of tab (You mentioned deleting and re-creating partitions using parted).

Anyhow, thanks :) Appreciate you for trying to fix our devices.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=5497042]divyanshu.grover[/MENTION] you could try downloading latest CWM.zip from my androidfilehost for your device.

After that extract the recovery.img and place it on your MicroSD Card.

You could try to use "dd" to replace your current recovery:

adb shell dd count=16384 bs=512 if=/external_sd/recovery.img of=/dev/block/mmcblk0p6

Edit:

Just to keep an eye on the reports and given information:

https://docs.google.com/spreadsheets/d/1jOHoJUzTQQ9jHvO4ijso4NlL5PuqLfTAHWzlrHShBgk/edit?usp=sharing