yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 Q&A, Help & Troubleshooting] geepounds:
Samsung GT-P3100 Restarting after every ten seconds

Hello everyone, Please I need help urgently with my GALAXY GT-P3100. It keeps restarting after every 10 seconds. I think my carrier (VOD) UK recently upgraded something on their server and my device was unable to successfully complete the installation as I am not in the UK. I have done all I can think of, which includes perfoming factory reset, flashing via odin with the same stock (VOD) firmware, flashing via odin with both Arabic and India repair firmwares by Rev04_user_low_ship, flashing the pit via odin, Installing via ADB and SD card and many more.

I'm guessing my device is on "Read-Only". Is there something I am missing? The stock (VOD) firmware gets stuck and fails at system.img while flashing with odin. Although, I get a pass while flashing with Rev04_user_low_ship Arabic and India repair firmwares, the phone returns to same problem after reboot. I get "E-Verification Signature Failed" while trying to Install via adb or SD Card and my recovery shows "MANUAL MODE Applied the CSC-Code : VGR did not match sized system/csc/common/system/csc/others.xml(No data available)". I have never used Custom ROMs or Recoveries on my device. Please what's the solution to this problem.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] لننطلق:
i have same proplem in my p3100 now

i have same proplem in my p3100 now... what you do to fix it
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Emmc reached end life. Replace emmc.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] ssqw1:
Should I try flashing latest recovery from ext sd card?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Won't change anything i think...

Did you checked re-format in odin and added the stock rom as pda?

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
You could try flashing the bootloader again, place as pda in odin:

P3100 http://d-h.st/Nfz

Or

P3110 http://d-h.st/FqI

It could be a dead nand.. maybe lifetime is over... damn flash memory...

I'll try to talk to some other devs too about your issue.

same 1 year ago, chip had to be replaced http://forum.slimroms.net/topic/2116-unable-to-re-flash/page-4

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] ssqw1:
Thanks, I tried re partitioning and flashing the bootloader but to no avail. Could you guide me to a video to replace the chip?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
No sorry... i am still looking around if there's a different way.

Jonathan from omap4 dev chat remembered this issue from gnex and linked me to http://xdaforums.com/showpost.php?p=43624372&postcount=25

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] p0nc:
Unfortunately i suffer the same as ssqw1. Although i have a P5110, running all the commands given by Android-Andi give me the exact same results.

Bottom line for me is, after flashing a new Slimrom alpha i got into an endless bootloop. Trying to install other roms didnt help. I then tried to go back to stockrom + pit file but to no avail. I can still get into recovery & download. The recovery performs its tasks (or so it seems) and after rebooting it goes back to the loadscreen of the slimrom. Even if i flash another rom, it still shows that logo. I have accepted that i have a dead p5110 (RIP). After reading the post from Jonathan i dont have alot of hope left. However i will continue reading up on this thread in particular and should you need any further info im happy to supply it.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Can you guys please check the eMMC details?

From an*adb shell:

su
cd /sys/class/block/mmcblk0/device
cat name
cat manfid
cut -b 19,20 cid
cat date

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

C:\Windows\system32>adb shell
~ # su
su
/sbin/sh: su: not found
~ # cd /sys/class/block/mmcblk0/device
cd /sys/class/block/mmcblk0/device
/sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0/mmc0:0001 # cat name
cat name
MAG2GA
/sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0/mmc0:0001 # cat manfid
cat manfid
0x000015
/sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0/mmc0:0001 # cut -b 19,20 c
id
cut -b 19,20 c
id
07
/sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0/mmc0:0001 # cat date
cat date
06/2012
/sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0/mmc0:0001 #
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Damn it... i will search, search and search...

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
A battery pull may work
[Galaxy Tab 2 Q&A, Help & Troubleshooting] kds1889:
same problem

