yashsingh1/xdaforums huggingface dataset:
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] da243K:
Data roaming in the EU is not working.

The problem existed on previous version (https://xdaforums.com/t/discontinue...or-the-asus-zenfone-5z.4513023/#post-88752877) and does not seems to be fixed with the current version.

My 5z has 2 SIM from 2 different French operators. As I am currently in Italy, I didn't have any data roaming with my phone (Lineage 20). In a hope to fix it, I upgraded to the latest LineageOS with latest MindTheGapps, data is still not working. Phone and SMS are OK. If I put my SIM card in another phone, data roaming is working.

I tried rebooting, reset networking, setting up Manual Network Selection, changing Network Type, with no success.

Build number : lineage_Z01R-userdebug 14 AP1A.240505.005 b31a040a3c

LineageOS version : 21-20240514-NIGHTLY-Z01R
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
@schlug I retract my statements! There might be something wrong with our sepolicy or maybe the USB HAL. Can you please try to connect to Android Auto and then logcat and same with quick charging?

I think it's mainly because USB HAL 1.0 was depreciated so we had to switch to 1.3
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] schlug:
I'm sorry, I can't create a logcat because the device is no longer recognized on the computer via USB. The only remaining USB function is slow charging.
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] schlug:
I am no longer sure whether the problem with EU data roaming is due to the operating system (LOS 20 or 21 or ArrowOS 13) or whether it is a problem with the Caller ID Spoofing Protection introduced by the EU since December 1st, 2022. This may result in incorrect transmission of the SIM card information. With LOS 21 I no longer have roaming problems in Austria or France (with a German SIM card). But don't ask me why.
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
@schlug it is possible to connect to adb via WiFi

Enable Developer mode in Settings

Go into Settings > System > Developer Options > Wireless ADB

Enable it and then on your PC do adb pair and include the IP and port and then enter the code

Once paired then do adb connect and IP and port it shows on that main wireless adb screen
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] raix1415:
There have been quite a few issues raised that microphone stopped working in apps like Google Meet, Zoom, Signal, Viber, etc. since upgrade to LOS 21. Can anyone confirm whether mic is ok with such apps on this Asus, pls?

Also, I would like to ask, does enabled 'tap to wake' option still cause restarts, pls?

USB issue is also unfortunate. Thank you for working on it!
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] schlug:
I also have problems with phone calls using the Signal app. It often happens that I can't hear the other party for about 10 seconds or the microphone doesn't work for a few seconds. In fact, this only occurs under LOS 21. I had previously thought this was a problem with my WiFi (Ubiquiti), as also the stock ROM didn't work very well with the Ubiquiti access points. I only used Zoom once (about 10 minutes) without any problems. I didn't try 'Tap to wake' again.
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
A new test build is going up! It's uploading meow so it might take 30 mins to be available. lineage-21.0-20240612-UNOFFICIAL-Z01R contains some fixes for USB so I need quick charging and Android Auto tested. I also merged the latest changes from the LOS QCOM sdm845 kernel repo too. @schlug can you especially test this build too please?

LineageOS for Z01R - Browse /lineage-21/lineage-21.0-20240612-UNOFFICIAL-Z01R at SourceForge.net

sourceforge.net
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] schlug:
I have installed the latest build. Unfortunately, no improvement. Quick charge, Android auto and connection to the computer still don't work. Maybe my USB port is broken. Thanks for your hard work anyway.
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
Hmm @schlug there's a chance it is... The ultimate test if it is software or hardware though would be to revert to stock ROM to test?

The latest test build Android Auto did work for me but I haven't yet tested quick charging
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
New test build is up! lineage-21.0-20240704-UNOFFICIAL-Z01R contains compatibility fixes for Android 14 QPR3 and updated CNE, DPM, QMI, RIL and IMS blobs from A13's fair phone 3 so please test all cellular stuff like VoLTE and mobile data and report any bugs with logcat

LineageOS for Z01R - Browse /lineage-21/lineage-21.0-20240704-UNOFFICIAL-Z01R at SourceForge.net

sourceforge.net

Please I need a few testers to confirm these changes are good it's pretty much the last thing I'm waiting on to go official on LOS again
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] PriCap:
Thank you for your work. After I got a new phone, I have a chance to take a look on this OS in the first time and install it.

It works well more than I expected but since I solely use just for hotspot, I haven't encountered to bug that hit me hard yet.

So far, only weird thing I found is default camera, if I set video quality to 480p it will crash. And I need to clear storage app to reset and make it work again. (I got logcat file in case you need to see.)

Current build on my device:

lineage-21.0-20240618-nightly-Z01R-signed

MindTheGapps-14.0.0-arm64-20240612_135921
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] dannychow:
I tried this test build on my 2nd phone for a few days. I mainly used it for web browsing, online store app, chat app, etc. It looks stable and smooth so far. (y)
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
@PriCap Hmm weird lol... I think I'll chalk that up to an Aperture camera app acting up. Does that video quality work fine in other camera apps?

Thanks for testing btw! (y)

@dannychow thanks as well for testing. Was that with mobile data?

Also, by chance have you two tested calls and texting? Mainly I'm curious if VoLTE works
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] dannychow:
The voice call, sms, and LTE data worked well. I even put 2 SIMs together into the phone and both could make call.

But when I used voice, I was not very sure it was using VoLTE or not as the status bar only showed "LTE" icon.
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] dannychow:
I got an issue of using a bank app (icbc) in LOS 21.0 (both the official and the unofficial versions). It hang in the app splash screen. When I used LOS 20.0, the app was ok. I 'm not sure whether it is the problem of the app or LOS.

Anyway, logcat attached.
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
@dannychow thanks for testing! That logcat for the icbc app doesn't have any specifics but it might need to be updated for QPR3 support? Otherwise some banking apps rely on SafetyNet and even bootloader lock and will exit or crash if those checks don't pass. Sometimes Nintendo apps do the same too, so you could try Magisk and mods to try and cheat SafetyNet and bootloader lock?

I'm going to push for Z01R official builds to resume, thanks again for testing!
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] dannychow:
For the issue of icbc bank app, Magisk & mods don't help.

In another forum someone mentioned that this kind of issue happened after Android 14 QPR2. Someone created the issue in LineageOS platform already:

https://gitlab.com/LineageOS/issues/android/-/issues/7159

I may need to wait for either the bank app or LineageOS to fix it.

Thanks for the new release build anyway~ :) @ThE_MarD
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
@dannychow oh nice find on the gitlab issue, yeah it seems to be a platform issue, so it's either AOSP needs a fix or the apps need compatibility fixes.

On Motorola devices, A14 QPR3 broke Motorola Camera app for all devices and we had to haxxs them to fix it as Motorola doesn't have any devices on A14 QPR3. I'm guessing this is a similar issue where some apps are trying to access certain things that are now blocked for device security
[Asus Zenfone 5Z  ROMs, Kernels, Recoveries, & Othe] ThE_MarD:
Apparently there's a bad APN issue so some builds were taken down. The next build should have fixed APN's
[8125, K-JAM, P4300, MDA Vario General] chakarbaz:
Hi

The "New outgoing port" from blue tooth menu is missing from my device. I actually need to use SimpleSms or smartGSM in order to synchronize the SMS from my PPC to Nokia 6120c.

Both devices can communicate via BT, but the outgoing port is needed for above mentioned tools.

I am very much confused about it.. :(

I have read some threads, but didn't get any idea about this, so posting my own question here.

Kindly provide some help, that how can I add some outgoing port in the blue tooth options.

I'm using (Jas Jam) SPV M3100 (Orange)

Thanks a lot :)
[8125, K-JAM, P4300, MDA Vario General] bjhamltn:
Wireless RS232 communication between PC and Bluetooth Enabled Phone

Setting Up your PC

Go to Bluetooth settings on your desktop and tap to Devices. Select your device and click properties.

Tab to services and make sure that Direct Dial-Up Network is not selected.

Tab to COM Ports and click the Add button.

Select the radio button for Incoming. Click OK

There should now be a COM Port listed.

Click OK again.

Open HyperTerminal configured for the COM port that you just added.

Open the COM Port. If the COM port is not open your Bluetooth phone will not see it.

Setting Up your Bluetooth enable phone

Make sure that the COM Port you configured on your PC is still open.

Go to Bluetooth settings on your phone.

Tab to devices. Select the device that corresponds to your PC’s Bluetooth adapter.

You should now be in Partnership settings. Click Refresh.

The Serial Port service should be available.

Check the check box for the Serial Port service and click save.

Tab to COM Ports.

Tap New Outgoing Port and select the device corresponding to your PC’s Bluetooth adapter and click next.

Select a com port from the combo box and click finish.

Note: If you select one that is not available you will get a message to select a different COM port, you get this message because the COM port that you selected is already being used.

You are now done setting up your PC and Bluetooth enabled phone for serial communication.

You still need to match up the serial port settings on your Phone with the setting on your PC.

Baud Rate

Stop Bits

Parity

Handshaking
[8125, K-JAM, P4300, MDA Vario General] a_petrov303:
how can I add a new outgoing port on my Toshiba TG01 running WM 6.5?

the instruction above work for a partnership with PC, but I need it for connection with my car Bluetooth
[Realme 9i] logopek:
Anyone have a overlay fix on gsis for device?
[Realme 9i] smartsmart:
Check realme 9i telegram group. All my fixes were posted there.
[Asus Zenfone 10] neatly:
If the bootloader unlock tool is ever reinstated, is it expected that the US version of the device will be unlockable? With some other manufacturers (Sony, Samsung) it's my understanding that generally only the international versions can be unlocked. But maybe no one knows in this case since AFAIK previous Zenfones did not have US versions.
[Asus Zenfone 10] TheStylus5Gmodder:
I think it should.
[Asus Zenfone 10] Voidseesaw:
I have a sort of related noob question: with bootloader unlocked will it be theoretically possible to switch an International phone to US? Or is the hardware different as well?
[Poco X3 GT (Redmi Note 10 Pro 5G)] alfablac:
I see apk sites added this version on Dec 1st, but I just got my update today.

This update includes "App content search" in the app drawer which allows you to type something like "New mail" and get an action of Gmail that composes a new email.

There's a security flaw on this app that is so dumb that I can't believe they pushed this to the public lol

Some hidden apps even get action suggestions right after opening the app drawer.

You can also open Hidden apps with it just searching by the app defeating the whole purpose of hiding apps with a password.

Deactivating the feature fixes it, but you can pretty much reactivate it without any password being asked

I don't even know how I can report this, trying to rollback to an older version in the meantime
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] ata-kaner:
Team Win Recovery Project

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

What's TWRP?

Team Win Recovery Project is a custom recovery for Android devices.

It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.

Read more about TWRP here: https://twrp.me/about/

How do I flash and set it up correctly?

Please notice that the following guide is meant for full stock devices, if you've already rooted your device you can skip it and flash directly the recovery without any extra steps.

Before starting, make sure to backup all your data and important files stored in your phone, since this procedure will format your data partition.

Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image.

Make sure your phone's bootloader is unlocked, follow the guide below in case it isn't:

Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).

Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button.

Reboot your phone in recovery mode: while it still plugged in your PC, hold both the power and volume up buttons.

Once TWRP has booted you need to format again your DATA partition in order to be able to boot in system again. To do so touch Wipe>Advanced wipe and choose these partitions on the screen.

Bugs:

Decryption will only work if no password/PIN/pattern is set in OneUI.

Decryption only supports FBE V2, so this recovery can't decrypt stock firmware.

Hey, where is the multidisabler?

Gone and will never get any support from me.

Download:

twrp.me

Patched VBMeta

Github

Donations

If you like my work for S20 FE development, feel free to send a donation.

Buy Me A Coffee

Sources:

Device tree: https://github.com/TeamWin/android_device_samsung_r8q

Credits:

Samsung for the kernel source code

TeamWin for their awesome recovery

@BlackMesa123 for A52sxq tree
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] mezacorleehone:
Hello colleague.

I'm glad to see an update on twrp.

See that you found the microSD problem, as you mention that it is difficult to solve, let's hope in the future to finally see SD working,

EROFS support for use in s21 fe ports and other future read-only systems.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Cilekcigs:
Hello sir, I am glad that there is some active development regarding custom recoveries but may I know how does this differ from JOSH1X's build?
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] ata-kaner:
Josh's build is based on afaneh's old prebuilt twrp. Mine is built from source with a new device tree so it includes all new changes from TeamWin source. Visual artifacts while scrolling are gone and I'm trying to bring decryption support and sdcard too.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Verygromf:
hey, just got this phone and unlocked the bootloader alright.

however, I can't get this to work: the OS is on the latest version WK8, and when flashing vbmeta_disabled.tar it succeeds then restarts normally, doesn't go to the recovery.

When flashing twrp, got a success too but actually the stock recovery remains.

And lastly, trying to flash manually with fastboot fails, all commands exit with an error "unknown command".

Any idea what I should do ? (tried to downgrade to a v12 rom, but knox apparently won't allow it)

(it's a G781B)
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Verygromf:
ok nevermind, managed to do it but it's been painful :

install magisk, patch the AP file, flash it

install the twrp app, copy over the twrp.tar, flash.

It's working, although only when rebooting to recovery with adb, can't find the proper key combination.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] ata-kaner:
You need to boot to recovery after flashing else booting to android will replace the recovery with stock one. TWRP will disable that replacement when you boot first time.

Use vol up + power to reboot to recovery. You need to plug your phone to your computer as well. It's a samsung security feature.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Ckr0n:
Please add this to first post if you can as something going wrong, like TWRP not sticking around, can lead to less knowledgeable people to try different hacks and such after failure (TWRP not sticking around). I had myself quite a bit issue with this, didn't apply any hacks of course, and it was very simple once I read this post of yours. I also have done this before on a different samsung device but I completely forgot about the security feature.

Thank you for your help!
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Verygromf:
Good to know -- indeed might be good to add this to the initial post.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Denisuu:
I'm getting 'Only official released binaries are allowed to be flashed(vbmeta)' I tried Odin 3.13 and 3.14.4.

I'm on firmware G781BXXS9HWK8 I can't flash anything older or I will get a fused binary error.

FRP Lock : OFF

OEM Lock: OFF (U)

KG STATUS: PRENORMAL

EDIT1: I even tried extracting the boot.img vbmeta.img and vbmeta_samsung.img from the latest FW on SamFW then patched the boot.img with Magisk and vbmeta with and vbmeta_disable_verification. The error remains the same.

Also tried putting my clock a week ahead and to 2019..

EDIT 2: I also tried to follow the official Magisk instructions and patched the whole AP_[device_model_sw_ver].tar.md5 file. Then tried to flash magisk_patched.tar as AP, together with BL, CP, and CSC but still the same error.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] 3mel:
KG STATUS of PRE-NORMAL means nothing will flash in Odin. you usually get this if you flash stock and then go straight into flashing twrp without booting the phone up once and completing the setup (minus accounts).

if you're not also using a vbmeta-disabled.tar file with the twrp.tar it won't flash either. anytime you flash something unofficial in Odin vbmeta-disabled is needed.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Denisuu:
I never tried to flash anything else than vbmeta. I followed the instructions clearly.

The Magisk documentation says:

But putting the clock of my device a week ahead doesn't seem to solve it. Maybe I actually need to wait a week?
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Denisuu:
I had to do all these steps first, what a hassle! I hate Samsung! Why can't it just be 'fastboot oem unlock' and ' fastboot boot twrp.img
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Klappp:
I cannot boot into recovery after flashing with odin. The bootloader warning does not go away until I let go of the volume up + power buttons and once I do it just boots normally
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] 3mel:
use a USB cable still connected to your PC when doing the key combo.

if you don't get into twrp straight away you'll have to flash it again as the stock recovery is restored unless we manage to boot into twrp.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] ata-kaner:
NEW UPDATE

I uploaded a new build for TWRP.

This build disables decryption support so we can use TWRP with encrypted custom roms. TWRP will never support decryption or sdcard in the future. Thank you samsung.

Disabling decryption support also broke init support for some reason. It is disabled as well and i'll try to bring it back.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Denisuu:
I updated to this recovery on my SM-G781B 5G and tried to update crDroid, but now my device is bootlooping. When I try to restore my backup I receive an error. Disabling 'Mount system partition read only' doesn't help.

When doing a factory reset I also see the red text at the top of the screenshot.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] skrreddy:
Power off your mobile and go to Samsung official download mode using combo keys and data cable which has connected to laptop/desktop and flash stock rom using odin3 may be it will help to boot your mobile in stock rom.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] skrreddy:
When I tried first time in my s20fe I also faced bootloop issue after that I do same method to boot stock rom. So may be it will help.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Denisuu:
Yes flashing back stock through Odin > vbmeta > then the new recovery > crDroid worked.

Thanks!
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] skrreddy:
No, when I'm back to stock rom after tired same instructions which posted in this page to flash custom roms then it's works for me.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Denisuu:
Restoring backups still doesn't work though. I sill get the error "System partition cannot be wiped"
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Cilekcigs:
Decryption support wen?
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] MauriJ2001:
When the dev can find a method to get working it is a mess try to make working decryption on samsung SD865
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Aadiraj:
while flashing vbmeta in odin it says "only official released binaries are allowed to be flashed(vbmeta) "

how to resolve this?
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Cilekcigs:
Go to stock oneui, connect to internet, enable dev settings(tap build number 7 times on about phone page), enable oem unlocking, unlock bootloader. Now it should be fixed

You need to connect to internet for oem unlocking to show
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] 3mel:
if it was just after a stock flash then check your KG state from download mode. anything but ''checking'' showing there means things aren't gonna flash.
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] Aadiraj:
I actually figured it out earlier after some experimenting lol as it wasn't mentioned in the steps so i was a bit confused, all good now tho.

Thanks
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] friin:
Hey folks,

I hope you're all doing well. I've got a rooted sm-781b running on Android 12 and I'm considering updating to Android 13. Before I proceed, I have a few questions I was hoping you could help me with.

1. Firstly, does Android 13 support Afaneh 3.7.0 12.1 or this version offered here, and will Multidisabler 3.1 still work with it? Are there any known drawbacks or issues I should be aware of before updating?

2. Can I still perform backups and restores with this TWRP version offered here on android 13? Can the backup created with this TWRP version and Android 13 be restored to another S20 device in case mine gets lost?

3. Additionally, I've been wondering about the process of updating a rooted phone. In the past, whenever I flashed a new update, I always performed a data wipe, factory reset, and re-patched the boot.img with Magisk, and installed TWRP essentially redoing all the steps. Is this extensive process really necessary, or is there a simpler way to update a rooted device without losing data or having to redo the root procedure each time?

Any insights or advice you could provide would be greatly appreciated.

Thanks in advance!

Friin
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] papitoonichan:
Does it also work for SM-G780F exynos?
[Samsung Galaxy S20 FE ROMs, Kernels, Recoveries, &] papitoonichan:
or when are they going to release a twrp recovery for exynos?