Database Info

Unable to flash anything other than oos

I know, there've been plenty of "please help, I can't flash xx" threads. If there's a duplicate out there, please point me towards it.
I've been trying to get havoc or omni on my phone recently for fun but have had no luck. I've tried multiple different ways, maybe someone can tell me what I'm doing wrong or if there is actually something wrong with my device.
Method 1:
-Use the Oneplus Recovery tool to get a fresh start
-allow OOS to update itself to 9.0.3
-unlock bootloader
-boot twrp-3.2.3-x_blu_spark_v9.91_op6
-flash havoc (for example), flash twrp right after
-reboot to recovery (using button in twrp)
->this results in the phone restarting, shows bootloader unlocked screen, and then goes to black screen/white LED
Method 2:
-bootloader unlocked
-extract 9.0.3 full rom, use flash-all.bat
-fastboot set_active other
-flash-all.bat again (to get the other slot)
-boot twrp-3.2.3-x_blu_spark_v9.91_op6
-flash havoc (for example), flash twrp right after
-reboot to recovery (using button in twrp)
->this results in the phone restarting, shows bootloader unlocked screen, and then goes to black screen/white LED
After this black screen/white led issue, I can get into fastboot but I can't boot the twrp image.
I'm at wits end... I really have no clue what to do. Any ideas? I'm open to try any suggestions.
I should note, when I get 9.0.3 on there, either from method 1 or 2 it's possible to boot and use it.

Try these steps:
(Make sure You have unlocked BL)
Fastboot boot twrp_blue_spark.img
Now go to wipe and choose format data, type yes.
Copy this: OxygenOS 9.0.3 OTA.zip
To Your internal storage.
Now flash it.
Now go to reboot in TWRP and choose reboot bootloader.
Now fastboot boot twrp.img again.
Flash OxygenOS OTA zip again.
Now go to reboot in TWRP, choose reboot bootloader.
Fastboot boot twrp.img again.
Copy latest Havoc OS 2.1 to Your internal storage.
Flash it.
Reboot without flashing anything else.
Should work now:fingers-crossed:

Like 99% you didn't read the "how to" oos needs to be flashed on both slot a and B from twrp rather than fastboot

whizeguy said:
Like 99% you didn't read the "how to" oos needs to be flashed on both slot a and B from twrp rather than fastboot
Click to expand...
Click to collapse
I've tried flashing it on both slots a ton of times from twrp. Never got it to work.

