OnePlus 6 - LineageOS install trouble - OnePlus 6 Questions & Answers

SOLVED: The solution was simply to use LineageOS recovery instead of TWRP.
Followed the install directions on the lineageOS website as I had beforehand, except I didn't substitute LineageOS Recovery for TWRP this time.
---------------------------------------------------------------------------------------------------------
Hello everyone. New member, first-time poster, long-time lurker.
I've been trying to install LineageOS 17.1 onto my (new-to-me) OnePlus 6 (A6003) but for some reason, once I finish the install process, the phone will not boot system but instead falls back to recovery mode.
*Edit:
Files used-
OOS 10.3.12 (OnePlus6Oxygen_22.J.55_OTA_055_all_2107132218_71d1c06b31fc)
LineageOS 17.1 (lineage-17.1-20210420-nightly-enchilada-signed)
TWRP (twrp-3.5.2_9-0-enchilada)
*
Here's what I've done:
- Unlocked the bootloader and enabled USB debugging
- ran adb reboot bootloader, then flashed TWRP.img and sideloaded the TWRP.zip and rebooted to recovery to make sure TWRP was installed (idk why)
**I was under the impression I needed to flash OOS.zip to both slots (along with TWRP) before I tried to sideload LineageOS, so I attempted that but OOS wouldnt sideload, so i thought my sideload was messed up. I later realized OOS.zip was too big to be sideloaded (tried to make adb.exe large address aware to no avail)**
- I then pushed OOS and TWRP zips to /sdcard/ on the device
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to recovery to change slots
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to system to check things out. Both slots are now 10.3.12
- booted back into twrp
- Clicked install, navigated to LineageOS 17.1, installed, hit the back arrow, installed TWRP, rebooted to recovery to change to slot B.
- For some reason, slots didnt change, so I manually changed to slot B.
- Clicked install, files now looked different in slot B (encrypted I guess?) and the files I had placed on the phone were gone.
- Instead of installing the same way, I ADB sideloaded LineageOS, hit the back arrow, then sideloaded twrp.
- Attempted to boot system, phone tries to boot into system, but instead boots into recovery mode.
Swapped slots, same problem.
I'm not sure what I'm doing wrong, but if someone could give me some guidance, it would be much appreciated.
Thank you!

TreasureSeeker said:
Hello everyone. New member, first-time poster, long-time lurker.
I've been trying to install LineageOS 17.1 onto my (new-to-me) OnePlus 6 (A6003) but for some reason, once I finish the install process, the phone will not boot system but instead falls back to recovery mode.
Here's what I've done:
- Unlocked the bootloader and enabled USB debugging
- ran adb reboot bootloader, then flashed TWRP.img and sideloaded the TWRP.zip and rebooted to recovery to make sure TWRP was installed (idk why)
**I was under the impression I needed to flash OOS.zip to both slots (along with TWRP) before I tried to sideload LineageOS, so I attempted that but OOS wouldnt sideload, so i thought my sideload was messed up. I later realized OOS.zip was too big to be sideloaded (tried to make adb.exe large address aware to no avail)**
- I then pushed OOS and TWRP zips to /sdcard/ on the device
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to recovery to change slots
- Clicked install, navigated to OOS.zip, installed, hit the back arrow, installed TWRP, rebooted to system to check things out. Both slots are now 10.3.12
- booted back into twrp
- Clicked install, navigated to LineageOS 17.1, installed, hit the back arrow, installed TWRP, rebooted to recovery to change to slot B.
- For some reason, slots didnt change, so I manually changed to slot B.
- Clicked install, files now looked different in slot B (encrypted I guess?) and the files I had placed on the phone were gone.
- Instead of installing the same way, I ADB sideloaded LineageOS, hit the back arrow, then sideloaded twrp.
- Attempted to boot system, phone tries to boot into system, but instead boots into recovery mode.
Swapped slots, same problem.
I'm not sure what I'm doing wrong, but if someone could give me some guidance, it would be much appreciated.
Thank you!
Click to expand...
Click to collapse
Hello!
LineageOS 18.1 is the latest stable official version. If that suits you, you should repost in the dedicated thread for help

duttyend said:
Hello!
LineageOS 18.1 is the latest stable official version. If that suits you, you should repost in the dedicated thread for help
Click to expand...
Click to collapse
Hey, thanks for replying! I opted for LOS17.1 because I didn't want to upgrade to android 11 but at this point I am willing to do whatever to get this phone running Lineage so I will move this post there like just suggested if I don't receive help here

