[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo]

Search This thread
By:
Advanced…
M

maruchandd

Member
Dec 22, 2017
47
14
rho-bot said:
Have you repartitioned the device before flashing revovery?
If not, then try with official TWRP from here first https://dl.twrp.me/flo/
Then repartition, then update TWRP to the one above (it is bigger than the original one).
Click to expand...
Click to collapse

I have not tried repartitioning yet because the guides recommend you have at least 3.3.1.0 installed before you try to run the partition script. are you sure repartitioning in my current 2.8.x.x version will be ok?

pitrus- said:
You should follow Clamors repartition guide here

https://forum.xda-developers.com/ne...repartition-nexus-7-2013-repartition-t3844386

Check out my LOS daily builds at https://lineageos.wickenberg.nu
Click to expand...
Click to collapse

thanks for the reply, I did go there and some suggested it's important to use the latest version of twrp before partitioning. Would it be ok to try to repartition it with my older version of twrp as above quoted user recommends? if not i need to get twrp updated first somehow

any suggestions on what I should wipe or clean in order to potentially fix this error and allow upgrading recovery flash version of twrp without bricking it?

EDIT: I managed to get it working, description is here https://forum.xda-developers.com/showpost.php?p=81818907&postcount=272

IT turned out repartitioning the device was not necessary, the newest twrp installed and works without having done any repartition
 
Last edited:
pitrus-

pitrus-

Senior Member
Sep 4, 2011
1,278
575
Östersund
www.wickenberg.nu
maruchandd said:
I have not tried repartitioning yet because the guides recommend you have at least 3.3.1.0 installed before you try to run the partition script. are you sure repartitioning in my current 2.8.x.x version will be ok?







thanks for the reply, I did go there and some suggested it's important to use the latest version of twrp before partitioning. Would it be ok to try to repartition it with my older version of twrp as above quoted user recommends? if not i need to get twrp updated first somehow



any suggestions on what I should wipe or clean in order to potentially fix this error and allow upgrading recovery flash version of twrp without bricking it?
Click to expand...
Click to collapse
As long as your version of TWRP isn't from the time the dinosaurs roamed this planet, you should just do as in the clamor guide, that's what I did and it worked fine and therefore I've never had to do it again as my device is future proof.

After repartitioning your have to at a bare minimum use the old special made TWRP as in the guide, but even better is to user the latest official as it handles repartitioned devices.

From there skies the limits what you do with your Nexus 7 2013. [emoji451]

Check out my LOS daily builds at https://lineageos.wickenberg.nu
 
A

anivegmin

Member
Mar 29, 2019
48
23
Just installed this ROM and everything seems to be working fine but just checking in security settings I noticed that SELinux is disabled. Is this normal for this ROM or an error on my device? Can it be enabled? Thanks.
 
pitrus-

pitrus-

Senior Member
Sep 4, 2011
1,278
575
Östersund
www.wickenberg.nu
anivegmin said:
Just installed this ROM and everything seems to be working fine but just checking in security settings I noticed that SELinux is disabled. Is this normal for this ROM or an error on my device? Can it be enabled? Thanks.
Click to expand...
Click to collapse
Accomplishing SELinux on older devices with outdated blobs and shims for making things work is if not impossible, more like painting Mona Lisa. If we would enable it, it would most probably break lots of functions.

Check out my LOS daily builds at https://lineageos.wickenberg.nu
 
  • Like
Reactions: defim, remedya and JT1510365
N

nneul

New member
Feb 29, 2020
1
0
Don't install TWRP when rebooting

After beating my head against the wall on this with it getting stuck on boot logo animation and then rebooting to recovery -- finally saw schnee1's post #615

That solved the problem instantly and it now works smoothly.
 
A

anivegmin

Member
Mar 29, 2019
48
23
pitrus- said:
Accomplishing SELinux on older devices with outdated blobs and shims for making things work is if not impossible, more like painting Mona Lisa. If we would enable it, it would most probably break lots of functions.

Check out my LOS daily builds at https://lineageos.wickenberg.nu
Click to expand...
Click to collapse
Thanks for the reply. I didn't realise the situation with SELinux. I don't really understand these things. I've installed this ROM thinking I was getting an up to date system security wise, as 14.1 for Flo doesn't seem to be available anywhere anymore. To what extent is security compromised by having SELinux disabled? Thanks.
 
pitrus-

pitrus-

Senior Member
Sep 4, 2011
1,278
575
Östersund
www.wickenberg.nu
anivegmin said:
Thanks for the reply. I didn't realise the situation with SELinux. I don't really understand these things. I've installed this ROM thinking I was getting an up to date system security wise, as 14.1 for Flo doesn't seem to be available anywhere anymore. To what extent is security compromised by having SELinux disabled? Thanks.
Click to expand...
Click to collapse
Theoretically the system is of course more exposed without Security Enhanced Linux mode active. However having your device rooted is what really opens up your device, if you're not careful that is. You have to download something containing that contains dangerous code that in turn could download more (download trojan).

So as long as you don't expose your device to dangerous apps and downloads from shady parts of the internet you should be safe. [emoji3526]

