yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Building as userdebug/eng gets you ADB root even on pure AOSP - LOS locking it behind a dedicated switch is extra protection. This root is also shell-only and can't be utilized by normal apps.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
So the root is an inbuilt function of the adb binary, which is able to grant root access via adb, despite the lack of a su binary. Makes more sense.

Perhaps you can help @n07w3n understand why the device disconnects from the PC when running the adb root command. On my PC, it works, shown in my screenshot. Previous experience tells me this is most likely a driver issue.

The issue for this user:

Seems to not be able to securize/spoof due to a missing toggle

Running adb as root not working, although it should work, and worked for me.

In the end, this isnt my issue, was just trying to help.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Anything special I need to do while building the gsi, to make it userdebug/engineering? Having this root shell could be handy, with or without Magisk.

I'm assuming it's not possible to build it as both userdebug and secure at the same time. They would seem to negate each other.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@n07w3n: for your Samsung phone, install this driver:

Samsung Android USB Driver | Samsung Developers

You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.

developer.samsung.com

You should also replace your adb with the latest binaries by Google.

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).

Also, try a different USB cable. And try with all of your PC's USB ports. Then run the adb root command again.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
It builds to userdebug by default. You can alter the target trivially in the script, but user isn't guaranteed to work, and eng is too slow and unnecessary.

Since *N comes without PHH-SU, all Securize does is spoof a few props like what some Magisk modules do.
[Treble-Enabled Device Development A/AB ROMS] Guanu244:
hi, thanks for your help

Sorry I didn't explain my problem clearly

now I can actually boot before dirty flash to 0218

my problem is i can,t pass cts profile in 0218

I've tried phh spoof system , shamiko, Universal saftyNet Fix

didn't work

i need help
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Did you try encryption? Do you have any news on that?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Encryption should work. I accidentally booted LOS yesterday but forgot to disable it. You just have to remember to format data partition first. I normally flash @ianmacd's multidisabler zip in twrp, because I prefer encryption to be disabled. It only needs to be done once, encryption stays disabled forever, unless you flash stock firmware.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Thank you for your response. I am currently on Lineage OS 20 light. Thinking of just flashing the TD version at the next update. Do I have to consider anything such that encryption works? Are there any real downsides by using encryption? (e.g. while debugging or whatsoever)
[Treble-Enabled Device Development A/AB ROMS] AJ:
same problem as you ,

has anyone gotten it fixed
[Treble-Enabled Device Development A/AB ROMS] AJ:
has anyone got this fixed ??

am fasing the same problem on all td-based roms
[Treble-Enabled Device Development A/AB ROMS] uluruman:
I am using SM-A325F and also have the low brightness issue on the "td" version but only since the latest 2023-02-19 release. I can't try the "light" version because that's my main phone and I don't want to reinstall everything. Obviously that's caused by the latest phh's vendor_hardware_overlay, which enabled the auto-brightness on A32 but also somehow broken the overall brightness scale. I hope that will be fixed, because now the phone is barely useable and for now I have to downgrade back to the January release.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Do you know how I can check that/fix it? I am new to the custom rom scene, but enjoy it very much!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You won't be able to do a used space only backup in TWRP with encryption enabled. Your backup will be of the raw image format. Which means if your data partition is 500 or 256gb (like mine), then your backup will be exactly that size. And then there is the issue of where to save it to. Restoring will take forever as well.

By "used space only backup", I mean that if your data partition is X GB size (whatever it is), but only 20gb (example size) of that is occupied/used by files, then your backup will be 20gb or less. A used space only backup, will only work if data partition isn't encrypted.

Another downside of encryption, you will have to format data every time you try a new ROM. Without encryption, you can just wipe data (not the same as format), the contents of your internal storage will be untouched. Formatting data deletes both data and internal storage.

The final downside, if your ROM gets stuck in a bootloop that you can't fix, you will be locked out of any personal files on the internal storage. Being able to access this stuff is preconditioned on your ROM always booting fine, because you need to be able to access Android to get to them. If you insist on keeping encryption enabled, then I suggest that you constantly backup your internal storage contents to a safe location, like a PC or cloud storage.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you have a Samsung device, flash @ianmacd's Multidisabler zip in twrp. But you must have twrp for this to work. If you don't have twrp or your device isn't Samsung, you can edit your fstab file manually. Or perhaps there are other tools that can edit it for you.

Maybe his zip might work on other non-Samsung devices too, try it and find out. The worst that happens is it can't find the required files to be changed.

