Database Users

[Q] Possible Brick?

I'm selling my Nexus 7 and I think I got a little click happy while clearing it out.
I had reinstalled 4.3 and then for some reason I formatted the data. Got stuck in a boot loop.
When I try to install the image again I get the following:
Updating partition details...
E:error opening '/data/media'
E:error: no such file or directory
Any help would be appreciated!

"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!

That's why I prefixed with 'possible'...
Thanks - I followed this guide later in the evening and got it all up and going again.
http://goo.gl/BsiewY
0vermind said:
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
Click to expand...
Click to collapse

[HELP] Recovery Bricked and can't reflash

Hello,
I've decided to install the Beta version of Oxygenos 3.0. Since my phone came from the OnePlus support, I've unlocked the oem, installed TWRP and flashed the Oxygen zip.
However, a day later I've spotted important touchscreen issues (I can't use the touchscreen sometimes).
To see if it is a software problem, I've decided to go to the recovery to reflash a backup. When I try to go to recovery mode, nothing Happen! (Just the oneplus logo ).
So, i've decided to reinstall TWRP by flashing it with fastboot.
"fastboot flash recovery recovery.img" -> OK
"fastboot boot recovery.img"
downloading 'boot.img' ...
OKAY [0.702s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I've tried to install the stock recovery but I've the same error.
PLEEEASE HELP. I've waited a week to receive my phone because it had a problem but it's broke again :crying:
Note: I can go in Android normally (but with the touchscreen problem)

http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.

This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.

AndroidBeginNinja said:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
Click to expand...
Click to collapse
Thank you,
I've done this and I had a working recovery, (bootloop if I try to boot up normaly but it's not a problem I just have to flash a rom)
Trey22200 said:
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
Click to expand...
Click to collapse
I've tested your manipulation and it worked well too.
For those having the same problem OR want to install Oxygen OS the CLEAN WAY, read this post before: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
It is very important to read the faq before flashing and doing **** like me.

http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 flash this first before you flash oos3

I need help with twrp ASAP please

I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.

willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)

willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..

SomethingWentWrong said:
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)
Click to expand...
Click to collapse
Fastboot mode

farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
I'll give that a shot, thanks!

farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
Oh man you're a life saver! Worked perfectly! Thanks so much!

willineedhelp said:
Oh man you're a life saver! Worked perfectly! Thanks so much!
Click to expand...
Click to collapse
Glad to know I was able to help, it happens with me and this is how I fixed ?

Hello! Had the same problem and the procedure let me access recovery, yet everytime I reboot to system, the phone opens recovery instead.
I tried restoring a backup but rom is unstable and stuff keeps crashing. Any ideas?
EDIT: did a fastboot flash of .9 ROM and at got it back to work.

farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!

willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Nvm, I just had a junk TWRP version.

willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
What MIUI version you have tried to go back?

[GUIDE] [ROM] How to Flash BeastROM to Mi CC9e

Hey guys,
Although Mi CC9e (laurus) has been released for some days, there's few discussion on this device. The reason why I bought laurus is because I think it will share a community with Mi A3 (laurel_sprout), and it's easier to get laurus in China (with 6GB RAM). And indeed, laurus use exactly the same kernel with laurel_sprout. Most people think laurus is A only and laurel_sprout is A/B, which is almost, but not entirely correct. Devices launched with Android 9 are mandatory to use system-as-root.
In previous versions of Android, devices that didn't support A/B updates could mount the system image under the /system directory. In Android 9, the root of the system image is mounted as the root of the device.
Click to expand...
Click to collapse
In short, laurus MUST flash A/B image instead of A only, just like Mi 9 (cepheus) and Mi Mix 3 (perseus).
I assume that your'phone is unlocked and you've configured ADB and Fastboot.
So, let's start.
1. Flash TWRP
Reboot your laurus to Fastboot with Power + Volume Down.
There's a available TWRP from Chinese developer LR.Team
Download Link
The batch script is in Chinese, but I'm sure you know what to do if you're familar with Fastboot.
Code:
fastboot flash recovery recovery-TWRP-3.3.1-0914-XIAOMI_CC9E-CN-wzsx150.img
2. Flash BeastROM 1.6
Although BeastROM 2.0 has released but I can't get it work. It just display Mi logo and then jump to Fastboot. Most other GSIs won't work as well, it dosen't boot at all. So the only choose is BeastROM 1.6 for laurel_sprout @mdeejay.
BeastROM 1.6
unzip it, and what we need to do is flash system.img ONLY.
Code:
fastboot flash system system.img
And then reboot to TWRP, wipe data partition.
Edited:
You can find your vbmeta in fastboot ROM of laurus.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This command is NOT NEEDED if you can disable dm-verity via magisk. You can't boot without disabling dm-verity (stuck on Logo). I don't know how it works. Need some help from devs.
3. Flash Magisk
You HAVE TO flash magisk, or it will stuck on boot animation.
You can do it by "Install Root" in Advanced of TWRP.
Or do it manually by flash Magisk.
4. Flash GApps (Optional)
OpenGApps
Just Flash it in TWRP, nothing more to say. Maybe you need to wipe data again.
I think everything is perfect for now, execpt it's Android 9 instead of 10. At least you can get most of features in Mi A3 and get rid of stupid MIUI
Some stupid idea: for people who wanna get MIUI in laurel_sprout, you can flash system.img in fastboot of laurus. I don't think it will work but it worth trying.
I've tried flashing laurel_sprout image into laurus, it can boot, but it won't work. Screen blinks and it get stuck on welcome page, touching works though.
Fastboot of laurus
Fastboot of laruel_sprout
For people who prefer stock A3 Android One ROM, Here is the method I've tested
con_sau_may_tinh said:
mi cc9e can use stock rom of mi a3 without root, this mean bank app will work perfect
1- flash full rom with miflash (any lower version will not boot) http://bigota.d.miui.com/V10.2.13.0...FMCNXM_20190830.0000.00_9.0_cn_fc9f51f46d.tgz
2- download rom of mi a3, extract file system.img only
http://bigota.d.miui.com/V10.3.4.0....0.PFQMIXM_20190815.0000.00_9.0_00838b4c0e.tgz
3- go to fastboot and flash (vbmeta of micc9e)
fastboot flash system system.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
Click to expand...
Click to collapse

i flash only system but, my phone stuck on fastboot mode
please help

vanly6.2 said:
i flash only system but, my phone stuck on fastboot mode
please help
Click to expand...
Click to collapse
Are your device Mi CC9e instead of Mi A3? Make sure you're flashing BeastROM 1.6 instead of 2.0 or you'll get stuck on fastboot. And maybe you need to format your data partition in TWRP.

Crosstyan said:
Are your device Mi CC9e instead of Mi A3? Make sure you're flashing BeastROM 1.6 instead of 2.0 or you'll get stuck on fastboot. And maybe you need to format your data partition in TWRP.
Click to expand...
Click to collapse
i has flash ok, but i can use finger, you have problem as me ?

vanly6.2 said:
i has flash ok, but i can use finger, you have problem as me ?
Click to expand...
Click to collapse
Fingerprint sensor works for me.

Can i back to miui if something wrong,or on bootloop

oska3 said:
Can i back to miui if something wrong,or on bootloop
Click to expand...
Click to collapse
Of course you can, just flash the fastboot ROM of laurus.

Stug on fastboot too
How i can go in twrp

oska3 said:
Stug on fastboot too
How i can go in twrp
Click to expand...
Click to collapse
Power and Volume up can make it boot into Recovery.
But if you flashed dtbo and vbmeta of BeastROM 1.6, or maybe you wipe your system partition. , it will be stuck at fastboot and cannot boot (or enter recovery)
One way to fix this is disable dm-verity, just use magisk, you can do it by "Install Root" in Advanced of TWRP. (Flashing magisk manully does the same job)
(However, you can't enter TWRP, so this won't work. )
Another way to disable dm-verity is flash vbmeta with --disable-verity --disable-verification, but I'm not sure whether it works.
Your best chioce is flash the fastboot ROM of laurus and do it again. Remerber to flash magisk in TWRP after flashing system.img, I made a mistake that magisk is not included in BeastROM and you must flash it to disable dm-verity or it will never boot.

im fix it and its ok now,how,i dont know
finaly miui gone,yyyuuhuu

If u update magisk and stug on bootloop,u can start on twrp and flash magisk manualy and reboot in beastrom again
---------- Post added at 09:32 PM ---------- Previous post was at 08:37 PM ----------
Just dont use or update to magisk 20,stug on bootloop

Crosstyan said:
Hey guys,
Although Mi CC9e (laurus) has been released for some days, there's few discussion on this device. The reason why I bought laurus is because I think it will share a community with Mi A3 (laurel_sprout), and it's easier to get laurus in China (with 6GB RAM). And indeed, laurus use exactly the same kernel with laurel_sprout. Most people think laurus is A only and laurel_sprout is A/B, which is almost, but not entirely correct. Devices launched with Android 9 are mandatory to use system-as-root.
In short, laurus MUST flash A/B image instead of A only, just like Mi 9 (cepheus) and Mi Mix 3 (perseus).
I assume that your'phone is unlocked and you've configured ADB and Fastboot.
So, let's start.
1. Flash TWRP
Reboot your laurus to Fastboot with Power + Volume Down.
There's a available TWRP from Chinese developer LR.Team
Download Link
The batch script is in Chinese, but I'm sure you know what to do if you're familar with Fastboot.
Code:
fastboot flash recovery recovery-TWRP-3.3.1-0914-XIAOMI_CC9E-CN-wzsx150.img
2. Flash BeastROM 1.6
Although BeastROM 2.0 has released but I can't get it work. It just display Mi logo and then jump to Fastboot. Most other GSIs won't work as well, it dosen't boot at all. So the only choose is BeastROM 1.6 for laurel_sprout @mdeejay.
BeastROM 1.6
unzip it, and what we need to do is flash system.img ONLY.
Code:
fastboot flash system system.img
And then reboot to TWRP, wipe data partition.
Edited:
You can find your vbmeta in fastboot ROM of laurus.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This command is NOT NEEDED if you can disable dm-verity via magisk. You can't boot without disabling dm-verity (stuck on Logo). I don't know how it works. Need some help from devs.
3. Flash Magisk
You HAVE TO flash magisk, or it will stuck on boot animation.
You can do it by "Install Root" in Advanced of TWRP.
Or do it manually by flash Magisk.
4. Flash GApps (Optional)
OpenGApps
Just Flash it in TWRP, nothing more to say. Maybe you need to wipe data again.
I think everything is perfect for now, execpt it's Android 9 instead of 10. At least you can get most of features in Mi A3 and get rid of stupid MIUI
Some stupid idea: for people who wanna get MIUI in laurel_sprout, you can flash system.img in fastboot of laurus. I don't think it will work but it worth trying.
I've tried flashing laurel_sprout image into laurus, it can boot, but it won't work. Screen blinks and it get stuck on welcome page, touching works though.
Fastboot of laurus
Fastboot of laruel_sprout
Click to expand...
Click to collapse
First of all, tks for getting the first not official rom for the cc9e! Really appreciated.
Can you please confirm if this rom has Spanish Language included? Tks!

im confirm,there is espanol language and almost all popular,and work like a charm

oska3 said:
im confirm,there is espanol language and almost all popular,and work like a charm
Click to expand...
Click to collapse
Tks buddy! I will try it

Thankyou heaps for for this post.
I will be back in 168hrs (mi unlock) to attempt （⌒▽⌒）.

