Question Help needed installing LineageOS with MicroG - ASUS ZenFone 8

I've managed to successfully install LineageOS 19.1 on my Zenfone 8 but I didn't realise you needed an entirely different release to use MicroG.
So I am now trying to install the LineageOS for MicroG release but I'm running into problems:
The MicroG release is a few weeks older than the LineageOS one. When I tried installing it I got an error "SPL is considered a downgrade" and it wouldn't let me install it.
The MicroG release doesn't provide a `vendor_boot.img` file which is required according to the LineageOS instructions. I tried using the file from the regular LineageOS release and it seemed to work the first time but now it won't boot into the recovery mode at all; it just boots into the bootloader menu.
I saw people saying that the MicroG release is missing some img files but I used the payload-extractor Python script and I cannot see any difference between the list of files in the MicroG release and the original LineageOS one. They both contain 29 img files.
I saw posts in the development thread that people are having similar struggles so I'm not sure how to proceed.
Ultimately, my request is: can someone please outline an easy-to-follow approach on how to install LineageOS with MicroG on the Zenfone 8?

AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Therefor I would recommend to install another OS:
OmniROM https://omnirom.org/
The OS images for OmniROM for the Zenfone 8 can be downloaded here:
https://dl.omnirom.org/zenfone8/
A new OS image of OmniROM with MicroG is created every Sunday.
The OmniROM image can be installed via sideload using the recovery image from the LineageOS.
And it works without problems (including MicroG) You can even install a patched version of the original playstore that will work with MicroG.
In case you want to stay with the LineageOS I recommend to use the LineageOS image without MicroG and use the NanoDroid image (which contains MicroG) from https://nanolx.org/
I used NanoDroid (installed as Magisk Module) on my previous phone several years for which no OS image with integrated MicroG exists.
regards
Bernd

bnsmb said:
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Therefor I would recommend to install another OS:
OmniROM https://omnirom.org/
The OS images for OmniROM for the Zenfone 8 can be downloaded here:
https://dl.omnirom.org/zenfone8/
A new OS image of OmniROM with MicroG is created every Sunday.
The OmniROM image can be installed via sideload using the recovery image from the LineageOS.
And it works without problems (including MicroG) You can even install a patched version of the original playstore that will work with MicroG.
In case you want to stay with the LineageOS I recommend to use the LineageOS image without MicroG and use the NanoDroid image (which contains MicroG) from https://nanolx.org/
I used NanoDroid (installed as Magisk Module) on my previous phone several years for which no OS image with integrated MicroG exists.
regards
Bernd
Click to expand...
Click to collapse
Thanks for the recommendation. I would prefer to stick with LineageOS because of the larger community.
NanoDroid looks good but I don't think it'll be suitable. It looks very complicated and talks about patching ROMs for signature-spoofing support. It also doesn't actually say how to install it (the documentation literally just says "install NanoDroid" as one of the steps...) and finally it only supports Android 11 at the moment.
If anyone else has hints about using MicroG with LineageOS on a Zenfone 8 please let me know. I feel like it really shouldn't be this hard.

hawkins22 said:
Thanks for the recommendation. I would prefer to stick with LineageOS because of the larger community.
NanoDroid looks good but I don't think it'll be suitable. It looks very complicated and talks about patching ROMs for signature-spoofing support. It also doesn't actually say how to install it (the documentation literally just says "install NanoDroid" as one of the steps...) and finally it only supports Android 11 at the moment.
If anyone else has hints about using MicroG with LineageOS on a Zenfone 8 please let me know. I feel like it really shouldn't be this hard.
Click to expand...
Click to collapse
I would prefer to stick with LineageOS because of the larger community.
Click to expand...
Click to collapse
Understand
But for the records:
Signature-spoofing is only required to use all features of MicroG , e.g. to use the patched Playstore. If you don't need that you can ignore this.
The best method (IMHO) to install NanoDroid is:
- install Magisk into the booot partition
- install the ZIP file with NanoDroid using TWRP
Nanodroid will then install MicroG as Magisk Module .
regards
Bernd