Even though the vendor security updates stay the same old, you get all the security updates of the newer LineageOS so it's still better than staying on an older build with SELinux.

Check out my LOS daily builds at https://lineageos.wickenberg.nu
 
Last edited:
  • Like
Reactions: anivegmin and ipdev
A

anivegmin

Member
Mar 29, 2019
48
23
pitrus- said:
Theoretically the system is of course more exposed without Security Enhanced Linux mode active. However having your device rooted is what really opens up your device, if you're not careful that is. You have to download something containing that contains dangerous code that in turn could download more (download trojan).

So as long as you don't expose your device to dangerous apps and downloads from shady parts of the internet you should be safe. [emoji3526]

Even though the vendor security updates stay the same old, you get all the security updates of the newer LineageOS so it's still better than staying on an older build with SELinux.

Check out my LOS daily builds at https://lineageos.wickenberg.nu
Click to expand...
Click to collapse

Thanks very much for explaining that for me. The ROM is great, no problems that I've noticed. Everything is snappy, battery life is excellent. Also the compass is working which was always a problem on anything post 14.1 that I've tried before. Thanks for all the work keeping these older devices alive.
 
M

maruchandd

Member
Dec 22, 2017
47
14
nneul said:
After beating my head against the wall on this with it getting stuck on boot logo animation and then rebooting to recovery -- finally saw schnee1's post #615

That solved the problem instantly and it now works smoothly.
Click to expand...
Click to collapse


