Database Users

No fastboot, recovery, or DL mode, rom works, please help!

TL;DR The title
Hey XDA,
So about a month or two ago, I decided to check out xdabbeb's VS982.5 rom because i felt like a bit of fresh air after all the lollipop roms was in order. So I grabbed his bumped bootstack+recovery, and flashed over to the rom.
What I didn't anticipate(and what I really shoule have) was the issues I would have getting back over to a lollipop rom because of the compatibility problems between loki'd and bumped roms and recoveries.
This is where my memory gets fuzzy because this was so long ago, and I apologize if that causes issues with fixing my problem. I do remember trying several different recoveries and bootstacks and none of them would flash because of the bumped recovery. Eventually I found a way to get back to my backup (The January 11th build of BlissPop). However, I still could not flash roms because of the bumped recovery I could not get off of. I tried several different recoveries, and several different methods of flashing them.
Eventually I downloaded flashify off the play store and downloaded the a recovery from there and flashed it from there, which to my recollection broke both my download mode and my recovery. The rom still works, but I can't access recovery or download mode to flash any new roms or do anything besides what is in the rom.
I would appreciate any suggestions anybody has for me, and am willing to totally revert to stock to fix this.
Much thanks!
EDIT: I was using/flashing TWRP builds for all of this in case it was unclear

check if you can get download mode using the mae way (vol up + power) but with usb cable pluged in, plug the usb cabe, presse the combo (up+pwr) and keep pressing until it reboots into downloadmode *always with usb plugged.

If you genuinely can't access recovery or download mode, you can enable usb debugging, adb shell, then dd write aboot, boot and laf to ensure the restoration of download mode. Might want to also write twrp recovery at that time so you have a bailout plan.

rafaelsartori said:
check if you can get download mode using the mae way (vol up + power) but with usb cable pluged in, plug the usb cabe, presse the combo (up+pwr) and keep pressing until it reboots into downloadmode *always with usb plugged.
Click to expand...
Click to collapse
Ah, trying this got me into DL mode safely. Thanks a ton, I'll make my way back to stock now.

LtZKilla said:
Ah, trying this got me into DL mode safely. Thanks a ton, I'll make my way back to stock now.
Click to expand...
Click to collapse
good to be usefull, we are here to help each other. thanks buton make that be more cool.

In my case I couldn't get into download mode.
This happened after flashing rpm, tz, boot and recovery partitions.
The screen doesn't show any logo and seems to be rebooting in a loop.
What can I do ?

Have you tried pressing volume down+ power an as soon as LG logo appears let both buttons off and press volumw down+volume up
Sometimes it works for goung into recovert
If asks for hard reset press YES YES YES and here you go
Hope it helps

Sadly my phone is not showing the logo, or anything on screen.
I can see that the screen is On because it has a weak glow, but it loops as if it was failing to boot the device.
When plugged to a macbook, I get this msg in dmesg:
hidd[65]: MultitouchHID: device bootloaded
kernel[0]: USBMSC Identifier (non-unique): 1234567890ABCDEF 0x5c6 0x9006 0x0, 2
kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
That repeats with the loop I mentioned previously.
This started happening after I I used 'fastboot' to flash partitions. I have tried many combinations to reset it, but none work, the screen never shows logos or error msgs...... that is really really disappointing about the device....

Has anybody found a fix for this? I'm in the same boat now, flashed CM12, went to update my outdated TWRP recovery and now its just a blank screen when I boot into recov, the ROM works fine. I'm afraid to do the aboot method because it seems like a lot of people are bricking.
At least I'm lucky I'm on a somewhat stable ROM at the moment.

How to boot LG Leon into recovery?

I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.

Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.

You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.

If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it

You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha

kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.

kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.

duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?

kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.

]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1

pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1

This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.

LG V20 Device is Corrupt and BootLoop

Hey all! Hopefully you can help with this issue. I have had this phone through T Mobile for a few months now, and am stuck in a real bind. As the title suggests, I have a boot loop issue and Device is Corrupt issue as well. The red Triangle is an issue with the OS. I cannot get the phone to boot to Android, nor get into recovery. I can however bring up the IMEI menu, which displayed the IMEI. I really need help, as this is my main contact for job search and family.

