Database Info

[ROM][NZH54D][2023/04/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP

This thread is about installing and using AOSP 7.x (Nougat) ROM for the ASUS Nexus 7 Grouper / Tilapia devices.
Asus - Model names
Grouper = Asus Nexus 7 2012 WiFi
Tilapia = Asus Nexus 7 2012 3G
Initial Setup Installation
Update Recovery to TWRP 3.6.2-9 for Grouper resp. TWRP 3.6.2-9 for Tilapia
Boot into Recovery
Factory Reset (only needed if you are not already on Android 7.x AOSP)
Install 7.1.2 Grouper OTA-Package (Build 20230418) (MD5: 3abdfef56c75cc171fce1c4ffd7a17a8)
or
Install 7.1.2 Tilapia OTA-Package (Build 20230418) (MD5: fc7a5bc81587dba848b37bd62e6166b9)
Reboot into recovery
Install Open GApps (arm/7.1/pico)
(if you have issues regarding the size of the GApps please refer to the next post)
[*]To get root access, I suggest to use either Magisk (V21.4) and Magsik Manager (V8.0.7) the "old" version of Magisk, or the new unified Magisk (V26.1) which can be flashed by TWRP, too. Probably you'll need to rename Magisk-v26.1.apk to Magisk-v26.1.zip
I was not able to flash Magisk 24.x by TWRP / direct install, nevertheless the patching boot.img method worked. For that you need to extract the boot.img from the OTA and transfer it to your devies. Then you need to patch the boot.img and transfer it back to your PC. Finally you can flash the patched boot.img using fastboot.
For detailed instructions please consult the Magisk threads here in XDA.
Do not install Magisk on initial setup as it might lead to issues. Start the ROM without having root access the first time and install Magisk in a second step.
If you are already on Android 7.x AOSP, it's sufficient to do the follwowing steps:
Update Installation
Boot into Recovery
Install 7.1.2 Grouper OTA-Package (Build 20230418) (MD5: 3abdfef56c75cc171fce1c4ffd7a17a8)
or
Install 7.1.2 Tilapia OTA-Package (Build 20230418) (MD5: fc7a5bc81587dba848b37bd62e6166b9)
Reboot into recovery
Install Open GApps (arm/7.1/pico)
(if you have issues regarding the size of the GApps please refer to the next post)
Wipe cache/dalvik-cache (optional, but suggested)
reboot
Important: For more detailed installation instructions please refer to the next post
Important: First boot after upgrading will take a bit longer (stays on ANDROID) because of art optimizations
flash and use on your own risk!
CREDITS,
AOSP/Google, LineageOS, Ziyann for setting up the Grouper-AOSP repository and his Unlegacy Android project, daniel_hk for some hints how to get the 3.1 kernel running with N, timduru for his work on the Asus Transformer, Timur Mehrvarz for his work on the tegra kernel, Francisco Franco for his kernel work in general
Bugs:
please report
Latest Changes
20230418(AOSP 7.1.2)
security fixes for January / February / March and April
Latest version with MicroG-patch applied to them:
aosp_grouper-7.1.2-mg-ota-20230418.eng.ds.zip (MD5: ccfd0b77ca5d2bc8bf98a530737158ba)
aosp_tilapia-7.1.2-mg-ota-20230418.eng.ds.zip (MD5: f91a7ac97aae3b724612980848fed342)
Changelog
Please refer to the changes found in the github repos
All ota packages can be found here:
AndDiSa ROM files repository
Sources
https://github.com/AndDiSa
If you would like to build from the sources, you can do so by cloning and build from repositories:
repo init -u https://github.com/AndDiSa/platform_manifest-Grouper-AOSP.git -b ads-7.1.0
repo sync (... and go out for lunch ...)
. build/envsetup.sh
lunch 7 / 8 / 9
make / make otapackage
but please take in mind that you need to have some free space (>= 100 GB) and some time ...
XDA:DevDB Information
Android 7.x AOSP, ROM for the Nexus 7
Contributors
AndDiSa
Source Code: https://github.com/AndDiSa?tab=repositories
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-09-23
Last Updated 2021-12-09

Please note:
the system partition is already quite full which leads to the problem that gapps probably will not install correctly and that may lead to weired problems (apps closing / not showing up correctly / ...). I suggest to use the dynamic gapps package linked above. In addition I suggest you to erase the system partition completely before applying the OTA package
If you get "Error 7" when trying to flash the ROM directly after upgrading to TWRP 3.5.2-9, wipe the Boot, System and Cache partition and clean dalvik-cache, then re-boot to Recovery and try again (you will not loose any data as long as you do not wipe the Data partition).
If you get "Error 70" when installing GApps copy the attached gapps-config files into the same directory where the gapps installation packages is copiedI.e. something like
/sdcard/open_gapps-arm-7.1-pico-20210922.zip
/sdcard/gapps-config-tilapia.txt
/sdcard/gapps-config-grouper.txt
and then try to start the installation again. Error 70 should be fixed.
Some additional hints
If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
Code:
adb reboot bootloader
After a few seconds the device should show up the bootloader screen

Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?

Nintonito said:
Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?
Click to expand...
Click to collapse
Why not figure it out by yourself?
If you flash this ROM you can create a list of what's working and what's not [emoji6]
Anyway, when I'm home, I gonna flash this ROM on my brother's Nexus 7 and give feedback. [emoji4]
Sent from my Nexus 5 using XDA-Developers mobile app

Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!
View attachment 3884176
View attachment 3884177
View attachment 3884178

Thanks, I'll correct the link
Nevertheless your problems I cannot reproduce ... probably because I've done an update installation. I'll have a look at it.
What was the ROM you have had installed before? Did you wipe?

When i get a chance this weekend I'm going to try this with Phh Superuser and Magisk. That combo is/was working great on your MM rom.

I flashed your ROM with TWRP 3.0.2-0 and after 'Patching system image uncondinionally' i get
Code:
Patching system image uncondinionally...
E:unknown command [log]
E:unknown command [log]
script succeeded: result was [1.000000]
Updating partition detail...
...done
I doublechecked the md5 of the file and reflashed but still no luck.
[Edit]
I rebooted and it seems to run....
[Edit2]
Flashing the plain ROM without the gapps seems to work - but after these gapps it doesnt start.

I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx

tpuserhp said:
I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx
Click to expand...
Click to collapse
I can connect my grouper to my PC and enter adb reboot bootloader command. But I'm not sure what to do next to fix the cache error in recovery. Any suggestions? Thx
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
DSTear said:
Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!
View attachment 3884176
View attachment 3884177
View attachment 3884178
Click to expand...
Click to collapse
Hi @DSTear, I'm running into the same problem on the cache partition as you. I'd appreciate if you could share your method on fixing the cache error in advance. Thx
I was managed to restore the backup and install twrp again.
I think I will retire my grouper on MM now.

As I can see, there are two main problems you ran into:
- you are using f2fs for cache and / or data and the version of twrp you are using is not supporting that file type
- you are flashing gapps / SuperSU /... but the space on /system is not sufficient
I'll update the OP to make aware of those possible issues and give some hints how to prevent them.
Sent from my Nexus 7 using XDA-Developers mobile app

AndDiSa said:
As I can see, there are two main problems you ran into:
- you are using f2fs for cache and / or data and the version of twrp you are using is not supporting that file type
- you are flashing gapps / SuperSU /... but the space on /system is not sufficient
I'll update the OP to make aware of those possible issues and give some hints how to prevent them.
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm not using f2fs. I issued a mount command and did not find any f2fs hits. Not sure why I am getting those msgs. Odd.

I've updated the installation instructions in the OP / second post
I've added some hints, too, how to get out of bootloops, if you encounter such situations.

tpuserhp said:
I can connect my grouper to my PC and enter adb reboot bootloader command. But I'm not sure what to do next to fix the cache error in recovery. Any suggestions? Thx
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
Hi @DSTear, I'm running into the same problem on the cache partition as you. I'd appreciate if you could share your method on fixing the cache error in advance. Thx
I was managed to restore the backup and install twrp again.
I think I will retire my grouper on MM now.
Click to expand...
Click to collapse
Hi. It's quite simple to fix that. Just connect your device to computer, then start bootloop. You will able to fix it using ADB:
Code:
adb reboot bootloader
And after that format your cache partition:
Code:
fastboot format cache
And reinstall TWRP just in case:
Code:
fastboot flash recovery [twrp img for your device]

Bluetooth is not working.
Could Restart be added to the shut down menu please?

Bluetooth will be fixed with the next release.
Sent from my Nexus 7 using XDA-Developers mobile app

difference to
http://forum.xda-developers.com/nexus-7/development/rom-naosprom-nexus-7-2012-t3467335

hanschke said:
difference to
http://forum.xda-developers.com/nexus-7/development/rom-naosprom-nexus-7-2012-t3467335
Click to expand...
Click to collapse
Bluetooth isn't working.
*SCNR*

I want Restart menu.
Next time
Please Support Restart menu.

AndDiSa said:
Some additional hints
If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
Code:
adb reboot bootloader
After a few seconds the device should show up the bootloader screen
Click to expand...
Click to collapse
I'm having the same bootloop issues when trying to go to recovery after my rom is installed. After adb reboot bootloader I have to flash twrp to fix that.
Do you maybe know what can cause this issue?
For the bluetooth I saw you already applied the fix to your source

[ROM][UNOFFICIAL][Oreo 8.1] AOSP Extended for Mi Mix (lithium)

I was quite disappointed to find that my favourite ROM from my old phone was not available for the Mi Mix. So I took some time to research how to compile roms and built this for the community to enjoy.
Download AEX v5.8 here: https://www.androidfilehost.com/?w=files&flid=285169
EAS version with pepsy kernel: https://androidfilehost.com/?fid=1322778262904030327
Recommended TWRP here: http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img
Sources:
https://github.com/AospExtended
https://github.com/PsyMan47/Pepsy-Kernel
https://github.com/PsyMan47/lithium
https://github.com/PsyMan47/msm8996-common
Requires global firmware 8.8.30. Nano Opengapps is recommended, but has Webview patches so you can install any version you like.
Everything works as it should, but unfortunately I'm no developer and won't be able to do feature requests or fix bugs. That being said, if and when the main AEX code base gets updated I will provide new builds. This was mainly a project for me to learn a bit more about Linux, Github and Android in general and I provide this with no guarantees of anything.
Big thanks to Psy_Man for his device tree that enabled me to build this.

Another great rom is revived!

New build with webview patches, you can now install whatever version of opengapps you like
https://www.androidfilehost.com/?fid=1322778262903988659

Inkypen said:
New build with webview patches, you can now install whatever version of opengapps you like
https://www.androidfilehost.com/?fid=1322778262903988659
Click to expand...
Click to collapse
Noice, thanks for your efforts.

Had anyone tried this?
Is everything working?
How is the battery life?

sexlord89 said:
Had anyone tried this?
Is everything working?
How is the battery life?
Click to expand...
Click to collapse
it's working good according to some users who've tried it.

New version up, last build had some random intermittent bugs. This new version uses the same kernel as the official SD821 aex roms, so everything works exactly like official version. This has on screen nav bar by default so no messing around with settings. Nano opengapps is recommended, but has webview patches you can install any version you like.
https://www.androidfilehost.com/?fid=1322778262903989778

Can anyone tell me DOES Magisk and SystemLess Xposed Work on this rom?

I use Magisk myself, works fine. I don't use Xposed so I have no idea

Wowwwwzer nice and smooth..so far so good !! Thanks ,!!!:??

TWRP Error code 7 happened...
Why it need MiUi to install?

00hobin said:
TWRP Error code 7 happened...
Why it need MiUi to install?
Click to expand...
Click to collapse
Hi there,
I don't understand your question "Why it need MiUi to install?".
But here's the suggestion, flash this twrp and try again : http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img

heindrix said:
Hi there,
I don't understand your question "Why it need MiUi to install?".
But here's the suggestion, flash this twrp and try again : http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img
Click to expand...
Click to collapse
This time error code 6 happened. I attached log file

Error code 7 is assert error (device does not match) in installer script, usually down to incorrect TWRP version. Error 6 is some other error in installer script, unfortunately your attached recovery log is no longer available. Does your device have MIUI installed or you coming from a different ROM?

Inkypen said:
Error code 7 is assert error (device does not match) in installer script, usually down to incorrect TWRP version. Error 6 is some other error in installer script, unfortunately your attached recovery log is no longer available. Does your device have MIUI installed or you coming from a different ROM?
Click to expand...
Click to collapse
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI

00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
Coming from CrDroid Oreo and using latest twrp (the one by raupe and blunden which file name ends with updated or some such) you should have no trouble...

00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
It makes no sense, if you already have crdroid installed then all the messy parts of getting rid of MIUI has already been done. If you reinstall MIUI, then it automatically encrypts storage and you will have to format (not wipe) data to move to a different ROM.
Best thing I can suggest is to wipe (not format) everything apart from internal storage. Then reboot into recovery and then try to install the ROM. I suspect error 6 might have something to do with not being able to mount /vendor partition. Make sure you have the updated raupe+blunden TWRP, I believe the official version doesnt mount /vendor as well as having touch screen issues with some variants of mi mix.

00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash all files you want to flash -> Throw the phone as far as you can -> BOOM

Inkypen said:
It makes no sense, if you already have crdroid installed then all the messy parts of getting rid of MIUI has already been done. If you reinstall MIUI, then it automatically encrypts storage and you will have to format (not wipe) data to move to a different ROM.
Best thing I can suggest is to wipe (not format) everything apart from internal storage. Then reboot into recovery and then try to install the ROM. I suspect error 6 might have something to do with not being able to mount /vendor partition. Make sure you have the updated raupe+blunden TWRP, I believe the official version doesnt mount /vendor as well as having touch screen issues with some variants of mi mix.
Click to expand...
Click to collapse
Problem solved.

New version up with September security update: https://www.androidfilehost.com/?fid=1322778262903998959

[GUIDE] Havoc P and other P GSI with anykernel2 8.1 to P boot patch [temp]

First things first
1. Remove all pattern, fp, face data and BACKUP all Partition in TWRP ( I lost baseband trying GSI images, those backup saved me).
2. TWRP should be installed and also Force disabled Encryption should be flashed.
Now follow the steps
1. Go to TWRP, wipe dalvik/cache, cache, system, data
2. Go back and Flash HavocP system image as System or you can try other P GSIs..
HavocP-arm64_aonly_vanilla_nosu-0830.zip
( You can check the source here for updates).
Optionally you can flash arm64 Gapps 9.0 (nano or micro is recommended) opengapps.org
3. Next without exiting TWRP flash this zip, this one patches boot for Android P GSI image compatibility..
POST-sGSI_3_v0.5.zip
4. Now go to wipe menu and wipe Dalvik/cache, cache, data and reboot.
For audio distortion fix:
[Temp] How-To Fix Audio distorted on P GSIs
For Volte: not found any fix yet, but may be fixed by tweaking build.prop like some other devices.. Will add if found.
May this line be added in Vendor/bin/init.qcom.sh like One plus 3.
Code:
# Hack to get IMS up and running on GSI
if [ -f /data/system/users/0/settings_global.xml ]; then
sed -i 's/"multi_sim_data_call" value="1"/"multi_sim_data_call" value="-1"/g' /data/system/users/0/settings_global.xml
restorecon /data/system/users/0/settings_global.xml
fi
This thread is temporary.. Will close it if stable Havoc is released by the Devs
Credits- skulshady, zenixxx, erfanoabdi, EnesSastim, phhusson, SH1M4BD

Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!
EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized
Regards.

Please test multitouch issue, if it exists in this rom.

NexusPenguin said:
Hi,
Thanks a lot...
Will try that and report if it worked for me
Hope the back up won't fail on me !!!
EDIT : tried to do exactly as you said...
It may be worth mentioning a thing or two...
1°) that you should install GApps also...
2°) that it takes some time for the device to get out of the "Pocophone" splash screen
3°) that it may take some time until the SIM card is recognized
Regards.
Click to expand...
Click to collapse
1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.
In short, these GSIs are not stable.
shailendra1993 said:
Please test multitouch issue, if it exists in this rom.
Click to expand...
Click to collapse
Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..

