yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] lucifersan:
Hi [MENTION=2188693]AndDiSa[/MENTION] I have installed the latest version with GAPPS and no root but an app (Movistar TV Argentina) is not working due that it detects a DRM error (Root detected). I tried installing Magisk and used Magisk Hide feature and it didn't work. Do you know why the app is detecting I have root while I'm not?

Thanks for this wonderful rom that keeps our nexus 7 still working.

Regards
[Nexus 7 Android Development] MacLeod100:
Try with

---------- Post added at 10:02 AM ---------- Previous post was at 09:57 AM ----------

There is a magisk module - SafetyPatch

that is hiding better than Magisk Hide

I was having same problem with HBO GO now is working well whitout problems

And my tilapia is certified according to GooglePlay ?
[Nexus 7 Android Development] Bakica:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Nexus 7 Android Development] MacLeod100:
The name is SafetyPatch
[Nexus 7 Android Development] Sam Nakamura:
we would need more details, are you sure you're on latest TWRP? ROM, GApps, Mods, Magisk? All for the correct device / architecture?

If so the procedure on this device:

- wipe:

/system

/boot

/cache

/davlik ART cache

-flash the latest build available here

-reboot to recovery (important!)

-flash latest GApps (7.1/arm/pico)

-flash magisk if needed

-reboot to system

and you should be good to go, sometimes it's necessary to format /data to get a clean start, just remember that this will wipe all files from internal storage, so you need a computer or pen drive to transfer the files (rom,GApps, magisk) back to your device!!!

good luck :highfive:

Edit: your issues could very well he connected to a outdated recovery!?!
[Nexus 7 Android Development] Seefuchs:
Thank you for your answer!

First more details about the device I have a ME370T so Nexus 7(2012)WiFi. And i used the links in the first post for the downloads.

And now to the condition of the device. I do not start up it just show "google" and an open lock stays there.

Once ago i needed Bluetooth-4.0 so i root it and put one the app from the appstore to update the driver. This went well and no problem. After i got a new phone i do not needed the Bluetooth and so i tryed to reverse it. I made an Backup before rooting and tryed to put this back on and unroot it.

For all of this steps i used Nexus Root Toolkit. But at this point Android got real unstable and was crashing again and again. So i tried to bring it clean on. And now i'm here. It do not boot to android. And i cant install or wipe anything. Every time it ends with:

Failed to mount '/system' (Invalid argument)

Failed to mount '/cache' (Invalid argument)

Failed to mount '/data' (Invalid argument)

This was the state one year ago and now i want to bring it back alive.

And i fear i tried to much to bring it back running and broke more than before.

Thank you for your help!
[Nexus 7 Android Development] garson99:
I installed this ROM about year ago, updated couple of times. Works really good. I noticed one glitch, that happened occasionally. In recent apps background is pink. Today I updated to latest version (Build 20190929), but now it is pink all the time. It is bit darker at the bottom. Looks weird for sure.

Not a big deal, I was just wondering does anyone else has this "issue"? :confused:
[Nexus 7 Android Development] MacLeod100:
????Sorry dude but you are funny !!!

Its the standard wallpaper just change it

---------- Post added at 08:15 PM ---------- Previous post was at 08:10 PM ----------

Do a factory reset before using Nexus Root Toolkit

In the NRT update the recovery and root folder , just download them separately and put then in the proper folder of NRT

Then try again to erase and wipe the cache , davlink and storage

I hope you will succed !
[Nexus 7 Android Development] garson99:
:)

It's not wallpaper, I use Car Launcher as launcher, and I never set any wallpaper especially pink one. :D

Before I've installed latest update, sometimes I could see pink background but with flashing white.
[Nexus 7 Android Development] breaktheblock:
I have had this off pink background too and showed as default for me but I don't know why. Then again my device doesn't work well with this rom at all.
[Nexus 7 Android Development] garson99:
You were right, I reverted to stock launcher and indeed it was wallpaper. :good:
[Nexus 7 Android Development] Seefuchs:
It starts that i can not do a factory reset.

After that he reboot to recovery. I downloaded the recovery from developers.google and androidfilehost and it don't work(latest Android version for Nexus same as on device). I believe with root folder you meant TWRP? As is did

