• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

AndDiSa

Senior Member
Dec 2, 2009
3,549
4,720
Heidelberg
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
  1. Update Recovery to TWRP 3.5.2-9 for Grouper resp. TWRP 3.5.2-9 for Tilapia
  2. Boot into Recovery
  3. Factory Reset (only needed if you are not already on Android 7.x AOSP)
  4. Install 7.1.2 Grouper OTA-Package (Build 20210917) (md5 :e0381d56f4f1c11c095a9d0057c50699)
    or
  5. Install 7.1.2 Tilapia OTA-Package (Build 20210917) (md5: 7a6b6d37b2f8ee5964c8d9164305a846)
  6. Reboot into recovery
  7. 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 (V23.0) which can be flashed by TWRP, too. Probably you'll need to rename Magisk-v23.0.apk to Magisk-v23.0.zip

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 20210917) (md5 :e0381d56f4f1c11c095a9d0057c50699)
      or
    • Install 7.1.2 Tilapia OTA-Package (Build 20210917) (md5: 7a6b6d37b2f8ee5964c8d9164305a846)
    • Reboot into recovery
    • Install Open GApps (arm/7.1/pico)
    • 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
  • 20210917(AOSP 7.1.2)
    • I fixed the crash of the clock application reported by @momentoid
    • I added a missing patch for external/sqlite
    • I applied the security fixes for September 2021
    • I optimized the kernel config settings, especially removed some superflouus settings
    • I applied / backported a bunch of CVE-kernel patches. Please have a look at the sources in Github to see the whole list of changes

Latest version with MicroG-patch applied to them:
aosp_grouper-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 9ea020054cfbe1b646e1c9cdcb11358d)
aosp_tilapia-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 617fbfddc39174fcc0486de8081448e7)


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:
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-03-05
 

Attachments

  • Screenshot_20170403-205552.png
    Screenshot_20170403-205552.png
    106.9 KB · Views: 89,380
  • snoopsnitch-Nexus7-20190309.png
    snoopsnitch-Nexus7-20190309.png
    60.3 KB · Views: 27,369
  • status-Nexus7-20190309.png
    status-Nexus7-20190309.png
    57.2 KB · Views: 27,072
Last edited:

AndDiSa

Senior Member
Dec 2, 2009
3,549
4,720
Heidelberg
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
 

Attachments

  • gapps-config-grouper.txt
    40 bytes · Views: 159
  • gapps-config-tilapia.txt
    40 bytes · Views: 74
Last edited:

Nexive

Senior Member
Feb 12, 2012
317
199
Brussels
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?
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
 
Last edited:

DSTear

Member
Jul 6, 2016
10
8
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!
 
  • Like
Reactions: AndDiSa

adrman

Senior Member
Jul 17, 2012
1,595
632
NYC
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.
 

fred0r

Senior Member
Nov 23, 2011
108
25
Hamburg
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.
 
Last edited:

tpuserhp

Senior Member
Jul 1, 2013
598
219
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
 
Last edited:

tpuserhp

Senior Member
Jul 1, 2013
598
219
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
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 ----------

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!
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.
 
Last edited:

AndDiSa

Senior Member
Dec 2, 2009
3,549
4,720
Heidelberg
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
 
  • Like
Reactions: dark0shark

tpuserhp

Senior Member
Jul 1, 2013
598
219
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
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.
 

DSTear

Member
Jul 6, 2016
10
8
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.
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]
 
  • Like
Reactions: tpuserhp

millosr