palbadi said:
1. Oh sorry opengapps is released officially , updating op..
2. If pocophone splash screen is stuck, force reboot. Booting is fast for me just like stock rom. That stucking happened once in Havoc, rebooting solved.
3. For me sim detection and registration was fast with Jio 4G and Airtel.. BTW I am sure there is conflicts in Modem and OS (this caused baseband 'unknown').. So sometimes it may some time for sims to get recognized or even not be recognized after booting.
In short, these GSIs are not stable.
Are you telling about that Ghost touch??? I am now back to stock.. Will test that when I will flash again..
May be software glitch..
Click to expand...
Click to collapse
No, the multitouch bug, ghost touch is different.
Check this out: en.miui.com/forum.php?mod=viewthread&tid=3746297

palbadi said:
1.
In short, these GSIs are not stable.
Click to expand...
Click to collapse
Hi,
Same impression here : Treble needs a lot more work to deliver what Google is aiming at !
I now understand why some ROM devs do not want to release GSI ROM images
Regards.

If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.

Technical said:
If I wipe system before flashing Havoc image, I cannot flash gapps P (as it seems to be "seeing" the other slot even on oreo).
If I do not wipe system, I can follow the steps and boot Havoc. But an error message appears: "Android System: There is an internal problem with your device. Get in contact with your manufacturer to know the details". Each boot, same message.
Click to expand...
Click to collapse
It is due to mismatch of ro.vendor.build.fingerprint value in build.prop in System and Vendor..
FIX:
1. Connect data cable to PC and boot into twrp
2. Go to Advanced/file manager
3. Copy build.prop from both Vendor and System to Sdcard, so that you copy them to your PC and edit.
4. In PC, Copy those build.prop files from sdcard and change the value of ro.vendor.build.fingerprint from build.prop (system) to build.prop (vendor).
5. Now overwrite the edited build.prop (vendor) to Vendor in the same process and you may give permission 644 (rw-r--r--) that vendor/build.prop
6. Reboot and check

