[ROM][flo|deb][UNOFFICIAL][LineageOS 18.1] -> 2020-12-11

[RazGame]

flo-kernel-aosp-20170810.zip
flo-kernel-aosp-20170810.zip.sha1

Can I flash it on my deb ?

 

[followmsi]

Can I flash it on my deb ?

Yes ..

2.*Install*the Kernel Update.Zip*file*(the kernel works for flo and deb*devices)

Sent from my AOSP on Manta using Tapatalk

 

[followmsi]

Any way to enable double tap to wake on stock Google kernel?

No .. not as I know.

Sent from my AOSP on Manta using Tapatalk

 

[RazGame]

@ followmsi, So... Android O AOSP available now ?

 

[followmsi]

@ followmsi, So... Android O AOSP available now ?

Yes the Oreo sources are available now.
Started with AOSP Oreo ROM for Pixel C .. to get some first impressions.
As it's a supported device the migration goes more or less quickly.
Still a few issues left.

The flo/deb versions will take longer .. too many changes under the hood.

- Starting with missing sdcardfs support inside flo kernels - except for glitch kernel.
- On first boot of Android Oreo your internal storage will be converted to sdcardfs format.
- Quota needs to be enabled too.

- Android binder seems to have changed as well.
- Causing boot-loops while booting into Android system.

- The "old" flo/deb sources need to be merged with 8.0 sources, if possible and applicable.
- Tons of build errors are expected

- And the 50 other problems I am not aware of - yet

etc. ..

Takes plenty of time .. hope you have a better understanding now ..

 

[GuestK0063]

Takes plenty of time .. hope you have a better understanding now ..

No need to rush, we are grateful for you even trying to bring 8.0 to flo

 

[whaevr]

Yes the Oreo sources are available now.
- On first boot of Android Oreo your internal storage will be converted to sdcardfs format.

Despite the name sdcardfs isn't a filesystem format, there will be no need to convert anything. You just need to mount them with the sdcardfs option instead of fuse.

Read more about it here and see examples on the differences between Oreo and Nougat

 

[followmsi]

Despite the name sdcardfs isn't a filesystem format, there will be no need to convert anything. You just need to mount them with the sdcardfs option instead of fuse.

Read more about it here and see examples on the differences between Oreo and Nougat

Thanks for the update .. the internal storage will be mounted and not converted.
It's not a real file system like F2FS ..etc.

Nevertheless SDcardFS needs to be integrated into kernel .. and the work has to be done

flo-kernel-aosp-20170825.zip
flo-kernel-aosp-20170825.zip.sha1

The kernel is working on flo and deb devices !

Changes:
- Ported "SDcardFS" from Glitch kernel into "stock" google msm kernel. ( Thx to @Tk-Glitch )
- Enabled Quota
- Change Android Binder configuration - to hopefully work with Android Oreo.

Installation:
1. Boot into TWRP
2. Install the Kernel Update.Zip file
3. Reboot into system .. no need for SuperSU / Magisk !

Tested on latest Android Nougat ROM.

Sources:
https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2017-08-25

Enjoy

 

[RazGame]

to hopefully work with Android Oreo.

Maybe you can ask dev's of Oreo for Mi3/4 somethings

 

[followmsi]

Made the OpenGapps package for Android Oreo .. until the official version is ready.

Initially done for "arm64" version (Pixel C) .. but as you have to download all the sources for "arm" architecture as well.
Here is the arm verison for flo/deb devices ..

open_gapps-arm-8.0-stock-20170823-UNOFFICIAL.zip

Pls use the following config file as example ..
.gapps-config

Just the Oreo ROM itself is missing now

 

[followmsi]

Maybe you can ask dev's of Oreo for Mi3/4 somethings

Thanks for the info ..
Would like to see the device tree sources .. and their other customizations on GitHub .. or somewhere else - online.

The first BETA Oreo version is ready .. for flo device only.
I did not install/test this ROM until now .. maybe it's not booting at all.

Here you are ..
AOSP_8.0.0_r1_OPR6.170623.010_flo-ota-eng.followmsi_BETA-1.zip

The next time slot for "playing" with Android Oreo will be hopefully soon .. to get a BETA-2 version.

Again I did not test this ROM myself - not yet.

EDIT:
Quick technical update too ..
- F2FS support inside fstab.flo for /data partition has been removed.
- Used kernel from today - SDcardFS support .. etc.
- Selinux problems to be expected - as kernel is still "enforcing". (change manually to "permissive" for better testing -> setenforce 0)

 

[wavedashdoc]

Thanks for the info ..
Would like to see the device tree sources .. and their other customizations on GitHub .. or somewhere else - online.

The first BETA Oreo version is ready .. for flo device only.
I did not install/test this ROM until now .. maybe it's not booting at all.

Here you are ..
AOSP_8.0.0_r1_OPR6.170623.010_flo-ota-eng.followmsi_BETA-1.zip

The next time slot for "playing" with Android Oreo will be hopefully soon .. to get a BETA-2 version.

Again I did not test this ROM myself - not yet.

