yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
Hello,

Some apps only working in last securized variant (2022-11-11), how to fix this?

Or how unsafe is it to use this outdated version?
[Treble-Enabled Device Development A/AB ROMS] darkfloid6:
Use magisk delta
[Treble-Enabled Device Development A/AB ROMS] darkfloid6:
To maybe check background proceses
[Treble-Enabled Device Development A/AB ROMS] zezinho7:
i already used magisk canary.

solution for cyberark + some banking apps: magisk module "universal safetynet fix" v 2.4.0 provided by kdragOn
[Treble-Enabled Device Development A/AB ROMS] ogghi:
Hey there, trying to flash this on Blackview BV9800Pro.

It stays on boot animation forever...any hint?

Flash was done via "fastboot flash system image.img" reporting success on terminal...
[Treble-Enabled Device Development A/AB ROMS] uschipower:
Hi there,

yesterday I started a new try to get running LineageOS 20 TrebleDroid on my Lenovo TB-X605L.

I made 2 identical clean flashings on the device -> formating System and data partitions in TWRP before flashing

First I used

lineage-20.0-20230622-UNOFFICIAL-arm64_bvN-vndklite.img

With this image, booting gets a loop. Every time when reaching androids first start wizard, GUI (not device!) starts again with LineageOS-Logo.

The second try was with

lineage-20.0-20230622-UNOFFICIAL-arm64_bgN-vndklite.img

With this image from last month, there is no loop while booting.

Is this a known problem?

Will this be fixed with next version?

2nd question:

The latest available stock rom for TB-X605x devices is Android 9. GSI-Images replace only the system partition. all other partitions remain or are based on stock rom.

Does this GSI from AndyYan really work without problems with the parts of Lenovo's Android 8 and 9 stock roms?

3rd question:

while developing and maintaining this GSI, do you consider the usage on a-only devices which are converted with MakeMeSaR.zip to a ab-device?

Is a converted device a "real" after converting a real ab-device?
[Treble-Enabled Device Development A/AB ROMS] onlinespending:
For the device I have, Tripltek Pro 8 tablet, LineageOS 20 (Android 13) works like a champ except for one major issue. Every time I try to run apps side-by-side I invariably can no longer access the multi-tasking recent apps and I encounter issues / freezes. "Trebuchet keeps stopping" dialogs come up too. So I figured I'd try other launchers that are compatible with Magisk QuickSwitch (allowing them to control recent apps). But I'm not having much luck there either. Any ideas on what could be causing the predictable issues with side-by-side? Thank you!
[Treble-Enabled Device Development A/AB ROMS] uschipower:
@AndyYan

I just read a little bit about KernelSU.

Some Questions about your Roms:

- why do your Roms not have a GKI-Kernel? Is a combination GSI + GKI not possible?

I am asking because I read that a GKI-Kernel would be neccessary to use KernelSU

- I noticed that you offer non-superuser-Images (...N.img.xy) with googleApps and as vanilla. But Images with superuser, you only offer as vanilla. Is there a reason for this?

- is PHH superuser the same as KernelSU?

- which modules can I use for PHH superuser? Magisk-Modules or Modules for KSU?

- What is the app for pHH superuser i have to use?

- Which gApps do you recommend for your Superuser-Images?

Thanks for your help.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with August security patches. [Insert obligatory backup-and-test warning here]

I've been inactive around online discussions due to day job - here's hoping it doesn't hinder my progress on U when it drops.

I'll only reply to what I meaningfully know - I don't think you'd like a quote then read an "idk"...

Does the spoof properties toggle not work? It's supposed to do most of the same thing as a Secure build.

Could just log me that?

Bugreports from non-stock vendors are automatically deprioritized due to their unpredictiveness.

This is long...

- At this time, most devices out there aren't GKI-eligible to begin with.

- We don't modify GKIs yet, so just grab Google-provided ones or whatever?

- KSU does not seem to require GKI though?

- PHH-SU is a continuation of Koush's Superuser from ancient times. It offers root and only that - for apps and shell that request root. Some valid usecases are modifying /data and /system, running high-privilege shell commands and automation. No modules at all.

