If you could, can you put a simple guide up. Im used to custom roms and have not flashed a treble rom before. Just wanna make sure I did everything correctly. Is there anything specific I have to do since it's a/b?
[AOSP 10.0] [2019-12-06] Quack Phh-Treble
- Thread starter phhusson
- Start date
If you could, can you put a simple guide up. Im used to custom roms and have not flashed a treble rom before. Just wanna make sure I did everything correctly. Is there anything specific I have to do since it's a/b?
Try this guide from xda:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
That's the guide I tried to use, I didn't know if there was anything I had to do different for a/b partitions. I'll wait for the next upload and try again. hopefully the new commit fixed it. I appreciate you posting that here though cause now I don't have to look for it again on the next release.
Honor Note 10
Not sure if my opinion on this matters to you, but I've been using Berkley roms on my Note 10 as they have the same SoC and the roms work perfectly with little to no bugs. So when I saw the picture posted containing the Honor View 10, I reverted my phone to EMUI 8.2 through e-recovery and flashed the system image a-only through fastboot.
Phone booted up and it was stuck in the android bootlogo before the phone restarted itself back to e-recovery.
Not sure if it's because of EMUI 8.2 as I know the View 10 has EMUI 9 already.
Not sure if my opinion on this matters to you, but I've been using Berkley roms on my Note 10 as they have the same SoC and the roms work perfectly with little to no bugs. So when I saw the picture posted containing the Honor View 10, I reverted my phone to EMUI 8.2 through e-recovery and flashed the system image a-only through fastboot.
Phone booted up and it was stuck in the android bootlogo before the phone restarted itself back to e-recovery.
Not sure if it's because of EMUI 8.2 as I know the View 10 has EMUI 9 already.
@phhusson
Hi,
i just flashed your Treble Rom on my xperia xz2. It boots without problems; i will make more test regarding functionality.
But i notice that the sec patch stands at September 2019.
So my question: Can you make the next build with the actual security patch?
Edit 1:
I tested a little bit the functions. Basic functions seems to work.
Only bluetooth, NFC and camera don't work.
Hi,
i just flashed your Treble Rom on my xperia xz2. It boots without problems; i will make more test regarding functionality.
But i notice that the sec patch stands at September 2019.
So my question: Can you make the next build with the actual security patch?
Edit 1:
I tested a little bit the functions. Basic functions seems to work.
Only bluetooth, NFC and camera don't work.
Last edited:
Asus Rog 2
Amazing rom
The only one that boots
Ultra fast and smooth
But
No 90 or 120 hz support
No always on display
Please fix
Amazing rom
The only one that boots
Ultra fast and smooth
But
No 90 or 120 hz support
No always on display
Please fix
Xiaomi Mi 8 SE
Tried with both system-quack-arm64-ab-vanilla and gapps version.
Device is using system as root and supports treble as per Treble Info app
Using as base xiaomi.eu 9.10.24 (Android 10), so it's an Android 10 vendor / firmware
Tried with TWRP 3.2.3-1227 and 3.3.1-1024
Procedure: flash 9.10.24, boot, reboot to recovery, factory reset, flash system image, reboot.
Device is stuck on Mi splash screen for ~5 seconds, reboots a couple times, does the same thing, then boots to recovery. No bootanimation, so I'm not even sure it's a bootloop, seems like it can't start the system at all.
Can't grab logs as adb is not running at the splash screen, also /proc/last_kmsg doesn't exist in recovery.
Let me know if there's anything I can do to get more information to fix this, or if anyone on Mi 8 SE managed to get a quack GSI to run, thanks.
Tried with both system-quack-arm64-ab-vanilla and gapps version.
Device is using system as root and supports treble as per Treble Info app
Using as base xiaomi.eu 9.10.24 (Android 10), so it's an Android 10 vendor / firmware
Tried with TWRP 3.2.3-1227 and 3.3.1-1024
Procedure: flash 9.10.24, boot, reboot to recovery, factory reset, flash system image, reboot.
Device is stuck on Mi splash screen for ~5 seconds, reboots a couple times, does the same thing, then boots to recovery. No bootanimation, so I'm not even sure it's a bootloop, seems like it can't start the system at all.
Can't grab logs as adb is not running at the splash screen, also /proc/last_kmsg doesn't exist in recovery.
Let me know if there's anything I can do to get more information to fix this, or if anyone on Mi 8 SE managed to get a quack GSI to run, thanks.
Thank you for the info. Unfortunately I'm on the US View 10 which is getting nothing. I'm on EMUI 9 and don't look like I'm getting anything more anytime soon.
I'm using the latest Germany October vendor, and elementalx kernel, ?? not sure what's going on
hi, can you show me step by step?
@suzook show me the step as below, please check if anythings wrong.
and do you know where to get the vbmeta.img? is this from the ROG 2 ROM? thz
Boots on Wileyfox Swift 2 Plus. but no fingerprint(wifi, Bluetooth works didn't check data as I didn't put a Sim card in) managed to transfer most of my apps but as Play Store is not certified, some would not even appear in the store.i see superuser is also installed, is there a way of un-installing superuser? as I would like to install Magisk (I did try via twrp, but I got a boot-loop) also the dark theme flickers on certain apps(including play store) but at least I know Android 10 boots on my phone!! roll on the updates! thanks
Attachments
Last edited:
You can get the vbmeta file from the raw Rom
Steps are very easy
Did you unlocked bootloader ?
Pm me with telgram
Rowihel2020
@phhusson
I would also prefer Magisk instead of Superuser because of the following reasons:
1. The twrp for Android 10 needs still some time so i can't install Magisk over twrp atm (and as far as i see it there's no boot img provided from you to patch it via Magisk Manager).
2. My prefered Tracking and Adblocker (AdAway) works on Android 10 only via systemless mode which needs a Module in Magisk. And this module is missing without Magisk so AdAway doesn't work.
I tried it with Ad and Tracking blocker without root requirement (for example Blockada and Nebulo) but these apps breaks the built-in DNS over TLS.
So would appreciate Magisk instead of SuperUser, too.
Or does anybody know how i can get the boot.img out of booted system?
Last edited:
Note: when changing rom (in this case gsi always go back to stock boot/vendor) so as to narrow down where issues might be from, flash stock os and try again this goes to all complaining of booting issues
1. Never use beta firmware, only use stable vendor releases
1. DON'T EVER INSTALL THOSE ****ING ****TY XIAOMI.EU FIRMWARES
There was already an explanation as to which variant to flash...
I added a Question about which vendor to use.
Uh, that's interesting considering pretty much every GSI on this phone was running off of a xiaomi.eu firmeare... not even sure it's possible to run it off of Chinese vendor / firmware. I'm pretty sure I've never seen it at least. Guess I'll wait for the next stable miui release, it'll likely be based on Android 10 and I'll try with that vendor then. In the meanwhile if anyone's currently running a Quack GSI on sirius, please hit me up.
EDIT: so I've had a look at the xiaomi devices in the treble_experimentations wiki and it looks like mi 8 se is the only one which is only available in China. This might be why we're forced to use xiaomi.eu firmware, as this phone unlike other Xiaomi doesn't have a global miui version.
Last edited:
I was able to get this rom to boot on a Umidigi X, but the storage size is only showing 5gb instead of what it should be which is 128gb. Any ideas on how to fix it?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
196Hi all,
Here is the thread about Phh-Treble for Android 10.0, codename Quack.
The goal of Phh-Treble for Android 10.0 is the same as for Android 8.0, 8.1, and 9.0: Bring latest AOSP to the maximum number of devices running Google-certified Treble[1], with full hardware support.
You can download latest release at https://github.com/phhusson/treble_experimentations/releases
Which variant do I pick
To know which variant to download, use https://play.google.com/store/apps/details?id=tk.hack5.treblecheck . Don't use other Treble Check apps, they'll give erronous informations.
And then, you're free to choose between vanilla and gapps variant.
What works?
On some devices, everything. They are still not the majority though.
What you can expect on the majority of devices?
It should boot successfully on pretty much all devices with Google-certified Treble. [1]
Most features should work on the majority of devices out-of-the-box: RIL, WiFi, brightness control, buttons, gestures, ...
However, many devices still have issues with hardware video decoding and camera.
Is device XXX supported?
If it's a Google-certified Treble, yes it is. Unlike Google's GSI, Treble devices supported, there is no exception.
There might be bugs of course, but if you help me, I'll fix them!
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
4. If you're on an Android 8.0 vendor, you'll need to stick to vendors with Security Patch Level before April 2019 (that's a bug of my GSI)
Enjoy!
[1] How do I know my device is Google-certified Treble?
Well it's easy, if your device has first been released with Oreo or more recent, and it has google apps, it has a Google-certified Treble.
Please note that this means only the vendor provided by the OEM is certified, not the one from device-specific ROM.117
Right, that's a fail from me, that will be fixed in next release.
That's intended for devices with optical under-display fingerprint.
I'm respinning a v212 to fix that.7
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 @PHHtreble 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