Im on sprint so this method is unavalable to me.
Tried LGUP? you have the ability to shoehorn a KDZ file in whicj will bring your phone to stock
As this is a no go for the ls997 i have no idea how this is accomplished. Check the forums for said method.

elijah420 said:
Im on sprint so this method is unavalable to me.
Tried LGUP? you have the ability to shoehorn a KDZ file in whicj will bring your phone to stock
As this is a no go for the ls997 i have no idea how this is accomplished. Check the forums for said method.
Click to expand...
Click to collapse
I will definitely look into this. I just want my phone back TT.TT lol

I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.

I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.

Griever0 said:
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Click to expand...
Click to collapse
So, I jinxed myself. I did in fact get the phone back up and running. But its not working correctly. I have a black home screen and the Recommended apps keeps popping up... THis is going to be a long night...

Griever0 said:
So, I jinxed myself. I did in fact get the phone back up and running. But its not working correctly. I have a black home screen and the Recommended apps keeps popping up... THis is going to be a long night...
Click to expand...
Click to collapse
Scratch that, I just had to pick my home screen loader. Phwew. I did it and I feel Happy. THANKS For the help!

HELP
Griever0 said:
Scratch that, I just had to pick my home screen loader. Phwew. I did it and I feel Happy. THANKS For the help!
Click to expand...
Click to collapse
How did you do it, I'm currently having the same problem with a phone that's on T-mobile

questionblock said:
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
Click to expand...
Click to collapse
Were you ever able to get this resolved? I'm having the same problem, except it's not showing anything about the bootloader that I can see

chuckyanutsup said:
Were you ever able to get this resolved? I'm having the same problem, except it's not showing anything about the bootloader that I can see
Click to expand...
Click to collapse
Ok, I seem to have my device back up and running. The step I was missing was to remove the battery, disconnect the USB cable, put the battery back in, hold volume down but don't press power, instead connect usb cable. This got me into fastboot and I was able to recover from there.

this might work for you!
questionblock said:
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
Click to expand...
Click to collapse
okay so holding VolUp while powered down and plugging into pc will bring up download mode if its still there,
if you have twrp installed prior to this red triangle then pull battery/put back battery. hold VolDown and power at the same time, as soon as LG logo comes up release power button (fast) and then hold it back down again while never letting go of VolDown. this is the factory reset hit yes for both questions and it should reboot phone into Recovery mode. some times you have to do it twice to get recovery (twrp) to pop up! i hope you have bootloader unlocked and twrp.
---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------
Griever0 said:
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Click to expand...
Click to collapse
If using the LGUP you must get the G4 Dll file for it to read the phone and com its on. i believe its a common.dll file i cant really remember...

chuckyanutsup said:
Ok, I seem to have my device back up and running. The step I was missing was to remove the battery, disconnect the USB cable, put the battery back in, hold volume down but don't press power, instead connect usb cable. This got me into fastboot and I was able to recover from there.
Click to expand...
Click to collapse
Awesome! Glad to hear it!

my lgv20 is supposed to be on the corrupt screen but it looks like a glitch happened or something and the corrupt screen is all messed up it has the red warning signs across the top of the screen and it just says giberish and it keeps bootlooping. ive tried everything i can only get to imei display if im lucky and it tells me "press the POWER key to exit and restart the phone" but when i do it just takes me to the messed up corruption screen and stays bootlooping someone please help.

weirdomane said:
my lgv20 is supposed to be on the corrupt screen but it looks like a glitch happened or something and the corrupt screen is all messed up it has the red warning signs across the top of the screen and it just says giberish and it keeps bootlooping. ive tried everything i can only get to imei display if im lucky and it tells me "press the POWER key to exit and restart the phone" but when i do it just takes me to the messed up corruption screen and stays bootlooping someone please help.
Click to expand...
Click to collapse
What model do you have?
You can put the phone to download mode (even if screen displays glitchy gibberish screen) by taking out Battery first, put battery back in after 10 seconds. Then just press Vol up and while keeping it pressed, connect to USB. If you have drivers installed, your phone will get recognized by LGUP. Now from here you can flash the stock rom.