What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.
I don't see the point.

SmallTarzan said:
What's the point of flashing the postGSI fixes, when it, at least for me and for my guide, works well without them.
I don't see the point.
Click to expand...
Click to collapse
Havoc did not boot without that zip

[GUIDE] TREBLE on Moto Z All variants for dummies [GSI][TWRP][ROOT][PLAY SERVICES]

Hi everyone!
I present to you the practical and simple guide special for dummies that will allow you to try and use the wonders of google treble project in our beloved Moto Z [Griffin has no official support but...] thanks to the great work of the highly recognized developer @erfanoabdi we can enjoy project treble in an easy way [*could apply user restrictions] in our griffin.
*First of all, this guide is designed for those who are curious and have a high degree of autonomy when they try to solve low level or common problems of the Android system. You dont need to be a developer but you must have experience in using and applying the following words: unlocked bootloader, ADB and Fastboot basic commands, Lineage OS, TWRP, Magisk , Back to Stock, Frustration, No "daily driver user" or maybe according to your needs, contribute to general knowledge, dont demand from me more than here is already here because I'm not a developer, I'm just a curious user who likes to try new things in his griffin and I have already given you more than 168 hours of trial and error with the only goal of making the process easier and more fun to you.
Now let's go to what interests us, do you have your bootloader unlocked?
If the answer is no, go here and do it or you can not continue
First we start with the files that we need to download:
Latest Lineage OS from here:
https://download.lineageos.org/griffin
[Thanks to Erfanoabdi]GSI image of your favorite flavor from here:
https://mirrors.lolinet.com/firmware/gsi/
Only type A not AB just A like ColorOS-Aonly-9-20190605-ErfanGSI.img.7z not ColorOS-AB-9-20190605-ErfanGSI.img.7z and decompress the .7z file to get the IMG file inside.
To decompress the .7z file
https://www.7-zip.org/download.html
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
Official TWRP from here:
https://dl.twrp.me/griffin/twrp-3.3.1-0-griffin.img.html
Latest Stable Magisk from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Thanks to @topjohnwu
Magisk module "Device Spoofing Tool" from here:
https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435
Thanks to @Dreamer(3MF)
Device ID apk from here:
https://androidfilehost.com/?fid=673956719939830832
Latest Android System WebView APK from here:
https://www.apkmirror.com/apk/googl.../android-system-webview-76-0-3809-36-release/
Finally put this on favorites because you will need it for the final touch:
https://www.google.com/android/uncertified/
Only if you have all those files downloaded and placed in your PC in the folder that you want you can continue.
Now the easy way step by step if you are on Official Stock ROM:
1 - Reboot to Bootloader and flash twrp-oemasvendor-2.img you can use ADB and fastboot of the .rar adb-fastboot-latest.rar that you ¿downloaded? from the back to stock link
Use
Code:
fastboot flash recovery twrp-3.3.1-0-griffin.img.img
Hard-reboot to bootloader again, down two steps and select reboot to recovery.
2 - Already in TWRP do this:
2.1 - Wipe Data - if it gives you error go reboot and select reboot recovery and again wipe data it should have been erased without errors, back and
2.2 - Manually wipe caches, system, vendor, data, internal storage
2.3 - Do "Swipe to Factory Reset" probably not necessary but for me it works.
3 - Now connect your Griffin and copy the Lineage OS ROM downloaded [obviously still inside of TWRP]
3.1 Go to Install and select the copied Lineage ROM and then install
3.2 Finished the installation restart and skip all startup, now in the launcher screen shutdown your griffin
4 - Power on your griffin again in bootloader, two steps down and select reboot recovery again.
4.1 - Now in TWRP copy the GSI type A image that you downloaded [MIUI, ColorOS, OneUI, Pixel, Flyme OS, etc)
4.2 - Allready copied go to Install and select "Install Image"
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, clear cache and restart to System.
5 - Be very patient, you will see the warning image for having your bootloader unlocked for 5 to 10 seconds [may vary] then you will see the start animation according to the GSI image that you will select before, again be very patient it can take 3 to 15 minutes to your griffin to start completely (MIUI 3-5 minutes, Pixel 3-5 minutes, OneUI 5-10 minutes, Flyme 15 to 20 minutes in my experience) If you see that the start animation reduces its brightness after a few minutes, it means that we are on the right track wait a little longer.
5.1 - Finally we start system we enter directly without previous configurations (configure wifi, google account, PIN, etc) just start screen now go to step 6, if not then go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
And start again
6 - Ok you are one of those who managed to install and start their GSI image and you dont have google services enabled and your griffin is not certified you probably have app errors that crash infinitely [if they are 1 or 3 - example the camera] manage to go to app administration in the ROM and cancel auto-start of that apps, instead if you have so many apps errors that dont let you move anything in the interface you need to go to TWRP and clean davlink cache and cache and reboot.
That's why this step is important
Code:
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, [B][COLOR="Red"]clear cache and restart to System
[/COLOR][/B].
7 - Now Root your griffin with Magisk, you know how otherwise I dont know how you got here
8 - Already in system, install the "Device Spoofing Tool" magisk module and reboot to activate the module.
9 - Again already in system, install Device ID APK
9.1 - Open Device ID app and find your device’s GSF (Google Service Framework) Device-ID
9.2 In your PC go HERE and use your GSF to register and certify your griffin
10 - Now install Android System WebView APK
10.1 - Go to TWRP again and clean cache one more time and reboot to system
11 - Configure your google account and be happy
11.1 - Camera its a common fail, use Gcam or Snapdragon Camera instead of GSI stock camera app
12 - Enjoy your griffin :highfive:
Well that's all from me and remember if something goes wrong or it does not work you can always go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/mot...mware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
The 99.99999999 percent of all this, maybe more, it's thanks to @erfanoabdi If you want to thank someone, buy a coffee for him.
Screenshots (sorry just from MIUI with my emotion I forgot to save from the other GSI that I proble) I feel comfortable with MIUI and now it is my ROM-GSI of daily use in my griffin (I really love taking screenshot with my three fingers )
https://ibb.co/bmDkRrz
https://ibb.co/HX3mghC
https://ibb.co/10jGLNr
https://ibb.co/jz6njXm
https://ibb.co/vv1Nr2F
https://ibb.co/9Gr29nv
https://ibb.co/qsZ2pFD
https://ibb.co/948H110
https://ibb.co/42nXM72
https://ibb.co/Jd73QwC
https://ibb.co/vVs15Hq
https://ibb.co/MVfptZ5
https://ibb.co/SywLwrW
https://ibb.co/ZXvg0QG
https://ibb.co/z8DF8L1
https://ibb.co/bBv1wxW
https://ibb.co/09nBnHW
Finally dont be mad with my english, itis very bad and I use translator