But it did not work. Same Situation. Thank you for your answer i hope you got some more ideas.
[Nexus 7 Android Development] Sam Nakamura:
You should start to read the basics about android moddin (fastboot & adb, how to flash TWRP recovery, etc., you seem to have only messed with those PC tools which might be convenient but doesn't teach anything and this is a big disadvantage if those programs don't work anymore, don't get me wrong, this is not meant in a bad way or anything but I see a huge lack of basic understanding regarding this subject...

The recovery you downloaded must be the stock recovery which can only be used to install officially signed software, it's not suitable for this task, not suitable for custom ROMs, rooting and so on!

"root folder" seems to be the folder were you're supposed to put in the file you need for the rooting process (i.e. magisk.zip) I assume but I never used those toolkits myself. As much as I understand the suggestion from the other member there's one folder to put in "root" and one for "TWRP/recovery", put files in accurately and accordingly.

Check the first post of this thread it's very helpful!

It provides everything you need!

There's TWRP linked, you need to flash this version to your device, there're plenty of guides and videos on YouTube (either toolkit or fastboot).

Once TWRP runs factory reset and format data. Transfer the ROM & GApps to your device and use TWRP to install it.

Then refer to my previous post for more details and on what else to do.

I'm sure your device is fine, it's just a mess right now but easily fixable in my opinion, wipe it and re-flash it...

Good luck!
[Nexus 7 Android Development] MacLeod100:
I assume is soft bricked

It was happening to me too

I use NRT to return to factory software 5.1.2

After i update manualy the recovery folder of NRT

Flash the recovery with NRT

After that i use the tablet as usual to flash the room , Gapps , magisk according to the instructions of the developer

No problem at all after that !
[Nexus 7 Android Development] lucifersan:
Thanks for the suggestion!! unfortunately it did't work. I tried every device fingerprints and advanced hide (Device emulation resulted in bootloop) and the app is still saying i'm rooted. I don't know what root checks the app is using since it says I'm rooted without Magisk and Magisk manager not installed and with a rom clean install. Do you have any other suggestions?

Thanks!!!!!
[Nexus 7 Android Development] Sam Nakamura:
I don't remember which partition magisk installer modifies but it's recommended to run the appropriate/latest magisk uninstaller which is linked in post #1 in the magisk thread right here:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Download & flash & check again....
[Nexus 7 Android Development] step5:
I have the same issue like [MENTION=6714062]lucifersan[/MENTION]

I need to run the DKB Tan2Go app which doesn't run with the last 2 builds (20190929 and 20190823)

With 20190516 it does run like a charm

I did a factory reset and formatted data partition before flashing and installed gapps pico because the app needs this.

The seems to be an issue with the latest builds.
[Nexus 7 Android Development] fsw_informatrix:
Same here on my Grouper 2012 :D

As I almost never use Bluetooth and don't even have some specific BT devices, I've missed that one, but this week-end, I had the time to try, for you guys having such troubles with it, to simply transfer files between the Nexus 7 and my M4 Aqua (stock MM, but rooted and debloated) and it worked, in both directions:

- On both devices, I switched BT on and they saw each others instantly.

- I paired them, got the expected warning, authorized both respectively and that was it.

- I used Solid Explorer (which I recommended) to send a file (a picture) to and from each device, one after the other.

- In both case, I got the download warning, authorized both respectively and got the files, as hoped.

- Today, I've tested sharing files the same way, but from / to the Sony Album / AOSP Gallery app and everything still work as expected!

So if not already done, I would start again fresh from scratch, really cleaning (formating, that is) everything but the recovery and give it another go...

But it could also really be something of a very hardware driven bug that cause the pairing (or whatever) issues you got, so you really need to give AndDiSa some logs (I use CatLog which is old, but great and simple), if you want it to be fixed....

And by the way, thank you AndDiSa, for still keeping it up with us, even without hardware :cowboy: I think I can say that we are all much obliged to you :cool:

---------- Post added at 10:36 AM ---------- Previous post was at 09:57 AM ----------

To [MENTION=6714062]lucifersan[/MENTION] and [MENTION=1753057]step5[/MENTION]:

It could be a change in a file like build.prop or in another file that causes the check to fail, but you didn't mention if your devices pass the SafetyNet test? You can download and install the apps from the Play Store and then, when starting, the apps internal checks failed, is that correct?

As with Bluetooth, I don't use such DRM/banking apps and I've rooted my 2012 Grouper with latest Magisk.

But I could one day want/need to use such an app, so I did the SafetyNet test proposed by Magisk Manager (with default settings from MagiskHide) and got both:

ctsProfile: true

and

BasicIntegrity: true

I also use another free app from the Play Store to double check it, namely SafetyNet Helper Sample and it gives me the same positive results, so could you try it on your side, as you don't have Magisk, if you haven't already?

If not already, you could also root on purpose your devices with Magisk, let it do it's thing and test the whole thing again from the beginning, if you're already annoyed that you are rooted, when you aren't :rolleyes:

And please, don't forget logs if it's still failing to work...
[Nexus 7 Android Development] step5:
[MENTION=7375441]fsw_informatrix[/MENTION]

i have one grouper device and one tilapia device

on the grouper device i had the may build with gapps and installed just f-droid and aurora store to get the dkb app. no google account, so no playstore access

that worked well until i flashed the latest build. i didn't and do not use magisk here.

i can't do much reflashing and tryouts here because i need the banking app running and it is a hustle to reactivate is once it stops working.

on the tilapia device i run the latest build with microg and magisk and just applied safetypatch. the dkb app is not running here, just crashes.

i try to get some logs at the weekend
[Nexus 7 Android Development] fsw_informatrix:
[MENTION=1753057]step5[/MENTION]: Thank for your reply and for the details.

If I may, I also learned the hard way, a long time ago, that it is smarter to make a full Nandroid backup with TWRP and export it from the device to safety, before starting messing around and having things looking really ugly and badly broken at the end...

Especially in the case of a "critical" application, that can't be shut down / uninstalled / reinstalled easily ;)

But as you said that you "had the may build with gapps and installed just f-droid and aurora store to get the dkb app. no google account, so no playstore access that worked well" until all Hell broke loose, you should be able to wipe anything but the recovery and redo just that (flash the may build and so on).

Then, you would to go to the annoyance of reactivate the app and all, but at the end of the day, you should be back in business.

And finaly, now would the good time for a full Nandroid backup with TWRP and an export in safety...

Making logs when the system and the app are working would be also a good idea, for later use (CatLog is great and simple for it).

If you have then a moment free, not needing the app (the week-end, perhaps) and you feel courageous and motivated :D you can flash the latest build and have a go at it.

If it fails to work, you will have to make new logs, to try to catch the differences in between...

If lucky enough, it can be easily found and fixed, or you wil have to restore your backup, if not.

I have no clue if the banking app will like to be restored or if after, you will stil have to reactivate it again, though...

Hope this helps, good luck!
[Nexus 7 Android Development] Seefuchs:
Thank you for your Answers i tried now a few days but every time the same all above fastboot is bricked i can get into the recovery but it starts with the "Failed" failures and everything i do there ends with the same "Failed". I tried different recovery all the same end.

If i refer to /nexus-7-2013/nexus-7-2013-qa/fix-nexus-7-2013-bricked-stuck-t3310608 and see my problems i and read the old topics about dieing eMMC with my 2012 and fear that i got the same Problem because nothing works. I'm in a dead end. I can change the bootloader and the recovery but all other things are blocked.

I don't know how to move on. Does anyone have an approach more?

Thank you for your time.
[Nexus 7 Android Development] MrSchaal:
I'm currently on the latest LineageOS build with security patches from November 2018.

Since LineageOS doesn't seem to receive updates anymore, I'd like to switch to this AOSP ROM. Even though I really love the extra functionality LineageOS adds to AOSP. But the outdated security patches are really frustrating and it's great to see that this developer here still keeps maintaining our good old nexus7!

During the last few days however, I've experienced that the Touchscreen starts to become very unresponsive after a while of using it (I use this device mostly for drawing and writing on the go) which is very annoying.

After a reboot, the Touchscreen is usually responding like before for a couple of minutes, but then it becomes unresponsive again and I need to reboot. This is quite annoying.

Somebody knows if this ROM maybe has different Kernel settings or something like that which are different from LineageOS and which may be solve my issues? I'd really like to keep this device after 7 faithful years.

Thanks in advance!

Christian
[Nexus 7 Android Development] bangsergio:
Everything runs smooth with last build except for wifi drop and Video stuttering Ehen streaming.

Regards
[Nexus 7 Android Development] mudduck454:
Total noob with flashing, but i just found my old nexus 7 hiding in the back of a drawer and the battery is working good, is there a step by step tutorial i can use to flash this rom? I have been looking but cannot find it
[Nexus 7 Android Development] mikeataol:
you have to start by unlocking it and rooting it

(Im going off of a long ago memory here)

search wugfresh Nexus Root Toolkit (NRT)

grab the TWRP appropriate for your device (grouper is WiFi model, Tilapia is the 3G cell model)

TWRP 3.2.3-0 for Grouper resp. TWRP 3.2.3-0 for Tilapia from first post in this thread

get the rom from the first post

get the open gapps link in the first post

get MAGISK from the first post (for root after you install the new ROM)

use the NRT toolkit and install/flash the TWRP img as recovery

after install Twrp, boot into recovery (which is TWRP)

it helps if you are already familiar with TWRP

For some time my process has been (on lots of phones and tablets, not just this Nexus)

wipe system, cache, and dalvik

(on the first install you also want to wipe /data if the rooting process didnt already do that)

Install ROM

REBOOT TO RECOVERY

Install OpenGapps

Reboot to Recovery

Install Magisk

I rarely see issues doing this
[Nexus 7 Android Development] mudduck454:
It took a little digging but i believe i got it to work, just installing all the other stuff now, thanks for the help
[Nexus 7 Android Development] Sam Nakamura:
Hey, sorry for the late reply but I´m not daily checkin XDA anymore...

My N7 had a dead EMMC too, the infamous "EMMC brick bug", I replaced the motherboard a year ago (then recently I cracked the screen, now my N7 actually constists of 3 diffrent devices, parts-wise but looks like new), repacing the board is easy and straight forward, I was getting a 32GB replacement for 20 bucks and to me it still worth it as I use this device daily to watch YouTube and stuff and the N7 get´s it done just fine...
[Nexus 7 Android Development] AndDiSa:
Version with October security fixes (2018/10/05) available

Here are the links for the October-release:

Grouper 20191025

Tilapia 20191025

not tested, so OP is not updated yet. I would like to wait until I get positive feedback from the community

For those who want to build by themselves: the repos are updated, too.
[Nexus 7 Android Development] someguykenadams:
I'd update the OS on my Nexus 7 tablet, but, the display broke and I need to get another one.
[Nexus 7 Android Development] TureX:
Hi! Last update works good, thank you!
[Nexus 7 Android Development] wwt:
Last update works well, thanks!
[Nexus 7 Android Development] AndroidGuy087:
Do you reckon that with a little manifest modification we could get Android 8.1 AOSP on our device?
[Nexus 7 Android Development] AndDiSa:
You are invited to do so, the sources are all available on GitHub ...
[Nexus 7 Android Development] Bakica:
Dirty flash on Grouper works good, thanks a lot!
[Nexus 7 Android Development] laugeek57:
@ Andisa flash successful from the previous version everything works ...

I tried a little infidelity by testing the ROM aosp 8.1 but impossible to install a Dolby Dolby Atmos lol sound module

Looking forward to testing one of your versions 8.1 I hope
[Nexus 7 Android Development] dark0shark:
Me too.
[Nexus 7 Android Development] Swanee123:
Dirty flash on Tilapia went well. Haven't tested every function yet but looking good so far. Thank you!
[Nexus 7 Android Development] Seefuchs:
Thank you for your answer. I bought one with a cracked screen and dead battery for 12 bucks. Now is switched the parts and now i did the same steps as before and no failures and now its runs fast and smooth with the 7.1.2-ota-eng-20190610 build. And i will never touch it again. ;)

