I installed LineageOS with and without Gapps and it still crashes my Shield. Should I try a different build from Lineage's page? I was running 12/15/21 with Gapps 12/17/21. Is it common for LineageOS to crash, freeze and reboot by itself?
I installed the build from 12/15/2021 and have not experienced a crash, freeze or reboot yet. I have never tried to install gapps. So if you followed the installation instructions in the LineageOS wiki, it should work.
Did you wipe your partitions prior to building? Sometimes flashing a new system onto the existing one without doing so, can result in, such undesirable behavior.. If you didn't this could help explain how and why, code is in description box
would also download the latest Lineage Build, they do Nightlys
jenneh said:
Did you wipe your partitions prior to building? Sometimes flashing a new system onto the existing one without doing so, can result in, such undesirable behavior.. If you didn't this could help explain how and why, code is in description box
would also download the latest Lineage Build, they do Nightlys
Click to expand...
Click to collapse
I wiped the partitions in TWRP using your guide. I have not tried wiping those partitions manually in fastboot. That could explain the issue I was having. Thank you
Delete the partitions with TWRP unfortunately did not work for me. TWRP has not recognized any memory. So I flashed the lineage_recovery and everything worked as it should.
Kladderadatsch said:
Delete the partitions with TWRP unfortunately did not work for me. TWRP has not recognized any memory. So I flashed the lineage_recovery and everything worked as it should.
Click to expand...
Click to collapse
Thank you for sharing, this will Surely help someone else in the same shoes. Glad you got it working!~!
Unfortunately it still reboots on its own. I tried wiping all the partitions you listed and flashed the proper files to get LineageOS working. It's better to wait until the build gets more stable
Skel40 said:
Unfortunately it still reboots on its own. I tried wiping all the partitions you listed and flashed the proper files to get LineageOS working. It's better to wait until the build gets more stable
Click to expand...
Click to collapse
I'm sorry to hear that! But thank you for being honest and letting us know you are still having problems! I think you are correct that waiting for a more stable build is a good step.
I have only gotten my feet wet in kernel editing and manipulation, so It's A lot Lineage does for us, its just a matter of them getting the Science down to a good, clean, consise, logic
I have now replaced the lineage recovery with TWRP and the memory is now recognized.
I must say everything runs stable, without crashes or so.
Also wiping the partitions messes up with fastboot booting TWRP. I only was able to have Lineage recovery flashed and booted up using boot recovery kernel found in bootloader mode. I don't know what I'm doing wrong here but another issue is the recovery itself directly from Lineage. I tried to factory reset as it told me to after wiping the partitions and it failed. Emmc is not supported, factory reset failed.
What wouldn't make sense is it's not the Shield's power supply issue or any of the components failing after booting into LineageOS. Nvidia's OS works perfectly without constant freezing and reboots. Hopefully this issue can be resolved at some point. It's a bummer I've tried everything to get this far.
I the same problem and i noticed an error in the fastboot flash of mdarcy.dtb
I checked the batch file that you tasked it to and found
Fastboot flash mdarcy.dtb mdarcy.dtb.img
I changed it to fastboot dtb mdarcy.dtb.img
And it corrected the partition
Related
I've not done too much with my phone over the years, flashed the odd root package and whatnot and never really had an issue before.
This time i'm pretty stumped.
Wife got a new phone for christmas, so i figured i'd try installing CM13 on her old Nexus 4
Did fastboot oem unlock, that worked fine, flashed the latest TWRP (2.8.7.0) using fastboot and that also worked fine.
Rebooted into TWRP and it was complaining about /data not being mountable. Wiped system/cache/data etc and got TWRP to format data which fixed the error.
Copied the latest nightly of CM13 over as well as opengapps nano, and flashed them.
Flashing worked fine, with no errors displayed, and then i rebooted the phone.
It gives me the google screen, then boots into TWRP again.
tried flashing an earlier build of CM13, and also tried not flashing the opengapps, but everything has the same result, phone just boots into recovery. Even tried flashing an unofficial build from this thread:
http://forum.xda-developers.com/nexus-4/development/rom-unofficial-cm13-marshmallow-builds-t3236487
Same thing.
What am i doing wrong?!
Fixed it.
Reflashed factory firmware and started from the beginning and it worked fine this time.
Thanks for the help.
Aragorn84 said:
Fixed it.
Reflashed factory firmware and started from the beginning and it worked fine this time.
Thanks for the help.
Click to expand...
Click to collapse
That happens because system partition's filesystem gets corrupted fyi. That's why reflashing factory image fixes it , it re-formats the partition. You can also do that manually , without flashing the factory image. Inspect the .bat file of the factory image in notepad , you'll see the code.
I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.
Make sure everything is formatted as ext4 and update firmware to 3.6.1 just to rule it out.
I would use the latest twrp.
I go to format tick all the boxes and clear everything then go to reboot > recovery. Once back in twrp copy the ROM and gapps across from pc install ROM and gapps together, wipe cache and dalvik reboot.
I'm in the process of doing that now.
The TWRP that I'm using is 3.1.1-0 which looks to be the latest. I am working with OOS 3.5.8 but will look at downloading 3.6.1. I am working to get Lineage 14.1 on there once everything is stable.
I ran into another weird is when using the qualcomm recovery tool:
My method is to enable ADB, enable OEM Unlock, enable Advanced Reboot.
Reboot into fastboot
Fastboot oem unlock: is successful
Fastboot reboot
I then go through renabling ADB and Advanced Reboot, OEM Unlock is still enabled.
I then reboot into fastboot
Fastboot flash recovery twrp-3.1.1-0-oneplus2.img
This completes successfully and then I fastboot reboot.
I have tried several times to get into TWRP but I keep getting the stock recovery.
I have tried to reflash recovery but nothing ever changes.
Is there possibly something wrong with the OEM unlock that says it was successful?
How do I go about troubleshooting this?
Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.
cyrus104 said:
Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.
Click to expand...
Click to collapse
Internal doesn't really matter to be honest, did you check they data and system are formatted as ext4.
It is in twrp advanced wipe options.
Did it ever boot ?
I did doubt check the data and system are formatted as ext4.
I let it sit for 3-4 hours and didn't see any progress.
Try a different rom. There are a lot of lineage based roms around.
I tried that and am getting the same results. Even if I flash a full TWRP backup from a time when I had it known to be working it happens.
I've tested this with 3 different roms now. My latest attempt has been to update TWRP to 3.2.1 and then install lineage 14.1 20171208. I also tested with Paranoid and Carbon because they were near the top of my list not because I know anything about them.
The phone just never gets past the boot animation. If I reboot to recovery is there a log I can pull to see what the issue is?
Thanks
Would like to see if anyone has any thoughts. If I run OOS I can use the phone but as of right now I can't use any other rom.
Is there any advanced fastboot or wipes that can be done to get it to boot. Is there any type of debugging that will show me what's happening when it tries to boot.
Just trying to bump this, I really need a way to debug this problem. Besides running OOS, I have a feeling this device is bricked and the mega unbrick guide doesn't work.
Also looks like if I try to put Kali on top of the base 3.5.8, the phone goes into the animation loop. So any change after OOS on the device puts it into an animation loop.
Is there a way the system or boot locked? Even thought I can TWRP anything onto the phone without errors.
Hey!
I've got the same issue it seems, phone just sticks to boot animation when flashing any other ROM than OOS 3.6.1.
Any update?
EDIT :
problem was with the persist.img
Flashed a different firm file and it was resolved
cyrus104 said:
I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.
Click to expand...
Click to collapse
OOS does not refuse to boot if a mountable partition is corrupt. This is not the case with lineage. If a mountable partition is corrupt and the corresponding fstab entry does not allow lineage to format and somehow mount it then init never proceeds
Try flashing this file: https://glassrom.botstack.host/firmware/oos-3.6.1-firmware-signed.zip and try again
Note that this file reboots the device after the flash is done so don't use twrp queue to flash this file. Flash this file last
---------- Post added at 17:45 ---------- Previous post was at 17:34 ----------
Alternatively this is a method I don't recommend to beginners because they accidentally give twrp logs to devs without realising it
You can get logs by making the forcing the device to "crash" through the power button
Here's how it's done: you boot the non-booting ROM and wait for about a minute. Then press power + volume down while it's on the bootanimation. You have to hold it until you see the oneplus logo and boot to twrp
TWRP's kernel will recover the last booted kernel's log from ram and place it in /sys/fs/pstore
First you have to open the log yourself to check if it's valid. The file is console-ramoops-0. All other log files in that location are invalid for your specific issue
Now for an ordinary user this is hard. They can't tell if the log is a recovery log or a ROM log. Since we're dealing with official lineageos we assume selinux would be enforcing
You want to search for this string "permissive=1". On Linux just do cat console-ramoops-0 | grep "audit" (quotes are part of the command)
If you're on windows then you can download Linux and get the logs. Stop bothering me
If you see the string "permissive=1" in the log you have accidentally fetched a recovery log
Go back and boot again and wait for about a minute if selinux is permissive
The string should read
"permissive=0"
That means selinux is enforcing and this is indeed a ROM log
Send this log here
Hello,
Was this problem ever solved? I am experiencing the very same thing with every single ROM i have tried so far. TWRP is installed, I can install all ROMS but when I try to boot the phone, it just won't get passed the booting animation.
Thank you
I have been running the No Limits Nougat build for a while with no issues. Decided to flash the Oreo build yesterday.
Followed the directions, ran a backup and checked it, and wiped (not a rookie, have flashed plenty of phones previously) but afterwards I'm having major issues.
The initial flash seemed like it went fine, the phone tried booting but went back to recovery and when I looked at the files it looks like they have been encrypted. I'm not getting a message when TWRP starts to put in my password which I thought was the issue. I've tried different recoveries and different ROMs but if I can sideload the ROM on and flash it after I restart it goes back to TWRP with encrypted files.
I know I've lost the data on the phone which is fine, I had dragged some backups to my computer but I can't figure out why every time I flash anything the phone is getting encrypted and pretty much bricked. I figured that once I factory reset and clean installed the encryption would be gone. Am I out of luck? I tried flashing the stock ROM from TWRP and get 'Updater Process ended with ERROR: 7'.
Not sure what to try next, HELP!
oneunder311 said:
I have been running the No Limits Nougat build for a while with no issues. Decided to flash the Oreo build yesterday.
Followed the directions, ran a backup and checked it, and wiped (not a rookie, have flashed plenty of phones previously) but afterwards I'm having major issues.
The initial flash seemed like it went fine, the phone tried booting but went back to recovery and when I looked at the files it looks like they have been encrypted. I'm not getting a message when TWRP starts to put in my password which I thought was the issue. I've tried different recoveries and different ROMs but if I can sideload the ROM on and flash it after I restart it goes back to TWRP with encrypted files.
I know I've lost the data on the phone which is fine, I had dragged some backups to my computer but I can't figure out why every time I flash anything the phone is getting encrypted and pretty much bricked. I figured that once I factory reset and clean installed the encryption would be gone. Am I out of luck? I tried flashing the stock ROM from TWRP and get 'Updater Process ended with ERROR: 7'.
Not sure what to try next, HELP!
Click to expand...
Click to collapse
Which guide did you follow? What steps did you exactly take and which version nougat rom you have and which oreo build(stable/beta) do you want to install?
There are plenty of instructions, like this one here: https://forum.xda-developers.com/showpost.php?p=75155514&postcount=8618
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!
Hi guys,
I have unlocked the bootloader of my S5e (T720) installed Magisk and TWRP. Wiped the unit and installed Gapps + Lineageos 17.
That said: I keep booting into TWRP...
How to make the unit boot in Lineageos please?
Thanks
Seems like something went wrong with the OS installation. I would advise that you reinstall the OS again.
Did you ever find a solution to this? I am in pretty much the same situation but I didn't use magisk cause I didn't want to root. I tried flashing lineage 16 and 17 after wiping system, data, vendor etc.. I always just seem to end up looping back into TWRP. Not really sure what I'm doing wrong, I do always get the warning asking me to press the power button to continue as I'm not running official software and have an unlocked bootloader so maybe there is some security feature that's still preventing me from getting in? If anyone could offer any help I'd appreciate it a lot, I'm very new to all this.
Yelnat said:
Did you ever find a solution to this? I am in pretty much the same situation but I didn't use magisk cause I didn't want to root. I tried flashing lineage 16 and 17 after wiping system, data, vendor etc.. I always just seem to end up looping back into TWRP. Not really sure what I'm doing wrong, I do always get the warning asking me to press the power button to continue as I'm not running official software and have an unlocked bootloader so maybe there is some security feature that's still preventing me from getting in? If anyone could offer any help I'd appreciate it a lot, I'm very new to all this.
Click to expand...
Click to collapse
Wiping System and Vendor? Why did you do that? That is likely why it doesn't boot. You will likely need to go back to stock to put those back and start over. I've found on these any deviation from the instructions below it's not going to work.
LOS Install Instructions
Magisk worked for me, but on this particular device I've found mods have to be flashed from Magisk afterwards from Magisk and not in TWRP like I do on other devices.
OhioYJ said:
Wiping System and Vendor? Why did you do that? That is likely why it doesn't boot. You will likely need to go back to stock to put those back and start over. I've found on these any deviation from the instructions below it's not going to work.
LOS Install Instructions
Magisk worked for me, but on this particular device I've found mods have to be flashed from Magisk afterwards from Magisk and not in TWRP like I do on other devices.
Click to expand...
Click to collapse
I only deviated when it didn't work, Ironically I fixed the issue by wiping literally everything via TWRP and then trying to reinstall lineageOS. I did have a problem with it taking hours to boot the first time, but I found that I had to install lineageOS without gapps, then reboot into TWRP and flash gapps afterwards. Strange Issue but all is well that ends well I suppose.
Did you guys get a solution for this? I am in the same situation. I have the ROM and Gapps on the external card, and although I installed it again, I am still stuck in this bootloop.