Develop Bugs

Unlocking the 32GB Mi5 frequency

Hi guys, I have been looking at / working on allowing the 32GB variant Mi5 to run at the full speeds (2.15/1.6/624) on the msm8996 SOC as its 64/128GB brothers.
I was able to patch the kernel frequency table to run my 64GB at the reduced frequency of the 32GB but cannot test this in reverse as I don't have a 32GB device
I am hoping a 32GB user can test a boot.img for me. Can fastboot boot/flash it, or flash via TWRP (install -> install image -> select img) and just backup your existing img.
I do suspect it will not boot or work (it does boot/otherwise work on my 64GB though, but there's a few more code differences I haven't changed), but it'd be nice to know
boot_rev1.img this revision does not work, yet
boot_rev2.img a few users report that this one works.
What I would like to know is overall stability for 32GB users, if they could test their phone in games etc as voltage tables may need more adjustment
Edit: please note this kernel is for CM13/AOSP based ROM. please don't flash it over MIUI8
Project moved to http://forum.xda-developers.com/mi-...d-32gb-mi5-t3482455/post69177557#post69177557
Source here: https://github.com/harrynowl/falconkernel-gemini

awesome. did you post in the miui forum?

rochee94 said:
awesome. did you post in the miui forum?
Click to expand...
Click to collapse
Not yet, hoping to find feedback here first

As you are using CM kernel as base, you must inform that this will only work on devices running MIUI 7.x firmware and a CM based ROM.
On top of that, don't forget to publish the link to the kernel source in order to follow XDA's GPL regulations. I know you have the source in Github.

Could you build a kernel to overclock the 64 &128GB versions too? That would be great.

Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)

razibrizal said:
Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)
Click to expand...
Click to collapse
No: https://source.codeaurora.org/quic/...init.qcom.post_boot.sh?h=LA.HB.1.3.1.c1#n1729.

GalaxyS4_Lollipop said:
Could you build a kernel to overclock the 64 &128GB versions too? That would be great.
Click to expand...
Click to collapse
First focus is on giving 32GB users the full power of the hardware they paid for

I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Edit
Using AOKP and Cm13 same result

sys01 said:
I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Click to expand...
Click to collapse
Thanks for info, I think I know why this is..

Harrynowl said:
First focus is on giving 32GB users the full power of the hardware they paid for
Click to expand...
Click to collapse
That's cool.
Anyway, if it is any method to power up the beast to the SnapDragon821 power, I wait for it. (on 64gb)
Good luck and thanks for your support.

4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !

Alex4455 said:
4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !
Click to expand...
Click to collapse
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:

Looking forward towards the fix.
Many people will be happy if this comes out with no issues !

Harrynowl said:
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:
Click to expand...
Click to collapse
thank u for the initiative will wait for the next build :good:

pls after making it work, build one for MIUI 8 if it's possible.

catalizgar said:
pls after making it work, build one for MIUI 8 if it's possible.
Click to expand...
Click to collapse
Miui8 firmware blobs are not currently compatible with the kernel sources we have.
A member got a kernel booting on miui8 but stability was a big problem.

First of all, thank you. I think all 32GB users will thank you for that.
Obviously when it's done, it will consume more power, and would have less SoT.
Can you make predictions of what it will take when optimized and fully working?

After changing my ROM to AOSP based I will use this. thanks for your hard working. really appreciated

I added a new boot.img to the OP with some updates to the source. Hopefully this one has more luck. Specifically changes to the voltage table(s).
Please test 32GB users

Any AOSP / LineageOS based ROMs in development?

Not asking for an ETA, but just wondering what we can expect in the future.
As of now, the only custom ROM in the Development section is the OOS-based FreedonOS.
A lack of AOSP-based ROMs is the only thing holding me back from using this as my daily phone.

