yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
How are you accessing fastboot? Because Samsung devices generally don't have fastboot. Or if they do (like my devices), it's a non-functional fastboot that can only be used to view a bit of useful info, but is otherwise incapable of flashing anything.

However, if you have a recent-ish TWRP, the developer may have added fastbootd support. From TWRP you can access this fastboot which is only available from the custom recovery. This particular fastboot is capable of flashing, I've used it before. If your TWRP has fastbootd, you can access it from the Reboot button. From there you will see options like System, Download, Recovery, etc. If fastboot isn't listed there, you should find your device's TWRP maintainer and ask them to add fastbootd support.

I pointedly asked if you have TWRP, but you didn't directly confirm or deny. And if you do, it's easier/faster to just use blockdev/dd to flash a gsi instead.

But anyway, I'll just assume you've been able to get into fastboot, one way or another. Before trying to flash anything, type:

fastboot devices

If no output is returned, you're not in a valid fastboot session. You should at least see your device's name returned.

For patching vbmeta, there are numerous ways, but my way is:

Extract vbmeta.img from stock AP tar firmware file. Open vbmeta.img in any hex editor, go to offset 123. At this offset, set the value to either 02 or 03 (the default value here is 00 in my cases). Save the file, tar it, flash with Odin. If you're running stock recovery, it should tell you that Android can't boot, forcing you to factory reset. In the case of having TWRP installed while flashing vbmeta, the device will probably bootloop, so you'll have to get into TWRP manually. I advise temp reflashing your stock recovery.img before flashing vbmeta, it resets some other values along with formatting data partition. You can always flash TWRP after.

Your data partition may be encrypted, so if you're planning to copy the img file to internal storage for flashing with blockdev/dd, you should format data from TWRP. This will remove encryption and it will stay removed, until you've tried to boot Android.

