Database Users

[Q]Bootloop, no recovery

Hi, my D802 is stuck in a bootloop, where it just shows the LG splashscreen and the custom ROM's boot animation, but it won't get past there.
Unable to get into recovery either. Phone screen just flashes and LG logo comes back up whenever I try the recovery combo (power + down then power + down). I can get into download mode but I can't seem to get adb to work, and then use [adb reboot recovery] to boot into recovery. Drivers all installed, and all are the latest. Recovery was working fine before this and it screwed up only after I flashed a custom ROM.
What am I doing wrong? My phone is now nothing but a paperweight since I can't get into the OS nor the recovery. Thanks.

Stuck on LOGO while going into Recovery Mode

I successfully Flashed Recovery using FastBoot but whenever I am going into recovery mode by pressing VOL DOWN+POWER it just shows OnePlus LOGO and nothing happens after it.
What should I do ?
I was using CW 13 with TWRP but then I FLASHED OXYGEN OS 3.0 and cleared the cache. After that, It is loading into OXYGEN but there is no developer options over there and it is not even going in recovery mode now.
HELP!

http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967
try this method. I tried and solved the problem.

Boot your phone into fastboot and on your pc, try 'fatboot oem device-info'
If it's locked, you're as ****ed as I was, my thread here.
(
You will have to go with Bhalla's unbrick guide
Tutorial on how to still get into your OS and save your stuff is in my thread - fastboot continue
)
If your bootloader is unlocked, try flashing this recovery (modified TWRP).
If it doesn't work - unbrick guide.
Afterwards, use the OOS 3.0 installation guide from Bhalla

try this
piyushmodi01 said:
I successfully Flashed Recovery using FastBoot but whenever I am going into recovery mode by pressing VOL DOWN+POWER it just shows OnePlus LOGO and nothing happens after it.
What should I do ?
I was using CW 13 with TWRP but then I FLASHED OXYGEN OS 3.0 and cleared the cache. After that, It is loading into OXYGEN but there is no developer options over there and it is not even going in recovery mode now.
HELP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 it worked i can now go into stock recovery...... Need to root but TWRP is not flashing any suggestions?

Can't boot into recovery using vol down+power but can boot normally

Hi,
I can't boot into recovery using vol down+power but I can boot normally into OS and from there I can boot into recovery through ADB or third party apps.
I was trying to update my OP2 with new OxygenOS 3.0.2. As my device was rooted so I had to do it manually using TWRP. Till now I was able to boot into recovery by vol down+power.
Before flashing I wiped everything(dalvik+cache+system+data), rebooted into recovery and flashed the OOS3.0.2 full ROM. At this point the installation was successfull but I was not able to boot the OS, it was stuck on the loading screen. After several attempts to boot OS, I finally tried to boot into recovery to flash again, but I was unable to. When I press vol down+power for few sec, the phone switches off with a vibration.
Later I found out that I was supposed to use a modified TWRP. So I flashed the modified TWRP via fastboot and flashed the OOS3.0.2 full ROM again, Now I can boot into OS normally but still I cannot boot into recovery by vol down+power. But the interesting thing is that I can boot into recovery through ADB or third party apps.
I tried flashing the TWRP recovery again with no luck. I thought this could be a problem with boot.img which is contained in ROM itself so I also flashed the ROM again with no luck. Also I am absolutely sure that this is not a hardware issue with by volume buttons as I can use them properly when I boot into OS.
A quick thought, is it possible that the boot.img of the ROM itself is broken? Seems unlikely as I am not seeing anyone else having this issue. But if it is, is it ok to flash the boot.img from OOS2.x version ROM, will that be compatible? Just wanted to be sure before doing this.
Any other thoughts are welcome.

Are you used this command for flashing twrp??
fastboot flash recovery recovery.img
You should add "flash", otherwise it won't install twrp in your mobile

yes I used that command only

Dreckk said:
yes I used that command only
Click to expand...
Click to collapse
After flash recovery use this command it will help to boot in twrp "fastboot boot recovery.img " without quotes

yes I know that, thats how I booted into recovery from fastboot for flashing the ROM. But I should be able to boot into recovery by vol down+power. That is why I posted this question.

Will you please send me screenshot of cmd?? after flash recover

I´m on bootloop on TWRP.

I have the same issue. https://forum.xda-developers.com/g5-plus/help/twrp-bootloop-t3740873
Im using latest twrp, im flashing Syberia Project + Magisk + Gapps
Then I reboot and it boots on TWRP, if I factory reset from the options on fastboot, it will start but without gapps and magisk, and if i try to install again those two, same thing happen, twrp bootloop
I saw some people that can start the phone on the OS using the start option from fastboot mode, but when i do this, it will start to boot on the rom for like 3 seconds, then it will turn the screen off, than twrp appears, please help.

[Help] boot recovery from windows ok but boot to recovery freeze

Hi,
I am experimenting my old xiaomi mi a1 with various roms. I can use hotboot (boot from windows with recovery img). It works normally with recovery from mohancm. However when I tried to boot directly on the phone to recovery. It can boot to recovery however I can't touch or slide or do anything with recovery other than pushing power button to restart. I have tried both 3.2.1-2 from mohancm and 3.3.1-0 from twrp team but no result.
I have used the guide from the forum to flash the rom, install recovery and gapps. I have no idea what's wrong. Please help me out. Thanks.