Here is my already edited/encryption disabled fstab.qcom file, located in my vendor partition. The only relevant lines in it are the ones that reference /data. I had to add .txt to the end, to be able to upload it, original name is fstab.qcom.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Thank you very much for the detailed explanation! Few things I would like to clarify.

I am very happy with LineageOS and do not plan to try many other ROMs. Hence, the point with formatting data is not of high relevance for me.

I do use the implemented backup solution (seedvault) provided by LineageOS, which as far as I can see backups my phone daily. Then, I synchronize this backup to other devices using Syncthing. So, I will always have a recent backup created by seedvault available. Hence, this point is not of great relevance for me either.

Am I overseeing anything, or does encryption indeed not make a relevant difference for my use case?

As mentioned, I am using seedvault to backup my phone. What are the benefits of a TWRP backup? Is it recommended to do it via TWRP?

Could there be a possible scenario that encryption prevents me from fixing a bootloop?

Thank you already for such precise and helpful explanations!
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I haven't tried Seedvault. Right now I'm using Titanium Backup and Swift Backup. However, both require root. I have read about Seedvault, not every comment about it is glowing. I do know that a non root backup solution will never be as comprensive as one that requires root.

A TWRP backup is useful if you want a backup that covers all files in the data partition (internal storage not included). Backup solutions that run within Android are generally limited to apps only, and maybe things like contacts, stored messages. TWRP let's you create a known good "snapshot" of sorts that you can fall back up and is all but guaranteed to boot, assuming the ROM itself isn't borked (example: you deleting critical files that Android depends on). Just make a known good backup from a point in which it booted fine, and you're good to go. Obviously, any changes made after the backup, and therefore not included, won't be present after a restore. I recommend a twrp backup as a failsafe, you can do it in addition to Seedvault or whatever. Do your in-Android backups more frequently, and twrp backups less, like once or twice per month.

Of course a bootloop scenario will always be possible. With encrypted data, you may be able to get in via safe mode. But if that fails you will probably need to do a clean ROM flash...or....a restore from a TWRP backup. At this point, none of the in-Android backup solutions will be of help, because Android needs to be booted before you can use them.

If you are the only person that uses your device, then IMO a decrypted data partition isn't such a big concern. My devices are with me at all times and noone ever uses them but me, not even my girlfriend or friends or family. My devices are off limits to everyone but me, I'm a real hardass on that point.
[Treble-Enabled Device Development A/AB ROMS] ildar_prophet:
try https://github.com/phhusson/treble_experimentations/issues/2413
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Thank you very much!
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
The error was found and the problem could be solved!!!

As described here under point 6 I have installed the IMS APK.

Immediately after that, the sending of SMS to recipients without RCS to which a sending was previously impossible was possible without any problems.

Another positive side effect:

In the network and Internet settings under "SIM cards" are now buttons with which I can activate and configure VoLTE and WLAN telephony.
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
Well, I thought toggle in Phh settings had been removed and it was only possible to enable via command line...

I was able to securize but the bank app still doesn't work.

Only works on November variant (secure by default).
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
I don't think it's a driver or cable issue.

I can access adb normally, my device is listed and everything looks ok. The problem only happens when I type adb root, the device is disconnected and adb returns timeout
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Glad to see that you solved it. So it really was an LOS issue. I only guessed it was a carrier issue because it seemed logical.

Right now I'm having problems sending/receiving texts to so called "short code" numbers. Especially important ones that come from Amazon, my bank, and a handful of others. I switched carriers earlier this month, that's when it all began.

I can text regular cell #s just fine, no issues with those either way. I know it's carrier specific because I've tested on stock firmware and got the same results. And with several devices I no longer use.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Just try updating your adb.exe to the latest one by Google in the platform tools zip. Awhile back I had issues with adb until I updated the binary. It won't hurt to do this, since google is the producer of the file. Oftentimes older adb versions don't work properly with newer android versions. It's just weird that you say that adb works but disconnects when you type a certain command.

I linked the zip in my previous post. I don't know how you installed it, but you probably used an installer that had an old version.

The proper way is to create an empty folder, add that directory to your user/system environment variables (in windows), so that you can run it from any command window. Extract the platform tools zip into that folder. Optionally, install the Samsung drivers and the generic Google USB drivers. I've rarely had an issue with adb, using these steps.

If you know how to use Linux, download a live distro like Ubuntu, install the adb/fastboot tools from their software repo. Linux has the drivers for most Android devices, already built in. You don't even need to install the OS to your PC's drive, just boot it from a flash drive.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Did anyone already try to flash this GSI onto a Samsung Galaxy Tab S6? I am thinking of trying it, but would love to hear any experiences, if any exist! I am particularly interested in how the SPen works.

