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.

[SOLVED] Unable to boot into recovery after flashing custom rom

Hi guys
So, i've been at this for most part of today. Looked all around and tried everything i found, and im still clueless.
I've done this steps twice, with the second time being more step-by-step instead of bulk actions, always starting from miui 8 global stable rom:
1 - flash twrp via fastboot with twrp-installer.bat for redmi 3s
2 - reboot into stock bootloader with power + vol+ and choose recovery to boot into twrp
3 - in twrp, slide to modify system and disable dm-verity in advanced options
4 - reboot into stock rom and power off phone
5 - boot into twrp in the same way as in step 2
6 - clean dalvik, system, data and cache partitions
7 - flash lineageos 13 from lsferreira and gapps
8 - reboot into custom rom and power off phone
9 - try to boot into twrp in the same way as in step 2 - NOK, just gets stuck at the MI logo
10 - reboot into custom rom and reboot into recovery from the power menu, twrp OK
11 - flash something, like goodix fix or xposed
12 - reboot into custom rom, verify installed packages OK
From this point on, i can not get back into recovery, either stock bootloader or twrp. Tried from the power menu, vol+ button, reflashing twrp through fastboot and adb, booting directly from recovery.img from fastboot and even reflashing stock recovery. The rom always boots fine and so does fastboot.
I saw some posts saying to hold both vol- and vol+, but this just seems to boot the phone in some deep recovery mode, judging by the drivers that the PC tries to install (EDL maybe?)
The only way i can get the bootloader/recovery (the vol+ chinese menu) back is to reflash stock miui 8 through miflash tool, which gets me to the starting line.
Will anyone be kind enough to point me to the blatantly obvious mistake im making?

I think I found a solution. I flashed a different twrp recovery (the one provided by fedosis, by cofface) instead of the one linked in every how-to in both this and miui's forums.
Now i can boot to recovery everytime.

[FIXED] Lg G6 [H870] TWRP recovery problem

So i wanted to finally install custom ROM on my LG G6 H870, needed twrp... obv, followed all the instructions:
adb devices - showed my device all was good
2nd: adb reboot bootloader
3rd: fastboot flash recovery twrp.img
4th: fastboot reboot + holding volume down and power button, on logo released power button and pressed it down again, finally got to factory data reset 2 YES options and saw the Teamwin bootup logo, but then phone just booted up normally...
5th: Tried to open recovery once more, but then it did regular Data erease.
What could be wrong?

Razexay said:
So i wanted to finally install custom ROM on my LG G6 H870, needed twrp... obv, followed all the instructions:
adb devices - showed my device all was good
2nd: adb reboot bootloader
3rd: fastboot flash recovery twrp.img
4th: fastboot reboot + holding volume down and power button, on logo released power button and pressed it down again, finally got to factory data reset 2 YES options and saw the Teamwin bootup logo, but then phone just booted up normally...
5th: Tried to open recovery once more, but then it did regular Data erease.
What could be wrong?
Click to expand...
Click to collapse
Which TWRP did you flash ? Bootloader unlocked ?

Razexay said:
So i wanted to finally install custom ROM on my LG G6 H870, needed twrp... obv, followed all the instructions:
adb devices - showed my device all was good
2nd: adb reboot bootloader
3rd: fastboot flash recovery twrp.img
4th: fastboot reboot + holding volume down and power button, on logo released power button and pressed it down again, finally got to factory data reset 2 YES options and saw the Teamwin bootup logo, but then phone just booted up normally...
5th: Tried to open recovery once more, but then it did regular Data erease.
What could be wrong?
Click to expand...
Click to collapse
I had exactly same problem when I did this = only Teamwin bootup logo and then boot into android (I hope your bootloader is unlocked first).
Solution was you have to use TWRP 3.1.1-0 and u get into recovery. I tried more versions of TWRP (3.2.1-0 , 3.2.2-0 , 3.2.3-0) but ONLY 3.1.1-0 works and I dont know why.
Anyway I got another issue after because I didn't want to install root yet (first I wanted to backup).
An issue was I got into restarting loop by installing no-verity-opt-encrypt 6.0 which should be a solution for boot into android without losing TWRP (considering to one walkthrough I found).
I was lost for a while but I found a solution = install another boot.img (in my case I installed one dm-verity or dm-verity & forceencrypt zip file - btw what is a difference between them?).