Thanks for guide, very cool
Official TWRP is updated with treble support BTW

Nice ,thanx to your contributions.

whats the waiting time for the moto image? ive installed the moto image, and still waiting for the device to bootup. its been about 15 mins
---------- Post added at 07:46 PM ---------- Previous post was at 07:25 PM ----------
after installing the image, im stuck on this (device will boot in 5 seconds screen) Can i boot back into recovery, and re install the image? its been more than 30 mins on this screen

Pixel image is the only one I managed to boot, but couldn't get gsf id from it, and it constantly force closed (cache was cleaned) and couldn't make it work at all. Moto image just gives black screen, all other images couldn't even be installed (either error in twrp or something else.) I'll try miui image one of these days, but would really like to try to make pixel image work, but without gsf id it's impossible
EDIT: Changed twrp to twrp-oemasvendor-2.img version, and managed to boot miui (but after magisk it bootlooped) and to start booting moto GSI images (moto bootloops), and just tried to boot pixel images, will see later... but I think that the problem was that twrp uses cache as vendor partition, and deleting cache, well, deletes vendor partition (will need clarification from @erfanoabdi on this)...

Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?

anwesh said:
Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?
Click to expand...
Click to collapse
Nop, Omni does not have the type of partition needed

After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...

anwesh said:
After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...
Click to expand...
Click to collapse
Go to TWRP and make full wipe factory, that fix the problem

