yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] immerblind:
Format your sd card to fat32 on computer (use a simple sdcard adapter or whatever) after that, my sd card works perfectly fine

AOSP 10.0 v202

system-quack-arm64-ab-vanilla.img.xz

works fine on sony xperia 10 dual sim + android 10 software binaries

camera,data, signal,fingerprint,sound,calls etc...the important stuff....all functional.

- adaptive brightness doesnt work, i can change brightness....but the automatic change isnt there....someone get what i mean?

- battery stats....there is no app data....only the graph

- do not disturb seems not to work...or i have no idea how to set it up properly under android 10 :silly:

daily driver material.

thanks for providing me AOSP+SU without gapps

ps i would love to continue seeing AOSP+su-nogapps :fingers-crossed:

ps.: changelog said october security update? in options still september written?

---updated without wipes,from previous release. no crashes or whatsoever
[Treble-Enabled Device Development A/AB ROMS] Ainz_Ooal_Gown:
Oh wait i missed the part about no Magisk .-. so what would we use for root?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Use stock vendor. It is very likely lineage breaks Treble compatibility.

Thanks for the report.

Could you update https://github.com/phhusson/treble_experimentations/wiki/ and create a page for your device mentioning your tests?

Those are fairly easy to fix, you just need an overlay, based on infos from stock rom.

There is a guide there https://github.com/phhusson/treble_experimentations/wiki/How-to-create-an-overlay? or a quite automatic script there: https://github.com/phhusson/treble_experimentations/blob/master/overlay/generate.sh though I recommend you join [MENTION=1960538]PHH[/MENTION]treble telegram group so I can help you create it.

I definitely don't plan on obsoleting it. Though i'm interested, may I ask why you're using this one?

Yup my bad, that's indeed still september.

Hopefully next should be proper november.

Well the zip itself is closed-source, I can't integrate it without its sources
[Treble-Enabled Device Development A/AB ROMS] Dior DNA:
Mi A1

anyone using this Phh Q GSI on Xiaomi Mi A1 ?

I ask because the device is not Google-certified Treble as OP recommends

(it came with Nougat and never got stock vendor).

But it has run Phh O and runs Phh P GSI just fine ...
[Treble-Enabled Device Development A/AB ROMS] jackzkj:
之前的v200b,或者v200c能够进入系统。但是有很多设备不工作。
[Treble-Enabled Device Development A/AB ROMS] eremeya:
You need to use English...

你需要用英文。。。
[Treble-Enabled Device Development A/AB ROMS] hbar98:
[MENTION=1915408]phhusson[/MENTION]

Using a Huawei Mediapad M5 8.4, SHT-W09, can't seem to boot A only with Quack. I updated to your version 120 on Pie and it works just fine.

I used fastboot erase system, then fastboot flash system (quack), then reboot. First I would get a black screen. Left it there for a good while, then tried rebooting. Still wouldn't boot, so I wiped the cache, rebooted, and got the slowly flashing "Android" logo. Waited about 10 minutes, still nothing. Rebooted back into bootloader, fastboot erase and flash v120, and the tablet booted right into Android.

What am I missing?
[Treble-Enabled Device Development A/AB ROMS] noobstyle1337:
Many Thanx ......Dev [MENTION=1915408]phhusson[/MENTION]

Working on Realme 3 Pro like a charm everything works except the fingerprint sensor

The fingerprint sensor is a Fpc102x / FPC
[Treble-Enabled Device Development A/AB ROMS] darren1:
It boots on mine, are you using magisk? If you are you have to use the following modded version.

https://github.com/phhusson/treble_experimentations/releases/download/v200/magisk-phh.zip
[Treble-Enabled Device Development A/AB ROMS] djlukas1983:
Try to format data with the stock recovery after the flashing.
[Treble-Enabled Device Development A/AB ROMS] rajaumarfarooq:
great rom working great on mate 10 lite

camera is fixed with patch provided before

one question

will this rom be able to use the new magisk which s released for android 10 on a only roms or we have to use the moded version provided by the developer
[Treble-Enabled Device Development A/AB ROMS] Mhystes:
FOD doesn't work on MI 9SE last vendor (and previous) (v202 and 203)

Also Wifi is not working on v203 ( no pb on 202)

Another problem is that the notch is detected like she is huge like on poco f1. Hozerver it's just a teardrop.... Si yo miss lot of space...

EDIT: After flashin last vendor (miui 11) wifi is working on v203 and the notch is seems to be well recognized.

