[Q] N900T constant reboot after rebooting to do a backup - Galaxy Note 3 Q&A, Help & Troubleshooting

Went to the Play Store, installed ONline Nandroid Backup by Thomas Otero, and ran a CWM online backup. It worked fine.
Went back to the Play Store, installed TWRP manager by Jmz Software, and ran a TWRP standard backup. Rebooted to recovery for the backup, and now the phone is stuck in a boot loop
It boots to:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
vibrates twice, and starts over.
the only way to stop it is to pull the battery.
Is there a combination of buttons that I can push to get it to at least boot to a recovery screen? I have tried power+home+volume up... no luck.

Nevermind... I did tried booting to download, and just saying cancel, and it booted up fine. I'll be getting rid of that TWRP dowload manager.

Related

[Q] Stuck in recovery boot loop...?

While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
It happened to me once. I pushed the power button for 60 seconds as it supposed to do a kind of battery pull, and it worked.
HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Lordificated said:
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Click to expand...
Click to collapse
I've done this twice to my nexus now and I think I found a reliable way to restore to running condition. YMMV
1)Boot the nexus into fastboot (power and both volume keys) when you power up.
2)Attach your usb cable from the PC (or MAC I guess, dont have one to try)
3)start WUG Nexxus Root Toolkit. 'Launch' advanced utilities.
4)Test your fastboot with Quick tools. check the button at Fastboot-Bootloader and click 'List Devices' if the box that pops up is empty then fastboot isn't working (I can't help you there and it must be working to continue).
5)If fastboot shows a device then go to "Boot Temporary" and click 'Custom Recovery'.
6)I selected 'Touch TWRP' but CMW may work as well. This will reboot you into (temp)TWRP and from there you can force a reboot that will reset the 'Recovery' flag that has locked your bootloader.
7)Give it a few minutes (be patient for 5 minutes) and hopefully you reboot to where you were prior to this mess.
Long time lurker and couldn't fix my fails without everyone here.
Thanks to all.
Bill
HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
zeroedout420 said:
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
Click to expand...
Click to collapse
I guess mine worked because I was still on stock bootloader and adding TWRP was an important key but the 5 minutes seems to be the solution after all the rest.
recovery boot loop:- Is coz, one of your partitions would be facing problems while mounting.. So Wipe the Partition and Format it with Ext-2 file format. and reboot the Mobile. Then it'll stops rebooting.
Do you have a Samsung device?
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
carltasmania said:
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
Click to expand...
Click to collapse
How do you install cf-autoroot when stuck in a boot loop with samsung galaxy S device if there is no fastboot?
My phone is stuck in bootloop too. It shows Twrp at the starting and then restarts. What am i supposed to do? I need help ASAP please

[Q] GT-I9505 doesn't reboot after flashing kernel

Hi,
I've flashed a kernel for multi boot. It says it was successfully.
After I hit reboot, my SGS 4 turned off. When I try to boot, it stocks at the Samsung logo.
I can't even go to recovery or download mode.
'Kernel is not seandroid enforcing'
I got a Nandroid back-up on the external SD and on my PC.
Is there a way to go to recovery or download mode?
Then I can install STOCK or restore the back-up.

[Q] Bad Recovery?

I have been using CWM recovery but wanted to go back to TWRP so I downloaded TWRP manager and went through the install procedure but my phone got stuck in the logo screen with Recovery Booting... in small blue letters in the upper left of the screen. But it never loads to the recovery. I need to put it in download mode then cancel out of it in order to get it to boot normally.
thaigh256 said:
I have been using CWM recovery but wanted to go back to TWRP so I downloaded TWRP manager and went through the install procedure but my phone got stuck in the logo screen with Recovery Booting... in small blue letters in the upper left of the screen. But it never loads to the recovery. I need to put it in download mode then cancel out of it in order to get it to boot normally.
Click to expand...
Click to collapse
Exact same thing happened to my recovery awhile back. The TWRP manager has never worked for me and always ended up messing up my recovery. Use odin to flash a custom recovery back on to it.

[VS980] Security Error on Boot

I'm not sure at all what caused this problem. I downloaded Autorec to try and update my recovery, it seems to have worked fine and I can access my recovery fine. After backing everything up with TiBu, and TWRP (EFS because I was told to always have a backup), I rebooted my phone and when I get to the LG logo, it says "Security Error" and reboots infinitely until I power it off. I can still get into recovery and restore but I can't boot into system.
What does this mean? Do I have to restore to stock or is there a way I can repair the partition(s)?
SOLVED: Flashed 39A KDZ

[Q] Recovery is not seandroid enforcing and Odin

Samsung Note 3
Installed CWM App from Play Store
Using that app I installed the Clockwork Recovery Mod
Tried to get into the recovery but saw an error with the line
Recovery Booting…
Recovery Is not seandroid enforcing
Set Warrantee Bit: recovery
I rebooted into the OS and using the Clockwork app I found the custom rom I wanted to install and chose the option to auto reboot into recovery and install.
The problem is it starts the boot shows that 3 line error message and keeps a reboot cycle which I can’t get out of.
I believe what happened is an outdated recovery was installed and I need to install a good/updated one.
I can get the phone into download mode.
My problem is I can’t get a valid version of Odin running that will actually see the phone running Odin 3.10
Help?

Categories

Resources