Same problem withbme happened, i tried flashing firmware 4.0,4.1,4.1.2 from the sammobile website ,the new odin software after 6 version shows error while flashing the firmware,older odin flashes wothout any error but after reboot tablet wents straight to slimLP firnware,have tried flashing through memory card too,everything failed :(. Now i can't use it.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Please everyone tell the device, used recovery and eMMC info (s. one.page back)

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Just pushed a, hopefully, fix for that issue to prevent other devices from damage. Thanks to [MENTION=3208754]codeworkx[/MENTION]:

http://review.cyanogenmod.org/87902

https://gerrit.slimroms.net/24584

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] p0nc:
C:\Android\adb>adb shell su

/sbin/sh: su: not found

C:\Android\adb>adb shell cd /sys/class/block/mmcblk0/device

(nothing happens)

C:\Android\adb>adb shell cat name

cat: can't open 'name': No such file or directory

C:\Android\adb>adb shell cat manfid

cat: can't open 'manfid': No such file or directory

C:\Android\adb>adb shell cut -b 19,20 cid

cut: cid: No such file or directory

C:\Android\adb>adb shell cat date

cat: can't open 'date': No such file or directory

PhilZ Touch 6.25.0

Clockworkmod v6.0.4.7

P5110

Recovery & Download function can still be brought up.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] p0nc:
Perhaps it helps, enclosed.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] divyanshu.grover:
Same error CM12 ROMs

I'm regularly using your CM12 ROM for GT-P3100. Was on the 31 Jan build when this happened overnight. I also see lots of infinite empty directories in /data, and /system won't partition at all. Edit: Adb works now . Please find a solution Android-Andi.

Thanks in advance.

---------- Post added at 02:18 AM ---------- Previous post was at 01:48 AM ----------

E:\Android\sdk\platform-tools>adb shell mount -t ext4 /dev/block/mmcblk0p9 /syst

em

E:\Android\sdk\platform-tools>adb shell mount -t ext4 /dev/block/mmcblk0p10 /dat

a

mount: mounting /dev/block/mmcblk0p10 on /data failed: Device or resource busy

E:\Android\sdk\platform-tools>adb shell umount /system

E:\Android\sdk\platform-tools>adb shell umount /data

E:\Android\sdk\platform-tools>adb shell e2fsck -vf /dev/block/mmcblk0p9

e2fsck 1.42.9 (28-Dec-2013)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

1996 inodes used (3.05%, out of 65536)

8 non-contiguous files (0.4%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 1646

155702 blocks used (59.40%, out of 262144)

0 bad blocks

0 large files

1437 regular files

208 directories

0 character device files

0 block device files

0 fifos

0 links

342 symbolic links (342 fast symbolic links)

0 sockets

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

1987 files

E:\Android\sdk\platform-tools>adb shell e2fsck -vf /dev/block/mmcblk0p10

e2fsck 1.42.9 (28-Dec-2013)

/dev/block/mmcblk0p10 is in use.

e2fsck: Cannot continue, aborting.

Note: Also flashing any ROM + Pit (with reformat partition) in Odin does not work. Always get the following error.

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> system.img

<ID:0/003> NAND Write Start!!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] alfick3:
So, if I don't have that particular emmc, am I ok?

root@android:/ # cd /sys/class/block/mmcblk0/device
root@android:/sys/class/block/mmcblk0/device # cat name
M8G2FB
root@android:/sys/class/block/mmcblk0/device # cat manfid
0x000015
root@android:/sys/class/block/mmcblk0/device # cut -b 19,20 cid
08
root@android:/sys/class/block/mmcblk0/device # date date
time date -> 0.0
root@android:/sys/class/block/mmcblk0/device #
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Ashwin Prabhunerurkar:
here is my emmc log

root@espresso10wifi:/sys/class/block/mmcblk0/device # cat name
cat name
MAG2GA
root@espresso10wifi:/sys/class/block/mmcblk0/device # cat manfid
cat manfid
0x000015
root@espresso10wifi:/sys/class/block/mmcblk0/device # cut -b 19,20 cid
cut -b 19,20 cid
07
root@espresso10wifi:/sys/class/block/mmcblk0/device # cat date
cat date
03/1998
root@espresso10wifi:/sys/class/block/mmcblk0/device #

