yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Older builds are in "History" subfolders of respective versions/types. I keep all of them until they're deprecated and SF asks me to purge.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Thanks @AndyYan also i would like to ask that if there will be solution of this non booting experiences due to Google's changes will be resolved or not
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If your non-boot doesn't reach bootanimation and pstore is absent, I'm afraid it's beyond my knowledge to analyze. Perhaps the larger TD community could be of more help.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Like it'll be stuck on Lenovo logo only and after it keeps bootlooping
[Treble-Enabled Device Development A/AB ROMS] stanley321:
Are there ways to get Xiaomi DT2W from TD to work on Light?

This is the only patches that is missing for me.
[Treble-Enabled Device Development A/AB ROMS] sso003:
Coincidence? I also have a Lenovo device (Legion Y70) which also would not boot with the latest rom, but works fine with the february build.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Yeah I think the problem will be solved soon
[Treble-Enabled Device Development A/AB ROMS] joselap:
Hello, I have tried to install the latest version lineage-21.0-20240518-UNOFFICIAL-gsi_arm64_gN.img.xz, but when configuring I get the message, "This Device isn't Play Protect certified". Does this happen with any phone? Mine is a Mi 11 lite 5G? I know the way to certify, but this only happens to me with these gsi roms. Greetings to all and thanks for the roms....they are going great
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
If said patch works for my current main (which I'll take a look later via DSU), I could absorb it, but probably without a UI toggle. Honestly I'm sick of brand-specific traits and would not like to make an opening for adding lots of them into Light, that would defeat the purpose of why it existed to begin with.

"Spoof system properties" and reboot; if that doesn't do it, resort to Magisk/KSU and their modules better written for the purpose.
[Treble-Enabled Device Development A/AB ROMS] stanley321:
Understood your reasoning behind, it is the right thing to do too.

I tried to cherry pick it my self but I can't find the commit for Android 14.

I can only find these 2 related commits for Android 12

Xiaomi DT2W ioctl binary to control /dev/xiaomi-touch

Fix DT2W on Xiaomi Mi 11 Lite 5G by using xiaomi-touch · phhusson/device_phh_treble@a66fa56

It may also fix for other Xiaomi devices

github.com

Prop handler shell script from Line 15 to 63

device_phh_treble/phh-prop-handler.sh at 26f132c4caefe410255d819f08546b391916a203 · phhusson/device_phh_treble

Android device-tree for generic Treble target. Contribute to phhusson/device_phh_treble development by creating an account on GitHub.

github.com

I copied the xiaomi-touch binary from your TD build, and ran

xiaomi-touch 14 1

but it keeps saying BUS error. Not sure what was missing or the binary changed for Android 14 such that the above shell command won't work anymore?

I need some help to get it to work, if we can get it to work with one binary and one shell script, I agree that there is no need put it in proper Light build, just add the steps to the FAQ or something similar.
[Treble-Enabled Device Development A/AB ROMS] Osanosa:
No boot on MTK G96. Stuck on bootanimation. No adb detection, can't take logs. Stock A12.
[Treble-Enabled Device Development A/AB ROMS] Hatrackman:
anyone using moto g power (2021) for last couple updates?
[Treble-Enabled Device Development A/AB ROMS] stephenjleng:
I am also using a K70 (Vermeer). Thanks for your building. it is better than my imagination. I will use it on a daily base.
[Treble-Enabled Device Development A/AB ROMS] asylor:
It works again on my device with vanilla version (POCO F5). The minimum sound volumn issue is fixed and is much better now (thanks a lot I can watch videos with bluetooth earbuds again). I find a new minor bug in this version but might be device issue. Sometimes the camera does not work even if camera right is granted (toggle the right won't work and it keeps saying it has no right), it can be solved by simply restaring the phone.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Check out TD-based?

Next month I'll add an option that makes the UI a bit smoother still, for certain devices like ours - I've been using it on personal builds.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
@AndyYan Does that option will be added to los 20 as well or not
[Treble-Enabled Device Development A/AB ROMS] Osanosa:
I mean yes, but I was curious about testing this one. Maybe I could at least take logs somehow?
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
So far that option only appears useful for some modern Xiaomi devices (as in, other devices don't show that type of lag to begin with).

My builds are supposed to have ADB enabled, if you don't even have that, the OS must've crashed so early/critically that not even the ADB daemon is up.

If you have a custom recovery and your kernel happens to have enabled pstore, you might be able to get that info, otherwise just don't bother and try TD-based.
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Is this rom compatible with Lenovo Tab M10 2gen x606x?
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
May be it could work try it out once 🤔
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Continuous boot…

Lenovo (orange state) boot, and reboot…
[Treble-Enabled Device Development A/AB ROMS] ForForkSake:
Successfully booted latest TD based release on my Motorola Edge 20 Lite 5G kyoto (Android 12)

As listed Volte does indeed work on Motorola Mediatek S devices

Everything working great. Very snappy.

My one and only gripe is that there is no 5G.. Is that a known wider issue that i have missed? Or is there something i can do?

Your work is much appreciated thank you!
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
In my lenovo m10 x606f bootloop , no way… The latest thst world is the 19 one
[Treble-Enabled Device Development A/AB ROMS] Klangerzeuger:
Look for 5G in the treble settings, there you can set the network to switch from 4G to 5G.
[Treble-Enabled Device Development A/AB ROMS] fondansion:
Hello every all, version (BVN 20240526 of Td Android 14 or lineageos21) is installed on my device, but it does not run, in fact, it does not reach the image of the lineageos bone, and after showing the boot image of the device (Samsung galaxy a21s), it restarts again and a version which runs on my device and has no problem in booting and running. The version of(BVN td lineageos 21 is 20240217). How can I run its latest version 20240526 on my device?
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
No… I tried with x606f and x606fa and after flash, fastboot -w and reboot

It goes to boot loop :-(
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
I've also have Lenovo tab which is 1 gen older than yours but mine works perfectly at first I also experience bootloops then I first flashed the system image and after flashing system i flashed permissiver v5 so my problem solver
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Permissiver v5? I don’t know what is it

I also tried to install the image under twrp but no changes, still loop

And I have two similar tablet with the same results. The latest image that works is Andy’s lineage 19
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
some kernels if set enforcing it won't be able to boot some gsi so permissiver changes it to permissive status so after you flash system image is you flash that you can boot
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Ok I will try to use permissiver and flash again

I must use permissiver on a working os and after that reflash, correct?
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Yes after you flash cleanly just after you flash then you flash permissive v5
[Treble-Enabled Device Development A/AB ROMS] ForForkSake:
Worked perfectly - thanks!
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Where can I take the latest version? Do I install the zip with twrp?
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Flash this in twrp just after you flash system image then reboot remember clean flash your system image
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Lineage 19 installed -> reboot

adb reboot bootloader

fastboot flash recobery TWRP

install permissiver under TWRP

reboot to Lineage 19

adb reboot bootloader

fastboot flash system lineage 21 BGN

fastboot -w

fastboot reboot

Lineage 21 is loading!

Super! The error was solved with Permissiver v5!

Errors:

- Android Keyboard (AOSP) is shutting down and isn't impossible to use the touchscreen keyboard

Fix - Improvement:

- Android Keyboard -> Must be solved

- Smart Dock auto-connection and this will be the latest image for Lenovo X606X/F/FA
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
I'm happy that I was able to help you out you can use other keyboards as aosp is crashing btw which gsi did you use light or td based
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
TD based, now i try to install the light one

What about the smart dock? is possible to port on theses gsi?
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Lemme know if light version works
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
No, the Light Version doesn't work. still loop on boot (lineage-21.0-20240518-UNOFFICIAL-gsi_arm64_gN.img)
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Light is not for legacy devices
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
I also tried the lineage-21.0-20240526-UNOFFICIAL-arm64_bgN-vndklite.img but loops
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
If your device support vndk lite then only it boots
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
It seems supported on other xda forums

But for me is the same light or tb… installed a different keyboard and it works… now I hope to be add the functionality for smart bar..
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
No you've to check by installing treble info app
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
It seems supported also android 14 gsi
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Can you click on more details
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Here you are
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
There you go your device doesn't support vndklite so don't use that image
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
I must use tb based correct?
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
You should use td based but in td based don't use vndklite just use normal like lineage-21.0-20240526-UNOFFICIAL-arm64_bgN.img
[Treble-Enabled Device Development A/AB ROMS] FedeDT:
Super, thanks a lot
[Treble-Enabled Device Development A/AB ROMS] romstockprivate:
Is it possible to setup yubikeys for 2FA?
[Treble-Enabled Device Development A/AB ROMS] fondansion:
Please, if anyone knows, tell me, I would be grateful
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Try permissiver
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
I don't recommend changing SElinux to permissive.

That is dangerous.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
After booting you can change it to enforcing however I'm using permissive and I've got no problems
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
Permissiver is nothing new to me.

I've tried booting Haridhayal's Proton AOSP in the past with permissiver.

But still dangerous.

So don't force your will.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
What's dangerous in using
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
A few seconds of typing in a search engine will answer it.
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
Is switching 'Security Enhanced Linux' feature off... why making a quiz of this, many users are clueless 😜

Gtz

Kurt
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
Here's why you should be wary of installing anything that sets SELinux to permissive

An undocumented Android feature allows any arbitrary app to gain root access on a permissive SELinux environment. Read on to know more!

www.xda-developers.com
[Treble-Enabled Device Development A/AB ROMS] Kurt Krummbein:
good finding :-), must confess, i was too lazy to search as well ... as many people :-(.

But ... i know how dangerous switching of this security feature and that se-linux "permissive" is a no-go, but well, im a Linux-Pro admin ;-).

As you, i'm also fed-up of people who rather ask in chats than first asking the chat's seach functions ... leading to getting same questions over and over :-(.

Gtz

Kurt
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated all variants with Android 14 QPR3 and July security patches. [Insert obligatory backup-and-test warning here]

Just like QPR2, QPR3 can and WILL break devices (old or new)! If your device can boot GSIs via DSU, absolutely try this update in DSU environment first! And regardless of status on DSU, backup important data before commencing update!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
A LONG note with couple of things to address...

Signed builds:

Starting this batch, g* (GAPPS'd) builds would be signed, which is said to be crucial to achieving MEETS_DEVICE_INTEGRITY in Play Integrity. To upgrade (dirty-flash) from an existing GAPPS'd installation, you need to run a migration script - instructions are now on SF.

Just signing the builds isn't enough, other workarounds are still needed to achieve MEETS_BASIC_INTEGRITY first. Unfortunately, during my testing, Securize and current ROM-side integrity hacks no longer work, and as someone outside of the GAPPS ecosystem, I'm not interested in figuring out on my own. As a result, also starting this batch, ROM-side hacks have been removed, and Securize have been grayed out. You're recommended to use better-maintained solutions such as Play Integrity Fix.

VNDKLite builds are also marked "signed", but as with before, these are entirely untested.

v* (vanilla) builds, incl. personal builds, are still unsigned - I don't see why they should be, and signing wastes a lot of time. If you need such signed, please offer a compelling reason.

And finally, remember the premise:

Signed IMS APKs:

The nature of IMS APKs means that they're supposed to bear the same signature as the GSI, so when the GSI is signed, so must the IMS APKs. However, that means each maintainer must have a standalone set of IMS APKs signed in their own keys.

Over the past month I've worked with PHH on this - with a few changes, we allow using IMS APKs with a known "PHH" signature, thus all GSIs could again use one set of PHH-signed IMS APKs.

For builders - you'll need to pick this fwb commit, and make sure your TrebleApp points to the signed APKs.

Light mode quick settings:

This is a feature I deem must-have, and picked since the beginning of A12. However, as Google starts to revise their design and color specs in A14 QPR2, it becomes increasingly cumbersome to get it to work right, and I certainly lack the designer skills to fix it up natively. Right now in QPR3, I reverted a bunch of Google's revision, with unknown side effects. I expected A15 to introduce major UI changes (which hopefully obsoletes these fixes), but so far the previews show otherwise. I might ditch light mode QS altogether in A15, just so we don't drag unstable code along.

Status and future:

In an earlier post I've touched on the mounting work pressure and burnout. For now I can still sustain monthly builds, but primarily work on things of my interest, plus common major issues (e.g. signing). Other things would be taken slow, even features and fixes you deem basic (e.g. face unlock). If you aren't satisfied, kindly please use some other ROM.

From here on out, GRF would start to show its menace, and devices we once deemed "modern" would eventually fall behind, starting with R vendor ones. Be ready for this to happen every 3 months.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Somehow missed a patch related to Magisk, rebuilding now. Done.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Temporarily moved this batch to History to investigate a potential breaking issue. Do not flash yet.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Updated batch of builds (timestamped 0722) has been uploaded, with the global breaking RIL issue synced/fixed.
[Treble-Enabled Device Development A/AB ROMS] Raptor14:
Version download?View attachment 6127987
[Samsung Galaxy S21 Ultra] gcarter:
Im not liking the performance drop of Android 14 on my S21 Ultra (SM-G998U1) so decided to downgrade to android 13.

However ODIN kept on failing...

PHONE

SM-G998U1

FIRMWARE DOWNLOAD

Samsung Galaxy S21 Ultra (SM-G998U1) - VZW - G998U1UEU5DVK3 firmware

Fast download latest Samsung Galaxy S21 Ultra firmware SM-G998U1 from USA (Verizon) with G998U1UEU5DVK3 and Android version 13

www.sammobile.com

PROCESS

How to Flash Samsung Stock Firmware using Odin Tool - Downgrade OS

Struggling with software issues on your Samsung device? Accidentally bricked your Samsung Galaxy phone or tablet while trying to update your firmware? Don't

www.downgradeos.com

Running the One U 6.0 with January 1, 2024 security patch

Using the original usb cable, latest ODIN version and latest Samsung drivers on windows 11 pc and USB debugging turned on

Any ideas what is causing the FAIL?

View attachment 6061287
[Samsung Galaxy S21 Ultra] PlutoDelic:
Maybe use the patched version of odin?
[Samsung Galaxy S21 Ultra] gcarter:
Is there a link to download this patched version?
[Samsung Galaxy S21 Ultra] PlutoDelic:
Patched Odin 3.13.1

For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...

xdaforums.com
[Samsung Galaxy S21 Ultra] gcarter:
With the latest patched version, still fails with the same error. Multiple phone and pc reboots, different usb ports, same error

I saw another xda thread stating that Samsung had blocked downgrades?
[Samsung Galaxy S21 Ultra] Sir0928:
Can’t Samsung only be downgraded equally? U4 Can S4but can't S3 If there is no problem with your downgraded data cable, you can replace it with another one.odin try
[Samsung Galaxy S21 Ultra] zmag:
I am also interested in trying to downgrade from Android 14/OneUI 6.0 back to 13 (I forget previous OneUi to be honest...)

Instead of opening an entirely new thread on the topic, I figured I would just post here.

To the OP: Have you had any luck? Also, have you made sure the file hashes are correct after downloading to your PC? (i.e. So you know they're not corrupted)

Also, have you tried a newer patched version of Odin 3.14.4 - https://xdaforums.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/

Just wondering what (if any) updates you can provide to your OP. Thanks in advance!

Important Edit

: It turns out, we can't downgrade because our SW revision is A, and all previous revisions are 9.

If you read this page (https://samfw.com/blog/what-is-bit-binary-value), it states the following:

Q: Can I flash lower SW REV. for my phone?

A: Samsung does not allow you to flash lower SW. REV. for your phone. Do not try if you do not want your phone bricked

I'm on DSH, but if you go here (https://samfw.com/firmware/SM-G998U1/DSH) and Filter OS to Android 14, you'll notice the latest SW is Rev. A, and the previous 2 are Rev. 9 and if you change the Filter OS to Android 13 they are also all Rev. 9 -- so we literally JUST missed the boat... if it was still Rev. 9, we'd be able to downgrade.

So basically, we're screwed. I'm not even sure what a factory reset would do at this point. I hope I'm wrong and someone can tell me otherwise that we are able to somehow downgrade. But based on that, it looks like a no-go.
[OnePlus 12] bdvince:
I posted in another thread regarding region-lock already but no one else has reported having issues. I recently bought a OnePlus 12 from Giztop and whenever I insert my SIM card or restart the phone I get the message:

"You are using a region-customized phone. Its calling functions will be restricted in your region. Please contact a retail store for support."

I remember this was a widespread issue with the OP11, however with the OP12 no one else is seeming to have this issue so far. I've read that OnePlus 12 was meant to have it's globalregionlock set to [0,0] in the firmware, however others are saying they have to be pre-activated by the seller and thus receiving an open boxes which mine definitely was still sealed.

I already reached out to Giztop but in the meantime anyone else having this issue besides me? Maybe important to note I am in the US and flashed the CPH2583_232 build for which most others seem to be using Global. Pictures attached.
[OnePlus 12] Canuck Knarf:
I bought from Giztop...Op12 China ...I dont have region lock ..?
[OnePlus 12] bdvince:
Yeah I know, no one else seems to have this issue either. I'm waiting to see what Giztop says but can you let me know:

1. What firmware are you using?

2. What region you have selected?

3. Did you first put in your SIM card still on ColorOS or after flashing to OOS?

4. Was your box open or sealed?
[OnePlus 12] Canuck Knarf:
1. Global

2. Canada

4. I flashed soon files were given to me then put in sim card ( never upated ColorOs )

5. Buds I cant remember anymore

ncphone can get region lock off
[OnePlus 12] qvert:
Did you rebooted the device more than 10x already?

I think the issue happened on OP11 after rebooting 10x

My Op12 i got from trading shenzen as the chinese version, i never rebooted so far but its still working from germany. But it was opened by TS and OxygenOS was flashed by them

edit:

i rebooted my OP12 now 10x and still be able to make phone calls
[OnePlus 12] HellsDelight:
Im not sure on the below commands but according to the comments from this site for the OnePlus 11 those commands should show the region lock state. https://github.com/AndroPlus-org/magisk-module-oplus-cn2global/issues/1

Could you try these and provide the information what these state?

su

getprop persist.sys.radio.globalregionlock (according to this Twitter specific to OP12:

https://twitter.com/i/web/status/1737117125314269664

)

From the site about OnePlus 11 that might be same or similar with 12?

getprop persist.sys.oplus.radio.globalregionlock

getprop persist.sys.rpmb.lock

dial *#3988691#

dial *#899#
[OnePlus 12] Warrenator:
I have a similar issue with you. My Oneplus 12 pop up with region lock message.

At this moment still working.

Not sure how to resolve it
[OnePlus 12] cd993:
Mine is from giztop too, was sealed and for what it's worth (if this may impact it or not) I didn't have ColorOS installed long as converted to global pretty much instantly.

Definitely rebooted more than 10 times. No region lock notification yet..... Here's hoping it doesn't appear!
[OnePlus 12] cd993:
Posting here too..

If you're rooted then this module *may* help...

Releases · AndroPlus-org/magisk-module-oplus-cn2global-regionlock

Contribute to AndroPlus-org/magisk-module-oplus-cn2global-regionlock development by creating an account on GitHub.

github.com
[OnePlus 12] cd993:
View attachment 6061519

Hmmm! My device was sealed and so unsure if Giztop did anything to it to prevent the lock. Also, I'm on global firmware and have been since day one of owning the device (before global launch) and so I'm wondering if I'm safer staying on global firmware...