I've been hunting down and trying out some different gsi's. With the latest twrp + los16 installed I've had success with some from this list
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
AOSP 10 with gapps included
Msm xtended gapps included
Blissrom + gapps
Aosip + gapps
EvolutionX gapps included
DU13 + gapps (not on list but works)
If installing gsi's without gapps included, let it boot first then reboot TWRP and install gapps + magisk if you want root.

Available kernel ?

I cannot retrieve the GSF id, how can I fix this?

Flashed OneUI GSI but it's stuck on the boot logo

So on my Moto Z running LineageOS 17, I can't launch Netflix on it. Will Treble-ing my Moto Z fix that problem?

This also works on moto z force?

[ROM][T525][UNOFFICIAL] LineageOS 17.1 | Android 10.0 Q 20210419

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
- video record
Links
5. 20210419: april security patch: https://drive.google.com/file/d/1aXGrtLrmqAQEYMxcvzck9hJOd-f4OVke/view?usp=sharing
4. 20201220: december security patch: https://drive.google.com/file/d/1KMqFHfDORMCsNXGSrpWkh5IIZp1ZN5oJ/view?usp=sharing
3. 20200815: august security patch: https://drive.google.com/file/d/1oVmXeSfa7p9d4L2nSmiigCjNCo60So7n/view?usp=sharing
2. 20200724: july security patch: https://drive.google.com/file/d/15_4QTR5vKMRvIwXevu1QYb3WHMZsCW72/view?usp=sharing
1. 20200616: initial build, june security patch: https://drive.google.com/file/d/1is2tRwqsd7Nm9dhpkPrGbpgg7AjnOkZh/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Recovery
this is my build, the error with the screen off is still present, but I added an option for twrp with unlimited screen timeout, as a result, the screen does not automatically turn off.
for recovery: https://drive.google.com/file/d/1UeC4LwVEA6d46y0UPpuuipHbcjAtAo0Q/view?usp=sharing
for odin: https://drive.google.com/file/d/1WmAzhWkq9l_3d4m3Ft1xmihZaYfccUym/view?usp=sharing
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_picassolte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_picassolte

