TWRP freeze on system reboot - Galaxy Tab S Q&A, Help & Troubleshooting

TWRP works fine while installing everything, wiping, etc. But when it comes to exiting, rebooting, etc, it freezes on the spot (the reboot button is highlighted but doesn't do anything.
Im using a tab s 10.5 LTE.

I have this issue too. It doesn't happen every time I reboot but when it does I just hold Home+Power+Volume Down to reset it.

I did that
And it solved the problem. Thanks mate

Just HOME + VOL DOWN

Related

[Q] sync-problem on 3.4.2-117 UK Froyo

I upgraded from 2.51.1 to 3.4.2-117, and the phone lags, seems to me that it is because of the google sync. Someone posted the very same problem and said that factory reset solved his problem.
My problem is that the phone does not do factory reset, in Privacy I press the erase button and nothing happens.
I tried to boot into recovery, but I can't get into it. The droid comes up but upon touching the lower right corner nothing happens.
When i try to boot with vol up and down same time, the phone boots into safe mode.
How shall I get into recovery so I could do a wipe? The phone is basically unuseable now because of the lags and freezes
Hey mate! Don't give up. When you see the droid in the center of the lcd just push vol+ and vol- at once. You'll get into recovery mode. )))
thx dude, i figured it out "accidentaly"
Everyone was writing on the net that the recovery boot is up and down the same time instead of the old method of power & volume -.
So, when I got to the droid, started to push every possible button in every possible variation and I got in.
since then I learned that the vol up and down is after power & vol -, not instead.

[Q] New ROM keeps re-booting

Hi,
I rooted my DHD today and tried to flash the CyanogenMod-7 for Desire HD & Inspire. It seemed to work but now keeps re-booting every couple of seconds. It won't actually stay on long enough to put another ROM on. Can anyone help? This is the first time I've done something like this and it seemed to be going so well!
Thanks!
Pull the battery for about 10 seconds. Then hold the vol- button down and power your device on. Now you should see a white screen with some text on it. Navigate to recovery and press the power button. Now it should boot into recovery.
In the recovery choose wipe data/factory reset ald let it finish. Once its finished choose wipe cache partition.
Then go to install .zip from sd and then choose zip from sd. Now search for your rom and reinstall it
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
This is common. Simply wait for it to boot and power off or use the power button to select reboot. You only have to do it once.
The instructions for installing CM7 all say to install ROM then reboot after first complete start up. Shouldn't need to reinstall anything.
Having been left alone for a few hours it seems to have sorted itself out. Thanks! I just wasn't expecting it to spend quite so long re-booting.
I guess you have enabled wi-fi just after flash cm7. Seems like there is a bug or whatever, all you need is re-boot device after first boot.
And about the re-boot loop, just remove battery to turn off you device then turn it on, enter recovery and flash cm7 again WITHOUT do wipe operation. OK, In this time remember to re-boot after first boot.
I got a bit trigger happy and tried to flash Android Revolution HD 3.3. I did a full wipe from ClockworkMod Recovery and tried to install the zip, exactly like I did for the previous ROM. That kept aborting the installation so I mounted the phone and re-downloaded and copied it onto the SD card again. Same problem. I then tried to re-install cm7 and that also kept aborting.
I now have the message "Back menu button disabled" and if I use the power button to select anything it goes straight to a white triangle with an explanation and the Droid, which I think is stock recovery? I'm getting there from what I think is Clockwork though. Is this recoverable or have I managed to brick it?
I had a similar issue a few days ago - it turned out that the battery stats were screwed up so a fix for me was to boot into recovery and then wiping the battery stats.
Everything was fine after that.
How do I do that? I don't want to reboot out of Clockwork as I'm not 100% sure I actually have a ROM at the moment.
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
mdaigt said:
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
Click to expand...
Click to collapse
open recovery, goto advanced and wipe battery stats
Going to leave battery out for the night as read in other posts. Fixes the problem of not totally shutting down for some. Thanks.
Well leaving battery out didn't help. Continuous boot loop. Put on charger after turning off orange light came on and didn't go to green after 10 hours. Restarted when I got home and boot loop again. Had CoreDroid ROM installed. Working fine than tried to load Kalagas Mixed Theme and that is where I am now. Looping.
Even a blind squirrel will find a nut now and then. During HTC Hboot menu, noticed it was looking for PD98IMG zip. So I shut phone down. Inserted card with it on it and it restored to original firmware. PHEW. Hope this might help someone else.

