yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] AndDiSa:
@LesGirauds it's a long time I didn't mess with Magisk especially not with the new Magisk 24.x versions. Probably I should try to get a bit more familiar with it ... 🤔

Edit: Looks as if the ROM in it's current state is not 100% compatible with Magisk 24.x. It finds an additional su binary which is located in /system/xbin/

Edit2: I've got it running. I had to remove the su binary from the system files, e.g. the next builds will not have any longer a su binary included.

Setting Zygisk to true and modifing the device fingerprint by using the MHPC-6.1.2 module root beer doesn't detect root any longer even though Momo is still detecting a custom rom and traces that the environment is abnormal.
[Nexus 7 Android Development] Baonks81:
Magisk-v24.3 can not install in TWRP 3.5.9_2 for grouper standard. But it run smooth
[Nexus 7 Android Development] AndDiSa:
@Baonks81 you need to patch the boot image to get it running. Looks as if Magisk 24.x doesn't support direct installation any longer.
[Nexus 7 Android Development] happy-kat:
Many thanks for this, installed just the grouper rom over a prior flavour of this and it is working great.

Just need to sort out battery charging, probably my battery is just not charging very well.

The battery is now sorted too, removed the battery and I/O connections and re seated, charge speed sorted.
[Nexus 7 Android Development] Baonks81:
I tested tilapia standard file, the new patch work smooth with twrp 3.5.9-2 and magisk 24.1.

New twrp 3.6.0/3.6.1 crash. Magisk 24.3 can not install in twrp. T

Done, thanks for support @AndDiSa
[Nexus 7 Android Development] AndDiSa:
@Baonks81 I also did some installation tests and I was not able to patch the boot image by applying the Magisk-24.3.zip in TWRP on it ... but I was successful in the following way:

- extracting the boot.img from the ota

- patching the boot.img by Magisk-24.3

- rebooting to recovery

- installing the ota

- installing gapps

- rebooting to bootloader (!)

- fastboot flash boot magisk_patched-24300-xxx.img

- reboot

Please note: as the currently published ota (aosp_xxx-20220311.zip) contains another su binary you will get an "abnormal" Magisk environment. Abnormal means it is working, but complaining about the additional binary and wants to re-install Magisk. This will be fixed with the next release.
[Nexus 7 Android Development] momentoid:
Dirty installed Grouper version of 2022-03 ROM with 2022-02-15 GApps (looks like it is not updated since Feb 15). All good except Kindle app on Play Store says the app is "no longer compatible with this device."

Thanks @AndDiSa👍
[Nexus 7 Android Development] colt2x:
Hi,

Thanks for this ROM, i wonder that it is much faster than the previous Lineage 14 ROM which i had (and also with latest security patches :) )

One problem is that USB isstopiing regularly. Even the charging, and the data transfer also. After a reboot, it works for some time, but if i leave the tablet without a charger plugged in for several hours, it surely will not work. This happened with the previous 14.1 unofficial Lineage ROM, but not with 14.1 official, or 15.1 unofficial. Not related to USB mode, as i tried to se it to charge only, PTP, MTP... but nothing changes.

Has anyone the same problem? Or is there a solution?

Thanks in advance :)
[Nexus 7 Android Development] colt2x:
Search for the app on Aptoide or APKpure, and download an older version. Maybe it will work. I have some apps on this way on my 7.1-based devices :)
[Nexus 7 Android Development] happy-kat:
Looks like I may have to reinstall after all, but with first doing a wipe this time as on using the tablet neither Chrome or the Play Store are loading.

Think first I will try adding the google gapps back
[Nexus 7 Android Development] Turtle Trader:
what is OP?
[Nexus 7 Android Development] AndDiSa:
OP = opening post -> first post in this thread
[Nexus 7 Android Development] marty_bebop:
Grouper March MG version.

I see the Magisk issue - but it will be fixed, so that's cool.

All good!

Thanks
[Nexus 7 Android Development] Turtle Trader:
done it thank you, but i got the problem, once i connect to wifi, my device will auto boot, and will never end bootloop