Stiil remain FOD not working ( the green dot appear and i can "press it" but the fingerprint enrollement doesn't work so i can't saved one ).
[Treble-Enabled Device Development A/AB ROMS] djtechno98:
tried to flash v203 on k20 pro, booting fine, wifi not working, fp works, bluetooth works, audio not work, pop up camera need to force close over terminal like previous android version. So for now, i think is not stable for k20 pro/mi9t pro
[Treble-Enabled Device Development A/AB ROMS] hbar98:
Not using Magisk.

Did you format userdata when you flashed Quack? That's about the only thing I didn't do.
[Treble-Enabled Device Development A/AB ROMS] darren1:
No, I dirty flashed it over 9. I have done this with both a 10" and 8" Mediapad M5 and both boot fine.
[Treble-Enabled Device Development A/AB ROMS] kalehrl:
No. I have this one which is based on phhusson build but with additional Note 9s fixes:

https://xdaforums.com/redmi-note-9-pro/development/gsi-t4105121

Very stable and no significant bugs.
[Treble-Enabled Device Development A/AB ROMS] valkirian:
Thank you for pointing that out.

I have managed to install stock ROM (after a few hours, because my Honor 8 kept bootlooping).

Just to make things clear, when you are mentioning "put stock back" are you referring to stock ROM, stock Recovery or both? Because I´ve just tried to factory reset, from Settings, and when it boots it goes straight up to TWRP. Once I'm on TWRP it asks me to enter an encryption key - that I've never defined - which ultimately leads to an error flashing GSI Rom on System partition.
[Treble-Enabled Device Development A/AB ROMS] brackenhill_mob:
You need both stock ROM and stock recovery without which, as you've discovered, you can't do a factory reset ;)
[Treble-Enabled Device Development A/AB ROMS] valkirian:
Indeed...oh well. I'm so angry about all of this. My patience is running low ahahah

Anyway, my next step - after getting both of them up and running - should be what? Flash GSI through fastboot instead of TWRP? (To make sure it 'sticks' this time)?
[Treble-Enabled Device Development A/AB ROMS] brackenhill_mob:
After you've done a factory reset in stock recovery, install the GSi via fastboot (IMHO system images should never be installed in twrp - I've had horrible experiences when I've used twrp for this). Once you've got the GSi ROM running you can install twrp if you wish, but you can install Magisk without it if all you need is root.
[Treble-Enabled Device Development A/AB ROMS] valkirian:
I swear to Almighty God that I'm loosing my mind with this procedure...Other phones I've owned are way easier to flash than this one.

Anyway, here's what I've done (not only as you suggested, but also as that tutorial tells me to):

- Get stock ROM and both recoveries (regular and erecovery) up and running;

- Fully boot EMUI and perform a factory reset;

- Let it perform said factory reset;

- Enter fastboot mode after reset and input these commands:

fastboot erase system

fastboot -u flash system system.img

fastboot reboot

- Wait for it to boot.