Oh wow.. Well thanks, ill try your solution as soon as i get time. Bootloader is unlocked indeed, used latest twrp. I'll try 3.1.1-0.

@ Razexay
that happened to me also with Official TWRP take that from Eliminater74 that's where backup and encryption work with dm-verity & forceencrypt look here in the forum everything is well described
https://forum.xda-developers.com/lg-g6/development/twrp-t3828254

Help stock on logo cant go to twrp

HELP , I am stock stuck on logo after I flash panadriod rom now I have flashed pda twrp but twrp is not opening stuck on logo only , I am on fastboot please help flashing twrp but not booting

farhan20 said:
HELP , I am stock stuck on logo after I flash panadriod rom now I have flashed pda twrp but twrp is not opening stuck on logo only , I am on fastboot please help flashing twrp but not booting
Click to expand...
Click to collapse
1. Obviously you need to have your phone bootloader unlocked and enabled USB Debugging.
2. Connect your phone to PC
2. Reboot to Fastboot using Volume Down+Power button
3. On your PC, navigate to the 4PDA TWRP folder
4. Start the Flash_TWRP.bat file (as Administrator just to be sure)
5. Follow the instructions in the CMD window
6. After TWRP Flash, reboot into recovery (Press Volume up Button+Power button)
in TWRP format data
reboot to twrp again in recovery
7. Flashe your Rom of choice
8. Rebooted and let the ROM load (have patience, first time takes pretty long!)
9. Follow and complete setup

Hard brick

Hey their. So i jsut bought a one plus 6t and started playing around iwth it. I tried to get twrp and i got it but when i rebooted to os i had no wifi. So i download magisk zip and flashed it. After this i got stuck in bootloop and so i wne to twrp and wiped everything except system. Then i rebooted and got this message Qualcomm CrashDump Mode Attempted to kill init! exit code=0x0000000b do_exit. Then i freaked out and accidently wipes system too. Now i think i have a complete brick as adb still works but i cant transfer any file from pc to phone because theirs no system. Please help!!!

Never wipe system and vendor on A/B devices, literally, never.
Boot twrp and flash OOS or use msmdownloadtool.

What do you mean flash OOS. Like flash a fastboot file? And what version of msmdownloadtool should I get as their is no system. Should I get 10 cause that was my last system or it doesn't matter.

Update. I left twrp after flashing a stock image and now adb doesn't recognize my phone. When booting into recovery I go into the one plus recovery. Now I'm really screwed.

Okay now im really screwed. Whenever I boot with power up or power down I get sent to the bootlaoder page that says fastboot mode products name. I cant leave this page however. On the options above the information I click reboot recovery I get sent back to this page.

UPDATE. My phone is a literal brick now. It won't even turn on. I tried to force reboot it before and after it powered off it wont turn on. Its fully charged and when connecting to charger of holding buttons nothing happens. I have no warranty so Im hoping that someone can help me.

The "bootloader page" is fastboot and that's normal because there's no system to boot, you wiped that partition... and ADB only recognizes the phone when the boot process ends and ADB is enabled in the phone.
If you press vol up + down when you connect the usb cable the phone boots in EDL (Emergency Download Mode) mode, long press power + vol up to leave that state.
Now, download msmdownloadtool from here, extract the file, power off you phone, conect the usb cable to your pc, press vol up + down and connect the usb cable to the phone, open msmdownloadtool and flash the OS.
Edit: Read this thread for more detailed instructions.

What do you mean by flash the OS. The OS in the system or do I have to download one?

whenever I plug in my device it vibrates and then goes into the fastboot page. Also adb can detect it if I type in fastboot devices.

So i go the device to work and MsM worked until 4 seconds and then It said param preload for status of connection and status of last communication says device not match image

Try with the fastboot ROM.

When i downloaded another version of MsM it did not say no image match instead it stays at 4sec and says recording download time

Can you give me instructions on how to use the fastboot room? Like after i download it what should i do with it?

Download the rom, unpack it, boot your phone in fastboot (Power + vol up + vol down), connect the phone to your pc and execute the "flash-all.bat" file, and just wait.

um what is flash-all... How does it work what am i supposed to do.

what does unpack it mean?

Hey their im going to assume you meant to unzip the file and then open the file called falsh-all.bash. In that case when i do that i get this message "error: failed to load 'images.zip': No such file or directory
Press any key to exit..." In a CMD window