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

[ROM][flo|deb][UNOFFICIAL][LineageOS 18.1] -> 2021-09-10

Search This thread

ipdev

Recognized Contributor
Feb 14, 2016
1,497
1
1,864
Google Nexus 10
Nexus 7 (2013)
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:
 
Last edited:

kahlostipper

New member
Feb 18, 2019
2
9
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

* 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
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
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
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-arm-11.0.0-R28_signed.zip
* Copy to device and install the latests BiTGApps package
* Reboot and configure
 

biwuchen

Member
Feb 27, 2021
6
1

EmPczMv.png

LineageOS 18.1

lineage-18.1-20210610-UNOFFICIAL-flo.zip
lineage-18.1-20210610-UNOFFICIAL-deb.zip



Known issues:

- Encryption has not been tested .. pls test on your own risk.
- We are still Permissive (SELinux)
- And maybe more issues .. ?

Installation:
1.) Do factory reset in TWRP - keep internal storage this way.
2.) Format /system partition in TWRP
3.) Install ROM
4.) Install Gapps (optional)
5.) Install Magisk 21.x (optional)
6.) Reboot into system and start to setup your device.

Android 11 Partition sizes: Flo and Deb device -> 1100 MB -> both devices needs reparition !
Pls check below for more details.

Gapps:
@ipdev made some opengapps test packages.
https://www.mediafire.com/folder/qxo023zef5chm/unofficial
Or use BITGapps or other packags for ARM.

MicroG:
The ROM have been patched to support microG !

Magisk:
Tested with Magisk 21.2
If Safety.net check does not work just disable and re-enable "Magisk Hide" in Magisk settings menu.

system-as-root (SAR)
https://forum.xda-developers.com/showpost.php?p=80591849&postcount=2709

System repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system partition .. either via TWRP package or manually via shell.
It's an one time task.

But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 880mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 880mb).
The free space we got thru repartitioning needs to be allocated again.

For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.

There are repartition solutions from @ipdev @Clamor @k23m .. and maybe more.

Made new sysrepart.zip based on the original from @k23m
https://forum.xda-developers.com/showpost.php?p=76278047&postcount=19
The original code is changing to 1140MB (system) and 260MB (cache).
These days /cache is not used anymore .. a few MB only.
For this reason I have changed the values to 1280 (system) and 120MB (cache) now.
https://forum.xda-developers.com/showpost.php?p=78703434&postcount=1971
sysrepart_1280_120.zip
All the credits to @k23m !!!

Sources:
https://github.com/followmsi/manifests/tree/flo-deb-lineage-18.1
https://github.com/followmsi/manifests/tree/flo-deb-aex-pie
https://github.com/followmsi/manifests/tree/flo-deb-lineage-16.0
https://github.com/followmsi/manifests/tree/flo-deb-pixel-pie
https://github.com/followmsi/manifests/tree/flo-deb-rros-lineage-16.0
https://github.com/followmsi/manifests/tree/flo-deb-aosp-p
https://github.com/followmsi/manifests/tree/flo-deb-aosp-o
https://github.com/followmsi/manifests/tree/flo-deb-aosp-nougat

Download:
https://drive.google.com/open?id=0By6p5AdQfavBUlhsLWFHZThGTnM
All other ROM have been moved to androidfilehost.com ..
https://androidfilehost.com/?w=files&flid=289295

All the testing has been done by @ipdev - big thanks to him !

Thanks to @nbehary and @DevSwift1 and @flex1911 and @yattodettaman and @emmett.tsai !

Big Thanks to LineageOS Team !

Enjoy :p
thank you
 
  • Like
Reactions: followmsi

godrick15

Senior Member
Oct 27, 2013
217
16
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

* 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
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
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
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-arm-11.0.0-R28_signed.zip
* Copy to device and install the latests BiTGApps package
* Reboot and configure
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?
 

ipdev

Recognized Contributor
Feb 14, 2016
1,497
1
1,864
Google Nexus 10
Nexus 7 (2013)
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?
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:
 

godrick15

Senior Member
Oct 27, 2013
217
16
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:
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
 
Last edited:
  • Like
Reactions: ipdev

followmsi

Senior Member
Oct 10, 2013
4,101
12,336
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:

Thanks for all your work ! (y)
 
  • Like
Reactions: ipdev

followmsi

Senior Member
Oct 10, 2013
4,101
12,336
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
 

Tuxianer1988

Member
Jan 30, 2021
10
2
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?
 
  • Like
Reactions: Voldo X

Voldo X

New member
Dec 19, 2017
1
0
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?
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.
 

killeriq

Senior Member
Dec 10, 2008
179
23
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
 

ipdev

Recognized Contributor
Feb 14, 2016
1,497
1
1,864
Google Nexus 10
Nexus 7 (2013)
Does anyone else have experience that says SELinux is disabled?
Hi. :)

For now, we are still SELinux Permissive.

For more on SELinux.
See Post # 3,286 - Link and Post # 3,372 - Link

Just installed using this awesome guide. Everything is working generally. Thanks!

I passed SafetyNet but still couldn't install Netflix.
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:
 
Last edited:
  • Like
Reactions: followmsi

ipdev

Recognized Contributor
Feb 14, 2016
1,497
1
1,864
Google Nexus 10
Nexus 7 (2013)
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
Hi. :)

The TWRP 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

The recovery.log file should also be included in the OpenGApps log files.
OpenGApps saves the logs in the directoy it is being installed from or the root of sdcard.

There has been comments across Redit, TeleGram, and xda about the last few builds of OpenGApps.
I belive most have droped back to the 0724 builds if I remember correctly.

You only need to partition once.
If you ran claymor's then you do not need to run another.

If Lineage 18 installed correctly, then you have a larger system partition.
The stock system partition is 840M. Lineage 18 builds using 1100M (1.1G) so it can not fit on the stock partition.

Cheers. :cowboy:
 
  • Like
Reactions: followmsi

bleuiko

Senior Member
Jan 29, 2007
354
46
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:

Nice! Clearing the cache did the trick in the play store!
 
  • Like
Reactions: ipdev

Tuxianer1988

Member
Jan 30, 2021
10
2
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.
Anybody having an idea this issue can be solved? I tried the office APK which installed fine not via play store but for paid games (which you don't download via an APK mirror) this is a pitty.

Cheers
 
  • Like
Reactions: Voldo X

mimo_007007

New member
Aug 4, 2021
1
0
is there is a way to run whats app on it when i try it stuck on writing phone number
and get me message to edit or return to type number
os lineage18.1
device nexus seven 2013 (flox)
 

Top Liked Posts