In this last step is where things are getting really annoying because, as far as I can tell, it gets stuck on bootloop. It says (atm I can't upload a picture, but hopefully I will) something like "your device is booting now" - with those yellow words due to unlocked bootloader - and it stays there a while, then reboots itself, and keeps doing this indefinitely.

I keep asking myself "what the heck am I doing wrong" for this Honor 8 to not be able to boot the GSI Rom?
[Treble-Enabled Device Development A/AB ROMS] brackenhill_mob:
I know your pain as I've had this happen on a couple of Honor phones. Try installing v217 rather than v221. I had weird issues with v218 onwards on various phones but v217 was rock solid on all of them. If that works try later versions as you can dirty flash once you have a working system (provided you stay with this ROM - moving to another GSi ROM probably needs a factory reset)

Also fwiw I never erase system and I don't flash with the -u switch (but I'm on Linux so don't know the procedure on windoze or Mac)

---------- Post added at 01:01 PM ---------- Previous post was at 12:54 PM ----------

If you never see the boot animation and it keeps rebooting immediately, I suspect that /data is not correct.

Reinstall stock and let it do the initial boot. When you see the very first screen (set language) immediately power off and then boot to bootloader to install the GSi. This first bit is important because /data is being formatted with encryption in the background before the language screen appears
[Treble-Enabled Device Development A/AB ROMS] wang1chung:
[MENTION=4575419]valkirian[/MENTION]

Hey, I see you're having trouble, did you by chance close avb after flashing? I only had that issue when I didn't disable avb or I was trying to flash A instead AB ROM.
[Treble-Enabled Device Development A/AB ROMS] valkirian:
It feels good to know that I'm not the only one in this situation, so to speak. Well, I did try to flash 217 as you suggested but, unfortunately, I'm still getting the same "dead end" result.

I've also followed these instructions, but with no luck. The result is still the same: after entering fastboot reboot command, phone boots itself and then gets stuck for a while on "Your device is now booting" and after a few minutes, it reboots and does exactly the same. It looks like the OS is there, but it is not able to boot.

Hello, [MENTION=2824296]wang1chung[/MENTION]. Thank you for dropping by and give a helping hand. If by closing AVB you mean flash the .img file on the troubleshooting section of this tutorial, the answer is yes. As you can probably guess, unfortunately, I'm still not able to boot. Honor 8 is a A device, so I'm assuming that if I even dare to try to flash a A/B GSI version, I would brick it even more.
[Treble-Enabled Device Development A/AB ROMS] brackenhill_mob:
Bummer. I'm afraid I don't know what else to suggest. Sorry :(
[Treble-Enabled Device Development A/AB ROMS] valkirian:
There's nothing to apologize for, man. In fact, you were responsible to keep this "madman's dream" of installing a GSI rom on a Honor 8 alive.

I'll keep checking this thread, only hoping one day I can get it working. On a side note: Honor? Never again!

Thank you for all your suggestions and help.
[Treble-Enabled Device Development A/AB ROMS] brackenhill_mob:
Final thought - try an openkirin rom. I've never known these to fail to bot. If it works, I'd look for a different GSi to try. I've got an old Honor 6X and this GSI was very hit and miss but DarkJoker360 has a GSI one for an Huawei P8 Lite (same phone pretty much) based on this which works really well if I use the March 2020 version, but his July ones barf in the same way you are experiencing.

Huawei/Honor is toast as far as custom ROMS are concerned going forwards as bootloader unlock codes are no longer available.

Anyway good luck!!
[Treble-Enabled Device Development A/AB ROMS] Nordicus:
maybe this topic can help? (#13)

But can't say anything about the relevance of the data))
[Treble-Enabled Device Development A/AB ROMS] Yahoo Mike:
I'm trying to load system-quack-arm64-aonly-gapps.img on a Lenovo Tab M10 (TB-X605F). The device hangs on boot.

The X605F supports treble with VNDK Lite version 28. It's A-only & arm64.

I don't know if it still matters but in [vendor] in ld.config.vndk_lite.txt on the stock ROM, namespace.default.isolated = false.

On boot, the tablet hangs at the manufacturer logo. It does not get to the boot animation. Flashing magisk v20.4 and "fastboot -w" have no effect.

ADB does not start, so I can't get a logcat. When I reboot to TWRP, there are no tombstones, ramoops or last_kmsg to report.

The /vendor/init/hw init.*.rc files refer to 10+ files that don't exist on the GSI (but do exist in the stock ROM).

What's the next step? Do I start modifying the system and/or vendor partitions until I get it to boot? Or is there something better to try?
[Treble-Enabled Device Development A/AB ROMS] stephenobe:
Just dropping by to say I have tried on Razer Phone 2. I am using T-Mobile and from what I can tell they seem to be a small hiccup in this ROM for now. I am having the same SMS and provisioning issues as already mentioned here so I want go into alot of detail, but I do look forward to future builds. Thanks for putting in all the time and effort regardless! 9.0 for now.
[Treble-Enabled Device Development A/AB ROMS] valkirian:
I have to try both. If I can get any of them to work, I'll get back here to report it.

To be honest, before this nightmare, I did manage to install one of the recent OpenKirin LOS versions. On the other hand, I just wanted to go with this specific GSI, as soon as I found out of its existence.

Once again, thank you for those insights and your time.
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
I have a elephone E10 which is A only with system-as-root partition layout i wanted to install V217 but after flashing with fastboot the result is

fastboot flash system system-quack-arm64-aonly-go.img

target reported max download size of 134217728 bytes

sending sparse 'system' 1/16 (131068 KB)...

OKAY [ 3.761s]

tem' 1/16...

FAILED (remote: This partition doesn't exist)

finished. totawriting 'sysl time: 3.767s

the bootloader is unlocked

can someone gave some advice
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
have you tried flashing boot.img and vendor.mg from stock rom after you flashed 217?

Or in TWRP you can wipe data and then reboot...
[Treble-Enabled Device Development A/AB ROMS] wang1chung:
Flash through TWRP, might need to resize your partition
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
I don't have TWRP on my elephone E10 I just flash with fastboot .
[Treble-Enabled Device Development A/AB ROMS] wang1chung:
Try fastboot flash system_a system-quack-arm64-aonly-go.img

Are you sure you're a-only? Did you use the treble checker app?
[Treble-Enabled Device Development A/AB ROMS] SHA_NDY:
Disabling verification on boot

Hi all,

I flashed the latest arm64-AB-vanilla GSI (I have a 64bit A-only phone with system-as-root) and get bootloop after flashing. Since TWRP for my device is not ready yet I used fastboot and did a factory reset prior to flashing system partition.

Does anyone have a suggestion on disabling verifying instances at boot time? I removed the "verify" key from /vendor/etc/fstab for the "system" and "vendor" mountpoint entries but it didn't work for me.

Thanks
[Treble-Enabled Device Development A/AB ROMS] massima:
My suggestion is, not tested yet on my locked Huawei tablet:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[Treble-Enabled Device Development A/AB ROMS] SHA_NDY:
And if my phone doesn't have a vbmeta-partition on its partition list? I can't find it...
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
i can flash in boot or vbmeta i also have a super partition,wich replaces the system partition(i guess),but flashing the V117 in there(wich went whell)makes reboot in fastboot mode.

picture is extracted stock rom elephone
[Treble-Enabled Device Development A/AB ROMS] Visera:
super.img replaces the system.img and its partition stuff (if i remember right) so thats why you can't flash it
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
you can flash in super.img

fastboot flash super system-quack-arm64-aonly-go.img

than it flashes as in system.img... but it doesnt boot but(i guess) goes emidiately in fastboot
[Treble-Enabled Device Development A/AB ROMS] SubSonix1:
Did you ever have any luck with GSI 10?

Do you think you could offer some advice for this please phhusson?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
You need to pick an A/B image.

You need to reboot to fastbootd (instead of bootloader):

fastboot reboot fastboot

Then you'll be able to flash system partition. Don't forget to flash vbmeta as well

Don't do that.

Super is super, not system. system is in super, but it's not alone.

It's like you ask me to remove your thrash, and I remove your whole house instead.

You're giving way too litlle information. Usually this is handled by flashing vbmeta.img with --disable-verification, or by simply unlocking the bootloader.
[Treble-Enabled Device Development A/AB ROMS] SHA_NDY:
My bootloader is unlocked and vbmeta partition doesn't exist.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Update your fastboot, yours doesn't support Android 10 devices.
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
A question, how did you installed this on Tab S4?

I installed TWRP, and installed this build but I'm stuck on bootloop. Do I need something else?
[Treble-Enabled Device Development A/AB ROMS] veekay:
Might be making the same mistake I did of installing the A version - it changed to AB with Android 10 - shouldn't really need to do anything else
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
i am using now

Android SDK Platform-tools 30.0.2 (newest?)

same result

(i am using ubuntu 20.4)
[Treble-Enabled Device Development A/AB ROMS] phhusson:
you mean

fastboot reboot fastboot

still says

?

Can you double-check with

fastboot --version

your fastboot version?
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
fastboot version 1:8.1.0+r23-5ubuntu2

Installed as /usr/lib/android-sdk/platform-tools/fastboot

and

fastboot reboot fastboot gaves the same output
[Treble-Enabled Device Development A/AB ROMS] phhusson:
So you have a fastboot targetting Android 8.1, not Android 10, so I confirm that your fastboot is too old and you need to upgrade it.

If you downloaded platform-tools for Android 10 (or 11) somewhere, what you probably want to do in the shell is

cd /where/is/platform-tools-30
./fastboot reboot fastboot
[Treble-Enabled Device Development A/AB ROMS] Fourcontrol:
Bonjour, je souhaiterais savoir si cette rom fonctionne bien sûr umidigi x, et quelle version télécharger du coup....existe t il des bugs non résolus ou blocant....merci par avance cordialement?
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
it worked rebooting fastboot ( ./fastboot reboot fastboot) on a console in platform-tools-30 after that see flashing result below.... (i havent tryed it in root mode)

ElphoneE10$ fastboot flash system system-quack-arm64-ab-go.img

target reported max download size of 268435456 bytes

sending sparse 'system' 1/8 (262140 KB)...

OKAY [ 12.113s]

writing 'system' 1/8...

OKAY [ 2.539s]

sending sparse 'system' 2/8 (262140 KB)...

OKAY [ 12.275s]

writing 'system' 2/8...

OKAY [ 2.508s]

sending sparse 'system' 3/8 (262140 KB)...

OKAY [ 13.358s]

writing 'system' 3/8...

OKAY [ 2.441s]

sending sparse 'system' 4/8 (262140 KB)...

OKAY [ 12.219s]

writing 'system' 4/8...

OKAY [ 2.532s]

sending sparse 'system' 5/8 (262140 KB)...

OKAY [ 12.153s]

writing 'system' 5/8...

FAILED (remote: Operation not permitted)

finished. total time: 73.571s
[Treble-Enabled Device Development A/AB ROMS] phhusson:
You also need a recent fastboot to flash, so for flash too you need to do ./fastboot...
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
Hmm tried installing arm64 AB version using CTF5 version (Android 10) and still nothing, even after disabling DM Verity.

Could you help me (please :) ) to find what I'm missing? For now I did:

1.- Install TWRP

2.- Factory Format at TWRP (also wiped Data folder)

3.- Install Image AB Vanilla

Also did:

2.1.- Install DM Verity disabler

3.0 Install Image A Vanilla

Thanks!
[Treble-Enabled Device Development A/AB ROMS] devrieshh:
ok it worked the system is om my phone and booted without flashing the old boot.img thanks

s/platform-tools$ ./fastboot flash system system-quack-arm64-ab-go.img

Resizing 'system' OKAY [ 0.008s]

Sending sparse 'system' 1/8 (262140 KB) OKAY [ 12.845s]

Writing 'system' OKAY [ 2.435s]

Sending sparse 'system' 2/8 (262140 KB) OKAY [ 12.937s]

Writing 'system' OKAY [ 2.542s]

Sending sparse 'system' 3/8 (262140 KB) OKAY [ 12.899s]

Writing 'system' OKAY [ 2.537s]

Sending sparse 'system' 4/8 (262140 KB) OKAY [ 12.922s]

Writing 'system' OKAY [ 2.503s]

Sending sparse 'system' 5/8 (262140 KB) OKAY [ 12.946s]

Writing 'system' OKAY [ 2.469s]

Sending sparse 'system' 6/8 (262140 KB) OKAY [ 12.783s]

Writing 'system' OKAY [ 2.574s]

Sending sparse 'system' 7/8 (262140 KB) OKAY [ 12.848s]

Writing 'system' OKAY [ 2.584s]

Sending sparse 'system' 8/8 (215376 KB) OKAY [ 10.562s]

Writing 'system' OKAY [ 2.151s]

Finished. Total time: 120.554s

devrieshh@devrieshh-desktop:~/Downloads/elephone E10 roms/platform-tools$ ./fastboot flash vbmeta vbmeta.img

Sending 'vbmeta' (4 KB) OKAY [ 0.001s]

Writing 'vbmeta' FAILED (remote: 'No such file or directory')

fastboot: error: Command failed

devrieshh@devrieshh-desktop:~/Downloads/elephone E10 roms/platform-tools$ fastboot reboot

rebooting...

finished. total time: 0.051s

system workes good on phone only a verry anoing pop up shows up every time

How to solve that

i havent flashed stock vendor,img (i couldnt find it on stock rom) should i look for some vendor.img?

so far thanks
[Treble-Enabled Device Development A/AB ROMS] veekay:
Just A certainly won't work anymore - the other steps seem fine and should work. Be sure you are formatting the data partition, not just wiping.

Have you also tried flashing Magisk?

Be aware that even if it does boot, this build won't work on this tablet due to the rotation issue - unless it was fixed in the last build.
[Treble-Enabled Device Development A/AB ROMS] WalterCool:
Haven't used Magisk as usually I don't need it, but will try. Maybe I "need" magisk

And last build has something mentioned about Samsung S10 related to rotation, check this https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-Tab-S4-10.5

EDIT: Magisk did it!
[Treble-Enabled Device Development A/AB ROMS] veekay:
Good to hear. From what I see, the rotation issue is still present and that fix doesn't work with these newer builds - if you have a different result I'd love to hear.

Maybe if I could get some other S4 users to post to the github it might get some attention - https://github.com/phhusson/treble_experimentations/issues/1399
[Treble-Enabled Device Development A/AB ROMS] Sundaram6:
Camera not working

[IMG="honor 8 camera and other errors"]https://drive.google.com/folderview?id=1--4NElA6NHA2folzCjxbYrBlvRGB-s9r[/IMG

]

Thanks bro you are great. Just installed this rom on honor 8. I was using open kirin's lineage os build 4 earlier. Installed this via fastboot. Everything is working except the camera. None of the camera apps are working. One weird problem I am facing that most of the apps on playstore are saying that your device isn't compatible. So, I have rely on apk pure for apps. And whenever I restart my phone I get a error which says there's an internal problem with your device. Contact your manufacturer .