Edit: Sorry for the not so simple way of editing vbmeta, but it's the fastest way I know. And the offset/hex values, I didn't just pull them out of my ass, they do mean something. I just forgot exactly where I got the info from.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
I used a patched recovery to have fastbootd (https://github.com/physwizz/Patch-Recovery)

Sorry for not answering all your questions, it's a little difficult to understand everything when you don't have English as your main language

I'll try to flash via TWRP then, could you tell me the steps?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I already did, but I left a few things out.

In my case:

Open TWRP terminal

Commands (in order):

blockdev --setrw /dev/block/dm-0

dd if=<PathToGsiImgFile> of=/dev/block/dm-0 bs=4096

Dont type the < and > characters, but it has to be the path to the file on the device. If you're putting the file in internal storage, decrypt it first by formatting data partition. Or put the file on MicroSD.

For internal storage, the path is probably /sdcard/<ImgFileHere

For external storage the path will likely be /external_sd/<ImgFileHere

And dm-0, dont use that until you do this:

In TWRP terminal:

cd /dev/block/mapper

ls -la

Note the dm- path of system, and use that value. It may be dm-0, or something else. If it's not dm-0 like in my example, then use whatever you found listed from that command output.

You will probably see other partitions like odm, product, vendor listed there, ignore them. Your device is new enough that it should have a super partition.

when the dd command completes, check for errors. its should something like X # of GB written. But if it says something like "out of space" or "not enough room", etc, then you have an error. These errors are possible if the img file you're flashing is too big to fit in the partition. In that case you will have to find a smaller img, like the non-vndklite img files.

Assuming there are no errors, format data partition from within TWRP. Then try to boot. If still stuck, and you've hit no obvious issues, then your vbmeta is most likely the issue.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I checked the recovery link you sent, it doesnt look like TWRP. Are you really sure you have TWRP? Because that link seems to just be a fastbootd patcher for stock recoveries.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Ah yes, bootloop again, I'll try to fix the vbmeta issue then and see if it works
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
It's right here: https://xdaforums.com/t/recovery-a14-teamwin-recovery-project-for-galaxy-a14-4g-exynos-850.4635006/
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Okay, there's 2 files on AP: vbmeta.img.lz4 and vbmeta_system.img.lz4, what's the right one?
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
There's no 123 offset on vbmeta.img.lz4 and either on vbmeta_system.img.lz4
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
I'll try to contact @Holodroid to see how he've managed to flash this GSI on A145M
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You need to extract the vbmeta.img.lz4, which will leave you with vbmeta.img. Patch that file, flash it.

If on Windows, you can use 7-Zip zstd to extract it.

I have never heard of vbmeta_system.img.lz4, so I wont advise for or against. My stock firmwares dont have it.

I just figured you would infer that the lz4 files need to be extracted. and i hope you arent making the mistake of not extracting the gsi img from the xz file....yet another possible source of a bootloop.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
How I do that? I tried with 7Zip but it failed, "Cannot open file as archive"
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Try with 7-Zip zstd. Not regular 7-Zip.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Yeah, I did that rn but still no 123 hex number offset on it, I give up :cautious:
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Upload the vbmeta.img file somewhere and send it to me.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Don't waste your precious time with it, my device is garbage, but here you go: https://anonymfile.com/7nan/vbmeta.img
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Give me an hour or 2, I will patch and upload it. But while you're waiting, I highly suggest that you reflash your pure stock recovery.img (unmodified) before flashing the vbmeta I will send.

And upload your vbmeta_system.img, I want to take a look at it.

No worries, once I'm back in front of my PC, the modifications will take no more than 5 mins to edit and upload.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@G4stavoM1ster: Here is a reference link for the offset 123 and the possible hex values for that.

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
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Take a look by yourself: https://anonymfile.com/Wn7o/vbmeta-system.img
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@G4stavoM1ster: if patching vbmeta and vbmeta_system img files won't let the gsi boot, would you be willing to let me remotely access your PC via TeamViewer? I would be able to do anything you can do, as if I were sitting in front of the PC. You will have full control and will be able to see everything I'm doing. And you can terminate the session at any time. After that I'll no longer have access.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
It's my last hope (behind @Holodroid, I really don't know how he managed to install a GSI on A145M), I don't have TeamViewer, but I have AnyDesk
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
We can try that, if it gets that far. I've only ever used TeamViewer for remote access.

Maybe your friend is a super Android hacker wizard? Nah, I doubt it. Whatever he can do, we can do too.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@G4stavoM1ster: I've just gotten home, will upload the files shortly.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@G4stavoM1ster: Here is the patched file. I used Frhed hex editor to do the change. I patched both img files and put them in a tar file. Boot your device into download mode, flash the tar with Odin. Use Odin's AP slot. Hopefully you have reflashed your stock recovery.img already, because as soon as you flash this file, the device should auto reboot into recovery and ask you to factory reset. Let it do so. After Android is booted, you can flash TWRP again.

Once you can get back into TWRP, flash the gsi img again, format data partition, try to boot again.

If that doesnt work, we can arrange a remote control session.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@G4stavoM1ster: I forgot to attach the file.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
Sure, can you pls explain step-by-step what I'll do? :)
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I already did. Scroll up the page.
[Treble-Enabled Device Development A/AB ROMS] G4stavoM1ster:
@AnonVendetta Same old bootloop, welp, I'm gonna sleep rn, it's like 3:00 AM here on Brazil, I'm sleepy, yet, thanks for the help
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Weird then. With a unlocked bootloader and patched vbmeta, it should have booted. Unless this gsi just isnt compatible with your device. When you are available we should give another try with fastboot.

Although you should ask your friend what he did. Maybe there's a step you're missing.
[Treble-Enabled Device Development A/AB ROMS] amnesia1000:
Sorry if this has already been asked, but why isn't a BgS version offered?
[Treble-Enabled Device Development A/AB ROMS] Klangerzeuger:
If you need root, BGN with Magisk. In my opinion is the included PHH Superuser outdated, because root for Apps only works with the Superuser App from 2016 and there never will be any update for this App.
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
samsung a14 4G, Mediatek MT6769 Helio G80 no wifi and no mobile data. solution?
[Treble-Enabled Device Development A/AB ROMS] myballgotkicked:
adb shell settings put global restricted_networking_mode 0
[Treble-Enabled Device Development A/AB ROMS] drnightshadow:
Redmi Note 10 5g