Even though my chip is working properly i noticed a strange thing that my cat date is 03/1998

I once had to reflash partition table For P5110 and wipe all partitions and reinstall stock rom when i was using Slim LP

I had the same bug like these guys are having that rom wont boot or wont format but luckily i was able to fix it

Is the 1998 part something to be concerned ?

i am using you build of cm12 and now everything is working preperly

I only faced that problem when i was on slim lp
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
New CWM recovery uploaded, it includes the kernel fix (recovery.img has it's own zImage).

New SlimLP roms and CM11 (stable tree) too.

For P51xx after sleep.

This bug can happen independent from the rom on MAG2GA eMMC (all 16GB models?).

I uploaded the fix for all roms now and will imclude it to all builds.

Afaik it should be safe with that patch, but i can't be 100% sure.

TRIM is enabled since 4.3 by default which means all roms, kernel and recoveries are / can be affected.

About the MAG2GA bug:

MAG2GA TRIM bug

Status:*possible fix available?*(unverified)

Fix type:*kernel workaround avoiding buggy functionality

About TRIM: http://en.m.wikipedia.org/wiki/TRIM

Send from OnePlus One using Tapatalk

---------- Post added at 01:08 AM ---------- Previous post was at 01:06 AM ----------

About already bricked devices maybe [MENTION=4243514]Hashcode[/MENTION] can help? I will try to talk to him, unfortunately he didn't response to me on hangouts.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] divyanshu.grover:
Here is my emmc log

cat name

MAG2GA

cat manfid

0x000015

cut -b 19,20 c

id

07

cat date

03/2012

Device already soft bricked since 2 days.

Found this on the CM wiki - http://wiki.cyanogenmod.org/w/EMMC_Bugs#MAG2GA_TRIM_bug
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
New CWM ready to use, recovery kernel patched.

Roms applied, the hopefully, fix for TRIM bug on MAG2GA eMMC (@codeworkx and [MENTION=4243514]Hashcode[/MENTION] told this looks good and should prevent from new issues):

- SlimKat 9.1

- latest SlimLp

- CM M12.1

Planned for new builds:

- Omni 4.4 & 5.0

- CM 12 & 10.2

- TWRP

- PhilZ Touch Recovery

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] souljhazz:
i have mag2ga emmc with my p5100 does this mean i might get the bug? im on slim lp with cwm 6.0.5.1 am i safe running on slimlp?, so far i dont have trouble s with the rom (20150129 2302 build ) just with the wifi therering , so if thats fix i could say rom is stable

do i have to use new cwm or apply any patch to apply new builds?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] ssqw1:
Will this work with already bricked devices? I tried flashing the latest recovery through odin, didn't work.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Nope

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] prdepune:
Details of my bricked (reboot loop) P3100

Hey Andi, thanks for all the efforts!

Here are my P3100 details. Same story of MAG2GA.

ADB output attached.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
It would be wise to flash ROM and recovery cooked after 2015-02-05

eMMC brick happenes suddenly and after that only motherboard replacement can help.

tetakpatalked from N7100
[Galaxy Tab 2 Q&A, Help & Troubleshooting] yomiguy:
What a horrible thing I'm reading here! I'm very sorry for all those mates losing their lovely tablets [emoji29]

I hope there won't be more lost! I'm pretty sure andi is doing all his best to get a good fix for this problem.

However as I don't manage really well with English I'd like to ask a few questions.

I think I've understand the brick happens when going back to stock roms? Or is it happening also with kit kat and lollipop custom roms?

Another thing is I don't know how to check my emmc with adb. What's adb and how could I check it?

And finally, I'm actually running slimkat 9 with last twrp recovery. Am I in danger anyway and should flash the new versions of my Rom and recovery as soon as andi brings them out? Or shouldn't I worry in my situation?

Sorry for so many questions, and I hope someone could answer them [emoji4]

Thanks! [emoji6]

Tapatalkeando
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
You can use terminal emulator instead:

Enter "su" to get root access

etc

