yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 18.1 - May 2021

lineage-18.1-20210506-UNOFFICIAL-flo.zip

lineage-18.1-20210506-UNOFFICIAL-deb.zip

Changes:

- Google Security updates -> May 2021

- Patched frameworks/base to support microG

- Latest LineageOS changes for Android 11

Pls check first page for installation instruction and known issues !

Tested flo build with opengapps test packages (pico) and Magisk 22.1.

Installed with latest TWRP 3.5.2.

Enjoy Android 11 :p
[Nexus 7 (2013) Android Development] RuneMason1:
So download the DEB version of TWRP (which i have already, but i'll reflash) and the lineage zip for DEB, and do i need the Sysrepart one? And flash TWRP, boot to recovery, copy the lineage zip onto the device storage, install it with TWRP? or do i install the sysrepart one first?
[Nexus 7 (2013) Android Development] ipdev:
I was thinking about you earlier today. ;)

I thought about your previous post and I was not sure if you got Lineage installed?

---

You need to (re)partition before installing the rom (lineage).

This normally only needs to be done once.

Take a look at the last part (Note to all), of this post to hopefully help explain partitioning.

Post 3,008 - Link

See this post for more information and links to the partitioning scripts for deb/flo.

Post 3,362 - Link

Since then, k23m went Supernova 🤯 making sysrepart-ultimate.

Post 3,387 - Link

Post 3,392 - Link

Note:

There is limited storage on any device. The storage has to be split up into all the partitions.

Including critical partitions like preloader, bootloader, boot, recovery, ....

When you increase one partition you have to take from another.

There is unallocated space on deb/flo that can be used but, once that is used you have to reduce a partition to increase another.

Keep this in mind while you decide how to partition the device.

---

Once you have a new partition scheme, you should be able the follow the install instructions from the OP.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] RuneMason1:
Felt like a moron, but i think it was number 2 i didn't do. I finally got it to work! Thanks :D
[Nexus 7 (2013) Android Development] JohnDovas:
Please help, i have repartitioned my nexus 7 flo, and when i try to install the rom it says that my model is flo and not flox.
[Nexus 7 (2013) Android Development] Mr.Conkel:
Reflash Twrp from here

Download TWRP for flo

Download TWRP Open Recovery for flo

dl.twrp.me

Then continue to flash this rom. This is an unofficial build of Los make sure you flash this rom with Official recovery.

Flox is the official branch for this device which has covered Los 17.1 and just recently Official builds for 18.1. If you use the official builds of 18.1 you will need the flox recovery which can be found in this thread

https://xdaforums.com/t/rom-official-lineageos-17-1-weeklies-for-nexus-7-2013-flox.4205241/

Happy flashing! Cheers!
[Nexus 7 (2013) Android Development] djibe89:
Hi, how do you pass SafetyNet ?

MagiskHide doesn't work. everything fails on flo.

Thanks for your help.
[Nexus 7 (2013) Android Development] ipdev:
Hi.

If you are checking SafetyNet with the Magisk app (Magisk v22.1 and below) you will get an error.

This has been fixed in Magisk and the next stable/beta releases will include the fix.

Double check SafetyNet using a different app.

Root Checker - PlayStore - Link

Paid apps.

Root Checker Pro - PlayStore - Link

SafetyNet Device Check - PlayStore - Link

Cheers. :cowboy:

PS.

From the Magisk and MagiskHide Installation and Troubleshooting guide.

Hiding root and passing Safety Net - WebSite - SafetyNet API error - Link

The API key Magisk was using was revoked. John requested a new key from Google and updated Magisk's SafetyNet check to use the new key.​
[Nexus 7 (2013) Android Development] jhford:
I recently upgraded my 2 Nexus 7 2013 debs to this Rom. It's very smooth and well done but I'm constantly receiving the "System UI isn't responding" error. Does anyone know the solution? Thanks
[Nexus 7 (2013) Android Development] mick3lson:
Is there any chance to activate double-tap to wake without an kernel manager, currently I installed crDroidAndroid-11.0
[Nexus 7 (2013) Android Development] djibe89:
Hi,

I don't have this.

Have you tried reflashing ?
[Nexus 7 (2013) Android Development] ipdev:
I use a boot script to enable DT2W.

Turned it into a magisk module a while back.

