[ROM][DISCONTINUED][10] LineageOS 17.1 [deb][flo]

Search This thread
By:
Advanced…
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,528
1
5,102
Google Nexus 10
Nexus 7 (2013)
MorpheusUK said:
I've read a few posts on the flox thread suggesting that people successfully did a dirty upgrade from the unofficial rom (having repartitioned in the past using clamour for unofficial ROMs) they seem to indicate the opposite and all that was required was:

1. Flash the TWRP flox recovery

2. Flash official flox signed zip

3. (Possibly optional) Flash LOS flox recovery if you want to use the internal updater to automatically install downloaded updates.



So is the above possible? I'd rather not have to reflash magisk and do a Migrate backup just to move to the official build which only seems to provide SELinux support above this one. AFAIK it can't repetition without erasing all existing data. Netflix and a few other things were working on the unofficial build when I last checked although I don't use them on here much anyway so not quite sure what advantages the move to official actually would bring. Are the unofficial builds going to stop which will make this necessary?.



Thanks.
Click to expand...
Click to collapse

The unofficial is built on a 1.1G system partition.
The official is built on a 1.5G system partition.

The stock partition table for flo/deb.
Pastebin - Link

To be safe, a lot of us only used system, cache and a bit of unallocated space to (re)partition.
So we have a 1.2G to 1.3G system partition depending on how we did it.

Clamor's script to (re)partition is a more complicated.
If you use that method, you will have a 1.5G system.
Along with creating vendor on partition 30.
Then adding partition 31 for userdata.

--

The official install instructions use Clamor's partition script to prepare the device for install.
LineageOS flox Wiki - Link

If you used Clamor's script to (re)partition then you should be good to flash flo(x) without having to partition again.

Not sure what the difference is between the official TWRP and TWRP for flox is.
I am guessing it is based on the UA TWRP so it has support for the new partition layout.

As for switching from unofficial to the official build (as long as you used Clamor's script originally), the only problem would be build signature.
Not sure how pitrus- was signing his but, I assume the official is using LineageOS's signing key.

The TWRP for flox very well could allow you to update a rom using different signing keys.

Cheers. :cowboy:
 
  • Like
Reactions: MorpheusUK and osm0sis
H

happy4ya

Member
Dec 18, 2010
19
1
I have a N7 2013 with rooted 4.4.4 on it and I would like to upgrade. Main reason is more and more apps not wanting to install on this because the OS is too old. I have been reading about all the different modded roms and would like to install this one. I have some questions:

What's the deal with the "official" and "unofficial" versions? Just wondering what the difference is to determine which to go with. Also, I went to the "unofficial" downloads and see there is a version 16.0 and a 17.1 for each week. I couldn't find any info on the differences between them.

Why all the different weekly versions? Do they just continuously tweak them to fix bugs, or is it for other reasons? Do I just install the latest build and if it works good leave it alone, or do I have to keep updating?

Are these modded versions able to download any type of Android updates? Or is that why there is a new version every week? I know on my Samsung phone they push Android updates constantly, usually seems to be a lot of security patches. I'm guessing these modded versions don't get anything like that

Do I have to continuously keep flashing new versions as they come out? I'd like to flash something newer and stable, download a few apps I use, and hopefully just use it for a long time and not have to keep re-flashing new versions. In 6+ years, I don't think I've done anything to this tablet other than use it.

In the FAQ's in the beginning, it mentions having to do the repartiion due to the system partition being too small to fit both the rom and the GApps package. But the list of instructions does not mention when to do that step. When exactly should I do this? I'm guessing that would be the first step but would just like to confirm.

I have already unlocked the bootloader years ago and installed TWRP since I rooted the tablet, and recently upgraded TWRP to 3.5.0_9-0 so I'm guess I'm good up to that point. And I have no files on the tablet that need to be saved. Do I just do the repartition first, and then just go right to the step 2 in the instructions on the first page?

Also, I would like to keep root. Do any of these versions come rooted, or do I have to install Magisk or something else for this. And if I do, when does that (or whatever is needed for root access) get installed.

Sorry for all the questions. The last time I did this was years ago with a Motorola Xoom on Android 1.something. I have been reading through and searching for info but it is so scattered and I just want this to go smooth. I know I can easily do this but I also know that one skipped/crossed step can leave me with a paper weight. Any help would be greatly appreciated.

** I just noticed one other thing. On the page for the repartitioning files, they tell you to use the recovery on the page. It is version twrp-3.3.1-1_UA-flo, and I have a newer version (3.5.0_9-0) on the tablet. Should I flash the one on the page, or should I be ok with the newer one I already have?
 
Last edited:
  • Like
Reactions: lyushiK
M

MorpheusUK

Member
Mar 22, 2009
26
5
ipdev said:
The unofficial is built on a 1.1G system partition.
The official is built on a 1.5G system partition.

The stock partition table for flo/deb.
Pastebin - Link

To be safe, a lot of us only used system, cache and a bit of unallocated space to (re)partition.
So we have a 1.2G to 1.3G system partition depending on how we did it.

Clamor's script to (re)partition is a more complicated.
If you use that method, you will have a 1.5G system.
Along with creating vendor on partition 30.
Then adding partition 31 for userdata.

--

The official install instructions use Clamor's partition script to prepare the device for install.
LineageOS flox Wiki - Link

If you used Clamor's script to (re)partition then you should be good to flash flo(x) without having to partition again.

Not sure what the difference is between the official TWRP and TWRP for flox is.
I am guessing it is based on the UA TWRP so it has support for the new partition layout.

As for switching from unofficial to the official build (as long as you used Clamor's script originally), the only problem would be build signature.
Not sure how pitrus- was signing his but, I assume the official is using LineageOS's signing key.

The TWRP for flox very well could allow you to update a rom using different signing keys.

Cheers. :cowboy:
Click to expand...
Click to collapse
Thanks, I'll give that a try, I guess like a few of us I originally partitioned with Clamor's script possibly even for the unofficial 16.0 builds initially (it was a long time ago). I just confirmed my 1.5GB system partition size using DiskInfo from the Play store (enable expert mode -> device mapper partitions in settings to see the system partition) in case anybody else wants to check their system.
 
  • Like
Reactions: ipdev
M

MorpheusUK

Member
Mar 22, 2009
26
5
happy4ya said:
I have a N7 2013 with rooted 4.4.4 on it and I would like to upgrade. Main reason is more and more apps not wanting to install on this because the OS is too old. I have been reading about all the different modded roms and would like to install this one. I have some questions:

What's the deal with the "official" and "unofficial" versions? Just wondering what the difference is to determine which to go with. Also, I went to the "unofficial" downloads and see there is a version 16.0 and a 17.1 for each week. I couldn't find any info on the differences between them.

Why all the different weekly versions? Do they just continuously tweak them to fix bugs, or is it for other reasons? Do I just install the latest build and if it works good leave it alone, or do I have to keep updating?

Are these modded versions able to download any type of Android updates? Or is that why there is a new version every week? I know on my Samsung phone they push Android updates constantly, usually seems to be a lot of security patches. I'm guessing these modded versions don't get anything like that

Do I have to continuously keep flashing new versions as they come out? I'd like to flash something newer and stable, download a few apps I use, and hopefully just use it for a long time and not have to keep re-flashing new versions. In 6+ years, I don't think I've done anything to this tablet other than use it.

In the FAQ's in the beginning, it mentions having to do the repartiion due to the system partition being too small to fit both the rom and the GApps package. But the list of instructions does not mention when to do that step. When exactly should I do this? I'm guessing that would be the first step but would just like to confirm.

I have already unlocked the bootloader years ago and installed TWRP since I rooted the tablet, and recently upgraded TWRP to 3.5.0_9-0 so I'm guess I'm good up to that point. And I have no files on the tablet that need to be saved. Do I just do the repartition first, and then just go right to the step 2 in the instructions on the first page?

Also, I would like to keep root. Do any of these versions come rooted, or do I have to install Magisk or something else for this. And if I do, when does that (or whatever is needed for root access) get installed.

Sorry for all the questions. The last time I did this was years ago with a Motorola Xoom on Android 1.something. I have been reading through and searching for info but it is so scattered and I just want this to go smooth. I know I can easily do this but I also know that one skipped/crossed step can leave me with a paper weight. Any help would be greatly appreciated.

** I just noticed one other thing. On the page for the repartitioning files, they tell you to use the recovery on the page. It is version twrp-3.3.1-1_UA-flo, and I have a newer version (3.5.0_9-0) on the tablet. Should I flash the one on the page, or should I be ok with the newer one I already have?
Click to expand...
Click to collapse
Ok I'll try and answer some of your questions as best I can and I'm sure somebody will correct me if I get anything wrong about the differences between official and unofficial in practical terms.

The weekly unofficial 16.0 builds are Android 9 and 17.1 Android 10. I used the Android 9 ones for about a year or so before switching to 10 which I've again been using for around the same period (I don't normally root). They both worked well for me during that time but if you want to use Netflix for example you have to download a specific APK version and sideload it so that it works. From my understanding that might be related to the difference between the official and unofficial. The officials support SELinux, are signed by LineageOS (unofficial builds you basically have to trust the developer is not doing anything dodgy or their servers haven't been comprised) and will pass Google's SafetyNet checks (which is what stops the normal Netflix and some other things from working on unofficial builds which won't pass by default).

The unofficial build has a built in updater which you can just click on to get the download the latest build and install it. I do this once a month around the middle of the month to get the latest Android security patches. It isn't necessary to do so each week. If you look at the changelogs you will see that there are constant updates to the code how relevant all of these are to a Nexus 7 2013 is another matter as LOS supports multiple devices. The main updates you should be interested in are the monthly security updates from Google that get merged into LOS, so yes it gets those.

On the first page of this thread is a link that takes you to a page that describes how to repartition (IIRC it describes the process using Clamor's script which I reference in my post above).

I know the TWRP UA version supports the modified partition sizes. I currently have that version installed although I believe there are later versions of the TWRP UA versions. That was the latest TWRP at the time this thread started IIRC. I think I remember reading that the official TWRP 3.4 and above also supported the larger partitions but I can't swear to that.

I briefly rooted to use Migrate to restore my apps data backup from the 16.0 build when I moved to 17.1. You will need to install Magisk (I used 20.4 which was the current version at that time) if you want root. It's straightforward enough once you have flashed LOS and Open GApps then flash Magisk. As I said above I generally don't run rooted as I find little advantage day to day so I unrooted after restoring my backup.

I'm afraid I don't know a lot about the new official build as I only spotted it's existence a couple of days ago hence my questions above but somebody else maybe able to tell you more about that so that you can decide which to install.

Hope this helps.

Edited: Fix typos
 
Last edited:
P

pfout

Member
Nov 5, 2012
8
0
Anyone have issues with the front camera? Rear one works fine but can't switch to the front in the default app or any other camera app.

Clean install on a nexus 7 (that was running LOS 15) btw
 
M

MorpheusUK

Member
Mar 22, 2009
26
5
MorpheusUK said:
Thanks, I'll give that a try, I guess like a few of us I originally partitioned with Clamor's script possibly even for the unofficial 16.0 builds initially (it was a long time ago). I just confirmed my 1.5GB system partition size using DiskInfo from the Play store (enable expert mode -> device mapper partitions in settings to see the system partition) in case anybody else wants to check their system.
Click to expand...
Click to collapse
Just a little feedback I've dirty flashed the official as per the steps I described in my earlier post:

1. Flash the TWRP flox recovery
2. Flash official flox signed zip
3. Flash Open GApps
4. (Optional) Flash LOS flox recovery

So far so good all looks well and SELinux is enforcing.
 
  • Like
Reactions: ipdev
R

rudolph323

Senior Member
Sep 9, 2014
108
15
LeEco Le Pro3
I updated to latest version (lineage-17.1-20210203), installed nano gapps over it and magisk and now it just boot loops to LOS loading screen and then turns off and boots into recovery... I successfully turned on after installing, but the next time it stopped working and continues to crash and boot into twrp.
 
Last edited:
  • Like
Reactions: kozmo2k4
kozmo2k4

kozmo2k4

Senior Member
Nov 4, 2010
443
147
Nature Coast
Nexus 7
Sprint Samsung Galaxy S4
rudolph323 said:
I updated to latest version (lineage-17.1-20210203), installed nano gapps over it and magisk and now it just boot loops to LOS loading screen and then turns off and boots into recovery... I successfully turned on after installing, but the next time it stopped working and continues to crash and boot into twrp.
Click to expand...
Click to collapse
Similar here, deb, previously on LOS17.1-20210115, used updater to install 20210202 this morning. Started to bootloop, so I shut it off.
Now that I got back home and powered it back on, still bootloops, but after about 5 minutes, it just boots in to TWRP.
Tried wiping cache, side-loaded 20210203 (verified hash) from my laptop and flashed it, but same result.
Interesting....
 
  • Like
Reactions: rudolph323
R

rudolph323

Senior Member
Sep 9, 2014
108
15
LeEco Le Pro3
kozmo2k4 said:
Similar here, deb, previously on LOS17.1-20210115, used updater to install 20210202 this morning. Started to bootloop, so I shut it off.
Now that I got back home and powered it back on, still bootloops, but after about 5 minutes, it just boots in to TWRP.
Tried wiping cache, side-loaded 20210203 (verified hash) from my laptop and flashed it, but same result.
Interesting....
Click to expand...
Click to collapse

I guess the only option now is to wipe everything.
I already wiped system and installed various versions of this LOS, earliest one I could get is from 22 January. Nothing worked.

EDIT:
I backed up data partition in TWRP, wiped everything except internal storage and installed LOS+GAPPS+Magisk again, now everything works.
But to restore TWRP Nandroid backup data partition you need titanium backup pro version to extract app data and have apps preinstalled already you want to restore.
 
Last edited:
  • Like
Reactions: kozmo2k4
kozmo2k4

kozmo2k4

Senior Member
Nov 4, 2010
443
147
Nature Coast
Nexus 7
Sprint Samsung Galaxy S4
The way I got the tablet out of the bootloop:
In TWRP, formated System, Dalvik, and Cache partitions.
Sideloaded latest LoS-17.1-20200203, latest gApps Pico. Rebooted it, it did get past the bootanimation, got the Welcome screen with Finish Setup notification; I just let it sit for about half an hour without even opening it. The rebooted back to recovery, flashed latest Magisk.
After reboot, it went in to the screen lock, and after unlocking it, it was in the default launcher (Trebuchet?). To my surprise, all my apps were still there. The only one that started to crash immediately, was Hangouts, which I uninstalled after that.
Everything works now, without problems; so far.
 
J

jhford

Senior Member
Oct 28, 2005
838
140
Nexus 7 (2013)
Amazon Fire HD 8 and HD 10
I have 3 debs - call me crazy, and the sound suddenly disappeared on 2 of them, which is really odd. The only thing I can think of is that I recently installed a volume boosting app to make WWVB louder. So, I uninstalled it, but still no sound. I can't figure out if it's a hardware or software problem. Any ideas?
 
M

machineabuse

New member
Sep 28, 2012
2
0
Nexus 7 LTE user here,

Flashed the repartition image and executed it in terminal, wiped and proceeded to install the recommended TWRP, then doing a complete wipe before installing lineage-17.1-20210208-UNOFFICIAL-deb.zip and open_gapps-arm-10.0-pico-20210209.zip, wipe dalvik and reboot.

After watching the lineage loading screen for a few minutes the device reboots itself back into TWRP. Issue replicated identically after fresh formats and installs 3 times. Any ideas what I'm doing wrong?

Footnote: I also tried the recently posted 18.1 build along with the arm-11 GAPPs, that one just stayed on the boot screen for an hour before I chose to abort it, fairly confident it's not going to boot into the OS.

Update: Got it to boot after a dirty install, I didn't format this time and I didn't clear the dalvik cache. I also skipped the install of the TWRP app.
 
Last edited:
P

pixel2404

Member
Nov 4, 2020
13
0
Hi@all,

thank you for reviving the Nexus 7. it's a good device. Even after years :). Good job!

I am not a professional but I try my best. I probably did something wrong :-(

I have carried out the following steps:
  • Device rooted and stock ROM installed
  • install twrp-3.4.0-0-deb.img
  • install flo-deb_clamor_repartition.zip and execute
  • Advanced Wipe with all options
  • format all
  • install lineage-17.1-20210223-UNOFFICIAL-deb
  • install open_gapps-arm-10.0-tvstock-20210224.zip

After that, I also have the problem that the boot animation runs for a long time and then I end up back in TWRP. I have repeated this several times. If I leave out the GApps, it works without problems.

machineabuse said:
Update: Got it to boot after a dirty install, I didn't format this time and I didn't clear the dalvik cache. I also skipped the install of the TWRP app.
Click to expand...
Click to collapse
Unfortunately, I only read that today.

LA 17.1 runs well on the device. I have also used it for a week without any problems. Is there a possibility to install the GApps later or will the device be completely reset?

with best
 
D

DCvan

Senior Member
Aug 4, 2017
92
55
Vancouver
pixel2404 said:
Hi@all,

thank you for reviving the Nexus 7. it's a good device. Even after years :). Good job!

I am not a professional but I try my best. I probably did something wrong :-(

I have carried out the following steps:
  • Device rooted and stock ROM installed
  • install twrp-3.4.0-0-deb.img
  • install flo-deb_clamor_repartition.zip and execute
  • Advanced Wipe with all options
  • format all
  • install lineage-17.1-20210223-UNOFFICIAL-deb
  • install open_gapps-arm-10.0-tvstock-20210224.zip

After that, I also have the problem that the boot animation runs for a long time and then I end up back in TWRP. I have repeated this several times. If I leave out the GApps, it works without problems.


Unfortunately, I only read that today.

LA 17.1 runs well on the device. I have also used it for a week without any problems. Is there a possibility to install the GApps later or will the device be completely reset?

with best
Click to expand...
Click to collapse
Gapps pico works fine. Give it ago.
 
J

jhford

Senior Member
Oct 28, 2005
838
140
Nexus 7 (2013)
Amazon Fire HD 8 and HD 10
I made a side trip and did a clean install of IP99's personal build of LOS 17.1. It seems OK, but only some of the root folders are visible using File Manager+. So, I'd like to return to Ripee's 17.1. Can I dirty flash it since 17.1 is currently installed, anyway, or should I do a clean install?
Thanks
 
Last edited:
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,528
1
5,102
Google Nexus 10
Nexus 7 (2013)
jhford said:
I made a side trip and did a clean install of IP99's personal build of LOS 17.1. It seems OK, but only some of the root folders are visible using File Manager+. So, I'd like to return to Ripee's 17.1. Can I dirty flash it since 17.1 is currently installed, anyway, or should I do a clean install?
Thanks
Click to expand...
Click to collapse
That is odd. :unsure:
What files can you not access as root?

Sounds like something did not install correctly, something is corrupted or a File Manager+ issue.

I run builds using followmsi's manifest.
Lineage 17.1 flo-deb GitHub - Link
Builds are test-keys

As far as I know, Ripee is not running builds for flo/deb.

The links in the OP are to pitrus-'s builds.
pitrus- was running builds using followmsi's manifest.

Unless pitrus- changed something or started signing the builds differently, you should be able to flash mine and his over each other.

Cheers. :cowboy:
 
J

jhford

Senior Member
Oct 28, 2005
838
140
Nexus 7 (2013)
Amazon Fire HD 8 and HD 10
ipdev said:
That is odd. :unsure:
What files can you not access as root?

Sounds like something did not install correctly, something is corrupted or a File Manager+ issue.

I run builds using followmsi's manifest.
Lineage 17.1 flo-deb GitHub - Link
Builds are test-keys

As far as I know, Ripee is not running builds for flo/deb.

The links in the OP are to pitrus-'s builds.
pitrus- was running builds using followmsi's manifest.

Unless pitrus- changed something or started signing the builds differently, you should be able to flash mine and his over each other.

Cheers. :cowboy:
Click to expand...
Click to collapse
You must be IP99. If so, I did a clean install, as I did with Ripee/Pitrus before, and all other Roms I've flashed, as follows:
  • I went back to pure stock with Wugfresh.
  • I booted TWRP and did a wipe to stock, Advanced wipe checking all boxes, and formatted the data partition.
  • Flashed your deb 17.1, Gapps Pico, Magisk, and Migrate to bulk install all my apps.
  • Wiped Dalvik & Cache.
  • Booted system.
  • Finished the Android installation
  • Ran the Migrate helper app to install my apps.
  • Setup Magisk
But, for the first time ever, I did not get a prompt to give File Manager+ superuser privileges. I got the prompt for Root Explorer, but it doesn't display any root folders either. So, I uninstalled and reinstalled both and nothing changed.

This flashing procedure has always worked, but failed when I flashed your build. I'm not blaming you - I'm just stumped. That's why I thought I should try the Ripee/Pitrus 17.1 build again even though I like yours.

As an aside, I'm a bit leery of 18.1. What do you think?

I appreciate any help. Thanks
 
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,528
1
5,102
Google Nexus 10
Nexus 7 (2013)
jhford said:
You must be IP99. If so, I did a clean install, as I did with Ripee/Pitrus before, and all other Roms I've flashed, as follows:
  • I went back to pure stock with Wugfresh.
  • I booted TWRP and did a wipe to stock, Advanced wipe checking all boxes, and formatted the data partition.
  • Flashed your deb 17.1, Gapps Pico, Magisk, and Migrate to bulk install all my apps.
  • Wiped Dalvik & Cache.
  • Booted system.
  • Finished the Android installation
  • Ran the Migrate helper app to install my apps.
  • Setup Magisk
But, for the first time ever, I did not get a prompt to give File Manager+ superuser privileges. I got the prompt for Root Explorer, but it doesn't display any root folders either. So, I uninstalled and reinstalled both and nothing changed.

This flashing procedure has always worked, but failed when I flashed your build. I'm not blaming you - I'm just stumped. That's why I thought I should try the Ripee/Pitrus 17.1 build again even though I like yours.

As an aside, I'm a bit leery of 18.1. What do you think?

I appreciate any help. Thanks
Click to expand...
Click to collapse

ip99 actually. ;)
I offered my builds awhile back when the deb/flo builds disapeared from pitrus-'s server.
Post # 653 - Link

---

That would not be an issue with the rom, more like an issue with root.
  • Magisk is borked
  • The app is not requesting root access.
  • Something is not getting restored properly with Migrate.
  • ¯\_(ツ)_/¯

I checked File Manager +
PlayStore - Link

Installed File Manager +
  • Enabled the Root access mode in settings.
  • Opened / and got prompted by Magisk to allow or deny. (Granted permission)
    Root directory was displayed and I could navigate all the directories.​
Since my deb was on l18.1, I did a clean install of l17.1 to check.
l17.1 (20210207-deb), OpenGApps (pico), Magisk (canary).

It worked fine on both l18.1 and l17.1.

---

As for Lineage 18.1

The Lineage team is still working on 18.1 but, it is pretty solid right now.
They have fixed a bunch of issues in the last few months.

I have been running l18.1 on my test flo since the beginning.
It actually did not boot yet at that time. ;)​
Started testing on deb once flo was booting and the big issues were fixed.

Since December, l18.1 has been pretty stable for deb/flo.

Only thing that held me back from moving to l18.1 was a gapps issue that was solved at the end of January.
OpenGApps GitLab - Commit

I did a clean flash of l18.1 on my main (daily use) flo after the gapps issue was fixed. ;)

followmsi did a great job at bringing Lineage 18.x to deb/flo.

---

Cheers. :cowboy:
 
Last edited:
kozmo2k4

kozmo2k4

Senior Member
Nov 4, 2010
443
147
Nature Coast
Nexus 7
Sprint Samsung Galaxy S4
I got a bootloop, again, after updating to the latest deb 03102021 version. Not my flo.
If anyone else gets a bootloop after using the System Updater to install the newest version, don't panic.
Let the tablet loop, it will rebot in to TWRP eventually. If not, force shut it down, and boot in to TRWP. On a computer, download the latest zip and latest OpenGapps. From there, just sideload install both, then wipe dalvik and cache, and you deb will/should boot properly. No need to go full nuclear, wipping the whole tablet...
 
  • Like
Reactions: rudolph323
osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,660
35,407
Halifax
GT-i9250
Google Nexus 4
Last edited:
  • Like
Reactions: ipdev
You must log in or register to reply here.

Similar threads

followmsi
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
Replies
4K
Views
976K
osm0sis
osm0sis
Scott
  • Locked
[ROM][10/27] CleanROM 7.1 -★| Marshmallow! | MRA58U !| Aroma! | Clean! | Stable! |★-
Replies
7K
Views
1M
Scott
Scott
ripee
[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo]
Replies
666
Views
219K
lyushiK
lyushiK
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

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 54
    ripee
    ripee
    android-nowe-logo-1.png


    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-17.1 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.3. Simply flash the linked below version 3.3 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: There are no plans to submit these builds for official LineageOS support, but it should not matter. What is most important is that these unofficial builds be stable enough for daily usage, which they are, thanks to followmsi's tireless work in porting Android 10 to these venerable old tablets.
    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: Even if neither dev nor flo will ever receive official LineageOS support, just out of curiosity, what are some of the differences be between unofficial and official builds?
    A: The following technical changes are in effect:
    - Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
    - Tablet 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.

    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, as per followmsi's advice.


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


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

    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
    - 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 17.1, ROM for the Nexus 7 (2013)

    Contributors
    ripee, followmsi, pitrus-, flex1911, Clamor
    ROM OS Version: Android 10
    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: 10
    Stable Release Date: 2020-01-21

    Created 2020-01-21
    Last Updated 2020-04-14
    View
    10
    followmsi
    followmsi
    edison0354 said:
    Is LineageOS seperated from AospExtended in the other thread?
    Click to expand...
    Click to collapse


    https://forum.xda-developers.com/showpost.php?p=81555475&postcount=2938

    Lineage-17.1

    Like mentioned before .. I did plan to handover Lineage-17.1 beginning of 2020.
    That's done now.

    @ripee will continue to build regular lineage-17.1 builds for flo/deb.

    If there are some code changes in the next time .. we test on AEX first and apply changes to Lineage sources later on.

    Thanks to @ripee for taking over !

    Cheers
    View
    10
    ripee
    ripee
    Changelog

    Build 0122 for both variants
    * NFC is fixed, courtesy of followmsi.
    * Synced with LineageOS sources.
    View
    6
    lollyjay
    lollyjay
    tomatosauce said:
    Looking for the flo build, thanks!
    Click to expand...
    Click to collapse
    Try this one
    https://drive.google.com/file/d/17XhZZwKDYJsaKSn0fS9a-c4wWze-2u5a/view?usp=drivesdk
    Regards

    Sent from my OnePlus7Pro using XDA Labs
    View
    5
    ripee
    ripee
    olliebean said:
    FWIW, if you are trying to download a file from Google Drive that has been restricted in this way and you have a Google account yourself, you can work around the blocked download by adding the file to your own Google Drive, making a copy of it, and downloading the copy.
    Click to expand...
    Click to collapse

    Along those lines, you can also add the folder of your variant to your own Google Drive. That way, all future builds will sync down to your account automatically.
    View

New posts