Database Users

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.

How do I unbrick a bricked P9Lite with a locked bootloader and without USB debugging?

Greetings all,
I recently got a P9 Lite but I bricked it trying to install a newer firmware on it (tried to go from 6.0 to 7.0). I've read various unbricking guides over the past two days but to no avail. I'd like to know what my options are at this point and if it is possible to unbrick it and bring it back to a usable state even if on a different rom.
How I got here:
The firmware that came with my phone was L23C605B120. I tried to update it to L23C605B362 and downloaded 2 zips (update.zip and update_data_full_VNS-L23_hw_la.zip). I unzipped update.zip into the dload folder of my sdcard and updated it via the dialer. The update installed and my device rebooted but now to this bootloop state.
What I can do:
If booting up normally, I end up in Huawei's erecovery. I can also boot to recovery mode where I can either "Wipe data/factory reset" or "Wipe cache partition". I can boot to fastboot & rescue mode but it says my phone and frp are locked. When pushing all three buttons I can boot to where the phone will attempt to update with the dload folder in the sd card again.
Stuff I have tried:
In erecovery when I select "download latest version and recovery", I can connect to my wifi but it always fails at "Getting package info failed". In recovery mode the factory reset fails and I don't think wiping the cache partition did anything meaningful. In fastboot & rescue mode it tells me to open HiSuite where there is a recover option but clicking it says "Your device is not supported for system recovery". I can see my device using fastboot on my computer but it seems almost useless here since its useful commands fail with "command not allowed" probably because my bootloader is locked. On my computer I installed the USB drivers adb needs and rebooted but adb cannot see my device presumably because I hadn't enabled USB debugging prior to getting bricked. At this point I'm downloading different roms to my sdcard and trying to flash with the 3 buttons method but pretty much all of them fail at 5% or 7% including the rom with the same version that my phone came with. The only one that doesn't fail at 5% or 7% is the rom I tried to flash that bricked my phone which fails at 99%.
So I cannot flash TWRP because my bootloader is locked, I cannot unlock my bootloader because adb cannot see my device, adb cannot see my device because I probably never enabled USB debugging and I cannot enable USB debugging because I cannot boot to the OS. At this point my only option seems to be trying to flash a working rom with my sdcard but I have yet to find one that works.
Where should I go from here and what are my options at this point? Is there a specific rom I should be looking for? Is there some intermediate downgrade rom I have to flash or is there a way to undo the update I just did? Is there a way to somehow enable USB debugging or to unlock my bootloader without it (perhaps via an exploit)?
Any help would be much appreciated!
TL;DR: title

Not booting into TWRP

Hey everyone,
I decided to root my lg g6 and got a fickle. After unlocking the device and flashing TWRP I tried to boot into it (''adb reboot recovery'' command) and it deleted all data and then twrp shows on screen for a split second and almost instantly boots normally into android so I set it up while still being unable to access twrp and any of it's functions. Does anyone have any idea what could be the problem?
P.S. Of it helps: before that i had a problem that every time I tried to use the ''adb reboot recovery'' command the console said ''no devices/emulators found''. After a couple tries I wanted to check whether the phone was connected just to make sure (''adb devices'') and after that it worked and I ran into the problem above.
Thanks for all the answers

When you first unlock BL and flash recovery you have to manually enter recovery mode.
Hold power and vol down till it turns off. Hold same buttons again until you see lg logo. Release power and press and hold again.
Then ask you to wipe etc hit yes both times and it will boot to twrp.

I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)

Ulrih said:
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Click to expand...
Click to collapse
You have to flash TWRP recovery and when it complete then use the button combo to boot into twrp, otherwise it will boot and restore the recovery.
flash twrp
button combo to twrp
done

Yes I've done that but the problem still exist.
btw thanks for the help

Maybe try fastboot flash recovery recovery.img

Try the all-in-one tool on this forum

By the way, I am running into the same issue.. I have a LG G6 US997,.. I have tried installing TWRP unofficial ones so many times and every time i manually try to access the recovery.. the phone simply wipes all my data to default

Hello,
I have the same problem. Did anyone figure out how to solve it? I'd highly appreciate any help.
If I try to boot into recovery, it asks me to factory reset, i hit yes twice and then the phone just goes on to boot normally. The data is not wiped but I can't get into TWRP.
If I enter "fastboot reboot recovery" after flashing TWRP it returns "fastboot: usage: unknown reboot target recovery"

Weird bootloop after OTA (21 April 2020)

My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you

Can you boot to safe mode ?
(Long press power button - then long press on power off)

Doesn't work
Tianhe said:
Can you boot to safe mode ?
(Long press power button - then long press on power off)
Click to expand...
Click to collapse
Safe mode makes no difference. Even factory resetting made no difference.

[SOLVED] Unable to enter TWRP/Stock recovery and can't boot into system

Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.

Could you try help me? I can't even get ADB to work anymore