Senior Member
Jun 11, 2015
290
827
Belgrade
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

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 :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    New Versions 7.1.2 (2021-10) are available

    Hi guys, a new release but only a few changes, i.e. the security paches for October 2021.
    The full list of changes, as always, you can find in my Github repos

    The "standard" versions for Grouper / Tilapia are available for download:
    aosp_grouper-7.1.2-ota-20211006.eng.ds.zip (MD5: b57ddee37bad03f59e2eff562076b027)
    aosp_tilapia-7.1.2-ota-20211006.eng.ds.zip (MD5: 65ea4ea189a41ec7792fb13a876157da)

    as well as the MicroG-Patched images:
    aosp_grouper-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: d5d788b3fa735c3e57d9f0fb562e15f6)
    aosp_tilapia-7.1.2-mg-ota-20211006.eng.ds.zip (MD5: 643f8fdf2195c2395f788611578c108e)

    I quickly tested the ROM and didn't find issues, nevertheless I will wait for feedback from the community before I'll add the new version to the OP.

    If you report a successful (or unsuccessful :)) installation, please note which version (Grouper / Tilapia, with or without MicroG-patch) you have installed and tested. Thank you very much!
    Stay safe!
    3
    I would advice to flash Magisk through TWRP right after dirty flashing the new ROM version instead of using the Magisk app. This has worked for me without any issue for numerous iterations now. If you do a clean flash, just reboot after flashing the ROM, then go back to recovery to flash Magisk.
    3
    ...The only thing you will loose (ime) is any apps that you have purchased through google - you cannot activate paid-for apps without gplay (and so the entire google framework)
    You can use Aurora Store to download paid apps if you log in via the same account that you have used to purchase those apps.

    If this is too much of a risk for you, there is a somewhat inconvenient workaround for apps that you have purchased via Play Store (not for all apps, but for some). Only thing you need is root plus a root file manager to grab those paid apk's from your /data directory and sideload them to your Google-free device.

    As said before, it works for some apps, but most of the paid apps are tied to your Google credentials and will check if Google services are available and if the correct account is logged in.
    2
    @tomtom_38 officially there are no security patches for Android 7 since about 4 years ago. The security patches applied here are backported from newer Android versions.
    2
    I finally found the time to upgrade from April build and I tried to flash the ROM only, no Micro-G, no GApps.
    I use the device like a monitor for my USB inspection camera so I don't need the G framework at all.
    I added 3 apps from apkpure (Endoscope, Nova 6 and Pixel icon pack) and...they work! :)

    The tablet is very fast and responsive. No more lags at all on the UI.
    Of course I would recommend this solution for those who have a very specific use of the device, like me.

    @AndDiSa do you think that resizing the System partition may help in keeping the device snappy using GApps? How could the difference between GApps and no-GApps be so dramatic?
  • 311
    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
    1. Update Recovery to TWRP 3.5.2-9 for Grouper resp. TWRP 3.5.2-9 for Tilapia
    2. Boot into Recovery
    3. Factory Reset (only needed if you are not already on Android 7.x AOSP)
    4. Install 7.1.2 Grouper OTA-Package (Build 20210917) (md5 :e0381d56f4f1c11c095a9d0057c50699)
      or
    5. Install 7.1.2 Tilapia OTA-Package (Build 20210917) (md5: 7a6b6d37b2f8ee5964c8d9164305a846)
    6. Reboot into recovery
    7. 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 (V23.0) which can be flashed by TWRP, too. Probably you'll need to rename Magisk-v23.0.apk to Magisk-v23.0.zip

    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 20210917) (md5 :e0381d56f4f1c11c095a9d0057c50699)
        or
      • Install 7.1.2 Tilapia OTA-Package (Build 20210917) (md5: 7a6b6d37b2f8ee5964c8d9164305a846)
      • Reboot into recovery
      • Install Open GApps (arm/7.1/pico)
      • 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
    • 20210917(AOSP 7.1.2)
      • I fixed the crash of the clock application reported by @momentoid
      • I added a missing patch for external/sqlite
      • I applied the security fixes for September 2021
      • I optimized the kernel config settings, especially removed some superflouus settings
      • I applied / backported a bunch of CVE-kernel patches. Please have a look at the sources in Github to see the whole list of changes

    Latest version with MicroG-patch applied to them:
    aosp_grouper-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 9ea020054cfbe1b646e1c9cdcb11358d)
    aosp_tilapia-7.1.2-mg-ota-20210917.eng.ds.zip (MD5: 617fbfddc39174fcc0486de8081448e7)


    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:
    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-03-05
    65
    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
    62
    Hi guys,

    first of all I would like to thank all of you for your support you offered to me in the last days and I really feel honoured that so many of your would like to support / help me so that I am able to continue the development for the Nexus 7.
    I've got many offers for a "new" Nexus device from all over the world which I really didn't expect. I was really torn between continuing and stepping out. I've thought very much about pros and cons and it wasn't an easy decision especially if you get so much positive feedback. Thank you again!

    Finally I've decided to stop development for the Nexus 7 (at least for the moment). There are several other projects (not all of them related to Android) I've in mind and probably this now was a broad hint to start with something different. I've uploaded the sources of the ROMs latest version (inc. security patches for June 2019) to Github and tested together with @fidoedidoe whether all needed repos and changes are consistent and that one can build the ROM from those repos without the need of doing additional modifications or patches. The build should run smoothly after synchronizing everything. I will also support and help everybody who would like to step in and continue the builds.
    I know there are several people interested in building the ROM from sources. Probably there is someone (or probably even a group) who would like to continue ...
    Cheers,
    AndDiSa
    55
    2019/02/05 - release for Grouper and Tilapia uploaded

    I've just uploded the latest version of the ROM for Grouper and Tilapia. As always the Android security issues listed in the latest Android Security Bulletin are patched in this ROM.

    Beside that once again I've worked much on the kernel side. Some features are added (multiple binder devices, alarm timer device, ...) and some bugs have been fixed.
    I am still working together with @OlliWi on the slow charging issue which occurs from time to time. Even if I was able to get charging currents up to 1500mA while the device was connected to a charger, we still have the impression that the cable / charger detection needs to be improved. We are on it ...

    Those of you who are familiar with the installation process of the ROM can download directly from here, otherwise please first read the instructions in the OP

    7.1.2 Grouper OTA-Package (Build 20190209) (md5: 885e601a06a2104628a1e450b73f3a18)
    7.1.2 Tilapia OTA-Package (Build 20190209) (md5: 8e4c0e1955ecc0bb65a51582bb01f779)

    And finally as always: flash on your own risk ... ;)
    52
    New year ... new security fixes (2019/01/05)

    Hi guys,

    I've just uploaded a new version of the ROM for our beloved Nexus 7 (Grouper / Tilapia) having the January 2019 security fixed applied to it.

    Beside that I found a bug causing bootloops on initial install / after wiping dalvik. This was caused by zygote not having enough memory available to create the boot.jar on the fly. To fix this issue, I am doing a dex-preopt for the boot image on compile time now which leads to a slightly larger image but improves initial boot time a bit, too.

    To get more memory free on the /system partition, I debloated the ROM a bit, e.g. removed the Browser2, LegacyCamera, Music and Calendar apps as some of them even didn't work fully. There are several alternatives available in several stores which you can install if you need them. Probably most of you do not even notice that these apps were removed.

    Most changes were applied to the kernel. I tested the changes in the last 4 weeks but as I have a Grouper device only and I cannot test each functionality I cannot exclude that something doesn't work as expected. So please file a bug report (best with logcat and a meaningful bug description) if you find some unexpected behaviour and I will have a look at it.

    The most important fix here is probably the improved charging behaviour (many thanks to @OlliWi who provided with fruitful analysis and hints and pushed me to have a deeper look at this issue).
    To get a faster charging of the device, do not boot with a USB cable connected as this prevents the device to charge with more than 500mA (or at least disconnect and re-connect the cable after the device booted).

    I've updated the links in the OP, so you can download the latest version from there.

    Happy new year to all of you!