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

[Fuzi0719]

Thank you!

I just wanted to say a big thank you for this ROM. I was running the previous Lineage 16 ROM on my FLO. It was good, but just rather slow. I didn't complain given the age of this tablet and its modern limitations. I held off upgrading it because I thought, "why bother?". But, on a slow day (they're all slow, lately, of course, this is 2020), I decided to do the upgrade to 17.1. I also decided to be brave and do a "dirty upgrade". I updated all the apps through Playstore, then connected to my desktop and did an adb sideload of the Lineage 17.1 ROM and the GAPPS nano release. Rebooted, let it settle for about 30 minutes, then rebooted again. This ROM is so much more "snappy" than 16, it's like a new tablet! Very impressed. So far, I have not had a single problem, been using Skymap (which uses GPS and compass), Amazon Kindle reader, Google News, rif (Reddit Is Fun), etc. I'm really pleased. Thank you, again!

 

[prsa01]

I wanted to make the best out of my old flo, which means: MicroG, the Google PlayStore, root support and an overclock kernel.
Getting all of this to work on this device is pretty straightforward, but you need quite a bit of files!

You need:
- the Android 10 ROM ZIP from this thread of course
- overclock kernel is the ElementalX 7.0.2 port for Android 10 by followmsi, available here (inside kernel subfolder) or here.
- root support comes with Magisk 21.0, available here
- MicroG is available through MinMicroG. This is available here. I recommend the MinimalIAP packages, it only contains the bare minimum for the PlayStore to work.
- You will also need Magisk Manager. You can either download that later or put it on the device to have it ready when you need it.