- The app is already integrated in *S builds. It looks decidedly ancient but works.

- PHH-SU almost certainly upsets GAPPS/SN (its binary is proudly resided in /system), so I don't provide it and I don't recommend any. For root+GAPPS, perhaps pair Magisk/KSU with a *N image.
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
If I enable the spoofing option the apps still don't work.

Only works on the latest securized version.
[Treble-Enabled Device Development A/AB ROMS] scottyrick2:
Lenovo Tablet TB-X606F. Shout out to Andy on the August GSI. Boot time much quicker on this release.
[Treble-Enabled Device Development A/AB ROMS] Hego.dmsk:
Hey,

how did you do this?

This is what I am looking for quite a while now
[Treble-Enabled Device Development A/AB ROMS] skran:
Hi Andy. Firstly, I'd like to thank you for providing us with one of the best GSI builds, and actively working on this project despite your day job.

I just wanted to suggest the use of torrents as a means of distributing your GSI images.

I've had many times where a download gets interrupted. While it is possible to resume it, I find that doing so corrupts the img file (the hashes change). Thus I have to re-download the image again, with the limited download speeds.

Torrents can fix this while providing quicker download speeds along with an opportunity for those of us with seed-boxes to contribute bandwidth :)
[Treble-Enabled Device Development A/AB ROMS] darkfloid6:
It's your browser issues are you using chrome?
[Treble-Enabled Device Development A/AB ROMS] uschipower:
sure, if you tell me which log you need, and how to get this

would you be so kindly and explain what you mean?

I read this too, but I think this is nothing for normal users.

My first question would be where to get source code for kernel, as it is described ;-)

Why i am asking for KSU, I read some opinions from some users that KSU would be the future, and that with KSU, root would neve be detectable.

will be developed this kind of su in the future?

what about root detection?

Thanks for explanation.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: I'm still stuck on the 5-7 LOS build, and for one reason only...my Sony PlayStation 4 controller no longer works in Bluetooth mode on all builds after that. I can pair it, but Android doesn't seem to recognize it as an input device, and neither do any games/apps.

I've already verified that the issue also exists on all of @phhusson's AOSP builds after that date.

So, who should I report this issue to? I already reported an issue to you with the work profile, and that remains unresolved, so I'm not holding out much faith for a fix. It just sucks when I submit proper logs, only to be told by a dev that an issue can't be found. It honestly makes me not want to report at all.
[Treble-Enabled Device Development A/AB ROMS] zezinho7:
follow these instructions

afterwards you can flash system via fastboot
[Treble-Enabled Device Development A/AB ROMS] golu8:
How to install GSI on samsung devices without TWRP support? Can we use heimdall for this?
[Treble-Enabled Device Development A/AB ROMS] drnightshadow:
NEXT TIME USE SEARCH!!!!!

https://xdaforums.com/t/how-to-flash-gsis-through-fastboot.4353849/
[Treble-Enabled Device Development A/AB ROMS] golu8:
Fastboot does not work on samsung devices
[Treble-Enabled Device Development A/AB ROMS] MPK99:
Nice. Which means one more monthly update iteration is enough for all GSIs to get overlay matching patch right?
[Treble-Enabled Device Development A/AB ROMS] pommefrite8:
Hello,

Firstly thank for your work, it's amazing.

Do you know why when we run with "lunch lineage_gsi_arm64_vN-user" during the compilation we get the error below.

Because it security issue, no ?

FAILED:

In file included from system/libvintf/Android.mk:18:

system/sepolicy/Android.mk:85: error: SELINUX_IGNORE_NEVERALLOWS := true cannot be used in user builds.

Thanks :)
[Treble-Enabled Device Development A/AB ROMS] K-BOX2022:
Hey. He has a problem with Lemfo T. On this Lineage os terribly stutters audio, animations are very muddy, terribly everything goes slow. I tried turning off animations but it didn't do anything. I need to catch some tweaks or something else to make it usable?
[Treble-Enabled Device Development A/AB ROMS] prazola:
Hi, is this quick settings behavior expected?