Thank you for this build.
Does anybody else have the problem that picture-in-picture mode is not working?
I'm watching a video with the German sky go app. Pressing the home button takes me to home screen and does not show the video in the small window.
This was working with the Android 9 build.
The permissions are set for the app.

Thank you for this version.
Warning: I initially tried with GApps Stock (like I did with 16.0) and it totally messed up the system (Pixel Launcher crashed constantly, attempting to log in to Google account resulted in a black screen). Now, with Pico, it seems to work alright.

deleted

Can i use a t525 rom to my t520 tablet? I mean, its the same tablet but without lte? If not, pls make a android 10 rom for the t520 tablet

Tabletbungie said:
Can i use a t525 rom to my t520 tablet? I mean, its the same tablet but without lte? If not, pls make a android 10 rom for the t520 tablet
Click to expand...
Click to collapse
T520 is not just T525 without LTE. T320, T325 and T525 have Qualcomm Snapdragon SoC's inside, so most of the codebase can be shared between them. T520 has Exynos which is quite different.

help
i had an error
it says
unknown command [retry_update]
Updater process ended with ERROR: 7
What i should do?
please help me

Just updated to 20200724 with GApps Pico, Magisk and Viper4Android. Nothing out-of-the-ordinary stands out, so in all regards this appears to be a safe upgrade.