Axon 7 can't boot, stuck on update screen then shuts down

So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.

*deleted*

vesheljinn said:
So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.
Click to expand...
Click to collapse
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs

This is what I thougth as well. But his link only refers to B08 in MM. So he didn't want to install B08 on Nougat. As his bootloader is still locked he cannot install this ROM in no way.

Choose an username... said:
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs
Click to expand...
Click to collapse
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.

vesheljinn said:
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.
Click to expand...
Click to collapse
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .

jjallday said:
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .
Click to expand...
Click to collapse
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.

vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
hmm well idk i had this problem earlier today, even when i had mine connected to the pc the pc would make a noise as if the phone was turning on, but when i connected to the actual charger is when the 60sec thing actually worked , also i noticed that when i finally got it on the battery was down to 1% maybe some sort of battery issue. maybe let it set on the actual wall charger for awhile and try again.

vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
Do the 4th category brick repair guide. Yes,you have to tear apart the phone, but I did this and didn't break it idk
No USB jigs or weird cables will work, you need to use the test pad to get into EDL.
There is another way though: it seems that if you discharge the phone completely, then hold vol down and power, and try a bunch of times, you might be able to get into FTM mode. You'll have adb from there, so you can do 'adb reboot edl' and use MiFlash to fix the software. But I haven't tried

Recovery Boot-loop, All help is accepted

So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.

Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.

Pretty sure you are using msmdownloadtool wrong. Completely shut down the phone. Make sure to DISCONNECT the phone form pc. Hold vol up and vol down for 5 sec. And it should unbrick hour phone

Hold power and volume up till the phone shuts off...
Now with the device completely powered off hold both volume buttons down at the same time for about five seconds then while continuing to hold both volume buttons plug USB in from pc to your phone the screen will be black and it's normal.... After this it should be showing up in the MSM tool....

It showed up in the MSM tool, but when i click start it goes for 4 seconds and then tells me that it doesnt recognize the image.

dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Yes, i was on the NoLimits rom and wanted to stop using it since i felt it was impacting a few things on my phone that i didnt like, but i really enjoyed Viper4Arise. So i was trying to flash V4A and after i was done flashing it wouldnt load past the unlocked bootloader screen, and i was stupid enough to not create a backup before i started because i didnt think V4A would be that harmful. After trying to wipe my phone and start fresh, i got stuck in the recovery loop.

dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Also, whats a good thread to get the system image?

Bildo41383 said:
Also, whats a good thread to get the system image?
Click to expand...
Click to collapse
If you are booting into recovery, first try formatting your data. In OnePlus's recovery, select English, and somewhere there is an option to "ERASE EVERYTHING." This will format the partition for OOS. On TWRP, go to Wipe--> Format Data. That may fix the bootloop.
If this does not fix it, the MSM download tool is a good option, however, I see it did not work for you. You can download OnePlus's official ROM from here, and for that, you want to flash it in TWRP like any other mod, then reboot. If you are still boot-looping after that, try formatting your data again for good measure.
For the MSM Download tool, you MUST be on Windows, and you must have extracted the archive fully, which can be done by right-clicking on the ZIP and selecting "Extract all." Then, turn the phone completely off, no USB attached. Press and hold Volume Up + Volume Down, and connect the device to the computer. You should then be able to launch the MSM tool, selecting the normal one for the stock variant, and the factory_mcl for the McClaren variant. If your device does not show up, make sure you have installed Qualcomm drivers from here.
Good luck and I hope you get your phone working!

Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
That happened to me as well with the 9.0.1.2 version.
What I did is I used an older version 9.0.1.1 works all the time. No matter what Rom you had previously installed, So try an older version.

https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
This saved my butt 100 times...whenever I mess with slot A and B and end up booting to recovery mode again n again