Double tap to wake - GitHub - Link

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] moonbosques:
Hi! I am getting the next error:

E : Error creating fstab

Any idea of why this is happening and how can I solve it.

Im in TWRP 3.5.2_9-0

Thanks in advance :)
[Nexus 7 (2013) Android Development] moonbosques:
Update: Now I am getting:

E1001: Failed to update system image.

Updater process ended with ERROR: 1
[Nexus 7 (2013) Android Development] ipdev:
Hi.

The recovery log file will show more information.

/tmp/recovery.log

The temp directory is empty after boot, so you need to copy the log file after the error and before you reboot the device.

Easiest is to pull the file to your computer using adb.

adb pull /tmp/recovery.log

This error means the updater (installer) script would not complete if it continued to run.

script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001

It should error out and exit before anything was modified or changed.

Leaving your system as it was before you attempted the install.

Normally that error means there is not enough space in the system partition.

Might also happen if you are using an old or unsupported recovery.

The system partition can not be mounted for some reason.

You should have received a different error if the zip file was corrupt.

Just to be safe, double check your download(s) using the md5sum file that matches the build you downloaded.

--

You need to (re)partition flo/deb before you install lineage. ;)

These posts have information on partitioning and installing lineage.

Post 3,362 - Link

Post 3,428 - Link

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] davidsekar:
APPS that have webviews in them shows slow scrolling and bad touch response?

I received same issue twice after fresh installing this ROM, I was able to resolve this issue by installing Android system web view from playstore and disabling the default system provided one.

Disclaimer : my observation might be flawed. But it did the trick for me.
[Nexus 7 (2013) Android Development] Crypto2k:
I realize this is asking a lot but has anyone had luck or know how to get LineageOS 18.1 & ElementalX working on a Nexus 7 2013? I have Lineage working along with Magisk 23. ElementalX I can only find support under the device for up to Android 8.1. If I try to use that one or 6.17 I go into a boot loop. That makes sense because it's too far behind but was worth a shot.
[Nexus 7 (2013) Android Development] ipdev:
followmsi has been updating an ex kernel for flo/deb also.

I took a look back and I believe this was the last post about it.

Look in the KERNEL folder.

Post 3196 - Link

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 18.1 - June 2021

lineage-18.1-20210610-UNOFFICIAL-flo.zip

lineage-18.1-20210610-UNOFFICIAL-deb.zip

Changes:

- Google Security updates -> June 2021

- Patched frameworks/base to support microG

- Latest LineageOS changes for Android 11

Pls check first page for installation instruction and known issues !

Tested flo build with opengapps test packages (pico) and Magisk 23.0.

Installed with latest TWRP 3.5.2.

Enjoy Android 11 :p
[Nexus 7 (2013) Android Development] Crypto2k:
Thank you both! Quick question, can I load this kernel on top of the official 18.1 build? I loaded that one up yesterday, going through the whole repartitioning, and would rather not rebuild all the customization/automation I've done since it if I don't have to. Also happen to know if anyone has carried on otg+charging and pem work (or similar outcomes) after Timur? Searches come up with a lot of outdated dead ends. I've gotten most of the core functions replicated through Automate but it's just not as reliable on the on/off functions.

So great to keep this tablet alive through the help of this community.
[Nexus 7 (2013) Android Development] Crypto2k:
Closing the loop. I tried to just flash the kernel and got into a loop. I then just flashed the unofficial over the official which corrected the boot loop. I then applied the kernel with no issues. Following that I build a new Magisk image and applied that through TWRP. Booted up fine and Magisk checks out. I then loaded EX Manager from the app store and turned on otg+charging, fast charge, and other needed features. All is working now far as I can tell and it seems like audio quality also improved.

There is a weird issue where when I enable bluetooth it bounces on and off about 5 times and then turns on officially. Too early to know if that's going to be an issue. I'll do my diligence on that if so and then revert back.

Really appreciate all the effort on these builds and the extra pointer to get me right where I wanted to be, Android 11 with near Timur functionality.
[Nexus 7 (2013) Android Development] ulao2:
1.) Do factory reset in TWRP - keep internal storage this way.

2.) Format /system partition in TWRP

3.) Install ROM

4.) Install Gapps (optional) <<-- error 1, using clamor is BAD took all day to repair my file system!

