Database Users

always booting into recovery

hello,
i've got a weird problem for some time now. i already have a workaround but it always requires me to hook the phone up to a pc.
the problem: after rebooting the phone to recovery, it gets stuck there.
i had this with cm12, cm12.1, temasek cm12.1, phronesis 2 and darklord N5 so i suppose the problem is not related to the roms itself.
if i long press power from running android and select reboot -> recovery the phone boots to recovery as expected.
whatever i do, after hitting reboot -> system in recovery it reboots to... recovery.
removing the battery for 5 minutes does not help.
the phone just keeps booting to recovery. the one fix i found so far is a mere workaround:
force download mode (vol down + home + power), hook it up to my pc, launch odin and flash twrp-2.8.7.0-hlte-4.4.img.tar
this gets my phone to properly boot into normal android, but it always requires a pc. so using CM Updater oder CyanDelta with automatic installation of updates always gets me stranded in recovery while on the go.
what can i do to avaid this recovery bootloop? sure, i can just boot into recovery manually (vol up + home + power), but i suppose there is a real "fix" for this. do i have the wrong recovery? did i pick 5 roms with all the same bug?
this is really really annoying, especially if i forget about the problem and reboot into recovery from long-press power...
my N3 is a n9005 running on custom roms since late 2014 (i.e. i havent got all the official OTA updates which may be available)

OP2 soft bricked, can't access recovery, not recognized by laptop

Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.

If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac

CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.

AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.

justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.

[HELP] Recovery doesn't get permanently flashed.

I recently rooted my Redmi 3S after unlocking my bootloader ( yes, applying for a request from the mi unlock page and everything) (not pro not prime, just the 3S)
I was on MIUI8, the most latest version ( I know this because I went to software update page and no updates were available. lol )
I proceeded to unlock my bootloader via the MIUnlock program ( nope, no errors, no 50% stuck issues) and flashed twrp and stuff from this link http://xiaomitips.com/guide/how-to-flash-twrp-and-root-redmi-3s/
Then I proceeded to flash LineAgeOS and from there whenever i try to reboot into recovery ( yes, i have the advanced reboot options) it just reboots into the main os completely skipping the recovery. I found this strange the first time and thought it was my mistake. But I tried volume down+power which is just Fastboot all the time. I tried volume up+power too, it just stays on the Mi screen. But whenever i run the twrp-installer.bat i got from the http://xiaomitips.com/guide/how-to-flash-twrp-and-root-redmi-3s/ it boots into TWRP. so, basically there is no twrp for me to access without me having access to a computer. I tried copying the recovery.img onto my phone and tried installing it as an image into the recovery. but same issue persists. I just can't access the twrp recovery without using a computer. Please help
Edit : I disabled dm-verify too

I had the same problem with my Redmi 3s 2/16
For me works
WITH OPEN BOOTLOADER
I flashed TWRP with Fastboot
fastboot flash recovery recovery.img
>>>directly after flashing<<<
1.) Push Vol+ and Vol- and Power at the same time
2.) If you see the MI-Logo release ONLY the Powerbutton and wait
3.) With a little bit luck you are now entering TWRP
4.) If not, do not release Vol+ and Vol-, the Devicescreen went totally black
5.) Do not release Vol+ and Vol- and push now the Power Button
6.) If you see the MI-Logo release ONLY the Powerbutton and wait
7.) Then TWRP starts (for me)
8.) A few times i landed into the chinese menue, then push the recovery button, with a little bit luck you arrive TWRP
9.) If nothing helps, and the device starts normally, imho the process changes twrp back into the original recovery -- then flash twrp again and start from Point 1.)
NOTE!! If you enter TWRP the first time go to Advanced Settings and tap on --Disable DM-Verify-- .
After i disabled DM-Verify and flashed the Xiaomi.eu Rom the above worked for me without every time flashing twrp.
I worked 6 hours at this workaround

ConradB said:
I had the same problem with my Redmi 3s 2/16
For me works
WITH OPEN BOOTLOADER
I flashed TWRP with Fastboot
fastboot flash recovery recovery.img
>>>directly after flashing<<<
1.) Push Vol+ and Vol- and Power at the same time
2.) If you see the MI-Logo release ONLY the Powerbutton and wait
3.) With a little bit luck you are now entering TWRP
4.) If not, do not release Vol+ and Vol-, the Devicescreen went totally black
5.) Do not release Vol+ and Vol- and push now the Power Button
6.) If you see the MI-Logo release ONLY the Powerbutton and wait
7.) Then TWRP starts (for me)
8.) A few times i landed into the chinese menue, then push the recovery button, with a little bit luck you arrive TWRP
9.) If nothing helps, and the device starts normally, imho the process changes twrp back into the original recovery -- then flash twrp again and start from Point 1.)
NOTE!! If you enter TWRP the first time go to Advanced Settings and tap on --Disable DM-Verify-- .
After i disabled DM-Verify and flashed the Xiaomi.eu Rom the above worked for me without every time flashing twrp.
I worked 6 hours at this workaround
Click to expand...
Click to collapse
Holy **** thanks. I booted into twrp with vol- and vol+ + power button directly after flashing

[Help] LS997 DirtySanta Stuck at Secure Startup

LS997 (September 2016 security patch), got to the end of root and couldn't reboot into TWRP recovery. The device is recognized in ADB while in fastboot but when I'm at the secure startup it's unrecognized, like USB debugging is disabled.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278

If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.

Phoenix591 said:
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Click to expand...
Click to collapse
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.

strapdad said:
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
Click to expand...
Click to collapse
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.

Phoenix591 said:
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Click to expand...
Click to collapse
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.

strapdad said:
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
Click to expand...
Click to collapse
Reflash your variant's official KDZ using [PARTITION DL] with patched LGUP leaving [aboot], [abootbak], [recovery], [recoverybak] partitions unchecked.
- Once the flash finishes & phone reboots, do a battery pull so phone doesn't fully boot (wiping recovery & encrypting data)
- Insert battery again
- While pressing volume down button - reinsert usb cable so it boots into fastboot mode.
- Follow dirtysanta guide for your variant from running step3.bat onwoards (which flashes TWRP back into your otherwise stock phone).

LS997, no official KDZ. Use VS995, but dump everything with LGUP (bar userdata) before hand

Nokia 6.1 Plus, boot loop to twrp and twrp fails to load

I tried flashing lineageOS 19 on my nokia 6.1 plus, after I flashed with Gapps 12(Nick Gapps) - something went wrong...
- I see that phone no more boots to "download mode"
- Phone boots to TWRP, TWRP fails to load and keeps restarting.
- Cannot get into adb or fastboot mode now.
- Tried vol-up + Pwr - phone does not go to download mode
Could anyone help with a fix?

First of all you need to press power+vol up when connected to charger and then when the screen turns off be quick and hold power+vol down to go to download mode

Thanks, will try this