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.
Related
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
Hi All.
So I'm not new to rooting / ROMs (nor am I an expert, as you'll see), but somehow have totally screwed up my tab. I've now honestly done so many things to try to recover, that I couldn't begin to summarize how I got into this mess, but I'll try.
Model is GT-P5113. Most recent working ROM was SlimLP 5.1
I went to flash CM12.1 (using CWM) and God only knows what happened. After it flashed, I tried to reboot and it would only go to CWM recovery. If I chose to reboot device, it would only shutdown, not reboot (This was actually one of the issues I was having with SlimLP as well, so I don't think the flashing had anything to do with that???)
After many attempts at reinstalling CM and SlimLP (I used the same Zip that had worked previously with SlimLP, and the flashing would say installed) it would still only boot to recovery. I finally said, screw it, I'll just start completely over
So attempted to go back to stock 4.2.2 using Odin3.09. Got the stock ROM off SamMobile site. ODIN seemed to flash,but again when it would go to reboot, it would just power down and a charging battery would show up. So I would unplug from the computer, push power button. When it powered up, it would say Installing system update, then after the status bar moved a bit, it would say Error and shut down. When I restart, it very briefly says installing system update, then show the dead android with a red triangle and No Command, and it would boot to the stock android system recovery (I assume CWM was taken off in the process). In yellow, under the stock recovery it says
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
I've tried installing the other ROMs again, this time with TWRP, but only for it to boot to recovery after the Samsung Tab 10. 1 logo.
I have no clue where to go from here. No clue if I'm still rooted (doubt it). At this point I don't care. I just want a functioning tab. I've spent hours searching, but nothing works. I'm open to any / all ideas.
Thanks
Aw, show me a little love, bros. Someone' gotta know something. I'm not above begging / pleading.
I can give more info, less info, post somewere else. Just let me know,and help me resuscitate my tab.
thanks again!
Hello everyone!
This is my first post here, and I have a problem with my phone.
It is Highscreen Boost II (russian one, you didn't maybe even heard about it). Google for it...
The main problem is that the phone started to act strange one day. Example: I unlock the phone, start opening my apps (Fb, Insta, Viber...) and after a few minutes it just restarts by them self. I also tried to turn OFF the Internet connection, but all the same thing.
The phone is rooted, and it have CWM recovery. And here starts the funny part. XD
When I go to CWM, i go to factory reset, it all done right, it says "successful" on the, but what is the strange part, that it just takes like 5 sec. to do the "reset". When I press reboot system, it reboots the phone, but nothing even changes XD.
I also tried, flashing new ROM, it says that is all done, but when I restart the phone, it just came back on the previous state that it was before. The other funny thing is that, the phone keeps go back, on the same date (~20. February 2017). I fix it manually in the Date and Time settings. I also tried in CWM, to go to Mounts and Storage, and doin' from there format of the SYSTEM, and than flash the ROM, it flash it for 10 sec. Reboot and all the same stuff. I even tried Mount /System and than Format it, i tried to format everything, but without success. It just says the CWM that is done, and nothing else...
Than, i tried to flash the Stock Recovery (it can be flashed from the CWM), it says that it's flashed, than when i try to reboot the phone in the Recovery mod, again it comes back with the CWM, so in fact, nothing has changed in the end. I also connected the phone with the ADB connected to the PC, entered in Fastboot mod, Booted in the STOCK RECOVERY (live boot - to say...), using the commands in the terminal, it successfully boot up the stock recovery, than i tried to do the factory, cash and all usually necessary before flashing the Stock ROM, after that, i flashed the ROM (from the ZIP file, SD card...), again, it was very short time, saying that it was successfully installed, restarted the phone, and imagine it all works good
-\ Nah', just kidding, it is the same thing again, all the same, not even changed the Recovery, the ROM, nothing... I also tried flashing the Custom/Stock ROM thru the commands on the PC, it says DONE on the end, and all the same, nothing...
After all that, i decided to restore the phone with other ROM (to say) in the way to go to the DFU mod (pressing + and - and Power button together), so i enter the phone in Download mod (to say). In that way, once (2 years ago) i recovered my phone from Hard Brick, since i deleted the partitions and all that stuff....
Than, i decided to flash the ROM from the DFU tool (Innos Upgrade Tool) - from here i was following the instructions, and doing all like before. It is connected in the device manager, and detected as DFU android phone (something like that), as it should be. When i try to format the partitions, it just crashes, or when i try to flash the ROM, it went to 100%, and doin' nothin' I even tried to reboot, and all, all over the same thing...
I want to add, that, i remember that on that date ~20. February 2017 When it always return to that date/time over and over again, that on that day, i re-flashed the ROM, because my system started to crash from itself... So by flashing the ROM from CWM only, it works fine, and didn't lost any app, i mean didn't needed to install all apps that i am using...
*The phone is running fine if i don't use it non-stop, i mean if i start to go in my settings, and click too many times, it will just reboot and go back on that date/time state... I am using it only for calling and sending some SMS. Nothing else...
*My 70% of the apps, we're on the SD card moved, trough the Link2SD app (root), so i cannot uninstall the apps that are here, neither i put the SD card IN.... This doesn't matter. But another thing is that, if i for an example took a Photo, add contact in the phone book, send SMS, call someone, after restarting the phone that data/info/sms/photo is not there... It acts like it is in the cash memory, something like that... It just all looses and starts over again, from the same date, and time.
My opinion is that the phone, somehow... that the "NAND" memory chip is death (just an example)... Something like the BIOS CMOS battery on the PC's, that is dead, and cannot keep the changes, after rebooting the phone, so it goes back on that time when it was last time in "good condition".
I really don't need the phone anymore, but it would be nice for an backup option to have it fully functional.
I want to hear your opinions, did you ever met a problem like this before? If you did, what did you did/fixed it?
For me this is kinda funny, because i never had/saw a problem like this before. So i don't know should i cry or laugh around... XD
Thanks.
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.
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet