[ROM][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1

[asineth]

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.

Downloads: https://asineth.me/post/android-rav/

Flashing:
1. Extract the zip and open a shell with ADB and fastboot.
2. Reboot your device into fastbootd mode.

fastboot reboot fastboot

3. Flash boot, system, product, and vbmeta.

fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img

4. Wipe userdata.

fastboot -w

If you are on the Moto G8/G Fast and your display cutout is misbehaving, enable your overlay like so:

adb shell cmd overlay enable org.omnirom.overlay.moto.rav

I've tested with Magisk v20.4 & OpenGapps Pico, to flash, temporarily boot into TWRP with fastboot.

Working:

• Display
• Touchscreen
• Wi-Fi
• Bluetooth (including audio)
• Headphones via 3.5mm
• Internal Speaker
• Moto Actions
• Calls/SMS/LTE/VoLTE on Verizon

Issues:

• Vibration motor is broken
• Stock wallpaper animation (fixed by changing it)
• Rav (G8/G Fast) users must enable their overlay manually

Source:
LineageOS
Device tree
Vendor tree
Kernel tree

Telegram:
https://t.me/MotoG8Official

Credits:

• @Vachounet - helped a lot, original device/vendor tree, TWRP build
• @kjjjnob - some LineageOS changes to @Vachounet's tree

This is my first ROM release, thanks for your guy's help!

XDA:DevDB Information
[ROM][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1, ROM for the Moto G8

Contributors
asineth
Source Code: https://git.asineth.gq

ROM OS Version: Android 10
ROM Kernel: Linux 4.x

Version Information
Status: Stable
Current Stable Version: 17.1-20200915
Stable Release Date: 2020-09-14

Created 2020-09-15
Last Updated 2020-09-15

 

[atiolon]

Nice work

Instalation was easy, everuthing is working as described or not working as described.

What would you think about setting your work for Micro G support?

 

[asineth]

Instalation was easy, everuthing is working as described or not working as described.

What would you think about setting your work for Micro G support?

Might provide microG builds if there's interest.

 

[atiolon]

Might provide microG builds if there's interest.

I vote for it.

 

[FoxySheila]

****ed up, send help.

Okay so, I followed the instructions but I ****ed it all up. adb shell wouldn't do fastboot reboot fastboot from the bootloader, nor would the mounting command work. It still doesn't. I flashed those files thinking maybe I was already mounted and it defaulted me back to stock os. Then I tried getting back into twrp, but it wanted a password and I had a pattern, so I set a pin code, and that didn't work either. So I reset data user data and another one that was mentioned in another xda thread and now I can mount twrp and get in, but the lineage zip won't flash, it says invalid zip file format. So, I have no idea what Ive done to this phone or how to get lineage on it, or even at this point how to upgrade the firmware because it doesn't even want to do that now, via the stock rom. A little help please. fastboot set_active a returns the table of commands same with b and with .fastboot --set-active=a and b

 

[atiolon]

Okay so, I followed the instructions but I ****ed it all up. adb shell wouldn't do fastboot reboot fastboot from the bootloader, nor would the mounting command work. It still doesn't. I flashed those files thinking maybe I was already mounted and it defaulted me back to stock os. Then I tried getting back into twrp, but it wanted a password and I had a pattern, so I set a pin code, and that didn't work either. So I reset data user data and another one that was mentioned in another xda thread and now I can mount twrp and get in, but the lineage zip won't flash, it says invalid zip file format. So, I have no idea what Ive done to this phone or how to get lineage on it, or even at this point how to upgrade the firmware because it doesn't even want to do that now, via the stock rom. A little help please. fastboot set_active a returns the table of commands same with b and with .fastboot --set-active=a and b

I had many bad experiences trying to understand my Rav better. So I think I can help with this one. Let's try the following things:

- BOOT ON STOCK B
Turn on your phone on Fastboot (pressing and holding turn on + volume down). If it works, the screen will be with that Android toy.
Then you plug USB and type fastboot reboot fastboot to enter fastbootD mode.
When screen goes to fastbootd (if you didn't flash TWRP) you can type fastboot set_active b and then fastboot reboot. If you're on TWRP, just don't type anything in password and then set Slot B as active and reboot.
Now you're on stock again, probably.

- TRY AGAIN TO INSTALL LOS
On stock running, you can plug it again on computer and reboot via ADB to fastbootD mode with adb reboot fastboot.
In fastbootD mode, you can try again the steps, not forgetting to put them on Slot A. and wipe userdata with fastboot -w.

- DON'T FLASH TWRP. JUST BOOT FROM IT WITHOUT INSTALL IT.
When you want to use TWRP to install GApps or Magisk, use it not flashing. just type fastboot boot twrp.img from fastboot or fastbootD mode.

Everything should work from this.

 

[FoxySheila]

Thanks for the reply, a few questions.

I already have twrp installed, I'd be happy to get rid of it but don't know how to, fastboot reboot fastboot open's twrp, or does nothing at all. Adb reboot fastboot does work, but it takes me to what I'm assuming is my stock bootloader? I think the issue is that I need to get rid of twrp and get my recovery back, but I don't have a stock recovery file to flash, "fastboot flash recovery.img" or whatever it would be. I had to use Lenovo's rescue software earlier to put my stock os back on it. The phone isn't behaving as it should, or perhaps its my computer. I digress, when I try to activate a partition with the aforementioned command to do so, it gives me an error like that's not one of the commands it accepts. I tried three different flavors of adb, and they all reproduced the same syntax error. How would you proceed; and do you have a recovery img that I could use, I can't find one via google or loli. Edit: Progress has been made as using your suggestion I was able to get into fastbootD, the **** still wount mount with that command though. Edit 2: Managed to get adb shell working as it should be and flash the files but it just boot looped the phone, please advise. I got an error that said wipe successful after the last command but then it says not automatically formatting.

 

[FoxySheila]

...

.....

 

[Beetle84]

.....

First, your syntax is incorrect.
Fastboot flash recovery (nor recover) recovery.img

Second, you can download firmware from lolinet.
Just google the name and you will find it. Recovery.img is bundled with your firmware

 

[FoxySheila]

Hey there, thanks for the reply.

First, your syntax is incorrect.
Fastboot flash recovery (nor recover) recovery.img

Second, you can download firmware from lolinet.
Just google the name and you will find it. Recovery.img is bundled with your firmware

Thanks for the tips, as stated above I was able to get into fastbootD. As for the syntax, that's just me not proofreading what I'm typing and including unnecessary **** into a help request. I digress, I've done everything The user above my last comment suggested, and it boot loops my device, which is my current issue. Any ideas on how I could fix that? To clarify, I'm able to now flash in adb shell the parts of lineage, however, it bootloops my device. Even more concerning and strange is that it booted to twrp even though I was using the one built into fastbootD moments earlier without me booting or flashing to it. Thanks for the help.

 

[m666p]

Thanks for the tips, as stated above I was able to get into fastbootD. As for the syntax, that's just me not proofreading what I'm typing and including unnecessary **** into a help request. I digress, I've done everything The user above my last comment suggested, and it boot loops my device, which is my current issue. Any ideas on how I could fix that? To clarify, I'm able to now flash in adb shell the parts of lineage, however, it bootloops my device. Even more concerning and strange is that it booted to twrp even though I was using the one built into fastbootD moments earlier without me booting or flashing to it. Thanks for the help.

Switch the active slut and flash again...

 

[FoxySheila]

Hey, thanks for the suggestion.

Switch the active slut and flash again...

I'll switch slots and try tomorrow , in the meantime, is this you? http://gph.is/2lgUAQ5

 

[m666p]

I'll switch slots and try tomorrow , in the meantime, is this you? http://gph.is/2lgUAQ5

Yup, I become white on weekends. Also make sure you are flashing the ROM on slot A.

 

[GeranisaurusRex]

Flashed this no problems. Only major issue I've noticed so far is Android Auto doesn't function (plugged in, mirroring). Any chance of this being fixed?

 

[FoxySheila]

Nothing

Yup, I become white on weekends. Also make sure you are flashing the ROM on slot A.

Tried it your way, got bootlooped again, not working.

 

[babysupra112]

Hi All,

I am new to android and also new to flashing custom roms.

I followed the instruction in the OP but got stuck with following error, i am in fastbootd just to get that info out of the way.

[email protected]:/home/michael/Downloads/platform-tools# fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 17.069s]
writing 'system_a' 1/2...
OKAY [ 6.594s]
sending sparse 'system_a' 2/2 (517844 KB)...
OKAY [ 16.871s]
writing 'system_a' 2/2...
FAILED (remote: Operation not permitted)
finished. total time: 44.807s

please help?

additional info, I've unlocked the bootloader via motorola website, but I did not do the patch stock firmware with magisk step and came directly to flashing custom rom, if this makes any difference?
mods: I've made the same post in the omniRom thread, if this is not allowed, I apologize here, and please remove this post and keep the omniRom post, thankis.

 

[FoxySheila]

Heyo, wealcome to "my hell".. I mean the thread

Yea, I've tried to come at flashing this without getting bootlooped for over a month in as many ways and angles as a person can imagine, and it always boot loops, even for omni rom. Can't flash in twrp becuase it says invalid zip. I have followed the instructions both here and elsewhere to a ****ING t, but nothing. So either I'm a dumb sack of **** or there's something going on with my phone, maybe both? Anyway, a fun factoid I discovered a while back after ****ting my pants for a while thinking I bricked my phone is Lenovo has a rescue agent that for free, resets all moto firmware from regular fastboot back to stock. I've used it over a dozen times in the last month for the aforementioned boot looping. Here it is, I'll be around but for right now, it's clearly beyond me. https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa

 

[pankee182]

Hi, I was able to install everything perfectly and I was also able to get the vibration to work, the only problem is that I cannot enable screen clipping, I have tested it in fastbootD as in fastboot and it does not take command "cmd overlay enable org.omnirom.overlay. moto.rav ". I would need your help to solve that little problem, many thanks to everyone who can help!

 

[Greydesk]

Its been a long time since I rooted a phone and I'm stuck. Here is what I've done:
1. Become a developer
2. Enabled OEM_Unlocked in developer options
3. Installed the ADB package using apt-get (I'm running Linux Mint 20 Mate)
4. Allowed debug connection to my computer (remember this PC)
5. adb reboot bootloader (works)
6. fastboot oem get_unlock_data (stuck with display of <waiting for device>

Don't know where to go from here without bricking the phone.
BL: MBM-3.0-sofiar_retail-3b6d53a311-200901
Baseband: M6125_34.30.03.38R SOFIA_LATAMDSDS_CUST
Product/Variant: sofiar XT2041-1 64GB PVT

---------- Post added at 03:20 PM ---------- Previous post was at 03:12 PM ----------

Its been a long time since I rooted a phone and I'm stuck. Here is what I've done:
1. Become a developer
2. Enabled OEM_Unlocked in developer options
3. Installed the ADB package using apt-get (I'm running Linux Mint 20 Mate)
4. Allowed debug connection to my computer (remember this PC)
5. adb reboot bootloader (works)
6. fastboot oem get_unlock_data (stuck with display of <waiting for device>

Don't know where to go from here without bricking the phone.
BL: MBM-3.0-sofiar_retail-3b6d53a311-200901
Baseband: M6125_34.30.03.38R SOFIA_LATAMDSDS_CUST
Product/Variant: sofiar XT2041-1 64GB PVT

Nevermind. In Linux, adb can be run normally, but fastboot is a sudo command.

 

[Greydesk]

To help anyone who is not familiar with flashing, especially in Linux, here is the terminal output of my successful flash:

[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.006s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 15.017s]
Writing 'system_a' OKAY [ 3.363s]
Sending sparse 'system_a' 2/2 (467728 KB) OKAY [ 13.203s]
Writing 'system_a' OKAY [ 3.090s]
Finished. Total time: 34.727s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.749s]
Writing 'boot_a' OKAY [ 0.473s]
Finished. Total time: 2.269s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash product product.img
Resizing 'product_a' OKAY [ 0.006s]
Sending 'product_a' (512204 KB) OKAY [ 14.631s]
Writing 'product_a' OKAY [ 3.290s]
Finished. Total time: 17.972s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash vbmeta vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.047s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot -w
Erasing 'userdata' OKAY [ 0.628s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.654s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $

---------- Post added at 03:55 PM ---------- Previous post was at 03:55 PM ----------

Question: Can I get rid of the Motorola boot warning that says the bootloader is unlocked and has the pause?