Develop Bugs

[ROM][5.1][Flounder] Pure AOSP 3/18/15 [LMY47D]

Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03

Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545

Future FAQ if necessary (let's hope not).

Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon

Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.

mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.

gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery

USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.

build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?

Flounder still isn't listed just lunch it anyway

Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0

Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse

belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.

Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.

omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.

gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?

jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.

[ROM][SUBSTRATUM][N9] Krexus 7.1.1 [OFFICIAL] [03.09.2017]

krexus_7.1.1-170309-flounder.zip - https://www.androidfilehost.com/?w=files&flid=144667 March security updates & Rootless Substratum
THINGS TO READ BEFORE ASKING:
Use N4F26T Vendor Image for 03/09.2017 build.
Stock kernel does not force encryption.
Not prerooted.
Built for the Nexus 9 Wifi (but it works on Nexus 9 LTE too. Flash latest volantisg vendor IMG and manually set APN)
Originally Posted by @KreAch3R
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested ON HAMMERHEAD, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
And lastly, this is first and foremost a ROM about Nexus 5 (hammerhead). This is my personal device, this is where I test the ROM. angler, bullhead, flo, mako, shamu builds are provided AS-IS, and bugs/missing stuff/features especially for them will be put on the lowest priority and will depend on my free time. I will only guarantee the nexus 5 ROM and its abilities.
That said, welcome aboard!
Click to expand...
Click to collapse
Google+ Community
PushBullet Channel
DOWNLOAD LINKS:
KREXUS on AndroidFileHost
Previous Builds
CHANGELOG
Source Code: https://github.com/krexus

When @KreAch3R started building this ROM for shamu in 2015, I jumped on board right away. I've got Krexus running on every Nexus in my family: mako, hammerhead, shamu, grouper, and NOW flounder.
It runs beautifully on flounder and I hope you enjoy it too.
I am extremely grateful to @KreAch3R for all of his help and support.
IMPORTANT POINTS:
You have to flash GApps (Open or BaNks recommended)
ROM is not rooted, flash stable SuperSu for root
Busybox is included
Included kernel is stock no-force-encrypt
Flash newest factory vendor.img (I had Layers issues with stock selinux enforcing kernel on an older vendor version. Newest vendor.img works perfectly with stock kernel enforcing and layers)

F.A.Q.
a.k.a questions you shouldn't repost
Check the always updated F.A.Q.:
https://plus.google.com/+GeorgeGian/posts/f9m7zmi42Gy
OR
https://docs.google.com/document/d/1hMX-lQ2iUiNsrhszMIlp0Wwj1tSHWvsaEQ_yT4pD_eE/edit?usp=sharing?
BELIEVE ME, THE QUESTION YOU HAVE IS PROBABLY ANSWERED THERE.

Thank you for supporting the building for flounder, @buffal0b1ll!
For the next build, I will try to make Layers work with the default google kernel, and fix the processor info.
I want to specifically thank @BeansTown106, which device trees and blobs I used for this bringup.
Enjoy Krexus!

Another more conspicuous link for the Krexus G+ community.
https://plus.google.com/communities/117603046007221302455/
You will want to join this community if you like Krexus. It's very beneficial to hear user and developer advice/feedback and experiences across all supported devices.

Firsties!
Sent from my Motorola Nexus 6 using XDA Labs

Finally, we are starting to get some more quality ROM builds for this device. This is just awesome.

KreAch3R said:
For the next build, I will try to make Layers work with the default google kernel
Click to expand...
Click to collapse
Layers actually works fine with the default kernel and SELinux enforcing. An up to date vendor.img flash was all I needed to fix that.

Is charging extremely slow for anyone else? Latest Fire&Ice kernel.

dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
Try the purenexus version of fire & ice
Sent from my Nexus 9 using XDA-Developers mobile app

dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
I'm still using fire-ice 10.2.2 and haven't noticed slow charging. In 18 minutes I went from 27 to 35% just now. Ampere has me charging at 1460 mAh

Thanks for a great rom! Will it work with LTE version?

maelfilk said:
Thanks for a great rom! Will it work with LTE version?
Click to expand...
Click to collapse
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.

KreAch3R said:
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
Click to expand...
Click to collapse
Will try it out on the weekend and report

Works great with LTE version!:good:

maelfilk said:
Works great with LTE version!:good:
Click to expand...
Click to collapse
That's awesome! Any hoops you had to jump thru?

buffal0b1ll said:
That's awesome! Any hoops you had to jump thru?
Click to expand...
Click to collapse
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.

maelfilk said:
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
Click to expand...
Click to collapse
Sweet. Not even a vendor fingerprint mismatch?

buffal0b1ll said:
Sweet. Not even a vendor fingerprint mismatch?
Click to expand...
Click to collapse
I always flash vendorfix in twrp to 100% avoid this error so can't tell

maelfilk said:
I always flash vendorfix in twrp to 100% avoid this error so can't tell
Click to expand...
Click to collapse
Got it. FYI I'd been manually vendor fixing the fingerprint since December on the Wi-Fi flounder and had layers issues on the stock enforcing kernel. Fire ice made it work with the old hacked vendor partition. To make layers work with stock kernel i updated to may factory vendor.img

my roms

Decided to start fresh here's my work
I will be back up soon for those who keep asking to donate
PayPal.me/samandjoe52 [email protected] all donations will help rebuild my system

My Links for roms
http://androiddevelopers.proboards.com
Alternate link but plz consider using afh link first so I can monitor downloads.
https://drive.google.com/folderview?id=1ujJ2dac56Llwqlf0bd-N8bd9L4ONgkMV
Twrp 3.2.0
https://drive.google.com/folderview?id=1pDh9y5lrdVFQuXXkQEC1zoDlF1vnpygG
Vendor img updated monthly
https://drive.google.com/folderview?id=11Tw8IOqCALXnbwJQX9pIv7GI7PzKi1uJ
Razorloves gapps all credit goes to him
https://androidfilehost.com/?fid=890129502657594387
My teammate build for sailfish thought I'd share
https://plus.google.com/114289258975611350933/posts/TqtMryz4HQ8
Titan du and rr unofficial back up

Mine again

Thanks man!

Du updated still March rr next last rr then doing a different rom things will be slow untill I can afford to replace machine

April updates have been released I'll update once du sources are pushed

Any testers available

So xenon had a big update but still March vendor that's why I'm releasing for testing purposes. It's on my afh. I won't be building as much until I can afford a new machine. I'm almost there. Anyways plz test and leave feedback if ur still on March vendor build will be up in a few minutes

Do answer the big question. Du will be updated april 6 maybe ?

Nice

Du is ready should be up in a few minutes April vendor guys April vendor only have fun

I wanna thank @petiolarissean and mr willis for their donation and i also wanna thank my good friend @Gordietm for guidance and support thank u guys. Also wanna thank dinesh and @Zehlek for always willing to test stuff thank u guys so much and everyone else @NepoRood and @bamafan39 for ur help.

joe_pacino said:
I wanna thank @petiolarissean and mr willis for their donation and i also wanna thank my good friend @Gordietm for guidance and support thank u guys. Also wanna thank dinesh and @Zehlek for always willing to test stuff thank u guys so much and everyone else @NepoRood and @bamafan39 for ur help.
Click to expand...
Click to collapse
It is an honor to be able to test your awesome roms

For those running the latest DU, how is the stability and functionality? Daily Driver?
I'm really missing DU, and haven't made the time to make the switch just yet. Anyone running it with Project Fi?

chowhoundb said:
For those running the latest DU, how is the stability and functionality? Daily Driver?
I'm really missing DU, and haven't made the time to make the switch just yet. Anyone running it with Project Fi?
Click to expand...
Click to collapse
It is perfect, I recommend flashing.

Is their certain steps to flash DU build? I've flashed with and without gapps and Launcher + Gapps FC's both times. I see it's running fine for others so obviously an issue on my end?

liam_davenport said:
Is their certain steps to flash DU build? I've flashed with and without gapps and Launcher + Gapps FC's both times. I see it's running fine for others so obviously an issue on my end?
Click to expand...
Click to collapse
Same as any other just flash april vendor i use open nano gapps and clean flash. Fyi u can install april vendor on even march roms. It will work fine

April version running great and substratum works just reboot and enable overlays. I did notice a audio.media f/c when installing viper4android maybe i did it wrong though as i never use it and i also installed other mods from magisk as well otherwise no issues
April vendor i use https://drive.google.com/file/d/1JKippRKyittsur0r9eptMR3sw9B9z7mO/view?usp=drivesdk
I pulled it personally so i know its workings lol
Steps
Flash rom and twrp. I use twrp still 3.2.0
Reboot to recovery i use hard keys to assure it does so. Once back in recovery flash gapps, vendor image. Mount vendor delete vendor/overlay reboot. Enjoy
Anyone want rr with april patches

joe_pacino said:
April version running great and substratum works just reboot and enable overlays. I did notice a audio.media f/c when installing viper4android maybe i did it wrong though as i never use it and i also installed other mods from magisk as well otherwise no issues
April vendor i use https://drive.google.com/file/d/1JKippRKyittsur0r9eptMR3sw9B9z7mO/view?usp=drivesdk
I pulled it personally so i know its workings lol
Steps
Flash rom and twrp. I use twrp still 3.2.0
Reboot to recovery i use hard keys to assure it does so. Once back in recovery flash gapps, vendor image. Mount vendor delete vendor/overlay reboot. Enjoy
Anyone want rr with april patches
Click to expand...
Click to collapse
I'll retry as using latest twrp might be the issues if not will report with logs. Thanks ^^
Edit: Still same issue with FC's I tried to get a log but can't get to settings to enable usb debugging, Thanks anyway will post back if I can get a log

@joe_pacino, i'm good for testing until may, that's when i'll be testing for google

Question Has Anyone Compiled AOSP 13 and Booted It?

I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.

GrapheneOS has test builds up for A13, which should be buildable using the normal approach. Also hardened with some extra security features.

Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.

I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com

Schnedi said:
I have tried for several days, but I'm missing something
It's a custom rom for personal use. A12.1 booted and worked perfectly but 13 reboots to bootloader
RealSchnedi - Repositories
RealSchnedi has 15 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help

liggerz87 said:
Stupid question have you flashed both slots with 13 as I know boot loader won't load of you have 12 version and not updated to 13 but also it has an anti roll back in it sorry not much help
Click to expand...
Click to collapse
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it

Schnedi said:
I flashed the bootloader and radio on both slots but haven't tried to change the current slot and flash the rom
But if I flash the official 13 release (only in the current slot) it boots, so, not sure if that's the problem. Anyway, I'll try it
Click to expand...
Click to collapse
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}