EDIT:
Quick technical update too ..
- F2FS support inside fstab.flo for /data partition has been removed.
- Used kernel from today - SDcardFS support .. etc.
- Selinux problems to be expected - as kernel is still "enforcing". (change manually to "permissive" for better testing -> setenforce 0)

@followmsi the Unofficial 8.0 GAPPS were too large for the system partition (error 70) fixed this by adding "gapps-config.txt" with NanoGApps inside the file to force it to shrink the install. Successfully flashed.

But... the beta Oreo build doesn't boot. Goes to google logo, then black for about 1 minute then to the bootloader. Tried again in TWRP and it failed to show the data partition as mounted. So unable to flash anything.

Used the old nexus root toolkit and restored factory 6.0. Will try again once I'm back up and running, with pico setting. Thanks for your hard work! Crazy to think that this device might see 8.0 before my nexus 6 lol.

EDIT: Wiped my storage partition. Make sure you save all your files before attempting this!
EDIT2: Second attempt failed as well. Won't get to the boot animation, and returns to bootloader. All storage is wiped.

 

[seansheng0412]

Can This version select language as "Chinese" ?

Can This version select language as "Chinese" ?

It's difficult to type on the phone.

Thanks a lot to @nbehary for his work .. and to @DevSwift1 for the pre-work !

It's better to start a new thread for my monthly AOSP builds

The plan is to make monthly releases - to include new google security changes.
Nothing more !
I have used lineageos/elementalx kernel and activated F2FS file-system.
But there are no plans to do more changes ... it's working perfectly already !

Here we go ..

AOSP_7.1.2_r28_N2G48C_flo-ota-eng.followmsi-v2.zip

AOSP_7.1.2_r28_N2G48C_deb-ota-eng.followmsi-v2.zip


Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (Not required if you upgrade from previous build)
3. Install AOSP_7.1.2_r28_N2G48C_flo-ota-eng.followmsi-v2.zip
4. install opengapps or beansgapps (optional)
5. install SuperSU.zip and/or Magisk.zip
6. Reboot into system

- Please install Magisk.zip and/or SuperSu.zip yourself.
- Due to systemless rooting - if you have installed magisk and/or supersu before you need to install it again !
- If you install SuperSu.zip it will boot twice - no panic, it's normal !
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- If you face any strange issues, pls do a factory reset via TWRP first.


Gapps:
The AOSP installer does not support "/system/addon.d/" scripts !
For this reason Gapps are not persistent like in LineageOS or in other custom ROMs.
I have modified the installer script to add this functionality.
You should be able to keep your gapps installation when you upgrade the ROM.
Pls have a look here: https://forum.xda-developers.com/showpost.php?p=71625784&postcount=170


SuperSU and/or Magisk:
SuperSU.zip and/or Magisk.zip has always to be installed after ROM installation/upgrade - because of systemless rooting.
If you install SuperSu.zip it will boot twice - no panic, it's normal !


TWRP:
Have made a new TWRP version, based on latest nougat sources .. pls have a look here:
https://forum.xda-developers.com/nexus-7-2013/orig-development/recovery-twrpflo3-0-3-0-t3564280


SOURCES:
If you want to build your own ROM .. just use my slightly modified manifest.
https://github.com/followmsi/manifests/tree/flo-deb-aosp-nougat


DOWNLOAD:
https://drive.google.com/open?id=0By6p5AdQfavBUlhsLWFHZThGTnM


Thanks again to @nbehary and @DevSwift1 !


Enjoy ..

 

[followmsi]

@followmsi the Unofficial 8.0 GAPPS were too large for the system partition (error 70) fixed this by adding "gapps-config.txt" with NanoGApps inside the file to force it to shrink the install. Successfully flashed.

But... the beta Oreo build doesn't boot. Goes to google logo, then black for about 1 minute then to the bootloader. Tried again in TWRP and it failed to show the data partition as mounted. So unable to flash anything.

Used the old nexus root toolkit and restored factory 6.0. Will try again once I'm back up and running, with pico setting. Thanks for your hard work! Crazy to think that this device might see 8.0 before my nexus 6 lol.

EDIT: Wiped my storage partition. Make sure you save all your files before attempting this!
EDIT2: Second attempt failed as well. Won't get to the boot animation, and returns to bootloader. All storage is wiped.

Thanks for your testing and report.

When you have flashed stock in between you use ext4 for /data partition.
If you still use F2FS you would get problems too.
/data should be formated to ext4 for testing the BETA.

If TWRP is not able to mount /data - SDcardFS is missing in TWRP kernel too ..same problem on Pixel C.
Had to use a new kernel for TWRP on Pixel C.
But you can still do installations via usb-otg at this point.
Will make a new TWRP version including the new kernel to support sdcardfs.

Made a kernel with disabled selinux for flo/deb .. in the same download folder - the permissive version.
Not sure if disabled selinux will fix booting .. I doubt.

Now we need to know what is blocking the boot process ..?
Most probably the kernel.

You see .. because of all this issues you may get Oreo first on Nexus 6

 