That sideloading and slot copying stuff sounds intense. Can you try getting it back to the state where you have TWRP installed (the way you did that sounds right, you need to either "install" the zip or flash the img through the advanced menu for it to stick) and 10.3.12 applied to each slot (you can do this in TWRP by dragging the.zips from your computer to phone internal storage, no terminal needed)?
After that it's simply a matter of dragging the ROM zip to internal storage and installing it from TWRP if I'm not mistaken. The LineageOS guide looks weirdly complicated – though you might as well be safe and follow the slot copying steps before flashing the ROM as well. Though for convenience I'd still do it by dragging it from the computer not by adb.
(BTW disclaimer I haven't messed with roms a lot on OP6. If you need LineageOS specific advice best place would prolly be where other poster suggested.)

Related

Can't install lineage-15.1-20180918 on a Google Pixel (sailfish) - bootloop

Hello,
I'm trying to install lineage-15.1-20180918 on my new (second hand) Google Pixel (sailfish). It came with Android 7.1.0 (NDE63H, Oct 2016) pre-installed.
No mater what I try to do, after installing Lineage zip file, I always get a warning saying that there is no OS. When I try to reboot to System, I am stuck in a boot loop between a screen saying that I should lock the bootloader and another one displaying the Google logo.
General information about device and softwares used
I run Debian on the PC that is used for the install, adb (v 1:7.0.0+r33-1) and fastboot (v 1:7.0.0+r33-1) are installed.
I got the Lineage zip from there (the shasum is good).
I got the TWRP image from there (v 3.2.3-1).
What I did
I followed the official howto there.
I have unlocked the bootloader, can boot into the TWRP recovery.
TWRP is launched via
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
I did "Format Data", then "Advanced Wipe" (selected everything and wiped).
Then
Code:
adb push lineage-15.1-20180918-nightly-sailfish-signed.zip /sdcard/
(Note that I first tried to sideload both this zip and the suaddon one, given that it didn't seem to work, I wiped everything out again and went with the adb push method)
And, finally, went back to the "Install" menu, selected the zip and launched the install process (without checking the "Verify signature checkbox").
I managed to restore the initial backup created with TWRP, the system booted normally. I then tried a LOS install again and got stuck into a boot loop again.
Problem
At the end of this process, when offered with a swipe gesture to reboot, there is a warning saying that no OS is installed. Swiping to reboot leads to the reboot loop described above.
Any idea on what I can do to fix this issue?
Huge thank you in advance!
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
post-mortem said:
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
Click to expand...
Click to collapse
I did not. But there were other issues as well (I used outdated version of adb and fastboot), I followed the instructions there (due to the stupid rule for new users, I can't post a direct link to it) old.reddit.com/r/LineageOS/comments/9h0aqy/cant_install_lineage15120180918_on_a_google_pixel/e6nbqg6/ and it worked

How to update to Android 10 open beta 1 and keep TWRP / Magisk

EDIT: After a few reboots, TWRP stopped working.. now if I try to enter recovery, I get into fastboot instead. But I can still boot the system fine and I still have Magisk. Sorry.. looks like TWRP on this version is still a no-go for now..
I leave the guide here to keep the discussion open, though.. and after the steps some more info on what exactly worked for me..
Hi all, the following steps worked for me (not really, see edit above), but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
EDIT 2: Just to give some more information in case someone else wants to try, here's what I did AFTER the steps below:
- Rebooted into OOS open beta 1, just to check that it was booting.. worked.
- Rebooted into TWRP and did a complete wipe, including the internal storage (I wanted a clean install of OB1)
- Rebooted into OOS and did the phone setup (Google account, ecc) including setting up a lockscreen pattern, but no figerprints yet.
- Rebooted again into TWRP to install Magisk, and everything worked, TWRP also asked for my pattern and decrypted data correctly
- After that I didn't reboot anymore for a while, and completed the setup with apps, fingerprints, etc.. and also installed a magisk module (quickswitch), but without using recovery.
- The next time I tried to reboot into recovery, I wasn't able anymore.. I was getting into fastboot instead, but the system can still boot just fine.
cc_rock said:
Hi all, the following steps worked for me, but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
Click to expand...
Click to collapse
Anyone tried?
This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?
kyljys said:
This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?
Click to expand...
Click to collapse
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.
I bet it stopped working after magisk install. It does the same fir the stock recovery also. No recovery, goes to bootloader.
Oh.. So that means we either have twrp and no root... Or root and no recovery... Choose whatever one wants... Hehe.. Thnx op for the efforts though
cc_rock said:
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.
Click to expand...
Click to collapse
One thing to try would be installing magisk 19.4 from twrp. In canary thread there's a discussion on this very problem with other oneplus devices with A10 and magisk 20.1 that the recovery disappears. Magisk 19.4 did have some fixes regarding Android 10, maybe worth a shot?
Though we could wait the next version of magisk as this problem seems to be under investigation.
I'm able to to keep twrp with magisk 19.3
[email protected] said:
I'm able to to keep twrp with magisk 19.3
Click to expand...
Click to collapse
Ive also managed to do this after a fair bit of fiddling. A quick guide below as im off to bed.
1) you need to be rooted
2) Flash twrp installer in magisk manager (twrp-3.3.1-x_blu_spark_v9.101_op6.zip)
3) reboot to bootloader
3) fastboot flash boot boothybridbeta2.img ( https://drive.google.com/open?id=1JCltKatjRUk1XdEibAme8MnDJxMkzhwE ) boot image is from [ROM][PORT][10.0.0] OnePlus7 Open Beta 3 Port for OnePlus 6 [12.10.19]
4) fastboot reboot
5) reboot to recovery via adb
6) run magisk uninstaller.zip
7) flash stock boot.img in twrp
8) flash twrp installer.zip
9) reboot recovery (to see if it works)
10) reboot phone and choose boot to recovery from phone system again to test it works
11) install magisk v19.3 installer zip in twrp
12) reboot

