Hey all. I'm trying to salvage my mother's Samsung Galaxy Tab 2 10.1 GT-P5113.
U.S. market Tab 2 GT-P5113 with original factory ROM started intermittently bootlooping. At times would successfully boot and operate briefly but then reboot on it's own. Executed wipe process a few times but completed without success. Odin flash completes successfully on most attempts. STILL just BOOTLOOPS! Looking for a reputable service center to replace the memory.
It's been suggested that the 16 GB Tab 2 have a known faulty EMMC (MAG2GA) issue. It can happen, that your EMMC get “read only”, so you can’t perform any write actions or format anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device lifetime is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a reboot
Formating the storage doesn’t work (after reboot the old rom and apps are back)
You can flash whatever you like via Odin - it shows “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)
… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do easily at home yourself). In some bad cases you need to find someone who can replace your EMMC.
Related
Hello everyone,
my Moto G came finally yesterday. I immediately proceeded with factory reset -> upgrade to Kitkat v4.4 and tried to encrypt the device prior to installing the apps and configuring the phone. However, during encryption, i lost power source for a while (20sec). Moto has never finished encryption task and now, i'm not able to boot anymore. After booting the phone, after i enter SIM pin and then decrypt PIN, moto g just displays green android cartoon for a second and then hangs with blank little-backlighted black display. I can go to fastboot menu, however, none of the options (Normal, Factory, Recovery) works, they always lead to the same blank black display....
It looks that it's seriously bricked, anyone knows if there is a chance to fix this? Device has not been unlocked neither modified in any way....
Thanks in advance for any help,
P.
If it's Booting then it's not fully Bricked ...
Most probably the power cut happened during system read/write operation and has corrupted the /System or /Boot Partition, And I guess it can't be fixed easily .
But the good news is that you can take it to Service center and tell them that this happened all of sudden during update (you can skip the power failure part ) , and they will either repair it or most probably give you a new device !!!
So just chill and take your device to service center ASAP !
The "A" Factor said:
If it's Booting then it's not fully Bricked ...
Most probably the power cut happened during system read/write operation and has corrupted the /System or /Boot Partition, And I guess it can't be fixed easily .
But the good news is that you can take it to Service center and tell them that this happened all of sudden during update (you can skip the power failure part ) , and they will either repair it or most probably give you a new device !!!
So just chill and take your device to service center ASAP !
Click to expand...
Click to collapse
thanks for your answer. i just wonder if there is any other way how to fix it manually. I'm completely disappointed with this Kitkat encryption process. If the ecnryption would have been caused by the short power outage of phone even the device was fully charged, it's really shameful...
Anyway, I bought it from Amazon in US and it's not being sold yet here in Slovakia so not sure if the international warranty will apply or if they will be able to fix this model here.. Definitely will try to ask at least.
Issue fixed using Motorola great support - Only thing that needed to be done was to perform external reset by following https://motorola-global-en-uk.custh..._id/96459/p/30,6720,9050/kw/reset/action/auth
perfect, issue solved, gonna encrypt again
reset
Interesting bookmarked that link may come in useful some time.
I am probably facing a very common issue, please clear my doubts regarding the issue. I have flashed my tab with cm10.2 and used it for about a year, then switched to cm11 nightly. 2 months ago i flashed TWRP and unofficial cm12 and my tab became weird. Boot loops, over heating were the symptoms. I did a wipe switched back to cm11. It was fine for few hours and then all apps and process started failing, my tab went into 3 min boot loops. It would over heat and go on and on until the battery gives out. I thought I can fix it, but the recovery was gone. When I go into recovery mode it just stays on Samsung Logo. I can access download mode, so I tried to flash cwm recovery, odin prompted PASS but the 'Custom Binary Count' stayed 2, I tried with TWRP, same, odin says PASS but counter stays the same. I searched for similar issues here, and found that the cause might be emmc bug. So my tab is in a read-only state. To verify that I tried creating folders in the 3 min boot loop sessions, it was gone at next restart. Being convinced that my tab is dead or the read-only state made it an invincible brick I deleted the system folder. It crashed, but when I restarted everything was normal.
So is it emmc related issue? Since my tab is in read-only state all apps are crashing, I tried installing new apps and it never succeeds, there are no JTAG services nearby, also I need to be sure if it's the superbrick bug or a hardware fault. Please provide me some clarification. I can try experimenting with it as I have recovered my data. If it can be fixed then it would help other tab owners as well. Any ideas, clarifications or instructions are much appreciated.
Thanks
Note : It all started after I flashed twrp-2.8.7.0-p3100.img and unofficial cm12 by Android-Andi. I flashed the rom knowing the risks and Bricking my tab is my fault not the rom-builder's.
anshu_6187 said:
I am probably facing a very common issue, please clear my doubts regarding the issue. I have flashed my tab with cm10.2 and used it for about a year, then switched to cm11 nightly. 2 months ago i flashed TWRP and unofficial cm12 and my tab became weird. Boot loops, over heating were the symptoms. I did a wipe switched back to cm11. It was fine for few hours and then all apps and process started failing, my tab went into 3 min boot loops. It would over heat and go on and on until the battery gives out. I thought I can fix it, but the recovery was gone. When I go into recovery mode it just stays on Samsung Logo. I can access download mode, so I tried to flash cwm recovery, odin prompted PASS but the 'Custom Binary Count' stayed 2, I tried with TWRP, same, odin says PASS but counter stays the same. I searched for similar issues here, and found that the cause might be emmc bug. So my tab is in a read-only state. To verify that I tried creating folders in the 3 min boot loop sessions, it was gone at next restart. Being convinced that my tab is dead or the read-only state made it an invincible brick I deleted the system folder. It crashed, but when I restarted everything was normal.
So is it emmc related issue? Since my tab is in read-only state all apps are crashing, I tried installing new apps and it never succeeds, there are no JTAG services nearby, also I need to be sure if it's the superbrick bug or a hardware fault. Please provide me some clarification. I can try experimenting with it as I have recovered my data. If it can be fixed then it would help other tab owners as well. Any ideas, clarifications or instructions are much appreciated.
Thanks
Note : It all started after I flashed twrp-2.8.7.0-p3100.img and unofficial cm12 by Android-Andi. I flashed the rom knowing the risks and Bricking my tab is my fault not the rom-builder's.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63868220&postcount=27
It's strange that this has happened mostly to the tab 2 owners, even those who were at stock rom, and changed nothing in their tab. So, it's not rom developers mistake neither its yours. Blame it on the emmc and Samsung.
QUOTED Android-andi "All latest Roms & Recoveries have MMC_CAP_ERASE disabled kernel side, to
prevent 16GB Tabs from damage because of
MAG2GA EMMC which is known for TRIM BUG."
http://wiki.cyanogenmod.org/w/EMMC_Bugs
If this is true, the latest versions you have the better.
I too have been keeping my tab updated and never gone stock again after upgrade.
billysam said:
http://forum.xda-developers.com/showpost.php?p=63868220&postcount=27
It's strange that this has happened mostly to the tab 2 owners, even those who were at stock rom, and changed nothing in their tab. So, it's not rom developers mistake neither its yours. Blame it on the emmc and Samsung.
QUOTED Android-andi "All latest Roms & Recoveries have MMC_CAP_ERASE disabled kernel side, to
prevent 16GB Tabs from damage because of
MAG2GA EMMC which is known for TRIM BUG."
http://wiki.cyanogenmod.org/w/EMMC_Bugs
If this is true, the latest versions you have the better.
I too have been keeping my tab updated and never gone stock again after upgrade.
Click to expand...
Click to collapse
Yeah, this TRIM bug appeared like an epidemic. I guess JTAG is the only option or the emmc in my device has reached it's end. I think it is time to put my tab to rest. Thanks for the link billysam.
I can access the shell even when my device is off. The device connects as OMAP4430 USB Device for a second and vanishes, after that in "Device Manager" it shows as "Samsung Android adb interface", though the internal storage can not be accessed this way, but I can see the filesystem, is there anyway to change the readonly mode so that I can attempt some sort of way to recover my tab?
Hi, i have samsung galaxy tab 2 (P5100) with no root. It started to restart 5-10 seconds after android starts... (i dont have time to go the settings or to do something before restart).
I tried to clear cache and factory reset from recovery but it doesnt work. (in recovery it shows done but when i reboot system, no changes are made)...
I also tried to flash new stock room with odin but it failed every time ( i use different versions of odin, different rooms and different pits). it fails after NAND write or system.img.
Im also not able to flash new recovery... in odin it pass but when i start recovery mode there is no change...
Does someone have similar problem? Im afraid that it could be problem with motherboard or memory.
In recoveory i see this error:
# MANUAL MODE #
--Appling Multi-CSC...
Aplied the CSC-code : ORS
failed to compare '/system/csc/common/system/app/MH_10_TCS_Tablet.apk' '/system/app/MH_10_TCS_Tablet.apk' (no data available)
Thank for any help.
Your tablet may have the emmc bug, sorry but only a mother board replacement or emmc firmware update will fix it
Same problem, not yet solved.
I also have a samsung tab 2. We bought it around 2013 and started to have problems around 2015. My device started to reboot out of nowhere, infinitely, randomly. I tried to look for patterns. Couldn't find any. But i noticed something, it's stuck on it's current state. When i do things like install an app or take/delete pictures, when it restarts, everything i did would be gone and it's back to it's "current state". App that i installed? Not there. Pictures i've taken? Gone. Pictures i've deleted? It's there again. Even a hard reset won't do anything. When i do a hard reset and it reboots again, guess what, back into it's "current state" again. I've read about it on some forums, i think it's hardware related. Emmc. A notoriously bugged chip, where when you clear your cache or flash it with a new os or something like that. Boom! Brickbug. I tried sending it to the samsung dealership where i bought it. They checked it. They said the motherboard needed to be replaced, which was very expensive. I'd rather buy a new one. Now it's 2018, i'm hoping they've found an alternative to fix this tablet.
Like others, the OTA Nought update hard bricked my phone while continuing to freeze recovery menu. I have used Odin to flash the original rom but it remains in a bricked state (recovery menu freezes after 1/2 second rendering the buttons inoperable and freezes in the Verizon logo during boot). I have my Bitcoin block chain and important documents on this device that had just transferred an hour before the forced OTA rebooted the phone and am hopeful I can recover them. I don't care if I destroy the phone in the process but I would really like to recover my blockchain.
Can anyone confirm or deny whether the internal UserData, which now appears to use the new faulty UFS 2.0 over the older but reliable emmc is encrypted or if it can be manipulated through jtag or an emmc reader? I have the Allsocket reader for emmc chips but UFS is foreign to me.
If there is another possibility using an on-Chip method, I would also like to hear about it. Note that the Verizon version has a locked bootloader so I cannot install a custom recovery.
Who's THE BEST resource for tablet repair?? GTP5113 w/faulty EMMC "End of Life" issue
Hey all. I'm trying to salvage my mother's Samsung Galaxy Tab 2 10.1 GT-P5113.
U.S. market Tab 2 GT-P5113 with original factory ROM started intermittently bootlooping. At times would successfully boot and operate briefly but then reboot on it's own. Executed wipe process a few times but completed without success. Odin flash completes successfully on most attempts. STILL just BOOTLOOPS! Looking for a reputable service center to resolve.
It's been suggested that the 16 GB Tab 2 have a known faulty EMMC (MAG2GA) issue. It can happen, that your EMMC get “read only”, so you can’t perform any write actions or format anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device lifetime is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a reboot
Formating the storage doesn’t work (after reboot the old rom and apps are back)
You can flash whatever you like via Odin - it shows “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)
… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do easily at home yourself). In some bad cases you need to find someone who can replace your EMMC.