btw what is microG version? what's the difference with non microG?
[Nexus 7 Android Development] AndDiSa:
@Turtle Trader

the standard version supports Google Application Framework (Gapps), i.e. if you would like to use GApps you most likely would use that version

the microg version is the special version prepared to support a framework which tries to provide the Google Application Framework functionality but without all the bloated functionality of it. You can see it as kind of "stripped down Gapps". More information you can find on microg.org

Especially useful for devices which do have only a limited memory.
[Nexus 7 Android Development] Turtle Trader:
Oh ok, then if i use the microG version, its also have playstore or not?

If not, how i can install app and update app?
[Nexus 7 Android Development] colt2x:
@AndDiSa : Can you please check the power/charging issue described here : https://xdaforums.com/t/rom-nzh54d-...s-ext4-android-7-x-aosp.3467514/post-86606373

Thx: )
[Nexus 7 Android Development] metterschling:
You could use an alternate Frontend to the Google app store like Aurora Store or even F-Droid as a free Software app store. If you depend on in-app payment there is a patched Play Store available for MicroG. I found it most convenient to install any of these using Nanodroid.
[Nexus 7 Android Development] AndDiSa:
@colt2x hmm ... I cannot reproduce the issue on my side. Could you please give me additional information, e.g. hardware revision of your device, probably a logcat, dmesg, ...
[Nexus 7 Android Development] colt2x:
Will collect and get back to you :) Thx!
[Nexus 7 Android Development] colt2x:
Dmesg - device is not rooted, but working on it.

HW rev : Nexus 7 2012 wi-fi, E1565 (16GB)

Charger IC is SMB347_INOK

Dmesg when charging

[ 185.141114] healthd: battery l=98 v=4104 t=28.0 h=2 st=2 c=0 fc=3606000 chg=u

[ 185.274454] smb347_charger: [smb347_config_thermal_charging] temp=28

[ 185.274844] smb347_charger: [smb347_config_thermal_charging] Bypass charger enable

Pulled out cable, plugged back

[ 244.453306] android_work: sent uevent USB_STATE=CONNECTED

[ 244.459326] android_work: sent uevent USB_STATE=DISCONNECTED

[ 244.561253] android_work: sent uevent USB_STATE=CONNECTED

[ 244.575073] set_config : usb set config wake lock ++

[ 244.575237] android_usb gadget: high speed config #1: android

[ 244.575453] android_work: sent uevent USB_STATE=CONFIGURED

[ 244.708132] inok_isr_work_function hostmode=00 lastExternalPowerState=00 lastChargeSlaveDevicesState=00

[ 244.708440] cable_type_detect()

[ 244.708602] INOK=L

[ 244.709297] smb347_charger: [cable_type_detect] Reg39 : 0x10

[ 244.709680] smb347_charger: [cable_type_detect] Reg3F : 0xc0

[ 244.709940] smb347_charger: [cable_type_detect] USB_IN

[ 244.710298] Charger: APSD Completed

[ 244.710560] smb347_charger: [cable_type_detect] Reg3E : 0x0c

[ 244.710699] Cable: SDP

[ 244.710838] ========================================================

[ 244.711093] battery_callback usb_cable_state = 1

[ 244.711230] ========================================================

[ 244.712617] elan-ktf3k 1-0010: Update power source to 1

[ 244.712971] bq27541_get_capacity = 98% ret= 97

[ 244.714017] inok_isr_work_function external power available hostmode=00

[ 244.714402] bq27541_get_psp voltage_now= 4110000 uV

[ 244.715456] bq27541_get_psp current_now = 187000 uA

[ 244.716266] bq27541_get_psp current = -187 mA

[ 244.717312] bq27541_get_psp charge_full = 3636000 uAh

[ 244.718350] bq27541_get_psp temperature= 280 (0.1�XC)

[ 244.719856] bq27541_get_psp status: Charging ret= 0x0201