5.) Install Magisk 21.x (optional)

6.) Reboot into system and start to setup your device. <<-- bootloops. ( or to be specific, takes really long and then reboot to twrp)

I think I need to rezise system but not sure the best way. Tried posting in general help but maybe here is best

tried cross flox for 18.1 and got 2 errors

1) could not mount vendor partition but it went on .

2) error 20 installing gapps.

now it does not boot at all, bootloops on the google screen. Twrp is gone can only load it via nrt.

I'm not sure what this flox is all about, I tried manually installing it and the scripts tells me I'm flo not flox? Is flox some kind of update to the file system for flo? If so then why does it still say flo after all of this?

Last try for the day, ill see if flo and 17.1 works. Using cross again.

No errors and seems to have worked.

I guess 18.1 is not meant to be for me.

Thx to @k23m his tool is pretty good.
[Nexus 7 (2013) Android Development] Mohsen:
WaaaaW ...

Just THANKS a zillion time.
[Nexus 7 (2013) Android Development] Enzimotory:
Hello. I can't figure out how to install Gapps, I installed the system via twrp 3.4 everything worked, I want to install Gapps,but it gives an error of 70, I tried everything but it doesn't help. I tried to use the sysrepart_1280_120 file.zip, but it is not installed, there are no errors, but nothing happens after creating logs. I tried the sysrepart file.zip the error Failed to mount ' system_root (invalid argument) what to do? how to install root? google nexus 7 2013 lte heeeeelppp plsssss:cry::cry::cry::cry:

P.S. I put the version [ROM] [8.1] [UNOFFICIAL] LineageOS 15.1 for Nexus 7 2013 (LTE) everything worked

P.S.S failed to mount /system_root (invalid argument) what's it mean?
[Nexus 7 (2013) Android Development] underflash:
Trying to install MindTheGapps-11.0.0-arm-20210412_124103.zip after installing latest LineageOS 18.1 - June 2021 before the first reboot. Error: could not mount /mnt/system

Also have a major problem booting into recovery, it boots randomly after numerous attempts (once in 10-15), if not, just hangs on Google logo. At this stage I have to remove battery to restart, no reaction to power+volume buttons. I have tried 3.4.0-0-flo and 3.5.2_9-0-flo, it seems no difference at all. Notices, that TWRP does not save it's settings.

Any solutions?
[Nexus 7 (2013) Android Development] underflash:
Any chance you could release AospExtended Eleven v8.3?
[Nexus 7 (2013) Android Development] Enzimotory:
try to flash through twrp version 3.4, I succeeded, although there was the same problem
[Nexus 7 (2013) Android Development] ipdev:
If you are on Lineage 17.1, your device is (re)partitioned, no need to do it again.

Be Careful.

Backup what you want to save and store it off device.

Copy it to your computer, cloud storage, USB, ...

Now you should be able to install 18.1 clean.

Boot into TWRP and Factory Reset.

Use the TWRP option to Wipe System and caches.

Install ROM.

Install GApps. (Optional)

Install Magisk. (Optional)

Reboot to system.

---

Quick look in k23m's thread, CROSS for l17.1 uses a 1.3G system partition.

OpenGApps Pico and Nano are your options with l18.1.

There is a difference between partitioning and resizing and image.

Post 3,428 Link

Please read all the linked posts. 🙃

---

As for flox..

When Lineage brought back an official flo build, since it required (re)partitioning and adding a vendor partition, they renamed it flox.

There is a debx branch also but, it seems to have issues.​

This changes how the rom is made.

Instead of vendor being included in the system image, it becomes a separate image.

The vendor partition is then symlinked into system.​

To install/flash flox, you need to use the modified TWRP or the Lineage recovery for flox.

You need a separate vendor partition and at minimum a 1.5G system partition.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] ipdev:
First I would suggest using TWRP 3.5.2

Post 3,393 Link

Quite a few fixes and updates since TWRP 3.4.x

---

You need to (re)partition for Lineage 17 (16?) and above.

As for (re)partitioning you only need to do it once.

Well as needed would be more correct.

I have made a few posts about this recently.

Including linked posts with partition options and links.

Post 3,428 Link

Please read all the linked posts. 🙃

From post 3,362 Steps under the hide tag

Be Careful.

Backup what you want to save and store it off device.