Trouble booting after LineageOS update

Today I downloaded the latest nightly (lineage-16.0-20200123-nightly-I01WD-signed) and did a backup of System, Data, and Boot before flashing it. After rebooting, the LineageOS boot animation loops continually. It also overwrote TWRP with the LineageOS recovery (which I didn't realize was automatically part of the zip. I'm still not accustomed to A/B slot devices without recovery partitions). I can still fastboot into a good version of TWRP that correctly prompts me for my PIN for decryption, so I tried restoring from my backup. The restore seems to finish without problems, but upon rebooting the LineageOS boot animation still doesn't finish. My data/media is still intact and backed up separately, so I can start from scratch if absolutely necessary, but I was hoping there's some easy steps I can try before resorting to that. Let me know if I need to include more information.
EDIT:
I think I got it taken care of, although I don't know exactly why it worked. Here's what I did:
1. Flash the new LOS image I downloaded using fastboot TWRP
2. Boot to newly installed LineageOS recovery mode
3. Flash the same LOS image again from LineageOS recovery
4. Fastboot TWRP again without trying to start system yet
5. Re-flash the old version of OpenGapps I've been using (from Nov 2019 or something)
6. Reboot system

OP6 won't get past bootloader after upgrading from 16 to 17.1

I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom

Question Help stuck in bootloop!

Hello! Today i tried Lineage os (came from PPUI) thought it was nice but i wanted to go back for the extra customisation options.
Steps i did: Removed screen locks
Reboot into TWRP recovery
I wiped the Dalvik+ Data+ Cache
Realised my PPUI restore was in the wrong folder and not the TWRP recovery thought i would just reboot and move it to the corect place
Then i got into a bootloop cause i wiped my os. Now phone says storage is encrypted.
Since i have no access to storage i tried to adb sideload the LOS i had in before and then just do a freshly install of PPUI. At 47% it says adb: failed to read command: No Error, (mobile mentions a magisk module missing) Any ideas?
Guns&roses said:
Hello! Today i tried Lineage os (came from PPUI) thought it was nice but i wanted to go back for the extra customisation options.
Steps i did: Removed screen locks
Reboot into TWRP recovery
I wiped the Dalvik+ Data+ Cache
Realised my PPUI restore was in the wrong folder and not the TWRP recovery thought i would just reboot and move it to the corect place
Then i got into a bootloop cause i wiped my os. Now phone says storage is encrypted.
Since i have no access to storage i tried to adb sideload the LOS i had in before and then just do a freshly install of PPUI. At 47% it says adb: failed to read command: No Error, (mobile mentions a magisk module missing) Any ideas?
Click to expand...
Click to collapse
You still should be able to access TWRP recovery? You can format data partition there and be able to use internal storage on your next boot to recovery.
From the looks of things i have formated all my storage data in my panic state. Thoughts on moving the Rom to the phone to be installed by recovery?
So as it looks i have nothing into the phone itself and i cant send files from the pc! How would i go about getting the LOS rom to the mobile and flashing from there?
Tried Adb sideload and i get error Magisk addon.d failed can not find magisk binaries. Do i flash magisk first?
Update: I get the rom in. i Flash the rom in. and im still stuck to the LOS loading screen for atleast 5 mins Thoughts?
Fixed. for some reason it was the LOS flash that had issues. when i tried flashing PPUI it worked the first time no issues
Lineage install at 47% for poco
I use lineage recovery and I didn't encounter any magisk thingy. That sound like a previous os persistence script which shouldn't be loaded in the first place....but still did for unknown reason
However, important to note that other user flashed using twrp without issue
Try these steps
1. Format Data
2. Sideload latest firmware
3. Sideload nightly LineageOS
4. Sideload opengapp arm64 (if you are using)
5. Sideload magisk (if you are using)
Boot

Categories

Resources