[Q] Bootloop & Recovery don't work

Hi guys:
I have this phone from about 10 months ago. I have always it rooted and with CyanogenMod, actually with CM7.
Today I was using my browser, and then it closed, the phone begin giving me a lot of errors, any application worked and I decided to reset it, because sometimes that work.
For my surprise, when I reseted it, It was bootlooping, It start booting (cyanogen logo doing circles), then freezes and then reset.
I know how to work with this problems and I reseted it on recovery and when I entered to the recovery everything seems to be fine, but I only see the menu, when I try to install zip from sd card, go to mount & stored, go to clear cache, or enable USB the screen just get empty but its ON.
Im very frustrated, I don't know how to proceed in this situation, I have looked in the Troubleshooting thread but have not found anything that worked for me with boot looping.
I hope someone can help me, sorry for my english, it's not my main language.
what button are you pressing to select the menus? Power?
Yes Im using power button.
Before I used the power button but now tried using the middle button and it worked.
Lets see if it recover correctly.
Yes because power button turns off the screen.

Power button doesn't work in recovery

I just returned my phone to stock, everything passed but I fell into a bootloop. So did the usual and go into recovery to do a factory wipe and try again but the power button you use to select factory wipe doesn't work. The physical button actually works cause I can power on my phone...
any ideas?
i fixed it.. i just flashed CWM and reset from there.
bicho6 said:
i fixed it.. i just flashed CWM and reset from there.
Click to expand...
Click to collapse
I flashed CWM but still no functionality in my power button. It works to turn it on, but not in recovery menu. Any suggestions?
Try using the bottom /menu /home button
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
power button does not work on K1 in recovery mode (only) after ransomware attack
bicho6 said:
I just returned my phone to stock, everything passed but I fell into a bootloop. So did the usual and go into recovery to do a factory wipe and try again but the power button you use to select factory wipe doesn't work. The physical button actually works cause I can power on my phone...
any ideas?
Click to expand...
Click to collapse
I have exactly the same problem with my Lenovo K1. I updated it a year ago to ICS ( http://forum.xda-developers.com/showthread.php?t=1798856 ) . It was rooted and worked wonderfully! Yesterday I caught the ransomware 'Android Defender' which disabled all and any functionality. I booted into recovery mode but the power button does NOT react as 'select' button although it works just fine for power on and off. I select a function and press [power] an the first line becomes the selected. pushing it again just flashed the screen. But pressing it long turns the K1 off.
I updated some time ago to JB. To clean things up I loaded K1_CM10_JB_Starter_v2.zip ( http://www.ibtimes.co.uk/articles/374282/20120816/lenovo-ideapad-k1-jellybean-jro03h-cm10-rom.htm ) onto the machine and it installed nicely. I needed recovery to install google play and problem consists. I used the nvflash method to get back to stock (rooted) so that I could go from there ( http://forum.xda-developers.com/showthread.php?t=1560441 ). And all is back to 2011 -well, except that I now can't go directly into recovery but when I do I have the exact same problem.
So, whatever it is (and I'd like to blame the ransomware since it misbehaves since then), it intercepts the short power push in recovery, but does NOT affect normal Android functionality while in the OS nor the long push in recovery mode.
I am -needless to say- desperate since I can have Jelly Beans without google play (needed the recovery console to load the zip) or stock 3.2.1.
None of the options are good options.
Can you help?
günter

Can't shut down t800

Have been having a strange issue lately. I can't seem to turn off my tablet.
Long pressing the power button to bring up the power menu just soft restarts. I tried using a third part app (shortcutter) to bring up the advanced power menu which works fine but I still can't turn it off. Pressing power off just soft restarts, pressing full restart just soft restarts.
I can get into recovery but selecting power off from there just reboots back into recovery again.
I managed to get into safe mode and tried from there to see if it was a rogue app but it just reboots back into safe mode. Am rooted with magisk running lineage os 14.1 most recent nightly. Did a factory reset as well but to no avail.
Any ideas appreciated.
Fixed! Turns out it was a substratum overlay causing the problem.

Categories

Resources