alvin14 said:
Yes, on ArrowOS, temp issues however that was same day arrow started updating to 13, have not run a build since. Evolution X reboot a few seconds after setup screen loads, does not boot without gapps either.
Click to expand...
Click to collapse
Update on this for ArrowOS. After removing connectivitythernmalmanager that fixed the issue as i am getting selinux denials with it, everything works, been testing for a few days.

alvin14 said:
Been looking at our github, you are using anayw2001 repo for your vendor files, remove the below from Android.bp. I had Restless nights with a poop load of testing thinking it was something with a missing lib file or so when i test anay's vendor files with lots of comparison to lineage extract tools that worked. Well if your getting bootonce-bootloader error that is as reason for bootloader load.
prebuilt_apex {
name: "com.google.android.compos",
owner: "google_devices",
src: "system_ext/apex/com.google.android.compos.apex",
prefer: true,
system_ext_specific: true,
}
prebuilt_apex {
name: "com.google.android.virt",
owner: "google_devices",
src: "system_ext/apex/com.google.android.virt.apex",
prefer: true,
system_ext_specific: true,
}
Click to expand...
Click to collapse
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot

Schnedi said:
I was already using your vendor from gitlab (arrow branch). It did the trick, bootloader not triggered anymore
Still not booting but it must be related to rom sources, will take a look
Thanks a lot
Click to expand...
Click to collapse
Do a logcat during boot, will definitely help with that.

