No longer able to boot into recovery mode after flashing LineageOS - ONE Q&A, Help & Troubleshooting

Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?

AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.

Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.

AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?

Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.

Related

[Q] Bootloop and everything lost

Here goes: I was a happy OPO user using the latest crDroid ROM and AK kernel, when suddenly my phone entered the sleep of death. I turned it off and back on, and since then it is in an eternal boot loop, never going beyond the Oneplus logo.
I am able to get into fastboot mode as well as recovery mode (I am using Philz Recovery), however, here is where it gets weird. I was hoping to just flash another ROM from the recovery and fix the problem, but all my files and folders on the SD card are gone, almost as if the chip died.
I also tried flashing a different ROM using ADB, to no avail. ADB shows "OK" but nothing sticks. All I can successfully flash are the boot logo and the recovery. The phone never gets beyond the logo before it reboots.
Does anyone have an idea what else I could try? I feel like sending it back for a replacement, but I am afraid that this will take forever.
Do you have a OTG USB stick ? Maybe you can flash from there.
I was able to get my phone to boot using this:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
All data is gone though. But at least I don't have a brick any more.

[Q] Help needed with bricked 1+1

Hey guys, I tried something on my phone and everything went to hell.
The following scenario took place:
Last night, I flashed this ROM and it worked just fine. I played around with it a bit and then wanted to go back to my daleski75 version of Lollipop.
I wiped the phone through TWRP and restored my backup and it booted into it just fine.
The thing I noticed immediately was that the bootlogo was the ColorOS version. And then when I was using my phone, the only way to wake the screen up, was to plug in the charger.
So I decided to fastboot flash CM11S.
I entered -fastboot flash boot boot.img and my phone automatically rebooted and then it just went blank.
A black screen, but I get vibration when I try to shut it off or go into fastboot.
I don't see it in Device manager though.
Any help at all would be greatly appreciated.
Posessor said:
Hey guys, I tried something on my phone and everything went to hell.
The following scenario took place:
Last night, I flashed this ROM and it worked just fine. I played around with it a bit and then wanted to go back to my daleski75 version of Lollipop.
I wiped the phone through TWRP and restored my backup and it booted into it just fine.
The thing I noticed immediately was that the bootlogo was the ColorOS version. And then when I was using my phone, the only way to wake the screen up, was to plug in the charger.
So I decided to fastboot flash CM11S.
I entered -fastboot flash boot boot.img and my phone automatically rebooted and then it just went blank.
A black screen, but I get vibration when I try to shut it off or go into fastboot.
I don't see it in Device manager though.
Any help at all would be greatly appreciated.
Click to expand...
Click to collapse
Do you have the chinese or the international version?
Have you ever had Color OS Installed?
Make sure that your battery is not empty and try again. If you can't boot into fastboot or recovery you have to contact the Oneplus Support to repair your device.

[Q] Stuck on

So I decided to try to flash Zombie-Pop today and everything went fine during installation but when the tablet started booting up it was stuck on "android is starting.." and it seems to load the apps. I knew it would take a bit of time to stabilize so I let it run but after 1 hour of it stuck there, I tried to reboot into recovery but I get a black screen and I can't access TWRP. It just boots right back to the android is starting screen. It doesn't seem to be a boot loop since it finishes the boot sequence. My biggest problem is not being able to access recovery because of the black screen which apparently is happening to some people with TWRP. I tried to go through adb but since my tablet isn't done installing, it doesn't have the drivers to run adb. Is my tablet toast? bricked?
edit: apologies for the title. I must have deleted the text before posting.
agentkalaw said:
So I decided to try to flash Zombie-Pop today and everything went fine during installation but when the tablet started booting up it was stuck on "android is starting.." and it seems to load the apps. I knew it would take a bit of time to stabilize so I let it run but after 1 hour of it stuck there, I tried to reboot into recovery but I get a black screen and I can't access TWRP. It just boots right back to the android is starting screen. It doesn't seem to be a boot loop since it finishes the boot sequence. My biggest problem is not being able to access recovery because of the black screen which apparently is happening to some people with TWRP. I tried to go through adb but since my tablet isn't done installing, it doesn't have the drivers to run adb. Is my tablet toast? bricked?
edit: apologies for the title. I must have deleted the text before posting.
Click to expand...
Click to collapse
Which bootloader are you on?
How are you trying to boot to recovery?