Mediatek Dimensity 700 (MT6833)

Mali-G57 MC2

No NFC, no WiFi 5GHz.. any solution?
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
ok 4g working but icon show me 0 dBm 0 asu. That's not good. calling working

The button on the wifi works, but I can't see the networks

your adb command not working for me

EDIT: fully working, It was my fault, bad kernel.
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
Does anyone installed lineage 21 test ROM? Any feedback yet?
[Treble-Enabled Device Development A/AB ROMS] Klangerzeuger:
Its better to wait till next year januar, Andy postet he will bring an stable release.
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
td 14 is my daily driver, it's better than samsung UI 6 or ios 12. I hate these stock versions that track users to the maximum. what's more secure than pure android these days. but on xiaomi redmi note 11 it was misery. on the samsung a14 it's a fairy tale. everyone talks about security and no one really understands it. applications that were supposed to be safe, such as Proton or Brave, are just another Google sauce for making money. i love fdroid and pure android because it's free. and I hate big companies that just make money.
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
I have installed android 13 Andy's custom ROM works like a charm. I just need to know if lineage 21- android 14 is better
[Treble-Enabled Device Development A/AB ROMS] Walterkom:
it depends a lot on what device you have. LOS 13 and 14 is the same for me.e every new generation of android is the same. In five years there was no evolution, we still only have two working systems, Android and IOS, and both are terrible
[Treble-Enabled Device Development A/AB ROMS] vassiliszacharis:
Indeed 😊 though I do prefer a lets say open source system like android than a close system that is iOS
[Treble-Enabled Device Development A/AB ROMS] Holodroid:
Same, but mine is Exynos (A145M).
[Treble-Enabled Device Development A/AB ROMS] dferreira:
Thanks for the work done here. I've successfully compiled and installed LineageOS 20 on an Hisense A9 eink smartphone :) Only thing now missing is porting the eink functionality as the screen requires a proprietary service to interface with the hardware. Any idea where in the device/lineage/gsi folder should I place the stock rom services?
[Treble-Enabled Device Development A/AB ROMS] zVpB9:
Hello! help is needed.

ROM lineage-20.0-20231212-UNOFFICIAL-gsi_arm64_gN

DEV xiaomi 11t pro

At first glance everything works. But I started noticing that applications closing randomly. For example, Google Play (may work well, may crash when viewing the description any app), telegram (not from market), MiHome generally closes immediately. At the same time, Chrome with 80 tabs works stably. What can be done to fix this? I really don't want to go back to Miui..

Thanks
[Treble-Enabled Device Development A/AB ROMS] zVpB9:
maybe it's an oom killer? I saw in the gcam logs that his process was killed by oom killer. How to check/change its settings in modern android?
[Treble-Enabled Device Development A/AB ROMS] zVpB9:
I tried to trace the work of lmk/oom via dmesg. It's empty there. That is, oom probably has nothing to do with it. But, I found an entry in the application logs:

java.lang.OutOfMemoryError: Failed to allocate a 8987248 byte allocation with 8388608 free bytes and 8531KB until OOM, target footprint 37400768, growth limit 37748736

vmstat shows this

lineage_gsi_arm64:/sys/module/oom_kill/parameters # vmstat

procs ------------memory------------ ----swap--- -----io---- ---system-- ----cpu----

r b swpd free buff cache si so bi bo in cs us sy id wa

0 0 606952 353332 8480 2849888 1 4 90 53 1 864 17 21 62 0

When I launch an application that crashes, I see this:

lineage_gsi_arm64:/sys/module/oom_kill/parameters # mm_events