в прошивке - LineageOS 17.1 | Android 10.0 Q 202007 24 (Samsung Galaxy Tab Pro 10.1)
не работает (функция не доступна) - поверх других приложений
Valera1978 - обратите внимание на проблему! исправьте пожалуйста!
....
in the firmware - the Lineages of 17.1 | Android 10.0 Q 2007 24 (Samsung Galaxy Tab Pro 10.1)
does not work (function is not available) - on top of other apps
Valera1978-pay attention to the problem! please fix it!

I tried to flash lineageOS 17.1 & 16 but got this error in attachment
What's wrong

Witzker said:
I tried to flash lineageOS 17.1 & 16 but got this error in attachment
Click to expand...
Click to collapse
Maybe try this?

M0lle said:
Maybe try this?
Click to expand...
Click to collapse
THX for taking care but it was my fault
I have not red carefully the instruction for recovery
I had an old version
Now installed the recommended one
for recovery: https://drive.google.com/file/d/1UeC...ew?usp=sharing
Here I have another question
when I go to TWRP -Install Choose the TWRP zip I only installed image not the Option Boot.
Was This OK?
TWRP is starting correctly and I have successfully flashed the image of June (1) & PICO.
BUT I have NO sound!!
How do I install the updates?
Links
3. 20200815: august security patch: https://drive.google.com/file/d/1oVm...ew?usp=sharing
2. 20200724: july security patch: https://drive.google.com/file/d/15_4...ew?usp=sharing
1. 20200616: initial build, june security patch: https://drive.google.com/file/d/1is2...ew?usp=sharing
Just flashing the latest (3) over the old
or flashing the next update (2) then the latest (3)
OR wipe and flash the Latest (3) ?
PLS Help again
THX