Thank you all for your help!
[Nexus 7 Android Development] CamoGeko:
I'm just curious, why arent you running the October patched ROM?
[Nexus 7 Android Development] Cydras:
Hi,

the October rom is working very good :) Thank you very much!

I have data and cache formatted to f2fs.

Anyone know if it is possible to overclock a litte bit the cpu?
[Nexus 7 Android Development] :
Clean flashed, WiFi would not connect. Dirty flash is fine. Weird huh? I usually clean flash to avoid errors!
[Nexus 7 Android Development] Cydras:
That's strange, i clean flashed on taliper and on my device wifi and bluetooth is working.

I formatted system, data, cache and dalvik.
[Nexus 7 Android Development] Cydras:
I found an issue with GPS on taliper.

When i connect to a WiFi network, GPS stops working. Then i must restart the tablet without connect to wifi to work again.

I use the tablet as car dashboard in my car, i can everytime reproduce the error whem i make a hotspot with my phone. I can make you logcat logs when needed.
[Nexus 7 Android Development] AndDiSa:
That's a very strange issue, I never heard about that. Can anybody else confirm the issue?

As I do not have neither a Grouper nor a Tilapia device anymore I am not able to test it but feel free to post / send a logcat. Probably there is a chance to identify the root cause of the issue.
[Nexus 7 Android Development] Cydras:
Sorry for writing the issue above, I maked some more tests and found out that this is not a rom issue.

