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.
Related
Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.
Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.
You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.
I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.
If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.
To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.
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! So, my father's old Samsung Galaxy Tab 2 10.1 P5110 (bought 5 years ago) has gotten into a bootloop. It's an odd case. Basically, it's like the device is completely read-only.
To describe the symptoms:
It boots into the OS, but after 30 seconds or so it suddenly restarts. The device cannot be turned off (it just reboots and reboots and reboots...), so it empties the battery if left unplugged.
I can enter download mode and recovery mode, where the device is stable.
The device is not rooted.
I tried to flash it with TWRP recovery (it worked on my mother's tablet; exact same model, but no problem like this), but the recovery mode is always unchanged. I've flashed with Odin 1.8*, Odin 3.0*, and latest Heimdall; it always completes, but nothing changes. I've learned about having to boot to recovery after flashing due to a script replacing custom recovery, but even when I go directly to recovery mode, it's the same old stock recovery.
I decided to try another approach, by uninstalling apps during those short 30 second intervals of functioning OS; I got to uninstall one app (AVG anti-virus software), but after the reboot, the app was installed again.
I tried to go into recovery mode to do "wipe data/factory reset" and "wipe cache partition", but even that did nothing! Everything is where it was.
I can use ADB in recovery mode, so I tried to see if I could do some damage there, but the tablet is unrooted, and no rooting works either. (Tried rooting with Odin and "apply update from external storage" in stock recovery.) Couldn't find a writable directory to upload a su executable into either.
Just now I finished a 90 minute flashing of some Chilean stock firmware -- although I'm Swedish -- to see if that made things "rewritable", but guess what? All the old apps and files and settings were still there, in Swedish.
At this point I'm starting to suspect that I could hit it with a sledgehammer and it would just return to normal after a minute.
My father is not poor (just a bit cheap!), so buying a new tablet isn't a big deal, but I'm ostensibly a computer engineer...ing student, so it feels like a surrender to leave it unsolved. What might be the problem? Can memory in these devices become read-only due to some hardware fault?
Risky suggestions are welcome. If it's bricked, that's no problem.
EDIT: Whoops! My father ordered a new tablet; I was still going to experiment on the old one, maybe get it working again, but it seems that he went and tried the sledgehammer mode on it. But what happened is still an open question.
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Maybe a battery issue?
a friend just gave me his very same model phone with the very same issues.. if I find out anything I'll tell you here, or if you solve it first please write down what you did.
Thanks Vibbuz.
I've been trying to download a stock firmware to flash via Odin, but download speeds from Updato are really bad.
So I managed to flash a firmware after installing Odin on a Windows laptop (painful trying to get it to work on my Mac)
Firmware installed OK, but after boot I was getting a constant "com.sec.epdg" pop-up box that wouldn't let me use the phone at all. Not sure if that's due to the tsar3000 firmware?
Wiped the cache and did a factory reset after booting into recovery, and now it's stuck in a boot-loop again (95% of the time it hangs at the Samsung logo animation)
Just tried using SamFirm v0.3.6 to find the correct file. Downloaded a 4gb file, but several attempts to extract only gives BL, CP, CSC files but no AP (throws up an Unknown Error during process).
So still stumped!
Yet another update. Left Updato running overnight and downloaded a firmware.
Flashed it with Odin, claims to have succeeded but phone then reboots and hangs at "Erasing" stage (Android logo is spinning, then stops)
I'm starting to think it's pretty broken...
I've been having this exact same issue since June. If your phone happens to boot try activating power saving mode (to reduce cpu speed) as soon as possible.
It seems that doing that diminished the frequency in which my phone rebooted. If it also helps you it might be a faulty battery that can't provide enough voltage. (I'm not 100% sure on this part though, just thought of it because of the apple batteries drama)
Please post your results! Looks like a lot of people are affected by this and it would be great if we could find the cause of the problem.
I just read your thread actually! Sounds very similar to mine.
I've got nowhere. I don't think it's hard-bricked as I can still access Odin mode on the phone, and sometimes boots to Recovery, but it freezes and various different points and is currently unusable (either freezes at Samsung logo, "Erasing" part after installing firmware, or once it started to run though new device setup then froze).
Went ahead and bought an S8, but still want to fix the S6!
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Does it have twrp? Try a non stock ROM and kernel
So did anyone manage to find an issue in this rebooting. I am having the same issue.
damir_nis said:
So did anyone manage to find an issue in this rebooting. I am having the same issue.
Click to expand...
Click to collapse
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Hello,
anyone found some kind of solution? Happened to me also - freezing, restarts and then my S6 stopped working.. Sometimes I can boot to recovery menu, sometimes it boots up to android (and then freezes again), but the chances are almost non existing. Service man told me the same thing as @ghasemzm - eMMC failure. Yes, it is completely possible, but i don't wanna believe it, because they only tried to reflash the rom. I've made some "google research" and found that there were some issues in power IC on S6/S6E. Could this be related to it?
ghasemzm said:
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Click to expand...
Click to collapse
Will test the theory and let the group know.
So i have installed philipines latest update 6.0.1 i think with PIT file provided on Sammobile.
I have tested it for a day with normal ussage like i set up every other phone and it still continued restarting.
Figured out let me test with no google account signed in and the phone is working perfectly. For a full day.
So i dont know what the problem is but i will try again with google account tomorrow for a day see what happens.
After that will install 7.0.1 uk update with PIT file for it and test with that.
I have the same problem and I am quite sure that it is the mobile hard drive.
I tried to use F2FS but didn't find a working rom for that.
Samsung refused repair because of root.... Never Samsung again!
same issues here - any solutions found? My best guess is hardware fault...
Objective: I am hoping to be able to boot my existing system to recover data such as SMS, call logs, app data, and so on - obviously it was inadvisable to start messing around without backing up my data, particular with my amateurish capabilities. But that's the situation I am in. For some reason I thought that just replacing the Recovery was not going to risk my data. Its been over 5 years since the days when I would regularly flash my new phones with cyanogenmod, and my abilities were very basic even then.
Context: G930FD with stock rom, baseband ETC? - apparently for Dubai, which does not allow VoLTE or WiFi calling, which is what I was trying to fix when I got myself into this.
the Events:
- I enabled ADB and used Heimdall on Windows 7 to flash twrp-3.3.1-0-herolte.img
- initial attempts failed to complete download. I booted back into the system and applied OEM Unlock. Flashed successfully.
- chose the 'allow modification' option or whatever it says, not the Read-only option
- I did NOT check at that point to see if the system would reboot properly. I instead right away made a full back-up to my external SD.
That's all I did. After the back-up was complete I rebooted, and arrived at "SAMSUNG Galaxy S7" endless boot loop.
best guess: this is related to samsung encryption? TWRP file manager says that DATA is 0MB.
Again, I am desperately hoping that someone can help me recover my existing system. The threads I found on this subject all lead to wiping the phone and flashing a new rom.
thanks.
digging in deepr
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
t.krug said:
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
Click to expand...
Click to collapse
Reflash TWRP with Odin, boot TWRP, wipe cache, reboot.
Thanks.
I think greenman at sammobile had the answer --> NEW: S7 5 file firmware options (this forum wont let me post a link).
But I botched the execution and the CSC file overwrote my data. Crushing blow. I would say lesson learned, except that I already knew better and risked my data anyway. Sad.
I have a backup I made at the first launch of TWRP - but I assume its worthless since TWRP was not reading the encryption. Its only 3.7GB.
Side note - I did achieve the original goal of replacing the Emirati rom with one that activates WiFi calling and VoLTE.
Has this issue been solved?
I never recovered my data if that's what you mean. Did you look up greenman at sammobile? It sounds like someone followed his directions and was able to flash just the system files without overwriting their data. I think you had to modify the csc_home file. It was a bit beyond my skill level.
Oh, I was just wondering if your phone was still bricked. I didn't read your last message properly before replying lol. My bad.
I'm not personally having issues with a device, I was just curious if I could help at all.