help
1)i flash fastboot stocck laurus rom
2)then flash twrp (always use files that you provide in this thread)
3)then flash system.img
4)then reboot to twrp >format data>yes
5)then install magisk 19.4 and pico gapps
6)then repeat format data and reboot
but always phone stuck on "G" logo booting
also try to flash vbmeta from stock after 4)
also try without gapps
also try vbmeta from beast 1.6
nothing
please help me
what i do wrong
sorry for my bad english

Some of us Mi A3 users want to use Miui 11 from CC9e, how possible is that. Could you give a tutorial?
Android one is snappy on mi a3, with 6g ram on CC9e it will be really smooth.

Xiaomi Mi A3 - Неофициальные прошивки miui 10 port,4pda

aleksbrain said:
1)i flash fastboot stocck laurus rom
2)then flash twrp (always use files that you provide in this thread)
3)then flash system.img
4)then reboot to twrp >format data>yes
5)then install magisk 19.4 and pico gapps
6)then repeat format data and reboot
but always phone stuck on "G" logo booting
also try to flash vbmeta from stock after 4)
also try without gapps
also try vbmeta from beast 1.6
nothing
please help me
what i do wrong
sorry for my bad english
Click to expand...
Click to collapse
Try to use the root in Advanced tab of TWRP.

mi cc9e can use stock rom of mi a3 without root, this mean bank app will work perfect
1- flash full rom with miflash (any lower version will not boot) http://bigota.d.miui.com/V10.2.13.0...FMCNXM_20190830.0000.00_9.0_cn_fc9f51f46d.tgz
2- download rom of mi a3, extract file system.img only
http://bigota.d.miui.com/V10.3.4.0....0.PFQMIXM_20190815.0000.00_9.0_00838b4c0e.tgz
3- go to fastboot and flash (vbmeta of micc9e)
fastboot flash system system.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot

Moto G7 and... Ubuntu Touch GSI