tetakpatalked from N7100
[Galaxy Tab 2 Q&A, Help & Troubleshooting] yomiguy:
Thanks a lot mate! You mean "su" enter, then "cat name" enter and then check the result, don't you?

I will try as soon as I'm home! Thanks! [emoji6]

Tapatalkeando
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
First change directory, just like in post #27

"cd..."

After that enter "cat name"

(that's why I edited my post, but you quoted me faster)

tetakpatalked from N7100
[Galaxy Tab 2 Q&A, Help & Troubleshooting] yomiguy:
Wow! Thanks a lot mate! I've followed your instructions and I think I'm safe! [emoji4]

It seems I don't have the bad one! Do I?

Good luck for everybody! [emoji6]

Tapatalkeando
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
My idea of calling Andi was awesome. I saved many devices. So give a thanks to me too:).

And thanks ANdi
[Galaxy Tab 2 Q&A, Help & Troubleshooting] yomiguy:
LOL Thank you too! [emoji6]

This community is awesome! [emoji4]

Keep pushing!
[Galaxy Tab 2 Q&A, Help & Troubleshooting] ssqw1:
Yup, thanks to Andi. My tab's sacrifice wasn't in vain..
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
You're right :D

tetakpatalked from N7100
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
I also have MAG2GA, [MENTION=5153662]Android-Andi[/MENTION] :D

You will save my Tab 2 one more time!

(I hope it will survive one more flashing of SlimKat 9.1, PhilZ blackhawk and Omni.... it already survived at least 400 flashing processes, LOOOOOOL!!!!!)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] prdepune:
So, folks, does that mean I have to bury my Tab now? :(:(:crying:

I mean there must be some way. I don't think it is end of the road!

Having said that I am counting big time on Andi .. !!:D;)
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
Well, replacing the motherboard in Samsung service can revive it for sure. I would do that with mine, as I love my P5110.

Add a letter with printed list of foulty chips and eMMC brickbug and try to get the service costs for free. Contact service boss if the mice you contact with denies your costs claim on first try.

tetakpatalked from Nexus 7 flo
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
I have asked the developer of the app eMMC brickbug check (available here on forum or from the Play Store) to update the app, as the faulty chip MAG2GA is being displayed as sane.

tetakpatalked from P5110
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=5051515]tetakpatak[/MENTION] superbrickbug is a different issue, MAG2GA have TRIM issue.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Please boot your recovery and get some more information for me.

type:

adb shell
parted /dev/block/mmcblk0

Your output will look like this:

C:\Users\USER\Desktop\Andi>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.

Now type

p

Will look like

(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 ext2 HIDDEN

Now type

u s
p

Will look like

(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 ext2 HIDDEN

Type

q

to exit parted.

Type

exit

to exit adb shell.

Please attach a *.txt with the information for me here.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] ssqw1:
Here is the output. Hope you can develop a fix for the bricked devices!
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
So,

How to prevent bricking of my tab?

I am on slim lp
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
Our hero developer (Android-Andi) will build recoveries and kernels with included security patch. We need both.

tetakpatalked from Nexus 7 flo
[Galaxy Tab 2 Q&A, Help & Troubleshooting] shsagnik:
Ok will wait for new twrp
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
Latest CWM and all.new roms include the commit already. Still some stuff need to be recompiled, but no time until sunday late evening to continue.

Send from OnePlus One using Tapatalk

---------- Post added at 06:29 PM ---------- Previous post was at 05:41 PM ----------

I might have an idea, just talking to hashcode about it.

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=4800883]ssqw1[/MENTION] , [MENTION=1181770]prdepune[/MENTION] , [MENTION=6387160]kds1889[/MENTION] , [MENTION=5018170]p0nc[/MENTION] , [MENTION=5497042]divyanshu.grover[/MENTION]

Can everyone of you please again tell me your:

- last used rom before the issue started

- used recovery + recovery version number

- eMMC info

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

Send from OnePlus One using Tapatalk
[Galaxy Tab 2 Q&A, Help & Troubleshooting] ssqw1:
Rom: SlimLP alpha 0.92