It's an issue from app Auto Mate. In Google Maps GPS is still working after connecting to WiFi.

Your rom is running very good :)

Thank you very much!
[Nexus 7 Android Development] aiamuzz:
Firstly Good to see the thread bustling with activity even now ...

Can somebody point me to the download builds for this ROM ... i'd like to browse through the dailies and the releases ...

Anybody successfully got Oreo Go up and running on our Grouper Device ... would be nice given it has only 1 GB RAM ...
[Nexus 7 Android Development] rahimali:
https://androidfilehost.com/?w=files&flid=117850

October builds are linked to in this post
[Nexus 7 Android Development] aiamuzz:
[MENTION=550835]rahimali[/MENTION] ... thanks

Are there no Oreo Go builds for our Grouper devices yet ?
[Nexus 7 Android Development] rahimali:
Negative.
[Nexus 7 Android Development] Sam Nakamura:
WOT :eek: updates physically break the device?!? I guess there's nothing impossible nowadays... lol
[Nexus 7 Android Development] CamoGeko:
Uhm... I heard it only happens if you download the "optional" Shattered Glass Magisk Module. :eek:
[Nexus 7 Android Development] MacLeod100:
The force is with us :)
[Nexus 7 Android Development] ltmcmullen:
Worked Right out of the Box