card13 said:
I'm just curious whether anyone has already compiled the AOSP for A13 and booted it. I noticed it had already been done/tested on OP5/5T, but wasn't sure if it had been done for P6P. I plan on trying my hand at it, but wanting to know what others may have experienced before I commit my slower internet connection to downloading the Repo.
Click to expand...
Click to collapse
There is a build of Hentai which is very good. You can even dirty flash from stock

alvin14 said:
Do a logcat during boot, will definitely help with that.
Click to expand...
Click to collapse
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?

Schnedi said:
Thanks, I'm making some tests, not so sure it's the rom sources
Question, to build Evo and Arrow, are you using your adevtool vendor or the other one?
Click to expand...
Click to collapse
Adevtool. The other one works as well however i need to clean it up a bit.

hi guys,
@Schnedi what gapps package are you using for prime?
And does udfps work on your raven with your prime base?

Well, after a dozen of test builds, I finally made it work
Still have to fix things tho

Schnedi said:
Well, after a dozen of test builds, I finally made it work
Still have to fix things tho
Click to expand...
Click to collapse
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?

ny-hardcore said:
Cool. I got oriole too boot prime yesterday too. Nice work!
What gapps package do you use? Is it on gitlab somewhere?
Click to expand...
Click to collapse
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it

Schnedi said:
I'm using this one: https://gitlab.com/spkal01/android_vendor_gms/-/tree/pyro
But removed some apps that can be installed from the store (drive, youtube, gmail, photos...)
Also, latest commit from fw/b fixes udfps
There's just a few features, I just pick the ones I use, didn't build prime to share it, so I'm not picking all of them. You can always fork the project and pick some features you use, PM me if you need any help with it
Click to expand...
Click to collapse
Thanks for the reply, i spark gapps too by the way haha
i picked udfps myself so had it working already
i like your vendor /vendor/extras very clean setup.
i know how to fork, but no need for now