Recovery: CWM 6.0.4.5

Device: GT-P3100 16 GB

Emmc info in the attachment.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] divyanshu.grover:
ROM: CM12 by you, build 20150130

Recovery: TWRP 2.8.4.0

Device: GT-P3100 16 GB

EMMC: MAG2GA

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

This is the output from the e2fcsk scan and mount commands you posted, and wanted to know if there is any error.

E:\Android\sdk\platform-tools>adb shell mount -t ext4 /dev/block/mmcblk0p9 /syst

em

E:\Android\sdk\platform-tools>adb shell mount -t ext4 /dev/block/mmcblk0p10 /dat

a

mount: mounting /dev/block/mmcblk0p10 on /data failed: Device or resource busy

E:\Android\sdk\platform-tools>adb shell umount /system

E:\Android\sdk\platform-tools>adb shell umount /data

E:\Android\sdk\platform-tools>adb shell e2fsck -vf /dev/block/mmcblk0p9

e2fsck 1.42.9 (28-Dec-2013)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

1996 inodes used (3.05%, out of 65536)

8 non-contiguous files (0.4%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 1646

155702 blocks used (59.40%, out of 262144)

0 bad blocks

0 large files

1437 regular files

208 directories

0 character device files

0 block device files

0 fifos

0 links

342 symbolic links (342 fast symbolic links)

0 sockets

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

1987 files

E:\Android\sdk\platform-tools>adb shell e2fsck -vf /dev/block/mmcblk0p10

e2fsck 1.42.9 (28-Dec-2013)

/dev/block/mmcblk0p10 is in use.

e2fsck: Cannot continue, aborting

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

If you need the parted command output, let me know. Edit: parted doesn't seem to work in the TWRP terminal

Thanks for trying to build a fix.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] PanchoPlanet:
Is this issue (brick) something related to a chip or was is something that was cooked in the rom having to do with lollipop 5.0 that affected these particular chips?

I have a P5113 since first launch, I ran stock rooted until Samsung stopped updating firmware and after went to CM10.1, over past two plus years this is the only os ran on this tab with no issues what so ever. Never ran any other builds or custom roms, until January when I flashed CM12, figured CM had played nice for so long, well that only lasted about 2 weeks, picked up tab and it was dead, no response from any buttons, plugging charger showed 75 % charge, holding down buttons got into CWM and restored last CM11 b/u.

Tab restored but was acting weird and some apps that where working properly on CM12 would not work or start, tried re-install on apps but still wouldn't work.

List of apps :

Pandora

Plants vs Zombies (only game on tab)

Yahoo Sports

You tube

Romtoolbox Pro

After trying several uninstalls and installs without any success, I opened recovery and re-flased CM11 and gapps with a factory reset just to clean up, after re-flashin all was good, all apps started working and all appears to be back to normal as in CM11 (before CM12 ).

This is it for this tab, as far as flashing goes.

Don't think this platform is capable of digesting lollipop, kitkat ok, lollipop is too much for this old platform.

For now my tablet will just stay the way it is and working until it the battery gives up, at that point will replace with current Galaxy Tab ? whatever that is ,6,7,8 ?

Pp.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tetakpatak:
Exactly, buggy chip. Samsung's biggest speciality (i9100/S2, i9300/S3, N7000/Note1, N7100/Note 2, few other phones as well and now obviously also our Tab 2)

I think meanwhile that they do this on purpose.

I will change my battery in service if it dies and the tab is otherwise still OK. But are you sure you want to buy Samsung again? I am not so convinced of their new philosophy, Knox, customer service policy and regularly sold tenths of millions of faulty chips.

I don't think I will buy any Samsung again. I have now switched to Nexus and OnePlus One and they are IMHO even better devices than Samsung in terms of hardware quality, besides all mentioned above.

tetakpatalked from Nexus 7 flo
[Galaxy Tab 2 Q&A, Help & Troubleshooting] manardj1:
Actually, a lot of the buginess after the restore was probably due to a pre-lollipop recovery. I had similar issues until I updated my recovery.