Hello,
The issue is due to the fact that LOS+MicroG has a long delay in releases (at the time of this message, the latest LOS version is 2023-02-03 and the latest LOS+MicroG 2022-12-22). I think it is an issue because the main site announces a build every two weeks, and there are some tickets in their Git repository about this.
Anyway, I had the same issue few weeks ago and I managed to install LOS+MicroG using an old vendor_boot image; indeed you have to use the one provided by the LineageOS wiki, but you have to use one older than the LOS+MicroG release to avoid the SPL issue.
Unfortunately, I had a look and the previous version was deleted on their website since I installed my phone and I can't provide the one I used because I removed the file...
So I'm afraid you have to wait a new LOS+MicroG build or find a old vendor_boot.img to proceed.
But I agree with you: it's a shame that there is no straightforward way to install LOS+MicroG. It was easy in the time, but now it's more complicated to manage due to phones specification (I guess, I'm not a ROM dev) - but yes I think that discourage a lot of people to use it.
Good luck.

bnsmb said:
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.
Click to expand...
Click to collapse
Yeah, that's why "LineageOS for microG" exists in the first place. It is a fork of LineageOS where signature spoofing was enabled. So, there is no issue using LineageOS for microG. Please educate yourself before posting things like this.
"I saw people saying that the MicroG release is missing some img files but I used the payload-extractor Python script and I cannot see any difference between the list of files in the MicroG release and the original LineageOS one. They both contain 29 img files."
Click to expand...
Click to collapse
There are (or at least in the past were) indeed some files missing from "LineageOS for MicroG" for the Asus Zenfone 8. It is/was a bug confirmed by the developers. I reported it to them, maybe they fixed it in the meantime. This would be good news! I haven't checked for a while.
However, then I don't understand why you say "The MicroG release doesn't provide a `vendor_boot.img`". So why exactly is this file missing and where did you find it in the official LineageOS? And for what step do you need it? I don't remeber that I was using this file for installing LineageOS. Only Magisk needed that file. But it was easy to retrieve from the extracted payload.

I managed to install it successfully using TWRP instead of Lineage's own recovery image. Maybe TWRP simply doesn't care if you're "downgrading" and lets you flash anyway?
The final step-by-step process I used was something like this:
Unlock the phone's bootloader using the official ASUS unlocking tool APK.
Restore the phone to its stock Android 12 state using the ASUS "raw" image (instructions):
https://dlcdnets.asus.com/pub/ASUS/...KS-31.1010.0410.61-MR0-2204-user-20220422.zip
Flash the "vendor_boot.img" file from the regular LineageOS release as detailed in the instructions.
Install TWRP recovery instead of the LineageOS recovery image.
Use TWRP recovery to flash the LineageOS-MicroG ROM.

Mario545 said:
However, then I don't understand why you say "The MicroG release doesn't provide a `vendor_boot.img`". So why exactly is this file missing and where did you find it in the official LineageOS? And for what step do you need it? I don't remeber that I was using this file for installing LineageOS. Only Magisk needed that file. But it was easy to retrieve from the extracted payload.
Click to expand...
Click to collapse
The vendor_boot.img is required according to the LineageOS installation instructions and is provided as a separate download on the same page.
However after extracting both the LineageOS and the LineageOS-MicroG releases, I believe the vendor_boot.img files are actually identical (same filesize) so you can probably use them interchangably anyway.

I see, probably was not required when I was installing an earlier version of LineageOS.
Anyway, vendor_boot.img should additionally be included in your payload file from the archive. The one they provide for download is probably just an extracted one to make it easier.

Mario545 said:
I see, probably was not required when I was installing an earlier version of LineageOS.
Anyway, vendor_boot.img should additionally be included in your payload file from the archive. The one they provide for download is probably just an extracted one to make it easier.
Click to expand...
Click to collapse
AFAIK the vendor_boot.img is also required by the LineageOS recovery image necessary to install the LineageOS image.
Therefor it must be installed before booting the LineageOS recovery.
regards
Bernd

Related

[Project Treble][v1.1][Android PIE + OREO][GSI][A-only]

View attachment 4567426
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
What's a GSI?:
A GSI literally means Generic System Image. It is a general system image meant for no specific device. Treble enabled devices have the capability to run a GSI. You can find a GSI here: Phh-Treble
ZTE Axon 7 hardware vs Treble implementation:
Our Axon 7 is an A-only device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-Only system images
What's Packaged in the zip:
A boot image (kernel)
A compressed vendor image (vendor)
Requirements:
- Unlock bootloader
- Installed patch EDL to add /vendor part. 800Mb
- Installed TWRP 3.2.1-8 - TREBLE
How to install:
- Format /system, /data and /cache, wipe /vendor
- Install Treble flashable zip package Project_Treble_v1.0-by-NFound
- Install GSI .img in /system part. How to flash a Generic System Image (GSI) on Project Treble supported devices
- Reboot
Alternative Instruction
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
Broken:
Encryption (format data or remove encryption when coming from a non-treble rom)
Sepolicy is still permissive
Nothing else? Otherwise please report it!
Download:
- TWRP 3.2.1-8 TREBLE
- AXON7_GPT_ADD_VENDOR_800MB
- Project_Treble_v1.1-Axon7-by-NFound
Available GSI images is here
Android Pie Release 1 and other (video proof on Axon 7)
Fixes:
- More fixes for Treble ROM by @Kranoner
Credits:
@djkuz for add part. /vendor
@NFound for the fact that this dude did this for us real
Contributors:
@NFound
OS Version based: 8.X Oreo
ROM Kernel: Linux 3.18.71
ROM Firmware Required: Official BETA B12 Oreo
Version Information
Status: Testing
Source-Code Vendor
Created 2018-08-08
Last Updated 2018-08-12
Reserved
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Waancho said:
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Click to expand...
Click to collapse
Any ARM64 with opengapps.org for 8.x, in GSI 9.x Gapps included
Dear friends! Do not forget to backup before installation, this is a test version. It's time for me to sleep, write. As time will be, I will read your comments. If you find bugs - be sure to specify the version of GSI Android 8.x or 9.x
Thank you!
Hey need fast answer! In this guide is talking about a Vendor 8.1 and 8.0 and 8.0 does not work with this rom, so my question is does this rom support your treble? https://forum.xda-developers.com/pr...development/aosp-9-0-android-9-0-gsi-t3826357
Source code vendor blobs in OP
NFound said:
Source code vendor blobs in OP
Click to expand...
Click to collapse
I am a bit confused: how would non-standard hardware like our famous DAC be used in a treble ROM? Would the vendor partition make specific APIs available for such non-standard hardware?
Thank you for this. Maybe its a stupid question, but does the DAC properly function even when we install a GSI?
I have a feeling that a proper fully functional treble will make the other custom ROM thread for Axon 7 obsolete.
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Zobat said:
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Click to expand...
Click to collapse
You dont need a windows-pc. Only twrp
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Let me see if I got this whole treble situation straight :cyclops:
I'm running the latest AEX but I assume this guide contains a more updated "treble" so to speak, is that correct? In order to try the GSI's do I need to follow this guide and wipe everything or will the next AEX release update treble and contain the new fixes?
https://sourceforge.net/projects/resurrectionremix-oreo/files/arm64aonly/
Arm64 and A only. Should be working right?
BaamAlex said:
You dont need a windows-pc. Only twrp
Click to expand...
Click to collapse
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
troy5890 said:
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Click to expand...
Click to collapse
You will need to install this again Project_Treble_v1.0-by-NFound
it contains bug fixes
bornlivedie said:
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
Click to expand...
Click to collapse
For this zip here he dont need a PC. For the EDL package yes.
Just wanted to thank you and talk about my experience.
Converting the device to Treble was a breeze. Can be done in under 5 minutes with no issues at all. I'm currently running Android P PR1 with no major problems.
However, when trying to install the GSI (totally not related to your work, but wanted to comment on this so everyone can enjoy treble) I ran into a small problem (error 7) when flashing the POST sGSI zip files. I resolved this by doing the following:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
This worked out fine for me.
Again, thanks a million times on your epic feat. This is no small task, and is very welcome. It marks a before and an after.
You, sir, are heaven-sent. Thank you for your good work.
bornlivedie said:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
Click to expand...
Click to collapse
Why a second time?
Dear friends!
In the video I am used Release 1.
1. Flash Project Treble
2. Flash GSI
3. !!! In Mounting - UNMOUNT and MOUNT system and vendor!
4. Install patches 1,2,3
5. Reboot
Android Pie Release 1 (Download A-only and patches): https://androidfilehost.com/?w=files&flid=280192
Work GCam: https://github.com/AospExtended/platform_vendor_aosp/blob/8.1.x/prebuilt/common/apk/Gcam.apk
NOTICE: If during a call on Android 9 you do not hear the subscriber. (thx @atakan33 )
PS Here is another list of available GSI ROMs, use the translator!
9.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-2
8.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-3
Thank you!

[Expert] [GUIDE] Install fully working Android 10 using jarlpenguin's project treble

I recently started experimenting with Android 10 and found a fully working setup. So I'm deciding to share my current setup
#USE THIS AT YOUR OWN RISK!
I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE DUE TO A BAD ROM FILE OR ELSE!#
#BUGS: NFC isn't working on downloadable build
You tell me#
NOTE: you can also use his newer builds. BUT those aren't preconfigured. For patches that you will need see 3rd post!
Requirements: latest twrp from official source,
Oreo firmware.
This Google play services APK:
https://drive.google.com/file/d/1V8ByPJx_hOoPpQNrG0LQcXzhHpFflN-I/view
I think that's it
Step 1: Download jarlpenguin's latest treble build here:
https://github.com/MontanaDevelopme.../lineage-16.0-20190713-UNOFFICIAL-montana.zip
Install it and wait for it to go into the lineage is setup screen. Reboot to recovery (you can download a rom by just going through setup, but all installed apps will be wiped!)
Step 2: if you haven't already download a rom of choice with a build date similar to this: 201910##
These builds should work with sim-card and possibly gapps
But I recommend this rom (please extract it first, otherwise you won't be able to flash this) : https://mega.nz/#!EE11mZyC!_45oKcdNv8djsA8CEh2ZVoTDkic3BCpLfFfU9TLUhes
Step 3: wipe system and data and head to the install section
Step 4: hit "install image" in the bottom right corner and navigate to the location of the extracted .img file
Step 5: select "system image" after pressing it and swipe to flash
Step 6: wait for it to boot (this can take quite a while so, please be patient!)
Step 7: when the device is booted, immediately head into the files application and install the Google play services app from the folder you put it in.
Step 8: after a while, the "completing system update" message should disappear. But there still is one problem... As this is a ported rom (I know I didn't mention this before) this still has the "system updater" app. So, you might disable that, otherwise it flashes a incompatible rom file.
ENJOY!
###ROOT###
to root the ROM, you need phh magisk, you should easily find it on Google or a search engine of choice. THE NORMAL BUILDS DON'T WORK, phh magisk is made for Android 10 treble builds using phhussons base or patches. That's why the normal version doesn't work
If you need help, feel free to contact me on telegram! @Rush
Sneak 100 profile picture
###GCAM###
To use gcam you should flash a Magisk module called:
"Several fixes for Moto G5/G5s"
Some apks may still not work though... As I haven't figured one out which 100% works
###Alternative ROMs###
To use alternative ROMs you will need to (most of the time) use a different lineage OS version by JarlPenguin together with only the boot & vendor images listed below:
https://drive.google.com/folderview?id=1QztsGvkhURcoCp-FjI40mvUpLp5NHSpj
Also, you know that a room won't boot when TWRP crashes, so don't even try, and no, even though the lineage 17.1 alpha build does "support" project treble, it doesn't have any better compatibility with Android 10 ROMs,
The only ROMs with at least some features I could get running is really just Pixeldust X ported from the pixel 1 using erfans tools
And this also works, of you are using (again) a newer or the latest build together with patches (see boot&vendor images above):
https://sourceforge.net/projects/zj...el-Aonly-10-20191120-GSI.img-1640.7z/download
Don't forget to extract this first! /\
Note: this newer build has NO MOTO GESTURES AT ALL
Sadly, I don't think there is a fix to that
### EVOLUTION X ###
I finally found a build which is working but. Uhhhh is kind complicated to bit to it first time
Basically you follow the normal tutorial, and then replace the advertised build with the latest 202001xx build by jarl
then wait for boot
Then reboot to recovery, and wipe system and data.
Reboot (I know that nothing is installed rn)
Select recovery and boot
Flash the evolution X .IMG fine and hope for it to but crash
Sadly,
There isn't even a guaranteed boot if you do that
But it will do the job good enough
Also, you won't need the GMS services APK anymore as this has everything already updated to ****
Please DONT flash the vendor and boot image patches as these will not allow the device to boot for some godforsaken reason
Link (please extract first):
https://sourceforge.net/projects/de...lution-X_3.3_20191111_ARM64-A.img.xz/download

[SHARE] LineageOS 19/18.1 android 11 and 12 Combined galaxy tab A 10.1 (2019)SM-T515/SM-T510

First of all this is not my work is just tried this rom and its preety stable. Thanks to developers @phhusson @Magendanz
DESCLAIMER :use it your own risk.
So finally this rom booted on galaxy tab SM-T515 everything thing is working with small bugs as mentioned below.
Download files given below:
Bugs :
1)voLTE: not working tried phh treble settings to solve the issue but no luck.
Other networks, data calling works perfectly
2)MTP: mtp not working but you can transfer files after booting device in TWRP mode
3)audio not recording in videos use open camera app and go to settings and set default audio as a source.
4)For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Reverting to Samsung oneui:
For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Download firmware using this app:
Download link for Android/Linux/Mac/Windows:
Releases ยท zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Linageos18.1 user restore your oneui backup using twrp or use ODIN firmware.
Except these you can check and tell me I didn't found anything till now
Download this gsi fileonly this is compatible)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20211010-UNOFFICIAL-treble_a64_bvS-vndklite.img.xz/download
Download arm 32 android 11 gapps :
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Linageos 19 android 12Gapps included)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.0-20220114-UNOFFICIAL-treble_a64_bgS.img.xz/download
Download magisk zip:
https://dl.magiskapp.com/MagiskZip/Magisk-v23.0.zip
If you gets device certification error follow this post:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
XZ file extractor android app:
GZ & XZ Extract - File Opener - Apps on Google Play
Extractor tool for tar, tar.gz, gz, gz2 & xz files. Just few taps for result
play.google.com
Process :
1)Download all files given first extract xz file gsi file using xz extractor you gets img file.
2)Now transfer gsi.img, gapps and magisk file in tablet.
3)boot tablet to TWRP MODE
4)Now first select wipe >advance wipe>select system> slide
5) now go back click install click install img you will see your file click on it and select system partition and enter.
6) now we have to install gapps but we need to first resize system partition so
First click mount and mount system Partation now go to wipe>advance wipe>select system >clcik repair >click resize
7)now click install and. Select gapps and flash.
8)now go back install magisk and hit reboot.
After reboot you may face device certification error so to solve this go to magisk and install magisk hide props configuration module and reboot your phone.
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Follow this video i will update thread soon
Android 11 Linageos 18.1
Android 12 lineageOS 19
How's the battery life?
works offline charge?
Pinage said:
How's the battery life?
Click to expand...
Click to collapse
Best battery life
Spawacz_Reduktor said:
works offline charge
Click to expand...
Click to collapse
Yes
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Sukrith said:
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Click to expand...
Click to collapse
Yes same time but that has grafix shutter issue same like gsi
pankspoo said:
Yes same time but that has grafix shutter issue same like gsi
Click to expand...
Click to collapse
There seems to be a new build, can you maybe try? It's based on 6th November build.
Sukrith said:
There seems to be a new build, can you maybe try? It's based on 6th November build.
Click to expand...
Click to collapse
Ok
In January I installed 17.1 using this ROM. Do I need to go through the whole process of resizing the partition, since I already did it for 17.1?
Never mind! I went ahead and installed it following the instruction . It works, thanks!
bedwere said:
Never mind! I went ahead and installed it following the instruction . It works, thanks!
Click to expand...
Click to collapse
Are you happy with this ROM?
Krekle said:
Are you happy with this ROM?
Click to expand...
Click to collapse
Yes, it's very stable.
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Shawnashley said:
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Click to expand...
Click to collapse
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
HansMampf said:
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
Click to expand...
Click to collapse
I can only answer some of your questions:
- Magisk is only used for root. It's not required.
- Mounting /system in TWRP or in a File explorer doesn't seem to be possible.
- GApps is built in to roms with "...bgS.img.xz". For vanilla roms without gapps download the "...bvS.img.xz"file.
- For LOS 19, I flashed treble_a64_bgS and didn't have an issue. I can't comment on the vndklite version or what it's used for since I never tried it.
betacrypt said:
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
Click to expand...
Click to collapse
Any idea about success of I am running Megadanz 11.0 ROM?
Shawnashley said:
Any idea about success of I am running Megadanz 11.0 ROM?
Click to expand...
Click to collapse
It's a good rom and works very well. I was using it before I upgraded to LOS19.1.
Hey there!
I Installed this a couple of weeks ago, but has to reinstall nexus stock 11.0 pretty quickly, as after spending an evening trying to fix issues, it just wouldn't work.
Issues:
1) App crashes are constant. I cannot open Chrome, YouTube, Google Podcasts, Twitter - they all crash to launcher. - Cache, dalvik and data was cleared, still nothing
2) Gesture Navigation is missing - is it meant to be?
3) Magisk installs successfully,, but is then not recognised by the app, meaning no modules. - Is that normal?
Does anyone have any idea on how I could fix these issues, so I can install again?
Many thanks