It happens in both Los 19.1 and 20.

I would like to reduce the tiles per row to 3 or 2, as 4 is quite busy and unreadable.

Phone: Umidigi S5pro

EDIT:

Problem solved using Debloat app to mask out vendor apps.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
Anyone has NFC working with Andy Yan's LineageOS ROMs? or with Phh's AOSP ROMs maybe?

I see it's failing badly, suspect it's the common problem.
[Treble-Enabled Device Development A/AB ROMS] pbgapski:
I have tested both TD and light lineageos 20 GSIs and NFC does not show up in both (poco f4).
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
In Xperia 10 III (latest Firmware) with lineage-20.0-20221111-UNOFFICIAL-arm64_bgN-vndklite-secure NFC ist working great.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
thanks for that.

It looks problems with NFC are due to missing parts in /vendor.
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
The best root strategy for gsi roms is to install a bvn or bgn rom then patch the boot image with magisk, it's better than a built-in phh su because phh su do not allow r/w system

And also installing bvs with patched boot would cause interference between pph su and magisk su
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
Nonsense! With Phh SU I easily modify /sysytem: install /system/etc/hosts with AdAway blocking , install MicroG with unofficial installer.

It just may be narrow in free space. But that's fixed with lptool (carefully).

You may not know but that's not successful with all the phones. Your mileage may vary.
[Treble-Enabled Device Development A/AB ROMS] ykom:
Can it be dirty updated? How can it be done?

Thanks!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I think that part of what you're saying can't be right. My boot.img is patched with Magisk Delta. However, if I install a gsi that has phh su, the Magisk always get overridden by the phh su. Presumably they're both trying to use /system/bin/su as the su binary, obviously both can't coexist at the same time. So phh su takes precedence. However, if I delete the phh su files (from TWRP), Magisk is able to work.

And if I manually create /sbin and add sbin to the path statement in /init.environ.rc, Magisk overrides phh su, but grumbles that it exists. This is because /sbin has priority over /system/bin in the path order, so /sbin/su is found first.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
This here.

Many non-AOSP PHH-based GSIs incl. mine already have this /sbin patch, therefore Magisk kinda works on *S. The existence of PHH-SU can still fail detections though, and that's where secure or *N is really needed.

Just flash an update like you would the original, nothing else.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I've noticed some peculiar behavior when Securizing on non-secure GSIs (tried on a few already):

If I install the phh su app (on a gsi that already has the binaries but lacks the app), securizing causes the ROM to softbrick. And not even a factory reset will allow it to boot again.

If i leave Magisk in /system/bin (by not creating sbin and adding to path), securize appears to work but silently fails (the phh-securize.sh file is still present after reboot, securize is supposed to delete it). I suspect Magisk "locks" the directory and reverts changes.

If I create sbin and add it to the path, Magisk migrates to sbin and securize succeeds. It reboots normally without softbricking.

On an unrelated note, I've tried your TrebleDroid (non-light) on my Galaxy Tab S7+ and a Galaxy Note 20 Ultra, it fails to boot on either device. It's strange, since phh's Android 13 appears to be based on your sources, but boots fine. I wanted to check on the exfat thing again, but can't since boot fails.
[Treble-Enabled Device Development A/AB ROMS] ykom:
"Just flash an update like you would the original, nothing else."

Thanks Andy,

My phone has no twrp and I have to use ADB. When updating OS19 to OS20, I have to ease the system and personal data, so it was a clean installation. I'm not sure that OS20 can be updated without easing the system and data.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I wonder if that's because I now integrally securize *N - I've had one report of that not booting on some other device. Did you try *N or *S?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I can't remember. It's been over a week. The only thing I can remember for sure is that it was a vndklite 11-11 build, because I refuse to try gsis that don't have that "flavor" available.

About the pre-securized gsi thing, they do boot for me. I've tried Pixel Experience (secure during build time) and secure phh Android 12 gsis. No issues with any of them.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Can confirm on my T290. All *N builds bootloop - they get to the splash screen, in some cases the setup screen, but eventually crash and reboot. No idea why.

