Related
[size=+2]TWRP Flashable Stock builds for the Moto G4/G4 Plus[/size]
As you all know, Moto has finally released the first Oreo soak test for select users to test. Thanks to @rajatgupta1998, we all get to try it out
[size=+1]About these builds[/size]
This is the stock firmware, repackaged to be flashable in TWRP Recovery. In an effort to make these zips safer, I have removed all bootloader and gpt (partition table) related items.
[size=+1]Requirements[/size]
-> Unlocked bootloader
-> TWRP Recovery Installed (or booted)
[size=+1]Installation[/size]
-> Download the TWRP Flashable zip (Links below)
-> Place zip on device (internal or external storage)
-> Reboot to TWRP (or boot it)
-> Flash zip && Profit
[size=+1]Downloads[/size]
Nougat 7.0 (April 1st Security Patch)
• AFH -- TWRP-athene-7.0.0-NPJS25.93-14-18.zip
• G-Drive -- TWRP-athene-7.0.0-NPJS25.93-14-18.zip
md5sum == 71cab7a1bdebb067c569366dcaa26968
Oreo 8.1.0 Soak Test (November 1st Security Patch)
• AFH -- TWRP-athene-8.1.0-OPJ28.108.zip
• G-Drive -- TWRP-athene-8.1.0-OPJ28.108.zip
md5sum == c995bcb22215346e362195447de686f8
Oreo 8.1.0 (December 1st Security Patch)
• AFH -- TWRP-athene-8.1.0-OPJ28.111-12.zip
• G-Drive -- TWRP-athene-8.1.0-OPJ28.111-12.zip
md5sum == d7f7a0acdbb8e4bd24fa89e8513ec21c
Oreo 8.1.0 (December 1st Security Patch)
• AFH -- TWRP-athene-8.1.0-OPJ28.111-22.zip <-- coming soon
• G-Drive -- TWRP-athene-8.1.0-OPJ28.111-22.zip
md5sum == coming soon
[size=+1]Other Notes[/size]
* If you want to root, use Magisk and just flash in TWRP immediately after flashing the newest Oreo build. The latest build now fully passes SafetyNet and shows the device as being Certified in the Play Store.
* If you're already on the previous Oreo build (OPJ28.108 - November Security Patch), you can easily update to the latest Oreo build (OPJ28.111-12 - December Security Patch) by dirty flashing. If you want to keep root, you'll still need to flash Magisk again after flashing the newer build.
* To root the Nougat build(s), you will need to flash a custom kernel, then flash Magisk (same as before).
[size=+2]XDA:DevDB Information[/size]
[size=+1]TWRP Flashable Stock Builds, ROM for the Moto G4/G4 Plus[/size]
Contributors
@Jleeblanch, @rajatgupta1998, Motorola Mobility LLC
ROM OS Version: Android Oreo 8.1.0 - December 1st Security Patch
ROM Kernel: v3.10.84
Version Information:
Status: Beta
Created: 2018-11-26
Last Updated: 2019-01-09
**Reserved**
Coming from Pixel Experience 9.0 rom, wiped and installed. Working great so far. I hope we see an official rom soon.
zerocoolriddler said:
Coming from Pixel Experience 9.0 rom, wiped and installed. Working great so far. I hope we see an official rom soon.
Click to expand...
Click to collapse
these ROM have the same problems with camera like a soak test bulid?
all wipes needed to install these ROM?
vlrgamaley said:
these ROM have the same problems with camera like a soak test bulid?
Click to expand...
Click to collapse
This IS the Moto Soak test build. I've just made it TWRP flashable and safer for everyone to use. But yes, to answer your question, the issue with the Camera and Flashlight tile taking a few (5 or more) seconds to open is present here. There isn't anything I can do about that, however when Moto releases a future OTA update and have fixed the issue, I will make a new zip and post it here.
I will also make a nougat build of NPJS25.93-14-18 that is TWRP flashable as well for anyone who would like to be on stock nougat or easily revert back to stock nougat.
Thanks for your Hard Work.
Jleeblanch said:
ROM OS Version: Android Oreo 8.1.0 - November 1st Security Patch
ROM Kernel: v3.10.84
Click to expand...
Click to collapse
For curiosity: Would any of the (32 bit) custom kernels work with this ROM?
Thanks, I guess I won't be bored until I decide to unlock my G6 Plus
Jleeblanch said:
[size=+1]TWRP Flashable Stock builds for the Moto G4/G4 Plus[/size]
As you all know, Moto has finally released the first Oreo soak test for select users to test. Thanks to @rajatgupta1998, we all get to try it out
About this build
What is different about this versus what's already available? Basically what I have done is taken the previous 7.0 (nougat) firmware and directly patched it using the 8.1.0 (oreo) OTA zip from this thread. In an effort to make this build safer for everyone to use, I have left out any bootloader related items which is what can potentially prevent you from being able to downgrade. If this had been an official release, I would also have removed dm-verity (and forced encryption) as needed also. But being this is a test build from Moto, they have yet to enable such features. Now, on to the good stuff.
Requirements
-> Unlocked bootloader
-> TWRP Recovery Installed (or booted)
-> You may or may not need to be on stock nougat prior, need confirmation on this
Installation
-> Download the TWRP Flashable zip (Links below)
-> Place zip on device (internal storage or external)
-> Reboot to TWRP (or boot it)
-> Flash zip && Profit
Downloads
Oreo 8.1.0 Soak Test (November 1st Security Patch)
AFH - TWRP-athene-OPJ28.108.zip
G-Drive - TWRP-athene-OPJ28.108.zip
md5sum = c995bcb22215346e362195447de686f8
Other Notes
Currently as mentioned in the other thread, the build doesn't fully pass SafetyNet as it's a test release. You can use Magisk modules to fix this if needed.
You can also easily root by flashing Magisk immediately after the TWRP zip or any time afterwards.
[size=+2]XDA:DevDB Information[/size]
[size=+1]TWRP Flashable Stock Builds, ROM for the Moto G4/G4 Plus[/size]
Contributors
@Jleeblanch, @rajatgupta1998, Motorola Mobility LLC
ROM OS Version: Android Oreo 8.1.0 - November 1st Security Patch
ROM Kernel: v3.10.84
Version Information:
Status: Beta
Created: 2018-11-26
Last Updated: 2018-11-26
Click to expand...
Click to collapse
Thanx your .zip fixed the sim issues . Thanx mate
Jleeblanch said:
This IS the Moto Soak test build. I've just made it TWRP flashable and safer for everyone to use. But yes, to answer your question, the issue with the Camera and Flashlight tile taking a few (5 or more) seconds to open is present here. There isn't anything I can do about that, however when Moto releases a future OTA update and have fixed the issue, I will make a new zip and post it here.
I will also make a nougat build of NPJS25.93-14-18 that is TWRP flashable as well for anyone who would like to be on stock nougat or easily revert back to stock nougat.
Click to expand...
Click to collapse
Waiting for the Nougat build! Really need to go back to stock. Thank you for your work!
Awesome work dont stop keep up the good work
I`ve had previously RR 5.8 (Nougat 7.1, no custom kernels) and try install your ROM (without wipes, like you describe in instruction). Result? Bootloop. I have Moto 2g RAM/16 Gb Flash, install through rajatgupta recovery v 3.2.1-r3. Try now with wipes, but i don`t have confidence for good result.
try again with wipes, works normally. woah
jer194 said:
For curiosity: Would any of the (32 bit) custom kernels work with this ROM?
Click to expand...
Click to collapse
I doubt any of the stock kernels currently available would work as they're intended for nougat (7.0).
corlatemanuel said:
Thanks, I guess I won't be bored until I decide to unlock my G6 Plus
Click to expand...
Click to collapse
Fair enough. I'm surprised you haven't unlocked the bootloader yet, LineageOS is pretty good for the G6+ and also is used as a base ROM for flashing GSI's. I'll be making a stock based custom kernel (and one for the custom rom's/GSI's soon too).
DanFaraday777 said:
Waiting for the Nougat build! Really need to go back to stock. Thank you for your work!
Click to expand...
Click to collapse
I gotta finish up some TWRP flashable builds for the Moto G6 and then I'll upload the one I made for nougat when I upload those [emoji41]
luv u
thanks a lot
Thanks for zip :good:
What do you mean by "Stock nougat prior"?
Sorry for the dump question
Henry Markle said:
What do you mean by "Stock nougat prior"?
Sorry for the dump question
Click to expand...
Click to collapse
I mean the latest stock nougat build NPJS25.93-14-18
jer194 said:
For curiosity: Would any of the (32 bit) custom kernels work with this ROM?
Click to expand...
Click to collapse
To expand on Jleeblanch's reply, you may have to wait for Motorola to release the Oreo kernel source code, so developers can work on improving the kernel. Best thing to do is to check the Motorola Mobility GitHub page every so often, where you may see a request for the Oreo source code for our device appear https://github.com/MotorolaMobilityLLC/kernel-msm/issues Once there's a request made, Motorola should release the code when it's ready for release and then pave the way for custom Oreo kernels
echo92 said:
To expand on Jleeblanch's reply, you may have to wait for Motorola to release the Oreo kernel source code, so developers can work on improving the kernel. Best thing to do is to check the Motorola Mobility GitHub page every so often, where you may see a request for the Oreo source code for our device appear https://github.com/MotorolaMobilityLLC/kernel-msm/issues Once there's a request made, Motorola should release the code when it's ready for release and then pave the way for custom Oreo kernels
Click to expand...
Click to collapse
I would make the request myself, same as I've done for other devices (currently have a request up for beckham) but being that this is supposed to be a private soak test, not sure if they'll appreciate it just yet. But best believe, when they release the official Oreo build, I'll be all over it (assuming someone doesn't beat me to it [emoji6])
Jleeblanch said:
I would make the request myself, same as I've done for other devices (currently have a request up for beckham) but being that this is supposed to be a private soak test, not sure if they're appreciate it just yet. But best believe, when they release the official Oreo build, I'll be all over it (assuming someone doesn't beat me to it [emoji6])
Click to expand...
Click to collapse
Oh yup, it'd probably be a bit soon to put in a request, and I imagine they may change the kernel source code for the final release anyway (e.g. if they update to the latest security patch). Thanks for keeping a close eye on it - exciting times ahead
Hey, all! I am very new here, although I always use this forum as reference, including for my previous smartphones: Xpera Z3 Dual and Galaxy S3.
But now I have a Pixel 2 XL (taimen) with the latest stock ROM (February 9, 2019 Android 9 Pie). I want a Custom ROM with no Google apps included whatsoever, could somebody help me out and give some directions? I have spent hours trying to flash a CarbonROM with no success. I don't want root, I just don't want Google Apps. A few questions:
- Is unlocking the bootloader mandatory to flash any Custom ROM?
- If I am on Android 9 Pie and the custom ROM is based on 8 Oreo, is it mandatory to flash the Oreo factory image from Google? If so, can I do it by simply using the OTA sideloading? I couldn't flash with the fastboot script.
- Is TWRP mandatory in this case? Is root mandatory?
I am really thankful for this community and appreciate any help you can give me.
abbluiz said:
- Is unlocking the bootloader mandatory to flash any Custom ROM?
- If I am on Android 9 Pie and the custom ROM is based on 8 Oreo, is it mandatory to flash the Oreo factory image from Google? If so, can I do it by simply using the OTA sideloading? I couldn't flash with the fastboot script.
- Is TWRP mandatory in this case? Is root mandatory?
I am really thankful for this community and appreciate any help you can give me.
Click to expand...
Click to collapse
- Yes
- Yes; No
- Yes, for flashing custom rom. Root is not mandatory.
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?
Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!
itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update
ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?
itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!
Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939
Hey everyone,
Just a quick question, if I'm flashing an Android Q GSI, do I need an Android Q Vendor image flashed? Or can I use the Pie Vendor and create an overlay for it? Last time I messed with "mismatched" partitions, I had to pay to have my phone unbricked, and with anti-rollback enabled, I'm hesitant to upgrade.
Thanks
Found my answer in this thread, you can use Pie vendors with Q GSI's https://www.xda-developers.com/install-android-q-beta-gsi-project-treble/
Hello, I was wondering if I need to update my firmware on my Xiaomi Redmi Note 5 Pro (whyred).
The reason for it is because it shows "1. November 2018" as latest vendor security patch level.
I am currently running LineageOS 17.1 which is based on Android 10 together with the Lineage recovery.
Mainly I have these questions:
1. Do I need to update the vendor firmware? In other words would that even increase the Vendor security patch level?
2. When I checked this website: https://xiaomifirmwareupdater.com/firmware/whyred/ it shows the latest Vendor Firmware to be from 2021, however with Android 9.0, would that even work with LineageOS 17.1 which is Android 10 level?
3. Would I need to flash back to the official Rom on Android 9.0 in order to then flash to the 2021 firmware ( should be included in the latest official rom anyway) and then flash back to LineageOS 17.1?
Any help is greatly appreciated as this is my first phone on LineageOS. (I did had a couple of other phones in the past with unofficial Roms so I am not a completely noob.)
Thanks and have a good day
StriKe_jk said:
Hello, I was wondering if I need to update my firmware on my Xiaomi Redmi Note 5 Pro (whyred).
The reason for it is because it shows "1. November 2018" as latest vendor security patch level.
I am currently running LineageOS 17.1 which is based on Android 10 together with the Lineage recovery.
Mainly I have these questions:
1. Do I need to update the vendor firmware? In other words would that even increase the Vendor security patch level?
2. When I checked this website: https://xiaomifirmwareupdater.com/firmware/whyred/ it shows the latest Vendor Firmware to be from 2021, however with Android 9.0, would that even work with LineageOS 17.1 which is Android 10 level?
3. Would I need to flash back to the official Rom on Android 9.0 in order to then flash to the 2021 firmware ( should be included in the latest official rom anyway) and then flash back to LineageOS 17.1?
Any help is greatly appreciated as this is my first phone on LineageOS. (I did had a couple of other phones in the past with unofficial Roms so I am not a completely noob.)
Thanks and have a good day
Click to expand...
Click to collapse
LOS has old version of vendors. Yes from 2018.. they build on that... if you wanna updated version go to LOS github and ask there.. that's how it is, nothing can be done here. Only LOS team can help you.
Good luck and stay safe!
drnightshadow said:
LOS has old version of vendors. Yes from 2018.. they build on that... if you wanna updated version go to LOS github and ask there.. that's how it is, nothing can be done here. Only LOS team can help you.
Good luck and stay safe!
Click to expand...
Click to collapse
Does this mean 2018 is the latest vendor security patch level?
StriKe_jk said:
Does this mean 2018 is the latest vendor security patch level?
Click to expand...
Click to collapse
If you use LOS, than yes.
Maybe I am a bit dense to understand this, but shouldn't all have the same? I thought Vendor security patch level are bugfixes from the vendor, so it only makes sense to me to include the latest patches in all roms to get this baseline patch level. Ofc every ROM can feel free to increase security even further with additional patches on top of that.
StriKe_jk said:
Maybe I am a bit dense to understand this, but shouldn't all have the same? I thought Vendor security patch level are bugfixes from the vendor, so it only makes sense to me to include the latest patches in all roms to get this baseline patch level. Ofc every ROM can feel free to increase security even further with additional patches on top of that.
Click to expand...
Click to collapse
Yap, but every custom Rom has it's own vendor version. LOS has old one and many custom ROMs. It's actually developer decision what version he's gonna use to build rom. That's it. Yes MIUI ROM uses latest. You can't mix them because you'll get bootloop or bricked device.
For latest version you need to ask developer to update it.
StriKe_jk said:
1. Do I need to update the vendor firmware? In other words would that even increase the Vendor security patch level?
Click to expand...
Click to collapse
The vendor security patch level is just a setting configured here: https://github.com/LineageOS/androi...0038ae0340b1da03ae9c00ff50/BoardConfig.mk#L56
The official LOS 18.1 rom contains at least some vendor blobs from the latest MIUI V12.0.2.0.PEIMIXM rom.
That probably means the vendor security patch level date is not accurate and can be ignored.
StriKe_jk said:
2. When I checked this website: https://xiaomifirmwareupdater.com/firmware/whyred/ it shows the latest Vendor Firmware to be from 2021, however with Android 9.0, would that even work with LineageOS 17.1 which is Android 10 level?
Click to expand...
Click to collapse
Yes, it works. Considering you are currently using even older firmware.
StriKe_jk said:
3. Would I need to flash back to the official Rom on Android 9.0 in order to then flash to the 2021 firmware ( should be included in the latest official rom anyway) and then flash back to LineageOS 17.1?
Click to expand...
Click to collapse
You can flash the firmware ZIP from https://xiaomifirmwareupdater.com/firmware/whyred/. It only updates the various firmware partitions without touching the "boot", "system" and "vendor" partitions (on which LOS is installed).
For some reason the firmware ZIP is missing the new boot logo. It can be updated manually by extracting the file "/firmware-update/splash.img" from the latest MIUI Rom and flashing it in Fastboot Mode with
Code:
fastboot flash splash splash.img
I'm on Lineage OS 18.1 now with Android 11 and figured I just leave it as is. But thanks all for the help