[ 244.720489] healthd: battery l=98 v=4110 t=28.0 h=2 st=2 c=0 fc=3636000 chg=u

[ 245.088044] cable_detection_work_handler(): vbus_active = 0 and is_active = 1

[ 245.088116] The USB cable is connected

[ 245.088226] smb347_charger: [usb_det_cable_callback] usb_det_cable_type=01

[ 245.088292] elan-ktf3k 1-0010: Update power source to 1

[ 245.619205] stop_machine_cpu_stop smp=0

[ 245.619221] stop_machine_cpu_stop smp=2

[ 245.620600] CPU2: shutdown

[ 246.719097] bq27541_get_psp status: Charging ret= 0x0200

[ 246.720846] bq27541_get_psp voltage_now= 4136000 uV

.

.

.

[ 246.743150] bq27541_get_psp status: Charging ret= 0x0200

[ 246.745067] healthd: battery l=98 v=4136 t=28.0 h=2 st=2 c=0 fc=3636000 chg=u

[ 246.913822] smb347_charger: [smb347_config_thermal_charging] temp=28

[ 246.914090] smb347_charger: [smb347_config_thermal_charging] Bypass charger enable

For logcat, what excatly do you need? I have Android studio installed, so i can check logs, but don't know what to search.

The very strange stuff is that not only the charging, but the whole USB seems stopping.
[Nexus 7 Android Development] AndDiSa:
@colt2x thank you very much. I'll look deeper into it tomorrow.

Btw. currently when you connect with ADB you should be able to change to root by su (as it is still included in the current release).
[Nexus 7 Android Development] Turtle Trader:
Oh ok thanks I'll try it
[Nexus 7 Android Development] colt2x:
Do not need to hurry - this is annyoing, but not a serious error :D

Yes, from ADB i can run dmesg, but not from device. (I think it would be not violating security if it would run from the device too, as many Linux distros are allowing dmesg for users :) )I checked Logcat when the USB is failing (there are apps to see logs ) but nothing was there related to charging or USB. Adb devices also does not return any devices. After any reboot, this happens after 2-4 usb plug-unplugs.
[Nexus 7 Android Development] AndDiSa:
@colt2x well, your info you posted above looks quite normal. I cannot detect any issue there. I also repeated the tests following your description (letting it for some time, plug/unplug several times, ...) but my device behaves normal. I.e. the device connects always via usb, there are no issues reported neither on the device logs nor in the PC logs. Probably you can post another log when the issue arrises to get a deeper insight.
[Nexus 7 Android Development] colt2x:
Hi,

Will be difficult as if the device does not charge, th USB completely stops... :D So i could only post the log of normal operation.

Maybe i'll check this while in recovery.

Or i need to root the device to get dmesg of a non-working charging situation.

Anyway, thanks for checking :)
[Nexus 7 Android Development] v0ltax:
i needed to make a clean install: wipe all > format > grouper > gapps > magisk

Works fine for me! Thanks for your support man!
[Nexus 7 Android Development] momentoid:
Thanks for the suggestion. It seems the Kindle app in Play Store stopped giving an error and works now. I do not understand what happened. The app was last updated on Feb 9 and I could not install it on Mar 18.

Anyway, it works now.
[Nexus 7 Android Development] PlsHelpXDA:
Hello AndiSa, thank you for keeping the tabet alive. I want to set it up again and I have several problems. I installed the latest twrp - recovery. Deleted everything from system etc. and wanted to install AOSP and also MG (Grouper) 20220311. ADB doesn't work in recovery and tablet, and I can't play data on the tablet with a cable in recovery either. I can only access it with an OTG cable and install roms. When booting I get the error message that the Louncher keeps crashing (MG/AOSP). What can I do to make the tablet work again?

I hope you unstand my question, sorry for this survival english.
[Nexus 7 Android Development] AndDiSa:
@PlsHelpXDA could you please explain the steps you have done?