[992.093] perfetto_cmd.cc:999 Connected to the Perfetto traced service, TTL: 3960s

It seems there is not enough memory, but not the OS, but vm java. I tried to look for how to allocate more memory for the VM, but I didn’t find anything useful. This is where my knowledge ends. It's sad that no one has any ideas..(
[Treble-Enabled Device Development A/AB ROMS] skills14:
Thanks for the update, looking forward to trying A14 on my Samsung T510!
[Treble-Enabled Device Development A/AB ROMS] x_berzerker:
hey mates anyone can help me on this?

using los 20-20230622-UNOFFICIAL-arm64_bgN on lenovo legion y70.

trying to use my ds4 controller but after bt connects a rain of logs "bt_btif: ... bta_hh_co_dat ... handler ..." falls down forever till i turn bluetooth off.

found this ticket for another rom/device but it got closed before solved.

Dualshock 4 controller not working · Issue #5562 · PixelExperience/android-issues

Build Date PixelExperience_Plus_vayu-13.0-20230814-0427-OFFICIAL Device vayu Version thirteen_plus Describe the Bug My PS4 controller not working via Bluetooth (idk whether it works via OTG, becaus...

github.com

please help!
[Treble-Enabled Device Development A/AB ROMS] xo.en:
Wait...we can use ps4 pad on android???

Damn :D Why I never...ohhhh....
[Treble-Enabled Device Development A/AB ROMS] a9381:
In MTK devices, all GSIs have a problem (at least in Qin F21PRO) - audio in wired headphones or Bluetooth headphones does not work.

After researching a bit, I found a fix on the Internet for the problem of wired headphones and based on that I also prepared a fix for the problem of Bluetooth headphones.

Only in both cases, it includes entries in build.prop that contain the word "phh", and so also parts of the APK files that are related to the patch. Is it necessary to make changes in TD GSI or will the corrections work as they are?

GitHub - AshiVered/Qin-F21Pro-treble-patches: GSI patches foor Qin F21Pro

GSI patches foor Qin F21Pro. Contribute to AshiVered/Qin-F21Pro-treble-patches development by creating an account on GitHub.

github.com
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@AndyYan: Unfortunately, no dice, the bvs build doesn't boot either. So now we know that, in my case, the rom's secure status, or lack thereof, isn't a factor. If you don't need any logs, then I'll delete this DSU ROM.

Just like the other LOS gsi from the same build date, it hangs on the Samsung bootloader unlocked warning, then drops me into TWRP. From there I can boot the non-DSU gsi. I tried booting twice to be sure.
[Treble-Enabled Device Development A/AB ROMS] ykom:
On my MTK phone, Umidigi S5 pro, BT works fine as well as wired. Also sim works well on OS20, but never on19. A dirty update never worked so far.
[Treble-Enabled Device Development A/AB ROMS] Luckz27:
I searched the thread but I didn't find the answer I was looking for:

is this GSI “microG-ready”?
[Treble-Enabled Device Development A/AB ROMS] MPK99:
Two strange issues:

1. Auto rotate doesn't seem to work. Anyone confirm this ?

2. During media playback, when a notification sound arrives, it drops volume to half (& doesn't regain until I restart the player)
[Treble-Enabled Device Development A/AB ROMS] MPK99:
Yes. *vN secure + magisk + nift4's microg module.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Ah, you may be correct.

I don't mean to be bothersome, I have zero experience with development. I understand that securizing is generally one way; is this what removes SU? What I was hoping was to use an unrooted unsecured build, and patch it with Magisk.

I don't see any secure builds for 18.1 or prior on your Souceforge. Is there a repository of any more GSI/Treble builds anywhere, or is it just the ones you've built?

Could I just use the SU removal tool on one of the **S builds? Or are those tools only for LineageOS 16.0 and below?

I may have to educate myself on how to build something and see what I can come up with. If I understand correctly, you're saying SU is included in the LineageOS source code so there's not really any such thing as a "sterile" build that hasn't been rooted - it can only be removed during or after build?
[Treble-Enabled Device Development A/AB ROMS] bentalebnordine:
Do you know that with magisk, you can root your device only once when using gsi builds, because gsi builds don't have boot, instead it uses the boot of the stock ROM.

But I recommend using the N* builds when the boot image is patched to avoid phh su and magisk su interference.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
I know, that's what I'm trying to do, but in this case all the *N builds are also securized, and for some reason this causes bootloops on my device.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If you were trying to boot mine to check out if there's any progress with exFAT, sorry to inform you that still no. Right now I prioritize life (esp. as China is seeing dramatic changes in CoV measures), then "Light". I'd of course like to have logs on the non-booting issue, but since ultimately you need exFAT in your life, I think it'd be better for you to stick to what you use now, until I actually get to solve exFAT someday.

(Also, I've bought 2 devices with my own money by now, just to see/debug their issues hands-on. I should really stop doing that...)

Looks like you just have to turn on the 2 corresponding toggles in PHH Settings?

Securize is a PHH concept. On PHH AOSP, PHH-SU is universally included on all variants, and Securize removes that, irreversibly (after Securizing, without SU, it'll be hard to add anything into /system again). But not only that - it spoofs lots of props to their vendor value, so that the device has a better chance to pass SN and such. Right now it seems one or more of this spoofing upsets a few certain devices.

After a most recent vote, I decide to build *N (no PHH-SU) and *S separately, so no need to remove SU, and the prop spoofing might be reversible, that's what I'm eyeing to do.

These are LOS-SU concepts, and LOS-SU had been dead since A10.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Did it ever occur to you that I was asking if there are any logs you want, because i'd like to help? Regardless of the exfat status. Besides not booting on my Tab S7+ or Note 20 Ultra, there are likely many other Samsung devices out there that this gsi currently isn't booting on. Wouldnt it be nice to get a better idea of what the problem is, so you can improve booting compatibility on more devices?

But I just realized that it may not be possible to get logs, since the booting never proceeds past the bootloader screen. From what I can tell, the data partition doesn't get populated either, it just stays empty.

The last time I was able to boot one of your gsis (a 19 build), exfat didn't work, but ext4 and fat32 did. And they are able to mount automatically despite not being in the 1st partition slot on the MicroSD (partition scheme is MBR, not GPT, so limited to 4 primary partitions max). It was also interesting to note that I could mount the exfat partition manually via terminal commands. It was as easy as creating an empty directory in /mnt/media_rw/ (or maybe it was /storage/, can't remember), and then mounting to that path. At least that way I could access the files, although it needed to be done after every boot. In the case of fat32, I found that it could be no bigger than exactly 32gb, or else windows would complain that the volume is corrupt. I'm pretty sure it has something to do with the # of sectors that fat32 can address.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
me being a samsung user owner of galaxy A32 4G (SM-A325F) can confirm this gsi is on booting just fine. Works great. android 11 vendor works, 12,13 all of them work. (13 is basically still android 12 vendor but they changed it and its way better for my phone). infact am using it as a daily driver
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I just realized this part as well... You can peek if /sys/fs/pstore has anything after it kicks to TWRP, but if it's empty, we won't have immediately useful info unless someone build a kernel with pstore enabled for the specific device.

Yes that'd be great, but with all the things going on, I don't want to promise everyone everything and keep many of them hanging on the backlog for long.
[Treble-Enabled Device Development A/AB ROMS] V0latyle:
Well, you are completely at your own prerogative, and everyone would do well to remember that. We appreciate your hard work but life always comes first, and we should simply be grateful you have chosen to share your hobby with us. You owe us nothing, good sir.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Well, that's nice to know. But I'd still be willing to bet that there are some Samsung users out there that can't boot this gsi. I too am using Android 13 vendor, I upgraded my stock firmware recently. I can't really say that it's better than 12 vendor, I see no differences at all. Not worse, or better.