Witzker said:
How do I install the updates?
Click to expand...
Click to collapse
Wipe Art/Dalvik Cache, Cache and System
Flash the ROM image (the latest one only)
Flash the GApps
(Flash Magisk if you want root)
Reboot to System
Wait...

M0lle said:
Wipe Art/Dalvik Cache, Cache and System
Flash the ROM image (the latest one only)
Flash the GApps
(Flash Magisk if you want root)
Reboot to System
Wait...
Click to expand...
Click to collapse
SO I will lose all my settings?

Witzker said:
SO I will lose all my settings?
Click to expand...
Click to collapse
No, you won't. Data and Internal Storage will stay intact. This is the procedure I follow when I update from one version of e.g. 17.1 to newer one. Only when upgrading to a new major version do I fully wipe the device.
If you're unsure, backup your stuff with "ROM Settings Backup" and "Titanium Backup" before wiping anything.

THX Great worked ok.
BUT still no sound!
How to check if there is maybe a hardware problem?

I'm going to install this Rom (thanks to developer) , is the sound problem real?

alonzimanuel said:
is the sound problem real?
Click to expand...
Click to collapse
I haven't had any sound problems with either 16.0 or 17.1.

Witzker said:
THX Great worked ok.
BUT still no sound!
How to check if there is maybe a hardware problem?
Click to expand...
Click to collapse
My tab also freezes during browsing websites or open other apps!
What can be the reason ?
Are there some settings to change??
PS: I use Microsoft launcher

Witzker said:
My tab also freezes during browsing websites or open other apps!
What can be the reason ?
Are there some settings to change??
PS: I use Microsoft launcher
Click to expand...
Click to collapse
Don't know that launcher (mine Nova Prime) but did you test turning of animations in dev settings?