Copy it to your computer, cloud storage, USB, ...

---

failed to mount /system_root (invalid argument)

The above error is about partitions and mount points.

The root directory is always /

Since SAR (System As Root) was introduced and later mandated.

/system is root and /system/system is system.

When booting into the rom(system) a switch mount happens in early boot.

/system is remounted as /

Since /system is now / everything drops down.

/system/system becomes /system​

When booted into recovery, recovery is mounted in root /

Before SAR, system was just mounted into /system

With SAR, mounting system to /system mounts the root of the rom(system).

Then system is /system/system to get around this..

The system is mounted to /system_root

Then /system_root/system is linked to /system

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] ipdev:
MindTheGapps can not mount the system partition.

TWRP will default to the older/original fstab when an older or no rom(system) is installed.

Since SAR (read the above post), TWRP will switch to using system_root when SAR is detected.

Try installing Lineage 18.1 and then reboot to recovery (this will switch the mounting to SAR) and see if MindTheGapps can mount system.

Note:

Since you mentioned TWRP does not save settings..

TWRP saves it's settings to data.

If you wipe or format data, TWRP's settings will be lost.

If TWRP settings are lost without wiping or formatting, then data is not accessible to TWRP.

You might need to format data and wipe all the partitions afterwards to get it to work.​

Please see my post above and follow the linked posts.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:

PS.

Be Careful.

Backup what you want to save and store it off device.

Copy it to your computer, cloud storage, USB, ...
[Nexus 7 (2013) Android Development] Enzimotory:
Thank you, but I've already done everything, everything works, but everything lags:cry::cry::cry:
[Nexus 7 (2013) Android Development] ipdev:
Odd..

A clean install, should be fast.

Normally the lag increases with use and sequential updates.

Let the initial boot settle down, setup and configure.

Once you configured everything, reboot and let it sit for a few minutes.

Note:

Set the Animation speed to .5 under Developer options, this will help speed it up a little.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] ipdev:
I prefer AEX myself.

When I have time I will try and port it. ;)

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] ipdev:
Hi all. :)

A bit of OT. 🙃​

I ran a crDroid build using followmsi's lineage sources.

crDroid v7.7

Android 11

Changes:

- June 2021 Google security updates

- Latest crDroid changes for Android 11

This is a one-off build.

I currently do not have the time to test/maintain a regular update for crDroid.

Note:

Tested on flo.

crDroid is a bit larger than lineage..​

- OpenGapps nano did not fit on a 1.3G system.​

- OpenGApps pico installed with no problems.​

Links.

crDroid Android - Personal Builds - SourceForge - Link

OpenGApps - Post 3,267 - Link

Cheers all. :cowboy:
[Nexus 7 (2013) Android Development] kahlostipper:
Just in case this is helpful for anyone, here are my notes / steps for installing this unofficial Android 11 Lineage build to my Nexus 7 deb

https://xdaforums.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-06-10.3569067/

* Power off

* Get into bootloader

power button + volume down

* Unlock the bootloader

fastboot oem unlock

* Get back to the bootloader

* Download the latest supported TWRP .img

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

twrp-3.5.2_9-0-deb_followmsi.img

* Install TWRP recovery

fastboot flash recovery twrp-3.5.2_9-0-deb_followmsi.img

* Select recovery mode to boot into TWRP

* Create a backup and copy onto PC

* Wipe all partitions, including system

Advanced Wipe, Select all partitions

* Download the latest sysrepart.zip

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

sysrepart_1280_120.zip

* Install the sysrepart by copying the .zip file onto the nexus 7 and using TWRP install dialogue

* Reboot device back into TWRP recovery (there will be no OS installed)

* Download the latest lineage build

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

lineage-18.1-20210610-UNOFFICIAL-deb.zip

* Copy to device and install the latest lineage build by selecting the .zip file

* Download BiTGApps ARM package for correct Android version (Android 11 at the moment)

BiTGApps Official - ARM

Custom GApps Package For Android Platform ARM.

www.pling.com

BiTGApps-arm-11.0.0-R28_signed.zip

* Copy to device and install the latests BiTGApps package

* Reboot and configure
[Nexus 7 (2013) Android Development] biwuchen:
thank you
[Nexus 7 (2013) Android Development] godrick15:
Did all this except for flo version.

Device able to boot and working fine.