Development [CLOSED] LineageOS Rom for Pixel 5a Android 11 - April 16, 2022

You MUST be on Android 11 to use this!!!!!
If your not, you must flash latest Google factory image for Android 11
This is based on the Android Open Source Project. It can be used without any need to have any Google application installed. It does still include various proprietary hardware-specific code.
Gapps must be flashed separately and are not included in this ROM.
All the source code is available in the Github repo here. You can also view the changelog for a full list of changes & features here.
Thanks go to Github and LineageOS for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the LineageOS source code, device specific code and proprietary blobs. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Repo Synced every three days to keep the code base fresh. Also updated daily with minor changes.
DOWNLOAD BOOT, ROM & GAPPS HERE
FLASH BOOT TO BOTH SLOTS IN BOOTLOADER
fastboot flash --slot all boot boot.img
REBOOT TO RECOVERY
FACTORY RESET
SIDELOAD ROM IN RECOVERY
adb sideload 20220416-barbet-OFFICIAL-signed.zip
REBOOT TO RECOVERY. IT WILL AUTOMATICALLY SWITCH SLOTS
SIDELOAD GAPPS
adb sideload SayaGapps-mini-20220418-signed.zip
REBOOT TO SYSTEM
REBOOT TO RECOVERY TO ROOT
SIDELOAD MAGISK.APK
adb sideload magisk.apk
REBOOT TO SYSTEM
OTA updates are now available through the built in updater on the phone and are updated daily.
Check settings, system, advanced, updater.
Download and let update install. Reboot to system.
You can change the preferences in the updater to check for updates automatically daily and you will get a notification when a update is available. Default setting is once a week.
Root is now retained after update. No need to root again after applying update.
Screen call now works with my latest gapps packages.
Can you share more details please about this rom? Any features?
jimmy16 said:
Can you share more details please about this rom? Any features?
Click to expand...
Click to collapse
As it states, its a basic ROM, open source with LineageOS features.
OTA updates are now available through the built in updater on the phone.
What's the difference between this rom and the official lineage os 18.1 rom? I know you stated,
"The ROM uses the LineageOS source code, device specific code and proprietary blobs. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Repo Synced every three days to keep the code base fresh. Also updated daily with minor changes."
Is that all?
Klimon5 said:
What's the difference between this rom and the official lineage os 18.1 rom? I know you stated,
"The ROM uses the LineageOS source code, device specific code and proprietary blobs. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Repo Synced every three days to keep the code base fresh. Also updated daily with minor changes."
Is that all?
Click to expand...
Click to collapse
Yes, basically the same, just uses my own signatures and a lower file size as it states. Other difference is that I update it daily while the other one is updated weekly.
Does VoLTE work on this rom?
achillesphazd said:
Does VoLTE work on this rom?
Click to expand...
Click to collapse
Yes
I like this ROM quite a bit on my Pixel 5a. Is it possible to get the Google Assistant working?
Riddickulus
RiddickulusSF said:
I like this ROM quite a bit on my Pixel 5a. Is it possible to get the Google Assistant working?
Riddickulus
Click to expand...
Click to collapse
Works fine but needs to be set manually in the settings. Go into settings and search assistant then select digital assistant app and change it to Google. Default setting is None. You must also be using either my gapps that are included to flash seperately or another form of gapps that have the google digital assistant app present. Any other gapps or none at all, then it won't work.
Official builds as of 02/19/22. Must wipe previous builds to avoid bootloop.
Test keys replaced by official developer signed private keys. Updater will not work on previous builds. Must update to this build manually to receive future updates in the updater.
Mr. Sayaman, I keep getting an "oops no mirrors available" error when trying to download your files. any clue why?
Thank you for taking the time to create this mod for us freeloaders.
One more question:
I just installed the official lineage, seems to work except it's not seeing my sim card. Any idea if your build will fix that issue?
edit: reflashing fixed sim issue.
Thanks for any help/info!
blasf69 said:
Mr. Sayaman, I keep getting an "oops no mirrors available" error when trying to download your files. any clue why?
Thank you for taking the time to create this mod for us freeloaders.
One more question:
I just installed the official lineage, seems to work except it's not seeing my sim card. Any idea if your build will fix that issue?
edit: reflashing fixed sim issue.
Thanks for any help/info!
Click to expand...
Click to collapse
Sorry, looks like Android file host is having problems. I uploaded them to my google drive and updated the links where you can download. As far as your sim card. I have Verizon and don't have such issue. What is your carrier? All I can say is to try it and find out for yourself. I don't have other carriers so I really couldn't answer that question. Also, make sure you are factory resetting when coming to this build. My signature keys are different from the other Lineage build and it will not boot otherwise.
Screen call is now working with my latest gapps package.
Due to lack of interest, this thread will be closed and no further updates will be made here. If you want to download this ROM, it will be available on Android File Host at the link supplied in the OP.
TheSayaMan said:
Due to lack of interest, this thread will be closed and no further updates will be made here. If you want to download this ROM, it will be available on Android File Host at the link supplied in the OP.
Click to expand...
Click to collapse
Thread closed on request of OP @TheSayaMan

Question Asus zenfone 8: How to rollback from LineageOS to original ROM ?

Hi,
I have successfully installed the LineageOS and it's been working fine.
Now I need some apps that depended on Google Services (Spying services),
How can I rollback to original Asus ROM without a need of a computer, can I do that with the Recovery mode using the Bootloader (Power button + Volume UP) then select reset to factory setting ?
Or
How to properly install the GApps without using a computer ? can I download it as APK and install it ?
Appreciate your help!
Adam
Wich recovery did you have installed? With TWRP you can download gapps package on internal memory and flash it, not sure if it's possible with LOS recovery
I've used the LineageOS recovery. Not the TWRP.
Is there gapps package for lineageOS ? How usually it is installed ? like a normal APK or it needed to be flashed as a ROM(LieageOS+GApps) ?
I have successfully installed the LineageOS and it's been working fine.
Now I need some apps that depended on Google Services (Spying services),
Click to expand...
Click to collapse
How can I rollback to original Asus ROM without a need of a computer, can I do that with the Recovery mode using the Bootloader (Power button + Volume UP) then select reset to factory setting ?
Click to expand...
Click to collapse
I doubt that you can rollback without using a PC (how did you install the LineageOS without a Computer?)
The Android OS images from ASUS for the Zenfone 8 can be downloaded from here:
https://www.asus.com/de/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_BIOS/
In principal it should be possible to install them using fastboot commands or a recovery from one of the CustomROMs or TWRP (https://twrp.me/) but in my tests most of the time that did not work.
Therefor I recommend using a raw image to reinstall the Android OS from ASUS like described in this thread:
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
Note that installing a raw image will wipe all data on the phone!
The raw image for Android 13 for the ASUS Zenfone 8 is the image for the beta version of Android 13 on this page:
https://www.asus.com/Content/Android-13-Beta/
After the installation of the Beta image you should install the official Android 13 using the current Android 13 OS image for the Zenfone 8 from this page:
https://www.asus.com/de/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_BIOS/
The raw image for Android 12 for the ASUS Zenfone 8 can be found here (at the bottom of the page):
https://www.asus.com/Content/Android-13-Beta/
The raw image for Android 11 for the ASUS Zenfone 8 can be be found here (at the bottom of the page):
https://www.asus.com/Content/Android-12-Beta/
After the installation of one of the raw images the installation of the current version of the Android OS from ASUS via the "normal" method is strongly recommended.
How to properly install the GApps without using a computer ? can I download it as APK and install it ?
Click to expand...
Click to collapse
GApps are partially system apps and must still be installed while the Android OS is not running (e.g. while booted from a recovery like TWRP)
If you do not really need all the Google apps but only the Google Stack to get an application runnnig you could test if MicroG (a replacement for the Google Stack; see https://microg.org/) is sufficient for your application. MicroG seems to be a bit outdated but it isn't -it's still working fine.
I use it on my phone to be able to use Apps that require Google functionality but without installing the Google Stack (and some of the Google Apps I like for example Google Maps)
To use MicroG either install a CustomROM with MicroG already included like the LinegaOS with MicroG (https://download.lineage.microg.org/sake/) or (my prefered ROM) the OmniROM with MicroG (https://dl.omnirom.org/zenfone8/).
Or install the MicroG packages on your LineageOS either manually (not recommended) or using an installation image for MicroG like for example NanoDroid (https://nanolx.org/nanolx/nanodroid/). One advantage of NanoDroid is that it also contains a patched Playstore that does work with MicroG.

Categories

Resources