If adb is not working there might be some driver issues with your PC, i.e. the device is not detected correctly. What operating system do you use on your PC? What type of USB port? (Sometimes USB 3.x doesn't work as good as USB 2.0). It's a bit difficult to help without detailed information.
[Nexus 7 Android Development] Cyriis:
First of all: Thank you for your great work. Last weekend I found my old Nexus 7 in my bookshelf and currently I try to resurrect it.

My problem: When I try to download the package from androidfilehost I get only this message "OOPS! no mirrors found." (in different browser from the same PC). Am I too late and the file is gone or is this a problem on my PC/network?
[Nexus 7 Android Development] AndDiSa:
As you asked the same question in the LineageOS thread it's most likely either an issue on AndroidFileHost side or even a network issue.

Edit: I just checked and noticed that AndroidFileHost has currently DNS issues

Edit2: works again
[Nexus 7 Android Development] rahimali:
Hi, I've added mirrors for all four ROM variations.

Grouper-MicroG

File links - Mirrored.to - Upload Your files to multiple hosts

Securely upload your files, media and documents to more than 30 cloud storage providers simultaneosuly. Remote Upload files to Google Drive and many other hosts.

www.mirrored.to

Grouper

File links - Mirrored.to - Upload Your files to multiple hosts

Securely upload your files, media and documents to more than 30 cloud storage providers simultaneosuly. Remote Upload files to Google Drive and many other hosts.

www.mirrored.to

Tilapia-MicroG

File links - Mirrored.to - Upload Your files to multiple hosts

Securely upload your files, media and documents to more than 30 cloud storage providers simultaneosuly. Remote Upload files to Google Drive and many other hosts.

www.mirrored.to

Tilapia

File links - Mirrored.to - Upload Your files to multiple hosts

Securely upload your files, media and documents to more than 30 cloud storage providers simultaneosuly. Remote Upload files to Google Drive and many other hosts.

www.mirrored.to

Please download the one that applies to your device.

Thanks!
[Nexus 7 Android Development] PlsHelpXDA:
Hello AndDiSa, thank you for your answer.

I installed the latest twrp version (twrp-3. 6. 1_9-0-grouper. img). In recovery I can't transfer any files USB2/USB3) via USB cable. ADB in recovery doesn't work either (PC linux mint 20.3, adb version 1.0.39 (version 1:8.1.0+r23-5ubuntu2 Installed as /usr/lib/android-sdk/platform-tools/adb)

I can only install Grouper rom via an OTG cable and USB stick (full wipe). When the tablet starts, the louncher always crashes, operation is not possible.

I think the tablet has had its time?
[Nexus 7 Android Development] AndDiSa:
@PlsHelpXDA I do not think that your device has had it's time but that you do not have the correct udev rules installed so that the device is not recognized correctly. Some time ago I did a small blog post about recognizing the Nexus device on OpenSuse 11.4 but the post is still valid for other Linux distributions, too. Beside the mtp connection (which was the origin) you can also see what udev rules nedd to exist that the Nexus is recognized in bootloader / recovery mode.
[Nexus 7 Android Development] Vrpghm:
Hola, istale la actualización nexus 7 grouper, luego no se pudo root, ni con el .zip ni la apk funcionan, se reinstaló 3 veces, tampoco funcionó con la versión anterior de magisk que si funcionó con la actualización aosp anterior del año 2021, es una falla de la actualización de aosp? Traté con iroot tampoco funcionó hacer root

Solo para que estuviera al tanto.

Saludos

Gracias
[Nexus 7 Android Development] AndDiSa:
@Vrpghm please post in English

.. and as I already wrote: you cannot install Magisk directly, you need to patch the boot.img when using Magisk 24.x
[Nexus 7 Android Development] Vrpghm:
Hello, install the nexus 7 grouper update, then root could not be done, neither with the .zip nor the apk work, it was reinstalled 3 times, it did not work with the previous version of magisk 23.0, but it did work with the previous aosp update of the year 2021 , is it a failure of the aosp update? I tried with iroot it didn't work to root either I am using gapps from May 2021 because with more recent gapps it gives error code 70, free space, it keeps giving an error, how do I solve it? Just so you were aware. Greetings Thanks
[Nexus 7 Android Development] Baonks81:
Hello, I found something about touch, when I install brave frontier games. It required DLC touch gestures. What does it mean DLC!? Is it a license?
[Nexus 7 Android Development] G_Bot:
Magisk Canary works.

Magisk Canary works.
[Nexus 7 Android Development] notnoelchannel:
For the transfer issue, try my recovery
[Nexus 7 Android Development] PlsHelpXDA:
Hello, thanks for your answer. I tried your recovery. It is the same, In recovery I can not transfer any files. If I intsall AndDiSa's rom (mg/aosp) the loucher crashed an I can't use the tablet. I think my grouper is out of order
[Nexus 7 Android Development] notnoelchannel:
Did you try using CyanogenMod 14.1? The same issue happened to me in that rom.

Did you wipe Cache, System, Data, Dalvik / ART cache before installing?
[Nexus 7 Android Development] AndDiSa:
New Versions 7.1.2 (2022-04-05) are available

Hi guys, I uploaded a new release with updated security, i.e. the security paches for April 2022 and some fixes for potential security issues within the kernel.

Please note: To be more compatible with the latest Magisk version, this is the first version where no longer a su binary is provided within the ROM. To get root access you need to install e.g. Magisk.

Installing Magisk 24.x I was not able to install via TWRP / direct install, nevertheless patching the boot.img worked. Please report your experiences.

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-20220409.eng.ds.zip (MD5: 930c906d2785959fe3c182a4f0f18dd5)

aosp_tilapia-7.1.2-ota-20220409.eng.ds.zip (MD5: 1997eddeb839ee167b6be6d6a05631b4)

as well as the MicroG-Patched images:

aosp_grouper-7.1.2-mg-ota-20220409.eng.ds.zip (MD5: 83266153e65179f3d6893f98742113f1)

aosp_tilapia-7.1.2-mg-ota-20220409.eng.ds.zip (MD5: 0bb6c4a450408a0497096ce445fcae61)

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!
[Nexus 7 Android Development] momentoid:
Installed the latest, 2022-04-05 version of Grouper Standard ROM and 2022-02-15 version of GApps (that's the latest build). Everything 👍 Thanks @AndDiSa!
[Nexus 7 Android Development] marty_bebop:
Grouper MicroG April ROM, TWRP, Aurora Store et.al

--

To install Magisk:

I extracted boot.img from the ROM

Using Magisk app, created a patched .img file

It did not install from the app

So installed the patched .img file with TWRP

Success

--

I don't know if I made an unnecessary step

--

Anyway, all working well for me.

Thanks AndDiSa and everyone who helps!
[Nexus 7 Android Development] Luckz27:
@AndDiSa

I successfully installed the last updated ROM (Grouper_MG) and patched "Magisked" boot.img but now everytime I open the app I get this message: see attached image.

I can't see no more my installed modules too.
[Nexus 7 Android Development] AndDiSa:
@Luckz27 I never tried to use Magisk together with the mg-version. What do you mean you do not see your installed modules? When / how did you install them?
[Nexus 7 Android Development] Luckz27:
@AndDiSa

Here, watch the attached image: no modules.

But I had installed "MicroG Installer Revived" and "F-Droid Privileged Extension", when I first installed your ROM, so the last autumn.
[Nexus 7 Android Development] AndDiSa:
@Luckz27 did you wipe in between? Are you sure the modules you installed in autumn are compatible to Magisk v24.x?
[Nexus 7 Android Development] marty_bebop:
I too see that message when I open the app (Grouper MicroG).

I don't have any additional magisk modules installed.

So, I just use magisk to create the patched boot.img - and leave it there

The "Root Checker" app says my device is rooted and apps which require root are working.
[Nexus 7 Android Development] G_Bot:
Im using mg ota package with magisk canary.

I too had problems using magisk. But I flashed Magisk Canary version. I dont have any issues. Everything is working smooth.
[Nexus 7 Android Development] :
Thank you @G_Bot I'm getting the same thing (I have no modules installed either) I'll flash canary and see what happens (y)
[Nexus 7 Android Development] Luckz27:
@AndDiSa

I did a dirty flash: just dalvik cache and cache.

I just tried to install them again: the modules are in fact installed but they don't appear in the Magisk's window. Probably it's just a Magisk's problem, because the modules are updated... I don't know!

@marty_bebop

Yep, the ROM is correctly rooted but even if I reboot the tablet, once I re-open the app, the message is there again.

@G_Bot

But Canary is the alpha version... Had you any problems? No message?

Anyway, does anyone know how still have root privileges after updates the ROM?
[Nexus 7 Android Development] Baonks81:
I saw lot of people said about patch boot.img. Now I understand those step clearly

1. Extract boot.img from OTA zip files

2. On Android, Nexus 7 tablet, using Magisk and patch file select vmeta boot(ramdisk boot) whatever, I don't know lol

3. Select boot.img which extracted, and patching it

4. Connecting to pc/laptop, adb pull patching image to pc/laptop

5. Using fastboot flash boot patching_boot_magisk.img to Nexus 7

6. Done, and installing Magisk normally

Instructions here:

Installation

The Magic Mask for Android

topjohnwu.github.io
[Nexus 7 Android Development] Luckz27:
Yes, this is what I did, in fact the ROM is correctly rooted, but this is not what I was asking for in my previous post: I need a way to not have to do this everytime I flash an update of the ROM.
[Nexus 7 Android Development] Baonks81:
Back to Magisk 21.4
[Nexus 7 Android Development] OlliWi:
Hi bro,

seems to be the time to revive my tilapia. Wasn´t using it since september ´19. :)

battery is probably dead, trying to recharge. or maybe some charging issue ;)

cheers

Oliver

/edit: for now stuck in "google" bootloop because of dead battery, can get it into fastboot screen but it´s not (yet) starting recovery or Android.
[Nexus 7 Android Development] Baonks81:
I installed tilapia ota rom 20220409 standard, with magisk 24.1 and my custom sysctl.conf. It worked, thanks for support
[Nexus 7 Android Development] :
Yes, that's worked for me too.

I now have everything working OK (grouper mg) (y)
[Nexus 7 Android Development] AndDiSa:
you can try to

fastboot boot <recovery.img>

to go into recovery.
[Nexus 7 Android Development] OlliWi:
Syntaxfehler. Was muss ich denn anstatt <recoevry.img> setzen?

Ich muss gestehen, ich hab viele von den Kommandos vergessen.o_O
[Nexus 7 Android Development] AndDiSa:
You could e.g. download the recovery for your device from TWRP 3.6.1-9 for Grouper resp. TWRP 3.6.1-9 for Tilapia and store it within your current directory. Then you can start e.g.

fastboot boot twrp-3.6.1_9-0-grouper.img

resp.

fastboot boot twrp-3.6.1_9-0-tilapia.img

... but if you get 'syntax error, most likely the fastboot pogramm is not in your path ... ;-)
[Nexus 7 Android Development] OlliWi:
fastboot commands are working.

i´ll try to reboot to recovery now.. stay tuned

ok.. that worked. TWRP is up

"adb devices" reports device in recovery mode

IIRC. i will now do adb push <the system image>and adb push <gapps> and then install them from TWRP, ok?

or shall i flash TWRP to device first?
[Nexus 7 Android Development] AndDiSa:
You can also install from the booted TWRP, no need to install first. As you prefer ... ;-)
[Nexus 7 Android Development] OlliWi:
but I have no idea how to do that:cautious:

ok, seems i flashed wrong partition.

anyone who an help me to flash the recovery partition with fastboot?

/edit: nope, flash command was OK, but it seems something to be wrong with cache partition. cannot be mounted
[Nexus 7 Android Development] AndDiSa:
Try to wipe your cache partition, probably it's corrupted or contains an unknown file system type

btw

fastboot flash recovery <name of the recovery image>.img

should flash TWRP permanently.