Also, I am not sure how to proceed exactly. Questions I ask myself are:

Which version of TWRP do I need to install?

Do I need to flash any kernel after flashing the GSI?

I ask this because I flashed the LineageOS 20 "light" version on my Samsung Galaxy A50 and followed the steps provided on recovery-mode website. These steps included flashing a certain version of TWRP, then the GSI and afterwards a kernel specifically for the A50, as far as I can tell.

Any help or pointing into the right direction is much appreciated!
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
Same problem with the latest ADB

And after that i can't connect the phone until disable adb as superuser option...

I will try on linux. Thx.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I have a tab s7+, i'd imagine your steps would be similar to mine. I won't do a blow by blow.

Ideally, you should use the latest TWRP version, or one that is compiled for the Android version you wish to run (built from 13 source, for 13 gsis). This isnt a hard and fast rule, just don't use a twrp that's too old.

Custom kernel is optional, your stock kernel/boot.img should be fine.

You will also need to flash a patched vbmeta.

This guide is for my device model, adapt and improvise if needed:

https://xdaforums.com/t/guide-a10-a11-flashing-and-booting-gsi-on-galaxy-tab-s7.4282085/
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Ignore the advice in that linked guide to use an Android 10 vendor.img. I have used 11/12/13 vendor images and got much better results. If the latest vendor from your installed firmware works fine with the gsi, don't use an older one.

I also posted in that thread to report my findings that A10 vendor is unnecessary, if you wish to read my other posts there.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Have you tried the November build now, or was it just working back then? Google changed SN/PlayIntegrity logic recently. The current checkbox also needs a reboot to come into effect.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Both the Wells Fargo and Chase Bank apps are working for me, I use those to manage my checking account and a few credit cards. I can play Pokemon Go too, which checks SN. My SN also passes. Perhaps everyone isn't affected.
[Treble-Enabled Device Development A/AB ROMS] AJ:
can tell us about your setup maybe it will help the rest of us , thanks .
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
I flashed the latest version again, enabled securize and reboot the device. I made sure it's enabled.

The bank app alerts me that there is "something strange originating from the cell phone".

In the latest build the device name is not recognized, it comes with the name "TrebleDroid with Gapps".

Theme settings are also having a bug (asking for permission to access images, but wallpaper preview won't update).

It's details and I don't know if it's related.

Then i back to the November build and everything works normally.

Tested files:

lineage-20.0-20230218-UNOFFICIAL-a64_bgN.img

lineage-20.0-20221111-UNOFFICIAL-a64_bgN-secure.img
[Treble-Enabled Device Development A/AB ROMS] n07w3n:
Probably.

I'm from Brazil and I use two banks: Santander and Next.

The Santander app works normally in the last build but Next does not.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I use the latest Magisk Delta, debug version. It allows to have both Zygisk and MagiskHide, official Magisk no longer has Hide. I keep both enabled at the same time.

I have a handful of modules installed, but the only one that's relevant for passing SN, is the modded Universal SN Fix by @Displax. I specifically use the 2.3.1 mod 3.0 version, SN fails with newer version of the mod for some reason.

I also add any apps to hidelist that I suspect may check SN, root status, etc.

I've also enabled securize/spoof system properties in the Phh Treble settings.

That's pretty much it, everything works on the this month's GApps build. Everything I care about, anyway. I'm sure there's apps out there that might not work, but since I don't use them, they're of no concern to me.

I actually don't care that much if SN passes or not. I can live without the apps I use that do check, even the banking apps. For those I can just log in via a Web browser, I will always be able to access those accounts even if their apps stop working. I know there are a handful of banks out there that only allow access via an app, those places just don't get my business.
[Treble-Enabled Device Development A/AB ROMS] kinet1c:
Hiya,

I'm having trouble with google apps signing in. I feel like its something to do with framework?

Chrome, maps and gmail are the ones I've tried so far but they won't see that my google account is already on the phone. They ask me to sign in, but will then say the account is already registered on the device.

Chrome beta andn Dev both will work however.

Ive tried clearing data and cache from all apps involved and allowing different permissions.

If I allow contacts for chrome the app will briefly open, I can see my account to be selected to sync, then it crashes.

I'm stumped.

Cheers

Edit: I have magisk installed with universal safetynet fix by displax, my device shows as certified in google play store.
[Treble-Enabled Device Development A/AB ROMS] IronDwarf:
Can anyone tell me why Verizo doesnt work on GSI roms. I have tried on multiple devices but so far no lick
[Treble-Enabled Device Development A/AB ROMS] insestito:
Working here on Galaxy S22 Exynos.

There is something to implement FACE UNLOCK?
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Thank you very much! I am going to try to flash the TD LineageOS 20 on the Galaxy Tab S6. Before I do that, I would like to know how two things:

How can I figure out if I need to flash vbmeta.image on my device? (E.g. on the Samsung Galaxy A50 I did not have to flash it).

If it has to be flashed, how do I figure out which one to flash?

Thank you!
[Treble-Enabled Device Development A/AB ROMS] nicflack:
Pixel launcher works fine? Cost much battery?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Use the vbmeta.img from your stock firmware. Extract the AP tar.md5, in it you will find a vbmeta.img. if it's compressed with lz4, you can use 7-zip zstd to extract the lz4 to an img.

The best way is to patch it manually, instead of using an empty vbmeta. You can do this with a hex editor, I used Frhed. It's portable and doesn't need to be installed.

Open the vbmeta.img file in Frhed. Go to offset 123, write 03 there. Save changes. Then compress the vbmeta.img to vbmeta.tar, flash with Odin, put it in the userdata slot. You will have to factory reset (cleaned cache/data partitions) after flashing vbmeta, so back up important files first.
[Treble-Enabled Device Development A/AB ROMS] m0byn:
Do you also know how to figure out in the first place whether it is even necessary to flash the vbmeta.img?

It was not necessary on the Samsung Galaxy A50, for example.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I don't know. Try not flashing it and find out. I do it anyway, just to be on the safe side.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If you can't figure out how to use the hex editor, I can do it for you. For me it's less than a minute of effort to extract, modify, save, and recompress.

Even google's own docs say you should use a patched vbmeta with their official gsi (except they provide both ready to download, so no effort on the user's part besides flashing).