Problem is I can't install magisk.

Tried via twrp and magisk apk v23.

Any help?
[Nexus 7 (2013) Android Development] ipdev:
Hi.

What issue are you running into?

- Device will not boot the Magisk patched image.

- Device boots the Magisk patched image but, Magisk shows as Not Installed.

Normally on flo/deb I just use the Custom Recovery install.

On other devices, I pull the boot image from the ROM zip and use the Magisk app to patch it.

Then I boot the patched image and check if Magisk shows as installed.

This is temporary since I only booted the patch image instead of flashing it.

If everything seems to be good (nothing broke), I then use the Direct Install option in Magisk to patch the installed boot image.

I use the Magisk canary build but, right now there is no real difference canary and release.

Magisk Documentation [github.io] Installation Instructions

Custom Recovery - Link

Patching Images - Link​

As I noted above, I test boot the images first, I do not just flash it.

If you read the Patching Images instructions, after Copy the patched image to your PC with ADB: use

fastboot boot /path/to/magisk_patched.img to temporarily boot the patched image.

You can use the Direct Install option in Magisk to patch the installed boot image, or reboot to bootloader (fastboot) and then flash the patched boot image.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] godrick15:
Twrp fails to install. I get the following message...

Cannot mount to vendor

Via magisk apk with Magisk23.0.zip...

Unknown image format

Edit:

Renamed apk to zip and flashed via twrp

everything working fine now
[Nexus 7 (2013) Android Development] followmsi:
Pls go ahead ! (y)
[Nexus 7 (2013) Android Development] followmsi:
Thanks for all your work ! (y)
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 18.1 - July 2021

lineage-18.1-20210721-UNOFFICIAL-flo.zip

lineage-18.1-20210721-UNOFFICIAL-deb.zip

Changes:

- Google Security updates -> July 2021

- Patched frameworks/base & apps/PermissionController to support microG

- Latest LineageOS changes for Android 11

Pls check first page for installation instruction and known issues !

Tested flo build with opengapps test packages (pico) and Magisk 23.0.

Installed with latest TWRP 3.5.2.

Enjoy Android 11 :p
[Nexus 7 (2013) Android Development] Tuxianer1988:
Hey,

I instlaled on my old Nexus 7 the latest build. Now I attempted to install Roller Coaster Tycoon, MS Office App and Stardew Valley. They all fail with an installation error at the end of the download when reaching 99% What I noticed is that all these apps require "additional" data to be download with the package.

Anybody else able to reproduce the issue and or tell me what I need to change/fix to get those apps working again?
[Nexus 7 (2013) Android Development] Voldo X:
I do have the same Problem with Rollercoaster Tycoon Classic and some other apps, but for a while now, not specific with the 20210721 rom. It trys to download but on around 90% it shows an error.
[Nexus 7 (2013) Android Development] bleuiko:
Just installed using this awesome guide. Everything is working generally. Thanks!

I passed SafetyNet but still couldn't install Netflix.
[Nexus 7 (2013) Android Development] bleuiko:
Does anyone else have experience that says SELinux is disabled?
[Nexus 7 (2013) Android Development] killeriq:
Hello,

I'm getting ERROR 70 again and again on DEB

After following instructions:

1. did wipe all partitions

2. installed sysrepart_1280_120.zip

3. installed lineage-18.1-20210721-UNOFFICIAL-deb

4. Soon as i try to install open_gapps-arm-11.0-pico-20210622-UNOFFICIAL_TEST or open_gapps-arm-11.0-pico-20210730.zip i get ERROR 70

Seems like the "partitioning" sysrepart_1280_120.zip is not working well or what...

I've tried "flo-deb_clamor_repartition" which im often using on FLO and i was able to install "open_gapps-arm-11.0-pico-20210730.zip" or first try

Where is the problem?

Thanks
[Nexus 7 (2013) Android Development] ipdev:
Hi. :)

For now, we are still SELinux Permissive.

For more on SELinux.

See Post # 3,286 - Link and Post # 3,372 - Link

If Netflix is not avaliable on PlayStore, make sure PlayStore shows Device is certified under settings.

If you pass SafetyNet and not Play certified, clear the cache and/or data of PlayStore app.

For more on installing Netflix.

See Post # 3,238 - Link

Cheers. :cowboy: