yashsingh1/xdaforums huggingface dataset:
[HTC Desire 20 Pro Guides, News, & Discussion] ssurell:
If your phone displays a proper IMEI then it has to be fixed on the server.
[HTC Desire 20 Pro Guides, News, & Discussion] GodMustaine:
But I insist, does this method still work? I always flash roms and similar things. It is the first time that I am going to take on the challenge of repairing an IMEI
[HTC Desire 20 Pro Guides, News, & Discussion] Hassaan24:
Has anyone tried on OnePlus 12 or any sd 8 gen 3 phone?
[HTC Desire 20 Pro Guides, News, & Discussion] SamaelThuum:
Hi, can this be used on a Samsung S22 live demo unit imei 00000000?
[Touch Pro, Fuze General] snark_be:
Hi,

For a few days, I cannot enter the Settings panel anymore. It just doesn't do anything, when I try to start it from the Settings TouchFlo screen or from the Settings shortcut in the Start Menu.

When I run ctlpnl.exe with the right parameters, the corresponding screen open, but I'd like of course to get the full Settings screen.

Any idea what I could do?

Thanks!

snark from Belgium
[Touch Pro, Fuze General] snark_be:
Could anyone export the registry key HKLM\ControlPanel and all its content? I'd like to compare with mine and see if something prevents the loading of Settings. Thanks a lot!
[Touch Pro, Fuze General] DeepThought:
PMail me your email-address and I'll send it to you.

[edit] --> just send.
[Touch Pro, Fuze General] snark_be:
DeepThought kindly sent me an export of the ControlPanel part of his Registry so I could compare it to mine. Differences were minor and not relevant IMHO. Anyway I delete that part from my Registry and import his export but it didn't solve the issue.

Does anyone have another idea or have the same issue?
[Touch Pro, Fuze General] indiana99:
If you recently installed MS Voice Command, version less than 1.69..., that could be the problem. I had the same problem. Several hard resets confirmed MSVC was the problem.
[Touch Pro, Fuze General] mr.right67:
MS Voice Command 1.6 German

Hello Guys ...

I read much about MS VC 1.6 cause Cyberon Voice Speed Dial

doesn´t work well in German - and would like to test it now.

Could someone please provide a download link?!

Thanks! :D
[Touch Pro, Fuze General] snark_be:
No, I've never installed MS Voice Command.
[Xiaomi Mi 11 Lite 5G] Evyatar83:
Or how to install official different rom
[Xiaomi Mi 11 Lite 5G] NOSS8:
Only the Indonesian roms have the miui dialer with the call recorder and for this phone there is none.

Try Xiaomi Eu rom more options and MIUI dialer

Stable or Weekly

https://xiaomi.eu/community/

Whether it's for another stock or custom rom, the bootloader must be unlocked.
[Xiaomi Mi 11 Lite 5G] Evyatar83:
Good guide to unlock bootloader?
[Xiaomi Mi 11 Lite 5G] NOSS8:
https://c.mi.com/thread-2262302-1-0.html
[Xiaomi Mi 11 Lite 5G] zgfg:
The guides can be found elsewhere, just google.

Process is the same for all Xiaomi phones - Xiaomi provides itself the instructions, the tool and they unlock Xiaomi phones themselves
[Xiaomi Mi 11 Lite 5G] Evyatar83:
I have to wait 168 howers
[Xiaomi Mi 11 Lite 5G] NOSS8:
This is the procedure.

Sometimes + or -.
[Xiaomi Mi 11 Lite 5G] zgfg:
Of course. No problem with. I did wait with my two phones, too. And exactly 7 days (7x24=168), in a minute (I tried unsuccessfully few minutes before passing the 168 hours and then unlocked successfully a minute or two upon passing 168 hours)

And if you google, you can find pretty reasonable explanation for that policy - they want to make it harder for resellers to buy the phones (for cheaper prices) in China, unlock BL, flash Global or EEA ROM and sell abroad (for the higher price)
[Xiaomi Mi 11 Lite 5G] Evyatar83:
Can i Change rom without unlock?Thers guide to flash rom thru the phone directly
[Xiaomi Mi 11 Lite 5G] NOSS8:
Just update,not changing version.
[Xiaomi Mi 11 Lite 5G] Evyatar83:
In the video you can change version..i tried but not secseed
[Xiaomi Mi 11 Lite 5G] zgfg:
I don't understand the language in video. Anyway, locked Bootloader prevents flashing

And don't believe to whatever YT (better read the stuff on XDA), otherwise you may sooner or later brick your phone and then, paying for the authorized EDL help will be costly

There are many people on XDA who followed one way or another some YT 'guides' (maybe the authors not providing full instructions or users not paying attention and not making their own research to read and learn before flashing something, or both), resulting by bricking their phones.

But they learnt the lesson for 30-50 Euros 😩
[Xiaomi Mi 11 Lite 5G] Evyatar83:
Thanks
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] radunn55:
I've factory reset several times trying to get FTB to function properly. The installation proceeds without error as far as I can tell. However when I open Chrome and click on "any" link/url a fast splash screen occurs: "The requested action is not permitted. Check Parental Control settings and try again."

This error also appears in the HD8 Settings on certain menu options. Does this have anything to do with my Amazon/Google account settings?

After Reset to Factory the default Fire OS is v5.7.0.0 before updates are applied and FTB installed. Thank you for your time and support.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alecxs:
looking forward to see flashable zip for deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
They are already removed from the provided vendor.img but sadly that didn't fix the problem, I will look for a solution.

View attachment 5581233
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quent1du58:
Many thanks for all your work. My SM-T590 is running on it for almost a day now (with MicroG and Magisk). Installation was not straightforward (I've had to factory reset after flashing LineageOS since the setup process kept freezing), but definitely easier than with the other GSI images. Not really sure if it is also related to the 32 vs 64 bits kernel, but the tablet definitely feels snappier than with BloatUI OneUI.

I've found only three problems so far:

The tablet does indeed randomly freeze from time to time. It does seems related to Magisk, but definitely not a huge deal since it rarely happens. I'll try to pinpoint the problem with a logcat if I have some time.

Only half of the speakers are working (but still not a deal breaker).

My book cover does not wakes up or put the tablet into sleep. It seems that one of the sensors is not working properly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Thanks for the feedback!

I'm working on a non-GSI variant since I couldn't fix the keystore errors and other issues on GSI.

However I have no previous experience on Android builds, and our device has no custom ROMs or device trees to begin with, so it might take a long time to fix everything. Also the 3.18 kernel is really old for Android 12.

Currently basic functionality like WiFi, Bluetooth, OpenGL, sensors, and lock screen are working, but there is still a lot more left like DRM, cameras, audio, GPS, etc.

As for your 3rd issue, I would suggest enabling double tap to wake in Phh Treble Settings.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quent1du58:
That's some great news. I've also tried to port LineageOS to this device (mostly as a way to learn new things, since Android/LineageOS/kernel aren't really my areas of expertise) using both Rupansh and heavily customised Xiaomi Redmi 5 (Rosy) sources trees without any success.

Have you managed to boot a non GSI build? I've tried to compile LineageOS 19 Using your device and kernel trees, plus Rupansh vendor tree. Build went fine, I've even managed to flash and to boot into recovery (which needs fstab fixes), but no way to boot a freshly flashed zip for now. I'm going to continue my research and will share any progress.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Yes, currently my tablet runs a build based on my device tree on GitHub but it's highly experimental. Basically I use GitHub only to have some revisions of the device tree for backup and testing purposes, that's why all the commits are named asd. 😆

I guess your issue will be that you use vendor files from Rupansh (since that's missing 64-bit stuff from Galaxy A20s vendor), here I have uploaded the ones I'm using: https://mega.nz/folder/zXZzVZaL#95t8V7DSr0rX7W0lTZmhHQ

Copy them to a folder named ~/system_dump for example, create a subfolder named system and another subfolder named vendor under the previously created system folder. Then you can use the commands below to extract the required proprietary files from system.img and vendor.img. Assuming you have everything in ~/system_dump folder:

sudo mount -o loop,rw system.img system

sudo mount -o loop,rw vendor.img system/vendor

Then go to your downloaded LineageOS source/devices/samsung/gta2xlwifi and run:

chmod +x extract-files.sh

chmod +x setup-makefiles.sh

bash extract-files.sh ~/system_dump/

Also you will need to apply some patches to the LineageOS 19.1 source to bypass eBPF requirement which is not available on our 3.18 kernel. Download Treble patches from here: https://github.com/phhusson/treble_...ases/download/v413/patches-for-developers.zip

Apply patches/platform_system_bpf/0001-Support-no-bpf-usecase.patch to system/bpf and patches/platform_system_netd/0001-Support-no-bpf-usecase.patch to system/netd in the source using git apply /path/to/.patch. You can also apply the Camera2 API patches mentioned in the first post but the camera doesn't work anyway currently.

The resulting build is barely usable, working stuff are mentioned in my previous comment. Feel free to try different versions in device.mk and add / remove stuff in proprietary-files.txt, I guess I messed up lots of things since I never built a device tree before.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quent1du58:
Thank you for all those details, I've managed to build a working image. I still experience the same problems so far:

UI crashes a lot shortly after rebooting

Inserting a SD card freezes the system

But since I now have a way to build my own releases, I'll try to fix things. Since I've forked your repositories on Github, I'll send you pull requests when needed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Glad you managed to get it work!

Yep, the UI hangs and crashes are happening here too, haven't found the cause yet. Logcat shows a blocked state and dumps tons of lines from the kernel. The interesting part is that sometimes, like in 2 of 10 reboots it starts up correctly without any freezes.

If I have some time I will continue fixing the tree as there are lots of randomly added and unfinished stuff which I did for testing purposes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] seeiu:
I tried to flash twrp in the download mode but it showed "only official binaries are allowed to be flashed". What's wrong?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] quent1du58:
You need to flash TWRP using a patched version of odin.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DerSammler:
Thanks for the great tutorial. The Rom runs so far quite well.

But when I want to flash microG_Installer_Revived with TWRP I get a 235 error.

When I connect the tab to the PC, the internal memory and SD card is not shown to me on the PC.

Although, the tab is recognized by the PC.

Is there a trick or do I have to live with it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
I just updated the first post with some instructions about MicroG. Basically you will have to flash it as a Magisk module, also use FakeGApps to have Signature Spoofing support.

Yea, that's a known issue with both GSI and non-GSI variants, it'll be fixed as I find the cause. Alternatively you can use adb or some wireless file transfer app like AirDroid.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DerSammler:
What do I do if I want to go back to stock Rom?

Can I simply flash with Odin original Android 10? Or is there anything else I need to consider.

Thank you very much.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Exactly, it's enough to flash the latest stock ROM with Odin to revert the changes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DerSammler:
I have installed lineage-19.1-20220525-UNOFFICIAL-gta2xlwifi according to the new instructions

unfortunately, when I start the tab, I get a red message—kernel is not seandroid enforcing -.

Afterwards, when the tab is started, I also get the following message on the home screen

Android System

There is an internal problem with your device. Please contact the manufacturer regarding this.

Are these two messages normal? Or am I doing something wrong. I have now installed LOS_19.1_64 again. Thank you very much.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Yes, these messages are completely normal in the ROM's current state and can be ignored, they won't cause any further issues.

The kernel message is related to the SELinux permissive state which is listed under known issues, the other one shows up simply because I haven't patched the LineageOS source code to hide it.

Disable AVB check · phhusson/platform_frameworks_base@a917ed6

This avoids the message "There's an internal problem with your device. Contact your manufacturer for details." on some AVB 1.0 devices. Change-Id: Ia54b857a3e98e2639d6bcc0ba713809704...

github.com
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DerSammler:
Thanks a lot for your help.

I find the Rom really great, super work you do. The system is really faster.

To transfer data I have MyPhoneExplorer and that works very well with it.

I'm curious what there will be updates for this Rom.

Wish you a quiet Sunday.

Greetings: Dirk
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Thanks for the feedback!

Yea, I'll try to improve things but as I stated in my previous posts, I'm just an average user with no Android porting experience, so it might take a while. I'll post new releases with monthly security updates from Google and maybe some fixes.

Also please note that the ROM isn't secure yet, the lock screen can be easily bypassed with TWRP since encryption isn't enforced, and adb with root access is enabled by default for debugging purposes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DerSammler:
I have a question about the GSI Roms?

Which roms can I flash on the Galaxy Tab A (T-590).

The roms must be Binder compatible, I know that.

Can I only flash Binder a64, or can I also use the Binder arm 64 Rom?

Thank you very much.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Here is a list of the ROMs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

There are 3 types of GSI ROMs; arm (32-bit), a64 binder (basically 32-bit with some 64-bit stuff on the kernel side), and arm64 (64-bit).

In order to use a GSI, you will have to reflash stock boot and vendor images first. With stock boot and vendor you can use a64 GSIs. Alternatively you can install my arm64 boot and vendor images from the first post to run an arm64 GSI, but the boot image has to be modified to disable kernel LMK which causes freezes and crashes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Nuwisam:
Thank you so much for your amazing work! It is really useful for me since I bought SM-T590 and faced x64 arch requirement for one of my desired apps - you saved me!

Is there anything to do about GPS? Why exactly is it not working? Is it some common problem in LineageOS or is this specific to this tablet? I would love to try to help if capable.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
I haven't really looked into fixing the GPS yet, it's definitely an issue with the device tree, so it can be solved. It might be a missing service or a vendor blob, maybe some permissions from initrc, I'm not entirely sure yet. I'll have to track back how it works on stock or other devices with the same SoC.

View attachment 5627443
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] cnukep:
Hi) can you do please the same for T595 ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
In theory the installer can be modified to allow flashing on SM-T595 too, but of course the device specific features like LTE will not work. Fixing these stuff would be quite difficult since I don't own the LTE variant and can't test the changes.

Also, as I can tell from my SM-T590, the modem has issues even after reverting the kernel patch that freed up some RAM, no success with fixing the GPS yet which is routed through some modem interface.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DerSammler:
@UDPSendToFailed will there still be updates for Lineage 19.1 gta2xlwifi?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Yea, I'll upload a new build with improved Double Tap to Wake reliability and some audio-related fixes as soon as LineageOS maintainers merge the android-12.1.0_r7 sources so it'll have June security patches too.

https://review.lineageos.org/q/topic:S_asb_2022-06
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
I have uploaded a new build, however fixing the quad speakers didn't go as I planned. There are tons of different control values for the audio paths, so it'll take some time to figure out which one is used for the 2 speakers on the top.

View attachment 5636075
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Clarobollo:
You are awesome! Keep up the good work
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] philip130683:
Thanks for the ROM. What am I doing wrong if the screen remains black after flashing in the system?View attachment 5657287
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
That's indeed a strange issue, I've never experienced anything like this. Are you using any modifications like Google apps or Magisk? Did you wipe and format data before flashing the ROM? Also, did you update to the latest stock ROM (T590XXS3CUK1) before doing anything?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] philip130683:
no I didn't make any changes. yes the last stock was up. i'm back on the samsung rom again. thank you.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Netriver:
Hi. After setup, cant use navigation. Navtab dont show in settings. How i can fix that?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Hey!

Do you mean the 3-button navigation bar?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Netriver:
Ye.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
I'll take a look at it if I can add that to the next update.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
New build is up with the System Navigation menu enabled.

Also, I have uploaded the patches that are applied to the LineageOS source code. https://github.com/UDPSendToFailed/lineage_patches_samsung_gta2xlwifi
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Clarobollo:
I'v been using this rom for around 2 months and it works like a charm.

I forced adoptable storage through adb to mount a sd card as internal, 32gb isn't enough for me, every app works fine
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Thanks for the feedback! That's good to know because I haven't tested if adoptable storage is usable or not.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bolaiya:
Will this ROM work for a Galaxy Tab A (SM-T510) ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
No, it's for SM-T590 only. The SoC in the two devices is entirely different so it won't work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Just an update about the quad speakers.

I've managed to enable all the 4 speakers, here is the commit. The binary will be included in the next release for those who want to experiment with it.

So, all the 4 speakers are working after running the audioloader binary mentioned above, but here comes the funny part. The sound quality is basically ununsable, it's distorted and crackling like a PC speaker from the 486 era.

As far as I can tell from the logs, on the stock ROM the whole thing is configured by two effect libraries, called lib_SoundBooster_TDM_ver100.so and lib_SoundBooster_ver900.so.

View attachment 5701815

View attachment 5701817

These libraries seem to be loaded by /system/lib/libcorefx.so which depends on various other things, so it's deeply integrated with OneUI.

I've tried several methods to make them load on LineageOS but haven't had any success so far.

Ideas are welcome, if someone here has the knowledge to solve this issue, feel free to contact me.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] St1k1:
Just stopped to comment that you are a legend mate! Stumbled across this one a couple of weeks ago. Way, way better than Sammy OS..

For any curious I haven't experienced any major glitches, freezing or restarts except for the known lower speakers only thing. I do wipe Data, Cache and Dalvik after installs as a personal preference.

Trying your latest today..

Thanks!!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BenisMusical:
Hey - I am currently trying to install this rom and TWRP on my T-590 tablet but when I try to flash TWRP it reads "Only official released binaries are allowed to be flashed"

I am using the previously linked customer version of Odin "Odin 3.14.1 3B PatchD" and the issue persists.

Do I need to enable any settings within android as a pre-requisite?

In download mode it reads:

Odin Mode (High Speed)

Product Name: SM-T590

Current Binary: Samsung Official

FRP Lock: OFF

OEM Lock: OFF

KG Status: prenormal

Warranty Void: 0x0

Qualcomm Secureboot: Enable (CSB)

RP SWREV: S1, T1, R1, A3, P3

RP SWREV: K 3, S 3

Secure Download: Enable

DID: 00b (etc...)

download mode !!

Only official released binaries are allowed to be flashed

Any help would be greatly appreciated, thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Hi!

You might need to follow these steps to unlock the bootloader properly: https://xdaforums.com/t/recovery-ro...-sm-t595-sm-t597.4054225/page-6#post-86851945
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] BenisMusical:
Thank you! Flashing now! :D
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 343N:
Bluetooth audio seems to be broken? My WH-1000XM4's connect, but audio output stays on the speakers. Even though the device specifies it's outputting to the headphones, whether output is set to headphones or speakers while connected, the audio is always output through the speakers. Unfortunately this is a dealbreaker for me, but if there's a fix available, I'd love to use it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Hmm yep, it might be broken as I checked Bluetooth a few months ago if it works but haven't tested Bluetooth audio at all. Could you upload the output of adb logcat -d > logcat.txt after connecting to the headphones and starting audio playback?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Edit: Updated build that fixes the UI flickering is available in the first post (20220930).

New experimental build of LineageOS 20.0 (based on Android 13) is up.
​

Dirty flashing should be fine, but it's impossible to predict if it will work for everyone, so

create a backup of your important data

before updating. You'll also need to have a backup in case you want to downgrade to 19.1 after testing 20.0.

This build is still in very early stage, some features might be missing or not working at all.

Known issues in addition to 19.1:

- Using features like Night Light causes some weird flickering on various UI elements, can be fixed temporarily with enabling Developer options -> Disable HW overlays.

View attachment 5720957​