SM-T320 stubborn to power on, then bootloops - Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble

A few weeks ago, my Tab Pro 8.4 started bootlooping. I did a few cache/dalvik wipes and got it going again. I think I reflashed the ROM and GApps also.
Now It is doing something odd. If I leave it plugged in overnight, it powers off. It takes a very long (20 second) power button hold to get it to wake. That woke it in the past, but today is something new. Now it is going into a bootloop. During the boot animation, it stutters, freezes, then goes back to the bootloader splash page (the one with the "seandroid enforcing" and "warranty bit" message on top).
It has no issue going into TWRP and I have just done a full backup. I am going to go back into TWRP and make a copy of internal. I have a few files in there that I don't want to lose.
Could this be a ROM issue? (I will update ROM info after next time I am in the device/TWRP) Hardware? I just installed a new battery, but this issue started with the old battery. Any ideas on how to get this revived?

Related

[Q] Stuck in first screen bootloader

So, I flashed yesterdays CM10.2 and had no problems, up until today. I was in class, using twitter, set the phone down, and looked back at it 5 minutes later to find it shut off. I restarted it, figured no big deal, it turned off again. I thought there was a problem with that nightly so I flashed back an older, more stable one(still 10.2). It booted up, and shut off again. Now, though, the phone boots up, shows Samsung, then shows the GS3 and CM logo, then just goes into a loop from there. I went to recovery and tried to wipe, which, oddly, the phone restarted again. Luckily I was able to get in and wipe data before a new reboot, but even that didn't fix it. I rebooted into recovery again, and it said something like "root access available" and asked me if I would like to use root, which I didn't get the chance to fully read because it restarted again. When I am able to successfully boot into recovery though, I get a warning saying "no file_contexts", this could be it?
I've already tried to flash back stock Touchwiz with Odin, but it keeps failing to do so. Any help with this?
EDIT: After successfully booting up a CM10.1 backup, I've begun to believe the power button is broke, because the power menu will randomly popup, followed by a shut down.
It's called SDS sudden death syndrome it's very common on the S3. It's a failure of the power button. It's a defect. If your phone is newer than a year old put it back to stock and take it to sprint.
Remember search is your best friend, Have a great day!

[Q] Phone turns off automatically

I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.
Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.

Soft-Bricked M9

I've had an M9 for 2-3. After the first year I got my phone, I installed a custom recovery and rooted it but later uninstalled root and custom recovery. It has been fine ever since except recently. Last month, my phone randomly crashed for the first time and got stuck in the infinite bootloop. It was as if everytime it tries to boot up, it crashed during it. If I hit the power, vol up, and vol down button, I make it to the screen with the option to go into recovery, download, etc. But when I actually try to go into either bootloader, recovery, or download mode from that menu, it crashes and goes back to the white htc logo. I've have gotten the phone to bootup a couple times by leaving it in the freezer as it tries to boot up but after using it for 1-5 minutes, it crashes again. If I don't use the phone at all, then it usually wont crash. After a day or 2, the phone fixed itself. Then one morning, my notifications got stuck together and my screen became unresponsive. So I took my death sentence and restarted my phone and now my phone has been doing the same exact thing for a week. I don't know how to fix this problem because getting it crashes trying to go into recovery and trying to do a factory reset is risky since it could crash during the reset. If also manage to make it into safe mode thinking maybe an application or virus is causing this but the phone crashed in SAFE MODE so I don't know what the problem is. I doubt there is any saving this phone because is probably a hard ware problem but who knows. Any help would be greatly appreciated!! Thank you.
Flash back to stock. Stock firmware fixes all sorts of issues.

Suddenly corrupted system, lit blue LED, fastboot only

To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.

Stuck in too-low-power-to-boot state (bricked?)

Hello!
After recently getting my hands on an old Samsung A50, I thought I might as well reflash and do some stuff with it.
After installing Orangefox and Lineage, everything worked fine until the phone eventually ran out of power.
I plugged it in and let it charge for a bit, but it was just constantly showing the gray circle with a charging/power icon in it, but no battery indicator.
This usually means that the phone is completely empty and has to charge a bit before booting.
After letting it sit for a long while and nothing changing, I got a bit worried.
At this point, unplugging the phone does not change anything - it will continue showing the indicator even while unplugged.
Holding power and volume down (or power + both volume) briefly blacks out the screen, but it simply comes back to the indicator a few seconds later.
All of this happened a few days ago - I eventually got it to boot again through some key combination while the screen blacked out, sending me to orangefox or download mode (i dont remember),
from which I was then able to boot into lineage again. In lineage, everything worked fine again, including the battery indicator which showed that the phone was full, and the battery seemed to work completely fine.
After that, I turned from lineage to Fresh, which also ran fine until Fresh wanted to install an update which sent me to TWRP. Not sure what to do, i just booted back into System which worked fine, but the Fresh update hadn't succeeded.
I attempted to update again and this time shut down from TWRP - big mistake. Now i am once again stuck in the low-power indicator.
I believe that last time i escaped by booting into orangefox - but i think fresh replaced orangefox with twrp?
Anyway, i tried holding different button combinations while the screen is briefly blacked out but nothing is happening (also tried getting into download by plugging into pc, holding power+volumedown, then holding volume up+down while screen is black).
I also let the battery empty itself until it went black by itself and then tried again, but no success.
I'm now again unsure what to do. How do i unbrick this to boot into the OS again? How do i prevent this from happening again?
Thank you all.
Same issue with my Redmi 9, it seems a battery issue idk if i had rekt mine after flashing a latest CN rom then after not being satisfied tried to flash thru recovery to its stock rom and it went bootloop. Fixed it by flashing with SP flashtool and some bypass stuff, but damage has been done with my batt. Maxing out the volume when I try to play something video or music would trigger a reboot to my phone.

Categories

Resources