LG Logo Bootloop - Can't access TWRP - No DL Mode

Hi guys,
New to flashing custom ROMS. Good news - flashed CM12, then LiquidSmooth and I'm learning a lot after having soft bricked my phone a few times. Bad news - After trying to get back to Stock I'm not able to get out of this LG Logo bootloop. The LG logo will flash, screen will go black and the whole process starts again. It doesn’t progress past that. I'm unable to get to TWRP recovery or download mode.
My idiotic move:
Iffy stability with camera and mobile data with CM and LiquidSmooth. Decided to go back to Stock.
I flashed my nandroid backup, which I believe led to a bootloop (can’t remember). Was able to boot to TWRP and get back to CM12. Then I had the genius idea of using AutoREC and selecting the “Go Back to Stock” option. Yes, it’s already sounding like a bad, and nonsensical idea as I say it now. Can't remember exactly what I did next - I either flashed my nandroid backup or did a factory reset through CM settings. Threw me into this bootloop.
The details:
Model - D800 - Am sure of this.
Stock software before flashing CM12 was Lollipop 5.0.2 via OTA.
TWRP Recovery 2.8x something or other. Used AutoRec to flash.
I can interrupt the bootloop and access Factory Hard Reset through Power + Volume Down
Had to go to JB Bootloader in order to Flash ROMs. Errors returned otherwise.
Roadblocks:
No download mode. Holding Volume Up & Inserting USB cable doesn't work. Although am able to get bootloop to include a blank screen with red flashing LED through this method from time to time.
Phone boots up, and goes directly into bootloop when plugging USB cable into phone. This happens both when plugging into a wall charger or into a computer. I think this is probably the biggest pain and is holding up things from progressing. Can turn off phone by holding down power for a few seconds, BUT if the phone is plugged in it will continue to boot on its own.
Phone not recognized by computer & ADB However, was at times able to get Device Manager to recognize the phone as an "Unknown Device" after going to the Factory Hard Reset screen. This is no longer working after trying different drivers. I’ve went through LG Mobile Universal Driver as well as the Koush driver.
Going through Factory Hard Reset via hardware buttons only throws phone back into BootLoop
Can’t boot into TWRP
Any insight or help guys? Thanks in advance. I think getting into Download Mode will be a quiet victory. I’d like to try to use Supersports guide once I get there to go back to stock.

G7 Power possibly soft-bricked, can't access fast boot anymore

Recently had issues with my G7 Power and it seems to be soft-bricked. I was using an app and the app in question usually has the occasional stutter but then things resume to normal a second later. This is what happened yet this time the phone froze and was completely unresponsive. I held the power button down, turned it off and back on and it seemed fine but for whatever reason it got stuck on the Verizon loading screen which never happens. Turned it off and on again and it got stuck on the Moto animation so I held the power button down again. The phone shut off and refused to turn on again.
Eventually I ended up getting into fast boot (initially tried getting into fast boot many times with no success, no idea why it suddenly worked that time) and reset the phone through there and it would still get stuck on the Verizon loading screen. Kept turning the phone off and returning it to fast boot to repeat the process which was probably a stupid mistake on my part as the phone proceeded to shut off like expected but this time I couldn't get into fast boot anymore at all, even when keeping it on the charger that came with the phone.
LMSA was looking like the perfect solution but my PC isn't recognizing the phone as a drive so I don't think any sort of software made for instances like this are going to work unless there's something I'm doing wrong here. I can't get into the phone to enable USB debugging either.
Any recommendations as to what I should do? It's looking like sending it back to get it fixed is my only option here. Never had any issues with the phone until now.
Re-flash Stock ROM.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
jwoegerbauer said:
Re-flash Stock ROM.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
Click to expand...
Click to collapse
My PC won't recognize the phone at all, would this still work? Would it also completely wipe the device's memory?

Categories

Resources