Only the *S flavors work for me, but since I'm a Magisk user, I was hoping to just patch the unrooted builds.

I've noticed this is true with your older builds, too - 18.1 and 19.1, only the S variants are stable.

Any plans to do a *gS flavor for 20.0?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I only just killed that... I hate excessive variants that are almost identical.

I'll see if making "secure" a toggle (instead of forcing it) works. In PHH AOSP, the SU app and binaries are universally preloaded, and Securize was a one-way trip. Now that it's only some props to be reset, I reckon it might work as a toggle. OR, I might as well grab one of the broken devices and see just which "secured" prop is breaking it. Either would push back the next release further though.

Only the most recent 19.1 update has *N, and 18.1 never had it. What they've had all along is VNDKLite "secure" builds. Please confirm if you meant that instead?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: I'm about to try booting arm64 bvs vndklite 11-11 build. I most likely used bvn vndklite on my last try, since I was trying to avoid manually securizing. It's an extra step I'd like to avoid. And my experience prior to that made me think that it's just better to go for a secure variant to avoid a softbrick. But that was before I figured out that it doesn't happen with Magisk in sbin.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Actually, it does, if you have a recentish version of TWRP installed. Newer TWRP versions usually include something called fastbootd (note the "d" at the end of fastboot, that's not a typo). Just access fastbootd mode from within TWRP, then connect phone to PC. From there you can do things like flashing img files, resizing partitions, etc (both personally tested by me and confirmed working).

My Note 20 Ultra/Tab S7+ do have a native (not depending on TWRP) version of fastboot implemented by Samsung, but it's mostly useless except for viewing some info. I tried a handful of commands, but most of them either did nothing, or I got an error about the command/operation not being supported.
[Treble-Enabled Device Development A/AB ROMS] golu8:
I see but my device does not support TWRP. Same here only fastboot commands work are info commands
[Treble-Enabled Device Development A/AB ROMS] drnightshadow:
So the only solution is porting TWRP for your device.. search the guide on XDA forum.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
This is exactly why I don't buy devices that don't already have a functional TWRP available. It's just too useful to go without, much like root. I do my research before purchasing a mobile Android-powered device.

And while I could try to develop TWRP for a device that doesn't yet have it, that's extra effort that I just don't have enough free time for. And there are enough devs that are plenty more experienced than me.

I'm an experienced Android user, I've been "modding" my devices since the earliest days of Android. But when it comes to things like ROM dev, kernel dev, creating a custom recovery, etc, I have to admit that I don't have that much experience. With more time I could have gotten into these things yrs ago, but there are other life matters that are more pressing.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Maybe you can try using this to patch your stock recovery img to make it support fastbootd.

GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.

CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - Johx22/Patch-Recovery

github.com
[Treble-Enabled Device Development A/AB ROMS] golu8:
patched recovery did not worked broke system but restoring old

recovery fixed it. https://github.com/Johx22/Patch-Recovery/issues/33.

Installed by heimdal and patched locally
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
That sucks. I see you filed an issue report, maybe they can help you fix it. I've never tried the patching myself, don't need to, since I have TWRP with fastbootd in both of my devices. Was just putting it out there as an option for you to try.

Did you try flashing it with Odin instead of Heimdall? I've rarely gotten Heimdall to work properly in Windows or Linux.

If Linux is your main OS, try this leaked native Odin:

OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux

Try out my new Linux flash tool called Thor - https://xdaforums.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in this leaked...

xdaforums.com

It's not too hard to get working, but you might need to manually create some udev rules and blacklist a kernel module. After that it should work fine. It's command line only, no GUI, but easy to use.

If on Windows, just use the official v3.14.x that is available on numerous websites.
[Treble-Enabled Device Development A/AB ROMS] golu8:
I tried to create TWRP but same issue.

Odin cli does not have "Re-partition" option.

Should i just install recovery by selecting AP file?

Or I should

1. untar Ap

2. replace recovery

3. tar Ap

4. install
[Treble-Enabled Device Development A/AB ROMS] tablet_seeker:
Hi everybody! Thanks @AndyYan and devs for the great work. I have built my own image with the github scripts and everything works perfectly fine. :) I just have a quick question.