[wavedashdoc]

Thanks for your testing and report.

When you have flashed stock in between you use ext4 for /data partition.
If you still use F2FS you would get problems too.
/data should be formated to ext4 for testing the BETA.

If TWRP is not able to mount /data - SDcardFS is missing in TWRP kernel too ..same problem on Pixel C.
Had to use a new kernel for TWRP on Pixel C.
But you can still do installations via usb-otg at this point.
Will make a new TWRP version including the new kernel to support sdcardfs.

Made a kernel with disabled selinux for flo/deb .. in the same download folder - the permissive version.
Not sure if disabled selinux will fix booting .. I doubt.

Now we need to know what is blocking the boot process ..?
Most probably the kernel.

You see .. because of all this issues you may get Oreo first on Nexus 6

You're welcome. Glad to assist!

I was using normal ext4, never bothered to go to F2FS.

Yeah I was thinking it was along the lines of an incompatibility, since each try resulted in the same case of losing the ability to see the data partition. I'm back up and running on your latest 7.1.2 with no issues.

Haha, it's always the same cycle when a new version of Android comes around. ??

 

[followmsi]

You're welcome. Glad to assist!

I was using normal ext4, never bothered to go to F2FS.

Yeah I was thinking it was along the lines of an incompatibility, since each try resulted in the same case of losing the ability to see the data partition. I'm back up and running on your latest 7.1.2 with no issues.

Haha, it's always the same cycle when a new version of Android comes around.

Thanks for the update .. strange issue indeed.

Made some more tests .. running Android 8.0 on Pixel C.
Tested TWRP using a Nougat kernel with SDcardFS support on Pixel C ... can't read my data partition anymore -> similar problem like on flo device.
If I just replace the kernel inside the recovery.img with Oreo kernel it works again - you can mount data without issues.

Compared Oreo and Nougat SDcardFS sources .. not much changes here - seems not to be the root cause of the problem.
It seems there are "more" kernel changes required to make Oreo working, more as just activating SDcardFS.

What is also very strange .. inside TWRP the sideload function does not work using the Oreo kernel.
The recovery.log is compaining about missing "libhwbinder.so" - never been part of the TWRP ramdisk.
They did kernel changes for the android binder .. maybe related.

Pixel C is using 3.18 kernel version and is still an official supported device .. You can easy build Oreo or Nougat kernels - as you have the sources available.
All Oreo supported devices are using verion 3.10 or above - but for sure no 3.4 kernel version like used for flo/deb. devices.

Maybe I will ask Glitch and other kernel guys for some help .. to make 3.4 kernel version ready for Oreo

 

[followmsi]

Can This version select language as "Chinese" ?

It's difficult to type on the phone.

Default AOSP settings .. no changes are done.

But first we need to get it running at all

 

[poondog]

Thanks for the update .. strange issue indeed.

Made some more tests .. running Android 8.0 on Pixel C.
Tested TWRP using a Nougat kernel with SDcardFS support on Pixel C ... can't read my data partition anymore -> similar problem like on flo device.
If I just replace the kernel inside the recovery.img with Oreo kernel it works again - you can mount data without issues.

Compared Oreo and Nougat SDcardFS sources .. not much changes here - seems not to be the root cause of the problem.
It seems there are "more" kernel changes required to make Oreo working, more as just activating SDcardFS.

What is also very strange .. inside TWRP the sideload function does not work using the Oreo kernel.
The recovery.log is compaining about missing "libhwbinder.so" - never been part of the TWRP ramdisk.
They did kernel changes for the android binder .. maybe related.

Pixel C is using 3.18 kernel version and is still an official supported device .. You can easy build Oreo or Nougat kernels - as you have the sources available.
All Oreo supported devices are using verion 3.10 or above - but for sure no 3.4 kernel version like used for flo/deb. devices.

Maybe I will ask Glitch and other kernel guys for some help .. to make 3.4 kernel version ready for Oreo

On bullhead there were some big changes to binder for oreo,
Including some defconfig changes.

Also the binder binaries might not be suited to our architecture

Just some things I've noticed diffing sources

Thanks for your work on this device

 

[followmsi]

On bullhead there were some big changes to binder for oreo,
Including some defconfig changes.

Also the binder binaries might not be suited to our architecture

Just some things I've noticed diffing sources

Thanks for your work on this device

Yes, quite some changes ..

Would love to checkout android-8.0.0_r0.2 and start compiling.
https://android.googlesource.com/kernel/msm/+/android-8.0.0_r0.2

And if you compare all the changes to "old" 3.4 flo binder implementation you will see even more differences.

Is it possible to port relevant 3.10 changes into flo/deb 3.4 kernel at all ?
If yes, who is able to port it ? .. not me - that's beyond my skills.

We need the kernel specialists here

Sent from my AOSP on dragon using Tapatalk

 

[mick3lson]

I've nexus 7 2013 with factory firmware image-razor-mob30 and TWRP_flo_3.1.1-0, is possible to install multirom to test your release AOSP_7.1.2_r28_N2G48C in other partition.