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

[me98278]

Hi,

I'm trying to build the PixelExperience ROM for nexus 7 2013 and was able to do that thanks to @followmsi ( for flo device, vendor and kernel sources) , @k23m (for the unbricking guide) and @Clamor ( for the re partitioning guide) ..

I used the following sources :

https://github.com/PixelExperience/manifest/tree/ten-plus
Device Tree: https://github.com/followmsi/android_device_asus_flo/tree/aex-10
Vendor Tree: https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-17.1
Kernel Tree: https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-10

I had to increase the system partition to 1.6 GB to accommodate the ROM and I have re partitioned the nexus 7 storage to create a bigger system partition .

I keep getting the following error while trying to flash the ROM :
-------------------------------------------------------------------------------------------------------
creating stash /cache/recovery/5a79362318d00cf4c316e86435b3ed38dd35082d
71118848 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 7086 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 2,402533,409619]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/PixelExperience_Plus_flo-10.0-20201101-0407-UNOFFICIAL.zip'
-------------------------------------------------------------------------------------------------------------------

I have tried to flash the ROM via sideloading but that did not help.

Can you help me figure out this error ??

 

[kozmo2k4]

No "love" for the deb since 10/26? I only see 16 o the website...

Sent from my Nexus 7 using Tapatalk

 

[pitrus-]

No "love" for the deb since 10/26? I only see 16 o the website...

Sent from my Nexus 7 using Tapatalk

Seems like the defined system partition size in the board settings of the device definition is not big enoug anymore. Probably LineageOS features taking up more space or something. Strange that the flo doesn't get affected though, maybe the 4G modem firmwares and other deb specific stuff takes up more space than the flo which only has wifi.

 

[ipdev]

@pitrus- @followmsi

I ran into it last Friday (30.Oct).
Flo built fine, deb failed.

Had to bump system image up to 1 Gig to get deb to build.
GitHub - Line_86

Not sure if it should be set higher (1.2G) or just see what happens and adjust it again later.
Would it be better to split flo and deb then use a deb BoardConfigCommon instead?

Cheers.

---------- Post added at 01:46 AM ---------- Previous post was at 12:59 AM ----------

@schnoeselmeier
Not sure if you have tried it or not.
On older devices, reducing the animation can help speed up a little.

Enable Developer options.
Under Developer options, find the animation scale and change from 1x to .5x
Normally you will not notice a visible change at half. If you turn it off, it will look flat.
--
@me98278
failed to execute command [erase 2,402533,409619]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7

Generally E1001 is the system image (rom) is too big to fit in the system partition on the device.
If you are sure your partition is big enough, then take a look at what size is shows.
You may have to format and/or wipe the device to get then new partitions sizes to show correctly in TWRP.
You could try resize/repair option under Advanced wipe in TWRP to try and extend it to the full (new size).

Or something could have gotten borked in the process and you need to rebuilt the rom, wipe/format the device and/or check and correct partitions.

Cheers all.

 

[followmsi]

@pitrus- @followmsi

I ran into it last Friday (30.Oct).
Flo built fine, deb failed.

Had to bump system image up to 1 Gig to get deb to build.
GitHub - Line_86

Not sure if it should be set higher (1.2G) or just see what happens and adjust it again later.
Would it be better to split flo and deb then use a deb BoardConfigCommon instead?

Cheers.

---------- Post added at 01:46 AM ---------- Previous post was at 12:59 AM ----------

@schnoeselmeier
Not sure if you have tried it or not.
On older devices, reducing the animation can help speed up a little.

Enable Developer options.
Under Developer options, find the animation scale and change from 1x to .5x
Normally you will not notice a visible change at half. If you turn it off, it will look flat.
--
@me98278
failed to execute command [erase 2,402533,409619]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7

Generally E1001 is the system image (rom) is too big to fit in the system partition on the device.
If you are sure your partition is big enough, then take a look at what size is shows.
You may have to format and/or wipe the device to get then new partitions sizes to show correctly in TWRP.
You could try resize/repair option under Advanced wipe in TWRP to try and extend it to the full (new size).

Or something could have gotten borked in the process and you need to rebuilt the rom, wipe/format the device and/or check and correct partitions.

Cheers all.

Increased to 1.1 GB in BoardConfigCommon.mk .. same size for both devices.

https://github.com/followmsi/android_device_asus_flo/commit/f75bebf741a81ea32d3d7c571959fa7b1c2997b0

As Android requires more space we have less free space in system partition left .. gapps installation may have problems too.
If we need more as 1280 MB we need to change repartition scripts too.

 

[me98278]

@ipdev .. thanks for your response .. that was indeed the problem.. i bumped up my partition size to 2 GB to be on the safe side.. I was able to flash the rom after that. Noticed a few issues..
1. not able to install new apps \ update existing apps from play store.. the apps get stuck in downloading status ..
2. only the back button works.. the home or running apps buttons . able to swipe up and see the running apps.
3. clicking on the settings icon from the pull down menu does not work.

I switched to pixel experience ten branch and that version also has the same issues. Any ideas?

 

[dansblackcat]

Any idea how to improve performance? My tablet lags to the point where I would call it useless as a daily driver.

Don't do updates after a clean install I found is the trick.
I find if I manually update or use the built in updater my tablet will become so slow it's virtually unusable.

5 days ago I flashed the latest version, wiping cache, data, system and dalvik. It's still running great.

 

[pitrus-]

Don't do updates after a clean install I found is the trick.

I find if I manually update or use the built in updater my tablet will become so slow it's virtually unusable.



5 days ago I flashed the latest version, wiping cache, data, system and dalvik. It's still running great.

