Database Users

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

Recover S8 from TWRP

I have a systemless-rooted SM950FD model with AQDG firmware/baseband, with TWRP.
Before anything took place I backed up with TWRP 3.1.0 the essentials: boot, recovery, system, data, baseband & efs.
Wanting to update to the latest AQH3 firmware without losing any data, I used the 'TWRP-flashable' firmware provided by Renovate here http://www.renovate-themes.de/firmware.html
This zip claims to update bootloader, modem and TWRP.
The update seemed to go well, but when I rebooted I the phone was stuck on Galaxy S8 logo. TWRP disappeared, as did any other recovery, so I had to flash TWRP from ODIN (at which point I updated to latest TWRP version, 3.1.1-2)
Now back on TWRP, I am trying to restore a bootable system from my backup, but no combination has worked for me so far. I always do a quasi-full wipe (system, caches, data) and restore boot/system/data/baseband/efs (with minor variations between the 5). So far nothing has succeeded in booting the phone, it always gets stuck at the Galaxy S8 screen.
At this point I could totally install a stock-like rom which will fast-forward me to the latest version, but since my goal was to keep my original stock rom without losing sms/apps, I would at least need to boot up once in my original backed up state.
Any ideas?
Thank you very much,

Batman Rom Is very close to stock.
I would say flash that one. In fact it's better than stock.
Sent from my SM-G950F using Tapatalk

SM-G950F FLASHED WITH TWRP WITHOUT OEM UNLOCK
Hi guys I need your professional opinion the stupidity I done. I Flashed cf-auto root and without to enable OEM unlock i Flashed TWRP. After reboot the phone stuck on the Samsung logo.
Is the phone dead? Any chance to recover ?
Thanks for ur time

erclalle said:
I have a systemless-rooted SM950FD model with AQDG firmware/baseband, with TWRP.
Before anything took place I backed up with TWRP 3.1.0 the essentials: boot, recovery, system, data, baseband & efs.
Wanting to update to the latest AQH3 firmware without losing any data, I used the 'TWRP-flashable' firmware provided by Renovate here http://www.renovate-themes.de/firmware.html
This zip claims to update bootloader, modem and TWRP.
The update seemed to go well, but when I rebooted I the phone was stuck on Galaxy S8 logo. TWRP disappeared, as did any other recovery, so I had to flash TWRP from ODIN (at which point I updated to latest TWRP version, 3.1.1-2)
Now back on TWRP, I am trying to restore a bootable system from my backup, but no combination has worked for me so far. I always do a quasi-full wipe (system, caches, data) and restore boot/system/data/baseband/efs (with minor variations between the 5). So far nothing has succeeded in booting the phone, it always gets stuck at the Galaxy S8 screen.
At this point I could totally install a stock-like rom which will fast-forward me to the latest version, but since my goal was to keep my original stock rom without losing sms/apps, I would at least need to boot up once in my original backed up state.
Any ideas?
Thank you very much,
Click to expand...
Click to collapse
try flashing stock AQH3 then booting then flashing TWRP again.

mweinbach said:
try flashing stock AQH3 then booting then flashing TWRP again.
Click to expand...
Click to collapse
Thank you, I ended up flashing a custom ROM, unfortunately I did not have time to do this intermediary step, but thank you!

Boot Partition Hidden in TWRP

My rooted Axon 7 (A2017U) does not show the boot partition in TWRP when backing up or restoring a backup that previously showed the boot partition. Here is what I did prior to the problem:
1. Manually updated stock rom to B32 using DrakenFX procedures, which includes flashing bootstack. (I made a backup after the upgrade of boot, data, and system - as usual.)
2. When I restored AICP nandroid, boot was shown along with data and system. Phone operated normally, but would not flash OTA upgrade - error 7. (Attempted to flash a previous version that I had flashed before with the same error 7.)
3. Rather than unzipping the rom and deleting the asserts line, I flashed the universal boot image from LineageOS and was able to OTA without issue, but when I ran the TWRP backup, boot did not show and only system and data backed up.
4. Restored the stock nandroid, boot did not show.
My phone is operating normally, but I find it disconcerting to have made an unintended change and would appreciate any help in correcting my error.
Thanks in advance.

Hi have you fixed your problem or not?

William Guo said:
Hi have you fixed your problem or not?
Click to expand...
Click to collapse
No, still waiting for assistance.

Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.

JKSurf said:
Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.
Click to expand...
Click to collapse
That worked. Thank you very much. Weird how that happened.

Just as a matter of interest, I just did a clean install of AICP, which required installation of universal bootstack, and found that TWRP version had been replaced with an old version that did not show boot partition when doing nandroid. Reflashed current build image and boot file was visible.

Keep the latest .img on TWRP, and when you flash the universal bootstack, flash the TWRP .img after. I've asked over at the LOS thread if they could update the TWRP version on the bootstack and nobody answered lol

Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.

jojofreddy said:
Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.
Click to expand...
Click to collapse
You don't change your recovery, the universal bootstack zip does
It's the same whether you use the zip from TWRP's official website or raystef66's download center really

booting to twrp

Yesterday I unlocked my lg-h870´s bootloader using offical method. after flashing twrp I wasn´t able to boot system because every time I hit reboot system it takes me back to twrp. I tried to install custom rom but after flashing the problem still remains.:crying:
so please tell me what should I do. (sorry for bad english)

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.