Howdy all,
Every once in awhile I get that urge to want to try Dual Boot Patcher but then I chicken out. Before I reconsider again I have questions regarding bootstacks and ROMs.
I've already gone to B32 bootstack.
Installed and run B32 stock just long enough to look at it. Backed up and wiped.
Installed B32 Dark ROM and ran for awhile. Backed up and wiped.
Went down to Universal Bootloader so I could flash other ROMs.
Was wondering, if I restored the B32 stock would it still run okay without its corresponding bootstack? I've never really been sure if various bootstack requirements apply to just flashing or also to running.
Any insights?
Sure I'll probably do the "try it and see" thing anyway.
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Okay, first part is done.
I restored B32 stock and it runs great.
Updated SuperSU and also have Xposed with Flat Style Bar Indicators (gotta tweak that status bar).
After finishing up some updates and third party apps I can move on to the dual booting stuff.
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
Okay, first part is done.
I restored B32 stock and it runs great.
Updated SuperSU and also have Xposed with Flat Style Bar Indicators (gotta tweak that status bar).
After finishing up some updates and third party apps I can move on to the dual booting stuff.
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
I also had the fear that I would need a different bootstack to flash a rom. Actually you only need to have a stock ROM with whatever bootstack, then just patch the ROM and flash it, and flash a patched SuperSU too. That's basically what I did with LOS and MIUI and both work
Have to wait until my next day off. Apparently /data is encrypted so other ROMs won't boot.
Gotta backup/save/copy stuff and reformat. Bah!
LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
Have to wait until my next day off. Apparently /data is encrypted so other ROMs won't boot.
Gotta backup/save/copy stuff and reformat. Bah!
LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
that's because you didn't flash magisk or supersu after flashing a ROM or wiping. Next time flash magisk as soon as you flash the new ROM. just as a reminder.
Choose an username... said:
that's because you didn't flash magisk or supersu after flashing a ROM or wiping. Next time flash magisk as soon as you flash the new ROM. just as a reminder.
Click to expand...
Click to collapse
You referring to the non-primary ROMs?
I did flash patched SU actually after the first one. The second one I did not.
I get the triple vibration and back to TWRP thing. From every post I've read where that happens the cause is said to be encryption. Didn't think I was but the stock ROM says otherwise.
I'd prefer the issue be superuser related as you said as I would rather not have to format /data.
Thanks.
LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5
could you give me a little insight on that dualboot thing? i softbricked my phone every time i tried it (bootloop after that "linux bootloader")... i previously had a one m8 / Galaxy S3 so this is unkown terrain for me.
thanks in advance :x
marcdw said:
You referring to the non-primary ROMs?
I did flash patched SU actually after the first one. The second one I did not.
I get the triple vibration and back to TWRP thing. From every post I've read where that happens the cause is said to be encryption. Didn't think I was but the stock ROM says otherwise.
I'd prefer the issue be superuser related as you said as I would rather not have to format /data.
Thanks.
LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
No; I meant that not flashing SuperSU encrypts the internal storage. Not on secondary ROMs though; only on the primary.
I had that problem too; the solution was to only flash the secondary ROM, then boot, then go back to recovery and flash whatever else. The problem is that GApps usually make a bunch of trouble if you do this.
I think the MIUI rom already comes with gapps so that's a good alternative. I dualbooted it just to see the state of it and it is pretty okay!
Choose an username... said:
No; I meant that not flashing SuperSU encrypts the internal storage. Not on secondary ROMs though; only on the primary.
Click to expand...
Click to collapse
The primary was B32 stock, restored from backup, already rooted with SU 2.79.
If I were to start from scratch I'd have to do the whole bootstack thing again. Not really a problem, just an inconvenience.
I had that problem too; the solution was to only flash the secondary ROM, then boot, then go back to recovery and flash whatever else. The problem is that GApps usually make a bunch of trouble if you do this.
Click to expand...
Click to collapse
I wasn't using GApps in either try.
First was Dark ROM, Extras, and SU.
Second try was just AOKP alone.
Today is my "Friday" so after work I'll have a go again.
I know this discussion should now be in the Dual Boot Patcher thread but I'm waiting for some success before doing so.
ZTE Axon 7 A2017U, VertexOS Carbide-v3.6 ROM, Tapatalk 4.9.5
To get ready for what I might have to do I backed up /sdcard contents to flash drive and commenced.
Did a normal, full wipe (not internal storage) and flashed a ROM. Then flashed Chainfire's AROMA config tool just to make sure it disables or doesn't use any encryption. Flashed SU.
Once in ROM I see I'm still encrypted. Expected actually.
So I formated /data. Restored B32 stock and updated SU. No more encryption.
At work right now copying back sdcard contents.
On another note, I don't think I've ever seen a ROM boot up so fast and ready for use. Literally only seconds before it's ready to go. Even previously when Xposed and everything else was in place.
After another setting up period I'll try the dual boot thing again.
LG G3 D851, LiquidSmooth v4.1 ROM, MultiROM, Tapatalk 4.9.5
Total frustration trying to get things to work. Found out that the patched ROMs weren't completely flashed even though you don't see any errors (via TWRP, though the RESULT shows a 1 instead of 0). Using In-App flasher the output is more verbose and there is a failure of some sort. Checked the logs and it seemed there was a permission denied issue when a system image was being created.
Eventually decided to give up. Wiped ROM and flashed AOKP then discover my /data partition inexplicably changed to f2fs. What?!
Had to format it once again. Well, I was warned but didn't heed.
So what the hey, one more time for dual boot.
Restored B32 stock.
Located and copied the stock boot image originally saved by SuperSU. Uncompressed it.
Ran unSU script.
Flashed osm0sis' busybox, adb, and nano (I prefer they be in /system).
Ran Chainfire's AROMA config tool).
Flashed SU 2.82-SR5.
Boot into ROM, check that SU is okay, do a little configuring.
Install Dual Boot Patcher and patch a ROM (AOKP in this case).
Use In-App flasher. Eh? What's this? SUCCESS! Yes!
Booted into second ROM. Runs without issue.
Just when I was about to give up on it. All good now. Now I gotta just figure which of the favorite ROMs I want use.
Many thanks @Choose an username... for the assistance. You did warn about what may happen if I didn't flash SU. ?
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
Wiped ROM and flashed AOKP then discover my /data partition inexplicably changed to f2fs. What?!
Click to expand...
Click to collapse
Lol I knew your data was f2fs when you said that bit about the fastest booting ROM you've seen. It happened to me on stock but I went back to ext4 because Magisk and a bunch other things didn't play nice with it
Related
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
shawek said:
Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
Click to expand...
Click to collapse
I agree with you!!! This is a mess
even though I have flashed thousands of roms over the years, since I got rid of my Nexus 6, I havent had a phone that I could flash roms on, so, after dumping my Note 8 for this great phone, I was very hesitant to flash a custom rom, for all the reasons you have mentioned..
So, my question is, can you flash ANY of these custom roms by using the clear method that you mentioned in the OP?
If on one of the beta releases, is the procedure the same as I am showing below, or, do you always have to first return to stock OOS?
In my years of flashing dozens of phones, you never had to go back to "stock" if you wiped everything before flashing, but, it seems like on several of these roms, you are instructed to first return to "stock", THEN flash the new custom rom...
Plus, some roms say to wipe everything before you flash, and others say not to wipe system, or not to wipe data...
Unless I am nuts, I always thought that you wipe everything before converting to a totally new rom, but, maybe I am wrong here too..
"for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine."
These instructions seem pretty clear and concise, hopefully, they are correct, and we can just use this exact method and be done with it!
No mention of wiping in your directions...what do YOU wipe before flashing a new custom rom?
Hopefully, this gets cleared up once and for all, and we can ask the MODS to make a sticky of the ACTUAL CORRECT INSTRUCTIONS>>
thanks
wase4711 said:
"for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine."
These instructions seem pretty clear and concise, hopefully, they are correct, and we can just use this exact method and be done with it!
No mention of wiping in your directions...what do YOU wipe before flashing a new custom rom?
Hopefully, this gets cleared up once and for all, and we can ask the MODS to make a sticky of the ACTUAL CORRECT INSTRUCTIONS>>
thanks
Click to expand...
Click to collapse
-if on custom rom,probably it's good to first go to stock OOS and then to another custom rom.but this is also strange to me,as I don't understand what are benefits of this.i also read this,Google heh.i tried going from AOSCP to PixelEcpirince without flashing OOS in-between process,all was fine.
-I haven't been on Beta OOS yet,only stable.But that thing bout "before flashing custom rom,flash stable OOS even if your on Beta OOS" is also a big question to me.they are practically the same,both are latest OOS,one maybe more stable them other,but this also can be discussed hehe
-i don't wipe anything!! when my custom rom boots,I go into it's settings, without setting my Google account and other stuff, and I do "factory reset"( not in TWRP,in custom rom's settings!).Phone reboots,and all is fine,clean beginning,TWRP works,root works.About unwantedFolders in internal storage,I delete them manualy.
Only thing in my experience to wipe in TWRP is DATA,but this is also questionable,as I run into problems also doing data wipe I TWRP.
Now ROMs(maybe only for a/b devices) have scripts that wipe previous System during flashing new rom,so we don't have to do a Clean Flash anymore.
I'm also confused,more I read,less I understand ?
I like the idea of wiping via factory reset, once the rom boots, but, if it does NOT boot, then you wouldnt be able to do it that way..
I guess flashing an OOS based rom over an OOS based rom would always allow you to boot, if done right..
But, roms like RR, Carbon, AICP, and a couple others that have shown up here recently were never really OOS based roms, but AOSP based, at least I thought so..
the more I think about this, the more confusing it seems to get..
wase4711 said:
I like the idea of wiping via factory reset, once the rom boots, but, if it does NOT boot, then you wouldnt be able to do it that way..
I guess flashing an OOS based rom over an OOS based rom would always allow you to boot, if done right..
But, roms like RR, Carbon, AICP, and a couple others that have shown up here recently were never really OOS based roms, but AOSP based, at least I thought so..
the more I think about this, the more confusing it seems to get..
Click to expand...
Click to collapse
This is from the pixel 2 xl forum another a/b device
First time installing Pixel Dust ROM, or coming from another ROM:
As mentioned above, you are required to flash stock ROM before installing this custom ROM.
1. Flashing Stock ROM:
Follow these instructions: https://developers.google.com/android/images#taimen
2. Flashing PixelDust ROM:
Reboot to twrp
Wipe Dalvik cache and Data partitions
Flash ROM
Flash twrp zip
Reboot to System and enjoy the Pixel Dust Goodness!
Flashing Magisk:
You cannot flash Magisk during the initial install. You must boot into PixelDust ROM at least once!
Reboot to Recovery
Flash Magisk-v17.x.zip
Reboot to System
shawek said:
Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
Click to expand...
Click to collapse
You make it overcomplicated.
To flash both slots you only need to do a complete reboot to make sure the OS is not hosed.
You do that so if it is you can use the other slot. This is not necessary.
You flash in TWRP, change the slot and reboot into TWRP and flash the other slot.
It could be easier if TWRP allowed flashing on the inactive slot.
But, even if you are rooted and want to upgrade it is suggested to upgrade both slots.
I think it's just a minor pain. There are bigger problems.
tech_head said:
You make it overcomplicated.
To flash both slots you only need to do a complete reboot to make sure the OS is not hosed.
You do that so if it is you can use the other slot. This is not necessary.
You flash in TWRP, change the slot and reboot into TWRP and flash the other slot.
It could be easier if TWRP allowed flashing on the inactive slot.
But, even if you are rooted and want to upgrade it is suggested to upgrade both slots.
I think it's just a minor pain. There are bigger problems.
Click to expand...
Click to collapse
it's not a minor pain if most of time that I go to flash custom rom,I lost all my 60-80gigs of internal data, cuz of failed decryption,or failed rom flash,or failed TWRP flash.There were times when I did Factory reset in TWRP,flashed OOS,flashed TWRP.zip,did reboot to recovery,and I lost recovery.I was left with bootloader (fastboot) and had to fastbooting OOS few times(which led to full wipe of internal storage).OOS wasn't even flashed,or TWRP wanst even flashed.And I just followed instructions.
this are the things that I'm talking about.Even if I follow instructions, instructions are not detailed.
now I probably know how to do it right,,but still...I learned it hard way,and still learning
thanks for your opinion and answer:good:
shawek said:
it's not a minor pain if most of time that I go to flash custom rom,I lost all my 60-80gigs of internal data, cuz of failed decryption,or failed rom flash,or failed TWRP flash.There were times when I did Factory reset in TWRP,flashed OOS,flashed TWRP.zip,did reboot to recovery,and I lost recovery.I was left with bootloader (fastboot) and had to fastbooting OOS few times(which led to full wipe of internal storage).OOS wasn't even flashed,or TWRP wanst even flashed.And I just followed instructions.
this are the things that I'm talking about.Even if I follow instructions, instructions are not detailed.
now I probably know how to do it right,,but still...I learned it hard way,and still learning
thanks for your opinion and answer:good:
Click to expand...
Click to collapse
I understand now.
The instructions are not clear for most of this stuff and you can screw up.
If something fails to flash, there are very few reasons to ever completely wipe. Even a factory reset does not require a complete wipe of data.
I would suggest at all times keeping a boot image of the current OS you are using.
I would also suggest keeping a TWRP.img on your computer. You can always boot from a TWRP image even if it's not the one you want to install.
That will at least get decryption and the ability to flash.
I don't flash custom ROMs, because the stock one with root does what I need. Also the fingerprint sensor is not guaranteed under custom ROMs and I need that to work.
no verify opt on most after data wipe or that brands version of it, then reboot to twrp verify is still not there because twrp will say no os installed the avb changed things every phone is different depending on their security Samsung for one
Try this guide. Read the first paragraph if you have problems with decryption.
Boot twrp
Wipe dalvik and data
Flash rom+twrp
Reboot SYSTEM!
Boot back to recovery
Factory reset
Flash gapps+magisk
Reboot and done
No data loss or PC needed...
So here's some food for thought. I read somewhere that when you install a ROM zip via TWRP it actually Installs to the Inactive Slot. And when you reboot to TWRP after reflashing the Installer it Switches Slots and then you can Flash GAPPS etc. But what if someone were to flash the ROM twice ; once to each slot? Would be noice if We can use this to Multi-Boot Two ROMs at once....
Mannan Qamar said:
So here's some food for thought. I read somewhere that when you install a ROM zip via TWRP it actually Installs to the Inactive Slot. And when you reboot to TWRP after reflashing the Installer it Switches Slots and then you can Flash GAPPS etc. But what if someone were to flash the ROM twice ; once to each slot? Would be noice if We can use this to Multi-Boot Two ROMs at once....
Click to expand...
Click to collapse
I think that question was asked in one of the threads in here "can use this to Multi-Boot Two ROMs at once" and I don't think it's possible. I'm sorry I don't remember the thread it was in. You might try Google.
It's wise to do the oos in both slots which you can switch slots without rebooting fyi because when you flash a custom ROM no matter if you switch back to a it'll flash magisk and probably gapps in the inactive slot. If you try to return the custom ROM to slot a after it flashes it will say insufficient room for gapps and such. So to me it seems this makes it a clean slate so it can flash to inactive slot. Hope that clears up why they encourage the double oos flash
Everyone, I think you have almost helped me figure out how I screwed up my 6T. I made a post needing help but this thread I believe is the answer. I wanted to install lineage16 but opted for Resurrection Remix since that dev claimed the fingerprint reader worked. To make a long story short, I flashed the latest .15 OxyOS update first, switched partitions via TWRP and flashed it again, them flashed TWRP and rebooted to recovery. Flashed Remix then TWRP again and rebooted to Remix. Now I have no room for anything in storage although it's only 25% full and my file explorer cannot access any storage not can I update apps through play store or anything. I have the latest OxyOS on my OTG flash drive as well as TWRP and magisk, but every time I find a thread on hope to do an installation, it varies and I keep coming back to this storage issue. Can someone PLEASE link me out tell me where to find the correct process to now start from the beginning and get my phone back working on the OxyOS .15 stock rom? Thank you very much and I'm glad I found this thread because it finally makes sense as to how misinformation is causing many people to have issues.
SuperUnkn0wn0ne said:
Everyone, I think you have almost helped me figure out how I screwed up my 6T. I made a post needing help but this thread I believe is the answer. I wanted to install lineage16 but opted for Resurrection Remix since that dev claimed the fingerprint reader worked. To make a long story short, I flashed the latest .15 OxyOS update first, switched partitions via TWRP and flashed it again, them flashed TWRP and rebooted to recovery. Flashed Remix then TWRP again and rebooted to Remix. Now I have no room for anything in storage although it's only 25% full and my file explorer cannot access any storage not can I update apps through play store or anything. I have the latest OxyOS on my OTG flash drive as well as TWRP and magisk, but every time I find a thread on hope to do an installation, it varies and I keep coming back to this storage issue. Can someone PLEASE link me out tell me where to find the correct process to now start from the beginning and get my phone back working on the OxyOS .15 stock rom? Thank you very much and I'm glad I found this thread because it finally makes sense as to how misinformation is causing many people to have issues.
Click to expand...
Click to collapse
You may have solved this by now, but I found that using the MSM Download Tool has enabled me to return to stock OxygenOS even after getting stuck in a boot loop. I've not been able to successfully flash RR or LineageOS however, still getting stuck in said boot loop...
I like Lineage OS but the fact the second screen stays on even when locked drains battery even with a custom Kernal. I would love to be stock and rooted but since I DS the boot. I understand flashing stock will get rid of it(maybe I am wrong?). I just want a stock rom or a way to go to stock and stay rooted? is this possible or am I stuck with everyone else?
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
kaluna00 said:
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
Click to expand...
Click to collapse
Thank you, Is alpha Rom hard to install?
stevieshae said:
Thank you, Is alpha Rom hard to install?
Click to expand...
Click to collapse
No. Details should be in the OP
kaluna00 said:
No. Details should be in the OP
Click to expand...
Click to collapse
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
stevieshae said:
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
Click to expand...
Click to collapse
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
jackson019 said:
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
Click to expand...
Click to collapse
Thank you jackson for the fast response, have you tried the rom, and do you like it?
stevieshae said:
Thank you jackson for the fast response, have you tried the rom, and do you like it?
Click to expand...
Click to collapse
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
jackson019 said:
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
Click to expand...
Click to collapse
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
stevieshae said:
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
Click to expand...
Click to collapse
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
jackson019 said:
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
Click to expand...
Click to collapse
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
stevieshae said:
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
Click to expand...
Click to collapse
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
jackson019 said:
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
Click to expand...
Click to collapse
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Also... Should I install dirty santa kernal?
stevieshae said:
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Click to expand...
Click to collapse
First off, you should be rooted with TWRP 3.2.3-4 from here already installed. Then follow these steps:
Clean Install -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Install 1.0.7 -> Choose the proper kernel for your root method
If you rooted via dirtysanta, choose the mk2000 santa kernel
Reboot to recovery, no need to go to setup
Clean Install 1.3.0 -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Use the same kernel from above
Flash Magisk v18.1
Wipe Dalvik/Cache
Reboot to System
I am sick of this encryption thingy everytime I want to flash a rom on 6t, sometimes it works sometimes it's triggered even if I follow twrp tutorial.
Lately I flashed omnirom, but it encrypted slot B, I rebooted to slot A in recovery and Oos booted.
So it looks like slot B is still encrypted while A is running great and rooted with magisk.
Should I decrypt slot B or it's useless as long as I won't flash a new rom?
So did you managed to flash omnirom or not?
cultofluna said:
So did you managed to flash omnirom or not?
Click to expand...
Click to collapse
Nop
Tried a second time but it will trigger encryption again following twrp first post tutorial. It's weird because it worked in the past with other aosp roms. Perhaps Omnirom dev forgot to add A6010 as compatible 6t?
vegetaleb said:
Nop
Tried a second time but it will trigger encryption again following twrp first post tutorial. It's weird because it worked in the past with other aosp roms. Perhaps Omnirom dev forgot to add A6010 as compatible 6t?
Click to expand...
Click to collapse
Try to install without rebooting on twrp in between..
Flash rom
Flash twrp installer (DON'T reboot on twrp)
Wipe data
Flash gapps
Flash magisk
Reboot
cultofluna said:
Try to install without rebooting on twrp in between..
Flash rom
Flash twrp installer (DON'T reboot on twrp)
Wipe data
Flash gapps
Flash magisk
Reboot
Click to expand...
Click to collapse
Ok I will try.
And what is the way back? Last time I went back to oos from aosp it encrypted both slots, I had to use unbriking tool that wipes the whole phone
vegetaleb said:
Ok I will try.
And what is the way back? Last time I went back to oos from aosp it encrypted both slots, I had to use unbriking tool that wipes the whole phone
Click to expand...
Click to collapse
If both slots are encrypted you can maybe put the oos rom and a magisk zip on a otg storage to flash it via twrp
Let me know if it works also. I had same problem, the only way I was able to recover was to fastboot flash ops to phone.
adeptustech said:
Let me know if it works also. I had same problem, the only way I was able to recover was to fastboot flash ops to phone.
Click to expand...
Click to collapse
Do you have 6010 variant?
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
CptUnicorns said:
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
Click to expand...
Click to collapse
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Striatum_bdr said:
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Click to expand...
Click to collapse
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
CptUnicorns said:
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
Click to expand...
Click to collapse
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Striatum_bdr said:
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Click to expand...
Click to collapse
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
CptUnicorns said:
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
Click to expand...
Click to collapse
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
OhioYJ said:
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
Click to expand...
Click to collapse
That does clear up things for me, I've either mis-read or not read that when on slot A you are actually flashing slot B and Visa versa.
I'll be flashing both my slots to 10.3.1 just so they're fully updated. ( A is my main)
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
CptUnicorns said:
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
Click to expand...
Click to collapse
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Great stuff. Thought I understood from how you explained it. I'll check that guide as well and have it to hand just incase.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Something didnt want to play when I was flashing... Got to flashing gapps and magisk, gapps flash gave me a error 64 and i got magisk installed, booted, now I've got no twrp and when I use fastboot it just softbricks then restarts after about 5 minutes, I'm gonna try booting from 3.2.3-2 as that was fine and hope I can boot into recovery and just go lineage I think for something new
EDIT
So I used fastboot --set-active=a, managed to get back to twrp so now its flashed on both again. In the process of flashing lineage now, hopefully this wont chuck another error at me for gapps