Sounds good, but apparently not true in all cases: I'm currently running on latest Stock OOS 11.1.x with maoronofrio's TWRP 3.4.0-1 as recovery.
Sure, but it's not TWRP I'm talking about but the Lineage recovery. And I'm talking about the to boot into a recovery from bootloader using
fastboot boot <name_of_revovery.img>Your post just was a real life saver: slightly different ROM (Jaguar) but the exact same situation - incl. the "don't ask!" part
. I learned a lot and feel ready to try this out. Just a few questions:Good on you to read instead of just asking questions that have been answered multiple timesYesss - I made it, really read most of the 54 browser pages of this thread
- currently I'm running a different A11 based custom ROM. I plan to follow these steps from @diemadedrei (https://forum.xda-developers.com/t/rom-official-enchilada-11-lineageos-18-1.4174687/post-85600297). I guess I still have to format data partition before first boot into system? Or can I risk keeping \data as it is now?
- in regards to flashing updates: while I was still running stock OOS I always used this sequence:
1. d/l and install full OTA
2. from Magisk run TWRP A/B retention script
3. from Magisk run "install to inactive slot"
4. reboot
Is this still a valid concept with LOS 18.1? (yes, I'm fully aware that I *should* use LOS recovery instead of TWRP...)
- in my currently used ROM I don't have the "ADB As Root" switch in developer options; I already edited /system/build.props (added ro.debuggable=1) and rebooted, but still no switch. And no way to use "adb root", just receiving the "ADB root is disabled..." message. >> is this switch available in LOS?
Thanks for your tips
The clean way would of course be, formatting data, yes. If the other ROM is Lineage based, it might work, if it's OOS based (or anything other than LOS) you will probably just end up with a clusterfuck. But you should always be able to bott into twrp, so no real damage should be expected (don't quote me on that)I admit having skipped some of the "face unlock"-related postsGood on you to read instead of just asking questions that have been answered multiple times
you will have to update the firmware to oos11 in order to use LOS 18.1
Thanks.
No, there are new blobs that are not included in LOSThanks.
So no chance to update without installing everything form the scratch again?
That's annoying and pretty much work to do, if I first have go to OOS11 and then back again to LOS.
But what's new in firmware OOS11 , that I can't jump direct from 16.0 to LOS18.1 ?
A new partioning? Could also be done probably by TWRP?!
Well Thx, I'll have a look on that post.
You can update from 16 to 17 and then from 17 to 18 without wiping, as I did the same. You will still need the corresponding OOS versions for each, so Flash these before flashing the next LOS version. It has been stated somewhere why the blobs are not included, I don't remember.Well Thx, I'll have a look on that post.
But to get you right:
I could do an update from LOS16.0 to 17 w/o wiping data?!?
Then I could do an update from LOS17.0 to 18.1 ?!?
Or is exactly this not possible due to the missing blobs in LOS18? (which only OOS11 have)
Btw1: Why they are missing? And why only vendor stock has it?
Btw2: Will there be a LOS 19 for enchilada dev?
Or should i better buy in the end a new oneplus dev to have latest secu patches on my phone ?
Ok. Thanks for 'ur patience.
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:GAPPS are preserved. If you dont need anything fancy, then also just use LineageOS recovery. This will most probably also fix your update isues on OP3.Dear Forum, i plan to switch my OP6 back to LOS as well.
Back, because once i bought it some years ago, i was running LOS on it, but then switched to OOS, due to some struggles (and it was the first phone since the good old Motorola Milestone, where CyanogenOS gave me Froyo for the first time
I don't need root or anything extraordinary, just LOS and Google apps. my Question: will the build in updater work and preser Gapps during updates? In the past due to A/B Layout, i always had to go to recovery, flash update and gapps, reboot into Recovery, flash gapps again, to no loose them.
And on my OP3 the builtin Updater is not working, i always have to flash manually through TWRP ;(
Thanks in advance!
No need for fastboot. Go into the Magisk app before installing the OTA, click on Uninstall Magisk, then Restore Images. Now install the OTA via the built in updater. Once the OTA update is installed, do not reboot. Go back into the Magisk app. Click on Install Magisk, select Install to Inactive Slot (After OTA), and only then reboot.
![[GER]Roxxor](/data/avatars/s/2923/2923886.jpg?1600603243){kind=avatar}