But their vbmeta won't have Samsung's signatures, it's just a generic vbmeta. So, you should patch it yourself.
[Treble-Enabled Device Development A/AB ROMS] psychofaktory:
Whats the difference in using a generic vbmeta and a patched with vendors signatures?

I'm using the generic one with my Sony Xperia 10 III.

Can I avoid some possible problems by using the patched original?

And to patch, do we have always write 03 at offset 123?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Patching the vbmeta from YOUR FIRMWARE would retain the signatures of your device's manufacturer. Whereas using a generic vbmeta like what google provides, would not. As for whether those signatures are necessary, who knows, but it's safer to keep them intact. And then there is an empty vbmeta that's filled with zeros, it basically contains no info at all, some have had luck with those. Empty vbmetas are also generic, excepting that they are empty. I'm pretty sure google's isnt.

Here, @phhusson himself explains why empty/generic isn't ok (his comment is further down the page).:

Progress on Samsung Galaxy Tab S7+ 5G (SM-T976B) · Issue #1744 · phhusson/treble_experimentations

UPDATE (May 23, 2021): GSI works with Magisk using A10 vendor (preferrably ATK3). However, there are some stuffs worth noting when flashing. For details, check recent comments. UPDATE (Apr 10, 2021...

github.com

There is another comment there suggesting to put 02, instead of 03, at offset 123, for passing Safety net. But I personally havent had issues using 03, my safetynet still passes, with magisk, and the modded USNF. I've never tested to see if it passes without magisk, with only securize/spoof system properties enabled. I'm always rooted and I insist on having it, so I have no incentive to test without it. I honestly believe that using 02 instead of 03, wouldn't matter on an unrooted gsi with an unlocked bootloader, even if you're using the securize/spoof toggle. And besides that, securize requires root (but deletes it after securizing is finish, if using Phh Superuser), while "spoof system properties" doesn't need root.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: i have an issue when trying to work through the setup wizard after clean-booting the latest arm64 bvn variant. During the wizard, the brightness is way too low, so I can barely see anything. I've tried going into brighter rooms, shining a flashlight on the screen, going outside. But still, the screen is too dim to proceed.

I know that it has booted because the LOS logo is very faintly visible, it's not a matter of stuck boot/bootloop/not booting.

The status bar isn't available at this time, so I can't use the brightness slider to turn it up.

I can think of 2 solutions:

1. Allow the user to pull down the status bar even when the setup wizard isn't completed yet

Or

2. Auto-max the brightness on 1st clean boot, until the wizard can be finished. Then it's up to the user to either activate auto brightness or manually adjust it.