I would like to add two system files to the build, that belong in /system/framework and /system/etc/permissions.

(Two Samsung files that trick the device and allow Samsung Notes to be installed)

But these folders apparently don't exist after syncing the repos and are only created later in the build.

So I don't know where or when exactly to add them, so they're placed in the correct location in the image.

Any tips on how to achieve this?

Thanks so much!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Flashing recovery should never need the repartition option anyway. And it's best to not use repartition unless you really have to, you could brick the device.

Yes, flash recovery in AP slot.

The TWRP file needs to be named recovery.img, and that img file needs to be compressed in a tar file. The name of the tar doesn't matter, but you must name the TWRP file recovery.img, or it will fail to flash.

Download AIK Mobile and use it to unpack the img file you got (not original, but the one the patching script produced). Just name it recovery.img and put it in the same folder as AIK, then run the unpack script from a command prompt. If it's ok, you should see some folders/files in the outputted ramdisk directory. Maybe the img doesn't have valid contents. Or in other words, it's possibly corrupt.
[Treble-Enabled Device Development A/AB ROMS] golu8:
thanks but I do not need GSI anymore because i will lose instant fingerprint feature.

Yes i may have corrupted TWRP
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I can't answer that for you, it's your decision. Fingerprint has lately been working fine for me on gsis. But every gsi is different, every device is different. The installed underlying firmware can play a big role too. So there are no guarantees. If stock is working better for you overall, i'd say go back to it. My gsi experiences have been mostly good, but it won't be so rosy for everyone else.
[Treble-Enabled Device Development A/AB ROMS] skills14:
Evening all, I have the latest BVN A64 Andy Yan image installed on my SM-T510 after initially following MagenDanz' guide including his version of TWRP but am still having issues with powering the device off? Also I am unable to install magisk

I get an error stating " Failed to mount system_root, I have flashed multi disabler previously in TWRP

Thanks in advance

​
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Issues powering off from where? TWRP? Android?

If the partitions in your super partition don't have shared_blocks, you should be able to mount it this way from TWRP terminal:

mount -o rw,remount /

mount -o rw,remount /system_root

This of course assumes you have a super partition.

As for Magisk, just patch your stock boot.img, flash with Odin from download mode.
[Treble-Enabled Device Development A/AB ROMS] skills14:
Apologies, from the system, I hold power button, select power off and it just sits there until I have to hold down both volumes and power button
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Never seen this behavior on any gsi that I've ran on both of my Samsung devices.
[Treble-Enabled Device Development A/AB ROMS] skills14:
According to other posts its a common fault on the SM-T510? I suppose ill just have to never turn it off ha, usb file transfer works fine along with everything else I've tested and its much snappier without all the bloatware

Thanks for replies
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Try another gsi. Probably same behavior on others though, most gsis share a lot of source code. If a bug exists in one, it's probably also in others released around the same date. But some bugs/issues are device-specific. Not much you can do except file a bug report and wait.

The best place to file a bug report is here, it's where most gsis derive their code from:

Issues · phhusson/treble_experimentations

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com
[Treble-Enabled Device Development A/AB ROMS] skills14:
I have tried two different roms so far, Magendenz' LOS 19.1 which is based off Andys GSI and the latest A64 bvn Andy Yan GSI and they seem to do the same thing, ill report it thanks for the link
[Treble-Enabled Device Development A/AB ROMS] droidkeyboardfan12:
I have twrp installed on a samsung a73, whenever i try to install the rom i get the error unable to find partition for path '/system_root'
[Treble-Enabled Device Development A/AB ROMS] ChristianWS:
Has anyone here found a fix for the Google Sign-in issues? I know Andy can't help with it, but I recently flashed

lineage-20.0-20230815-UNOFFICIAL-arm64_bgN-vndklite and Drive keeps going on the login screen, and Youtube doesn't even open