Development [TWRP Recovery] TWRP recovery for SM-F926B based on CVCA

Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)

So just push it as the recovery to the active slot via adb?

Breaks dex? If Not its kompatible with latest one ui?

It doesn't break dex, you can backup your recovery partition, it should be compatible with latest Android, since recovery is contained

Mikowitsch said:
So just push it as the recovery to the active slot via adb?
Click to expand...
Click to collapse
Yes, the usual way works fine

is the link down.. i cant download it

miman04 said:
is the link down.. i cant download it
Click to expand...
Click to collapse
Fixed !

Azkali said:
Fixed !
Click to expand...
Click to collapse
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?

miman04 said:
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?
Click to expand...
Click to collapse
Yes in Odin putting recovery.tar in AP will work fine ^^

i cant download recovery and vbmeta

Azkali said:
Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)
Click to expand...
Click to collapse
404 page on TWRP and VBMETA

Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon

ROM-PacMe said:
Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon
Click to expand...
Click to collapse
I have a newer TWRP, maybe instead of a new build we could figure something out together
Join the discord and ping me there, I'll be available later

Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!

ROM-PacMe said:
Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!
Click to expand...
Click to collapse
is it compatible with SM-926B?
q2q is SM-926B?
google didnt know anything about "q2q samsung"

Can you try, If not working, only re install the recovery stock and vbmeta too

The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?

thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
the revision is a random number gived from Github Actions, nothing more my friend

thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
only use the vbmeta and recovery tar of my own github releases, let me any update, ok?
i see soon any bug to help to fix