Gibsonflyingv said:
I've tried flashing it on both slots a ton of times from twrp. Never got it to work.
Click to expand...
Click to collapse
Boot to twrp
Flash OOS 9.0.3 (if it's recommended to use that)
Flash twrp
Reboot to twrp
Flash OOS again
Flash twrp
Reboot to twrp
Wipe data, cache / dalvik
Flash custom rom
Flash twrp
Reboot to twrp
Flash gapps
Flash magisk
Done.
I've read this 4 times, should be right (high fever now so I just wanted to make sure)

Stuck in Bootloop when installing Magisk

Helloguys and gals,
I just got a Pixel 3 and wanted to root it. I followed this guide: https://www.youtube.com/watch?v=BgV1xxkcBk8
I installed the latest TWRP recovery (didn't keep it read only, maybe this was a mistake?). After that I installed Magisk which was followed by a bootloop.
To fix the bootloop I used TWRPs fix bootloop fix which worked. But that makes Magisk undone.
So my Questions is how to install Magisk? Do I need to flash the stock image on both slots and start again? Is the guide outdated? If so, which guide should I follow?
Edit: My phone is still on the update from November 2018.

On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot

bafforosso said:
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
Click to expand...
Click to collapse
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance

I run twrp as the devices recovery and have magisk. I would follow the twrp and magisk guides for this device. First boot twrp then use the installer, second reboot, third get to recovery and flash magisk. The boot partition needs to be rebooted before root. It is an initialization thing. Get twrp, reboot, magisk.

Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?

levibuko said:
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
Click to expand...
Click to collapse
I tinker a lot with my phone so I usually want to have both slots clean flashed when I start back from scratch, not sure that is really necessary, but here are the steps I use for flashing both slots :
Code:
fastboot getvar current-slot
./flash-all.sh
fastboot --set-active=x (x being a or b, the other slot than the one you get with the fastboot getvar command)
./flash-all.sh

Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
tenthousandfeet said:
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
Click to expand...
Click to collapse
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.

Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.

wangdaning said:
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
Click to expand...
Click to collapse
Tried that. No success.

Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.

wangdaning said:
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
Click to expand...
Click to collapse
I had a similar thought, but no dice. Tried installing Magisk 19.2, which boot looped just like the latest 19.3.
I even went back to 16.7, and though that one didn't boot loop it also didn't show up in the system. Magisk Manager didn't recognize it, anyway.
Though I'm loathe to do a full wipe/reset and then reconfigure all my junk, I may be headed in that direction as I'm running out of other ideas. Perhaps I'll save a backup just before that I can return to if the reset is fruitless.
---------- Post added at 07:53 AM ---------- Previous post was at 07:36 AM ----------
Magisk 18.0 does the same as 16.7 - no bootloop, but no root.
Interestingly, I noticed that the 18.0 and 16.7 zip installers say something about the partition being boot_a, whereas the bootlooping 19.2 and 19.3 zip installers say it's boot_b.

Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.

sliding_billy said:
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
Click to expand...
Click to collapse
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.

tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.

sliding_billy said:
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
Click to expand...
Click to collapse
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.

tenthousandfeet said:
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
Click to expand...
Click to collapse
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.

tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
Please update when/if you find a solution. We are both in the same boat.
I'll let you know if I get anything working.

sliding_billy said:
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
Click to expand...
Click to collapse
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.

tenthousandfeet said:
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
Click to expand...
Click to collapse
It still looks like your boot slot ended up the one you had tried already (b), since you changes to a and ran flash-all, changed back to b and ran flash-all and rebooted. As for the old platform tools, that could definnitly have an impact on running the fastboot of the patched boot. Other than that, I think a flash-all with the -w is the only approach left.

I'm also in the same boat. I've tried all the various install methods, and done the double "flash-all" on both slots, and no matter what, it ends in a bootloop.
Haven't tried the -w yet so I'll be interested if anyone gives that a go. Until then I'm dying with no root

I cant get TWRP to "stick" on my new pixel - following lineage directions

Got my pixel from swappa the other day. So far I:
1. Unlocked the bootloader
2. temporarily booted into TWRP 3.3.0-0 (3.3.1-0 wouldnt let me format for some reason)
3. Installed the most current microG lineage build. (and then also flashed magisk 19.3 immediately after)
It boots into lineage, but when I boot into recovery, it gives me the lineage recovery. Since when does lineage wipe out twrp?
I tried sideloading over adb and also right through the temporary twrp, but it doesnt make a difference. Also - in lineage, I see no sign of magisk - which is normally there after installing a rom and then magisk.
I also tried the twrp-pixel installer.zip, which also did NOTHING.
Am I missing something? This is my first phone with the weird dual partitions - is that why its so weird? Ive never had this problem before.
EDIT: Also when trying to flash twrp via fastboot it gives me
"(bootloader) Flashing active slot "_a"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.016s"

Hi mate, here's a link regarding the lineage recovery thing. It may explain some of what you have occurring.
https://lineageos.org/Changelog-19/
I had twrp on my pixel a while back and it was sticking so not sure what that's all about. If you have booted twrp.img, flashed ROM, flashed twrp zip and rebooted it should be on both slots. You may need to activate root in Dev options to get root up and running, been a while since used it so that might not be accurate as currently on Q.

after flashing a rom you need to flash the twrp-pixel installer.zip right after. Then reboot into recovery (dont need to fastboot since the zip installs twrp to the boot.img ramdisk) to switch slots (switches automatically). Back in recovery you can install magisk.

Devices with A/B partitions do not have a recovery partition. What we think of as recovery is actually part of the boot.img file. When you update the OS, you update the boot.img. The TWRP installer .zip finds and unpacks the boot.img, then modifies it to make the device load TWRP instead of stock recovery. By default, the TWRP installer installs to both A & B partitions. If you screw something up (like flashing the wrong version of TWRP, for example) and put yourself into a bootloop, you can often recover by simply flashing the original boot.img file with fastboot flash boot boot.img .
Here's an article which was written by XDA to help explain the differences in how A/B phones work, and the ramifications for us flashers:
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

Lineage OS 16/17/GSI Install Guide for LG G7 ULM

UPDATE: I kept finding bugs in josh1x's rom, so i installed the LOS17 GSI instead. Guide for that outline in reply #11
Figured this out and thought i'd write a simple tutorial that covers stock (i was at 20e) to lineage. You'll need the LG USB Drivers and adb/fastboot. There are a couple other things to download through out the tutorial and the unlock tutorial in step 1.
LG USB Drivers 4.2.0
ADB/Fastboot
LGUP with partition DL
Note: I was able to reach download mode and fastboot at any point in this process and even when it went wrong (kernel crashes, boot loops etc) while figuring out this tutorial. I found that i could just hold vol down or up in a bootloop with the usb connected to get to the mode i wanted.
Typical combos:
-Download mode: power off phone with usb disconnected. hold vol up and plug in cable
--NOTE: after wiping laf_a and boot_b, you must switch to slot b to access download mode (run command: fastboot -ab)
-fastboot: power off phone with usb disconnected, hold vol down and plug in cable. or adb reboot bootloader
--NOTE: after wiping laf_a and boot_b, you can only access fastboot from slot a by holding vol up on boot (for 20e/21d, on 11g vol down still works).
-Recovery: power off. hold power and vol down, when you see the white LG G7 logo temporarily release just the power button. Continue to hold power and vol down till you get to the option menu. Select Yes three times.
Guide:
1. Follow the universal unlock method here.
1.5. You need to zero out laf_a and boot_b before flashing 21d/20e to maintain fastboot access. Use adb to run the following commands
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
1.75. Enable usb debugging (should already be done). Open LGUP and connect to your phone. dont close it. If you open it after booting to DL mode it wont recognize it
2. 21d ULM firmware (here) must be flashed to use the latest twrp (20e works as well). The 11g twrp cannot install lineageos. I would imagine the EU firmware could be flashed as well, but I used ULM.
Code:
Boot into fastboot
fastboot -ab
Boot into download mode
Use the lg up linked in this post to flash 20e/21d without laf_a and boot_b with partition dl mode
3. Format userdata to decrpyt your file system so TWRP can access it. Then flash TWRP; boot_twrp-june.img can be found here. It's from Josh1x's post here. Note: this TWRP is non persistant.
Code:
Boot to bootloader
fastboot format userdata
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Select restart in fastboot
Boot to recovery
4. Obtain the latest lineage build here. This is from Josh1x's post here. I attempted to flash gapps at this point and it failed, see the next steps.
Code:
Wipe everything
Transfer lineageos to your phone and install it
Restart normally
5. Gapps
Code:
Reboot to bootloader
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Reboot to recovery
Transfer opengapps 9.0 to your phone and install.
Reboot to bootloader
6. We need to flash the stock lineage boot image (here) again now that we are done. The file was obtained with this method
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Restart normally
if you have magisk, it would be magisk_patched_boot.img (here). this one was made from the above image with magisk on my phone.
Code:
fastboot flash boot_a magisk_patched_boot.img
fastboot flash boot_b magisk_patched_boot.img
Restart normally
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
I am so glad to be off of stock, enjoy guys and girls!
Bugs (from my ULM phone)
-flash doesnt work in the camera. also probably why gcam crashes (gcam works on an EM phone somehow)
-brightness slider is calibrated incorrectly compared to stock. way too bright when set to 0%
NOTE: using ULM vendor fixed the flash and brightness, but gcam still doesnt work. This would make it the most functional rom for this phone at this point (vibrate does work).

Being that since day1 of g710pm/ulm could be boot unlocked, all ypu had to do is flash the eu firmware and go to lineage frlm there due to twrp incompatibility.
I have not tested it, but does being on lineage based off EU blobs, do you still get full LTE and/or volte.
If sprint users have switched to eu/lineage do you have full lte/ril compatibility.

Ah crap I didn't know that. I tried unlocking through LG when I got it a couple months ago and that didn't work of course. At that time the phone was working well (not going on a background apps killing spree), so I didn't bother. I couldn't find anything on here at the time for unlocking, but I obviously missed that.
LTE and wifi are working fine. Maybe that has something to do with me never flashing the EU rom to install lineage? Anyways, I couldn't find a volte toggle, but I'd assume it is working. I'm on Verizon and I believe they are killing their cdma network, so I'll find out.
Would this work on sprint phones? There is a warning at the end of the unlocking guide about sprint phones loosing fastboot when upgrading to ulm pie.

does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too

Emanel000000 said:
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Click to expand...
Click to collapse
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.

Have you tried the other twrps?

sirbow2 said:
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Click to expand...
Click to collapse
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?

Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk)
Click to expand...
Click to collapse
oh yea. i see, yes, they might as they are from the lineage rom.
Emanel000000 said:
... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.

sirbow2 said:
oh yea. i see, yes, they might as they are from the lineage rom.
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
Click to expand...
Click to collapse
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide

Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
Emanel000000 said:
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Click to expand...
Click to collapse
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.

Edit: Update 2: dont use the vendor in this post. I patched the ULM vendor, but vibrate and gcam are still an issue with a GSI. links here: https://forum.xda-developers.com/showpost.php?p=81563763&postcount=41 Also, using the ulm vendor on Josh1x's rom fixed everything but gcam.
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.

sirbow2 said:
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Click to expand...
Click to collapse
i just had 20c for em it doesnt matter the version

sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Thanks. You're process got my audio working on GSI. Not sure what incorrect image I was installing or what the issue was.
Just need to disable the LED notification and get vibration working.

EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.

loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
thats what i was kind of thinking the issue was. thats over my head though.

sirbow2 said:
thats what i was kind of thinking the issue was. thats over my head though.
Click to expand...
Click to collapse
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet

loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
loonycgb2 said:
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
Click to expand...
Click to collapse
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?

sirbow2 said:
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
Click to expand...
Click to collapse
Once you got twrp running with stock then do the normal thing of format userdat to decrypt it then flash the no dmverity zip mentioned in the thread or magisk then backup vendor via twrp or dd...
That will give you a usable vendor for lineage and such.
All josh1x or whoever did to the EM vendor was modify fstab to remove the force encrypt so that way decrypted roms would work.

sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Nevermind

I tried using the vendor from ULM 20e and it doesnt work, i even tried flashing dm verity right after. How would one modify the vendor partition anyways?

Question Installing GSI on Moto G Stylus 5G (2021)

In a moment of weakness, I finally allowed my G Stylus to update to Android 12, and my stability has been a nightmare since then. I have been reading through many guides here and elsewhere to getting a GSI installed.
So far, I have unlocked the bootloader and followed the instructions for installing TWRP using adb/fastboot for my device. When try to flash a GSI, the partitions in TWRP don't look like anything I've seen in guides. The options it shows me are:
-Boot
-Dtbo
-Persist
-Super (system system_ext product vendor)
-Install Recovery Ramdisk
I tried installing on Super, as I found a thread mentioning it should contain both vendor and system. However, when I flash the img for a gsi to it, it will only boot to bootoader. I can get it into TWRP recovery but the screen is entirely unresponsive, even attempting to power off prompt's a restart. I was able to use Moto's Rescue program to get it back in working order, but each time this happens I have to start over at square one.
I tried with a GSI for crDroid on my first attempt, and then LineageOS on a follow-up attempt, both I had the same issue.
I'm new to Android modding, so I could really use some guidance through getting this set up. I've extensively referenced guides on here and elsewhere, but I've struggled with parsing and figuring out what I need to do in this case. Currently my device has TWRP installed but I'll be doing nothing else until I know what the best way forward is. I'd be happy to provide additional info.
Edit: Just found the dedicated 5G section. Sorry about this.

I am not sure why people use TWRP and a GSI/crDroid /w LineageOS rom.
All you need to do is install the magisk module L Speed
Remember this phone has 2 boot partitions....1 is secured (even if you have the bootloader unlocked and your rooted) So if you trip the SafetyNet your going to have bootloading issues and boot loops

Not sure what the previous comment was about, what does safetynet have to do with anything? It fails the second you unlock the bootloader.
First, you'll want to make sure to have installed at least one OTA update so both your slots are occupied. You could also install copy-partitions from a custom recovery. Otherwise your phone might brick if it ever switches to slot b.
Download and extract the official firmware for your device that matches what is installed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
And reflash your vbmeta partition(s) from fastboot to disable verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_system.img
Then you need to reboot into fastbootd (you can also get into it from a custom recovery)
Code:
fastboot reboot fastboot
From there you can erase your system, install the GSI, wipe data, and reboot
Code:
fastboot erase system
fastboot flash system GSI_system.img
fastboot -w
fastboot reboot