Maybe it isn't a right place to ask for it, however, I saw that erfanoabdi made an Ubuntu Touch GSI and also a halium-boot port for river. Maybe it's a silly question, but it is possible to just simply install this GSI (or maybe semi-GSI, because it requires halium port) on river and boot it? There's a simple guide for installing this GSI or any device which has a halium port, here it is:
0) Install treble compatible android 9 rom
1) FORMAT data in twrp
2) Flash halium-boot.img of your device
3) Flash GSI zip (I think I can't give a link here, it is allowed?)
So can it theoretically work? I tried it, but unfortunately I saw just blank screen after booting.

don't format data before LOS16

HueyT said:
don't format data before LOS16
Click to expand...
Click to collapse
So, I should:
1. Flash LOS 16 without formatting data (I'm on Android 10)
2. Format data
3. Flash halium boot
4. Flash UBports GSI
I'll try that but I don't think it's a data problem, because I've already tried it and the zip was successfully installed - files it should copy were copied on data partition, I've checked this. But I'll try once more, without formatting data. Should I boot lineage after flashing?

Yeah, so I followed this and it worked. Thanks!
If anyone had the same problem, I'll write down all what I did:
0. Temporarily booted TWRP and installed it via zip (twrp-3.3.1-14-river)
1. Installed LOS 16 (lineage-16.0-20200127-UNOFFICIAL-river) without formatting data.
2. Booted LOS but it rebooted as the data wasn't formatted and i kept it booting until it booted into LOS Recovery to format data, so I just rebooted phone without formatting data and installed TWRP as in step 0.
3. Flashed halium-boot as boot image in TWRP and installed UBports installed v5 zip, also in TWRP of course.
4. Rebooted phone.
5. Now Ubuntu Touch booted succesfully. Unfortunately, it reboots after about 1 minute. So it's not stable enough at this time. Or maybe I'm doing something wrong, I'll try also another vendor image.
EDIT: I've just tried another vendor.img from newer LOS16 build. Worked fine, but sim doesn't work

Nick_Nicker said:
Maybe it isn't a right place to ask for it, however, I saw that erfanoabdi made an Ubuntu Touch GSI and also a halium-boot port for river. Maybe it's a silly question, but it is possible to just simply install this GSI (or maybe semi-GSI, because it requires halium port) on river and boot it? There's a simple guide for installing this GSI or any device which has a halium port, here it is:
0) Install treble compatible android 9 rom
1) FORMAT data in twrp
2) Flash halium-boot.img of your device
3) Flash GSI zip (I think I can't give a link here, it is allowed?)
So can it theoretically work? I tried it, but unfortunately I saw just blank screen after booting.
Click to expand...
Click to collapse
Did it occur to you to maybe link to what you're talking about? Where is this halium-boot port for River you're talking about? I see nothing in the main GSI thread about anything but the G7 Power. No results on google for halium-boot river or halium river point to anything but this thread, so I have no idea what you could possibly mean.

Check on https://build.lolinet.com/file/halium/
Here you can find GSI and halium-boot images from Erfan. He also posted it on XDA, here you can find all information about it: https://forum.xda-developers.com/pr...development/gsi-ubuntu-touch-ubports-t4110581
So, halium-boot.img is found on build.lolinet.com
But you can also build Halium 9 image if your device's kernel source is available, here's some info https://github.com/ubports/porting-notes/wiki/Generic-system-image-(GSI)#how-to-install-gsi
Also it's very important to have Android 9 ROM installed before. However, stock Android 9 didn't work for me, I prefer LineageOS. So, just install Lineage and then the GSI and halium boot image. For Moto G7 also flash 'river-firmwares.zip' found on lolinet. It'll fix that weird vibration noise bug. For now, there are some visual glitches visible (also only on river), but it'll be fixed. Anbox is working if you have /data partition formatted in ext4 (not f2fs), so if you follow instructions, you can also run some Android apps. Unfortunately, for me internet connection inside Anbox doesn't work.

Thanks sorry I was just starting to feel a bit insane, that stuff is not indexed on google at all by the looks of it. Thank you.

So here is the process that worked for me.
I started with the stock rom.
1. Followed the full Lineage OS install instructions, including the partitions zip etc.
2. Installed Lineage OS on Slot B per the above instructions
3. Wiped data
4. Flash halium-boot.img
5. Flash GSI zip
Everything works perfectly including cellular functionality.

Followed the steps above. Is it possible to revert?
I followed the steps above, but I am have serious issues with the screen jitter. I have been looking all over the place to see if there is a way to revert back to android so that I can use my phone without the screen jitter. Does any one have any instructions on how to do this? I did turn on ADB mode on Ubuntu Touch but my computer does not see an adb device. Thank for any help.

Took me a long time to figure out too.
Main thing is, if you hold down Power and Volume Down, eventually it will reboot to the boot menu. Don't select anything, just plug it in, and you'll have fastboot.
To go back to stock:
1. Hold down Power and Volume till the boot menu shows up.
2. Plug the phone into your PC
3. Get the newest firmware for your phone model. I bought mine at Best Buy, so it was RETUS aka retail US. https://mirrors.lolinet.com/firmware/moto/river/official/
4. Extract the archive, and enter that folder in your terminal
5. Run the following commands from that folder. I saved these commands in a shell script and ran it but I think you can just paste it
THIS WILL WIPE ANY DATA ON YOUR PHONE AND PUT IT BACK TO FULL FACTORY FIRMWARE WITH LOCKED BOOT LOADER. At least when I ran it, it got my phone 100% no more complaints when it boots about untrusted code. After this you should have a fresh phone you can unlock and try flashing again. THis also restored my OTA ability and I was able to get the Android 10 update without any issues.
fastboot oem lock begin
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot oem lock
Click to expand...
Click to collapse