I believe several groups are working on their AOSP firmwares for this phone. It's still pretty new and nobody wants to release a crap product out of the gate.
I know one very popular group for sure is (they're dirty ?).

I'm hoping for lineage and aospa support. Pretty sure lineage will reuse their oneplus5 rom. It's basically the same phone just with another display. With aospa we'll have to wait until the Oreo update is out. I don't expect anything new from them before that.

I am especcially waiting for Ressurection Remix

Slimroms is one of best aosp.
I'm definitely going to wait their release before op5t will become my daily phone.
As is for now 2017 op5t has less functionality than my nexus6.

GZOSP just added a dumpling section for devices so there's some hope for Validus. We'll have to wait for full development though since I don't think we'll have unified builds.

x111 said:
Slimroms is one of best aosp.
I'm definitely going to wait their release before op5t will become my daily phone.
As is for now 2017 op5t has less functionality than my nexus6.
Click to expand...
Click to collapse
The device is what, 2 weeks old? You expect development to be at the level of a 3 year old device? You may need to lower your expectations a bit.
Sent from my Pixel XL using Tapatalk

I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks

varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
Check with @darkobas, he got his kernel to boot.

varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
Oh Varund great to see you. I remember your builds for the Oneplus One and Galaxy S3 have you buyed the op5t?
Great to have you here. :good:

DocRambone said:
Check with @darkobas, he got his kernel to boot.
Click to expand...
Click to collapse
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Tiz92 said:
Oh Varund great to see you. I remember your builds for the Oneplus One and Galaxy S3 have you buyed the op5t?
Great to have you here. :good:
Click to expand...
Click to collapse
Yes I got my device 2 days back

varund7726 said:
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Yes I got my device 2 days back
Click to expand...
Click to collapse
He had the same problem with reboot to fastboot, he solved it somehow tho.
Darkobas fix: https://gerrit.omnirom.org/#/c/27256/

DocRambone said:
He had the same problem with reboot to fastboot, he solved it somehow tho.
Darkobas fix: https://gerrit.omnirom.org/#/c/27256/
Click to expand...
Click to collapse
Thank you buddy .will give this a try
EDIT: got stuck with this annoying error
Code:
INSTALL usr/include/asm-generic/ (35 files)
/home/varun/RR/kernel/oneplus/msm8998/scripts/Makefile.headersinst:55: *** Missing UAPI file /home/varun/RR/kernel/oneplus/msm8998/include/uapi/linux/ashmem.h. Stop.
make[2]: *** [linux] Error 2
make[2]: *** Waiting for unfinished jobs....
INSTALL usr/include/drm/ (21 files)
INSTALL usr/include/misc/ (1 file)
INSTALL usr/include/media/ (21 files)
make[1]: *** [headers_install] Error 2
make[1]: Leaving directory `/home/varun/RR/out/target/product/dumpling/obj/KERNEL_OBJ'
make: *** [sub-make] Error 2
make: Leaving directory `/home/varun/RR/kernel/oneplus/msm8998'
[ 36% 930/2537] target C: libc_openbs...tream-openbsd/lib/libc/string/strspn.c
ninja: build stopped: subcommand failed.
make: *** [ninja_wrapper] Error 1

Maybe ask some of the big guys of LOS

varund7726 said:
Unfortunately hes got the Oreo version booting .
I tried his kernel , doesn't work on los (14.1) based ROMs
We'll probably have to wait till one of the core los devs gets this booting
Yes I got my device 2 days back
Click to expand...
Click to collapse
Nice to have you around... What device tree did you try use?

varund7726 said:
I personally tried make an RR build (Nougat)
Everything built fine except that the device doesn't boot (goes to fast boot)
Used the OOS Kernel source
I'm guessing the kernel needs boot image to be signed
If anybody is willing to help me out (devs only) please PM me
Thanks
Click to expand...
Click to collapse
i can tell you that the OnePlusOSS source / msmcortex_defconfig boots 14.1.
check your disk encryption config.
also use your own recovery and/or fastboot format userdata
some recoveries floating around don't have FBE right. don't trust recovery wipe

dcd1182 said:
i can tell you that the OnePlusOSS source / msmcortex_defconfig boots 14.1.
check your disk encryption config.
also use your own recovery and/or fastboot format userdata
some recoveries floating around don't have FBE right. don't trust recovery wipe
Click to expand...
Click to collapse
Hi do you have a working device tree ? Mines messed up

jgcaap said:
Nice to have you around... What device tree did you try use?
Click to expand...
Click to collapse
I tried the NastyAndroidDevs device tree from lineage 15.0 branch

[ROM] [LINK] Sailfish OS 2.1 JBBL ONLY

the original OP is VERY confusing. Take a look for credits sake though. I am putting a link to the download page below it.
I DIDN'T MAKE THIS ROM! All credit for the Droid Razr M build goes to elros34, also please thank vevgeniev for making the Photon Q port.
JBBL ONLY!!! -- I MIGHT be tempted to try and build a KKBL port if enough people are interested, but at the moment, JBBL works flawlessly, and a few KKBL users downgrading their Boot loaders is way easier than me building a whole new (most likely) barely functioning port just for KKBL, when we already have a great JBBL port
What works:
Camera
Wifi
GSM: Everything works, including calls, data, and text
CDMA: I don't use CDMA but as far as I know, only calls work.
Vibration
Audio and Video
>>*when using the YTPlayer app, turn off early video loading in Settings>Player>Early video loading = set it to "Never"*
USB MTP to both my PC and my Chromebook.
What doesn't work:
nothing, this is a ROCK SOLID PORT!
you have to first flash CM11, and then flash sailfish over it.
So I was browsing around the Photon Q xda page and saw this gem. I would have passed it over and just thought "neat" and moved on, but as I skimmed the page I saw that it is based on msm8960_jbbl sources, so it theoretically works on all unified msm8960 devices on jbbl. I actually read the OP and low and behold there is the RAZR M on the list of supported devices. I didn't make this (obviously) but definitely swing by the original thread and take a look.
NOTE: THE PHOTON Q PORT WON'T BOOT ON THE XT907 OR XT905 - Please use the elros34 build linked in the Direct Download links section.
https://forum.xda-developers.com/photon-q-4g-lte/general/sailfishos-2-0-motorola-photon-q-t3281262
http://www.vladislavonline.com/sailfishos-for-photon-q/
DIRECT DOWNLOAD LINKS
CM11 BASE [ https://archive.org/download/cmarch...626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip ]
Sailfish OS 2.1.3.7 alpha3 xt907 [ https://goo.gl/DJ8zre ] || Mirror [ https://onedrive.live.com/?cid=f188cb653189eae0&id=F188CB653189EAE0!403&authkey=!AGtl3flkGPJHaiE ]
rahimali AFH: [ https://androidfilehost.com/?w=files&flid=236124 ]
Headphone Jack fix for xt907 ---> HEADPHONE JACK FIXED IN ALPHA BUILD 3, THANKS elros34!!!
tested and working on the alpha 2 build, thank elros34 for this not me, he is the genius behind this one, think of me as a parrot.
You need to either use ssh on your computer, or the terminal app on your phone. You also need to set a root password in Settings -> Developer Options
devel-su
[input root password]
vim /etc/ohm/plugins.d/accessories.ini
*you'll see 4 lines, one of witch being Jack Match = /dev/input/event5 (or something similar, you'll see it, it should be the last line in the file)
*enter the letter "i" to edit
*replace "/dev/input/event5" with "/dev/input/event4"
*enter CTRL+C
*enter ":", and enter "write"
*now hit ":" again and enter "quit"
reboot your device and now headphone jack should work, hooray!
I DID NOT MAKE THIS!!! I AM SIMPLY LINKING IT FOR OTHER XT907 USERS TO ENJOY! CREDIT TO elros34 FOR THE PORT TO THE RAZR M, AND vevgeniev FOR MAKING THE PHOTON Q PORT!

The link doesn't seem to work. Says an error has occurred.

link is not working

faisala66 said:
link is not working
Click to expand...
Click to collapse
Ill update it :good:
The one drive links works fine on my chromebook, but Ill replace it with the direct one I find in the thread.

I've shared the files here

it is for kkbl?

faisala66 said:
it is for kkbl?
Click to expand...
Click to collapse
Nope. JBBL only.

rahimali said:
Nope. JBBL only.
Click to expand...
Click to collapse
but it says it is for kkbl and I have also installed in my phone in KKBL

faisala66 said:
but it says it is for kkbl and I have also installed in my phone in KKBL
Click to expand...
Click to collapse
Good for you! :good:

rahimali said:
Good for you! :good:
Click to expand...
Click to collapse
thanks but its not booting

faisala66 said:
thanks but its not booting
Click to expand...
Click to collapse
So what do you expect if you don't follow instructions?

rahimali said:
So what do you expect if you don't follow instructions?
Click to expand...
Click to collapse
sorry sorry i wlashed wrong CM11 snapshot (msm8960) it is for (msm8960jbbl) right:laugh::good:

its working great. but it is not android rom and i cant run apk

faisala66 said:
thanks but its not booting
Click to expand...
Click to collapse
then it's obviously only for jbbl, switch to jbbl if you want to use this, its a real quick 10 minute process, and since this is a GNU/Linux rom, the downgrade won't do much.

faisala66 said:
its working great. but it is not android rom and i cant run apk
Click to expand...
Click to collapse
well yeah, it isn't an android rom, so you won't be able to run android apps. It is a GNU/Linux based OS, the only way you will be able to run android apps is if you somehow hack in alien dalvik (edit platform manifest file, cross your fingers), or get one of the other android emulators set up. The reason you use Sailfish OS is because it is lightweight, fast, and a generally beautiful and fun to use OS.

It's stuck in the bootlogo here.
I used the CM11 mentioned in the OP (from here), SailfishOS 2.0.1.11 (from here) and ilichva's TWRP 3.0.2-1 (DiamondJohn's TWRP 3.1.1-1 failed with error 7). Both data and system partitions are ext4. Am I missing something? Thanks in advance.

hernandezjonathan21 said:
It's stuck in the bootlogo here.
I used the CM11 mentioned in the OP (from here), SailfishOS 2.0.1.11 (from here) and ilichva's TWRP 3.0.2-1 (DiamondJohn's TWRP 3.1.1-1 failed with error 7). Both data and system partitions are ext4. Am I missing something? Thanks in advance.
Click to expand...
Click to collapse
you are on JBBL right? I used that same zipe and rootfs and all is good.. you flashed the cm zip, then the sailfish zip on top without wiping anything right? and you wiped all your partitions (except internal and external sd of course) before hand?\
EDIT: You are using a photon Q build on xt907, no wonder it won't boot. grab the one from the bottom of the rahimali afh link or the xt907 one in the downloads section.

Galaxyninja66 said:
you are on JBBL right? I used that same zipe and rootfs and all is good.. you flashed the cm zip, then the sailfish zip on top without wiping anything right? and you wiped all your partitions (except internal and external sd of course) before hand?\
EDIT: You are using a photon Q build on xt907, no wonder it won't boot. grab the one from the bottom of the rahimali afh link or the xt907 one in the downloads section.
Click to expand...
Click to collapse
Alright, gotta try it ASAP (which means in a week or two :crying. Any fixes for the headphone jack?
EDIT: Nevermind, I just saw the updated OP. Now this is looking reaaaally good for a daily driver.

hernandezjonathan21 said:
Alright, gotta try it ASAP (which means in a week or two :crying. Any fixes for the headphone jack?
EDIT: Nevermind, I just saw the updated OP. Now this is looking reaaaally good for a daily driver.
Click to expand...
Click to collapse
headphone jack is being patched in the new update, elros34 should release it by tonight, he was messing with it on the IRC (it'll be based on the newest version of sail and have fixed headphone jack built in, hooray!!! )

I'm replying from Sailfish in my XT907! I tried to install the alpha 3 from @rahimali's folder and it didn't boot (I wasn't surprised though, as it said it was for XT897).
Battery seems to last waaay more than Android and it's really fun to use! I just need to find a way to use WhatsApp.

[TWRP][OFFICIAL][3.2.2-0] TeamWin Recovery For Moto E4(woods)

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.​
​
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
​
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
​
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13

Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.

ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .

if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks

I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.

EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179

Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.

ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.

Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).

ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.

Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.

Tks
Thanks man!

Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.

OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.

Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img

iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽​
Click to expand...
Click to collapse

Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html

I cannot flash gapps arm 7.1.x

Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine

Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?

Android 9 Pie on N7 2013

Any chance we'll see Pie on N7? Even doable?

xenokc said:
Any chance we'll see Pie on N7? Even doable?
Click to expand...
Click to collapse
Let us all hope and Pray....

The way its getting delayed, i doubt pie will come (that too fully stable) for our old device. Last @flex1911 said that Lineage is almost fixed. Maybe be should ask him and motivate more.

abhifx said:
The way its getting delayed, i doubt pie will come (that too fully stable) for our old device. Last @flex1911 said that Lineage is almost fixed. Maybe be should ask him and motivate more.
Click to expand...
Click to collapse
Yeah, I've been working last week on some stuff for Flo, but unable to test since my USB is dead. I got one guy to do it, waiting for him.
I've got no solder now, so can't fix my flo yet. Gonna do it later.

flex1911 said:
Yeah, I've been working last week on some stuff for Flo, but unable to test since my USB is dead. I got one guy to do it, waiting for him.
I've got no solder now, so can't fix my flo yet. Gonna do it later.
Click to expand...
Click to collapse
Apologies for naivete, I just repo sync'd Unlegacy Android Pie thinking that since Flo was in the branch that it was already possible just no one was compiling it.
Again, just a brand-nubian banging my head against obstacles until they give, is it not possible to take say a Marlin P kernel and run it through LazyFlasher to make it Flo friendly?
LazyFlasher is a custom kernel flashing tool designed to make it easy to dynamically modify ramdisks and inject kernel binaries into the current boot image.
It's the swiss army knife of kernel flashing for use in Team Win Recovery Project.
The intent behind it was to allow a 1 custom kernel fits all approach, where your users can flash single zip on any ROM for a particular device,
allowing your kernel to be compatible with the vast majority of custom ROMs already out there. It takes away the pain of building custom boot.img
for each and every variant a user requests and puts it into 1 low maintenance intelligent universal flashable zip.
Click to expand...
Click to collapse
Thank you for persevering and keeping this awesome device awesome.

Here is an android pie ota package for nexus 7 (flo):
https://forum.xda-developers.com/showpost.php?p=78575088&postcount=1811

Dummy question - how to flash that OTA package?