I was prepared to wait another 25 minutes :eek: but after turning this off (you can disable it in TWRP advanced menu you don't even have to do a wipe/fresh install to disable it at the prompt, as i was expecting to have to do) it booted up in seconds

schnee1 said:
Thanks for the help. I grabbed some logs if somebody interested i can share it. After grabbing the logs i was able to resolve the issue as on other forums i read that installing TWRP on the boot could cause such issues. I disabled TWRP installation and the tablet booted normally. I will play with the settings if it happens always or only if i install the app as system app.
Click to expand...
Click to collapse

i also had to remove the app from within twrp to get it to stop the incessant boot animation
 
Last edited:
  • Like
Reactions: ipdev
O

oneprivy

Member
May 15, 2019
17
2
Bug 1 : stuttering when pressing multitasking button and swiping through open apps. (Clean install, no openGapps, no root)
Bug 2 : flashing the addonsu doesn't give root access

Question 1 : Can I flash magisk on this rom ? and How ? (last time I did it after clean install and it ended up in a bootloop)
Question 2 : Is there a way to dirty install without getting in a bootloop ? (last time I "dirty" updated a rom I ended up losing all data)
OR to update without losing system preferences, app data, without having to reinstall apps... ?
Question 3 : Can I use the stock system updater ?
 
pitrus-

pitrus-

Senior Member
Sep 4, 2011
1,278
575
Östersund
www.wickenberg.nu
oneprivy said:
Bug 1 : stuttering when pressing multitasking button and swiping through open apps. (Clean install, no openGapps, no root)
Bug 2 : flashing the addonsu doesn't give root access

Question 1 : Can I flash magisk on this rom ? and How ? (last time I did it after clean install and it ended up in a bootloop)
Question 2 : Is there a way to dirty install without getting in a bootloop ? (last time I "dirty" updated a rom I ended up losing all data)
OR to update without losing system preferences, app data, without having to reinstall apps... ?
Question 3 : Can I use the stock system updater ?
Click to expand...
Click to collapse

I suspect there's not much we can do about stuttering on this device, CPU performance and RAM is limited compared to other devices running Android 9 or 10. Also addonsu is not supported on 10 and forward so Magisk is the proper root method.

When flashing latest Magisk stable from XDA thread, make sure to have latest TWRP and also boot device one time and set it up, then reboot and flash Magisk zip and reboot again and it should work out fine as long as your device has been partition resized using clamor zip. Also make sure you're using Opengapps nano package and not any of the larger ones.

Built-in updater should work, however the json OTA server I've been using doesn't seem to like when LOS16 and LOS17 builds ends up in the same folder breaking built-in OTA and I haven't had the time to fine one that does support different LOS for multiple devices.

Check out my LOS daily builds at https://lineageos.wickenberg.nu
 
  • Like
Reactions: kozmo2k4 and ipdev
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,526
1
5,085
Google Nexus 10
Nexus 7 (2013)
Hi all.
Just a quick PSA.
Regardless of your device/rom..
Nexus, Pixel, some off brand or even a new OnePlus or SamSung device.
You can adjust the animation scale under Setting-> Developer options Drawing.

Normally changing from 1.x to 0.5x speeds up the display without notice.
Animation off would be the extreme. (Noticeably Flat like AndroidGO.)
Play with it a little bit and see what you need to change.
If memory serves correct, normally changing Window and Transition to .5 is all that is needed.

Outside of that, the gradual bough down in LineageOS 15/16 has been noted across different (older) device threads. Lineage 17 seems to be less so far but, time will tell.

Cheers all. :cowboy:
 
Last edited:
  • Like
Reactions: metaxda
pitrus-

pitrus-

Senior Member
Sep 4, 2011
1,278
575
Östersund
www.wickenberg.nu
kozmo2k4 said:
Hi @pitrus. Is the update server down? Can't access it in browser, shows " 502: Bad gateway"



Check out my LOS daily builds at https://lineageos.wickenberg.nu
Click to expand...
Click to collapse
Yeah, sorry. I ran out of disk space completely on the build server. Redid storage as Raid0 and I'm currently restoring the machine from backup which will probably take some time until done as it's 550GB in total. [emoji23]
 
Last edited:
  • Like
Reactions: makey404 and kozmo2k4
kozmo2k4

kozmo2k4

Senior Member
Nov 4, 2010
443
147
Nature Coast
Nexus 7
Sprint Samsung Galaxy S4
pitrus- said:
Yeah, sorry. I ran out of disk space completely on the build server. Redid storage as Raid0 and I'm currently restoring the machine from backup which will probably take some time until done as it's 550GB in total. [emoji23]
Click to expand...
Click to collapse
Oh, I feel ya. Last couple of days/nights I was migrating my media (around 8TB) to new OpenMediaVault server. Build. And instead of RAID, I wanted to try my hands MergeFS, so there was a slight learning curve... Running smooth now, with Jellyfin and other stuff in Docker. Fun times...
Thanks for all you do in this community!
 
  • Like
Reactions: pitrus-
You must log in or register to reply here.

Similar threads

followmsi
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
Replies
4K
Views
975K
osm0sis
osm0sis
ripee
[ROM][DISCONTINUED][10] LineageOS 17.1 [deb][flo]
Replies
718
Views
193K
kozmo2k4
kozmo2k4
Scott
[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1
Replies
2K
Views
367K
S
Suici Doga
zaclimon
[ROM][OFFICIAL][KitKat 4.4.4][Flo/Deb] PAC-man 4.4.4.RC-1
Replies
1K
Views
220K
Memo13v
Memo13v
BeansTown106
  • Locked
[ROM][6.0.1][FLO]★ The Pure Nexus Project ★ Substratum ★ [08/21/16]
Replies
1K
Views
325K
BeansTown106
BeansTown106

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 81
    ripee
    ripee
    android-p-logo.jpg


    LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
    ​

    Code: 
    * [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.


    FREQUENTLY ASKED QUESTIONS

    (Please read them BEFORE posting anything in the thread!)​
    Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
    A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.

    Q: I am seeing Error 7 when trying to flash a GApps package.
    A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.

    Q: When will any of the variants receive official builds from LineageOS?
    A: Not before all the issues listed under "Bugs" below are fixed.
    Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.

    Q: What will some of the differences be between unofficial and official builds?
    A: The following technical changes will take effect:
    - Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
    - Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
    - The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
    Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.

    Q: How often will new builds be released?
    A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.


    [REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]


    ROMs
    pitrus-
    - LTE: deb
    - Wi-Fi: flo

    LineageOS Extras
    - addonsu-16.0-arm-signed.zip
    - addonsu-remove-16.0-arm-signed.zip

    Magisk

    Open GApps



    How to flash LineageOS and Open GApps​
    1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
    2. Download your LineageOS Rom and GApps Package,
    3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
    4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
    5. Swipe to Wipe at Bottom of Screen,
    6. Back to Main start screen,
    7. Wipe > Format Data,
    8. Type 'Yes' and press blue checkmark at the bottom-right corner,
    9. Go Back to Main Start Screen,
    10. Move your LineageOS Rom and GApps Package to the internal storage,
    11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
    11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
    12. Reboot System! Enjoy!


    Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.


    Problems known to happen after a Dirty Installation​
    1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.

    * Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.

    * Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.

    Bugs
    - Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
    - You tell us!

    Changelog
    All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.

    Credits
    - Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.

    Sources
    - deb device tree
    - flo device tree
    - kernel
    - blobs

    XDA:DevDB Information
    LineageOS 16.0, ROM for the Nexus 7 (2013)

    Contributors
    ripee, followmsi, pitrus-, flex1911, Clamor
    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.x
    ROM Firmware Required: System partition large enough to accommodate the rom and GApps.

    Version Information
    Status:     Stable
    Current Stable Version: 9
    Stable Release Date: 2019-08-11

    Created 2019-02-22
    Last Updated 2019-11-10
    View
    13
    ripee
    ripee
    Switching to pitrus-'s builds!

    I have updated the links in the OP to point to his folders. He builds with the same sources as I do, which are followmsi's repos linked at the bottom of the OP. It will be up to him how often he build for deb and flo, but I will continue to maintain this thread and answer questions. I am working on other devices right now and my build environment doesn't have the space to keep building for deb and flo, but rest assured I still have my flo tablet and will enthusiastically and regularly flash pitrus-'s builds.
    View
    12
    ripee
    ripee
    Reserved
    View
    12
    ripee
    ripee
    Reserved
    View
    10
    ripee
    ripee
    Changelog

    Build 0301 for both variants
    * Synced with LineageOS sources.

    Since today is the day that Pie has become official, it's a good day to build even though our tablets are not among the lucky few devices. You can be sure that the builds are stable enough as daily drivers, with the exception of NFC.
    View

New posts