As always with updates, it can take some time before all update scripts, system checks and stuff complete after doing an upgrade. Thats also why battery usage is unstable a while after update. I only do upgrades on my flo:s but I leave it alone for half a day after updating before using it. However sometimes changes in LineageOS source code can introduce incompatibility or slowness due to software bugs which can either be avoided by doing clean flash or just returning to previous version before the source code change.

 

[schmatzler]

I would like to use microG with this ROM. Any chance to include signature spoofing into the ROM? Or do you know of any other method to use microG with this ROM?

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.

 

[2kpilgrim]

Applied the installation description from schmatzler (Thanks!) to my DEB. Partition size changed to 1.2 GB.
Installation went through without errors.
Problem1: SafetyNet Check in Magisk reports errors. : MagiskHide off and on don`t help
Problem2: Play Store: " Error getting information from the server ......." - app don`t start up.

Magisk changed 21.0 ->20.04 (from beta to stable)

Can you help me?

 

[me98278]

@ipdev .. thanks for your response .. that was indeed the problem.. i bumped up my partition size to 2 GB to be on the safe side.. I was able to flash the rom after that. Noticed a few issues..
1. not able to install new apps \ update existing apps from play store.. the apps get stuck in downloading status ..
2. only the back button works.. the home or running apps buttons . able to swipe up and see the running apps.
3. clicking on the settings icon from the pull down menu does not work.

I switched to pixel experience ten branch and that version also has the same issues. Any ideas?

@ipdev @followmsi
Any tips about how to fix the above issues ??

 

[schmatzler]

Applied the installation description from schmatzler (Thanks!) to my DEB. Partition size changed to 1.2 GB.
Installation went through without errors.
Problem1: SafetyNet Check in Magisk reports errors. : MagiskHide off and on don`t help
Problem2: Play Store: " Error getting information from the server ......." - app don`t start up.

Magisk changed 21.0 ->20.04 (from beta to stable)

Can you help me?

Make sure PlayStore has all permissions, specially storage. Then it should start just fine.

 

[2kpilgrim]

@schmatzler
Thanks. Don`t found any problems with PlayStore permissions on my DEB.
Solved my problem with a clean install + Magisk 20.3 and OpenGapps pico. Then toggled MagiskHide switch OFF and ON starts SafetyNet Check without failure.
As a permanent fix for toggling MagiskHide after reboot, i installed and activated the MultiFunktionsPlus Module of Dreamer. After reboot and waiting cca 30 mins SafetyNet Check pass. No more manualy toggling necessary. Then for PlayStore certifiing - due to Custom Rom - registration of Device ID on Google web site was necessary. Now in PlayStore Setting - device not certified, but dont have any problems on app installation for google and other apps.

 

[Spanking Time]

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.

And are you able to download and use Netflix with this setup?

 

[bobby8921]

And are you able to download and use Netflix with this setup?

I followed his instructions.
I am able to install Netflix from the playstore but as there is no Widevine DRM, this is only low quality content.

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.

On my side, I had an issue with the playstore and I had to register the tablet to goog!e in microG settings. (Not sure it's what you meant by check everythlng in miroG)

Also, I'm not able to pass SafetyNet. I have a SafetyNet error API un Magisk.

 

[xxxmadraxxx]

Is anyone else having these odd symptoms:

After I install LineageOS 17,1, my Nexus works fine for a random length of time. Then, at some point the tablet will spontaneously shutdown and reboot into TWRP Recovery. From then on, it will only boot into TWRP. The only way I can get it to boot into LineageOS again is to do a factory reset. Then all will be fine... til it happens again.

It seems to always happen when the tablet's asleep and on charge. I'll be using it as normal, to read intarwebs in bed. And then I'll plug it in to charge while I sleep. In the morning when I pick it up again, I'll find that, at some time during the night, it's shutdown and booted into TWRP and will no longer boot into the OS. The timescale seems completely random too. Sometimes this will happen the very first night I use it. On other occasions, it's been fine for several days, before suddenly doing this again.

Anyone else seen anything like this?

 

[_ck_]

Is anyone else having these odd symptoms:

After I install LineageOS 17,1, my Nexus works fine for a random length of time. Then, at some point the tablet will spontaneously shutdown and reboot into TWRP Recovery. From then on, it will only boot into TWRP. The only way I can get it to boot into LineageOS again is to do a factory reset. Then all will be fine... til it happens again.

It seems to always happen when the tablet's asleep and on charge.

Yes I too get random reboots overnight in the middle of the night like every other day or two. But I am stuck on a build from end of July, anything newer installed over won't completely boot. It settles down for another day or two after the reboot.

Tried both the old ElementalX kernel and MSI's TEN, both have reboot so it must be something else.

 

[Mr.Conkel]

Anybody know of good custom kernels compatible with this rom? I wanted to do some digging myself but figured I should ask here as to take pre-caution so I don't end up in any bootloops. Please give some advice and kernels to try! Any replies are appreciated.

Thanks! Cheers

 

[xxxmadraxxx]

Yes I too get random reboots overnight in the middle of the night like every other day or two....

Wow! --glad it's not just me. I was beginning to think there was an actual hardware problem with my Nexus. I had this keep happening with LineageOS 17. Then I tried LineageOS 14. With that, I didn't get any random shutdowns, but my tablet ran like an absolute dog; literally taking 5 or 10 seconds to popup the keyboard, or redraw the window when I changed screen orientation.

I'm currently trying LineageOS 16 and.... so far, so good. About 4 days in and no random reboots into recovery. And it seems to be running snappily enough. Fingers crossed!

 

[GeekyTanuj]

Suggestion

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.

Can you make a separate post for this, it's getting hidden like a rare gem in the discussion feed.