Thanks for all your work. I installed with no problems and everything worked out fine. I also dodged a bullet because I installed Magisk before doing the boot first. It took a long time to boot up the system but so far so good. :good:

Thanks Again!! :victory:
[Nexus 7 Android Development] Seefuchs:
First post link :)
[Nexus 7 Android Development] diein2hard:
Hello,

I have not touched my Nexus 7 in a long time. I am going to try to follow the installation instruction on the main post on page 1. But I do not recall or know what details steps I should use to install the Grouper Recovery, and the OTAs etc. Any help or pointing me to the detailed instructions would be super appreciated.
[Nexus 7 Android Development] mikeataol:
There are no OTA's for this. You just update your ROM when you feel like it.

It's being updated frequently by the developer at the moment.

edit: By the way, this ROM and device is eminently usable, I use mine all the time.

Here's a rough guide to getting this custom ROM on the Nexus 7 2012.

https://xdaforums.com/showpost.php?p=80598105&postcount=3874
[Nexus 7 Android Development] davidjormi:
After software update the touch screen has been stopped working :eek: Now I am using it with a mouse through OTG

Could be possible due to the software or is just a coincidence?

Thanks¡
[Nexus 7 Android Development] someguykenadams:
Actually, no. The touch screen worked just fine, the glass cover cracked on me when I accidentally left it on top of my dryer.
[Nexus 7 Android Development] vinibali:
[MENTION=2188693]AndDiSa[/MENTION]

thank you for this great rom. would you mind set the default governor to interactive?

intelliactive for me is so laggy, interactive is much more smooth on the UI.
[Nexus 7 Android Development] CamoGeko:
You can use a kernel app and set it to retain the setting on reboot. :)
[Nexus 7 Android Development] AndDiSa:
On a first glance I wanted to say the same ... but it is not as easy as it seems. Currently the power management is setting back to intelliactive frequently.
[Nexus 7 Android Development] vinibali:
Kernel adiutor just let me to set it to interactive and nothing has forced it back intelliactive yet (1day+).

Btw I just fine tuned the intelliactive now and it's much more responsive now, I just wanted to point out, that I felt it a bit laggy.

My expectations are not so high, I'm using a Oneplus3 with underclock.

Is there any reason why are we using this particular governor with these settings?

Do we expect a small amount of saved bettary capacity over interactive?

Regards
[Nexus 7 Android Development] MacLeod100:
No ! you r digitizer ( aka touch ) decide to let you down .