Database Users

Nexus 6p with Android 7.0 in bootloop cannot access recovery

Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA

Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE

@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode

ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?

fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.

sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.

I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?

Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..

I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.

Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..

So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.

Dirty Santa and Restoring From Backups - Suck in some kind of limbo?

So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!

This may be an issue with TWRP. When I had my Galaxy S3 rooted back in the day I would have this issue, also with a Nexus tablet I rooted as well. It turns out I needed to flash a specific "fixed" version of TWRP to fix the mount/flash issue. That was a long time ago though, so this might not be the problem, but I thought I would at least tell you my experience.
Sent from my LG-LS997 using Tapatalk

biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I beleive you have to do Dirty Santa over again....The steps that is.

biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.

imucarmen said:
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
Click to expand...
Click to collapse
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.

biglightbt said:
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
Click to expand...
Click to collapse
I would run the dirtysanta exploit again from the beginning. Your assumption about being stuck in read only seems correct. I'm guessing you might have chosen read only on accident one time when you booted into TWRP and now it's stuck there.
Or you could try using flashfire to flash the TWRP.img

I am having the same issue. I tried doing the DAC mod that enables high impedance as always on. Audio quit working along with the stock music app. Did a restore from after I flashed the konverged kernel. And now no r/w ability and twrp will not mount system unless I check mount as read only. I was able to reinstall supersu from the recovery. But still have the issues.
Only thing I can think of is waiting for a return to stock unrooted method to Come out and re-root.

biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Hey I was having the same problem and I fixed it myself messing around with a few things I could think of.
Here it is pasted from another thread.
Dinked around with a few ideas and got my problem fixed! Heres what I did.
1. Made a backup of system in twrp just in case.
2. Formatted system in wipe > advanced > and only checked system.
Panicked because I thought I bricked my device, wouldnt boot farther than the lg logo,
(next steps might be unnecessary but I panicked and tried them lol)
3. still had fastboot access so I repeated step 3 in the root method.
4. Reflashed boot2.img
5. Rebooted to recovery with volume- power, release power while keeping volume- at lg for a second then repress and hold power. Yes twice to get to recovery.
6. Restored system backup. (was able to fully boot now but with lag)
7. Reflashed konverged kernel.
And everything is working perfect now and I have my r/w ability and can mount system in recovery without having to select mount as read only.
---------- Post added at 09:57 AM ---------- Previous post was at 09:10 AM ----------
You can probably just wipe your system like I said in the previous post then Just restore it. I panicked and did a bunch of extra stuff. I realized that when I did my initial backup of my system, or said that its size was about 126247251477482716MB. So I'm guessing when I did my restore (possibly what happened to yours) that it somehow messed up the system.

TWRP or Other issue?

I"m having issue with flashing roms, kernels and restoring on my device and i'm not sure if its cause a process was done incorrect and/or a TWRP.
I have a 2017U. Bootloader is unlocked, TWRP 3.1.0, and currently on stock B19 (no root, via TWRP with Draken's Stock system).
Here are the issues I"m facing:
1. Unable to Restore backup. I've made a backup and selected Boot, System and data. Also selected "compression". Restore shows complete, but device freeze on boot screen (the one says hit vol for more options).
2. Issue flashing kernel. I tried flashing Beastmode (a couple of previous versions up to the most currect R45). I keeps booting back into Recovery. I then tried flashing the stock kernel from Freeza and it still boots into recovery.
3. Flashing Roms. This one is possibly a rom issue, but just wanted to throw it out there any ways in case it's not. Flashed Bad Boys rom. Works fine when installing with SU or Magik, but doesn't boot if it select "no root"...
Any help/advice is appreciated.

You either need to flash supersu, or no-dmverity to patch the kernel to bypass this security feature.

3.1 is also not ready according to twrp thread.
Sent from my ZTE A2017U using Tapatalk

Thanks guys.
Just having a difficult time with TWRP recently. I wasn't able to restore properly on 3.0.4.
Every time i tried to restore, it says i need to uncheck mount system partition read only. Do need to flash the no-dmverity after i restore?

Stuck in bootloop in all LOS and OOS based roms

Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?

Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.

Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.

I have now also tried flashing the stock boot.img, but no difference.

I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work

"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?

After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.

Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.

If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead

It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?

Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far

You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.

https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?

I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578

Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP

Yeah, I tried with Gapps, and I never rooted before first trying to boot.

As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%

Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation

Bump. I am also stuck in this state

Orangefox or RedFox for Oneplus 6T/fajita or other recoveries beside TWRP?

I was wondering if there is alternative option for Oneplus 6T/fajita recovery, like OrangeFox, RedFox, or other recoveries beside TWRP. TWRP doesn't work to restore on OP6T after backup. If I try to restore from previous backup, I will always end up in a continuous boot loop :'( and to resolve is issue, I have to flash the original ROM again but that affects some of my apps, so I have to check each app and reinstall them. In general TWRP doesn't work well on OP6T like other phones, and I couldn't find any alternative recovery options, and I wish someone is working on this.
Please let me know, even if there is beta or unofficial version that works with full ROM Backup and restore.
Thank you
FYI- I tried TWRP on different Pie custom Roms and OOS9 but the result is always the same, endless boot loop.

Nothing exists

You just taking a wrong steps while restoring. I've already done a two or three successful restores
Just backup these partitions:
1. Boot
2.System image
3.Vendor image
4.Data

romixer said:
You just taking a wrong steps while restoring. I've already done a two or three successful restores
Just backup these partitions:
1. Boot
2.System image
3.Vendor image
4.Data
Click to expand...
Click to collapse
I tried in that order and it doesn't work. I always end up in the boot-loop.
I even tried the following steps.
1. Boot to twrp recovery after full backup
2.Restore System image only
3.Reboot to twrp recovery
4.Restore Vendor image only
5.Reboot to twrp recovery again
6.Restore Data only
7.Restart
=>End result is the same, boot-loop.
I think TWRP is only good to flash zip files on Oneplus 6T .

duckduck2020 said:
I tried in that order and it doesn't work. I always end up in the boot-loop.
I even tried the following steps.
1. Boot to twrp recovery after full backup
2.Restore System image only
3.Reboot to twrp recovery
4.Restore Vendor image only
5.Reboot to twrp recovery again
6.Restore Data only
7.Restart
=>End result is the same, boot-loop.
I think TWRP is only good to flash zip files on Oneplus 6T .
Click to expand...
Click to collapse
You must be doing something wrong, perhaps using the wrong outdated version? The latest "unofficial" version posted here works, I can personally attest to that, but the older "official" version available on the TWRP site doesn't. It's outdated, and only works with Oreo and older ROMs.
There were issues with the "unofficial" TWRP and "Q" up until a couple of months ago that required the flashing of an additional file to get it to work properly, because of encryption errors, but even during that time period it was still working as expected on Pie.
Double check what you're doing, as you are making a mistake somewhere. The problem isn't with TWRP.
Link to the OP in the TWRP developer's thread here.