1. Boot into TWRP and do an advanced wipe to clear out all of your partitions
2. Then put all of the files (4 ZIP's) onto the root of your device with MTP / Windows File Explorer.
3. After that, install the programs in this order with TWRP:
- LineageOS ZIP
- ElementalX
- Magisk
- MinMicroG
4. After booting, install the Magisk Manager and open it up. It will install some more stuff and reboot the device.
5. Now open Magisk Manager again and install (and activate) the Riru - Core and Riru - EdXposed modules. Reboot.
6. You now have the EdXposed Manager in your app drawer. Open it up and install the FakeGapps module with it. This enables signature spoofing so you can use the original PlayStore.
7. Reboot. Go into the microG settings and enable everything .

That's it. You can now use the PlayStore without all of the other bloat that makes the system really slow and unresponsive.
The overclock options of the kernel can be set with Kernel Adiutor.

Questions for those that understand this better than I:

How do you copy the files once you have wiped the partitions? I don't see the nexus partitions in windows when in twrp (or do you need to use adb)?

Anyone know if Google voice, maps, etc are available with microG or do they require gApps?

How about play store backup/restore?

Thanks much!

 

[schmatzler]

How do you copy the files once you have wiped the partitions? I don't see the nexus partitions in windows when in twrp (or do you need to use adb)?

I can see them just fine in Windows when TWRP is loaded. It works over MTP.

 

[jhford]

Magisk never updates

I have 2 deb and I flash new updates on them simultaneously. But only one of them flashes Magisk. Have I done something wrong to cause this?

 

[pitrus-]

I have 2 deb and I flash new updates on them simultaneously. But only one of them flashes Magisk. Have I done something wrong to cause this?

What happens on the other one, does flashing off the Magisk 20.4 installer fail somehow or do you just mean that the Magisk selfheal after update is not doing it's job? Do you have the same TWRP version on both tablets?

 

[jhford]

What happens on the other one, does flashing off the Magisk 20.4 installer fail somehow or do you just mean that the Magisk selfheal after update is not doing it's job? Do you have the same TWRP version on both tablets?

Both tablets are running TWRP 3.4.0-0. I've been using this Rom for quite a while and Magisk is the last thing to flash when one flashes a "nightly," as they used to be called, but that only happens on one tablet.

Also, while I have your attention, my only other complaint is that both tablets randomly reboot intermittently for no obvious reason. Is that an idiosyncratic issue as to my tablets only, or is that SOP for all debs? It seems like a memory management issue to me.
Thanks

 

[pitrus-]

Both tablets are running TWRP 3.4.0-0. I've been using this Rom for quite a while and Magisk is the last thing to flash when one flashes a "nightly," as they used to be called, but that only happens on one tablet.



Also, while I have your attention, my only other complaint is that both tablets randomly reboot intermittently for no obvious reason. Is that an idiosyncratic issue as to my tablets only, or is that SOP for all debs? It seems like a memory management issue to me.

Thanks

No Magisk gets reflashed unless you have actually installed the Magisk zip manually before, it's not included in LineageOS as it's from a third-party.

There's some SoC issues on these tablets and it's pre-built blobs that just gets more apparent for each newer Android version being ported over, also development on this tablet isn't exactly active as it starts to show signs of wear in form of faulty battery cells and electrical issues as well as glitchy flex cables and such. My flo tablet hasn't spontanious rebooted itself, but it does get slow and needs a reboot now and then, so I suspect rebooting issues could be caused by either faulty battery cells, somebother electrical issue or maybe even other apps installed on the tablet.

 

[jhford]

No Magisk gets reflashed unless you have actually installed the Magisk zip manually before, it's not included in LineageOS as it's from a third-party.

There's some SoC issues on these tablets and it's pre-built blobs that just gets more apparent for each newer Android version being ported over, also development on this tablet isn't exactly active as it starts to show signs of wear in form of faulty battery cells and electrical issues as well as glitchy flex cables and such. My flo tablet hasn't spontanious rebooted itself, but it does get slow and needs a reboot now and then, so I suspect rebooting issues could be caused by either faulty battery cells, somebother electrical issue or maybe even other apps installed on the tablet.

Interesting. Maybe I should take the one with the Magisk issue back to stock and and clean reflash it and let LOS flash Magisk. Also, I've never changed their batteries and I have a couple of newish batteries I could install. And newish batteries are cheap and plentiful.

 

[_ck_]

look like pages are broken on the new forum software

trying to find if there is a new build host/location or if that's the end for this rom (which would suck)

 

[ipdev]

look like pages are broken on the new forum software

trying to find if there is a new build host/location or if that's the end for this rom (which would suck)

The current builds are by @pitrus-
Are you having problems accessing the website or downloading?

| Main - Link | Flo - Link | Deb - Link |

Cheers.

 

[_ck_]

thanks for the links, apparently my bookmarked links have a trailing slash which oddly breaks their server, removing it solves all

they must have changed their software just like the forum here and broke things

 

[tomasjobbar]

hey i try to get the new update , but it says check internet connection all the tim

https://mva1.androidfilehost.com/dl/b26_mU7t7_HSjk8cOgwPRw/17.1-20200823-pme.zip

can i get this somewhere and manual install it ? i have htc 10 with lineagos 17.1 best os i ever had in a phone

 

[jaucar]

The page for download, not work.
Many thanks for tour time and tour work

 

[Dodgy_Bob]

@jaucar

I don't know why, but doing this, things will work once again!

The front page has these links:

https://lineageos.wickenberg.nu/deb/

and

https://lineageos.wickenberg.nu/flo/

All you need do is remove that very last character, the backslash, so in the end you have this:

LineageOS Downloads

lineageos.wickenberg.nu

and

LineageOS Downloads

lineageos.wickenberg.nu

Try those links without the trailing backslash and you should find that the links work again for you

 

[tomasjobbar]

@jaucar

I don't know why, but doing this, things will work once again!

The front page has these links:

https://lineageos.wickenberg.nu/deb/

and

https://lineageos.wickenberg.nu/flo/

All you need do is remove that very last character, the backslash, so in the end you have this:

LineageOS Downloads

lineageos.wickenberg.nu

and

LineageOS Downloads

lineageos.wickenberg.nu

Try those links without the trailing backslash and you should find that the links work again for you

is that the updates files ? because i have an update in the system that the phone wants me to do ?

 

[Dodgy_Bob]

@everyone

This may not need to be stated, however, I just want to help out in any little way I can

My N7-flo's were on the last Google Official build with an older version of TWRP installed. Even though I updated TWRP to the latest (3.4.0), I still kept on running into the dreaded Error.7 issue - from what I first read, I was understanding things to mean that if I was on the latest TWRP, I should not get this issue. But after going back and re-reading the posts in this thread, it would appear you will get this issue regardless, as it also occurs if you are coming from an older version of Android, in my case 6 (Marshmallow).

So I realised I needed to do the repartition step, however the link for this file is dead at the moment; it gives a 502 'Bad Gateway' error. So that started me off google'ing for how to rectify this issue.

Long story short - too late, I know! - I came across this thread here in XDA:

[IIIII] CROSS - Custom ROM Scripted Setup

Nexus 7'13 CROSS - Custom ROM Scripted Setup (c)2020 k23m CROSS works on PC with Windows, or WinPE if you do not have Windows installed. Currently supported ROMs: - Android 7 LineageOS 14.1 - Android 10 LineageOS 17.1 FEATURES -...

forum.xda-developers.com

CROSS is a script that you can run which will take care of flashing / re-flashing your flo (or deb) device. It has the repartition step "built-in" so you don't need to download anything extra.

Thus, if you are having troubles with flashing your flo (or deb) device, try CROSS and see how that works for you. It worked for me and got me out of a pickle!

Just my 5cents

 

[Dodgy_Bob]

is that the updates files ? because i have an update in the system that the phone wants me to do ?

Ahhh, no actually, those links are to the full ROMs
I'm not sure where the updates are kept...

 

[tomasjobbar]

Ahhh, no actually, those links are to the full ROMs
I'm not sure where the updates are kept...

okey thx for the answer i think i got the rom installed correctly it works anyhow . actually i think i missed a couple of steps but the phone works , so im happy anyway just wanted to see what the update could do more for the phone

 

[iforget]

@everyone ... Long story short - too late, I know! - I came across this thread here in XDA ... CROSS is a script that you can run which will take care of flashing / re-flashing your flo (or deb) device. It has the repartition step "built-in" so you don't need to download anything extra. ...

This is fantastic.

If you're a total noob like me, you can run RESTOCK2:

[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix

RESTOCK ANNIVERSARY - VERSION 2 RELEASE! RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most...

forum.xda-developers.com

and then run CROSS. You don't need to know pretty much anything besides whether your Nexus 7 has cellular capability or not. Huge shoutout to @k23m for his ostensibly underappreciated apps! I don't know why I'd use anything else

 

[Eguy]

I'm having an issue getting my N7 booting right now. I was on a build from last month and I have tried the last several days and I get stuck on the boot animation until the battery drains. Does anyone know how to fix that? I've had problems in months past and clearing the cache in TWRP has fixed it but it's not fixing it this time.